Truly the 24th (or whatever) Century were (will be?) more enlightened times.
He was promoted to Captain in STIII: The Search For Spock. He was assigned to the U.S.S. Excelsior while Starfleet was investigating the incident with Khan. That’s how he was able to cripple the Excelsior so that Kirk could take the Enterprise to the Genesis planet.
In the TNG episode Relics, he remained a captain, although retired.
The basic rules are just the same for ocean-going vessels. But you don‘t call them all captains; you have the Captain, the First Mate or First Officer, and the Second Mate or Second Officer. However, I don’t know of any play, movie, or TV show that treats it all realistically; it just makes for better storytelling to have all the interesting events happen during the Captain’s watch.
I believe TNG made Data the Second Officer, and gave him an episode. Babylon 5 had a Second Officer, for the record, but he never appeared. Good, tight stories always trump cluttered realism.
Right, that’s him holding the rank of “Captain”. That’s realistic; promotion through the ranks will happen to any competent officer who stays in the service long enough, no matter what their specialty. The part that doesn’t match real-world militaries is the title “Captain of Engineering”.
Engineering officers on submarines can advance to command of vessels, though.
Not on subs - on subs every officer except for supply officers can become a CO.
Maybe @Monty is thinking of the UK Navy? There at least used to be a strict division between engineering officers and command officers on British subs.
My engineering watch section got assigned the midwatch for a month straight while the “day” sections trained for their ORSE exam, which meant we had to get up for all of their drills.
On the upside, this gave us time to figure out how to take over the world. We never actually did because:
- We didn’t know where to get ahold of a speedboat.
- We didn’t actually have any demands (other than not having to stand midwatch anymore).
Nope. I was thinking of the US Navy. I’ve very little knowledge of how submarines work.
@iiandyiiii Why are supply officers left out?
It’s having the plan thats the important thing.
Thanks for the info.
So we may be, quite understandably and doubtless unknowingly, conflating two things. Not all officers (in the US Navy, at least) holding leadership positions in engineering are “Engineering Duty Officers” or (as another distinct category) Limited Duty Officers in Engineering. The Chief Engineer on an operational submarine will almost certainly be an Unrestricted Line Officer, same as the Navigator and the Weapons Officer. *Smaller conventional ships (Cruiser and smaller) tend to follow the same model, but are even faster and looser with roles. It’s not uncommon within the conventional navy to find someone who has had a leadership role in engineering on one ship and a non-engineering job on another ship. With particularly junior officers (the Ensigns) they might even change jobs on the same ship during the same tour.
Anyway, almost all the officers on a submarine are nuclear trained submarine officers of the unrestricted line, with the exception of the supply officer and… maybe the weapons officer on an SSBN? Honestly, that I don’t know.
Point being, the biography you have linked for appears to be an unrestricted line submarine officer who has predominantly filled roles in engineering, but not the type of officer who could only fills roles in engineering.
*On larger ships, such as amphibs and aircraft carriers, you are much more likely to find specialists. So for instance the Chief Engineer (who is not in charge of the reactors) on a Nimitz-class CVN may be some form of Engineering Duty Officer or Limited Duty Officer who only works in engineering. Now, if you really want your head to explode, the person who is actually in charge of the reactors (the Reactor Officer) will be a Commander or Captain by rank who most recently performed the job of Captain on a smaller ship.
But evidently, Star Fleet does things differently. Or… maybe it doesn’t. Maybe the reason we see Scotty always in engineering is the same reason we see him as always on the Enterprise: the writers didn’t want to write him off and replace him with someone else as would tend to happen in the real world every few years, so him staying forever in engineering was incidental to him being bound interminably to Enterprise (brief interludes in other assignments notwithstanding).
So is the Chief Engineer actually an engineer, or is he just a guy who’s in charge of engineers?
At least sometimes, yes. Both WEPS that I served under were prior-enlisted and not nuclear propulsion trained.
On a submarine, the Chief Engineer will have been through nuclear propulsion training, which the Navy claimed was equivalent to a Masters in nuclear engineering. OTOH, some of my classmates at Nuke school had been history and English majors at the Naval Academy.
On a surface ship? Maybe. On a submarine? Yes.
That is, all submarine officers except the supply officer (and maybe the weapons officer on an SSBN—thanks @abcdefghij) might fairly be called “engineers” in that they will all have gone through the year-long nuclear propulsion training pipeline. Oh, and they all (all the nuke school grads officers, I mean) have to qualify as Nuclear Engineer Officers by the end of their first tour.
On a surface ship, however… well, on a bigger ship they actually will tend to be an engineer. On something like a cruiser or a destroyer, they will have had less formal training and—once upon a time, but not so anymore thank god—it might once have even been their very first tour in engineering. This was a thing the Navy would do 15 or more years ago, or so I’ve heard: since all Surface Warfare Officers (the generalist surface ship equivalent to a submarine officer, but with a lot less training) are required to qualify as Engineering Officer of the Watch to qualify for command at sea, there was a time when the surface Navy applied its “sink or swim” mentality to the role of Chief Engineer. Part of the motivation may also have been spite and to avoid the “hookups for f##k ups” problem. Because Chief Engineer is a tough job, you know? If there is a way to avoid it by simply not qualifying EOOW, well…
Anyway, I never had that problem. I was a surface nuke and did my share of time in… well, not engineering, but reactor department.
Thanks for all this.
I’m not @iiandyiiii and I don’t definitively know, but probably because Supply Corps is its own distinct arm of the Navy. At least when I was in, Supply Officers tended to move between sub and surface and sea and shore more than Unrestricted Line Officers. SuppOs would get qualified as Diving Officer of the Watch, but not Officer of the Deck or Engineering Officer of the Watch.
I would think they would run watches like Horatio Hornblower and Nimitz did.
As for the OP, it was right in the first episode, The Corbormite Maneuver that they mentioned watches. Remember:
MCCOY: Practically end of watch.
BAILEY: What, are you all out of your minds? End of watch? It’s the end of everything.
TOS would have watch changes, but it was “background” rather than a plot point.
TNG must have watch changes, or otherwise how would the poor helpless red shirt (literally!) navigator get his brain fried by Nagilum instead of Westly, who was sitting there mere moments before.
The Corbomite Maneuver was the tenth episode, aired on November 10, 1966. The first aired episode was The Man Trap on September 8, 1966.
Oh, and it’s Wesley, not Westly.