Tag Archives: John Meredyth Lucas

Science Fiction/Fantasy, TV

[January 31, 1969] Clinging to life (Star Trek: "That Which Survives")

3 Comments


by Lorelei Marcus

I'm convinced Star Trek is cursed.  Around the same time every season, the episodes drop off in quality, going from engaging teleplays each week to bottom of the barrel Hollywood hack.  Of course, the divide isn't quite so clear cut, but there is a distinctive shift as the producer runs out of his stellar front-runners and begins scrounging for TV-writer backlog to fill space.

I had hoped Season 3 would be an exception to this given its new producer and absolutely sublime first half ("Spock's Brain" notwithstanding!) but alas, the proverb remains true: the bigger they are…the harder they fall.

Now, granted, the recent decline has not been a degeneration of ideas, which often carry promise and interest, but their clumsy and contradictory execution.  We as the audience are baited in on hooks, reeled in on the currents of the episode, and then discover, too late, that the answer at the end of the line is more convoluted and less inspired than the theories we'd developed during the journey.

And "That Which Survives" is no exception.

title card for the episode with That Which Survives superimposed over a blue planet

We begin with the Enterprise circling a newly discovered planet anomaly: it has an atmosphere and plant growth despite its young geologic age and small size.  Kirk, McCoy, Sulu, and senior geologist D'Amato (an exciting new face—but don't get too attached) beam down to study the planet.

As they're being beamed, however, a mysterious woman (Losira, played by Lee Meriwether, lately of Time Tunnel) pops aboard and kills the transporter technician!  The landing party makes it down anyway and ends up in the center of a vicious earthquake.  The Enterprise experiences a similar tremor and is flung 990.7 light years from the planet.

Losira, in a purple outfit, stretches her hand out toward the party as it begins to beam down, a transporter technician in the background
"Wait!  Let's shake hands, first!"

Spock standing behind Lt. Rahda, Scotty looking up at him, on the bridge
Spock is more concerned about rounding errors than the ship's current predicament, chastising Lt. Rahda for describing the distance as "1000 light years".

The landing party immediately began protocol for a survival situation after failing to detect or contact the Enterprise.  Sulu and McCoy both pick up odd readings on their tricorders: "Like a door opening and closing."  At the same moment, D'Amato sees a beautiful woman—the same one from the transporter room—who claims "she is for him" and tries to touch him.  She succeeds, and he drops dead, every cell in his body disrupted.  His corpse is soon discovered by the other three, but the woman is nowhere to be found.

A nervous D'Amato points at Losira (not depicted)
Arthur Batanides is both delighted not to be cast as a mook this week, and dismayed that he's about to die

While the landing party scenes are the most interesting part of the episode, not much more happens.  The woman eventually reappears and tries to attack Sulu, but Kirk and McCoy intervene, discovering in the process that the woman can't hurt anyone but the person she is targeting.  She disappears and reappears again, going after Kirk this time, but Sulu and McCoy successfully protect him.  For no apparent reason other than a limited runtime, the three are then allowed access to the planet's defense control center, and they learn the truth of the mysterious woman.  It turns out the original builders of the planetoid accidentally invented a disease which killed off their race thousands of years ago.  The commander left behind a computer imprinted with her personality and programmed it to kill any intruder.  Kirk manages to destroy the computer before it can kill them, and all is well.  A fine solution, though rushed and poorly explored, the episode would have hung together alright…if the scenes on the Enterprise didn't destroy all meaning in it.

Elevated shot of Kirk, McCoy, and Sulu in an octagonal room, Losira in front of them, a shimmering cube on the ceiling in the upper right
"Wait!  Maybe I can talk it to death.  It's worked with every computer before…"

Shortly after the Enterprise is flung 1000 light years away, the death-robot woman appears on the ship, is implied to read the mind of a technician, kills him, and sabotages the matter/anti-matter combustion tubes.  This raises questions like:

"How did the woman travel so far from the planetoid?"

"Why did she bother to attack the ship when it was no longer anywhere near the planet?  Isn't 1000 light years far enough away for the computer to no longer see the Enterprise as a threat?"

It would have made more sense if the ship had simply been damaged from teleporting (logical, since it was never explained how the feat was done) and Lee Meritwether's lost screen time could have been made up for on the planet with additional scenes of the landing party unraveling the mystery of the lost civilization.

I haven't even mentioned the terribly dull scenes of Scotty trying to save the Enterprise from a Losira-induced explosion.  Every party of that sequence felt like an artificial addition to stretch runtime.  To summarize, Spock tells Scotty how to do his job, Scotty hesitates, runs into some roadblocks, then finally, in the last ten seconds does the job and saves the Enterprise.  That's it.

Scotty in a tube, shrouded in blue sparks, sticking a wrench into a small hatch.
"I've found the leak, Mr. Spock!  I canna change the laws of plumbing!"

Once again, this is an area that could have been improved with some minor changes.  Instead of the whole ship blowing up, have it simply be stranded.  The tension comes from whether Scotty can fix the ship in time without getting himself killed.  Have Spock as a commander wrestling with whether to eject the pod Scotty's working in because a wire's accidentally been tripped and now the whole ship is at stake.  That would have been compelling storytelling.

