The Constitution class Enterprise self destructs.
The auto-destruct system (also known as self-destruct or destruct sequence) is a starship system that allows the total destruction of the vessel. This is typically activated as a last resort, usually to prevent a ship from falling into enemy hands.
On Starfleet vessels, the activation sequence varies from class to class, but usually requires authorization from the Captain and/or senior officers, with the use of command authorization codes in most cases. Once the countdown is activated, the computer gives audio warnings, usually with an interval of 10 seconds until the last 10 seconds in which case in counts down in intervals of a second, and displays graphics on viewscreens.
Known sequences
Kirk, Scotty and Chekov activate auto-destruct
Constitution class
On Constitution-class starships, three officers were required to initiate the destruct sequence, using the following, concurrent codes. Each would state name and rank, then the code:
- "Destruct Sequence One, Code 11A"
- "Destruct Sequence Two, Code 11A2B"
- "Destruct Sequence Three, Code 1B2B3"
The computer would then ask for the final code to commence countdown, given by the highest-ranking officer (usually the captain): "0-0-0-Destruct-0"
The default setting was for a one-minute countdown, but this could be altered during the sequence initiation. The sequence could be aborted at any time up until T-5 seconds by the captain or highest-ranking officer, with the code "Abort destruct sequence, code 1-2-3-Continuity". (Star Trek III: The Search for Spock, TOS: "Let That Be Your Last Battlefield")
Galaxy class
On Galaxy-class starships, the Commanding and Executive Officers activate the destruct sequence from Main Engineering. Both would provide palmprint identification, and order the self destruct with both officers having to agree. This can be aborted from the Bridge, by voice recognition of both of the same officers.
- Note: The time alloted for the destruct sequence varies. In 11001001, the ships computer only allows for a five minute countdown to auto-destruct; however, in Where Silence Has Lease, the computer asks to be given a time interval. This could be a result of the Enterprise's computer systems undergoing an upgrade in the former episode.
(TNG: "11001001" and "Where Silence Has Lease")
Defiant class
The Defiant class sequence was activated from the Bridge, requiring two officers' consent, and handprint verification to activate and abort. (DS9: "The Adversary")
Intrepid class
Aboard the Intrepid class, auto-destruct required the captain's sole authorization. This class 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")
Sovereign class
The Sovereign class returned to the 'three-officer' authorization method. Each would state name and rank, confirming the sequence, and giving their authorization code. The senior officer would then select the destruct sequence type, sequence delay, and whether a silent countdown would be initiated. The sequence would begin upon use of the command "Enable". (Star Trek: First Contact)
- The self-destruct was authorized in Star Trek: Nemesis, but failed because the computer was offline. It appeared to have been changed, as Picard authorized the sequence by himself.
Methods
On most Federation ships, the destruct sequence used one of two methods of completion (both may be installed to allow for redundancy).
The first uses 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.
In the second, explosive charges placed at key points throughout the vessel to ensure complete destruction. It is approximately half as powerful as the former method (an estimated yield of 1,000 and 500 photon torpedoes, respectively).
Evidence
Computer Logs
A computer log is a form of data. In the late- 23rd century, Federation starships were equipped with a "black box" that stored computer logs. The logs could be used in criminal investigations or to determine the cause of a lost ship. Computer logs were for official purposes only and were available to authorities only under specific legal circumstances or court-order. (TOS: "Court Martial", "Star Trek IV: The Voyage Home")
also refers to:
- Captain and other officer's logs
- personal logs
- sensor logs
- tactical data
- exterior sensor data of a starship set on auto-destruct (Presumably the footage seen of the USS Enterprise NCC-1701 "Star Trek IV: The Voyage Home")
Log Buoy
A log buoy is a device, similar to a recorder-marker or data recorder which was used during the 23rd century.
These devices were typically launched upon the destruction of a starship to allow searchers to discover the final events leading up to ship's demise. (Star Trek II: The Wrath of Khan)
Recorder-marker from the SS Valiant
Record-marker
A recorder-marker is a device carried by starships, similar to a log buoy. In the event of imminent destruction or capture, a recorder marker is designed to relay all the vessel's data back to its command base. The marker is built to withstand the complete destruction of a starship, with the slight possibility of external forces causing damage to the data held within.
The SS Valiant carried a recorder marker on its mission in 2065. When the vessel was destroyed crossing the galactic barrier, the recorder marker was ejected, and remained adrift for 200 years, when it was picked up by the USS Enterprise. Despite the damage done to it by 200 years exposure to space, most of the data was still retrievable. (TOS: "Where No Man Has Gone Before")
Federation starships also carried recorder markers. During the encounter with the Fesarius, Captain Kirk ordered the Enterprise's marker launched. Balok destroyed it almost as soon as it was launched. (TOS: "The Corbomite Maneuver")
Data Recorder
A data recorder was a device carried by starships similar to a log buoy or a recorder-marker. In the event of imminent destruction, a data recorder was designed to record all the vessel's data. The recorder was built to withstand the complete destruction of a starship, with the slight possibility of external forces causing damage to the data held within.
In 2154, a data recorder was retrieved from the wreckage of the Andorian warship Kumari by the NX class starship Enterprise. (ENT: "Babel One")