All posts by Paul

“Amok Time”

This fight is to the death. Thee should be used to that by now.
“This fight is to the death. Thee should be used to that by now.”

After behaving strangely for several days — throwing soup and stuff — Spock tells Kirk he must go to Vulcan to engage in a mating ritual, a diagnosis McCoy confirms. Kirk, never one to devalue a good mating ritual, defies orders and takes Spock to Vulcan, where he and McCoy accompany Spock to a sort of wedding ceremony. But Spock’s betrothed wife T’Pring (Arlene Martel) chooses a challenge (invoking an ancient right) and surprisingly picks Kirk as her “champion.” Figuring that the weakened Spock might be in trouble if he has to fight someone else, Kirk agrees — and then learns the fight is to the death. Spock, unable to stop himself because of his “blood fever,” goes full on after Kirk, before McCoy sneaks in an injection he says will help Kirk deal with Vulcan’s arid climate and atmosphere. Shortly thereafter, Spock appears to kill Kirk, and McCoy beams back to the ship with the body. Spock then learns T’Pring picked Kirk as a way to ensure she could be with another dude (the details aren’t that important). Back on the ship, Spock arrives in sickbay, all set to turn himself into the authorities when Kirk (alive and well) comes from behind a corner. Spock briefly reacts with joy, in a signature moment of the series, and learns McCoy actually injected Kirk with a substance to knock him out and simulate death. Then, Kirk and Spock head back to the bridge to mind the store.

Hey Spock, he's got an "aw wound." Get it?
“Hey Spock, he’s got an ‘aw wound.’ Get it?”

Why it’s important

This is the original series’ closest look at Vulcan culture and the only time we get to Spock’s home planet before the movies. The idea of a society built on logic, steeped in antiquity, is established here and we get the clear message that Vulcans work so hard to suppress their emotions because they were (and are) capable of such rage. Spock, at one point, says his “blood burns.” McCoy even says that the ordeal Spock and other Vulcans go through once every seven years might be the price they pay for suppressing their emotions most of the time. It’s interesting stuff.

We get our first idea of the look and feel of Vulcan culture, too. Some of it works, though I’m not sure why the wedding officiant T’Pau (Celia Lovsky) speaks in Old English (maybe she really digs malt liquor?). Of course, we see T’Pau nearly 40 years later in “Star Trek: Enterprise” in a well-intended and mostly successful callback to TOS. She appears in the prequel series’s fourth season as a member of a group said to understand the “true” teachings of Surak, the father of Vulcan logic (though she doesn’t speak like a she’s doing Shakespeare in the Park in those episodes, thankfully). Turns out that T’Pau’s group actually has it right and that she and others help turn Vulcan society into what it is in 23rd century Star Trek (dignified pacifists) — as opposed to Vulcans we see in the 22nd century (treacherous bureaucrats).

I just had some great plomeek soup!
“I just had some great plomeek soup! Want some?”

What doesn’t hold up

It’s a nice moment when Kirk and McCoy explain (sort of) why T’Pau is important — because it shows that the Federation isn’t all about humans (a real problem in Trek’s first season). However, it seems like Kirk would know more about T’Pau if he knew she turned down a spot on the Federation Council. In “The Savage Curtain”, where we meet a recreation of Surak, Kirk’s never heard of the guy. So, Kirk’s heard of T’Pau, but not the Vulcan messiah, whose true teachings were uncovered (in part) by T’Pau in a spiritual awakening that changed Vulcan culture and involved Starfleet? Wouldn’t this be like Spock knowing who George Washington was but only that he was the first U.S. president — and not a famed general in the American Revolution?

It’s also odd that we don’t see or hear of Spock’s parents in this episode. In the first season, he speaks of them as if they were dead, but later this season in “Journey to Babel”, they’re quite alive and on Vulcan. Maybe the rift between Sarek and Spock was the reason they didn’t attend this ceremony. Or, perhaps parents aren’t supposed to attend such ceremonies, as part of tradition. Either way, it’s odd when we learn they are, in fact, alive (and that one resembles a certain Romulan commander). The simplest answer, of course, is that the writers decided Spock’s parents were dead until “Journey to Babel.” Same sort of thing happened with Captain Benjamin Sisko’s father 30 years later, FWIW.

