of abandoning his crew? I never fully understood why he had his crew abandon ship. The Constellation, while badly damaged, was still perfectly capable of suppoting the crew. The life support systems were still functional and as Scotty showed even the engines were fixable. More importantly, had they stayed on board, they could have used one of the warp capable shuttles to find help. Stranding the crew planetside cut them off from potential means of rescue.
Was Matt Decker guilty...
- Thread starter Gotham Central
- Start date
No - at that time, he thought he was saving his crew. Remember, they were still too close to the 'Doomsday Machine®' and Matt wanted to get everyone off of a crippled ship. They didn't know (apparently) exactly what the Doomsday Machine was actually about at that point so they didn't realize what would happen to that planet.
Remember that Matt said they were hit again after he beamed the crew down and he couldn't do anything to save them when the DM went after the planet they were on...
It may be a bit of a stretch, but the point was to make him the last survivor and mentally strained by that fact. It worked well to move the story.
Remember that Matt said they were hit again after he beamed the crew down and he couldn't do anything to save them when the DM went after the planet they were on...
It may be a bit of a stretch, but the point was to make him the last survivor and mentally strained by that fact. It worked well to move the story.
They find the Constellation still habitable, but that doesn't mean it was a stable or safe environment. It was under attack from the Planet Killer - remember that the Transporter went out after everyone was beamed down. Decker may simply have judged that at the rate systems were failing under the machine's attack that the crew would not be able to carry out an evacuation later.
Let's not forget that when they first encountered the Planet Killer it was doing what the name suggests: chopping chunks out of a planet with a force beam. Based on that, it wasn't terribly logical to assume they were any safer there than on the ship. The only possible rationalization is that Decker assumed the Planet Killer was going to keep hitting the Constellation until it was destroyed, which meant imminent death versus a beamdown to a probably doomed planet. It's one of the dramatic weaknesses of the story that this isn't addressed at all. I mean, they discovered all the "totally destroyed" solar systems, which should've told them the thing was gonna wipe out every planet it found. No safe haven.
It makes no sense. The machine's MO is to shoot a few times then tractor the unfortunate ship into its maw for quick disposal (see the battle with the Enterprise).
How much time did they have to beam an ENTIRE CREW down to a nearby planet IN THE MIDDLE OF A BATTLE? Totally unbelievable. Also a stupid move, considering they knew the machine destroyed planets. Also out of character for Starfleet personnel who would rather "go down fighting" then flee to safety. What happened to Decker's obsession with "preserving life and the safety of Federation planets"? It would have been difficult to stop it without a crew to at least attempt repairs.
Maybe, just maybe, Decker's plan was to get the crew off, hope the planet killer would swallow the Constellation, and detonate the impulse engine inside it. That's the only plausable explanation to me, but why wouldn't he relay the plan to Kirk when the Enterprise comes along immediately? And how could he possibly have time to beam the crew down with the ship already dead (no power, phasers useless)?
Here's what we know of the chain of events as described by Decker:
1) Constellation discovers the machine hovering over the fourth planet, already slicing it up with its anti-proton beam.
2) Constellation engages planet killer - Decker makes the mistake of firing when they are "too far away."
3) At some point the machine clearly devastates the Constellation with its anti-proton beam (evidence of destruction from the planet killer's only offensive weapon is obvious).
4) Constellation is dead (no power, phasers useless) - beam down to third planet commences.
5) After the beam down is complete, the machine "hits again" and the transporter goes out.
6) Planet killer apparently loses interest in the Constellation after knocking out the transporter and goes after the third planet, destroying it.
So basically we have to either believe there is sufficient time to beam the crew down "between shots" or the planet killer is considerate enough to give Decker the time he needs before coming back for a final strike. Why would it do this?
Conclusion: The sequence of events as stated by Decker cannot possibly be correct. The only explanation that fits the facts and the demonstrated behavior of the machine are that Decker beamed his crew down to the third planet WHILE THE SHIP WAS STILL FUNCTIONAL with the intention of using the Constellation for a suicide run, sacrificing only himself and the ship to save the Federation. By traveling to the third planet after the first engagement, Decker escapes the machine's defensive sphere long enough to have time to beam the entire crew down. A long-range communications device is likely beamed down with the crew so that they can contact help after the machine is destroyed. Decker's plans are thwarted by the planet killer's second attack on the ship which fatally cripples the Constellation before it can enter the machine's maw and explode. Decker is then forced to watch/listen as the machine loses interest in the ship and kills his crew by consuming the third planet. The only question remaning is - why lie to Kirk? Why not brief him on the plan to destroy the machine immediately and petition him to help repair the Constellation enough to implement it?
Then again...it IS just a TV show.
How much time did they have to beam an ENTIRE CREW down to a nearby planet IN THE MIDDLE OF A BATTLE? Totally unbelievable. Also a stupid move, considering they knew the machine destroyed planets. Also out of character for Starfleet personnel who would rather "go down fighting" then flee to safety. What happened to Decker's obsession with "preserving life and the safety of Federation planets"? It would have been difficult to stop it without a crew to at least attempt repairs.
Maybe, just maybe, Decker's plan was to get the crew off, hope the planet killer would swallow the Constellation, and detonate the impulse engine inside it. That's the only plausable explanation to me, but why wouldn't he relay the plan to Kirk when the Enterprise comes along immediately? And how could he possibly have time to beam the crew down with the ship already dead (no power, phasers useless)?
Here's what we know of the chain of events as described by Decker:
1) Constellation discovers the machine hovering over the fourth planet, already slicing it up with its anti-proton beam.
2) Constellation engages planet killer - Decker makes the mistake of firing when they are "too far away."
3) At some point the machine clearly devastates the Constellation with its anti-proton beam (evidence of destruction from the planet killer's only offensive weapon is obvious).
4) Constellation is dead (no power, phasers useless) - beam down to third planet commences.
5) After the beam down is complete, the machine "hits again" and the transporter goes out.
6) Planet killer apparently loses interest in the Constellation after knocking out the transporter and goes after the third planet, destroying it.
So basically we have to either believe there is sufficient time to beam the crew down "between shots" or the planet killer is considerate enough to give Decker the time he needs before coming back for a final strike. Why would it do this?
Conclusion: The sequence of events as stated by Decker cannot possibly be correct. The only explanation that fits the facts and the demonstrated behavior of the machine are that Decker beamed his crew down to the third planet WHILE THE SHIP WAS STILL FUNCTIONAL with the intention of using the Constellation for a suicide run, sacrificing only himself and the ship to save the Federation. By traveling to the third planet after the first engagement, Decker escapes the machine's defensive sphere long enough to have time to beam the entire crew down. A long-range communications device is likely beamed down with the crew so that they can contact help after the machine is destroyed. Decker's plans are thwarted by the planet killer's second attack on the ship which fatally cripples the Constellation before it can enter the machine's maw and explode. Decker is then forced to watch/listen as the machine loses interest in the ship and kills his crew by consuming the third planet. The only question remaning is - why lie to Kirk? Why not brief him on the plan to destroy the machine immediately and petition him to help repair the Constellation enough to implement it?
Then again...it IS just a TV show.
If it needed to happen in order for us to get one of the all-time best hours of Trek, I'm cool with it.
well i think that given the circumstances , he just wasnt thinking clearly . sometimes when things are happening so fast you sometimes react without thinking.
he wanted to destroy the machine , but wanted to spare his crew if he could . prob thought that , a ( beaming the crew down to the planet would put them out of the line of fire, plus maybe the ship would not have supported everyone , they were out of power he said. but in his haste he inadvertently
put them directly on the menu as it were.)
plus maybe had scanned said planet and thought that it was "bad tasting" to the planet killer . saving them in case he did not succeed . but then like someone has already said , the ship was crippled before the plan could be carried out . then it went after said planet , killing all the remaining crew.
he wanted to destroy the machine , but wanted to spare his crew if he could . prob thought that , a ( beaming the crew down to the planet would put them out of the line of fire, plus maybe the ship would not have supported everyone , they were out of power he said. but in his haste he inadvertently
put them directly on the menu as it were.)
plus maybe had scanned said planet and thought that it was "bad tasting" to the planet killer . saving them in case he did not succeed . but then like someone has already said , the ship was crippled before the plan could be carried out . then it went after said planet , killing all the remaining crew.
Right you are. My feeling is that Decker was going off the deep end already by the time he ordered the crew beamed down to the doomed planet. He already knew exactly what the DDM was capable of doing. Spock himself stated that the DDM was apparently programmed to ignore something as small as a starship...especially a nearly-dead one, one would assume. So Decker's best strategy would have been to play dead until help arrived. He could have saved both his ship and crew...then the episode would basically pick up as we saw it, except the Constellation would have a partial crew on board.
It makes no sense. The machine's MO is to shoot a few times then tractor the unfortunate ship into its maw for quick disposal (see the battle with the Enterprise).
How much time did they have to beam an ENTIRE CREW down to a nearby planet IN THE MIDDLE OF A BATTLE? Totally unbelievable. Also a stupid move, considering they knew the machine destroyed planets. Also out of character for Starfleet personnel who would rather "go down fighting" then flee to safety. What happened to Decker's obsession with "preserving life and the safety of Federation planets"? It would have been difficult to stop it without a crew to at least attempt repairs.
Maybe, just maybe, Decker's plan was to get the crew off, hope the planet killer would swallow the Constellation, and detonate the impulse engine inside it. That's the only plausable explanation to me, but why wouldn't he relay the plan to Kirk when the Enterprise comes along immediately? And how could he possibly have time to beam the crew down with the ship already dead (no power, phasers useless)?
Here's what we know of the chain of events as described by Decker:
1) Constellation discovers the machine hovering over the fourth planet, already slicing it up with its anti-proton beam.
2) Constellation engages planet killer - Decker makes the mistake of firing when they are "too far away."
3) At some point the machine clearly devastates the Constellation with its anti-proton beam (evidence of destruction from the planet killer's only offensive weapon is obvious).
4) Constellation is dead (no power, phasers useless) - beam down to third planet commences.
5) After the beam down is complete, the machine "hits again" and the transporter goes out.
6) Planet killer apparently loses interest in the Constellation after knocking out the transporter and goes after the third planet, destroying it.
So basically we have to either believe there is sufficient time to beam the crew down "between shots" or the planet killer is considerate enough to give Decker the time he needs before coming back for a final strike. Why would it do this?
Conclusion: The sequence of events as stated by Decker cannot possibly be correct. The only explanation that fits the facts and the demonstrated behavior of the machine are that Decker beamed his crew down to the third planet WHILE THE SHIP WAS STILL FUNCTIONAL with the intention of using the Constellation for a suicide run, sacrificing only himself and the ship to save the Federation. By traveling to the third planet after the first engagement, Decker escapes the machine's defensive sphere long enough to have time to beam the entire crew down. A long-range communications device is likely beamed down with the crew so that they can contact help after the machine is destroyed. Decker's plans are thwarted by the planet killer's second attack on the ship which fatally cripples the Constellation before it can enter the machine's maw and explode. Decker is then forced to watch/listen as the machine loses interest in the ship and kills his crew by consuming the third planet. The only question remaning is - why lie to Kirk? Why not brief him on the plan to destroy the machine immediately and petition him to help repair the Constellation enough to implement it?
Then again...it IS just a TV show.
Must we remember every little detail? You totally ruin my argument when you do that!
There's a lot with this episode that doesn't make sense from a military perspective:
1) Beaming the crew down to a planet AFTER seeing that the Doomsday Machine has been destroying entire star systems and was slicing a planet up when the Constellation went in. Sorry, but any Commander after witnessing that thinks "Okay, my crew should be safer down there..." isn't thinking properly.
2) That Commadore Decker is ABLE to say "I'm taking command of the Enterprise..."; as I do believe that once you've LOST your entire ship and crew, you'd be barred from being able to command another starship until a board of inquiry cleared you, or extrodinary circumstances, such as the rest of teh command crew being dead or incapacitated which was never the case here.
But hey, without all of the events that occured as they did, it would have been a very botring episode.
Had Decker survived there most certainly would have been a Court Martial, and the question posed by the OP would just as certainly been one of the charges.
Decker cannot be "guilty" in the legal sense without such a trial.
He may be guilty in a moral sense as described by other posters. He certainly felt morally guilty which drove him into the madness we saw in the episode.
Decker cannot be "guilty" in the legal sense without such a trial.
He may be guilty in a moral sense as described by other posters. He certainly felt morally guilty which drove him into the madness we saw in the episode.
Okay, that last line made my point FOR me.
An extrapolation of present day society, sir. The orders given at the top do not reflect the realities at street (or interstellar) level. It has always been so- the closure of the gap between is always a precursor to success; the widening of the gap... well, see our present U.S. & Earth economy for that relevancy.
Strand your crew on the third planet, or go to war in Iraq... emotion-driven, fact-deprived decisions that lead to a recipe for unpleasantness.
Kirk's way is best. Do the correct thing & take the heat later. Unfortunately, he is a singular soul.
Yeah...commodores. Stocker drove them into the neutral zone; Wesley was going to blow them up; Travers didn't survive to give Bones his un-reconstituted meal; Stone court-martialed Kirk; Mendez's likeness "court-martialed" Spock; Enwright made them pick up Daystrom and M-5; Barstow got them embroiled with Lazarus and anti-Lazarus.
Thanks for the back-up, Jeri!
You're welcome; but I was working on that before you posted. Didn't see your post until after I posted...Thanks for the back-up, Jeri!
Similar threads
