HB of CJ wrote:Yep..me too. To the point where I re read that part about 3 different times thinking there was something I missed. Nope. Just consider it a major goof that does happen from time to time writing science fiction space opera shoot 'em ups.
All the excellent reasons already given why. No need to add except that Honor had all the time in the world to re establish communication with the next admiral in line and get him/her to self destruct all the incoming Sollie missiles.
My belief is that the Sollie onslaught, like most or all navies offensive missiles, MUST have redundant self destruct systems built into them, if for no other reason than to keep bad accidents from happening ... which is kinda what happened.
HB of CJ (old coot) Lt.Cm.
Why should Honor assume that (a) there was any reason to contact a second admiral, (b) that the aforementioned second admiral would have listened to her if Filaretta obviously hadn't, (c) that she even knew how to get in touch with this hypothetical individual, or (d) that she had "all the time in the world" to do it?
She didn't know anything had happened to Filaretta or his flag bridge. All she knew was that the admiral to whom she'd been talking had cut his communications with her and launched a hellacious number of missiles. There was absolutely no reason for her to think he'd been suddenly killed or that the missiles had been launched without proper command authority. She also had no way of judging how effective any DDMs coming at her might be. She could safely assume they would be far, far less effective than GA missiles would have been, but she had an enormous number of them inbound and --- as Tom Theisman pointed out --- no possible moral justification for risking her own personnel's lives to save those of people who'd come expressly to invade her star system
and been the first to open fire.
The entire notion that anyone on the Sollies' side could have reacted in time to (a) realize what had happened to Filaretta's flag bridge, (b) alert his next in command about it, (c) shift tactical control to the new senior officer, and (d) self-destruct the missiles is, quite simply, ludicrous. One of the factors most often overlooked in bad military fiction is the human reaction-response time limitation. It takes time to simply transmit information, and at each stage in the process, that information had to be evaluated before the proper authority at that stage can determine what to do in response to it.
Following the battle between the
Chesapeake and the
Shannon in the War of 1812, a midshipman --- I believe he was only about 13 years old --- was court-martialed and dismissed the service for deserting his post. His crime had been to drag his mortally wounded captain below decks to the surgeons. Unfortunately, in the short interval he was below decks,
every officer senior to him was killed or incapacitated, and command of the ship devolved upon him. Except he wasn't on deck to assume it because he was trying to save his captain's life. At the Battle of Jutland, Admiral Beatty's flagship survived only because a mortally wounded turret officer got the order to seal the magazine's flash-tight scuttles to the magazine crew in time. The timing was so close that they found members of the crew dead, killed by the flash Major Harvey had seen coming,
with their hands still on the securing clips. My point is that things move incredibly fast in combat and that human brains, information transmission, and the time required for people to realize what's happening
and react to it very, very often fail to keep up with them.
I could give you dozens of more examples --- from Daniel Callaghan's task group in the Naval Battle of Guadalcanal in 1942 to the night action following Jutland, to mention only two --- where failures in communication and response caused catastrophic results. And none of them resulted from the deliberate destruction of the commanding officer
and his entire staff by a saboteur.