Final thoughts

I’ve always felt this episode was somewhat overrated. The fight scene is fine — and the music is pretty great — but such fight scenes were such a part of TOS that this episode isn’t anything close to groundbreaking. That said, as TOS tropes go, it’s not on par with exposition dialog miraculously diagnosing a complex problem, Kirk outsmarting computers or Bones’ medical pouch containing scores of day-saving goodies.

Also, while McCoy’s plan was fairly smart, it also was incredibly lucky. What if the order of the weapons used in the challenge had been reversed? If the bladed weapon had been the second one used, Spock could have easily beheaded Kirk — or bashed in his skull. Or, what if Kirk had simply passed out at a moment when Spock wasn’t attacking him? Then, what?

And, of course, T’Pau’s failure to explain the ancient ritual is a huge conceit. Would it really have been that hard to tell Kirk, before he accepted the challenge, that the fight was to the death? This flaw could have been fixed, by the way, by Spock simply being unhinged during the fight with the matter of “to the death” being vague. I know T’Pau telling Kirk the true stakes of the fight — after he’s accepted — is a thunderclap moment, but it’s too hard to swallow. It either means T’Pau wasn’t smart enough to consider Kirk wouldn’t just know that the fight was too the death or that she was too obstinate/prideful to tell him. The second option doesn’t fit with the idea that Vulcans are logical pacifists.

All that said, there are moments in this episode that I like a lot. Seeing Vulcan and the land owned by Spock’s family was pretty cool (this is an episode that really benefited from the new remastered effects, BTW). And T’Pau was certainly an interesting character. I liked her questioning of Spock’s humanness — in lines that (I believe) were sometimes cut for syndication. There are a couple other moments I didn’t love — was Spock about to seduce Nurse Chapel in his quarters when she came to tell him they were heading to Vulcan? — but Nimoy and the writing staff really did a good job overall.

The episode’s best moment, though, is when Spock asks McCoy to attend the ceremony for his “closest male friends.” It’s an important moment because it shows Spock and McCoy are not actually enemies, despite their trademark bickering. I know the surprised/happy Spock is what everyone remembers from “Amok Time,” other than the fight music that would show up again and again for the next two seasons. But Spock’s moment of vulnerability with McCoy was really wonderful.

“Errand of Mercy”

Kor,_2266
“By your comman — I mean, today is a good day to die.”

Kirk and Spock travel to Organia, a primitive planet about to be in the crossfire in a looming conflict between the Federation and some newly introduced baddies, the Klingon Empire. As Kirk tries to convince the Organians that they should let Starfleet establish a base on the planet, the Klingons arrive, led by Commander Kor (John Colicos), and establish a military post as Kirk and Spock are forced to go undercover (and as the Enterprise leaves orbit). With the Federation and Klingon fleets poised to begin fighting — Sulu’s in command of the ship with Scotty and McCoy apparently on Wrigley’s Pleasure Planet or something — the Organians reveal themselves as extremely power aliens, and stop the conflict from happening. This, of course, sets up decades of Cold War-style conflict between the two heavyweights, one of the key aliens in all of Trek, and bat’leths hanging over many a nerd’s fireplace.

asdfasdf
“Starfleet’s about exploration. But I just said I’m a soldier, not a diplomat. But sometimes, my job calls on me to be a diplomat. And my medical officer keeps saying he’s a doctor … and not a bricklayer or a moon-shuttle conductor. And one time, he said he wasn’t an escalator! Basically, I’m really confused all the time.”

Why it’s important

The Romulans technically arrived first, but the Klingons were TOS’ main bad guys, a fact that is especially true in the movies (Klingons appear in five of the six TOS films). Instead of being mysterious and enigmatic like the Romulans, the Klingons clearly have had lots of recent dealings with the Federation, as Kirk is able to describe them — or, at least, how he sees them — without much couching to the Organian leaders. Klingon bastards.

The Klingons really became the Bad Guy of the Week in Trek’s second season, whereas the Romulans only appear twice more in TOS (only once more with actual actors playing Romulans) and only briefly in the movies and never as the main bad guys. It’s hard to imagine Star Trek without Klingon-heavy moments like the final battle scene in “Star Trek VI: The Undiscovered Country” or the tense scenes at the Genesis Planet in “Star Trek III: The Search for Spock” — to say nothing of the Klingons’ role in the next four series. “Star Trek: Voyager” is the only show without a lot of Klingon stories, despite the presence of a half-Klingon chief engineer.

