The first crewed voyage of Boeing's Starliner was supposed to last around a week, but the high-stakes mission is still in limbo eight weeks after launch.
The first crewed voyage of Boeing's Starliner was supposed to last around a week, but the high-stakes mission is still in limbo eight weeks after launch.
Their high-stakes mission was supposed to last about a week — but 56 days later, two NASA astronauts are still aboard the International Space Station, waiting as teams on the ground try to figure out how to bring them home safely in the Boeing spaceship they rode to orbit.
The beleaguered Starliner capsule has two problems: its propulsion system is leaking helium and five of its thrusters malfunctioned as it was docking with the space station. Mission managers were aware of the leaks before the vehicle lifted off but had said they were unlikely to affect the flight or the astronauts’ safety.
If your flight is on a Boeing aircraft, you’re likely in the same situation as the astronauts.
What I can’t understand about this situation, is they’ve apparently been studying the craft’s helium leaks this whole time. But, as far as I’m aware, they’ve done 1 EVA to look at the thing. How are they inspecting the physical condition of hardware(pipes, seals, welds, brazed joints) via software from the ground and the results of one EVA. I also can’t see NASA giving the green light to really strip the Starliner to the guts while it’s attached to the space station, so did the astronauts even get a chance to look closely to find these leaks. A quarter of my job is finding leaks in high pressure piping systems, and you often have to really get in there and remove all the panels to pinpoint a leak. I highly doubt nasa has allowed the crew to rip apart a space capsule the same way I would rip apart a rooftop unit.
What I can’t understand about this situation, is they’ve apparently been studying the craft’s helium leaks this whole time. But, as far as I’m aware, they’ve done 1 EVA to look at the thing. How are they inspecting the physical condition of hardware(pipes, seals, welds, brazed joints) via software from the ground and the results of one EVA.
The thing that takes the most time isn't looking at the thing, it's doing the engineering to figure out WTF you're going to do about it afterward.
How are they inspecting the physical condition of hardware(pipes, seals, welds, brazed joints) via software from the ground and the results of one EVA.
Well, there are a whole lot of sensors and monitors on all of the hardware in that capsule, and all that data gets collected. So they can tell a lot about what's going on with the capsule even remotely. But it's still a lot of data to dig through and analyze.
And then once you identify the problem it's like... "well the temperature on component X went way past its lower limit and one section of the fuel line went way over pressure and this third sensor isn't responding at all", so... now you know some things, but that might not immediately tell you what exactly happened, or why it happened. And then once you figure out why it all happened, there's trying to figure out how to prevent it reliably without introducing new problems.
And I think you're right that it is actually pretty hard for the engineers to do all that without physically being there. I wouldn't be surprised if a lot of the slowdown is due to needing to replicate the problem in simulations or physical mockups down on earth.
Based on my knowledge gained by watching multiple space station related movies there are several emergency escape capsules up there, so they aren’t technically stranded until those don’t work also.
There is also at least one astronaut up there who smuggled a pack of chewing gum that can be used to plug the leaks once all other options are exhausted, but he hasn't told anyone because he'll get in trouble.
Mission managers were aware of the leaks before the vehicle lifted off but had said they were unlikely to affect the flight or the astronauts’ safety.
So managers made that decision? Not engineers? Rocket scientists?
So they are all jockeying over who is going to fall on their sword when this ship blows up on reentry. We're going to hear later about an engineer who tried to put a stop to it but was overruled because there was only a 30% chance of everything going to hell. It's the Challenger all over again in slow motion.
Just scuttle the ship and send a rescue mission. And fire whoever they are throwing under the bus, since that's the only closure we're likely to get.
The leaks were examined and found to benon-critical. They were even controllable. No helium has leaked since docking with ISS and there is plenty to get home.
The problem has been the crew capsule and the space propulsion module are 2 different pieces. The capsule comes home. The propulsion module gets ditched in space. NASA and Boeing have been taking their time to review the propulsion module (leaks and all) while docked at ISS because they can't bring it home.
Nothing much has changed from all that. NASA is in control of the mission. It's all proceeding at their pace. I wouldn't trust any spin Boeing makes. But watching the NASA mission reports shows there isn't much reason for concern.
Mission Manager is a technical role, not a managerial position. They might also be people managers, but the role is about managing the mission. And even if they are also people managers, they had to be engineers or scientists first to start working at NASA.
And I think they can't simply scuttle the ship. I read they need humans in the ship to get it to properly disconnect from the station.
I think or hope that these managers were engineers in the past but at the same time wont be surprised if they are not. I mean like, isn't it a thing in the aerospace or any engineering industry to promote engineers up until they become managers and such? It does feel like Challenger 2.0 :( hope they return safely.
Technical people that move into management usually (but not always) suffer from something I’ve started calling management brain rot. They’re exposed to the spreadsheet warriors and their corporate jargon, and it doesn’t take long for the good ones to give up and the bad ones to thrive in a, let’s call it, “low-information environment.”
Yeah. I was in Hawaii when 9/11 happened, and of course all flights at the time were canceled for days. It wasn't a bad place to be stuck for a little while, but even that short of a delay in returning did cause a few issues.
I do love that Boeing is like "we have no idea what the fuck went wrong. Here's the data cause we give up." Boeing sure is turning de a new leaf and putting safety first. /s
Starliner thrusters all passed 3 hot fire simulations of a return mission. Probably fine to fly home.
Ground testing was able to match what happened to the thrusters on approach. NASA now more confident the theory around fuel flow restrictions was correct.
Catch is they'll never know for sure because the thrusters in space can't be taken apart to examine. And they won't make it back to Earth because they're on a portion that detaches before re-entry.
The rumors around using Dragon for a return mission are true. But in that NASA has had time to think up multiple scenarios that weren't ever possible prior for return missions. There are now around 4-5 options thought up. NASA might go on to test some of those ideas out.
ISS has so many ships docked, with more planned, that a decision on Starliner is happening soon. Regardless of if people are aboard, it needs to leave ISS by September if I was following along correctly.
If they actually send up a SpaceX capsule to pick them up, they should not fly empty. They should take the managers responsible for this project up, and let them return in the Boeing capsule.