Changes: Long range sensor scan

Revision as of 18:26, 21 August 2013

AT: "xx"

Long range sensor scan display — On a display on the *Defiant*

A long range sensor scan or long range scan is a scan which allows a person to search a large area in space for objects such as starships.

Captain Archer ordered to use the long range sensors again after the ship went through the liquid phosphorus and detected the Suliban helix. (ENT: "Broken Bow")

In 2151, Captain Jonathan Archer ordered Lieutenant Malcolm Reed to stay on their long range scanners and let him know when the Enterprise made another contact with the unidentified aliens they had encountered earlier. (ENT: "Silent Enemy")

In 2267, the sensors of the USS Enterprise were able to scan out to one parsec (3.26 light years) and give a near instantaneous result. (TOS: "The Enterprise Incident")

In 2367. Lieutenant Commander Geordi La Forge stated that the long range sensors aboard the USS Enterprise-D were able to scan a radius of ten light years within a 24-hour period; effectively, one sector per day. (TNG: "The Wounded")

In 2368, the long range sensors aboard the USS Enterprise-D were able to detect a cubical Borg scout ship with a mass of 2.5 million metric tons, at a range that would take thirty-one hours and seven minutes to traverse at warp factor seven-point-six. (TNG: "I Borg")

In 2369, Lieutenant Commander Worf informed Commander William T. Riker that the long range sensors of the Enterprise-D picked up a distress call from a Romulan warbird. Later, La Forge was unable to find the Enterprise-D, as it was not at the rendezvous point. He told Captain Jean-Luc Picard that the long range sensors were at maximum and there was no sign of the Enterprise-D. (TNG: "Timescape")

The same year Doctor Julian Bashir and Major Kira Nerys responded to a priority one distress signal from the Kobliad transport ship Reyab and found the ship via the long range sensors. (DS9: "The Passenger")

During a rescue mission for the runabout USS Yangtzee Kiang in the Gamma Quadrant, the long range sensors of the USS Rio Grande were affected by the delta radiation of the star of a binary star system. (DS9: "Battle Lines")

The computer aboard Deep Space 9 activated the long range sensors when Commander Sisko requested data about all Cardassian traffic at the border in 2369. (DS9: "The Forsaken")

In 2370, Sam Lavelle performed a long range scan to find an escape pod near the Cardassian border, but with no success. Data suggested it was possible that at this distance, the sensors of the Enterprise-D were unable to distinguish the pod from the inorganic matter normally present in space. (TNG: "Lower Decks")

In an alternate timeline, Data, on board the USS Pasteur, performed a long range sensor scan to locate anomalies in the Devron system but found nothing. (TNG: "All Good Things...")

In 2372, Worf performed a long range sensor scan from a console on the bridge of the USS Defiant, searching for Klingon starships. (DS9: "The Way of the Warrior")

Following the destruction of the Federation colony Ivor Prime near Deep Space 5 in 2373, long range sensors detected the Borg. Admiral Hayes reported this to Captain Jean-Luc Picard. (Star Trek: First Contact)

The long range sensors of the USS Enterprise-E went offline after the ship went through the temporal vortex to the year 2063. (Star Trek: First Contact)

