Star Trek 2009: The 13 Biggest Mistakes in J.J. Abrams' Reboot, Ranked

Star Trek 2009 made Star Trek feel like an event again. It was fast, exciting, funny, and beautifully cast, and it introduced an entirely new generation to Kirk, Spock and the Enterprise. Without this movie, there is a very good chance Star Trek never becomes the massive streaming franchise it is today.

But it also made some enormous mistakes. The more you think about its story, its villain and the timeline it created, the more parts of this movie begin falling into the cracks. Some are harmless shortcuts. Others fundamentally misunderstood what made Trek work. I like this movie. I think it is incredibly entertaining, but as I see it, "entertaining and intelligent are not always the same thing." Here are the 13 biggest mistakes, counted down from least damaging to most.

13. The lens flares attack the Enterprise bridge in every scene

There are so many lens flares in this movie that watching it occasionally feels like somebody is attacking the television with a flashlight. J.J. Abrams wanted the future to feel bright, energetic and slightly chaotic, and I understand that visual reasoning. The problem is the effect appears on the bridge constantly, during conversations, sometimes directly across a character's face.

It does not make the Enterprise feel futuristic. It makes the Enterprise feel like it was constructed inside a lighting showroom. Abrams himself later admitted the lens flares became ridiculous, essentially conceding in hindsight that the film did not need quite so many streaks across Kirk's forehead. This is the smallest mistake on the list because it does not damage the story, but it did become the defining visual joke of the entire Kelvin timeline.

12. The Enterprise becomes comically huge for no reason

The original Enterprise was already an enormous starship, but the 2009 movie decided it needed to be the size of a small city. Depending on which official measurement you use, this version runs around 725 meters long, making it considerably larger than the Enterprise D. The ship does not need that scale for the story, and most of the interior still feels like ordinary corridors, rooms and engineering spaces.

Making it gigantic does not create wonder, because the movie never gives a meaningful sense of space to back it up. It plays like someone looked at the original dimensions and simply doubled them because audiences like bigger things. The Enterprise should feel impressive because of what it represents, not because the scale was cranked up until it surpassed Picard's ship.

11. Engineering looks like a brewery bolted onto a spaceship

The bridge looks polished, bright and expensive. Then we enter engineering and discover the Enterprise is apparently powered by industrial pipes, metal tanks and what looks like a beer distribution facility. Much of the engineering set was in fact filmed at a real Budweiser brewery in Van Nuys.

Using real industrial locations can make a ship feel grounded, but nothing about this environment matches the rest of the Enterprise. The bridge belongs to a sleek 23rd century starship. Engineering looks like Kirk wandered into a processing plant. The ship's interior has no consistent visual language, and it feels like two entirely different productions were welded together.

10. Kirk goes from cadet to captain of the flagship in one afternoon

Kirk begins the story as a reckless civilian. He enrolls in Starfleet, spends three years at the Academy, cheats on the Kobayashi Maru, and gets suspended. Then Nero attacks Vulcan. Kirk sneaks aboard the Enterprise, gets thrown off the ship, returns again, helps stop the threat, and is immediately given command of Starfleet's newest flagship.

Not promoted to ensign, not assigned as a junior officer, not even made first officer under an experienced captain. He goes directly from suspended cadet to captain. Starfleet apparently lost every qualified officer in the organization during one battle. Kirk absolutely proves his courage and instincts, but that does not prove he is ready to manage hundreds of people and represent the Federation across the galaxy. At the very least, give the man a performance review.

9. The entire crew assembles through an aggressive chain of coincidences

The movie had to get Kirk, Spock, McCoy, Uhura, Scotty and Sulu together fast, and it does this through a chain of coincidences so aggressive that destiny practically becomes a character. Kirk meets McCoy on the shuttle. Uhura happens to overhear the Romulan transmission. Sulu happens to replace the original pilot.

Kirk gets launched onto the exact planet where old Spock is stranded, then walks into the exact cave where Spock is hiding. Spock then takes him to the exact outpost where Scotty happens to be stationed. At some point it stops feeling like fate and starts feeling like the universe is physically shoving the cast into their assigned seats. Coincidence can begin a story, but it should not solve every logistical problem inside it.

8. Nero waits 25 years and does almost nothing with an advanced ship

Nero arrives in the past, destroys the Kelvin, then spends approximately 25 years waiting for Spock. That sounds intimidating until you ask what he was actually doing for all that time. Deleted scenes explain that Nero and his crew were captured by the Klingons and imprisoned on Rura Penthe before escaping, which at least fills the enormous hole in the timeline.

The finished movie removes that explanation. As presented on screen, Nero simply disappears for a quarter of a century and then conveniently returns when the plot needs him. He has an advanced ship from the future, knowledge of major historical events, and an entire crew of Romulans, and apparently uses none of it until Spock arrives. You cannot remove the explanation for your villain's 25 year absence and act like nobody is going to notice.

7. Nero's revenge plan makes zero logical sense

Nero blames Spock and the Federation because a supernova destroyed Romulus. His rage toward Spock is understandable on an emotional level, since Spock promised to save Romulus and failed to arrive in time. But Nero travels into the past more than a century before Romulus is even destroyed and decides his solution is to annihilate Vulcan and Earth.

These people did not destroy Romulus. This version of Spock never met Nero. The Federation he attacks has zero knowledge that the supernova will even happen. Nero has access to the past and information that could potentially save his planet, mourn the Romulan Empire, or prevent the disaster completely. Instead he spends his one shot murdering people who had nothing to do with it. Grief can make somebody irrational, but Nero's entire plan actively prevents him from accomplishing the one thing he claims to care about.