And it all started on a little world called Organia.

asdfasd
“I don’t like the tights you’re making me wear.”

What doesn’t hold up

Of course, the Klingons here LOOK very different than they do starting in “Star Trek — The Motion Picture”. Up until the events of the fourth season of “Star Trek: Enterprise,” this was arguably the biggest wink-wink-nudge-nudge item of the franchise, with DS9 even acknowledging it as such in perhaps Star Trek’s most meta moment in “Trials and Tribble-ations.” Later, of course, we learn that the change in appearance had something to do with Klingons’ attempts to create Super Klingons by riffing on human genetic-engineering methods. Oh, and Anakin Skywalker actually built C-3PO. Yuck.

As was the case for a lot of the Klingon depiction in TOS, the warrior race that is so concerned with honor in TNG sure doesn’t seem very honorable here. The Mind Sifter — a tool Kor uses unsuccessfully on Spock to determine whether he’s a spy — is straight out of the Romulans’ playbook. But, to paraphrase Worf in another episode, “They are Klingons, and it is a long story.”

Also, Starfleet is at its most militaristic here, with Kirk actually calling himself a soldier (not a diplomat). Was Gene on vacay on the Jersey Shore with Majel when this episode was filmed? While TOS is certainly the most militaristic series in Trek (DS9 competes at times) with lots of talk of “the service” and “braids on shoulders,” etc., “Errand of Mercy” takes it to the extreme. That’s not necessarily a problem in an episode where everyone’s worried about a war. But it is noteworthy.

Final thoughts

This is a great Kirk-Spock episode (not to be confused with a Kirk-Spock-Bones episode, which is actually a very different thing). It’s my favorite example of Spock not being an overt pacifist (talking about crimes against science) while also not being a caustic jerk (proposing to off Jim’s long-time buddy who just happens to be evolving into a god or something). Shatner also is about pitch-perfect in this episode (“Go climb a tree”) and Colicos is great as Trek’s first real Klingon. Kor’s final line about how the averted war “would have been glorious” might have laid a foundation for Klingons as much as anything else.

This isn’t a great episode, but it’s a very good one. The biggest mark against it is that the plot here is too similar to what happened in “Arena.” In both episodes, Starfleet is prevented from taking action (combat) against an enemy — and god-like beings intervene (with different details). The Organians here are somewhat more interesting because they’re posing as simple backwards aliens — which sets up the big twist when they reveal they have the power to stop the Federation and the Klingons. But the lesson that Kirk learns at the end (that humans aren’t the most powerful beings in the universe) isn’t at all new. Or, at least, it shouldn’t be.

“Space Seed”

“This was nice! How’s about we do it again in 15 years when you’ve gone crazy and when I’m feeling old and worn out?”

The Enterprise finds a derelict ship that left Earth in the late 1990s. On board are about 70 individuals asleep for (ahem) two centuries. The leader is automatically awakened when Kirk and Co, enter the ship and later identifies himself only as Khan (Ricardo Montalban). It turns out he is actually Khan Noonien Singh, one of many genetically engineered supermen who fought for control of Earth in the early 1990s, when most of us were watching “The Real World” or something. These supermen were defeated, but Khan and his followers escaped in the sleeper ship. Khan awakens his followers and briefly takes over the Enterprise with the help of the ship’s historian, Lt. Marla McGivers (Madlyn Rhue) who has fallen for him. But after Khan gets more and more brutal in attempts to turn enough of Kirk’s crew to operate the ship, McGivers helps Kirk escape suffocation. Kirk defeats Khan in hand-to-hand combat (hmmm) and then allows Khan, McGivers and the rest of his people to settle on the savage Ceti Alpha V, rather than going to prison. And everything works out just swell for Khan after that. Oh, wait …

asdasdfadsf
“You’re right, Mr. Spock. He does look a lot like Mr. Roarke from ‘Fantasy Island.’ Security …”

Why it’s important

