Skip to main content

In Star Trek, why do Federation / Starfleet ships always seem to delay returning fire until it's almost too late?



I keep seeing this situation in Star Trek series:



"Captain, they've raised shields!"
"Now they're charging their weapons!"
"Captain, they're targeting our engines!"
"OK Ensign, evasive maneuvers."
BOOM
"Shields are holding, Captain, we're at 25%."
"They're coming about for another pass!"
BOOM

"Captain that one took out our warp drive, shields are offline as are phasers"
"Ensign, target their weapons array with a photon torpedo."
"Captain, they're hailing us..."
"Ok, belay that, put 'em on-screen."



& from this point they're possibly boarded, taken hostage, all kinds of bad outcomes that they have to come back from. One might imagine that a well-equipped cruiser would drill for such eventualities. I'd imagine it more like:



"Captain, they're raising shields!"
"Folks, you know what to do - defend the ship!"
All over the ship the crew work together as a well-oiled machine. Shields go up, phasers take out the bad guys' weapons & engines faster than the other guys can react, while simultaneously the helmsman takes them through a series of seemingly random maneuvers designed to make them a very slippery target.

"OK hail them, see why they made an aggressive move on us."



Any reason why it's always the former & never the latter case?



Answer



It is because of the policies of the United Federation of Planets. The TNG Technical Manual has this to say on the matter, (For those following at home: Section 11.6, 'Tactical Policies').



Starfleet draws proudly on the traditions of the navies of many worlds, most notably those of Earth. We honor our distinguised forebears in many ceremonial aspects of our service, yet there is a fundamental difference between Starfleet and those ancient military organizations. Those sailors of old saw themselves as warriors. It is undeniable true that prepairedness of battle is an important part of our mission, but we of Starfleet see ourselves foremost as explorers and diplomats. This may seem a tenuous distinction, yet it has a dramatic influence on the way we deal with potential conflicts. When the soldiers of old pursued peace, the very nature of their organizations emphasized the option of using force when conflicts became difficult. That option had an inexorable way of becoming a self-fulfilling prophecy.


Today, peace is no easier than it was in ages past. Conflicts are real, and tensions can escalate at a moment's notice between adversaries who command awesome de- structive forces. Yet we have finally learned a bitter lesson from our past: When we regard force as a primary option, that option will be exercised. Starfleet's charter, framed some two centuries ago after the brutal Romulan Wars, is based on a solemn commitment that force is not to be regarded as an option in interstellar relations unless all other options have been exhausted



(bolding mine, italics are verbatim)



Further down the page it says:



A starship is regarded as an instrument of policy for the United Federation of Planets and its member nations. As such, its officers and crew are expected to exhaust every option before resorting to the use of force in conflict resolution. More important, Federation policy requires constant vigilance to anticipate potential conflicts and to take steps to avert them long before the escalate into armed conflict.



Later on (I'm not going to type the full quote because my fingers hurt from typing all of that!) they state that "there are situations in which a starship and her crew can be considered expendable". So the Federation places a very high price on peace /over/ immediate loss of life. Logically speaking going to war causes more loss of life in the long run, so if you take the aphorism "The lives of the many outweight the lives of the few", then it is also a rather logical choice.


So the crew are just adhereing to policy meant to preserve the peace (And I have no doubt that Picard would have valued and cherished these policies very highly).


Comments

Popular posts from this blog

languages - Do we ever see written English in the Star Wars films?

In Empire Strikes Back , we see a transcription of what R2's beeps and bloops mean, but it's not English (sorry for the low quality, it's from the 2004 DVDs): I'd assume it's what Basic looks like when written, but is there some point in the the Star Wars films we see written English instead? (This sort of spun off from a discussion in How do people understand astromech droids? .) Answer At one point there was English but it has been phased out in subsequent versions of the films. Chris Gould at DVD Active did a comparison of all versions of each of the Star Wars films, and in his comparison of Episode 4 , there are a couple of screenshots showing how the power gauge for the Death Star tractor beam was changed. I imagine there are probably more to be found in his other comparisons but I haven't got around to reading those yet.

Was the "pure soul" of Harry's what had really hurt Voldemort?

In the Order of the Phoenix, Voldemort possesses Harry, and it hurts. Greatly. I think that Dumbledore explained that it was because Voldemort's rotten soul was incapable of assimilating Harry's pure soul, that Voldemort didn't understand the love and friendship etc that Harry has in his heart. But, I think it was a lie. Remember that in Deathly Hallows, while looking for information regarding Horcruxes, it is discovered that it is in fact possible to merge a soul fragment back, but that the process was extremely painful. Now then, if Voldemort tried to possess Harry, and Harry had a fragment of Voldemort's soul, I think that it could have been the true cause of Voldemort's pain: the fact of having his soul so close of another fragment. I think that Dumbledore knew that fact, but had to lie to Harry because it was inappropriate to let him know that he had one of Voldemort's soul fragments at the moment. Is that right? Or was it truly the pure soul of Harry's...

star wars - What "exactly" happens when someone turns to the Dark Side?

When I saw the original Star Wars saga as a kid, the concept of the Dark Side imprinted in me was quite simple. You did a bad thing, so you're a bad person so you go to the Dark Side and keep doing bad things. Now, obviously this doesn't hold true in reality. In my mind it is perfectly reasonable for Luke to kill the Emperor and Vader and then just flee the Death Star and rejoin the Alliance. After all they are at war, those are enemy officers that have captured him and are taunting him by threatening with death of all loved ones and the whole operation was intended to kill the Emperor anyway. The same would hold true for Anakin. He could have killed Mace Windu to save the Chancellor and Padme but that doesn't mean he's going to then go mad and kill all Jedis including children. It doesn't add up from a merely psychological point of view. He had a set of objectives and that made him want to keep the Chancellor alive (quite valid by the way, Mace Windu is quite clums...

star trek - Warning regarding forward saucer section in Nemesis?

In Star Trek: Nemesis , just before the Enterprise rams into the Scimitar, Picard sends a text message from his captain's chair arm pad to Troi — who is manning the helm in lieu of the crewman who was just blown out through what was once the view screen — indicating that she should put full impulse on standby. (Literally, if you watch the scene closely, Troi's console prefaces the order with "TXT MSG" !) My question is: Did Picard also somehow warn crew members in the forward saucer section about what was about to happen? The ramming of the Scimitar was a heat of the moment decision. Considering that he also resorted to calling the auto-destruct sequence shortly after (which ended up being offline), he probably was of the mindset that any losses would be acceptable in order to hault Shinzon's march to Earth. Still, I'm curious. Answer The original script indicates that he called for the crew to " brace for impact ". Whether that call (or the comma...