Two Software Flaws Almost Caused Boeing to Lose Starliner During December Test

A United Launch Alliance Atlas V rocket with Boeing’s CST-100 Starliner spacecraft onboard is seen as it is rollout out of the Vertical Integration Facility to the launch pad at Space Launch Complex 41 ahead of the Orbital Flight Test mission, Wednesday, Dec. 18, 2019 at Cape Canaveral Air Force Station in Florida. The Orbital Flight Test with be Starliner’s maiden mission to the International Space Station for NASA's Commercial Crew Program. The mission, currently targeted for a 6:26 a.m. EST launch on Dec. 20, will serve as an end-to-end test of the system's capabilities. Photo Credit: (NASA/Joel Kowsky)

Boeing and SpaceX are working toward crewed launches for their new spacecraft this year, but there have been setbacks for both companies. While SpaceX seems to have moved past its issues from last year, Boeing is still addressing the failed test flight from December. NASA and Boeing have jointly provided an update on the investigation, which cites three errors in the CST-100 Starliner test flight. Two of the issues are severe enough that they would have caused the loss of the capsule without intervention by the ground crew. 

In December, Boeing was supposed to show everyone that the Starliner was able to launch and autonomously navigate to the International Space Station (ISS). However, unspecified software errors caused the Starliner to enter the wrong orbit and miss its ISS rendezvous. At the time, Boeing claimed the incident had a connection to the mission timer that was supposed to control the orbital burn. The full story is a bit more nuanced, though. 

The mission elapsed timer (MET) was one of the three issues cited in the report. The spacecraft thought it was in a later part of the mission, causing it to fire the thrusters and waste fuel. We now also know that ground control had to step in and stop the CST-100 from continuing to burn fuel in that manner. The team had no choice but to redirect the spacecraft so it would make it into a stable orbit. 

Separately, there was an issue with the Starliner’s Service Module (SM) Disposal Sequence. This is supposed to trigger the automated release of the SM before reentry, but the system didn’t properly register with the flight controller. The team on the ground had to step in and make propulsion changes to save the spacecraft (again). 

Boeing’s CST-100 Starliner spacecraft passes by the Vehicle Assembly Building at NASA’s Kennedy Space Center in Florida on Nov. 21, 2019.

The last issue is still under investigation, so we can’t say how severe it is or how it contributed to the mission failure in December. NASA reports that the Starliner suffered intermittent communication glitches that impeded ground control’s ability to control the spacecraft. We should have more information about this in the future. 

The update does seem surprisingly candid for a public-facing blog post. NASA says Boeing’s quality controls should have detected the software abnormalities at multiple points, and the problems with this mission suggest a basic breakdown in Boeing’s processes. It’s unclear how NASA will move forward, but it probably won’t let Boeing fly any people to space until the company can satisfactorily explain and fix the issues.

Now read:

• NASA Astronaut Accused of World’s First ‘Space Crime’ Denies Allegations
• NASA’s Space Launch System May Have Set Back Orbital Refueling by a Decade
• Boeing Completes CST-100 Starliner Parachute Testing

sourse ExtremeTechExtremeTech https://ift.tt/38bpIcL