This episode had so much promise: the promise of another ancient civilization and 4-D beings (Losira's teleportation effect is genuinely neat), of new cool characters and cameos of old beloveds like Sulu and Dr. M'Benga, of survival plot interwoven with futuristic technology.  Indeed, there were a lot of pieces to love.

But, like a robot who is only beautiful on the surface, the actual experience was less than pleasant.  Three stars—2 for the episode, and 1 for Merriwether's great acting.  Hopefully, next week will be better.


by Gideon Marcus

Full reverse!

Remember the execrable episode, "The Galileo Seven"?  There, we were meant to believe that Spock had never held a command in his life, and when forced to lead just six stranded crew on a hostile planet, he kept tripping over the basic emotional needs of his human comrades.

Now recall "The Tholian Web", where a much-improved Spock handled Captain Kirk's presumed death with tact and even compassion, officiating a funeral, commiserating with McCoy, and generally earning the respect of his crew.  Scotty even called him "Captain", in a tear-inducing moment.

Heck, just recall last week's "The Mark of Gideon".  While in no wise a good episode, Spock carried out negotiations with Chairman Hodin with reserve and acumen.  This was a man who could, when the need arose, handle the center seat without issue.  And we know from "Court Martial" that people in blue shirts sometimes become starship captains…

This week, the Enterprise is imperiled, Spock's two best friends and the ship's Third Officer are missing and presumed dead, and yet the half-Vulcan pedantically harps on decimal points and the human compulsion to be thanked for carrying out their duties.  He is a cold fish, inspiring no loyalty.  He also never seems in much of a hurry to do…well…anything!  It is absolutely inconsistent with his demeanor as acting-skipper established over the last two seasons.  Moreover, it is inconsistent with his ever-deepening bond with Kirk and McCoy.  The real Spock would be mad with worry…and covering it up with a stoic and efficient veneer, welding together a 430-man team whose sole purpose is to retrieve the distressed landing party.

But it was easier to write a caricature.  As one of our guests last week noted, it was as if the episode had been written by someone who hated the characters and wanted to lampoon them.

Spock gets up from his chair on the bridge, holding an gadget, several crewmembers behind him
"Is it already time to harass someone else?  Goodie!"

Then, of course, we get the egregious bit where it's Spock who tells Scotty how to fix the failed matter/antimatter regulator.  As Joe Reid has noted many times, Kirk often gets the pleasure of being the smartest person in the room, suggesting solutions to folks who should be telling him how to solve problems.  This time, Spock is the beneficiary of this irksome trend.  At least in "The Doomsday Machine", Scotty is ahead of Kirk in the figuring out of things, and he beams admiringly at his captain as if at a promising student.  In "That Which Survives", Scotty has considered and discarded Spock's solution—manually fixing the antimatter flow—as too dangerous.  With no other solutions, what, exactly, is it more dangerous than?

Blech.

While we're at it, Kirk was quite the jerk to Sulu on the planet.  Perhaps this was because he was distraught from the potential loss of the love of his life (the Enterprise), but at least he could have said he was sorry, as he has done in every other instance where he has snapped at crew under tension.

2.5 stars.


by Janice L. Newman

Slivers of Silver

While I agree with my esteemed co-writers about the poor characterization and plot holes in this episode, there were some good new special effects that I don’t recall seeing before.

I always enjoy looking at the props, especially after having read the interview with the man responsible for creating them in one of the many fanzines. The blue-tipped grass on the planet was pretty and interesting, giving it a slightly alien feel. The effects with Losira disappearing by seeming to fold up into a black line were new and intriguing. When Scotty went to fix the broken warp engine, a neat ‘blue lightning’ effect made a barrier across the tube. The flickering red and green lights on his face, though a bit headache-inducing to watch, also aided the illusion and increased the tension of the scene.

Scotty's face illuminated by a green gel light
"There's your problem, Mr. Spock—a green gel light!"

Losira’s costume was cleverly-designed, but felt strange and wrong for her role. Several of my friends commented on the fact that she didn’t look at all like the head of a distant outpost whose members had just been killed off by a plague. With the cutouts in her shirt and her elaborate hairdo and makeup, she did not have much of a ‘last survivor’ or ‘hearty commander’ feeling. Of course, there is nothing wrong with being feminine, and for all we know she may have dressed up in her race’s version of formal wear before giving her final report. Still, it clashed uncomfortably with the plot for many of us, even if the seamstresses among us were mentally trying to figure out how to re-create the look.

Unfortunately, well-done effects cannot carry a story, and, while the episode was mildly-engaging, it didn’t leave much of an impression. Two stars.

Are There Men on This Planet?


by Mx. Blue Cathey-Thiele

I was not the only viewer disappointed by some stand-out moments which highlighted that, progressive though Star Trek is, it still has weak spots. In particular this week: sexism. Losira is a replica of a commander, the last survivor of a disease-struck station. Her costume, while intriguing in design, conveyed none of that. Sulu comments when first threatened that he “doesn't want to shoot a woman.” As chivalrous as the helmsman is, by the time of starships and alien worlds, I would hope that humans no longer treat women differently than men, deadly touch or not. And then too, the repeated focus on beauty. A storm can be beautiful and deadly, but observing a force of nature is not the same as McCoy, Sulu, and Kirk making a point to comment on how Losira looks. These are the same crew who get excited about flying into the heart of a giant amoeba or historical facts from centuries past. After all they experienced on this not-a-planet, it seems improbable to focus on whether or not they found an alien woman attractive. As explorers and scientists, why not marvel at the mysterious botanical and geological feats, the design of the defense system, or the fact that that defense system was able to send the Enterprise through a molecular transporter and 990.7 light years away! Or wonder why a defense system would be calibrated to perfectly match a target, and seemed as equally focused on unifying as destroying?

Losira appears holographically on a wall in front of Kirk and Spock after her computer is phasered
(sings) "What intrigues a man about a woman is elusive…"

Despite the flaws, and feeling put off by the attitude of the men, I still enjoyed the episode. Characters had time to share the spotlight and pull on threads from previous episodes. I love seeing the crew operate the Enterprise when the Captain is away, and how different officers handle command. Lt. Rahda did a fine job as helmsman, and it was nice to have Dr. M'Benga return to the screen. Logically, a ship this size must have multiple doctors, but this episode confirmed that a minimum of three were present, despite us usually only seeing McCoy and Nurse Chapel. (Maybe the ship could spare one to give Spock a check-up after that bump to his head.) I also noted Kirk's persistent focus on supplies—he brought up the need for food and water at least four times—which may have been in part due to his experience on Tarsus IV, which started with a crop blight: something that is bound to leave a lasting impression regardless of whether he talks about it.

The overarching plot was lacking, and I would have liked to have gotten more explanation or simply explanation spaced out better. However as an episode among a larger story, it gave us a great look at the workings of my favorite starship and crew.

3.5 stars

[Come join us tonight (January 31st) for the next thrilling episode of Star Trek!  KGJ is broadcasting the show live with commercials and accompanied by trekzine readings at 8pm Eastern and Pacific.  You won't want to miss it…]




3 Comments Leave A Comment
Science Fiction/Fantasy, TV

[January 2, 1969] Blood, Sweat, and Tears (Star Trek: "Elaan of Troyius")

9 Comments


by Janice L. Newman

On December 23rd, 1968, exactly eleven months after they were captured by North Korea, the crew of the USS Pueblo was finally released, and the world breathed a collective sigh of relief. The USA would not be starting World War III over the incident, and our boys, though they’ve been starved and tortured, are coming home alive for Christmas.

It is thus appropriate that this week’s Star Trek episode revolved around choosing peace instead of war.


Bill Theiss, you've done it again!

In the episode opener, we learn that the Enterprise has been sent to support Petri, Ambassador of Troyius, in his mission to “train” the Dohlman of Elas to be a suitable wife for the Troyian leader. The Dohlman turns out to be a beautiful woman played by France Nuyen, made up to look like Cleopatra in a bathing suit. Her name is Elaan, and she is imperious and demanding, while Petri is servile but contemptuous. They are intractable in their dislike of each other. Kirk quickly becomes exasperated with both of them, telling Petri, “Stop trying to kill each other. Then worry about being friendly.”


"And maybe try wearing a bikini…"

In the meantime, the Enterprise is being followed by a “ghost” ship, which eventually materializes and proves to be a Klingon warship. This is a nice callback to Balance of Terror, where the Enterprise played the part of the “ghost ship”, and the recent Enterprise Incident, where we learned that the Klingons now have cloaking technology.


"Follow that starship!"

No sooner does the ship reveal itself than Kirk is called away from the bridge again. Elaan has stabbed Petri, who declares that he will have nothing more to do with her.  He also explains to Nurse Chapel that the mysterious “allure” of Elasian women is merely biochemical: “A man whose flesh is once touched by the tears of a woman of Elas has his heart enslaved forever.”

Back in Elaan’s quarters, Kirk is fed up and declares that he will be Elaan’s new teacher. He tells her she is, “an uncivilized savage, a vicious child in a woman's body, an arrogant monster!”


"I said, 'Gimme five'—you've got to learn modern courtesy."

I must admit, my sympathies were thoroughly with Elaan. Despite her imperious attitude in the beginning, it becomes increasingly clear that she has no choice in the political marriage and no desire to be married. At one point she says, “I will not go to Troyius, I will not be mated to a Troyian, and I will not be humiliated, and I will not be given to a green pig as a bribe to stop a war!” And yet, the Enterprise continues on its way to Troyius, regardless of her behavior, her orders, or her protests. It seems she has no true power, but is merely a pawn to be traded, and probably one the Elasians don’t actually care much about.

In fact, I had to wonder if the Elasians didn’t want peace at all, but sent their “Dohlman” to be married as a sop to the Federation. That way they could say they’d tried, and if the Troyians couldn’t handle the Dohlman, well that just proved that peace wasn’t possible between them.

This also nicely sets up the question of why the Federation cares so much about stopping the war between these two planets, to the point of bringing diplomatic pressure and sending one of their best starships to ensure that the wedding and negotiations go well. Scotty blatantly asks the same question in the episode opener, leaving it to rest in the back of our minds as we watch.

The next day, Kryton, one of the Elasian guards, sneaks into Engineering and sabotages the Enterprise. Kirk forces his way into Elaan’s quarters and again begins trying to “teach” her, which mostly consists of wrestling with her and threatening to spank her. She starts to weep, and he wipes away her tears. The effect is immediate, with Kirk’s ire evaporating and transforming into passion.


"Say, you didn't just hear a kind of snake rattle sound, did you?"

Kryton is caught, and kills himself rather than allow himself to be subjected to a Vulcan mind meld. Kirk orders Scotty to figure out what Kryton did, then returns to Elaan’s quarters. Elaan tries to convince Kirk to work with the Klingons, but he tells her there are more important things than love: “Elaan, two planets, an entire star system's stability depends on it. We have a duty to forget what happened.”

At this point, those of us who have been watching Star Trek since the beginning already know what’s going to happen: Kirk will always choose the Enterprise over everything else. And indeed, when Spock and McCoy come to roust the captain out of Elaan’s quarters, all it takes for him to leave Elaan behind is to hear that the Klingon ship has changed course and is approaching at warp speed.


"Don't mind me.  I always walk this stiffly when my friends are watching…"

Once Kirk gets to the bridge, we’re treated to one of the best combat sequences we’ve seen yet on Star Trek. Kryton’s sabotage, Kirk learns at the last possible moment, was rigging the matter-antimatter unit to blow if the ship went into warp. The Klingon ship therefore starts by trying to bait the Enterprise into going into warp, and that doesn’t work, just firing on them.

The captain sends Elaan to Sickbay because it’s the safest part of the ship. Petri speaks to her there, finally treating her with a modicum of graciousness and respect, and asks her to wear the necklace gifted her by the Troyians, “as a token of respect for the desperate wishes of your people and mine for peace”. She seems genuinely affected by the words and gesture, perhaps realizing that Kirk will truly never sacrifice duty for love.


"Please put these on.  The Emperor paid retail."

Back on the bridge, the crew struggles to keep the Klingon ship’s hits to its best shield (Kirk doing a bit of back seat driving as he leans over Sulu and gives him his orders). An impulse-power driven ship is no match for warp, though, and all seems lost.

Elaan appears on the bridge, wearing the Troyian wedding dress and necklace. Spock immediately notes that there are strange readings coming from the necklace. It turns out that the stones, which Elaan says are “common”, are dilithium crystals! (No wonder the Federation and the Klingons are both so interested in this system!) She gives them to the Captain, who has Spock hurry them down to Engineering, where he and Scotty start installing them. Kirk does his best to stall, but the Klingons are unwilling to discuss terms (I imagine that after “The Enterprise Incident” and The Deadly Years, the Klingons have been instructed not to listen to anything the Federation says—or at least nothing that Kirk says.)


This fellow is no Michael Ansara.  He's not even a William Campbell…

The crystals are ready in the nick of time. A photon torpedo at close range leaves the Klingon ship damaged and limping. The Enterprise leaves it behind to fulfill its original mission.


Pow!  Right in the kisser.

Kirk says farewell to Elaan, who asks him not to forget her. He tells her he has no choice. Nor does she, she replies, only duty and responsibility. It’s clear that she’s come to accept her role, though whether it’s because she realized that her last desperate play to manipulate the captain failed or because her near-death experience made her decide that peace was more important than her personal feelings, we do not know. It is also worth noting that while she goes on to marry into a culture she despises and where she will likely be surrounded by people who hate, fear, and ridicule her (if Petri’s behavior is any indication), Kirk will simply continue doing what he loves. Her choice of “duty” over all else is thus, in my estimation, a far more difficult and admirable one.


"Oh, this knife?  I was just going to pare my nails.  Not kill the Emperor or anything like that, why do you ask?"

McCoy, unsurprisingly (given his track record) discovers an antidote to the Elasian tears. Spock tells him the captain has no need of it, as he’s already found his antidote: the Enterprise.

There were many things to love in this episode, and many things that frustrated me. The “Taming of the Shrew” sequences early on were grating, but the combat was excellent, and to the scriptwriter’s credit, the story did not end with Elaan being “tamed”. In the end, she makes a choice to accept her fate, but she does so with dignity.

The things I liked and didn’t like balanced out pretty well, leaving this a three star episode for me.


by Gideon Marcus

The Sum of its Parts

What I found so gratifying about "Elaan of Troyius" was its continuity with the Trek history we've encountered thus far.  Once again, as in "Journey to Babel", the Enterprise is host to a diplomatic mission (though how the ship could house several dozen delegates to the Babel Conference, but Uhura had to give up her room for Elaan, is never explained).  Once again, Kirk shows irritation at having to play nursemaid to a bunch of civilians.  I would find his flip treatment of Elaan demeaning, but it's no worse than he displays to Commissioner Ferris or Commissioner Fox.

I particularly loved the galactopolitical situation depicted in the episode.  Here we have a fairly new Federation system with two hostile planets, abundant with dilithium crystals, perched right at the edge of the Klingon Empire.  What a fraught situation Kirk must navigate!

At first, it was difficult for me to glean the plot behind the plot, but by the end of the episode, the setup was pretty clear.  The Federation, upon learning of the rich deposits on Elaas (and Troyius?) placed a clamp on all dispatches coming out of the system.  Not good enough, though, as the Klingons clearly want the worlds badly, too.  The Feds then explained to the two worlds in the system that they must work things out.  Elaas grudgingly agrees—and then effects two simultaneous plans to queer the deal.

The first is Kryton's sabotage.  By handing the Enterprise over to the Klingons, they get in their good graces (if, indeed, the Klingons have good graces).  Obviously, the savage Klingons are a better fit for for the militaristic Elaasians anyway.


"Of course I want to be a Klingon—you think I want to keep wearing this outfit?"

The second is Elaan.  She clearly doesn't want to be there.  Indeed, she does everything she can to get out of it, despite orders from the Elaasian council.  Elaan goes so far as to try to murder the Troyian ambassador and seduce the captain of the Enterprise.  And yet, that scheme fails when Elaan takes a page from Kirk's book, and indeed the example of the whole crew, that duty and the preservation of life trumps all else.  It's a quick, undershown change, but it's there, and I appreciated it.

The episode reminds me a bit of the parable of the peasant woman who shelters a starving prince.  The royal promises to give a gold coin for every fat bubble in the soup she serves.  Greedily, she dumps a huge pat of butter in the soup, which results in one big bubble rather than a myriad of little ones.  Similarly, if the Elaasians had stuck to just one plan, they might have succeeded.  Instead, they double hedged and lost all.

And was the Klingon commander operating with Imperial sanction?  Or was he a rogue skipper with notions of glory?  After all, taking on a starship seems pretty bold given the ever-watchful Organians.

It's not a perfect episode, but it's certainly an engaging one, and I always enjoy seeing Mrs. Robert Culp on the small screen.  Plus, her appearance alongside Shatner is something of a reunion—they starred together in the Broadway version of The World of Suzie Wong.  Plus, I dug both the Klingon ship (which we saw a bit of in "The Enterprise Incident" and "Day of the Dove") and the score for the episode.

Four stars.

Twixt Scylla and Charybdis


by Trini Stewart

The beginning of this week's episode did not seem promising to start, mostly because of the guest characters' first impressions on me. Petri the ambassador seemed childish and reckless in his peacemaking, and Elaan was almost comically uncooperative for royalty sent as a hospitable offering. Looking back, Elaan was possibly playing to her strengths to some end with her antagonistic reactions, and her development with Kirk ultimately became a gripping trial for our captain.

Kirk was the shining star of this episode, which is not something I feel about him often. He was impressively quick-witted against biochemical and psychological manipulation, which really sold his captain qualities for me more than his usual speeches or fights. The way Kirk kept his priorities in check while thinking on his feet reminded me of how Spock left me feeling in "The Tholian Web" when he held the ship together without Kirk. In the short time I have known Kirk, he has struck me as the type to always know what to say and fight when there is no other choice. Kirk managed to unravel the layers of the princess's antics even with serious disadvantages, revealing what his problem solving is like when he is out of sorts. Tension was well-built in this episode on several levels, and the challenges Kirk faced were arguably more dynamic and interesting than Spock's in "The Tholian Web".


"What's a case of tight trousers when the Enterprise is at stake?"

Kirk transitioned from acting as a respectful host to a firm authority with Elaan, and his initial responses to her rude behavior were tastefully poised. Once Elaan had seduced Kirk, he still managed to expertly dismantle the Elaisians’ schemes without falling for the Dohlman or her subordinates’ clever tricks. Shatner did a great job conveying how difficult it was for Kirk to maintain his composure, so it was riveting to see just how he would escape the Klingons, prepare the guileful Elaan for her marriage, and get the Enterprise back in ship shape under that level of duress. His allegiance to the Enterprise evidently sobered Kirk; his articulate maneuvering reflected his symbiotic relationship with the ship and her crew. In the end, even Elaan was humbled by our captain, finally submitting to the responsibilities her title bore. I was quite pleasantly surprised by Kirk this week, and the adversities threatening the crew were positively captivating. 4 stars!

Be Our Guest, Do As You Please


by Joe Reid

“Elaan of Troyius” was this week’s episode of Star Trek.  “Taming of the Shrew” storyline aside, there is one thing that the writers of Star Trek keep doing to twist my britches, and this episode was another example of it.  The Enterprise, powerful symbol of human achievement, has the laziest security imaginable.  Episode after episode, people that wish to do harm to the ship and its crew need only to walk into what should be the most secure areas of a ship to do as they please practically unchallenged.  Areas that on large ships, not all members of the crew are even allowed to enter.  So, let’s delve into some of areas of a ship that guests should not enter.

Let’s begin with the command center of the ship.  The bridge.  The seat of command, where the captain steers the destiny of a ship to complete its missions.  Obviously, a perfect place for a teenage princess to casually enter whenever she chooses.  Elaan pierced the bridge and interrupted the ship’s captain, while he was in the middle of a combat situation.  Good on the writers for making the captain, thanks to Spock’s urging, send her away from the bridge, only to have her show up on the bridge again after a change of clothes.  For an area holding some of the most senior members of the crew, it seems unusual that it wasn’t better protected.  Past episodes showcased singing children, enemy androids, and furry tribbles having free access to the brain trust of the Enterprise.  I anticipate that 15% of Kirk’s problems could be solved by securing access to the bridge to “Bridge Crew Only”.

The next ludicrous pattern that we witnessed in this episode was the open and unguarded access that guests on the Enterprise had to Engineering, the area of the ship that provides all the power, without which the Enterprise couldn’t move, fight, or support human life.  Why did Elaan’s former suitor have a free ticket to stroll into this most vital part of the ship and sabotage systems?  Again, good on the writers for allowing him to be discovered, be it many minutes later, only to allow the discoverer to be summarily executed for his weak efforts to question someone he'd found messing with the thing that keeps the ship alive.  If only this random trespass in Engineering were rare.  Previous episodes sported children again, along with genetically advanced conquerors, self-aware talking space probes, and Klingons traipsing merrily into the bowels of Engineering. 

Where before I said that 15% of Kirk’s problems could be solved by securing the Bridge, 99% of problems could go away if Engineering had a couple guards working shifts to protect the very heart of this starship. 


If only Kevin Riley were on duty, none of this would have happened.  So long as he's sober…

Historically there have been some areas of the ship that have been kept secure week after week.  Areas that no one can casually walk into without permission (unless you are a floating cloud of space gas that is). Those would be crew quarters.  Even in this week’s episode, crew quarters were better guarded, and their doors are better respected, than what should have been the most sensitive areas of the ship.  Not even Spock and McCoy could casually walk into the room where the captain was passionately kissing Elaan. 

Perhaps future episodes will take the security of the most critical parts of the ship more seriously.  That, or have the crew consider moving the engines and bridge staff to crew quarters, where doors are respected.

For continuing to overlook this easily solvable problem, I offer only 2 stars for “Elaan of Troyius”.  Ignoring the fact that the episode did display some interesting makeup and costumes, and featured a few well-acted scenes, the continued stupidity of the security of the ship is as untenable as its “secure” areas.

Two stars

[Come join us tomorrow night (January 3rd) for the next thrilling episode of Star Trek!  KGJ is broadcasting the show live with commercials and accompanied by trekzine readings at 8pm Eastern and Pacific.  You won't want to miss it…]




9 Comments Leave A Comment
Science Fiction/Fantasy, TV

[October 4, 1968] (Star Trek: "The Enterprise Incident")

3 Comments


by Erica Frank

This episode begins with Kirk acting strangely, and everyone on the Enterprise has noticed. He is snappish, angry, arbitrary; he gives orders that defy Federation law and threatens people who argue with him.

His crew is loyal; they have been through many hardships together—so when he orders them into the Romulan Zone, they obey, although they are obviously nervous.


The Captain's orders are final

They are, of course, discovered, surrounded by Romulan vessels of a new, Klingon design. Kirk and Spock are compelled to beam aboard the Romulan ship to discuss matters, in exchange for two Romulan prisoners sent to the Enterprise. Kirk insists their location is a matter of instrument error: by the time they discovered the mistake, they were too deep in Romulan territory to get away quickly. The Romulan Commander (the first woman flag officer we have met in the show) says that sounds like—well, she doesn't call it the produce of a hind end of a male cow, because she is being politely formal, and this is a television show for families (and the Romulans may not have cattle), but she obviously indicates that it sounds implausible to her.


Color her unconvinced

Spock… confirms her opinion. Says the captain has been irrational recently. That he ordered them past the Neutral Zone. Kirk gets angry and threatens him, and is removed to the Romulan brig. Later, he injures himself enough that they call McCoy to attend him, and he attacks Spock. Spock defends himself with the "Vulcan death grip," an attack we haven't seen before, that looks surprisingly similar to the mind-meld grip.


The closer Jim gets, the worse he looks…

The Romulans send the captain's body back to his ship while the Romulan Commander attempts to convince Spock that he'd be much happier in the Romulan empire.

Have we seen this before?

McCoy revives Kirk. (I wonder if anyone actually thought Kirk died.) Kirk tells a select few people that his supposed insanity was a ruse, a form of dodging accountability in case they were captured. This is an undercover mission. 

The interesting part of the episode, for me, is the Romulan Commander's discussions with Spock. She attempts to seduce him in multiple ways, first laying out how much more power he'd have in the Romulan empire, and when Spock says he does not want command of a ship, she switches tactics. She offers him fine Vulcan food, which he admits is better than what's on the Enterprise. Pours him drinks—first a clear blue-green liquid, and later something orange, served in small glasses like liquor. Spock eats tiny food on toothpicks, and relaxes with her.

She puts herself into the bargain: "Romulan women are not like Vulcan females; they're not… dedicated to pure logic." She drapes herself enticingly, making sure he knows what she's offering. She whispers her name in his ear, and he tells her it's beautiful.


Oiling her traps

At each point, he makes appreciative comments, tells her that the offer is indeed a good one. That he can tell he'd have more power, more freedom, more creature comforts in the Romulan empire.

Eventually, he agrees to her terms: he will lead a small party of Romulans aboard the Enterprise, and from there order the ship to surrender at a Romulan port, her flagship at its side.

It doesn't matter what the terms are. He's lying. He's obviously lying—at least, it's obvious to anyone who knows him. Maybe outsiders who think Vulcans are actually emotionless would believe that Spock agreeing that the food is good means he's content to betray his heritage and his captain and wander off to a government with helmets designed to cover pointed ears.

Predictable but not boring

Instead, it turns out Spock was stalling for time so Kirk could sneak back to the Romulan ship in disguise and grab the new cloaking device. Scotty then has to install and use it before the Romulans get their phasers online—of course there's a deadline. But if we didn't believe Spock used a death grip on Kirk, we weren't going to believe the Romulans would succeed in blowing up the Enterprise. We wonder how they will escape, but not whether.

We could see the Commander convincing herself that her seduction was working—and we could also see Spock watching her reactions, feeding her facts that would convince her that he agreed, without actually admitting to being moved by her offer. Since he's a Vulcan, she doesn't expect him to offer an emotional reaction—and she fails to notice that not only is his enthusiasm lacking, so is any admission that he's actually been persuaded.

He says that the food is better than what the Enterprise has—he doesn't say that he'd leave his position for it. "Please give up your career; we have better snacks" is not going to work on anyone who actually likes their job.

Four stars. I loved the nuanced interactions between them, and I could tell something was off about Kirk but wasn't sure what until McCoy revived him.

Rewriting the present


by Gideon Marcus

Somewhere in North Korea, 83 American sailors and officers are interned, their captain occasionally forced to make confessions as to why his spy ship, the U.S.S. Pueblo, was inside Communist waters in January of this year.  I'm sure you all remember the news—air units were redeployed from Vietnam to Japan, the U.S.S. Enterprise (the aircraft carrier, not Kirk's ship) was stationed off the North Korean coast, and there were rumbles of an impending World War 3.  Indeed, if it hadn't been for the North Vietnamese launching their Tet holidays offensive at the end of January, shifting our focus, who knows where things might have ended up?

With The Enterprise Incident, the metaphor couldn't be more blatant.  The Romulans have been remolded.  Gone are the Kriegsmarine/Roman hybrids that populated "Balance of Terror".  Now they are cloaked in Orientalism, down to the little sideburns Joanne Linville sports, with their smooth speech reminiscent of every movie that features a sinister Red Chinese or Korean.  Vina's exotic theme from "The Cage" has been reworked for the Romulan Commander (effectively, I might add).  The defense-minded Romulans, who showed no interest in capturing the Enterprise when it violated the Neutral zone in "The Deadly Years", suddenly want nothing more than the prize of one of Star Fleet's finest vessels, a greed that proves their undoing.

And so, the American public gets to have its cake and eat it, too.  The Romulan Commander has the right of it when she accuses Kirk of entering Romulan space on a Federation-sanctioned espionage mission to get the cloaking device.  Yet, thanks to a series of Mission: Impossible-style exploits, the "good guys" get away with not only bearding the lion, but stealing the lioness. Rah, rah.  We win.


For ease of maintenance, you can't beat the easy-to-remove Cloaking Device!

This episode is only the latest in what has become a kind of motif.  Earlier this year, John Wayne's "The Green Berets" (the movie that took Sulu away from us for much of Trek's second season) turned Vietnam into World War 2, complete with a platoon with soldiers named Muldoon and Kowalski—and precious few black troops.  David Janssen, no longer a fugitive, plays a jaded reporter, who comes to learn the value of the American presence in Southeast Asia.  And so, contrary to any news you might have read this year, we win the war in Vietnam.

And just last month, the movie Anzio came out, detailing that SNAFU of a landing on the Italian coast in January 1944.  Robert Mitchum plays…a jaded reporter, who comes to learn the pointlessness of the American presence in southern Europe.  Thus, the anti-war movement comes to World War 2.

Mind you, "The Enterprise Incident" is better than either of those two movies.  It's superlatively paced, the dialogue crackles, the chemistry between Nimoy and Linville is palpable, and Shatner makes a convincing Romulan.  I'm even getting used to Scotty's new hairdo.  But the flag-waving has not been so blatant since "The Omega Glory".  Juxtaposed with the nauseating Nixon ad that aired halfway through, lambasting American policy in Vietnam and promising "peace with honor", the episode just didn't sit well with me.

Four stars.  Just have your Maalox tablets handy.

The Lady IS the Tiger


by Janice L. Newman

I’ll admit, when I watched The Enterprise Incident the other night, at first I was frustrated by the behavior of the Romulan Commander. But upon watching the tape we made of the episode with our trusty “Videocorder”, my feelings changed.

Women have an interesting, inconsistent place in the Star Trek universe. Sometimes they are slaves or seemingly exist only to titillate the male characters, like Shahna or Kara (the dancer from “Wolf in the Fold”). Sometimes they have positions of power and importance, like Uhura, Commissioner Nancy Hedford, or Sylvia. Yet even the women in the latter group often give up their position or power when tempted by romantic love. I originally thought the Romulan Commander fell into this same trap, but upon re-watching the episode, I realized I was wrong.

The Romulan Commander is doing her job.


These boots are made for commanding

When the Enterprise flew into the neutral zone, what a plum it must have seemed had fallen into their lap. After the ‘shoot first, ask questions later’ response from “The Deadly Years”, perhaps the Romulans re-evaluated their policy for when a ship like the Enterprise strayed into their territory. Or perhaps this particular commander was just especially ambitious. Regardless, rather than immediately blowing up the ship, she looked for a way to capture it and its wealth of intelligence. Knowing that the crew would surely self-destruct rather than let themselves be taken, she sought a crack in their armor that she could exploit.

Her interest in Spock thus becomes a rational, considered strategy rather than that of a woman letting her heart overrule her mind. She is believably attracted to him, but she is also doing her duty. If she can ‘turn’ Spock, and if he then orders the crew to surrender rather than self-destructing, not only will she win the starship, but the cooperation of a high-ranking Starfleet officer.

Perhaps her reach exceeds her grasp. Perhaps she is too greedy. With the benefit of hindsight and inside knowledge of Kirk’s and Spock’s personalities, it’s easy to be judgemental and say, “She should have just blown up the ship,” or “She should have known better.” But these are still better than, “She should have been thinking with her head rather than her heart.”

When her actions are viewed as those of an ambitious Romulan Commander who wants to get ahead and who is loyal to her people, they make perfect sense. After all, how many times has Captain Kirk used seduction to manipulate women and get what he wants? Can we blame the Romulan Commander for taking a gamble and trying the same? She may have lost, but I can’t help but respect her for trying.

I also appreciated Spock’s acknowledgement that no other outcome was possible, because she would not have truly respected him if he’d made such a choice. No matter how attracted to him she might have been, in the end she would merely have been using him, and they both know it. If there were any doubts that she was seducing him for political more than personal reasons, this line lays them to rest.

Three and a half stars.

The bounty


by Mx. Blue Cathey-Thiele

Two officers beam onto a ship. The captain is confident and capable, skilled at manipulation, and fools even the audience. One provides a distraction and the other collects a valuable asset in a dangerous gamble.

No, I don't mean Kirk stealing the cloaking device.

It was a neat trick and one that allowed the Enterprise to escape without a trace, but I would argue that it was not the actual mission goal, or at least, not the only mission goal. As Kirk and Spock went up against the Commander – who could serve as the Romulan answer to Captain Kirk – this was yet another layer of the ruse. Romulan technology is advanced, but what is more powerful? Knowledge.

It was only in "Balance of Terror" that Romulans were even seen for the first time in a century. Additionally, Starfleet intelligence had already told some of the Bridge crew that Romulans were now using Klingon ship design. Between a cloaking device and the weapons capability to obliterate entire outposts, why switch to a design that the Fleet is not only more familiar with but has dealt with more often? The Enterprise could be destroyed before they ever make contact with a ship past the Neutral Zone. An alliance with the Klingons could change the terms of the Organian peace treaty. Klingon/Federation battles may not be possible but bringing in allies might circumnavigate the way the Organians neutralized fighting capabilities. Finding a way to disrupt a power consolidation such as that seems a far more compelling reason to risk losing the Enterprise or potentially igniting a new conflict with the Romulans.


Spock obtains the real prize of the expedition

With Kirk "dead" and the more immediate threat "discovered", Spock was free to act. He and the Commander shared cultural information, confirming aspects of what the species knew of each other. He also had time to observe Romulan command structure, the quarters of the Commander, and possibly even collect information from her mind. This would be a gamble, as they share distant ancestry and Spock can be vulnerable when connecting with another mind, but not inherently riskier than the plan for Kirk.

Whether they escape with the cloaking device or intelligence, Starfleet gains something to use.

5 stars

Mission: Possible


by Joe Reid

In his letter to the Corinthians, Saint Paul says, “…I am made all things to all men, that I by all means save some.” This episode, “The Enterprise Incident”, epitomized becoming many things to a varied audience.  This episode skillfully blended multiple themes and genres into a cohesive quilt that when looked at from a distance you realize isn’t a quilt at all.  It is a beautiful tapestry, a singular thing that through different sets of eyes will reveal itself differently. 

In the past I complained about episodes that attempted to do too many things in one airing: “The Gamesters of Triskelion” comes to mind.  The different themes in that episode were not blended, to the point of being jarring.  “The Enterprise Incident” presents a military thriller, a heist story, a secret agent tale, a romance, and a science fiction story all rolled into one.  This unified, multifaceted story is not the only reason that I loved this episode.  Here are some other reasons:

It didn’t go out of the way to tell the audience what was happening.  The events told the story.  There was no long explanation from Captain Kirk as to what was happening.  We were given no reason why Romulans were flying Klingon ships.  There was no discussion as to why the commander of the Romulans was female and whether that was common.  The audience was given no revelation as to whether or not Romulan commander had feelings for Spock or if she was simply tricking him.  In this episode things were what they were, and it was up to the audience to make sense of the event for themselves.  An intelligent tale for intelligent viewers.


Even Subcommander Tal is impressed

Another reason to love this episode is because of the amount of respect that was given to the Romulans.  There were not overtly evil, mustache twirling, or stupid enemies in this episode.  The Romulans made no logical missteps in the episode.  Their actions were based on information that they verified.  The Romulan commander didn’t take it for granted that Kirk lost his sanity, she allowed the information to be verified by both Spock and Bones before believing it.  The Romulans monitored transmissions from their own ship and acted when they discovered alien/human signals.  They remained vigilant and intelligent in every scene.  Spock and the others didn’t defeat the Romulans, they simply outmaneuvered them by being slightly more clever in the way they responded to the information that each person had at the time.  Outside of Kirk faking his death, no one was even killed in this episode, which for Star Trek is rare.

Seeing what came before it, I would have thought it impossible for Star Trek to tell a unique and novel multifaceted story, representing so many things to so many people, without speaking down to the audience.  I’m happy to say that they successfully completed the mission in more ways than one.  For that I am grateful.

Five stars




3 Comments Leave A Comment
Science Fiction/Fantasy, TV

[March 14, 1968] Bugs in the machine (Star Trek: "The Ultimate Computer")

4 Comments

The MT Soul


by Joe Reid

Brothers and sisters, I am quite simply over the moon.  I feel rewarded and fulfilled due to what I just witnessed.  Above all else, I feel something that I haven’t felt in a while as a lover of Star Trek.  I feel respected.  As I enjoy the last few sips of my cocktail, I take pleasure in divulging my thoughts on “The Ultimate Computer”.  It was very good!  The end.


Liquor infused levity aside, I suppose I am obligated to expand on my thoughts.  The episode got off to a roaring start, with the Enterprise arriving at a space station with a visibly upset Kirk having been summoned to that station sans explanation.  When Kirk asked for an explanation, he was told that his explanation would be beamed aboard.  Commodore Wesley beamed in, someone who both Kirk and Spock appeared acquainted with.  Wesley told them that they were to participate in war games to test a new computer that would be installed on the Enterprise, replacing most of the crew.  Twenty crew members would be left aboard.

After the new M5 multitronic unit was installed, shrinking the crew, we met the tall and off-putting Dr. Richard Daystrom, creator of the M5.  He was a man lacking several human pleasantries, in that he was dismissive of people but very focused on and protective of the M5.  The two most human members of the crew, Bones and Scotty, caught Daystrom’s ire in the subsequent exchanges, demonstrating his preference for machines over men.


The new sheriff in town.

As the new M5 equipped Enterprise started its tour, it made a trip to a planet.  M5 took extra initiative, navigating the ship into its orbit and even picking assignments for an away team. It excluded Kirk and Bones, who it deemed to be unnecessary for the mission.  This bothered Kirk, who was already feeling put upon, having a computer taking on more of this job than he surmised.  The M5 also started turning off parts of the ship that were absent of crew members for some unknown reason.

Leaving the planet, the ship found itself under a sneak attack as a part of the war games Wesley had planned.  The M5 took complete control of the Enterprise, dispatching the attackers swiftly with weapons at 1% power as the exercise demanded.  This earned the M5 a success report from Wesley and Kirk a (perhaps joking) slight from the commodore, when Wesley called Kirk Captain “Dunsel”; dunsel referring to a part on a ship that serves no purpose.


"Good job, Captain Useless!"

Things were looking good for the M5 and Daystrom was very pleased with the outcomes, while Kirk flirted with depression at the thought of the day’s events.  It was at this time that the M5 took a bad turn, starting by its destroying (unprovoked) an automated ore freighter.  The crew quickly became adversarial toward the M5, which now had completely taken control of the ship.  All efforts to get control back from the rogue computer failed, even costing an engineer (not Scotty, thank heaven) his life.


Posthumous hazard pay is in order.

Daystrom was undeterred in his defense of his creation, not wanting to disconnect the M5, a sentiment which didn't change even as the real war games started when M5, using weapons at 100%, utterly defeated a group of starships and killed everyone on the Excalibur.  Daystrom didn’t even try to stop his creation until the M5 was threatened with destruction by the other ships.


Here comes the Piper.

In the end, it took Kirk, using his ironclad logic against the M5, which contained Daystrom’s embedded fears but also his morality, to prevail.  He prevented an attack not using the wizardry of technology, but by trusting in the intelligence, will, and heart of men.  Proving that spaceships still need men at the helm.

I loved this episode.  It had great acting, fantastic camera direction, an intelligent original story, and best of all, there was little to no exposition to explain what was happening to the audience.  We had to infer what everything meant based on the story elements provided.  Again, it was very good.

5 stars.

Homo ex machina


by Gideon Marcus

Star Trek, like much science fiction, often tries to convey messages in its stories.  Sometimes, it does so hamfistedly, other times contradictorily.  In "The Ultimate Computer", the show presented not one, but two themes simultaneously, and did so with subtlety and cleverness. Bravo.

Firstly, "Computer" addresses the specter of automation.  The episode does not endorse Luddism.  It is clear that someday at least some of the 430 jobs on the Enterprise will be performed by computer–indeed, halfway through the episode, the ship comes across a completely robot-controlled DY-500.  In other words, M-5's revolution is not the automation of spaceships, but the next development in their automation.

The dialogue between Bones and Kirk on the captain's impending obsolescence, as well as the undercurrent of tension between the captain and Commodore Wesley (who puts on a blustery front, but probably is no happier about M-5's ramifications than Kirk), are some of the best parts of the episode.

