Looking at NASA’s history and the pressures at play, I’m concerned they are deliberately leaving the door open to building flight rationale even if they end up not fully understanding the thruster issue before the capsule needs to come back.Listening to the press conference yesterday was frustrating. Both NASA and Boeing kept talking around the issue without clearing stating it. NASA needs to just come out and say, “We don’t fully understand why the thrusters failed or if we can do anything to avoid those failures occurring again during the return. Unless we can get comfortable with that, we will not approve the return of the Starliner with the astronauts on board.”
Before the launch, someone on another thread made the argument that while a single small leak in and of itself may not be a big deal, what if the same root cause affected other similar areas of the spacecraft and therefore could manifest during the flight. Well, we went from one leak to five.They had 18% (5 of 28) of the thrusters fail. After testing them, 4 of those 5 are now preforming nominally. However, they need to know why they failed in the first place and much more importantly, that they now have confidence that 18% or more won’t fail during the return. The testing they are doing at White Sands prior to approving the return of Starliner with astronauts on board must be to try to answer those questions.
Pining for fjords...“I want to make it very clear that Butch and Suni are not stranded in space...perhaps they are marooned, in the lurch, left high and dry, adrift and abandoned...but certainly not stranded! I cannot stress that enough."
Polaris dawn is a free flyer that has been modified to support a spacewalk. If it still has the docking port it isn't currently functional. It would make way more sense to pull the next regular crew vehicle forward if that's what they had to do.Polaris dawn is supposed to launch mid July. They still have not set a date for the launch and seem to be pushing the date for the launch. I wonder if this has something to do with the starliner.
I was thinking more of if the thrusters failed completely to de orbit starliner, the Polaris dawn vehicle would be a high risk rescue where everyone could suit up and then transfer to the crew dragon.Polaris dawn is a free flyer that has been modified to support a spacewalk. If it still has the docking port it isn't currently functional. It would make way more sense to pull the next regular crew vehicle forward if that's what they had to do.
That would actually make a lot of sense. The cost to postpone Polaris Dawn a few days is presumably negligible in the big context, so no reason not to keep this rescue option open. And Jared Isaacman would surely be very happy to be the heroic rescuer of such a mission.I was thinking more of if the thrusters failed completely to de orbit starliner, the Polaris dawn vehicle would be a high risk rescue where everyone could suit up and then transfer to the crew dragon.
The suits that the astronauts wear on Starliner and regular Dragon flights are not intended to be used outside the capsule, and even the Polaris Dawn suits are tethered. There is no way to transfer in space.where everyone could suit up and then transfer to the crew dragon.
I came for the fiasco story, stayed for the orthogonal concepts.Being safe and being stranded are orthogonal concepts.
The suits that the astronauts wear on Starliner and regular Dragon flights are not intended to be used outside the capsule, and even the Polaris Dawn suits are tethered. There is no way to transfer in space.
That’s a Hollywood plan, not a NASA plan.You could survive for a minute or two on the air available in the suit itself. Disconnect, transfer, reconnect at new location.
I'm not saying it's a great plan, but it is possible. Only in a dire emergency, I suppose... And better than that 2001 method.
Also, I have no idea how long it takes to connect or disconnect.
That’s a Hollywood plan, not a NASA plan.
There are people on this one. Changes a lot of things.If I remember correctly 2 thrusters failed in the second unmanned test, is there any reason they didn't keep that one on station, run two weeks of trials and find the issue then? Instead they called it at 5 days and reported it as a success. Im just surprised they are surprised that the thrusters are failing like last time
Yes, I do use vocabulary like that in ordinary conversation.I came for the fiasco story, stayed for the orthogonal concepts.
Only problem is that they couldn't reconnect as the Starliner and Dragon suits have different connections.You could survive for a minute or two on the air available in the suit itself. Disconnect, transfer, reconnect at new location.
I'm not saying it's a great plan, but it is possible. Only in a dire emergency, I suppose... And better than that 2001 method.
Also, I have no idea how long it takes to connect or disconnect.
The Starliner suits can’t plug into the Dragon capsule as discussed in previous comments.You could survive for a minute or two on the air available in the suit itself. Disconnect, transfer, reconnect at new location.
I'm not saying it's a great plan, but it is possible.
The batteries were rated at a 45 day service life, plus margin, for a reason. They don't just arbitrarily assign a short service life for giggles and grins. So even if battery performance is at the best end of the tested performance envelope, they're now cutting into margin. Eventually you run out, even with optimal performance.The article specifically indicates that they believe that can be extended based on an analysis of actual battery performance. I haven't seen anything to indicate the batteries are a special short term pack they designed for two missions. Likely NASA wanted to see the performance of the batteries before certifying them for a longer duration.
This is a test flight after all.
The batteries were qualified or certified for 45 days. That doesn't mean they're only rated for 45 days. They could be the batteries for a full mission, they just hadn't been testing in-use on the ground long enough to say they were ready for 210 days. Instead, they may be executing that testing as they're running now. It's totally valid to say that the internal resistance of the cells is still below a threshold for another period of time (or whatever the metric is). That's not a way to say this batter is capable of making it 100 more days, but they might be able to qualify it for 5 additional days however often they like. Until the battery no longer passes its internal test.The batteries were rated at a 45 day service life, plus margin, for a reason. They don't just arbitrarily assign a short service life for giggles and grins. So even if battery performance is at the best end of the tested performance envelope, they're now cutting into margin. Eventually you run out, even with optimal performance.
And no, this wasn't a "test flight." This was a certification flight. It was supposed to be the flight that shows, within reason, that everything is working as-designed and that the vehicle is ready for operational use.
Are we really going to pretend that it's ready, after all these unforseen problems?
Fair enough. What little aerospace certification experience I have is in structures, which is a bit more determinate, if you'll pardon the pun.The batteries were qualified or certified for 45 days. That doesn't mean they're only rated for 45 days. They could be the batteries for a full mission, they just hadn't been testing in-use on the ground long enough to say they were ready for 210 days. Instead, they may be executing that testing as they're running now. It's totally valid to say that the internal resistance of the cells is still below a threshold for another period of time (or whatever the metric is). That's not a way to say this batter is capable of making it 100 more days, but they might be able to qualify it for 5 additional days however often they like. Until the battery no longer passes its internal test.
That's not a great way to run a long-duration mission. That's a great way to provide mission flexibility to extend a mission if hardware isn't failing as fast as a worst-case scenario.