The issue I take with this analysis is that it assumes that manufacturing defects weren't also a cause, just because they found another possible cause. Compounding issues are sneaky like this, especially when you can't possibly get your parts back to inspect.Just to add on to my comment earlier: NASA completely screwed up the failure analysis of the foam on Columbia. NASA concluded it was manufacturing defects and told the workers it was their fault.
Nope. It was cracking caused by thermal cycling.
Can Starliner be sent back unmanned? If it can, it seems like a no-brainer to send them back on Dragon.
To be fair, we also would have been far better served if the shuttle had been built to only serve NASA's goals and that the program had been properly funded without being tied to DOD operations.In retrospect, the proper way to fly a side-mounted Orbiter would have been to have the wings on the far side of the fuselage from the ET. The easiest way to accomplish that would have been to have the same geometry and just have the heat shield pointed out. It would have looked odd, but it would have been more immune to foam strike damage.
Of course, the proper, proper way to mount the Orbiter would have been on top.
In triple retrospect, we would have been better served flying the Saturn V 135 more times (manned or not) for what was spent on STS.
Fair enough.The issue I take with this analysis is that it assumes that manufacturing defects weren't also a cause, just because they found another possible cause. Compounding issues are sneaky like this, especially when you can't possibly get your parts back to inspect.
IIRC, NASA was the agency pushing for going into DOD operations and taking over all spaceflight activities.To be fair, we also would have been far better served if the shuttle had been built to only serve NASA's goals and that the program had been properly funded without being tied to DOD operations.
The cross range capabilities alone significantly increased the chances of a foam strike.
Okay, that seems a logical sequence, and I'll bow to your experience here.In the last press telcon, they stated that the software still has the auto mode logic. What's missing is the mission data load (configuration file) that sets parameters for what the software does in various situations, currently set to "notify the operator". The alternate settings tell the software to execute the appropriate auto actions. Apparently the vehicle can only fly one of those parameter sets at a time, so they need to install the auto parameters over the manual ones. And, since the software has changed since they last used the auto parameters, it needs to be tested in that configuration.
IIRC, they were trying to take over DoD funding, that way, because Congress wasn’t giving them enough money to build the shuttle. It backfired, in that the shuttle became that much more costly and complex in order to try to meet DoD requirements that were never even used.IIRC, NASA was the agency pushing for going into DOD operations and taking over all spaceflight activities.
If there were a problem with Dragon that caused them to not be able to leave safely, they'd want another option (not another Dragon). That's why 2 totally different options is always better than 1. It also would allow them to have a proper competition for launch contracts - while SpaceX is a bit more 'free market company' than 'monopolist' right now, that doesn't mean it always will act that way.I understand the principled reasons for having 2 options (Dragon and Starliner), but at this point, what logistical benefits is it providing? What possible technical challenges could arise with Crew Dragon that couldn't be fixed/resolved faster than fixing Starliner? It's clearly demonstrated itself as a reliable crew vehicle.
I no longer understand the practical reason for continuing to entertain the Starliner "option" when the primary vehicle is not going anywhere for the lifespan of the intended Starliner contract.
Good thing we've got Artemis nowIn triple retrospect, we would have been better served flying the Saturn V 135 more times (manned or not) for what was spent on STS.

Right now, we also don't want to have to go begging for seats from Russia.If there were a problem with Dragon that caused them to not be able to leave safely, they'd want another option (not another Dragon). That's why 2 totally different options is always better than 1. It also would allow them to have a proper competition for launch contracts - while SpaceX is a bit more 'free market company' than 'monopolist' right now, that doesn't mean it always will act that way.
Not knocking the other dozen Canadian astronauts, but Roberta Bondar and Chris Hadfield get you full credit to have any opinions you want.What troubles me about all of this is somewhat simple.
We in this community are the anomaly: we pay attention to this and we care about it.
Speaking from the country to the north that has a pathetically small and not particularly capable space agency, my observation is that NASA seems to be all but invisible and irrelevant to the overwhelming majority of the US public.
The only real 'mainstream' media coverage of this situation has been a couple of small articles describing the astronauts as 'stranded' on the ISS.
Nothing substantial reporting on how Boeing has screwed this up, very little on the NASA normalization of deviation that permitted it to fly in the first place. Nothing discussed within the context of the presidential campaigns about the situation.
It is very disheartening to see such a state of affairs on space policy and space efforts, and why I'm concerned is "well no one is paying attention: no matter what we do, it won't matter"
Much as I “really” love innuendo, referencing “back office talk” is rumor or worse (and shortly turning 82 and the very small likelihood that he would have significant value to Boeing, especially given the current and likely next Congress and Boeing’s level of disasterous screw-ups in recent years, makes Boeing hiring him in any capacity seem massively unlikely to me), and claiming he got paid off by Boeing while in the Senate is pretty much slander without evidence. So do you have any actual citations for the claims you made?The real problem is Bill Nelson's ties to Boeing. How much of that is going to influence his decision (and is there some sort of back office talk of him taking on a far more lucrative position with Boeing at some point). He's a politician at heart, so my faith is extremely diminished in that regard, especially with how much Boeing greased those palms during his Senate years.
Yes, I believe grabbing DoD funding was the motivation.IIRC, they were trying to take over DoD funding, that way, because Congress wasn’t giving them enough money to build the shuttle. It backfired, in that the shuttle became that much more costly and complex in order to try to meet DoD requirements that were never even used.
There's still Soyuz.If there were a problem with Dragon that caused them to not be able to leave safely, they'd want another option (not another Dragon). That's why 2 totally different options is always better than 1. It also would allow them to have a proper competition for launch contracts - while SpaceX is a bit more 'free market company' than 'monopolist' right now, that doesn't mean it always will act that way.
I have questions about the contract stipulations around this flight. If they bring the astronauts home alive on Starliner, does that mean that the vehicle is automatically approved? How much say does NASA even have in it after that?A/B title which I am responding to: "I trust NASA’s safety culture this time around, and so should you"
You know what the clincher was for why I don't trust NASA this time around? This snippet from Steven's article:
"If Starliner comes back without its crew, this would almost certainly lead to debate within NASA about whether to require Boeing to complete yet another Starliner test flight before clearing the spacecraft for operational missions"
Why would this "lead to debate"? Boeing has failed their milestone. There should be no debate. Boeing should be required to fix the issues and try again. Or they simply don't get paid.
Now, I do have a base level of distrust, because NASA is so far incapable of a 20 year stretch of crewed spaceflight without killing astronauts because of "go fever" and normalization of deviance. We've been told time and time again that they have "learned their lesson". They were supposed to have learned their lesson after Apollo 1. They were supposed to have learned their lesson after Challenger. They were supposed to have learned their lesson after Columbia.
Contracting Officer makes the final call on if it's successful or not, it's not an automatic thing.I have questions about the contract stipulations around this flight. If they bring the astronauts home alive on Starliner, does that mean that the vehicle is automatically approved? How much say does NASA even have in it after that?
Being a politician at heart could be a very good thing here.The real problem is Bill Nelson's ties to Boeing. How much of that is going to influence his decision (and is there some sort of back office talk of him taking on a far more lucrative position with Boeing at some point). He's a politician at heart, so my faith is extremely diminished in that regard, especially with how much Boeing greased those palms during his Senate years.
Then you hold Boeing's ass to the fire to get them to correct the issues with the capsule at their own expense. That is the advantage of these contracts. Its flown three times now, I think we have a fairly good idea what problems need fixed.There's still Soyuz.
NASA has never had more than one option for domestic crew transfer to/from the ISS. For quite awhile they had zero.
I don't see how giving Boeing a free pass on their obviously deficient capsule is a meaningful benefit to NASA.
These are good questions; flight-qualified software development is a lot more tedious than most other types of development, for good reason...Okay, that seems a logical sequence, and I'll bow to your experience here.
But as I noted in the other article's thread, if that's the case, how can this possibly qualify as a certification flight? Presumably the operational configuration would have both manual and autonomous modes, and yet those can't both be invoked on this software load? And if the software changed since they last used the auto-function parameters, how again is this a certification flight and not a test flight?
I have zero question with your explanation and your expertise, but rather that there's something really fishy about all these changes and untested flight software modes and loads being used on a certification flight. That's not how it's done.
I'm personally waiting to hear the news that Boeing has "gotten into the ears" of the House Committee on Science Space and Tech, or the Senate Subcommittee on Space and Science on the subject, and that the pressure on NASA to throw the dice is loud and clear.I hope you’re right, but all the bluster and bullshit we have seen which got us here in the first place looks a lot like go fever with a side order of normalized deviance.
The right decision is the hard one, and I’m cautiously optimistic but in no way confident they won’t just throw the dice and cross their fingers.
I agree. My concern is that Boeing is being declared to be that backup when they have failed again and again and again - for a FAR higher price tag than the successful Crew Dragon.Right now, more than ever, the international community needs its own backup ride to the ISS.
That sounds like a really, really shitty set of requirements/parameters. Any semi-modern vehicle carrying crew should be capable of both manual and autonomous mode. Hell, STS/Shuttle should have had that capability, and there was no technical reason to eliminate that capability.These are good questions; flight-qualified software development is a lot more tedious than most other types of development, for good reason...
Your presumption that both modes should be enabled is prudent, but not necessarily how the requirements might flow. Since the mission data load apparently can contain only one set of parameters, it's a configuration change with all the attendant CM paperwork.
Butch is 61 and Sunni is 58. The next 3 missions (crew 9, crew 10, and starliner 1) to the ISS already have crews assigned. So: the absolute earliest they would fly again with NASA is 2026. And this is far from guaranteed.Sure, but if they make that choice after management says go (or even while management is still pondering) - they will be permanently grounded. NASA culture demands an exceptionally gung-ho, always-positive output from astronauts. Express any doubt about NASA or the program, and you're done. Permanently.
I do not think that the problem is Boeing not learning new stuff. Learning new stuff from the MBAs while forgetting the engineering drilled into them by Bill Boeing is the problem.I think I could believe NASA has learned something since 1986. Boeing, not so much.
Okay, this might seem pedantic, but the vehicle does have that capability. They didn't eliminate it, they just didn't configure and test the auto mode for this mission. Now, it would seem based on all that's transpired that the ability to switch configurations mid-flight would be a thing, remains to be seen if that is implemented as a capability given that the eventual nominal operation of the vehicle is crewed.That sounds like a really, really shitty set of requirements/parameters. Any semi-modern vehicle carrying crew should be capable of both manual and autonomous mode. Hell, STS/Shuttle should have had that capability, and there was no technical reason to eliminate that capability.
Yes, anything that wasn't flying on F9 was going to be significantly higher costs these days. I think we did eliminate our third choice from the competition too early, but that is congress for you.I agree. My concern is that Boeing is being declared to be that backup when they have failed again and again and again - for a FAR higher price tag than the successful Crew Dragon.
Not knocking the other dozen Canadian astronauts, but Roberta Bondar and Chris Hadfield get you full credit to have any opinions you want.
What would have happened is ... the capsule would have been inserted into its orbit correctly and SpaceX would have discovered the problem and been able to fix it without losing a mission's worth of Starlink satellites.It's perhaps a good job they didn't spin up a Dragon Flight. That might have gone up on the Falcon 9 that launched recently and had a launch anomaly. SpaceX / NASA were fortunate that that 2nd stage that failed had only StarLink satellites on top, and not a crewed Dragon capsule.
If it had been a crew launch, goodness knows what would have happened to them. Probably - best case - a scarcely controlled reentry into a random location; pretty life threatening. Worst case - an uncontrolled reentry in the wrong orientation, and burning up.
The counterpoint to this would be the 737 Max. Mass production really doesn't have anything to do with it. It is almost certainly just a cultural issue now at Boeing.One of SpaceX's biggest advantages is that they have a culture of mass production. Mass production requires higher levels of QA automation and process standardization. The infrastructure and culture that supports mass production then gets applied to lower volume programs like Dragon as well leading to much more reliable outcomes for minimal extra cost.
Thank you for confirming that the Starliner currently in question does NOT have that capability because it was eliminated by Boeing. "Didn't configure" is functionally equivalent to "deleted" when it's going to take weeks (more?) of software updates to allow autonomous mode.Okay, this might seem pedantic, but the vehicle does have that capability. They didn't eliminate it, they just didn't configure and test the auto mode for this mission.
As I noted in an earlier comment thread, the two astronauts in question are both test pilots and are probably more comfortable with professional risk than NASA's administration is. As such, they probably won't bat an eye if NASA says they're flying home in a Starliner, but if NASA feels that prudence requires a return on a Dragon, I don't know that the astronauts should necessarily have a vote. They may have some input on their willingness to stay until February, potentially, but I have yet to hear of an astronaut turning down a longer mission in space.I would feel better if the two astronauts had the final say. After all their lives are at stake.