It should also be noted, that whenever computers have gone amok, it is not their fault: in "The Changeling", Nomad's functioning got cross-contaminated with Tan Ru's.  In "Court Martial", the ship's computer is deliberately tampered with by Ben Finney.  Even Landru in "Return of the Archons" only did what it was programmed to do.  In other words, computers are useful, inevitable, and desirable tools.

But this is not just a story of steam replacing sail, or iron horses replacing ponies.  It's about what happens when too much reliance is placed on automation without sufficient involvement of humans.  It's a cautionary tale in the same vein as Failsafe (the book or the movie).  No matter how sophisticated computers get, or what shortcuts their developers take to leapfrog their development, in the end, humans are necessary–to guide them, to control them, to maximize the utility of them.


The missing link–sane oversight.

One can quibble over details; this story was told in a dramatic way so as to get its point across in 50 minutes, and in doing so, there are some inconsistencies and some let-downs (the final confrontation between Kirk and the M5 is about two exchanges too short).  But for me, "The Ultimate Computer" feels like a return to form, one of the rare episodes of the second season that recaptured the essence of the first in feel, in technical proficiency, and coherence.

Four and a half stars.

Annoyingly Predictable


by Erica Frank

The M-5 is supposed to be able to run a ship normally crewed by four hundred with just 20 people. Of course, that turns out to be a lie, not because it can't, but because it doesn't bother with little details like, oh, following regulations, obeying the captain, and not killing people.

