Battle of the Quarantine Zone
From Halopedia, the Halo wiki
|
Previous: |
|||||||||||||||||||||||||||||||||||||
|
Next: |
|||||||||||||||||||||||||||||||||||||
| Battle of the Quarantine Zone | |||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Conflict: |
|||||||||||||||||||||||||||||||||||||
|
Date: |
|||||||||||||||||||||||||||||||||||||
|
Location: |
|||||||||||||||||||||||||||||||||||||
|
Outcome: |
Strategic Covenant victory
Tactical Flood Victory
| ||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||
- "At the center of this zone, is a Sacred Icon critical to the Great Journey. I must find it."
- — Thel 'Vadamee to Rtas 'Vadumee
The Battle of the Quarantine Zone was a battle which took place on Installation 05 in 2552, as the Covenant and UNSC fought through the Quarantine Zone in search of the Activation Index, known to the Covenant as the Sacred Icon. The battle encompassed an extended conflict between Flood and Forerunner Sentinels that stretched back nearly 100,000 years.
Background[edit]
The establishment of the Quarantine Zone is rooted in ancient history - approximately 3,000 years after the activation of the Halo Array, the Flood under containment on Installation 05 were released. Under normal circumstances Sentinel guards would have been able to keep the parasite under control. Unfortunately, the Flood had access to hosts, and were able to hold off the constructs.
At some point, Installation 05's Monitor 2401 Penitent Tangent was warned by a Forerunner ancilla of a pending outbreak in one the installation's Flood containment facilities. The monitor continued to ignore this warning, and those that followed, for millennia. Within 99,779 years, the containment facility had been overrun by the Flood, with lockdown protocols in effect within the Halo's teleportation grid to prevent further infestation.[2] Eventually, the full force of the installation's Sentinels and Enforcers was mobilized, and a Quarantine Zone was established, surrounded by an enormous wall projecting a powerful Containment Shield.[3][4]
The establishment of the Quarantine Zone was too late to prevent the formation of a Gravemind. Over the centuries, the Gravemind's reach spread throughout the installation,[5] eventually capturing the monitor of the installation, 2401 Penitent Tangent, giving him access to the teleportation grid and causing the structures on the Installation to fall into disrepair.[6]
In 2551, a small Covenant team found a Luminary on Meridian after a battle on the moon.This Luminary was delivered to the Prophet of Regret, one of the three ruling Hierarchs of the Covenant. By late 2552, two Stewards assigned to decrypt the Luminary finally revealed its content to the Prophet of Regret: the locations of the Halo rings, including Installation 05. Hastily assembling a fleet of fifteen warships, the Prophet made his way toward the planet that housed the gateway portal to the Ark, unaware that the planet was in fact humanity's heavily defended homeworld.[7] After a failed invasion of Earth, Regret fled to Installation 05 aboard his flagship Solemn Penance, pursued by the UNSC In Amber Clad.[8]
The Battle[edit]
UNSC Incursion[edit]
- "Proceed to the objective, we'll hold out as long as we can!"
- — Gunnery Sergeant Marcus Stacker, as the released flood overwhelm UNSC forces inside the Sentinel Wall.
Shortly after arriving in the Coelest system in pursuit of the Solemn Penance, Commander Miranda Keyes of the UNSC In Amber Clad demanded the AI Cortana provide her with all information from the installation her father had discovered a month prior.[9] Keyes was able to locate Installation 05's Library, and set out to reach it and secure it's Activation Index before the Covenant could do so. Marine forces lead by Sergeant Major Avery Johnson were ordered to extract from their positions on the ring's surface and rendezvous with the In Amber Clad at the Library while Spartan John-117 proceeded on his mission to