SoylentNews

Starliner Fails to Make Journey to ISS

posted by janrinok on Friday December 20 2019, @06:31PM   
from the keep-on-trying dept.

PiMuNu writes:

https://www.bbc.co.uk/news/science-environment-50855395

The Boeing company is going to have to cut short the uncrewed demonstration flight of its new astronaut capsule.

The Starliner launched successfully on its Atlas rocket from Florida, but then suffered technical problems that prevented it from taking the correct path to the International Space Station.

It appears the capsule burnt too much fuel as it operated its engines, leaving an insufficient supply to complete its mission.

Starliner will now come back to Earth. A landing is planned in the New Mexico desert in about 48 hours.

See also:

• https://spacenews.com/starliner-suffers-off-nominal-orbital-insertion-after-launch/

• https://spacenews.com/starliner-anomaly-to-prevent-iss-docking/

---

Original Submission

• Re:off-nominalRe:off-nominal (Score: 1) by khallow on Monday December 23 2019, @09:50AM (3 children)

  by khallow (3766) on Monday December 23 2019, @09:50AM (#935440) Journal

  Ok, I read the transcript. No, you still don't get it. But let's quote that excellent question in full:

  KEITH COWLING (NASAWatch.com):Yeah. I wanted to go back to the timer thing for one moment. This is kind of a basic Spacecraft 101 thing that we've been doing for a half a century, and I'm just wondering why there wasn't a redundancy string or a backup system that would kick in or have the different systems bode with each other to see if the time was correct.And moreover, this issue of the crew possibly, you know,being in a position, had there been a crew to do something,how would they have known the timing if the timing was wrong? I mean, would they have to look at their wristwatches?And another question.You know, there's no live video from this mission, and I'm kind of wondering why because SpaceX and Russia Soyuz program do it all the time. Why is Boeing so shy about in mission—[audio break].
  
  ADMINISTRATOR JIM BRIDENSTINE:Did we lose him?
  
  JIM CHILTON:Is he still on?
  
  ADMINISTRATOR JIM BRIDENSTINE:I'm sorry. If he's speaking, we can't hear him.
  
  BETTINA INCLÁN:I think something happened with the system. Everyone from our end, there's nothing on the screen. So.
  
  KEITH COWLING (NASAWatch.com):Hello?
  
  BETTINA INCLÁN:Hi. Can you hear us? Can you hear me?
  
  KEITH COWLING (NASAWatch.com):Can you hear me?
  
  BETTINA INCLÁN:Yes.
  
  KEITH COWLING (NASAWatch.com):Okay. Do I have toask the question again?
  
  BETTINA INCLÁN:I guess where you left off.
  
  KEITH COWLING (NASAWatch.com):I don't know where I left off. Very simply, the timing system on the spacecraft,this is basic technology that we've been doing half a century. Why is it that there wasn't a redundancy string or a backup system that could detect the error like boding with one system or another to check the time? There has been mention that a crew, had there been one on the spacecraft,could have noticed this, and how would they have known the proper mission time if it was wrong? I mean, would they have had to look at their wristwatches?And, secondly, why is there no live video from this mission? Soyuz and SpaceX do it all the time. Why is Boeing so shy about providing live video?
  
  JIM CHILTON:Okay. I'll kind of start, and then I'll turn it over to Steve if he wants to go deep on the—we haven't—we haven't delved into this deep enough to answer the redundancy question,Keith. So I just don't know. Obviously,that's a great idea, and in fact, we'll go see why what we had in there didn't perform as expected.On the crew, they wouldn't have been timer activated. They would have been on a mission profile and said, hey, I didn't—they would have known based on spacecraft instruments, "I didn't leave where I wanted to be," and we would have had voice-to-ground and said, "Go do an orbital insertion burn." And they would have done that manually. This spacecraft lets the crew take over at any time. So we wouldn't have been as dependent on those com links.From a Boeing video standpoint, the choice we made on this flight test was just to record it, and had—once we were docked with the Station, all that could have come down through the Station. We just chose to record it and then release it once we land. We thought we'd be sending it down from the Station at about the time we opened the hatch, but since we didn't rendezvous,unfortunately, we don't have it. So it wasn't a "we're not transparent." It was just we architected the avionics not to—on this very first live test not to send it in real time.And, Steve?
  
  STEVE STICH:And I'll add a little bit more to the crew. I mean, what the crew would have done when the spacecraft separated from the launch vehicle, they would have noticed an extreme amount of jet firings. They would have noticed that the guidance mode was in the wrong mode for where they should have been.They could have went free drift and stop those thruster firings and just kind of flown the spacecraft manually. This spacecraft has a manual capability to bypass the flight computers, which is a very elegant design. They could have gone to the manual mode.And then the crew is also trained to know that "I need to execute a maneuver at about 31 minutes to get the vehicle into orbit," and so they could have gone to a manual mode of the software and executed a—or manual mode and executed a burn at approximately 31 minutes to just get the vehicle into orbit safely and at that point then work to recover com.They also—there's a manual capability with the com system to where if there's something going off nominal with pointing to TDRS, the crew can actually command various antennas and decide to get a com link. So having been in the ops world in the past, I think the crew would have methodically worked those steps, recovered com, talked about executing a burn if they got com back with the ground, and then executed that burn and got us in a safe orbit. And then we can recover the rest of the mission.

  So yes, it was a subtle timing issue that caused the mission to fail. And yes, that sort of thing is systemic, which shows that there likely are other such subtle problems that could kill missions and perhaps crew in the future.
  
  But you got it completely wrong. Redundancy (or rather vastly more mission redundancy) is not a panacea for whatever breaks. It adds things that can break as well. And it takes up mass, volume, and mission capabilities. Nor are the presence of the above problems of the press conference an indication that Boeing's effort has somehow gone off the rails. That's the whole point of flying unmanned missions now - to find this stuff and get a working vehicle. Meanwhile, a genuine "million failsafes" means you don't fly, for one reason or another.
  
  Sure, a spacecraft is complex, but it's not that complex. Slapping more redundancy on it isn't a long term solution. Testing it repeatedly so that you can figure out what parts need redundancy and what parts don't is a better approach.

  Parent

• Re:off-nominalRe:off-nominal (Score: 0) by Anonymous Coward on Monday December 23 2019, @03:55PM (2 children)

  by Anonymous Coward on Monday December 23 2019, @03:55PM (#935517)

  Now you're just babbling because you know you're wrong so the mental gymnastics kicks in to avoid acknowledging that. Keep this up and you'll be voting democrat before you know it.

  The Delta IV has a payload capacity on the order of 50,000 pounds depending on the orbit. The Atlas V around 30,000. Redundancies and redundancies for your redundancies have a negligible mass cost - and provide unimaginable value. There's no technical reason they didn't include redundancies. We're not even talking some hugely complex stuff. Boeing is screwing up things as simple as mission timing. Many of these redundancies can be entirely implemented in software and with negligible scale hardware redundancies working as redundancies for your redundancies. The one and only problem here is Boeing. They're an incapable relic of a company that would have crashed and burned long ago if not for their position at the height of crony capitalism, alongside their coasting off inertia and taking credit for what entirely different people under an entirely different company, that happened to share the same name, achieved decades ago.

  Parent

  • Re:off-nominal(Score: 1) by khallow on Tuesday December 24 2019, @01:19AM

    by khallow (3766) on Tuesday December 24 2019, @01:19AM (#935720) Journal

    Redundancies and redundancies for your redundancies have a negligible mass cost

    Nonsense, particularly when you get to engine systems and life support.

    and provide unimaginable value

    Sorry, I can "imagine" quite well their value. That's why I'm complaining in the first place.

    Many of these redundancies can be entirely implemented in software and with negligible scale hardware redundancies working as redundancies for your redundancies.

    Then they aren't redundancies. No amount of software can replace a bad engine or life support system.

    Parent

  • Re:off-nominal(Score: 1) by khallow on Tuesday December 24 2019, @03:54AM

    by khallow (3766) on Tuesday December 24 2019, @03:54AM (#935784) Journal

    I see the Starliner just landed without major damage. So despite the alleged problems, it still operated pretty well. I think this brings up one of the strategies more important than some imaginary level of redundancy, namely, aborts. When not if things don't work out, it's better to have a plan B than to have a backup doodad.

    Parent