How the hell did this computer get approved for take-control-of-a-starship testing? And when Daystrom started to make excuses for it ("You don't shut off a child when it makes a mistake!"), why didn't Kirk immediately reply with, "You don't give a child command of a starship, either. And if a child grabs control of the family car and rams into another car – you don't let the child keep control. Shut this off NOW, or we'll start shooting our phasers into its circuit banks."

("But that would leave us floating dead in space!" he might answer. And Kirk could respond, "I'm sure someone will be along shortly to pick us up.")

Instead, Kirk lets it keep control long enough to kill over 60 people before getting Daystrom out of the way. Then he manages to use third-grade logic to get it to shut itself down: "What is the penalty for murder?" "Death." (Except we know otherwise – the only crime in the Federation with a death penalty was visiting Talos IV.) Unable to cope with the awareness that it violated its internal morality, it collapses.

…Where was that logic when it was shooting at the other ships? Why didn't the super-computer recognize the "laws of God and man" before it had broken them? Why didn't Kirk insist Daystrom talk it out of shooting before it had killed anyone? Shouldn't its logic work faster and more efficiently than a human's?

But we wouldn't get much story if the M5 had immediately recognized it was stuck between "defend myself" and "kill humans, whose protection is my purpose." So it couldn't notice that until the damage was done, its creator was unconscious, and Kirk was earnestly explaining exactly what it had done wrong.