This could have been a very good one-off episode. But Khan, of course, returns in “Star Trek II: The Wrath of Khan” and returns (in a different way) in “Star Trek Into Darkness”). Anyone who hasn’t seen Wrath of Khan who’s reading this blog is probably a statistical anomaly. But, if you are the anomaly, stop reading now. 🙂

Not long after Kirk maroons Khan on Ceti Alpha V, a nearby planet explodes, making Khan’s planet even less hospitable. For the following 15 years, he and his remaining superpeople somehow manage to survive (they played a lot of checkers) until Khan captures the U.S.S. Reliant and steals the experimental Genesis device, which can turn a dead planet into a living planet. More details on all that when we review “Star Trek: II”. After a battle with the Enterprise, Khan detonates the Genesis device in the Mutara Nebula. Spock sacrifices himself to fix the Enterprise’s engines to escape the device’s blast, setting up the events of “Star Trek III: The Search for Spock”. When Kirk steals the Enterprise to retrieve Spock’s body on the newly created Genesis planet (what used to be the nebula) he encounters a Klingon vessel intent on stealing Genesis’s secrets. In the ensuing ordeal, Kirk’s son David Marcus (one of the Genesis creators who we meet in the previous movie) is killed, the Enterprise is destroyed and Kirk and Co. steal the Klingon ship and escape as the unstable Genesis planet explodes. They then take Spock to Vulcan, where he is, in effect, reborn.

And, of course, Kirk and Co. use the Klingon ship in “Star Trek IV: The Voyage Home”. Without the ship and its cloaking device, it would have been much harder to go back in time to 1986 San Francisco to bring two humpback whales to the 23rd century to answer the call of a probe threatening to destroy Earth. Without them, Earth would have been lost.

I could keep going, of course, as the death of David Marcus plays a minor role in “Star Trek VI: The Undiscovered Country”. But you get the idea. The introduction of Khan is a major domino in Star Trek, even though the character only appears in one episode and one movie. Our apologies for the high amount of spoilers — but we figured it was important to explain Khan’s relevance .

as;ldkfjas;dfkj
“Wait, what am I doing reprising the role of an Indian character played by a Mexican actor? This would only get more ludicrous if my character’s blood somehow revives the dead.”

What doesn’t hold up

There’s, of course, the issue of Khan and other supermen taking control of Earth in the early 1990s. This is one of those nudge-nudge-wink-wink moments on par with (pre-“Star Trek: Enterprise”) why the Klingons didn’t have forehead ridges in TOS when they had them starting in “Star Trek — The Motion Picture”. All that said, it’s hard to be that critical of the creators for not expecting in 1967 that people would be watching Star Trek in 1996, let alone 2014.

But there’s also some dispute regarding Earth’s third world war. Spock says the events surrounding Khan and his ilk in the late 20th century were a world war, which McCoy labels “The Eugenics Wars.” Subsequent Trek episodes and movies seem to place the third world war in the mid-21st century (at least, that’s when it ended).

There’s no real good explanation for this — unless you figure that the tampering with the timeline (starting with “Tomorrow is Yesterday” and continuing throughout the next 50-plus years of Trek) had a bigger effect than the good guys realized. I personally blame it all on Scotty’s decision to give that one dude the secret to transparent aluminum in 1986.

And, maybe, the time-traveling we see throughout Star Trek’s many episodes and films could explain even more timeline questions …

Obviously, this episode is probably the greatest illustration of the creators being overly optimistic about the progress of space exploration in the late 20th century. There’s the existence, in 1996, of a sleeper ship capable of interplanetary travel and McGivers’ line about how suspended animation was used in space travel until the late 2010s because of the time involved (a reference to the fact that ships were likely slow). That said, if anyone knows how I can get on one of those sleeper ships, I hear Vulcan is lovely in the spring. And I’d love to go skiing on Andoria.

There are even more, less obvious clues. Khan left Earth in 1996, and Kirk tells him that he’s been asleep for two centuries. Of course, the timeline established later puts this episode in 2267 — 271 years after Khan left Earth. Wouldn’t most people, in a similar situation, tell Khan he had been asleep for three centuries, or NEARLY three centuries, or even 250 years? I doubt someone in 1967 would say something that happened in 1696 took place two centuries ago …

