2020 Feb 10, 8:28am
421 views 7 comments
The Starliner’s failure to execute the orbit insertion burn was blamed on software that incorrectly set the spacecraft’s internal clocks based on data retrieved from the Atlas 5’s flight control system. The Starliner code should have retrieved the time during the terminal countdown, after the Atlas 5’s clocks were precisely set for launch.Instead, the Starliner computer retrieved the time used during an earlier countdown sequence and as a result, its timer was 11 hours off from the actual time. That, in turn, threw off the timing of downstream post-launch events like the orbit insertion burn.With that problem finally corrected, 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.
We need an Operation Paperclip Seance to channel the dead nazis to save this project.
We should not do engineering in house, instead outsource it to Bangalore for $3/hr while increasing executive compensation by $TRILLION and increasing bribes to politicians by $BILLION. WIN-WIN!
Except you neglected extort the government for billions plus favoritism passing laws to crush everyone else.
That’s exactly what Boeing does. Except you neglected extort the government for billions plus favoritism passing laws to crush everyone else.