m (Protected "Auto-destruct": Counter-productive edit warring: Post the issues on the talk page and try to stay with the MA style ([edit=autoconfirmed] (expires 23:43, February 4, 2014 (UTC)) [move=autoconfirmed] (expires 23:43, February 4, 2014 (U) |
Brian Gordon (talk | contribs) No edit summary Tags: VE Mobile edit Mobile web edit |
||
(61 intermediate revisions by 28 users not shown) | |||
Line 1: | Line 1: | ||
⚫ | |||
− | {{Pna-inaccurate}} |
||
⚫ | |||
⚫ | |||
⚫ | |||
+ | On [[Starfleet]] vessels, the activation sequence varied from class to class but usually required authorization with the use of [[command authorization code]]s. Once the countdown was activated, the [[LCARS|ship's computer]] could give audio warnings and/or displayed countdown warning graphics on [[viewscreen]]s and terminals, though this featured could be disabled when initiating the sequence. ({{DIS|Such Sweet Sorrow}}; {{TNG|11001001|Where Silence Has Lease}}; {{DS9|The Adversary}}; {{VOY|Dreadnought|Deadlock}}; {{film|8}}) In the [[23rd century]], self-destruct was also known as [[Starfleet Order 2005]]. ({{film|1}}) |
||
− | The auto-destruct system aboard {{Class|Intrepid}} starships could not be activated if the [[secondary command processor]]s were damaged. ({{VOY|Basics, Part I}}) |
||
− | |||
− | The auto-destruct system aboard {{Class|Sovereign}} starships could be activated even if the [[computer|main computer]] was locked out and encrypted. ({{film|8}}) |
||
− | |||
− | On [[Starfleet]] vessels, the activation sequence varied from class to class, but usually required authorization from the [[captain]] and/or [[senior officer]]s, with the use of [[command authorization code]]s in most cases. Once the countdown was activated, the computer gave audio warnings, usually with an interval of ten seconds until the last ten seconds that were counted down in intervals of a second, and displayed graphics on [[viewscreen]]s. There was also an option for a silent countdown, which gave no further audio warnings once the auto-destruct sequence was engaged, preventing boarders from learning the ship was about to explode. ({{film|8}}; {{VOY|Deadlock}}) |
||
== Known sequences == |
== Known sequences == |
||
− | === ''Constitution''-class === |
+ | === ''Constitution''- and ''Constitution II''-class === |
− | [[File:Destruct sequence engaged.jpg|thumb|Destruct sequence engaged]] |
+ | [[File:Destruct sequence engaged.jpg|thumb|Destruct sequence engaged (2268)]] |
− | On {{ |
+ | On {{class|Constitution}} and {{class|Constitution II}} starships, the [[captain]] or [[admiral]] (including [[rear admiral]]) and two [[senior officer]]s ([[Chief engineering officer|chief engineering]] and [[science officer]]s/acting science officer) were required to initiate the destruct sequence, using the following, concurrent codes: |
Each officer would state their name, rank and corresponding code: |
Each officer would state their name, rank and corresponding code: |
||
− | |||
# "''Destruct sequence 1, code 1-1 A.''" |
# "''Destruct sequence 1, code 1-1 A.''" |
||
# "''Destruct sequence 2, code 1-1 A-2B.''" |
# "''Destruct sequence 2, code 1-1 A-2B.''" |
||
Line 21: | Line 15: | ||
The computer would then reply: |
The computer would then reply: |
||
+ | [[File:Constitution II class destruct sequence countdown.jpg|thumb|right|The countdown begins (2285)]] |
||
− | |||
− | :"''Destruct sequence completed and engaged. Awaiting final code for |
+ | :"''Destruct sequence completed and engaged. Awaiting final code for (time interval) countdown.''" |
− | {{bginfo|In {{TOS|Let That Be Your Last Battlefield}}, the countdown was only thirty seconds.}} |
||
The commanding officer would then state: |
The commanding officer would then state: |
||
Line 29: | Line 22: | ||
:"''Code zero zero zero. Destruct. Zero.''" |
:"''Code zero zero zero. Destruct. Zero.''" |
||
+ | The computer would than activate [[red alert]] and respond: |
||
⚫ | |||
+ | :"''Destruct sequence is activated.''" |
||
⚫ | |||
− | * {{audio|file=Destructconstitution.ogg|text=Listen to the USS ''Enterprise''{{'}}s destruct sequence activated in 2285}} |
||
− | {{bginfo|In ''[[Mr. Scott's Guide to the Enterprise]]'', it was stated that if the code "0-0-0-Destruct-1" |
+ | {{bginfo|{{audio|file=USS Enterprise destruct sequence.ogg|text=Listen to the USS ''Enterprise''{{'}}s destruct sequence activated in 2285.}}|In ''[[Mr. Scott's Guide to the Enterprise]]'', it was stated that if the code "0-0-0-Destruct-1" was given, it would result in an overload of the [[warp core]] (most likely an intentional [[warp core breach]], although that term was not used until {{s|TNG}}). This version of the auto-destruct was meant for use in deep space, nowhere near a planetary environment. Using the code "0-0-0-Destruct-0" (as it was in TOS and Star Trek III), would render the ship as a useless hulk to all hostile forces.}} |
+ | |||
+ | === ''Crossfield''-class === |
||
+ | It was possible to set a remote auto-destruct for a {{class|Crossfield}} starship, allowing the crew to evacuate to another vessel. In [[2257]], [[Christopher Pike]] and [[Saru]] attempted this method with the {{USS|Discovery}}, both of them providing [[handprint]] authorization. The crew was then evacuated to the {{USS|Enterprise|NCC-1701}}, but the attempt failed due to the {{dis|Sphere|lifeform}} data merging with the vessel's systems and protecting itself. ({{DIS|Such Sweet Sorrow}}) |
||
=== ''Galaxy''-class === |
=== ''Galaxy''-class === |
||
⚫ | |||
− | On {{Class|Galaxy}} starships, the [[commanding officer|commanding]] and [[executive officer]]s activated the destruct sequence from [[main engineering]]. Both would provide palm print identification, and order the auto-destruct with both officers having to agree. This could be aborted from the [[bridge]] by voice recognition and palm print identification of both of the same officers. |
||
+ | Originally, the auto-destruct sequence aboard {{class|Galaxy}} starships required the authorization and palm-print identification of both the [[commanding officer|commanding]] and [[executive officer]]s from [[main engineering]]. The sequence could be aborted from the [[bridge]] by voice recognition and palm print identification by the same officers. The time interval could not be adjusted and was preset for a five minute countdown. ({{TNG|11001001}}) |
||
− | {{bginfo|Note: The time allowed for the destruct sequence varies. In {{TNG|11001001}}, the ship's computer only allows for a five minute countdown to auto-destruct and needed palm print identification from the Engineering station on the [[main bridge]] to abort; however, in {{e|Where Silence Has Lease}}, the computer asks to be given a time interval and accepts a value of twenty minutes from Picard and Riker without the need of the palm print upon its deactivation. This could be a result of the ''Enterprise''{{'}}s computer systems undergoing an upgrade in the former episode.}} |
||
+ | |||
− | In ''{{e|Let That Be Your Last Battlefield}}'', Kirk stated that the destruct order could not be countermanded once the countdown reached T minus 5. This restriction did not apply to the Enterprise-D, however, where the destruct order was aborted with one second to spare. |
||
+ | By [[2365]], the time interval could be pre-selected and the countdown aborted without the need of palm-print identification. The activation of the auto-destruct sequence also triggered a [[red alert]]. ({{TNG|Where Silence Has Lease}}) |
||
+ | |||
+ | Upon providing palm-print identification, the captain would order the computer to initiate the auto-destruct. The computer would ask if the first officer concurred. Providing the first officer agrees, the computer would verbally confirm the order and begin the countdown with the appropriate time delay. Should the order be desired to be cancelled, the captain would order the computer to abort the sequence. The computer would question the first officer's agreement before cancelling the sequence. ({{TNG|11001001|Where Silence Has Lease}}) |
||
<gallery> |
<gallery> |
||
⚫ | |||
⚫ | |||
− | Auto-destruct countdown, |
+ | File:Auto-destruct countdown, 2365.jpg|The countdown timer in 2365 |
⚫ | |||
</gallery> |
</gallery> |
||
=== ''Defiant''-class === |
=== ''Defiant''-class === |
||
− | [[File:Kira authorizes self-destruct.jpg|thumb|Activating the |
+ | [[File:Kira authorizes self-destruct.jpg|thumb|Activating the USS ''Defiant''{{'}}s auto-destruct sequence]] |
− | The {{ |
+ | The {{class|Defiant}} sequence was activated from the bridge, requiring the captain and first officer's consent and palm-print identification to activate. The time delay was left to the captain's discretion. Upon activation of the destruct sequence, a red alert would be triggered and all bridge computer terminals would display the remaining time left in the countdown. Cancelling the sequence would require the captain and first officer's orders without the need of palm-print identification or computer clarification. ({{DS9|The Adversary}}) |
{{clear}} |
{{clear}} |
||
− | === |
+ | ===''Intrepid''-class === |
− | Aboard the {{ |
+ | Aboard the {{class|Intrepid}}, auto-destruct required the captain's sole authorization. In addition to selecting the desired time interval, the captain also had the option of ordering a silent countdown – a single voice prompt would occur at the commencement of the sequence, with no further audio warnings made. ({{VOY|Deadlock|Dreadnought}}) |
+ | |||
− | :"''Janeway to computer: initiate the self-destruct sequence. Authorization: Janeway Pi 1-1-0. Set at (desired time interval followed by option {e.g. "mute voice warnings"}), enable.''" |
||
− | The computer would reply the following: |
||
− | "''Warning: Self-Destruct Sequence has been initiated; Warp Core overload in (given time interval and, if commanded to mute voice warnings, {"there will be no further audio warnings."}). |
||
{{bginfo|In the ''[[String Theory]]'' trilogy, auto-destruct could also be activated by the [[first officer|first]] and [[second officer]]s. Meanwhile, in the video games ''[[Star Trek: Voyager - Elite Force|Elite Force]]'' and ''[[Star Trek: Captain's Chair|Captain's Chair]]'', the user could activate the self destruct from the captain's personal console on the bridge.}} |
{{bginfo|In the ''[[String Theory]]'' trilogy, auto-destruct could also be activated by the [[first officer|first]] and [[second officer]]s. Meanwhile, in the video games ''[[Star Trek: Voyager - Elite Force|Elite Force]]'' and ''[[Star Trek: Captain's Chair|Captain's Chair]]'', the user could activate the self destruct from the captain's personal console on the bridge.}} |
||
+ | |||
If the starship's [[secondary command processor]]s were offline, the auto-destruct sequence could not be completed. ({{VOY|Basics, Part I}}) |
If the starship's [[secondary command processor]]s were offline, the auto-destruct sequence could not be completed. ({{VOY|Basics, Part I}}) |
||
− | === '' |
+ | === ''Sagan''-class === |
+ | The {{class|Sagan}} had an abbreviated, ten-second sequence activated with the old code "zero-zero-zero-destruct-zero".({{PIC|The Star Gazer}}) |
||
⚫ | The {{ |
||
+ | {{Bginfo|Admiral Picard was able to activate this sequence alone, without even Captain Rios's concurrence. This may be an emergency sequence available only to flag officers, as no formal transfer or addition of command codes was shown, and the other characters specifically called on him to do it.}} |
||
+ | === ''Sovereign''-class === |
||
⚫ | |||
⚫ | The {{class|Sovereign}} required the authorization of the captain and two senior officers. Each would state their name and rank, confirming the sequence, and giving their authorization code. The captain would then select the destruct sequence type, sequence delay, and whether a silent countdown would be initiated. |
||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
:(The computer would ask for the final code to start the sequence.) |
:(The computer would ask for the final code to start the sequence.) |
||
⚫ | |||
+ | {{bginfo|Worf was able to use his authorization code to help activate the auto-destruct despite not being a serving member of the ''Enterprise'' crew, implying that any command level officer would suffice or the computer took battle reassignment into consideration.}} |
||
⚫ | |||
− | The auto-destruct |
+ | The auto-destruct need not be deactivated by the ship's captain, as [[Lieutenant Commander]] [[Data]] was able to deactivate the auto-destruct sequence by himself, however, this could be the result of Data hacking into main computer past normal operating parameters. |
⚫ | |||
⚫ | |||
− | The ship's captain was able to activate the "Omega" option for the auto-destruct on his own authorization without the need of any other officers. The captain would order the computer to stand-by to initiate the Omega-destruct option with the use of an authorization code. In the case of the ''Enterprise''-E, the order would proceed as: |
||
+ | |||
+ | An "Omega" option for the auto-destruct was also available and only needed the captain's authorization to initiate. |
||
:"''Computer, stand-by auto-destruct sequence Omega. Recognize voice pattern Jean-Luc Picard, authorization Alpha-Alpha 3-0-5.''" |
:"''Computer, stand-by auto-destruct sequence Omega. Recognize voice pattern Jean-Luc Picard, authorization Alpha-Alpha 3-0-5.''" |
||
⚫ | |||
− | {{bginfo|Considering the close proximity the ''Enterprise'' had to the ''[[Scimitar]]'' at the time the order was given, it is likely that the "Omega" option would result in the instant destruction of the vessel with enough force to destroy any nearby objects with it.}} |
||
− | |||
⚫ | |||
== Methods == |
== Methods == |
||
⚫ | |||
− | [[File:Self destruction.jpg|thumb|[[James T. Kirk]] and his crew witnessed the self-destruction of an [[Orion scout ship]]]] |
||
− | On most Federation ships, the destruct sequence used one of two methods of completion (both could be installed to allow for redundancy). |
||
+ | The {{class|Nimitz}} {{USS|Europa|NCC-1648}} self-destructed by voluntarily creating a breach in the [[antimatter containment field]]. ({{DIS|Battle at the Binary Stars}}) |
||
− | The first used the ship's [[matter]] and [[antimatter]] fuel supplies, combining them in an unmoderated reaction with the resultant annihilation reaction being more than enough to obliterate the entire vessel, much like a [[warp core breach]]. (''[[Star Trek: The Next Generation Technical Manual]]'') |
||
− | {{bginfo|This was apparently the primary method used on ''Intrepid''-class vessels, as when it was activated, the computer made a point of announcing that a warp core overload was in progress.}} |
||
+ | Some 23rd century Klingon ships had scuttle systems that would trigger the self-destruct upon the slightest interaction with any onboard control, in circumstances where the crew was unavailable to trigger it directly. ({{SNW|Lift Us Where Suffering Cannot Reach}}) |
||
⚫ | |||
⚫ | Twenty-third century [[Romulan]] [[Romulan Bird-of-Prey|vessels]] used "old style" [[atomic]] weapons in their self-destruct system which were not integrated into the ship itself. These weapons could be removed and jettisoned into space as [[mine]]s. ({{TOS|Balance of Terror}}) [[Romulan scout ship]]s were equipped with an [[Auto-destruct sequencer]]. ({{TNG|The Defector}}) |
||
− | In the second, explosive charges placed at key points throughout the vessel would ensure complete destruction. It was approximately half as powerful as the former method (an estimated yield of one thousand and five hundred [[photon torpedo]]es, respectively). (''[[Star Trek: The Next Generation Technical Manual]]'') |
||
+ | During the [[Galen border conflict]], [[Talarian]] [[Talarian observation craft|observation craft]] equipped with self-destruct devices and [[subspace proximity detonator]]s were responsible for 219 casualties over a three day period. ({{TNG|Suddenly Human}}) |
||
− | Sometimes a self-destruct sequence would result in a chain reaction of explosions, as in the case of ''Constitution''-class starships, while in others it resulted in one massive explosion, as in the case of the [[Orion scout ship]] encountered by [[James T. Kirk]] and his crew. ({{film|3}}; {{TOS|Journey to Babel}}) |
||
⚫ | A [[Borg cube|Borg vessel]]'s self-destruct mechanism forced the ship's power grid to feed back on itself, forcing an explosion that destroyed the ship. Lieutenant Commander Data was able to trigger such a destruction while being linked to the collective consciousness of the Borg ship that threatened Earth in [[2367]]. The [[Borg Queen]] ordered the self destruction of several Borg ships that carried drones linked to [[Unimatrix Zero]] as well as a [[Borg tactical cube]] that had Captain [[Kathryn Janeway]], Lieutenant Commander [[Tuvok]], and Lieutenant [[B'Elanna Torres]] aboard. ({{TNG|The Best of Both Worlds, Part II}}; {{VOY|Unimatrix Zero, Part II}}) |
||
⚫ | |||
⚫ | |||
⚫ | A [[Borg cube|Borg vessel]]'s self-destruct mechanism forced the ship's power grid to feed back on itself, forcing an explosion that destroyed the ship. |
||
+ | == Appendices == |
||
⚫ | |||
⚫ | |||
+ | * [[Computer log]] |
||
⚫ | |||
− | === |
+ | === External link === |
− | * |
+ | * {{mbeta|Self destruct}} |
− | == Evidence == |
||
− | * '''See''': [[computer log]] |
||
− | |||
⚫ | |||
⚫ | |||
[[de:Selbstzerstörung]] |
[[de:Selbstzerstörung]] |
||
− | [[Category: |
+ | [[Category:Maneuvers]] |
+ | [[Category:Spacecraft components]] |
Latest revision as of 01:09, 17 September 2023
The auto-destruct system (also known as self-destruct or destruct sequence) was a starship system that allowed the total destruction of the vessel. This was typically activated as a last resort, usually to prevent a ship from falling into enemy hands.
On Starfleet vessels, the activation sequence varied from class to class but usually required authorization with the use of command authorization codes. Once the countdown was activated, the ship's computer could give audio warnings and/or displayed countdown warning graphics on viewscreens and terminals, though this featured could be disabled when initiating the sequence. (DIS: "Such Sweet Sorrow"; TNG: "11001001", "Where Silence Has Lease"; DS9: "The Adversary"; VOY: "Dreadnought", "Deadlock"; Star Trek: First Contact) In the 23rd century, self-destruct was also known as Starfleet Order 2005. (Star Trek: The Motion Picture)
Known sequences
Constitution- and Constitution II-class
On Constitution-class and Constitution II-class starships, the captain or admiral (including rear admiral) and two senior officers (chief engineering and science officers/acting science officer) were required to initiate the destruct sequence, using the following, concurrent codes:
Each officer would state their name, rank and corresponding code:
- "Destruct sequence 1, code 1-1 A."
- "Destruct sequence 2, code 1-1 A-2B."
- "Destruct sequence 3, code 1 B-2B-3."
The computer would then reply:
- "Destruct sequence completed and engaged. Awaiting final code for (time interval) countdown."
The commanding officer would then state:
- "Code zero zero zero. Destruct. Zero."
The computer would than activate red alert and respond:
- "Destruct sequence is activated."
The sequence could be aborted at any time until T-minus five seconds by the captain or highest-ranking officer, with the command "Code 1-2-3-continuity, abort destruct order." Beyond that, the destruct order could not be cancelled. (TOS: "Let That Be Your Last Battlefield"; Star Trek III: The Search for Spock)
Crossfield-class
It was possible to set a remote auto-destruct for a Crossfield-class starship, allowing the crew to evacuate to another vessel. In 2257, Christopher Pike and Saru attempted this method with the USS Discovery, both of them providing handprint authorization. The crew was then evacuated to the USS Enterprise, but the attempt failed due to the Sphere data merging with the vessel's systems and protecting itself. (DIS: "Such Sweet Sorrow")
Galaxy-class
Originally, the auto-destruct sequence aboard Galaxy-class starships required the authorization and palm-print identification of both the commanding and executive officers from main engineering. The sequence could be aborted from the bridge by voice recognition and palm print identification by the same officers. The time interval could not be adjusted and was preset for a five minute countdown. (TNG: "11001001")
By 2365, the time interval could be pre-selected and the countdown aborted without the need of palm-print identification. The activation of the auto-destruct sequence also triggered a red alert. (TNG: "Where Silence Has Lease")
Upon providing palm-print identification, the captain would order the computer to initiate the auto-destruct. The computer would ask if the first officer concurred. Providing the first officer agrees, the computer would verbally confirm the order and begin the countdown with the appropriate time delay. Should the order be desired to be cancelled, the captain would order the computer to abort the sequence. The computer would question the first officer's agreement before cancelling the sequence. (TNG: "11001001", "Where Silence Has Lease")
Defiant-class
The Defiant-class sequence was activated from the bridge, requiring the captain and first officer's consent and palm-print identification to activate. The time delay was left to the captain's discretion. Upon activation of the destruct sequence, a red alert would be triggered and all bridge computer terminals would display the remaining time left in the countdown. Cancelling the sequence would require the captain and first officer's orders without the need of palm-print identification or computer clarification. (DS9: "The Adversary")
Intrepid-class
Aboard the Intrepid-class, auto-destruct required the captain's sole authorization. In addition to selecting the desired time interval, the captain also had the option of ordering a silent countdown – a single voice prompt would occur at the commencement of the sequence, with no further audio warnings made. (VOY: "Deadlock", "Dreadnought")
If the starship's secondary command processors were offline, the auto-destruct sequence could not be completed. (VOY: "Basics, Part I")
Sagan-class
The Sagan-class had an abbreviated, ten-second sequence activated with the old code "zero-zero-zero-destruct-zero".(PIC: "The Star Gazer")
Sovereign-class
The Sovereign-class required the authorization of the captain and two senior officers. Each would state their name and rank, confirming the sequence, and giving their authorization code. The captain would then select the destruct sequence type, sequence delay, and whether a silent countdown would be initiated.
- "Computer, begin auto-destruct sequence, authorization Picard 4-7 Alpha Tango."
- "Computer, Commander Beverly Crusher. Confirm auto-destruct sequence, authorization Crusher 2-2 Beta Charlie."
- "Computer, Lieutenant Commander Worf. Confirm auto-destruct sequence, authorization Worf 3-7 Gamma Echo."
- (The computer would ask for the final code to start the sequence.)
- "This is Captain Jean-Luc Picard. Destruct sequence Alpha-One. Fifteen minutes, silent countdown. Enable."
The auto-destruct need not be deactivated by the ship's captain, as Lieutenant Commander Data was able to deactivate the auto-destruct sequence by himself, however, this could be the result of Data hacking into main computer past normal operating parameters.
An "Omega" option for the auto-destruct was also available and only needed the captain's authorization to initiate.
- "Computer, stand-by auto-destruct sequence Omega. Recognize voice pattern Jean-Luc Picard, authorization Alpha-Alpha 3-0-5."
If the ship was significantly damaged, the auto-destruct system could be rendered inoperable. (VOY: "Basics, Part I"; Star Trek Nemesis)
Methods
Klingon vessels, like the D7-class, could evoke their own self-destruction by causing a containment failure within the warp core. (VOY: "Prophecy")
The Nimitz-class USS Europa self-destructed by voluntarily creating a breach in the antimatter containment field. (DIS: "Battle at the Binary Stars")
Some 23rd century Klingon ships had scuttle systems that would trigger the self-destruct upon the slightest interaction with any onboard control, in circumstances where the crew was unavailable to trigger it directly. (SNW: "Lift Us Where Suffering Cannot Reach")
Twenty-third century Romulan vessels used "old style" atomic weapons in their self-destruct system which were not integrated into the ship itself. These weapons could be removed and jettisoned into space as mines. (TOS: "Balance of Terror") Romulan scout ships were equipped with an Auto-destruct sequencer. (TNG: "The Defector")
During the Galen border conflict, Talarian observation craft equipped with self-destruct devices and subspace proximity detonators were responsible for 219 casualties over a three day period. (TNG: "Suddenly Human")
A Borg vessel's self-destruct mechanism forced the ship's power grid to feed back on itself, forcing an explosion that destroyed the ship. Lieutenant Commander Data was able to trigger such a destruction while being linked to the collective consciousness of the Borg ship that threatened Earth in 2367. The Borg Queen ordered the self destruction of several Borg ships that carried drones linked to Unimatrix Zero as well as a Borg tactical cube that had Captain Kathryn Janeway, Lieutenant Commander Tuvok, and Lieutenant B'Elanna Torres aboard. (TNG: "The Best of Both Worlds, Part II"; VOY: "Unimatrix Zero, Part II")
When a Borg vessel was critically damaged, all of its vital technology, such as the transwarp coils, self-destructed to prevent their use by other species. This process is autonomous and independent from the ship's self destruction. (VOY: "Dark Frontier")
Appendices
See also
External link
- Self destruct at Memory Beta, the wiki for licensed Star Trek works