
Memory Alpha Entry
Chrissie's Transcript
SFDebris' Review
Booby Trap-

...is an episode that many would cite as falling victim to the "Too many cooks" idiom. To those who are unfamiliar with it, it's taking what should be a simple story and making it needlessly complex and convoluted because every writer that this story passed through had their own idea on where to take it. What makes this particular case special is that it feels as though all the writers weren't even in the same room when writing this story and didn't bother to read what everyone else did. That or the higher ups who decided to take their favorite bits from each writer didn't bother to check the final product to see how compatible each writers' contribution was. More on that later.
Our episode opens on the holodeck with LaForge on a date with someone named Christy. We know this date will go nowhere because it not only follows every typical "Bad Date" trope, but because this is Star Trek: The Next Generation, a show that is renowned for our characters starting a relationship and quickly ending it by episode's end. Heck, the only character who actually gets married in TNG jumps ship to a different series where that kind of behavior isn't looked down on.
Back to the A-Plot, the Enterprise is exploring an asteroid cluster that contains a ship that's a thousand years old. Picard being such an expert on archeological finds almost has a bona fide nerd gasm about the prospects of exploring such an ancient vessel. So much so that he joins the away team to explore the interior. It's clear that the person writing this part of the story understood Picard's fascination for exploring the unknown and wanting to preserve such finds with lines like
"That ship belongs in a museum."
"You'd expect the bridge layout of this era to be clumsy, awkward, but look at this. It's a model of simplicity. Elegant, functional. They built this craft for generations. And it worked."
and upon returning...
"Thrilling. That was absolutely thrilling."
Too bad the person who wrote that didn't handle the resolution.
But things start to go bad for our crew when the Enterprise finds herself caught in the same trap that rendered this ancient ship powerless. It seems that the asteroids actually drain energy from sources around them and is quickly draining the Enterprise to the point where it can hardly move at all. This is where we get what I can only assume was the "creepy and unintelligent" portion of the episode comes in with Picard making one of the worst command decisions of this entire season and Geordi literally getting attached to the Enterprise's AI. And I am not kidding. The crew know that the asteroids absorb energy, and they are actually contemplating firing their phasers at them.... Phasers.... beams of energy. Here's where the stupid part comes in.
RIKER: I recommend we fire directional phasers at those coordinates.
LAFORGE: We won't be able to maintain energy reserves. We might even lose a few circuits in the new configuration.
PICARD: How critical will the losses be?
LAFORGE: Not enough to shut down our engines, but if we don't make it I don't know that I can hold the shields.
DATA: There is also the possibility that the phasers will supply the assimilators with what they need most. Energy.
PICARD: You know, I imagine a very similar discussion taking place on our neighbour ship over a thousand years ago. Let's hope our decisions are more successful than theirs were. Mister La Forge, I want you to return to Engineering and continue with your efforts without delay. Mister Worf, prepare the phasers.
WORF: Phasers locked on coordinates.
PICARD: Fire.
*Enterprise shoots at the asteroids*
RIKER: Nothing.
WORF: Radiation levels increasing. Eight percent. Ten percent.
DATA: Energy reserves are dropping rapidly, sir.
PICARD: Damn you.
This scene is just... astonishing. When I was watching it on BluRay, I actually rewound to the part where Data literally explains to Picard that the phasers would give these "energy consuming" asteroids what they need, ENERGY! Seeing Picard brush this warning aside and firing the phasers anyway, I felt like I was watching an episode of Enterprise with Jonathan Archer doing his typical screw up job because he didn't want to listen to his Vulcan crew member's warning. Only in Enterprise, there was a slight chance that the writers would make Archer's decision be treated as an actual mistake on his part, where as this episode tries to play it out like Picard was cleverly fooled, hence the "Damn you" line. Yeah, if you want your story to be clever, you've got to be clever yourself.
So things go from bad to worse, Geordi tries working on ways to come up with a way out of there, and we finally get one. The Enterprise will free itself! So we spend a good chunk of this episode going over this plan to find out that it has a low chance of success, so LaForge decides to abandon the plan entirely and declare "We don't need no stinkin computers! We have our minds to pull us out of this problem!" The plan works and the Enterprise is safely clear of the astroid field with all systems coming back online. So now that the Enterprise is free and fully restored, Picard and crew contemplate on how to successfully retrieve this ancient and historical ship so that it can be fully examined and restored for historical....
PICARD: Number One, make sure that booby trap doesn't bother anyone again.
RIKER: Mister Worf, ready photon torpedoes. Set to detonate on impact with the Promellian vessel.
WORF: Aye, sir.
*The ancient ship and three asteroids blow up*
This is that thing I was talking about earlier about how the writers of this episode not working in the same room creates some questionable story progression. We have Picard literally falling in love with this Promellian ship at first glance, and than being so gung ho in destroying it without even contemplating on how to retrieve it safely from the asteroid field. Other things to note. One, the asteroids are what was causing the energy drain problem, not the Promellian ship. Two, given how the Promellian ship was the ONLY SHIP in the asteroid field when the Enterprise arrived, it's safe to assume that no other ship was lured into this trap for a period of over a thousand years. So why the urgency to destroy it the moment the Enterprise gets it's systems back? Three, why not just dispatch a beacon from a safe distance from the asteroids to alert all potential craft that the area is dangerous and full of asteroids that drain energy? Ugh.
So the episode ends the same way a lot of female characters end in Star Trek.
LAFORGE: You know, I've always thought that technology could solve almost any problem. It enhances the quality of our lives. Lets us travel across the galaxy. Even gave me my vision. But sometimes you have to turn it all off.
What an a%&. Not only was this entire episode about trying to save the ship from turning off completely, but he's only talking about turning her off. Yeah, technology gave me my vision, but when I say "turn it all off", I mean I'm going to turn YOU off and keep my vision on forever. No wonder you suck at getting women Geordi. You prefer ones who you can shut off with ease.
CONCLUSION:
Despite the many negative slaps I've given this episode, it isn't all that bad. The tension is rock solid, the actors give a good performance and it does tell an interesting story that delves on the "exploration" part of Star Trek really well. It's just a pity that there are so many areas that are in conflict with one another and we have competent characters making really stupid decisions. In regards to Leah (The actual Enterprise)? If you want a story where the ship that our main hero flies around in becomes sentient and the two develop a very nice relationship with one another, watch Neil Gaiman's Doctor Who episode "The Doctor's Wife". It's a far more superior take on the concept and it doesn't end with..... "I'm with you every day, Geordi. Every time you look at this engine, you're looking at me. Every time you touch it, it's me."
STINGER:
