Star Trek Anniversary - John's Top #20: "The Enterprise Incident" (#15)
At #15 on my top twenty Star Trek list is an episode that involves a classic adversary: The Romulans, and also lands Spock in some difficult circumstances.
The episode is a reflection of a real life event of the '60s, and adds significantly to our understanding of Spock, the Romulans, and the Trek universe.
Boy, would this episode have made one hell of a third season premiere!
Of course, that's not what happened, and for over fifty years now, Trekkers have passionately debated the third and final season of ST: TOS (Star Trek: The Original Series, for the non-trekkers out there).
This was the spell during which the late Fred Freiberger (1915 - 2003) assumed the role of executive producer after series creator Gene Roddenberry -- the Great Bird of the Galaxy -- reduced his involvement.
A little background: Roddenberry had apparently promised NBC he would be a hands-on show-runner for the third season, but then the network pulled a fast one and re-scheduled Star Trek to the Friday night graveyard (or "death slot") at 10:00 pm. Roddenberry stepped down, and Freiberger arrived on the scene. Not everyone was a happy camper.
The general perception has long been that Star Trek took a significant downward turn in quality during Freiberger's tenure; perhaps as a result of his involvement.
Yet the ratings-troubled series had other problems to grapple with too, including a dramatic budget cut in the third season which rendered location shooting impractical except on rare occasions (such as "The Paradise Syndrome," early in the new season). According to William Shatner's Star Trek Memories, the per episode budget dropped from a high in the first season of $193,500.00 to a low at the third season of $178,500.00. (William Shatner, Chris Kreski, Harper Collins, 1993, pages 290-291).
Now intriguing, visually-exciting location work -- "planet side" action -- had been a staple of Star Trek in the first two seasons; with episodes such as "Arena," "This Side of Paradise," "The Alternative Factor," "Shore Leave," and "Friday's Child" springing to mind. But in the third season, Freiberger -- in the words of original series star, Nichelle Nichols -- suddenly became a "producer who had nothing to produce with." (Nichelle Nichols, Beyond Uhura: Star Trek and Other Memories, G.P. Putnam and Sons, New York 1994. p.189.)
So depending on mind-set, you can either appreciate Star Trek Season Three for what it is (and in some cases, by necessity what it had to be), or dislike it for the manner in which it differed from the first two seasons.
One can either laud episodes such "The Paradise Syndrome," "The Enterprise Incident," "The Tholian Web" and "All Our Yesterdays" or curse the quality of such outings as "Spock's Brain," "And the Children Shall Lead" and "The Way to Eden."
You'll know exactly where I stand when I review those particular stories in the coming months
One third season episode that holds up remarkably well today is author D.C. Fontana's "The Enterprise Incident," which first aired September 27, 1968 and featured the Enterprise's secret espionage mission inside Romulan space to recover a new and deadly cloaking device technology. This was the second broadcast installment of the last season.
When I interviewed D.C. Fontana for Filmfax, she explained in detail about the origins of this episode: "It was a reflection of the Pueblo Incident, where a ship was captured in an area of sea where it shouldn't have been. The ship claimed not to be a spy ship, but in fact it was a spy ship."
Specifically, on January 23, 1968, the U.S.S. Pueblo, a Banner-class research vessel with six officers and seventy crew men aboard, was surrounded and captured by North Korean vessels. The U.S. government insisted the ship was well within international waters, but the Democratic People's Republic of Korea countered that Pueblo was inside its territory when captured.
Classified, high-security material was eventually found aboard the Pueblo...it was on an American spy mission after all. The ship was brought back to an enemy port (the nearest U.S. naval vessel was -- ironically, the U.S.S. Enterprise -- positioned some five hundred miles south and in no position to assist...). The Pueblo crew was then processed, tortured, and eventually returned stateside. The ship itself remains in the custody of the North Koreans.
In space, all warriors are cold warriors...
In "The Enterprise Incident," Kirk and Spock's secret spy mission also involves the logical half-Vulcan science officer...uh...romancing the Romulan Commander to gain her confidence.
Like the rest of us, then, the Romulans prove themselves intrigued by Vulcan morals and ethics. In this case, they make a bad mistake. The commander is manipulated by the poker-faced Spock. Specifically, he distracts her while a surgically-altered Kirk (now resembling a Romulan) makes off with the top-secret cloaking device. Scotty does a lickety-split installation, and the escape is made.
Notably, Spock re-affirms in this episode that "Vulcans are incapable of lying" and live by a code of "personal honor and integrity." The Romulan Commander naively accepts his word on these crucial matters, and pays the price for trusting Spock.
Yet, "The Enterpise Incident" works so well because the noble Spock clearly takes no satisfaction, let alone joy, in manipulating this Enemy of the Federation. In the hands of another actor, Spock might very well seem like a heel or a cad for actively encouraging the romantic inclinations of the Romulan Commander, but Leonard Nimoy plays the role sensitively; humanely. This subtle approach comes to the forefront during Spock's final conversation with the Romulan commander aboard the Enterprise, in the turbo-lift.
The Romulan commander has been tricked and disgraced. She is angry, and rightfully so, over Spock's trickery. And yet Spock doesn't hide behind orders or regulations here. Instead, he expresses, perhaps obliquely, that this has all been a rather useless and short-lived game. "Military secrets are the most fleeting of all," he acknowledges. Rather, he suggests to the Commander that it is the connection that the two of them shared that will prove more permanent, more lasting.
This is one of the reasons I love and admire Star Trek. The character of Spock -- perpetually the outsider -- gives us a good, outside perspective on ourselves and our behavior.
By contrast, Kirk is the giddy American cowboy, the dashing American secret agent, the guy who is going to accomplish his mission with heroic flair and dynamic action. He is entrenched in his mission (he cannot afford otherwise), and he doesn't really look outside it at the big picture. We love and admire Kirk for this clarity of vision and purpose.
But Mr. Spock thinks more analytically, and with a deeper perspective. He weighs matters outside of petty political and military concerns. Though as a Starfleet officer he performed his duty, he intimates that in this case, that duty involved something "fleeting," hence ultimately unimportant. Rather, the bond established by the Romulan Commander and Spock suggests that these two clashing races/empires can find common ground in the future, beyond the conflict of the present.
The second-to-last time we encounter Mr. Spock in Star Trek history, he is pursuing this very cause: the re-unification of Romulus and Vulcan. I've always wondered if Spock's personal encounter with the Romulan Commander was the impetus of his decision to pursue this tough-to-negotiate peace. In some subtle way, Star Trek -- despite the presence of all kinds of alien creatures and some imperialistic tales -- has really been, sub textually, about the bonds that unite humanity.
We may differ with the Soviet Union (during the Cold War) or the Taliban during the War on Terror, but we hope and pray that in the future what unites us all as inhabitants of the planet Earth will overcome that which today divides us. In Star Trek VI: The Undiscovered Country (1991), only Nixon could go to China; only Kirk could bring peace between the Klingons and The Federation. And here, way back in "The Enterprise Incident" in 1968, the seeds of peace between the Romulans and the Federation are being planted...by Spock; in his humane treatment of the Romulan Commander.
Now, Spock also manipulates the Romulan Commander very successfully and in some sense, it does play as cruel. But lest we forget, she is also manipulating him simultaneously, using what she perceives to be Spock's sense of racial superiority to harness resentment against Kirk and loyalty towards her. So they are both pawns of the mission. But I would suggest that -- all along -- Spock may have a better future in mind. He may be stealing a cloaking device and deceiving a beautiful woman in the present, but he also realizes that military secrets are fleeting and that one person can change the world; can alter the direction of the future (also a message of another Star Trek episode, "Mirror, Mirror.")
In Star Trek history, "The Enterprise Incident" may actually be one of the most significant episodes of all, especially in terms of impact on the franchise.
This episode establishes a Klingon-Romulan alliance (later shattered, with great resentment and animosity in the Next Gen era), and it introduces blue Romulan Ale, though not in name, as a "powerful recruiting inducement." The episode also establishes Spock's time in Starfleet as 18 years.
Much of the drama also hinges on the mistaken belief that "Vulcans are incapable of lying," a turn of phrase which returns in Star Trek II: The Wrath of Khan (1982) and Star Trek IV: The Voyage Home (1986). Also, although Fontana introduced Vulcan "finger-touching" as a gesture of affection in "Journey to Babel," here we see a more...erotic...application. That too returned to Star Trek, in 1984's Star Trek III: The Search for Spock. Additionally, in "The Enterprise Incident," the audience gets some significant knowledge of the Romulans, from the "Right of Statement" to the command structure inside the Empire.
And of course, "The Enterprise Incident" introduces the Vulcan Death Grip. Which, as you surely know, does not exist...
I'll go even further. I believe that "The Enterprise Incident" is very much a template for the modern Star Trek motion picture series, as it involves the Enterprise forced to take dramatic action to capture or otherwise stop a weapon of mass destruction. Here it is the Romulan Cloaking Device. But Khan had Genesis, Soran had the Ribbon -- which he wielded as a weapon, Shinzon had a tharalon device, and Nero had Red Matter.
Over the years "The Enterprise Incident" has not been without controversy, of course. Fontana told me that the "episode wasn't substantially re-written" from what she had imagined, but rather "was changed in ways that really bothered me. The relationship between Spock and the Romulan commander was somewhat different than what I had envisioned. From a production standpoint, the cloaking device was supposed to be small and easily hidden, but on the show it looked like a lamp. That didn't work for me, because they had to run around holding this large device, it was pretty obvious. More than that, the relationship between Spock and the Romulan commander wasn't what I had in mind. I wanted it to be more adversarial than it was."
Indeed, if "The Enterprise Incident" contains one weakness, it is that the Romulan Commander appears far too trusting, far too early, of Spock. Especially since she did not know he was stationed on the Enterprise and therefore could not anticipate her strategy before seeing him on the viewscreen.
Of course, given a little thought, the Commander's actions might be written off as signs of a healthy, Kirk-sized ego. She believes she can appeal to Spock's ego, assuring him that he is a "superior being" and thereby offer him ample incentive to turn against the Federation. Given Kirk's irrational, arrogant behavior leading up this incident (all orchestrated, of course...) it is also easy to see why she could imagine Spock would prefer to serve her rather than the fragile, insulting Captain Kirk. Of course, that's what she's supposed to believe.
I think some fans also dislike "The Enterprise Incident" because it says, basically, that when Starfleet breaks its own laws, it is okay, because -- hey, these are the good guys.
Perhaps today, given all we've been through in the last decade, this makes the program feel a little simplistic. The (overlooked) fact of the matter is that this mission could have sparked an all-out war with the Romulans, one that could have cost millions if not billions of innocent lives across the galaxy.
And furthermore, the Romulans had not even used this cloaking device in battle yet. They had used a similar weapon in the past, on Federation border outposts ("Balance of Terror"), but still, this seems to qualify as a pre-emptive strike, right?
But you know -- honestly -- that sounds more like a Next Gen era story of DS9-flavored one.
And if that had happened here, we might have lost the valuable message that is clear in "The Enterprise Incident:" that peace can begin in the heart of one person, or one Vulcan, as the case may be. That Spock is, for lack of a better word, emotionally affected by his contact with the Romulan commander...who, despite her manipulations, comes across as strangely vulnerable...and likable.
In closing, I submit that "The Enterprise Incident" is a worthwhile and memorable installment of Star Trek because in that last scene, Spock acknowledges something important and true. Kirk, the Romulan Commander, and Starfleet itself are all playing one dangerous move in a much larger chess-game. They are focused on that move: getting the Cloaking Device (or getting the Enterprise, contrarily).
But Spock is thinking a long-term strategy, thinking several moves ahead, to something more permanent than a fleeting military secret. He was touched by his encounter with the Romulan Commander, more than he ever could have imagined.
On the other hand, you could also argue that Spock's entanglement with the Romulans, begun in earnest in this episode of the classic series, is the very thing that destroys his timeline some hundred years down the road. As the Vulcan himself might note, "fascinating..."