Editing Remote contact team
From Halopedia, the Halo wiki
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 3: | Line 3: | ||
==History== | ==History== | ||
Shortly after [[2553#December|December of 2553]], numerous remote contact teams were deployed by {{UNSCShip|Rubicon}} to the surface of the damaged [[Installation 00]].<ref>''Halo: Hunters in the Dark'', p. 43 (Google Play edition)</ref> The RCTs were forced to endure extremely hostile conditions, as the installation's life support systems were severely damaged. The teams were ordered to avoid all fauna they encountered on the Ark. The teams managed to conduct several initial surveys on Installation 00's surface, but contact with most RCTs was lost after eight days.<ref name="provenance">''[[Eleventh Hour reports]]'', Report 4</ref> One team, [[Broadside]], was attacked by [[chaefka]] on the Ark; only the [[Bobby Kodiak|team leader]] survived, though he was captured by [[monitor]] [[000 Tragic Solitude]]. | Shortly after [[2553#December|December of 2553]], numerous remote contact teams were deployed by {{UNSCShip|Rubicon}} to the surface of the damaged [[Installation 00]].<ref>''Halo: Hunters in the Dark'', p. 43 (Google Play edition)</ref> The RCTs were forced to endure extremely hostile conditions, as the installation's life support systems were severely damaged. The teams were ordered to avoid all fauna they encountered on the Ark. The teams managed to conduct several initial surveys on Installation 00's surface, but contact with most RCTs was lost after eight days.<ref name="provenance">''[[Eleventh Hour reports]]'', Report 4</ref> One team, [[Broadside]], was attacked by [[chaefka]] on the Ark; only the [[Bobby Kodiak|team leader]] survived, though he was captured by [[monitor]] [[000 Tragic Solitude]].<ref name="hitd6"/> Only [[RCT-06]]—after suffering heavy causalities—returned to ''Rubicon'',<ref name="provenance"/> with the remains of [[343 Guilty Spark]]. The monitor soon took control of ''Rubicon'' and left the area with the ship.<ref>''[[Halo: Primordium]]'', p. 376-379</ref> | ||
In [[2557]], after the [[Office of Naval Intelligence]] lost contact with its research teams on [[Erebus VII]], several remote contact teams were sent to determine the cause of contact loss; the teams were unable to determine the location of the researchers.<ref>[https://www.halowaypoint.com/en-us/universe/locations/erebus-vii '''Halo Waypoint''': ''Erebus VII'']</ref> A RCT was also deployed to an [[asteroid]] belt in an unidentified system, where the team deemed the site to be too dangerous for study.<ref>''[[Halo 2: Anniversary]]'', "[[Nebula]]" map description</ref> [[Extra-vehicular activity]]-ready remote contact teams were deployed by ONI to a violent meteor collision site where a non-native fragment of an impacting agent of unknown origin was discovered.<ref>''[[Halo 4: The Essential Visual Guide]]'', p. 216</ref> | In [[2557]], after the [[Office of Naval Intelligence]] lost contact with its research teams on [[Erebus VII]], several remote contact teams were sent to determine the cause of contact loss; the teams were unable to determine the location of the researchers.<ref>[https://www.halowaypoint.com/en-us/universe/locations/erebus-vii '''Halo Waypoint''': ''Erebus VII'']</ref> A RCT was also deployed to an [[asteroid]] belt in an unidentified system, where the team deemed the site to be too dangerous for study.<ref>''[[Halo 2: Anniversary]]'', "[[Nebula]]" map description</ref> [[Extra-vehicular activity]]-ready remote contact teams were deployed by ONI to a violent meteor collision site where a non-native fragment of an impacting agent of unknown origin was discovered.<ref>''[[Halo 4: The Essential Visual Guide]]'', p. 216</ref> | ||
