Editing RCT-06

From Halopedia, the Halo wiki

You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
{{Status|Canon}}
{{Era|Post}}


'''RCT-06''' was the designation of one of the [[Office of Naval Intelligence]] [[remote contact team]] attached to the {{UNSCShip|Rubicon}} during its expedition to [[Installation 00|the Ark]] in [[2554]].<ref name="provenance">'''[[Eleventh Hour reports]]''', Report #4 ''Provenance''</ref>  
'''RCT-06''' was the designation of one of the [[Office of Naval Intelligence|ONI]] [[Remote contact team|Remote Contact Teams]] attached to the {{UNSCShip|Rubicon}} during its expedition to [[Installation 00|the Ark]] in [[2554]].<ref name="provenance">'''[[Eleventh Hour reports]]''', Report #4 ''Provenance''</ref>  


==Overview==
==Overview==
In March [[2553]], [[Commander-in-Chief of the Office of Naval Intelligence]] [[Margaret Parangosky]] approved the deployment of an automated remote-probe delivery system, fitted with highly advanced [[slipspace]] systems, to [[Installation 00]], the Ark. After the [[Battle of Installation 00|events of late]] [[2552]] and the disappearance of [[John-117]], it was decided that reconnaissance should be done on the Ark in order to gather intelligence, recover assets, and establish a secure presence on the structure. The delivery system arrived at the Ark in November 2553 and dispersed its probes. Initial transmissions indicated that the Installation, while damaged, had survived the firing of [[Installation 08]]; however, contact with all of the probes was lost soon after this. In response to this turn of events, a manned expedition to the ark was organized. In December of 2553, the state-of-the art {{UNSCShip|Rubicon}} was commissioned and dispatched from [[Luna]] to discover what had happened to the probes and to continue their original mission. Among its complement the ''Rubicon'' included a number of highly-trained remote contact teams; RCT-06 was the designation of one such team.<ref>'''[[Halo: Hunters in the Dark]]''', ''page 48''</ref>
In March of [[2553]], [[CINCONI]] [[Margaret Parangosky]] approved the deployment of an automated remote-probe delivery system, fitted with highly advanced [[slipspace]] systems, to [[Installation 00]], the Ark. After the [[Battle of Installation 00|events of late 2552]] and the disappearance of [[John 117]], it was decided that reconnaissance should be done on the Ark in order to gather intelligence, recover assets, and establish a secure presence on the structure. The delivery system arrived at the Ark in November 2553 and dispersed its probes. Initial transmissions indicated that the Installation, while damaged, had survived the firing of [[Installation 08]]; however, contact with all of the probes was lost soon after this. In response to this turn of events, a manned expedition to the ark was organized. In December of 2553, the state-of-the art UNSC ''Rubicon'' was commissioned and dispatched from [[Luna]] to discover what had happened to the probes and to continue their original mission. Among its complement the ''Rubicon'' included a number of highly-trained remote contact teams; RCT-06 was the designation of one such team.<ref>'''Halo: Hunters in the Dark''', ''Pg. 48''</ref>