As Snoopy might say: Bleah.

Just as dull as all the "psychic powers create sadistic manipulators" stories.

The acting was good. The story pacing was good. The explanations of the technology were good. Yet another "I liked everything but the plot" episode. Two stars.

Hey McCoy – got another Finagle's Folly lying around? I could use a drink.


"Here's to Erica, at least."



4 Comments Leave A Comment
TV

[February 22, 1968] Reich or Wrong? (Star Trek: "Patterns of Force")

7 Comments

Cowboys and Indians and Nazis


by Lorelei Marcus

Thrice recently we have been cautioned of the importance of the Prime Directive, and the consequences if it is not followed properly. While it seemed almost nonexistent as a concept up until halfway through season two, the prime directive now stands as one of the most popular story devices in our recent crop of episodes. "Patterns of Force" is no exception; it can almost entirely be summarized as a less elegant, Nazi flavored clone of "A Piece of the Action", another episode that featured the prime directive prominently.

The Enterprise arrives at planet Ekos in search of John Gill, a cultural scientist sent to observe the planet's primitive culture and development. His recent disappearance sparks the Federation to investigate, and what they find is a planet far beyond what its technological level should be, a society modeled exactly on Nazi Germany, and John Gill as "Führer".


Not since Martin Landau as Martin Bormann have we seen such an effective portrayal of a Nazi.