It’s pretty clear to me (as discussed in previous reviews) that TOS was loosely intended (back in the ’60s) to take place in the late 22nd century. Fifty years ago, a Federation of Planets with Earth as a key member might have seemed somewhat plausible, by the late 2100s, if space exploration had continued at its 1960s pace throughout the rest of the 20th century. This episode, Kirk’s comment in “Tomorrow is Yesterday” that being locked up for 200 years (starting in 1969) would be about right and Gary Mitchell’s comment in “Where No Man Has Gone Before” that a poem written in 1996 was “one of the most passionate love poems of the past couple of centuries” (among other things in that episode and others) all would seem to back me up.

BTW, I don’t keep bringing this up to knock TOS. I just find it interesting to note the optimism the creators — and the adjustments they quietly made over the years when their optimism turned out to be misplaced. The adjustments start appearing early in the TOS films.

In other news, I’m constantly amazed at how much access to the Enterprise Kirk routinely gives to potential security threats like Khan and Christopher from “Tomorrow is Yesterday,” (to say nothing of Lazarus in the absolutely awful “The Alternative Factor”). This is a very different episode if Kirk doesn’t decide it’s cool for Khan to wander the ship (allowing him to manipulate McGivers) and look over the Enterprise’s technical manuals. Hell, it’s hard to imagine that Khan would have had the wherewithal to run the Reliant 15 years later if not for that knowledge.

Lastly, while some would say that Chekov’s absence in this episode doesn’t jibe with Khan recognizing him in “Star Trek II,” that can easily be explained as Chekov being on the ship but not yet a bridge officer. I note this to show that I’m not a total geek when it comes to continuity — but just wait until we get to “Voyager” …

Final thoughts

I go back and forth between “Space Seed” and “Mirror, Mirror” when asked about my favorite episode of TOS. I’m probably in a “Space Seed” mood these days, because “Mirror, Mirror” has two of my least favorite Trek tropes — exposition dialog that somehow analyzes a very strange problem with amazing clarity (the TOS equivalent of technobabble, really) and a technical solution that’s just totally ham-fisted and doesn’t make a ton of sense.

“Space Seed” isn’t perfect, but it doesn’t use either of those crutches — and it’s a great episode besides. Montalban is just amazing as Khan, and the scene where he manipulates McGivers is about as edgy as anything Trek has ever produced (it’s amazing it was on television at all in 1967). Shatner, too, is really strong in this episode. Of course, we are shown another example of Kirk in a fight to beat the bad guy for all the marbles — but while that’s cliche, it’s a believable cliche that mostly makes sense. I guess that thing Kirk hit Khan with was really, really hard?

I suppose the biggest question is, should Kirk have left Khan and Co. on Ceti Alpha V? Even if you put aside the fact that the planet became a barren wasteland after the events of this episode, Kirk’s decision could have had some pretty nasty side effects (as Spock hints at before the credits roll). What if Khan had escaped isolation and become a major threat to the Federation? Rich Corinthian leather and Chryslers for all?

“Tomorrow is Yesterday”

Fellini_questions_Kirk
“Wait, did you say 200 years? That won’t work — can you lock me up for 300?”

An accident hurls the Enterprise back in time to Earth, circa 1969, where it’s spotted in the atmosphere by an Air Force pilot sent to investigate a report of a UFO. Kirk accidentally crushes the plane with a tractor beam (good one, Jimmy) and is forced to beam the pilot, Captain John Christopher (Roger Perry) aboard. Kirk and Spock must deal with Christopher in a way least damaging to the timeline. They’ve also got to find a way to get the Enterprise and her crew back home. After initially determining Christopher isn’t historically relevant — which Spock TELLS Christopher in a kind of harsh scene — the crew later learns Christopher’s unborn son will be historically significant, so he needs to go back, Jack Shephard-style. The crew first must recover some photos from Christopher’s plane, leading to Kirk briefly getting captured at an Air Force base. After rescuing Kirk, the crew determines they can slingshot the ship around the sun to go back in time (or something) to return Christopher and a security guard they beamed up  during the photo-recovery mission and then get back to their own time.

Yes, yeasdfklajsd;fkasdf
“That’ll be the last time Scotty makes me watch clips from his trip to Wrigley’s Pleasure Planet.”

Why it’s important

Other than the goofy business at the end of “The Naked Time” — which, kinda probably could have been part one of this episode — this is the franchise’s first foray into time travel. Admittedly, it’s questionable as to whether this is enough to make the episode historically important under this site’s guidelines — would a history text about Star Trek include this incident or even be able to record it? — but it’s significant in a creative sense. Without this episode, one wonders if we’d have seen classics such as “The City on the Edge of Forever,” “Yesterday’s Enterprise” or “The Visitor.” Of course, it would have likely saved us from the Temporal Cold War nonsense on Enterprise, but you take the good and you take the bad, as Mrs. Garrett would say.

Even if this episode is borderline significant, it’s extremely interesting to watch Kirk and Co. as they get their arms around what kind of roles they might play if they interfere with the timeline. It’s almost on an elementary level. Once Christopher’s aboard the Enterprise, Kirk lets him just walk the ship — something that later captains likely would have prohibited. Spock actually has to point out to Kirk why letting Christopher see so much is a problem! Later, Spock only has the presence of mind to check for Christopher’s name in the historical records, and not his offspring. This is something that Kirk and Spock would have been all over even by the second season, but here, they really don’t get it yet.

Oh, and of course, the method for time travel seen here is what we (mostly) see in “Star Trek IV: The Voyage Home”.

KirkChristopher
“This is all very disconcerting, Captain Kirk. But I’m sure I’ll be good with it in like 5 minutes.”

What doesn’t hold up well

This episode shows another example, or a possible example, of how the Star Trek creators were overly optimistic about how far mankind would get in the latter part of the 20th century when it came to space travel. Christopher’s son, Sean, turns out to be historically significant because he was on the first mission to Saturn. Now, as of this writing, there are no plans for that to happen.

It’s, of course, possible that Sean was born much later in Christopher’s life — say, 30 years after the events of this episode. That would make Christopher about 60 when Sean would have been born and Sean about 15 as of this writing. That means Sean could end up being on a mission to Saturn sometime after 2025 or so.

Regardless, the big question is, how likely is it that man will send anyone to Saturn sometime in the next 30 years? Based on the scuttling of the shuttle program in the early 2010s, I’d say it’s pretty unlikely. And based on events from other episodes — notably Khan leaving Earth in a fairly sophisticated spacecraft in 1996 — I doubt the creators were expecting Sean’s mission to take place so late in the 21st century. The idea almost certainly was that Sean would be born relatively soon after this episode and been involved in a mission to Saturn before the end of the 20th century.

The other big issue in this episode is the ending. Putting aside the slingshot business and the logistics of the final scene — if the Enterprise is traveling at warp, how does it have several minutes to beam Christopher and the security guard to Earth? — why was it necessary to beam them both down? Shouldn’t they just have vanished from the Enterprise when Christopher’s plane wasn’t destroyed? Shouldn’t the Christopher in the jet have been the one to stay? And, where did the one who was in the cockpit go? Same question for the guard.

Like I said: The creators were clearly getting their arms around time travel here.

Final thoughts

I know I’m being hard on an episode that almost deserves pilot-level (no pun intended) treatment. In all honesty, I like “Tomorrow is Yesterday” a lot. Nimoy found the right notes as Nimoy and particularly Shatner might have turned in one of his best performances. His scenes with Christopher are great, and the interrogation where Kirk calmly refuses to provide any information to the Air Force officers who captured him was pitch-perfect. Gregarious-but-authoritative Kirk is one of the things Shatner did very well. He doesn’t bark at Christopher as to why they can’t just send him back to Earth. He explains it calmly, but it’s clear who’s in charge.

And Perry as Christopher is good, too. Granted, he’s a little too composed for someone who’s just been beamed aboard a space ship, learned of alien life and been told he can never go home. But, he’s an interesting character if you swallow he’s that strong a person.

Meanwhile, Kirk and Spock determine where they are at the beginning of the episode when they hear a radio broadcast about the upcoming “man-moon shot,” set to launch on that upcoming Wednesday. This episode, of course, was broadcast in 1967, before Apollo 11 launched — which occurred on Wednesday, July 16, 1969. Apollo 11, of course, was the mission that actually sent men to the moon.

So, while I might have dinged the creators for being too optimistic about man’s long-term progress in spaaace, it’s pretty neat that they nailed it here, even if it was just a stroke of luck to pick the actual day of the week of the launch two years later. Hat tip to our buddies at Mission Log for pointing this very cool detail out.

