Columns > Published on June 4th, 2013

The Absence of Story in "Star Trek Into Darkness"

By now you've no doubt seen Star Trek: Into Darkness. If not, read no further, for here there be SPOILERS. I would warn you that I will be discussing the movie in detail and might possibly give away aspects of the story, but that is a singularly unnecessary concern with this film. As cinematic adventures go, it is sufficiently fun and exciting, but it fails to delve deeper into the story, which is something Star Trek should always endeavor to do. While it bears the brand of a franchise best known for being about exploring the unknown, the latest installment from Abrams is content to boldly go where many movies have gone before.

Into Darkness may take place on a ship called Enterprise, with characters named Kirk and Spock exchanging comic quips, but its similarity to Star Trek ends there. All opportunities for storytelling presented by my favorite fictional universe are paved over to facilitate the delivery of big action set pieces. I'll admit that I've wanted to see a Star Trek action movie ever since I was twelve years old, and I finally got it. In 2009. Unfortunately, the sequel steadfastly refuses to explore any new frontiers it encounters.

In the only scene that truly felt like Star Trek, Kirk and crew are trying to save a Stone Age civilization from being wiped out by a volcano without exposing themselves. Although the Prime Directive, Starfleet’s sacred non-interference clause, prohibits it, Kirk reveals the ship in order to rescue Spock. And for a second, it almost looks like Kirk is in big trouble. An admiral is yelling at him after all, and he loses his command for almost five whole minutes. Instead of exploring what effects this could have, why the Prime Directive is important and how it came to be, and thus possibly learning something about the society that would view such a rule as necessary, the Enterprise's profound impact on a primitive civilization is played as nothing more than a joke. The expansion of knowledge, that sacred cow of Star Trek, is not given any priority and only the barest of attention in this story, so something else explodes and Kirk is given the Enterprise again so he can warp to the next action scene on far away Kronos, the homeworld of the feared Klingons.

While this would have been the perfect chance to learn more about one of the more robust and beloved alien cultures in the history of the show, the Klingons are merely there so Khan can demonstrate what a badass he is by killing them all. Sadly, the shameful practice known as Worf-beating continues. After Khan’s anti-climactic capture, Kronos is left behind and its inhabitants are not seen again. I couldn’t help but wonder how much more interesting the story could have been if they had stayed on Kronos, with Khan himself trying to ignite the war between the Federation and the Klingons. It would have been more interesting than yet another race to rescue an imperiled Earth from vengeful madman.

I couldn’t help but wonder how much more interesting the story could have been if they had stayed on Kronos...

Which brings us to the biggest missed storytelling opportunity in the whole movie: Khan himself. Other than constantly reminding us how dangerous he is, the movie tells us very little about its most intriguing character. When he finally reveals his true name, there's a bigger reaction from the audience than from Kirk. Which is not just a missed opportunity, but doesn't make any sense. This would be like finding out the Navy had revived Hitler to help them plan the war on terror, but no one on the Enterprise seems to have the slightest idea who Khan is, or the inclination to find out, which also calls into question why his identity had to be kept secret in the first place. Khan is a literal link to their past, the epitome of what humanity used to be like: a genetically engineered super soldier turned conqueror, willing to do anything to achieve his ambitions. Kirk represents the future, a member of a human race so enlightened that he would hesitate to kill even a mass murderer. Khan's brief stay in the Enterprise's brig presented the perfect chance to study the contrasts between protagonist and antagonist, possibly learn how the decidedly divided world we are now will some day become the cornerstone of the United Federation of Planets, but it is allowed to pass with little remark.

You might find yourself saying: "Sure, there could have been more story, but did it really hurt anything?"

Oh, most certainly, hypothetical reader. If you are lazy in your storytelling, you might not end up telling the tale you think you are. For example, if you didn't know anything about Star Trek before seeing Into Darkness, it would be easy to get the impression that Khan is really the tragic time-displaced hero, struggling to save his family from an oppressive, inhumane future regime.

Let's look at the most compelling story in the whole movie. For the first twenty minutes we watch a couple despairing for their very ill daughter. The young Starfleet officer played by Noel Clarke conveys the pain and frustration of a father forced to endure his child's suffering despite the miracles of 23rd century medicine with only his eyes and a handful of words. When Cumberbatch's enigmatic villain offers to save her life, we already know that this man will do anything to save his daughter, like blow up a building that may have been a library or a top secret research facility, depending on who you ask. Thus we are introduced to the dominant theme of the movie: the lengths one is willing to go to for family. This theme is reinforced later when Kirk breaks the Prime Directive to rescue Spock, and then also volunteers for a mission to terminate the slayer of his surrogate father figure with extreme prejudice. By this measure, no one is a more devout family man than Khan.

All of the terrorist acts Khan committed were to free his people from the regime holding them hostage. He says they were unjustly condemned as war criminals, and the only person to contradict this is the corrupt admiral that defrosted him to design weapons for a war he was planning to start. Even when Spock calls his future self to get the scoop, his older counterpart merely recounts the obvious: Khan is very dangerous. But the only reason Khan is dangerous is because Kirk intends to hand him over to be tried and judged by the same people who forced him to build WMDs by threatening his family. In fact, there is nothing in the movie to condemn Khan other than actions he took under duress in order to save his family. In another film, Khan would be the steadfast, indefatigable hero who will stop at nothing to protect those he loves. We would root for him. By the end of the movie, I pretty much was. Is Khan really the bad guy here, or is Starfleet?

While plots will always have holes and even the most well-developed characters can go off-script, it is important to keep such things at a manageable level, where they can easily fit under a reader's suspended disbelief. But lazy storytelling is not so easily fixed or forgotten, because readers will fill the void with a story of their own. Remember that scenes where people talk aren't just filling space between the big shoot outs: this is where you tell your reader what the story is about. If you can't be bothered, don't be surprised if they come up with another one.

About the author

BH Shepherd is a writer and a DJ from Texas. He graduated from Skidmore College in 2005 with degrees in English and Demonology after writing a thesis about Doctor Doom. A hardcore sci-fi geek, noir junkie and comic book prophet, BH Shepherd has spent a lot of time studying things that don’t exist.  He currently resides in Austin, where he is working on The Greatest Novel Ever.

Reedsy Marketplace UI

1 million authors trust the professionals on Reedsy. Come meet them.

Enter your email or get started with a social account: