NASA confirms seriousness of 2nd Starliner software issue
At a press conference today, NASA and Boeing officials confirmed the rumors that there was a second software error during Starliner’s unmanned demo mission in December that might have caused a serious failure had it not been caught on time.
[After the first software error], engineers began reviewing other critical software sequences as a precaution and discovered yet another problem. Software used to control thruster firings needed to safely jettison the Starliner’s service module just before re-entry was mis-configured, set for the wrong phase of flight.
Had the problem not been found and corrected, the cylindrical service module’s thrusters could have fired in the wrong sequence, driving it back into the crew module and possibly triggering a tumble or even damaging the ship’s protective heat shield.
While a detailed analysis was not carried out at the time, “nothing good can come from those two spacecraft bumping back into one another,” said Jim Chilton, a senior vice president for Boeing Space and Launch.
That two different software errors were not caught prior to flight has NASA demanding a complete review of Boeing’s quality control systems. And NASA here is correct. Boeing as a company appears to have fundamental quality control issues up and down the line, in all its projects. A complete review appears warranted.
At a press conference today, NASA and Boeing officials confirmed the rumors that there was a second software error during Starliner’s unmanned demo mission in December that might have caused a serious failure had it not been caught on time.
[After the first software error], engineers began reviewing other critical software sequences as a precaution and discovered yet another problem. Software used to control thruster firings needed to safely jettison the Starliner’s service module just before re-entry was mis-configured, set for the wrong phase of flight.
Had the problem not been found and corrected, the cylindrical service module’s thrusters could have fired in the wrong sequence, driving it back into the crew module and possibly triggering a tumble or even damaging the ship’s protective heat shield.
While a detailed analysis was not carried out at the time, “nothing good can come from those two spacecraft bumping back into one another,” said Jim Chilton, a senior vice president for Boeing Space and Launch.
That two different software errors were not caught prior to flight has NASA demanding a complete review of Boeing’s quality control systems. And NASA here is correct. Boeing as a company appears to have fundamental quality control issues up and down the line, in all its projects. A complete review appears warranted.