@@ Line 1: / Line 1: @@
+{{at|xx}}
-[[Image:Long range sensor scan display.jpg|thumb|On a display on the ''Defiant'']]
+[[File:Long range sensor scan display.jpg|thumb|On a display on the ''Defiant'']]
-A '''long range sensor scan''' or '''long range scan''' is a scan which allows the person to search a large area in space for something like starships.
+A '''long range sensor scan''' or '''long range scan''' is a scan which allows a person to search a large area in [[space]] for objects such as [[starship]]s.
-In [[2151]], [[Captain]] [[Jonathan Archer]] ordered [[Lieutenant]] [[Malcolm Reed|Reed]] to stay on their long range scanners and let him know when the [[Enterprise (NX-01)|''Enterprise'']] made another contact with the [[Unnamed non-humanoids (22nd century)|unidentified aliens]]. ({{ENT|Silent Enemy}})
+Captain Archer ordered to use the long range sensors again after the ship went through the [[liquid]] [[phosphorus]] and detected the [[Suliban helix]]. ({{ENT|Broken Bow}})
+In [[2151]], [[Captain]] [[Jonathan Archer]] ordered [[Lieutenant]] [[Malcolm Reed]] to stay on their long range scanners and let him know when the [[Enterprise (NX-01)|''Enterprise'']] made another contact with the [[Unnamed non-humanoids (22nd century)|unidentified aliens]] they had encountered earlier. ({{ENT|Silent Enemy}})
-In [[2267]], the sensors of the {{USS|Enterprise|NCC-1701}} were able to scan out to one [[parsec]] (3.26 light years)and give a near instantaneous result. ({{TOS|The Enterprise Incident}})
-In [[2367]]. [[Lieutenant Commander]] [[Geordi LaForge]] stated that the long range sensors aboard the ''Enterprise-D'' were able to scan a radius of ten light-years within a 24-hour period; effectively, one sector per day. ({{TNG|The Wounded}})
+In [[2267]], the sensors of the {{USS|Enterprise|NCC-1701}} were able to scan out to one [[parsec]] (3.26 light years) and give a near instantaneous result. ({{TOS|The Enterprise Incident}})
-In [[2369]], [[Lieutenant Commander]] [[Worf]] informed [[Commander]] [[William T. Riker]] that the long range sensors of the {{USS|Enterprise|NCC-1701-D|-D}} picked up a [[distress call]] from a [[Romulan]] [[warbird]]. Later, [[Geordi La Forge]] was unable to find the ''Enterprise''-D, which was not at the rendezvous point. He told [[Captain]] [[Jean-Luc Picard|Picard]] that the long range sensors were at maximum and there was no sign of the ''Enterprise''-D. ({{TNG|Timescape}})
+In [[2367]]. [[Lieutenant Commander]] [[Geordi La Forge]] stated that the long range sensors aboard the {{USS|Enterprise|NCC-1701-D|-D}} were able to scan a radius of ten [[light year]]s within a 24-hour period; effectively, one [[sector]] per day. ({{TNG|The Wounded}})
+In [[2368]], the long range sensors aboard the {{USS|Enterprise|NCC-1701-D|-D}} were able to detect a cubical [[Borg scout ship]] with a mass of 2.5 million metric tons, at a range that would take thirty-one hours and seven minutes to traverse at [[warp factor]] seven-point-six. ({{TNG|I Borg}})
-In [[2370]], [[Sam Lavelle]] performed a long range scan to find the [[escape pod]] near the [[Cardassian border]], but without any result. [[Data]] suggested it was possible that at this distance, the [[sensor]]s of the {{USS|Enterprise|NCC-1701-D|-D}} were unable to distinguish the pod from the [[inorganic]] [[matter]] normally present in space. ({{TNG|Lower Decks}})
+In [[2369]], Lieutenant Commander [[Worf]] informed [[Commander]] [[William T. Riker]] that the long range sensors of the ''Enterprise''-D picked up a [[distress call]] from a [[Romulan]] [[warbird]]. Later, La Forge was unable to find the ''Enterprise''-D, as it was not at the rendezvous point. He told [[Captain]] [[Jean-Luc Picard]] that the long range sensors were at maximum and there was no sign of the ''Enterprise''-D. ({{TNG|Timescape}})
-''In an [[alternate timeline]], [[Data]], on board the {{USS|Pasteur}}, performed a long range sensor scan to locate anomalies in the [[Devron system]] but found nothing.'' ({{TNG|All Good Things...}})
+The same year [[Doctor]] [[Julian Bashir]] and [[Major]] [[Kira Nerys]] responded to a [[priority one]] [[distress signal]] from the [[Kobliad transport ship]] ''[[Reyab]]'' and found the ship via the long range sensors. ({{DS9|The Passenger}})
-In [[2372]], Worf performed a long range sensor scan from a console on the bridge of the {{USS|Defiant|NX-74205}}, searching for [[Klingon]] [[starship]]s. ({{DS9|The Way of the Warrior}})
+During a rescue mission for the [[runabout]] {{USS|Yangtzee Kiang}} in the [[Gamma Quadrant]], the long range sensors of the {{USS|Rio Grande}} were affected by the [[delta radiation]] of the [[star]] of a [[binary star system]]. ({{DS9|Battle Lines}})
+The computer aboard [[Deep Space 9]] activated the long range sensors when [[Commander]] [[Benjamin Sisko|Sisko]] requested data about all [[Cardassian]] traffic at the border in 2369. ({{DS9|The Forsaken}})
+In [[2370]], [[Sam Lavelle]] performed a long range scan to find an [[escape pod]] near the [[Cardassian border]], but with no success. [[Data]] suggested it was possible that at this distance, the [[sensor]]s of the ''Enterprise''-D were unable to distinguish the pod from the [[inorganic]] [[matter]] normally present in space. ({{TNG|Lower Decks}})
+''In an [[alternate timeline]], Data, on board the {{USS|Pasteur}}, performed a long range sensor scan to locate anomalies in the [[Devron system]] but found nothing.'' ({{TNG|All Good Things...}})
+In [[2372]], Worf performed a long range sensor scan from a console on the bridge of the {{USS|Defiant|2370}}, searching for [[Klingon]] starships. ({{DS9|The Way of the Warrior}})
+Following the destruction of the [[Federation]] [[colony]] [[Ivor Prime]] near [[Deep Space 5]] in [[2373]], long range sensors detected the [[Borg]]. [[Admiral]] [[Hayes (Male Admiral)|Hayes]] reported this to [[Captain]] [[Jean-Luc Picard]]. ({{film|8}})
+The long range sensors of the {{USS|Enterprise|NCC-1701-E|-E}} went offline after the ship went through the [[temporal vortex]] to the [[year]] [[2063]]. ({{film|8}})
-[[Category:Scans]]
 [[de:Langstreckensensor]]
+[[Category:Scans]]