6. Red matter does whatever the script needs it to do

Red matter may be the most convenient substance in Trek history. One drop can create a black hole. A larger amount can apparently destroy a planet. It can absorb a supernova. It can send ships through time, and it stays contained in a glass sphere that looks like it was purchased from a hobby shop.

What is red matter? How does it work? Why did Spock bring enough of it to destroy every planet in the Federation when he apparently needed one drop? The movie never explains, because red matter is not really technology, it is a plot button. Whatever the writers need, a planet destroyed, a ship consumed, a timeline altered, somebody pokes a little red ball and the story moves forward. Trek has always used imaginary science, but the best technobabble establishes rules, and red matter has none beyond simply not thinking about it too hard.

5. Spock and Uhura's relationship arrives fully formed from nowhere

I am not against Spock and Uhura as a couple, and there are even moments in the original series that can be read as slight flirtation. The problem is this movie does not develop the relationship, it just reveals that it already exists. Uhura demands assignment to the Enterprise, Spock changes their orders, and they kiss in the transporter room.

Suddenly the audience has to catch up with a romance that apparently developed offscreen. Their relationship creates some interesting moments, especially after Vulcan is destroyed, but the movie never shows why these two people were attracted to each other or how they navigated a relationship between an instructor and a cadet. It feels less like a natural extension of their characters and more like the writers wanted a surprising romance.

4. The Kobayashi Maru test misses the entire point of the original story

Kirk cheating the Kobayashi Maru is one of the most famous pieces of Star Trek history. In the established version, he refuses to accept a no win scenario, reprograms the test, and receives commendation for original thinking. The 2009 movie turns that legendary story into a joke, with Kirk openly acting bored and installing a cheat so obvious that everybody immediately knows what happened.

He does not outthink the scenario, he effectively activates god mode. Kirk and Spock could have debated whether leadership means accepting death or challenging the assumptions that make defeat inevitable. Instead the hearing exists mainly to put Kirk in a room when Vulcan sends its distress signal. The movie creates an iconic piece of Kirk's history but misses all the intelligence that actually made it iconic.

3. Vulcan's destruction happens far too quickly to register

Destroying Vulcan is the boldest moment in this movie. Six billion people die, Spock loses his mother, the Vulcan species becomes endangered, and the entire direction of the timeline changes forever. That should be devastating, but the movie barely gives us time to process it. Vulcan collapses, Spock watches Amanda fall, the Enterprise escapes, and almost immediately the story moves toward the next argument and the next action sequence.

The destruction becomes fuel for Spock's emotional breakdown, but the larger tragedy disappears into the movie's momentum. We do not see the Federation react. We do not feel the scale of six billion deaths. We do not spend enough time with the surviving Vulcans. The film blows up one of the most important planets in Trek history and treats the aftermath like it did not even matter.

2. Spock Prime becomes the movie's easy button for every problem

Leonard Nimoy's return is genuinely great. Seeing him as Spock again gives the movie emotional legitimacy and directly connects the Kelvin timeline to everything that came before. But Spock Prime also becomes the movie's emergency solution to every problem. He explains Nero, he explains the alternate timeline, and he tells Kirk that he must become captain.

He gives Kirk the emotional strategy required to remove young Spock from command. He leads Kirk to Scotty and hands him the future formula for transport beaming. He even encourages young Spock to remain in Starfleet so the original crew can come together. At that point Kirk did not create his own destiny, the older version of Spock is arranging the timeline until it resembles the one he remembers. It is satisfying fan service, but it takes agency away from these new characters.

1. It was ashamed to be Star Trek

This is the mistake that affected everything that came after. Star Trek 2009 wanted the characters, the uniforms, the names, the ships, all of it, but it seemed terrified that audiences might associate it with slow conversations, diplomacy and complicated science fiction ideas. So it transformed Trek into a modern action blockbuster, with Kirk hanging from ledges, cars flying off cliffs, planets exploding, and ships firing hundreds of weapons.

None of that is automatically bad. Trek can be exciting. The Wrath of Khan has action, First Contact has action, Deep Space Nine delivered some of the largest battles in the franchise. But those stories used action to support ideas and characters. Star Trek 2009 often uses familiar characters to support the action. The movie rarely asks the crew to solve a problem through diplomacy or collective reasoning.

It introduced millions of people to Star Trek, but it also taught studios that Trek needed to resemble every other blockbuster to survive, and that mindset followed the franchise for years, with bigger threats, faster pacing and more destruction. As I see it, "the greatest mistake that I think the movie made wasn't changing the timeline. It wasn't even destroying Vulcan or turning engineering into the brewery. It was believing Star Trek needed to be embarrassed by the qualities that made it Star Trek."

It is a complicated legacy. It resurrected the franchise, gave us an excellent cast, and introduced Trek to an entirely new audience that proved Kirk, Spock and the Enterprise still mattered. But it also created a version of Trek that never really figured out what to do after the excitement wore off. I enjoyed the movie, it moves incredibly well, the cast had immediate chemistry, and Michael Giacchino's score is one of the best things to come out of modern Star Trek. But when you look beyond the spectacle and the lens flares, the cracks are everywhere.

Is Star Trek 2009 a great Star Trek movie, a great action movie wearing a Star Trek uniform, or somewhere in between?