Halopedia Era UNSC.png
HaloArray.png

UNSC Prophecy

From Halopedia, the Halo wiki

Revision as of 14:32, February 28, 2021 by SpyglassUnitBeta (talk | contribs) (→‎Production notes: adding archive fields to ref/site)
UNSC Prophecy
File:UNSC Prophecy.png
Production information

Class:

Marathon-class heavy cruiser

Specifications

Length:

1,192 meters (3,910 ft)[1]

Width:

293 meters (960 ft)[2]

Height:

375 meters (1,230 ft)[2]

Powerplant:

Deuterium fusion cores

Slipspace drive:

Equipped

Hull:

2 meters of Titanium-A battleplate

Armament:

Service information

Destroyed:

February 3, 2531

Participated battles:

Battle of Bliss
Harvest campaign

Affiliation:

UNSC Navy

 

"Is that the Prophecy? I can see why there were no survivors."
— Professor Ellen Anders mistaking the UNSC Spirit of Fire for the Prophecy

The UNSC Prophecy (98877) was a Marathon-class heavy cruiser commissioned by the UNSC Navy in service during the Human-Covenant War. Its onboard artificial intelligence construct was FitzGibbon.[3]

History

Early history

Captain James Cutter once refused the position of commanding officer of the Prophecy, for the chance to command the UNSC Spirit of Fire.[4] Following the Battle of Bliss on February 13, 2526, the Prophecy's crew recovered the black box of the UNSC Accra, an Office of Naval Intelligence survey vessel. This recovery was significant, as the black box contained a detailed account of the colony's downfall. This black box was instrumental in leading dissident leaders among the Outer Colonies to have an agreement of peace with the UNSC.[5]

Harvest campaign

Main article: Harvest campaign

In February 2531, the Prophecy was heavily damaged during the ongoing Harvest campaign. Sergeant John Forge was sent aboard the ship in a Pelican with his squad to recover survivors, but was redirected by Spirit of Fire's AI, Serina, to purge its NAV database. Prophecy's AI, FitzGibbon, prevented Forge from accessing the database because of the latter's poor service record, but eventually relented when informed that his actions breached the Cole Protocol. Allowing Forge to purge the database, FitzGibbon then initiated a self-destruct sequence, destroying the ship to deny its access to the Covenant.[3]

An ONI prowler was present when the Prophecy was damaged, but refused to help because the radiation emissions would have compromised their stealth systems, rendering their only tactical advantage moot. The survivors were also deemed to be a lost cause, the radiation doses they had received were too much to survive. Such a callous assessment of living humans greatly upset Captain Cutter.[3]

By February 4, debris of the Prophecy including armour plating bearing the ship's name had fallen onto the surface of Harvest, landing near the UNSC's firebase facility, Alpha Base.[6]

Production notes

To assist in writing Halo Wars, Graeme Devine wrote a series of self-described "fan fiction" to give the team at Ensemble Studios a window into life aboard the Spirit of Fire. One log, written from the perspective of nurse Lulu Hershey, describes that the crew of the Prophecy were forced to evacuate the ship in lifepods. Unfortunately, the lifepods were caught in the radiation pulse of the ship's engines.[7] Half of the evacuees were subjected to extreme amounts of radiation, managing barely to survive, while the other half were killed. The lifepods were picked up by the UNSC Spirit of Fire, where the survivors were made comfortable. All of the Prophecy's survivors died slow, agonizing deaths, with no spare morphine to ease their pain.[8]

Gallery

List of appearances

Sources

  1. ^ Halo: The Essential Visual Guide, p. 42
  2. ^ a b Halo 2 Marathon-class heavy cruiser 3D model data
  3. ^ a b c Halo Wars: Genesis
  4. ^ Halo Wars, instruction manual
  5. ^ Dr. Halsey's personal journal, attachment: Confidential Directorate Memorandum - Excerpt from Accra log
  6. ^ Halo Wars, campaign level Alpha Base
  7. ^ Graeme Devine's Blog, Serina and Anders talk: (Archive) (Retrieved on Jun 1, 2020) [archive]
  8. ^ Graeme Devine's Blog, Medbay: (Archive) (Retrieved on Jun 1, 2020) [archive]