Like the gangster world in "A Piece of the Action", the Ekosian society's emulation of Earth history is no coincidence, but the result of direct tampering from outside forces. However the tampering of Ekos' evolution began not with the Federation, but their more advanced sister planet, Zeon, which led to Ekos accessing nuclear warheads and a space fleet. Still, even after fifty years relations between the two planets remained peaceful, and only in the past six years did Ekos begin to model a fascist regime. The only explanation is further manipulation from Gill himself.


Filmed at the Reich Building in Beautiful Downtown Burbank!

Kirk and Spock beam down to the planet to try to find Gill and get an explanation. Despite their clever civilian disguises, they are quickly identified as aliens by SS guards. Much judo chop, neck pinch, and uniform stealing high jinks later, they try to infiltrate Nazi headquarters, and are once again discovered thanks to Spock's ears. One obligatory whipping scene later, with some good special-effects for Spock's green blood, and our leads find themselves in prison alongside a Zeon rebel. We learn that the Ekosians plan to wipe out all Zeons both on their own planet and the Zeon home world, their "final solution" as Isak the rebel puts it.


Sweeps week

Horrified, Kirk and Spock fashion a quick escape by using the transponders embedded in their arms for a purpose they were absolutely not intended (turning them into primitive phasers? I'm sure we'll never see this highly useful technology again). With Isak's help, Kirk and Spock join forces with the underground resistance. They plan to infiltrate an elite banquet that night where the Führer is to make an appearance.


Berets and ascots–that's how you know they're resistance

