No longer want to take risks due to reduced resources. Simple.
Spoilers Things that grind my gears about S3
- Thread starter ED-209
- Start date
especially as Book’s ship could enter the nebula...
But they did contact starfleet, otherwise how could Tilly know all this?
this was before the Burn.
Jeysus thats bad. Time to sack a few writers me thinks
You keep saying that but its a stupid reason. If thats the best they can come up with then dont do that story line in the first place
Fear makes people do stupid things.
They were still facing resource shortages.
all more reason to investigate a dilithium nursery.
Logically, yes. But, this wasn't a logical decision. It was fear based.
fear of what?
According to the writers, the federation was “as strong as ever” before he burn.
I'd have to revisit it but losing ships seemed to cause a pretty big fear reaction. But, I could be misremembering. Just because the Federation was strong doesn't mean they can't overreact to a ship loss.
Anybody who doesn't think that "fear based decisions" by governments and populations isn't a real thing hasn't been alive a day for the past 50 years.
Rationality typically has VERY little to do with decision making, based on my observations.
The older I get the more I realize this and the more people who go "Well, they should have just done that" really grinds my gears because it basically treats everyone as lacking emotion. It has become incredibly frustrating over the years because apparently fear is not something that is readily acknowledge in decision making process. I'm probably way oversensitive to it given my line of work but it frustrates me that it isn't acknowledged at all.
The problem is not that, just that there isn’t much to be afraid of here. They had the means to rescue that ship, they had the location and the motivation, so why didn’t they?
From what I am recalling a ship was sent but it was two weeks out to get to the nebula and was apparently destroyed. So, there was an attempt and they lost another ship. So, wouldn't you be afraid of losing another ship?
i would investigate on *why* the second ship was lost.
Cool.
I don't think it really adds up here. If you are running out of dilitihum to the point that it's such a crisis that you are ordering all the scientists in the Federation to find a solution and losing member worlds because of it, that you wouldn't chase down every possible lead you could find (especially leads that are easily accessible via transwarp corridors)?
Also, why would the admiral sitting in his chair at some starbase be pissing in his pants at the prospect of sending another ship to investigate why the first one was lost? It's one ship. A fleet admiral oversees, what, 10,000 ships? It just doesn't add up.
They did send another ship-it was destroyed.
How many do you send? From reading this thread it appears that many if they were in charge would send the whole fleet and be OK with however many dying. I suppose that is the easiest part.
Given how dire the situation was I would think sending more ships would make sense (or maybe send a more powerful ship then the one that was destroyed and tell them to be more careful)? I mean, if things are so desperate that you are willing to lose Vulcan as a member world, I don't think the fleet admiral is going to think twice about sending some more people potentially to their deaths. in a position like that you are probably making decisions that affect a far greater number of lives daily.
This is what I aimed at in my reply (as to why it seemed like the USS Hiraga hadn't contacted Starfleet to inform them they were going to Verubin nebula to try and rescue the Khi'eth - because it seems to me that they hadn't, otherwise, SF would have dispatched another ship to investigate the disappearance of the USS Hiraga after it has been out of touch for a few weeks (which would have led SF to the Khi'eth and another potential rescue attempt).
If they said a second rescue attempt (after the USS Hiraga) was attempted and failed, and the Verubin nebula classified as 'too dangerous' to go back into, that would solve the problem, but to me, that doesn't make much sense because SF wouldn't want to leave anyone behind, and as we know, the Khi'eth was equipped to handle the nebula, so surely SF could have modified one of their ships or sent a ship similar to the one Booker had with morphing capabilities to go in, grab the survivors, quickly download the data from the Khi'eth and bring back everyone.
No, the distress call indicated only the USS Hiraga tried rescuing the Kelpiens but was presumed lost when the Khi'eth scientists mentioned there has been no communications from the Hiraga for 6 months after entering the nebula.
Federation logs only mention the Khi'eth being sent to investigate a dilithium nursery, however they (and the distress call) do NOT mention another Federation/SF ship being dispatched to investigate the disappearance of USS Hiraga or try a second rescue of Khi'eth.
This is where things don't add up.
Federation records never mention a follow-up investigation leading to the loss of USS Hiraga (which should have been done)... and if such an investigation was done, why isn't anything mentioned?
For that matter, it would have been as simple as having Tilly add: 'There was a second attempt at rescuing the Khi'eth, but before the USS 'whatever' could execute it, they conducted an investigation into the loss of USS Hiraga, and determined that the Verubin nebula was too dangerous and couldn't be traversed safely to reach the Khi'eth'.
This however was never mentioned. And also, it still doesn't explain why did the Khi'eth survive the nebula (albeit damaged) and other SF ships were dropping like flies, and why couldn't they modify another ship to go into the nebula like the Khi'eth did?
Programmable matter (or heck, even transporters with replicators) could do the work in hours or less to modify structural integrity... the Discovery never even tried modifying their shields to make them more resistant to the nebula radiation (but then again, Saru was a bit rash in his decision to take Disco inside).
Similar threads
