FANDOM


Help This article, The Joyl system Ambushes, is currently under active construction.
Terminal This article, The Joyl system Ambushes, was written by AdmiralAckerson. Please do not edit this fiction without the writer's permission.
Ambushes on the Joyl system
Jiralhanae strike

A Jiralhanae fleet ready to engage a Sangheili battlegroup

Conflict:

Sangheili-Jiralhanae War

Date:

may 8, 2553(Human calendar)

Location:

deep space area of the Joyl system

Outcome:

Jiralhanae crushing and strategic victory

Belligerents

Sangheili hunting forces

Jiralhanae fleet

Commanders

Unknown Sangheili commanders

Chieftain Marturus and 2 trusted commanders

Strength

3 Sagheili battlegroups: 4 ccs battlecruisers and 1 reverence class per group

3 Jiralhanae fleets: Unknown forces, presumably a dozen times larger than the Sangheili

Casualties

all battlegroups completely destroyed

none or irrilevant losses

 


The Joyl system Ambushes were the first relevant engagements in the Sangheili-Jiralhane War.

Although since the Great Schysm the Sangheili actually never stopped fighting the Jiralhanae, all engagements from the end of the war against the UNSC to this defeat were insignificant: in fact, in that time the major naval battles included not more than 3-4 ships, and usually ended with the Sangheili winning or both forces retreating without heavy losses.

A Sangheili Ship Master stated about the Jiralhanae " They seems unsure what to do on the battle, and despite their nature they prefer to avoid us than fight to death".

That Sangheili didn't know that the Prophet of Renovation and the Chieftain Marturus were taking power over the whole Jiralhanae army, but it took some time for the commanders near the Sangheili perimeter to learn about the new leadership and for some time they didn't receive orders or had contacts with their Master packs.


Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.