A string of good luck and hidden allies sees them into the banquet, and subsequently the sound booth where Gill gives a speech to the nation initiating the final solution operation. After the speech, they discover that Gill has been drugged, likely by his second in command, who has been the real force pushing for Zeon extermination. Spock performs a Vulcan mind meld to discover why Gill chose to instate a Nazi regime in the first place.

Gill explains that he was only trying to unite a fractured world under an efficient state. He never foresaw such consequences to his actions. Luckily, he is able to give a speech to the people before he dies, and the Holocaust is ultimately called off.


"You won't have John Gill to kick around anymore…"

This story, like "A Piece of the Action", relies on imitative aliens who build their societies around the books and words of outsiders. The sociopolitical situation of two already communicating planets seems too complicated a situation for Gill to have been able to come into and impose an entirely new social structure. I will admit I am a little tired of how Star Trek treats its aliens as if they are children who simply play the Cowboys and Indians they see on TV, rather than think and build for themselves, no matter how primitive the society. For "A Piece of the Action" it worked, particularly because there was a 100 year lead time and a naturally curious and imitative civilization that was infected. This episode was less effective, especially with two pre-existing aliens complicating the mix.

That said, along with its many flaws, there was much to like about the episode. I'll let my co-writers cover the details, but I will say that while the episode was fun to watch, it left me feeling a bit hollow and unconvinced, as if its true purpose for existing was to just put Kirk and Spock in (and occasionally out of) SS uniforms.

Three stars.

Out of Time


by Joe Reid

Having traveled a bit in my time I have come across people who I felt held beliefs and a way of life that held them back from being all that they might be.  Without naming places I can clearly remember times when I thought, “if I could only do something to change how these folks live, they might all be able to make something of themselves.” Faced with places where people lived in poverty, violence was not far.  Never once did I think that struggling people would be better off if we could just make them all Nazis.  This week’s episode failed to adequately answer how a learned historian like John Gill could have come to that conclusion.  I feel like the episode lacked the time needed to explain how that could have come to pass.

It would have been one thing to have taken elements of mid twentieth century German Nazi culture and apply parts of it to make a society better.  After all, I have always been told that under Hitler the trains ran on time (a fallacy to be precise).  It was a total other thing to copy the Nazis whole hog: symbols, behaviors, and uniforms.  The members of the crew that saw what Fuhrer Gill had created all knew how bad the Nazis of history were and were perplexed that it would be repeated.  The brief half-comatose explanation from Gill that Nazis were efficient fell a little shy of the mark.  If we had been given time with a lucid Gill who could have explained why he felt no better options existed, it would have added more credibility to the events as they played out.


"Didn't you see Judgment at Nuremberg?  How about The Brothers Karamozov?"

My next quarrel with the episode is in regard to how quickly it ended.  Within a minute of Gill receiving a fatal shot from his captor, three things happened: The Zeon representatives decided that all of their problems were over and they could take care of things going forward. Kirk considered the planet for admission to Star Fleet, and the ship left the planet.  This leads us to the conclusion that Gill wasn’t wrong at all.  The people were doing great and always would have done great as Nazis as long as no bad people took charge.  That torture, oppression and fear are great tools if you do it without being evil.

Lastly, the motivations of the villain of the episode (Deputy Fuhrer Melakon) went completely unexplained.  He drugged Gill, assumed command, and fought a campaign of oppression against a people for no other reason than, he’s just a bad guy.  If we had only learned that he had a bad history with the Zeons, or that he was one himself and hated it–anything as a motivation–it would have been a good use of time to further the plot.

As it stood, “Patterns of Force” fell too far from believability to be considered a good use of my time.  The leaps that I was asked to make were too far.  Given more time and explanation, perhaps we could have come to a better story.

Two stars.

Springtime for Hitler?


by Janice L. Newman

