Skip to Content

NASA: A second, unreported glitch could have wrecked Boeing’s Starliner

February 7, 2020
Boeing Starliner
Boeing StarlinerBoeing

NASA safety officials have revealed that the Boeing Starliner’s failed attempt to dock with the International Space Station last December—the vehicle’s first ever flight into space—was marked by multiple software problems, not just the error that had been previously disclosed. In fact, they say, a second issue put the spacecraft at risk of a “catastrophic” failure.

The first glitch: We already knew that Starliner’s December 20 mission, an uncrewed test flight, ended early when the spacecraft’s engines did not burn as intended. This was due to a faulty internal timer, as previously reported. The issue meant it was unable to rendezvous with the ISS, and returned to Earth just 48 hours later. NASA now says a coding error caused Starliner to pull its time from the mission’s Atlas V launch vehicle, creating an 11-hour mismatch. 

The second glitch: But now NASA has revealed there was a second coding error, this time in the sequence that governs Starliner’s preparation for reentry into Earth’s atmosphere. If it had not been addressed, Starliner would have erroneously fired its thrusters, resulting in uncontrolled motions that could have made the service module collide with the crew module—potentially damaging the crew module’s heat shield, or causing it to tumble dangerously during descent.

The glitch was caught and fixed by ground crews the night before the spacecraft returned to Earth. Jim Chilton, a senior vice president at Boeing, says the glitch wouldn’t have been found if the timer error hadn’t prompted mission control to look for more faults in Starliner’s software.

Rising concerns: Neither NASA nor Boeing had given any previous indication of more than one issue, although both organizations became aware of the problems during the mission. The coding errors should have been noticed in multiple checks conduced by both parties, officials said. “Our NASA oversight was insufficient,” says Doug Loverro, the head of human spaceflight at NASA.

What’s next: NASA’s independent review panel is recommending a complete review of Boeing’s software verification process, and Boeing plans to re-review all of Starliner’s software—more than one million lines of code. 

The panel is still finishing its own review of the mission and craft. NASA has still not given any indication of how these new revelations will affect Starliner’s 2020 time line, and whether it will require another uncrewed test flight to the ISS before Starliner can take people into space. A decision is expected by the end of February.

Deep Dive


The search for extraterrestrial life is targeting Jupiter’s icy moon Europa

NASA’s Europa Clipper mission will travel to one of Jupiter's largest moons to look for evidence of conditions that could support life.

How to safely watch and photograph the total solar eclipse

The solar eclipse this Monday, April 8, will be visible to millions. Here’s how to make the most of your experience.

How scientists are using quantum squeezing to push the limits of their sensors

Fuzziness may rule the quantum realm, but it can be manipulated to our advantage.

Stay connected

Illustration by Rose Wong

Get the latest updates from
MIT Technology Review

Discover special offers, top stories, upcoming events, and more.

Thank you for submitting your email!

Explore more newsletters

It looks like something went wrong.

We’re having trouble saving your preferences. Try refreshing this page and updating them one more time. If you continue to get this message, reach out to us at with a list of newsletters you’d like to receive.