[[File:H3 Guitly Spark Debris.png|300px|thumb|Five smoldering pieces of debris from when 343 Guitly Spark exploded during the [[Raid on Installation 08]]. The only remains of his dead [[monitor]] body.]]
The UNSC ''Rubicon'' arrived at the Ark on August 10, 2554. Upon arrival, it detected a non-standard, heterogenic signal eminatig from the structure's surface. After navigating with some difficulty through the debris field surrounding the Ark, the ''Rubicon'' deployed all of its RCTs, including RCT-06. Because of the damage to both the structural and environmental systems of the installation, the surface conditions faced by the RCTs were extremely severe.<ref name="provenance"/> Over the next several days, contact between the ''Rubicon'' and the numerous RCTs, the latter having come under attack from the Installation's wildlife and constructs at the behest of the Ark's [[monitor]], 000 Tragic Solitude.<ref name="provenance"/><ref>'''Halo: Hunters in the Dark''', ''Pg. 3''</ref> On August 18, RCT-06 managed to successfully return to the ''Rubicon'', being the only team to do so. Despite having suffered heavy casualties, RCT-06 had managed to locate and retrieve the source of the mysterious signal, a "severely damaged armature."<ref name="provenance"/> Investigations by the ''Rubicon's'' science detachment discovered that this was in fact the barely functioning remains of [[343 Guilty Spark]], the former monitor of [[Installation 04]].<ref>'''Halo: Primordium'', ''Pg. ???''</ref> Over the next several days, technicians extracted data from the construct, during which time it repeatedly breached the ship's firewalls. On August 21, all data extraction was completed and the remains of the monitor were powered down and ejected into space.<ref>'''Halo Mythos''', ''Pg. ???''</ref>
The ''Rubicon'' arrived at the Ark on August 10, 2554. Upon arrival, it detected a non-standard, heterogenic signal eminatig from the structure's surface. After navigating with some difficulty through the debris field surrounding the Ark, the ''Rubicon'' deployed all of its RCTs, including RCT-06. Because of the damage to both the structural and environmental systems of the installation, the surface conditions faced by the RCTs were extremely severe.{{Ref/Reuse|provenance}} Over the next several days, contact between the ''Rubicon'' and the numerous RCTs was lost, the latter having come under attack from the Installation's wildlife and constructs at the behest of the Ark's [[monitor]], [[000 Tragic Solitude]].{{Ref/Reuse|provenance}}<ref>'''[[Halo: Hunters in the Dark]]''', ''page 3''</ref> On August 18, RCT-06 managed to successfully return to the ''Rubicon'', being the only team to do so. Despite having suffered heavy casualties, RCT-06 had managed to locate and retrieve the source of the mysterious signal, a "severely damaged armature."{{Ref/Reuse|provenance}} Investigations by the ''Rubicon's'' science detachment discovered that this was in fact the barely functioning debris of [[343 Guilty Spark]], the former monitor of [[Installation 04]].<ref name="Primordium">'''[[Halo: Primordium]]'''</ref> Over the next several days, technicians extracted data from the construct, during which time it repeatedly breached the ship's firewalls. On August 21, all data extraction was completed and the broken pieces of the monitor were powered down and ejected into space.<ref>'''[[Halo Mythos]]'''</ref>


Unbeknownst to the crew, however, Guilty Spark had already transferred his consciousness into the ''Rubicon's'' computer framework. After subduing the ship's [[AI]] [[Curator]], Guilty Spark took control of the ''Rubicon'' and forced its crew, including the surviving members of RCT-06, into a deep sleep. Believing after careful consideration that the [[Librarian]] was still alive, Guilty Spark then directed the ''Rubicon'' to where he believed her to be.<ref>'''[[Halo: Primordium]]''', ''pages 376-379''</ref> The [[UNSC]], having lost all contact with the ''Rubicon'', dispatched search-and-rescue teams, but these could not discover any traces of the ship.{{Ref/Reuse|provenance}} The ''Rubicon'' was formally declared  ''lost'' on July 2, 2557 and its complement, including RCT-06, was presumed dead.<ref>'''Halo Waypoint''', ''Catalog Interaction (post 2969311)''</ref> In reality, the ''Rubicon'' crashed into [[Geranos-a]] in 2554 after its hijacking by Spark who survived by transferring himself into an [[armiger]] salvaged by the crew. The entire crew of the ''Rubicon'', including RCT-06, perished in the crash. Spark buried the crew in a mass grave near the crash site which was discovered three years later in 2557 by the ''[[Ace of Spades]]'' who had hacked a distress signal ONI had intercepted from Spark.<ref>'''[[Halo: Renegades]]'''</ref>
Unbeknownst to the crew, however, Guilty Spark had already transferred his consciousness into the ''Rubicon's'' computer framework. After subduing the [[Curator|Ship's AI]], Guilty Spark took control of the ''Rubicon'' and forced its crew, including the surviving members of RCT-06, into a deep sleep. Believing after careful consideration that the [[Librarian]] was still alive, Guilty Spark then directed the ''Rubicon'' to where he believed her to be.<ref>'''Halo: Primordium''', ''Pp. 376-379''</ref> The [[UNSC]], having lost all contact with the ''Rubicon'', dispatched search-and-rescue teams, but these could not discover any traces of the ship.<ref name="provenance"/> The UNSC ''Rubicon'' was formally declared  ''lost'' on July 2, 2557 and its complement, including RCT-06, was presumed dead.<ref>'''Halo Waypoint''', ''Catalog Interaction (post 2969311)''</ref> In reality, the ''Rubicon'' crashed into [[Geranos-a]] in 2554 after its hijacking by Spark who survived by transferring himself into an [[armiger]] salvaged by the crew. The entire crew of the ''Rubicon'', including RCT-06, perished in the crash. Spark buried the crew in a mass grave near the crash site which was discovered three years later in 2557 by the ''[[Ace of Spades]]'' who had hacked a distress signal ONI had intercepted from Spark.<ref>'''[[Halo: Renegades]]'''</ref>


==List of appearances==
*''[[Halo: Primordium]]'' {{Im}}
*''[[Halo: Hunters in the Dark]]'' {{Mo}}
==Sources==
==Sources==
{{Ref/Sources}}
<references/>


[[Category:UNSC military units]]
[[Category:UNSC military units]]
[[Category:Office of Naval Intelligence military units]]
[[Category:Office of Naval Intelligence military units]]

Please note that all contributions to Halopedia are considered to be released under the Attribution-ShareAlike 3.0 Unported license (see Halopedia:Copyrights for details). If you don't want your writing to be edited mercilessly and redistributed at will, then don't submit it here. You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)

To view or search uploaded images go to the list of images. Uploads and deletions are also logged in the upload log. For help including images on a page see Help:Images. For a sound file, use this code: [[Media:File.ogg]].

Do not copy text from other websites without permission. It will be deleted.