Star Trek Beyond is out, and as the trailers for the film indicate, Captain Kirk’s USS Enterprise does not have a good go of it in the film. Faced with an unprecedented attack by alien forces, Kirk and his crew must take refuge on a nearby planet. As for the ultimate fate of the vessel, I’ll leave it to the reader to go check out Star Trek Beyond for themselves. But whatever the case, this is far from the first time that the NCC-1701 (or any of her descendants) faced possible destruction.

Loading

So let’s take a look back at the history of Enterprises getting blown up real good. Some of these examples come from alternate timelines or possible futures, but they all have one thing in common: The flagship of the Federation going out in a blaze of glory. Let’s make sure that history never forgets the name… Enterprise!

<em>Original Enterprise</em><br>Star Trek III: The Search for Spock

<em>Possible

“Time Squared”: Six hours in the future is a bad place to be for the Enterprise.

<em>Enterprise-C and Alternate Timeline Enterprise-D</em><br>The Next Generation, “Yesterday’s Enterprise”

Loading

<em>Time Loop Trapped Enterprise-D</em><br>The Next Generation,

Groundhog Day for the Enterprise

<em>Time Frozen Enterprise-D</em><br>The Next Generation,

Getting timey-wimey blown up and then un-blown up in "Timescape"

This is the original -- and the only truly iconic -- death of the Enterprise. William Shatner’s Captain Kirk, desperate to save his crew and his best friend Spock -- miraculously resurrected after the events of the previous film -- must activate the auto-destruct sequence of his beloved ship, pulling a classic Kirk move in the process as he outwits his Klingon adversaries. “Code zero, zero, zero. Destruct. Zero!” he spits out, activating the oft-teased, never-before-used device. As the Klingons beam onto the Enterprise to take command of her, Kirk’s gang beams off, and moments later the ship blows itself to hell.In this not so great second-season episode of TNG, a Picard from six hours in the future arrives on the Enterprise of the present warning that the ship will be destroyed… you guessed it, six hours from now. This gives the crew time to figure out what the heck is going on and avert the tragedy, though they’re less successful in understanding why this Picard from beyond is such a wuss. It also gives Patrick Stewart the chance to shoot and kill Jean-Luc, which is no doubt something he’s wished he could do many times over the years.In one of the greatest Star Trek episodes ever produced, “Yesterday’s Enterprise,” the arrival of a previous Enterprise -- the NCC-1701-C -- from the past causes history to be altered, resulting in Captain Picard and his crew living in a galaxy torn apart by war between the Federation and the Klingons. The Enterprise-C, the predecessor to Picard’s ship, was believed destroyed years earlier while protecting a Klingon outpost on Narendra III against a Romulan attack. Though the C’s Captain Rachel Garrett and her crew were thought to be killed, their act of sacrifice while protecting the Klingons was a key step in achieving peace between the Federation and the Klingon Empire.But when the C slipped through a wormhole into Picard’s present, history was changed and that peace never happened. In order to restore the timeline to its proper (less horrible) place, the C must return to certain doom in the past while this alternate Picard and his crew sacrifice themselves as well, making sure their sister ship can escape to its preordained fate. And this is where Picard utters his immortal “Let’s make sure that history never forgets the name… Enterprise!” line. So great.Often referred to as Groundhog Day, Star Trek style, this TNG yarn is a trippy variation on that Billy Murray classic (though it should be noted the episode predates the film by a year!). “Cause and Effect” starts with the Enterprise in the midst of an alarming catastrophe that culminates in its destruction. But after the opening credits, we return to a seemingly fine Enterprise… which is again destroyed by the first act break. This happens again and again, as it becomes clear that the ship -- unbeknownst to the crew at first -- is stuck in a time loop. Of course, thanks to Mr. Data, they eventually free themselves… only to find that they’ve been reliving the same event (including their deaths) over and over again for 17 days. But hey, that’s not nearly as bad as the other ship that was also stuck in the loop (and captained by Kelsey Grammar for some reason): They’ve been on repeat for 90 years.The TNG crew found themselves in another timey-wimey situation when the Enterprise was virtually frozen in time while engaging in a rescue mission of a Romulan vessel. Luckily, Captain Picard, Troi, Data and Geordi were off-ship at the time, and they’re able to board the Enterprise and investigate the situation, determining that (essentially) once they get time running correctly again, the Enterprise will be instantly destroyed due to sabotage. It’s a high-concept and fun episode where Picard not only gets to watch his ship blow up and then un-blow-up, but we also get to see him draw a happy face in the frozen smoke of a warp core explosion right before he has a nervous breakdown!