Vader47000

3rd Jan 2010

Star Trek (2009)

Corrected entry: Before dropping out of warp near Vulcan, Pike orders Enterprise to red alert and its shields up. He's acting on a hunch from Kirk that the planet is being attacked. First, the ship's sensors should be able to detect the wreckage in orbit, but that would negate the drama of dropping out of warp amid the debris. Second, the shields should protect the Enterprise against the floating hunks of metal, yet several bounce off the Enterprise hull, and a destroyed saucer section of another ship scrapes the Enterprise nacelle and damages it as if the shields were never up. Shouldn't the debris bounce off the shields? As is typical for the Star Trek franchise, the effectiveness of the shields is only as strong as dramatic license permits.

Vader47000

Correction: Historically, the shields have generally not protected the Enterprise from large, slow moving debris. They are designed to protect against energy based attacks. The shields would not prevent the Enterprise from slamming into another ship, for example.

wizard_of_gore

3rd Jan 2010

Star Trek (2009)

Corrected entry: In his attempt to rescue the Vulcan leadership, Spock beams down to the planet, then has to run up the side of a mountain to reach the sacred cave. Later we see there is plenty of room just outside the cave entrance to stand to be beamed out. Why couldn't Spock just beam to the mouth of the cave and save himself the precious time of having to run up the mountain?

Vader47000

Correction: Sure, there's plenty of room outside the caves. But it would also be a very precarious position to beam in, as there were many rocks coming down the unstable mountainside. Spock was probably beamed a reasonably safe distance away to avoid being pummeled by a falling rock.

JC Fernandez

28th Dec 2009

Star Trek (2009)

Corrected entry: Old Spock seems to know that it is 2258. Yet he assumes Kirk should be in command of the Enterprise by then. In the prime universe Spock is from, Kirk doesn't become captain until 2265. And if Spock is simply suggesting that Kirk could be captain now, his knowledge of Starfleet should tell him otherwise.

Vader47000

Correction: Old Spock apparently was never told what year it is by the Romulans; he only knows that it is some time in the past. He obviously thought it was 2265 or later.

BocaDavie

28th Dec 2009

Star Trek (2009)

Corrected entry: Despite the Kelvin supposedly existing in the pre-Nero Prime universe, it displays design characteristics more in line with the Abrams rebooted universe concept, such as a window on the bridge instead of a viewscreen, an irregular warp nacelle configuration and an engineering section that looks like a factory.

Vader47000

Correction: Since we've never before seen a starship from the Kelvin era, this conclusion is exclusively based on supposition. Whatever happened in the original timeline to alter the design aesthetic simply didn't occur in the altered timeline and so things from the Kelvin-era ships carried over to the rebooted Enterprise.

JC Fernandez

28th Dec 2009

Star Trek (2009)

Corrected entry: After encountering the Narada, the Kelvin receives a transmission from one of Nero's crewmembers instructing the Captain to fly over. Remember, the Kelvin pre-dates the divergence in the timeline, and in the prime universe, no human or Romulan had seen the other until more than 30 years later. So the Kelvin should have assumed the man was a Vulcan and asked questions accordingly, such as, "If you're Vulcan, why attack us?"

Vader47000

Correction: Because the Captain's not stupid. He knows Nero is not a Vulcan. Pointy ears do not a Vulcan make. He may not know what race Nero is, but he doesn't need to know much about him to see that he's not friendly.

Phixius

28th Dec 2009

Star Trek (2009)

Corrected entry: The Kelvin computer tells George Kirk that the auto-pilot is disabled, leading him to decide to remain behind. He fires the ship's weapons to protect the escaping shuttles. Once the shuttles are safe, the status display shows that weapons are offline. Kirk sets a collision course and then sits in the captain's chair for a couple of minutes and does nothing else but talk to his wife and await his death. If there's no auto-pilot, how did he program the collision course and why would the computer follow it? Shouldn't he have to be at the helm flying the ship manually? And if not, why isn't he trying to get to an escape pod? According to the readout, he has at least a minute.

Vader47000

Correction: You've answered your own submission with one of the MANY questions you've included. Regardless of the weapons now being offline, so long as Kirk remains at the helm, he can adjust the course of the ship if the Nerada alters its course to intercept the escape pods, so no matter what time he has left, he has to stay at the helm. The computer merely warns him of the collison, clearly with the auto-pilot being offline is in part why the computer cannot alter course to avoid the collision. Your submission would have been better separated, and most of it should have been submitted as questions.

GalahadFairlight

28th Dec 2009

Star Trek (2009)

Corrected entry: Nero's drill interferes with both transporters and communications. Yet when Kirk, Sulu and Olson space-jump to the drill, the Enterprise can read their telemetry data and the trio can provide verbal updates.

Vader47000

Correction: The drill interferes with long-distance *subspace* communication, hence their inability to contact Earth (as well as why they didn't receive a warning from the ships that arrived first). Clearly it doesn't disrupt all communication as Nero is able to contact the Enterprise. As for the telemetry readings, that could be patched via the suits' communication system. In other words, the readings could be coming from Kirk and co's suits, not from the ship's sensors. Even if they are readings from the ship's sensors, establishing coordinates is the simplest part of the transporter system, but not the only thing needed in order to successfully beam in or out. It's been long established in Trek that you can't beam onto a shielded ship, despite having telemetry readings as to the other ship's location.

JC Fernandez

Join the mailing list

Separate from membership, this is to get updates about mistakes in recent releases. Addresses are not passed on to any third party, and are used solely for direct communication from this site. You can unsubscribe at any time.

Check out the mistake & trivia books, on Kindle and in paperback.