Last point: This might be one of the very few time-travel episodes reviewed on this site. That’s not because we don’t like those episodes. But in many cases, the metaphorical reset button shows up, meaning the events aren’t historically relevant because they didn’t actually happen. That’s not really the case in this episode — Kirk’s crew retains memories of the events. Still, it was the episode of TOS that gave us the most pause to include in this project.

“Balance of Terror”

Star_TrekBOT
“I can’t figure out why there’s a camera right here. Guess I’ll call tech support …”

The Romulan Star Empire — a mysterious former nemesis of Earth unheard from for a century — returns and destroys several border outposts with a mysterious and super-scary weapon. The Enterprise responds and has protracted battle sequences (think submarine warfare … in space!) before Kirk’s tactical genius bests Spock’s dad — err, the Romulan commander (Mark Lenard) — and destroys the invading ship preventing another war and cementing our boy Jimmy as, well, our boy Jimmy. He’s apparently of a kind. And a sorcerer!

Why it’s important

“Balance of Terror” introduces one of Trek’s main villains, the Romulans, and does so in a way that is amazingly consistent with what we see of them for the next 40 years — unlike, say, the Ferengi, who go from allegedly eating their enemies to caterers and bartenders in six years flat. Of course, the episode also has the big reveal that the Romulans are offshoots of the Vulcans and introduces the concept of the cloaking device to Star Trek. It’s an extremely foundational hour of the franchise. Just think if that racist dude Stiles (Paul Comi), the Enterprise’s navigator in this episode whose ancestors fought and died in the previous conflict with the Romulans, had stuck around!

asdfasdfasd
“Just a second, Enterprise. I need to make sure you get video from me even after my outpost is destroyed.”

What doesn’t hold up well

The previous conflict with the Romulans as stated by Spock and others, is too Earth-centric even for first-season TOS standards — and especially if you consider the events of “Star Trek: Enterprise” (but even if you don’t). Apparently, Earth’s war with the Romulans occurred after the coalition that would become the Federation was established in Enterprise’s final episode “These Are the Voyages …” but before the Federation itself was formed. Or something.

Dramatically, it’s interesting in “Balance of Terror” that the Romulans have never been seen by humans (and it sets up the Big Moment™ when Spock sees a dude who looks just like his pops on the viewscreen — even though we don’t see Mark Lenard playing Sarek until season two). But it’s hard to believe that no visual communication or prisoner taking was previously possible, based on the 22nd-century technology on “Enterprise,” to say nothing of the visual communications technology available in the real world in the 21st century. It’s too bad that Spock didn’t just say that the Romulans refused visual communication back in the day. That would have been more believable than the apparent lack of Skype on Romulus or Earth 150 years from now. Maybe the Romulans were just way into Snapchat?

“Enterprise” also later pisses all over the wonderment of the cloaking device by giving Jonathan Archer’s crew’s a clear understanding of the technology and knowledge that the Romulans (and others) use it. “Selective bending of light,” indeed, Mr. Science Officer.

Lastly, the bad science of TOS pops up by asserting that the Romulans are a real threat despite their vessel’s lack of warp drive. Maybe Romulans have warp (even though the Bird of Prey seen in this episode doesn’t) making the Romulans a threat to the Federation in a larger sense, as opposed to being on par with the goofy aliens from TNG’s “The Outrageous Okona.” But the cat-and-mouse game is undercut by the fact that the Enterprise should be able to outrun the Romulan vessel several times over.

stiles
“My bigotry is too big for my quarters. Sir.”

Final thoughts

Complaints aside, it’s possible that this episode set up the very idea of recurring villains in Star Trek, a huge, huge deal. Soon after, the Klingons were introduced, and the two main rivals of TOS were set (with all due respect to a certain dude in a certain rubber lizard suit and Harcourt Fenton Mudd). Beyond that, “Balance of Terror” is fascinating because it’s willing to show actual bigotry (from a 23rd-century human!) as a way to show why bigotry is wrong and something humanity was still working to move past (and mostly succeeding). It’s very effective, but it’s also unusual for Trek and would have been unheard of in TNG, when all humans were apparently beyond such things.