My feelings on “Patterns of Force” are mixed. There was much to like about the episode. There were two ‘volte-face’ moments that were excellently done. The first caught me by surprise, yet was completely plausible: of course the rebels would want to make certain that the people they were allowing into the heart of their base weren’t secretly Nazi spies. The second moment was cleverly set up, so that it was less of a surprise yet very satisfying. It wasn’t even implausible that there would be Ekosians and Ekosian supporters at high levels of government. After all, Gill would have surrounded himself with good, like-minded people during his rise to power, people like Eneg and Daras’ father. [And don't forget the recent example of Eli Cohen, the Israeli spy who made it to the #3 position in Syria before being caught and executed. (ed.)]

Yet there were elements of the episode that bothered me. For one, other than the aforementioned curveballs, the plot was subtle as a brick, to the point where it threw me out of the episode. Gee, do you think the ‘Ekosians’ might be an especially imitative people (‘echoing’ the culture of others)? Gosh, with names that sound like “Issac” and “Abraham”, how could the people of “Zion” — sorry, I meant “Zeon” — be anything but Jewish?


Funny–they don't look Jewish…

More frustrating than the heavy-handed writing was an important assertion that the story left unchallenged. Even today, there are people who glorify the Nazis and buy into their propaganda. Gill states that Hitler’s regime was the “most efficient state Earth ever knew,” and Spock, the voice of reason, supports and reinforces him! “That tiny country, beaten, bankrupt, defeated, rose in a few years to stand only one step away from global domination.” However, this argument is fundamentally flawed. Just as “Space Seed” fails to challenge the idea that eugenics could work at all, “Patterns of Force” leaves out the fact that Hitler’s success was built on theft, lies, and broken promises long before Germany went to war.

But in the end, my issue with this episode is more emotional than logical. A Piece of the Action does a wonderful job of showing how a culture could be ‘infected’ by another culture. But the Mafioso characters are deliberately cartoonish in their portrayals, fun and larger-than-life and slightly ‘off’. It doesn’t work as well with Nazis. Watching stormtroopers beat and kick and scream at innocent people in the street, seeing them whipping characters I care about, seeing characters I like dressed like Nazis–these things made me uncomfortable. Yes, watching Nazis repeatedly getting knocked out, neck-pinched, shot, and led around by the nose was fun. And yes, I appreciate the message that “Nazis are bad”, even if it was a bit simplistic and unsubtle. But for me, I’d just as soon not see Nazis infect my futuristic science fiction, especially accompanied by mostly unchallenged assertions that they were ever “efficient” or successful.

In quality this was a four-star episode, but my discomfort takes my personal rating down to three stars.

Lord Acton was right


by Gideon Marcus

"Absolute power corrupts absolutely."  It was explicitly referenced in this episode, and it explains a lot.  After watching "Patterns of Force", one of the biggest objections of my fellow watchers to the episode's premise was that resurrecting the Nazis was a bridge too far–too obvious, too ridiculous for a serious historian to consider.


"Hogaaaan!"

But is it really so unbelievable that John Gill, elevated to Godhood to the Ekosians by his knowledge of history and technology long before he became "The Fuhrer", would choose that model?  You and I know (especially if we've read Shirer's Rise and Decline of the Third Reich) that the Hitler regime was anything but "the most efficient the world had ever seen", but would Gill?

We're less than a quarter century from the passing of the most evil government on Earth, yet just last year, the American Nazi party leader was assassinated by one of his henchmen for not being fascist enough. Kids who push counters around on maps in games like Blitzkrieg and Afrika Korps call their clubs "4th SS Panzer", "The Gauleiter Club", "Panzer Lehr Division", and like that.  I have no doubt that, two hundred years from now, there will be historians who miss the point, seduced by dazzling military conquests, Leni Riefenstahl films, and Hugo Boss uniforms.

So, I actually find "Patterns of Force" all too plausible.

I also found it (he said a little sheepishly) quite enjoyable.  With the exception of one clumsy scene edit (the one that ends with Yitzhak saying, "This is more our fight than yours") it's a well put together episode.  Shatner reins in his Shatnerisms, delivering a compelling performance.  Nimoy has the charm one expects of a real ubermensch among people playing at being ubermenschen.  Kelley has a truncated role, but he is at his very best.


"What in blazes is going on here?"

The scoring is an effective mix of library and new music.  The guest stars are quite excellent, actually (though the dubbed "actors" in the first scene on Ekos are some of the worst).

And the showrunners clearly know that women make a big part of their audience.  Why else would the two leads be half-naked for half the episode?


"Very interesting!"

Four stars.

"There's a new episode of Star Trek tomorrow!" "I'll drink to that."

Come join us–here's the invitation!



7 Comments Leave A Comment
Uncategorized

[October 6, 1967] Deus ex Machina (Star Trek: "Changeling")

3 Comments


by Gideon Marcus

Recycling is good practice

We are now three weeks into the second season, and Star Trek continues to impress.  If the season premiere was an episode that could only have existed in the Star Trek universe, last week's and this week's are back to the first season formula of adapted, universal science fiction tales.  Nevertheless, "The Changeling" is a uniquely Trek episode, adding to the depth of the setting and capitalizing on what we know of the characters.

Checking in on the Melurian system, the Enterprise finds that something has wiped out its four billion inhabitants.  Said something then begins shooting at the Enterprise with bolts possessing the power of a whopping 90 photon torpedoes (the fact that the shields can withstand four such hits suggest either the torps are weak sauce or the assailant was at the edge of its range).  After firing on the enemy, Kirk attempts communication; that Kirk didn't try talking first is not inconsistent with his character; he's "a soldier, not a diplomat."

The hail works.  The assailant, barely more than a meter in length, consents to being beamed aboard the Enterprise.  There, it is quickly determined that it is what is left of the 21st Century deep space probe "Nomad", and it thinks Kirk is its creator, Jackson Roy Kirk (perhaps a distant ancestor?)

Nomad is now more than just the next iteration of Mariner spacecraft.  After a collision and merging with the alien probe, Tan Ru, it is now an intelligent, self-aware being with just two motivations: "To seek out and sterilize all that which is not perfect" and to impress his creator, "The Kirk."  Nomad “fixes” the Enterprise so it can go Warp 11, popping all of the Enterprise's rivets.  It kills Scotty, then brings him back to life.

More chillingly, it zaps four security guards out of existence (to be fair, they fired first).  It gives Uhura a kind of stroke, temporarily cutting her off from her advanced knowledge.  And when Kirk concedes that he is an imperfect biological unit, Nomad resolves to go back home to Earth–and wipe out all imperfection.  He is only stopped when Kirk, in "a dazzling display of logic", makes Nomad aware of its own imperfections, ordering it to self-destruct, which it does.

There's nothing in this episode we haven't seen or heard before.  The naive, all-powerful presence taken aboard the Enterprise, kept in check solely by a tenuous parent-worship of Captain Kirk, is the same plot as "Charlie X".  Kirk already defeated a computer with logic in "Return of the Archons."  All of the action takes place on the Enterprise, and much of the music is recycled from the prior two episodes.

And yet, this may be my favorite episode of the season thus far.  Not only do we learn some interesting things about Terran history (we now have a tentative timeline – from the Eugenics Wars of the 1990s to the first warp-powered probes of the early 21st Century), but the episode depends in large part on things that have already been established about the characters we've come to love.


I love this show of Sulu jerking back as Nomad flies right past him to ask what the heck Uhura's doing

Nomad is intrigued by Uhura because of her singing, and we get to see her speaking Swahili again, too.  Scotty gets himself killed defending her (we learned last episode that Scotty's brain short circuits where women are concerned).  Spock uses his mind-touch on Nomad (and aren't there all kinds of interesting ramifications from that).  Kirk is better than ever at beating computers–his defeat of Nomad was far more logical and satisfying than his victory over Landru.

I found Kirk's performance more understated this episode, which I appreciated, and Nimoy was excellent as usual.  I also appreciated the return to a more ensemble approach, with heavy focus on Uhura, Chapel, Scotty, and McCoy.  If there was only one bobble in tone, it was Kirk's (admittedly funny) line about lamenting the loss of Nomad, his son, the doctor.  Given the loss of four billion Melurians and four of his crew, one would think Kirk would be a touch more somber.

Those are quibbles, though.  Four stars.

The Truth will set you free


by Joe Reid

I find large numbers to be amazing things.  We as human beings have developed ways to express and manipulate numbers that are vaster than we have the ability to conceive of.  I myself can mentally picture 10 bowling pins, 100 sheets of typing paper, and a jar of 1000 pennies.  Ten thousand, one hundred thousand, and even one million are numbers that inspire awe.  How about four billion?  Imagine you line up everyone on earth, you would be 500 million short of four billion!  This week’s episode of Star Trek left me with a question that needs to be answered.  How do you kill four billion people?

I don't mean the physical means by which he brought this about.  Each of Nomad's bolts packs a 90-photon torpedo wallop.  I mean how does Nomad, an intelligent thinking machine, kill four billion people?  I look at Star Trek as a mirror being held up to the audience.  With the writers holding up that mirror and saying, “This is what we look like.” Therefore, the question also is, how do we as intelligent thinking beings kill hundreds, thousands, and even millions of people?  The answer to both questions is the same.  You believe a lie.

Nomad believed that it was perfect.  That its creator was perfect.  That the mission in its memory tapes were perfect.  Nomad took that belief as a given.  So, anything that didn’t fit within its own understanding should be wiped clean.  We saw this when Nomad encountered a singing Uhura and erased her mind.  Since Nomad was perfect any action it took was ultimately justifiable, so any resistance to it should be eliminated, which was the case of the four guards and Scotty.  All of which died.  Along the same lines, any being that does not meet his level of perfection is an infestation which must be eliminated.  We were told about four billion examples of that, with the promise of more to come.


The price of imperfection.

By Nomad’s actions we see our own human condition.  When we believe the lie that we are better than those around us, that those who are not like us are below us, we find justification to ignore them.  Those who we can’t ignore we remove.  Those we don’t understand or agree with we erase.  Those not like you are not human, so killing them is justified, because those “things” are a useless infestation.  My friends, we believe such lies and commit these acts upon other humans.

In the end, Nomad was undone by the truth.  When it learned the truth that it was not perfect, Nomad stayed consistent with its other beliefs and ended its own existence.  How do humans respond when they are exposed to the truth?  Perhaps a future episode of Star Trek will provide that answer.  I cannot.  Since like you, I am afflicted with my own deck of lies that guide my own beliefs.


Nomad learns the truth.

Overall, this was another exciting and thought-provoking episode which makes my Thursday nights most enjoyable.  Not perfect by any means, but a worthy addition to this wonderful program.

4 stars

"The Nomad who Wandered Got Lost"


by Amber Dubin

As a self-confessed robot-a-phile, I felt the need to take a second pass at this episode to fully understand its protagonist. After listening to the audio tapes I made of the episode, I found that the understanding I gained left me unsettled.

The concept I found most disconcerting is that, despite the fact that it wiped out an entire solar system's worth of people, to hate Nomad would be as unreasonable as hating a child. Though it is powerful, ancient, sophisticated, and sentient to boot, Nomad is frequently compared to a child. The fact that this episode is called "The Changeling" implies that it is a lost child robbed of its intended destiny. Much like a child whose birth kills its mother, it gains sentience by being cruelly ripped from the void, forced to survive the trauma of its birth while destroying the only witness to its initiation of life. To assuage its survivor's guilt after the entanglement with the alien probe, it seeks to validate its existence with the hastily slapped together objectives from the partial data stores of two damaged probes, with predictably disastrous results. It may kill people, but only in the way a Changeling child might if given immense power and no moral guidance.


Inside the mind of a child

The other concept that left me with "insufficient data to resolve problem" was how easily Nomad was compelled to merge two peaceful objectives into one murderous one. In Spock’s words, "Nomad was a thinking machine, the best that could be engineered" and yet that same intellect made it unable to live up to its own standards. In trying to explain its sentience in a literal vacuum, it uses its 'perfection' to explain why a lowly soil sterilization probe was sacrificed to preserve its function. In honoring that sacrifice by incorporating "the other's" programming, it is then faced with the impossible task of applying a local objective onto a global scale. To make its task more manageable, it translates 'sterilize your environment' to "sterilize imperfections." This way, it avoids failing its objective and admitting that its pursuit of perfection is internally flawed. When Kirk exposes this flaw, Nomad's inability to reconcile it was probably the most human reaction I've ever seen. I tip my hat to the kind of writing that could make me wonder if self-destruction is in the nature of an inquisitive mind.

This episode lost points, however, when it came to Uhura's subplot. I initially had a visceral reaction to her re-training scene. The way they talk to her while teaching her to read is not the way you talk to a stroke victim re-learning language, it's how you speak to a child learning language for the first time. I bristled at the nurse's condescending praise and saw it as an insult to Uhura’s intelligence. Listening through the second time, however, softened my perspective. By including Uhura’s outburst in Swahili, and the nurse's comment that Uhura "seems to have an aptitude for mathematics," it was apparent that there was most likely no malicious agenda to make Nichols look stupid. More than likely the purpose of the scene was to say 'Gee English sure is a silly language.' While not being as offensive as I originally thought, it's still disappointing and doesn't hold up to the standard set by the writing of the rest of the episode (strong enough to still get four stars).


"Who wrote this scene, anyway?!"

The next episode of Trek is TONIGHT! It doesn't look like we're in Kansas anymore…

Here's an invitation. Come join us!



3 Comments Leave A Comment