Star Trek is my all-time favorite science fiction TV series. In this post, I want to take a deeper look inside the Star Trek universe itself and talk about an important technicality of commanding a starship.
Several important caveats: this topic was never addressed in the Series Bible (that we know of), episodes were not always written by the same writer, and the story editor and/or producer were not always able to keep things consistent, even within the same season. The point is not to focus on the seeming inconsistencies, but to try to come up with a plausible mechanism for everything to co-exist.
This episode’s topic: The Self-Destruct Sequence or Who’s the Captain?
In the Original Series episode “Let That Be Your Last Battlefield”, the Captain, Science Officer, and Chief Engineer had to voice-authenticate themselves to the main computer and recite a code sequence. The Captain then initiated the self-destruct countdown.
This seems reasonable. The computer can examine voice patterns and can authenticate the person from that voice. The use of a random code sequence would prevent the splicing together of previous utterances of the persons into the correct code sequence to start an unauthorized self-destruct (the computer does not seem to be able to tell where a person is — remember Ben Finney in “Court Martial”). Assuming the code sequence is subsequently changed (assuming it CAN BE — it’s presumed to be a one-use code!) or cannot be used a second time, then all is well.
However, in the third movie, Kirk, Scotty, and Chekov use the exact same code sequence to initiate the self-destruct sequence. There are several problems here. Kirk may or may not still be in command of the Enterprise; it’s in Spacedock to be decommissioned. Scotty is officially Captain of Engineering on the Excelsior. Why would the Enterprise’s computer think he is authorized? Ditto for Chekov: he was last the Executive Officer of the Reliant. This brings into serious question how much the computer trusts who is giving it orders. Certainly it can have voice patterns for every Star Fleet officer. But it seems to blindly trust that whoever has the correct code sequence is authorized to use it to initiate the self-destruct sequence. It’s also beyond belief that the code sequence is the same in the time between these two events. It’s a deliberate breaking of the fourth wall to have it remain the same.
In various Next Generation episodes, the Captain and First Officer must voice authenticate and verbally agree to initiate the auto-destruct sequence. There’s no more command sequences. Since the computer now knows where an individual is, this makes sense.
However, there is an underlying issue I’d like to examine. How does the main computer know who is really in command?
In the Original Series episode “The Doomsday Machine”, Commodore Decker attempts to take command of the Enterprise in the absence of Captain Kirk (and being a ranking officer in addition). He is ultimately thwarted when Kirk orders Spock to relieve Commodore Decker, “on my personal authority as captain of the Enterprise”. The episode was a psychologically-focused episode and Decker did not remain in command for long, so the question cannot be resolved.
In The Next Generation, it appears that the ship’s computer decides who is in command. When Captain Picard is captured by Cardassians, Captain Jellicoe is appointed captain. There is a short ceremony in which the computer acknowledges Jellicoe’s authority. Another ceremony occurs when Picard resumes command. There are a few questions here.
How does the computer recognize an authorized transfer of authority? Presumably it must consult with Star Fleet Command, otherwise there could be a transfer of authority under duress. Can command be transferred to someone not a member of Star Fleet? I would expect not.
In another Next Generation episode, Data locks the rest of the crew out of the computer by applying an encryption key. While the key is probably long enough to not be guessed or easily computed, the fact that the Second Officer, on his own authority, can prevent the Captain from issuing commands is troublesome.
One episode in which we can give the computer a pass is when Captain Picard is transformed into what his body was like decades ago. The computer refuses to accept his voice commands, but he can still issue commands via direct entry. Although this does raise a question about an officer having a cold or laryngitis, it seems a reasonable safety feature, given the option of entering commands from a terminal.
I’ve probably missed other episodes or situations that raise questions about this subject. Maybe I’ll cover them in a future article.