After being successfully placed in a preliminary orbit by ULA’s Atlas 5 rocket early this morning, Boeing’s Starliner capsule failed to reach its required orbit for docking with ISS when its own rocket engines did not fire properly at the right time.
The orbit it is in is stable, and the spacecraft is undamaged. Engineers now plan to bring it back to Earth on Sunday, landing at White Sands, New Mexico.
It appears some software issue had the capsule fire its own rockets either at the wrong time or for too short a time. The spacecraft was then in the wrong orbit, and needed to use too much fuel to correct this issue, making it impossible to dock with ISS.
More information here:
However, for reasons Boeing engineers do not yet understand, Starliner’s Mission Event Timer clock malfunctioned, causing the vehicle to think it was at a different point in the mission and at a different time in its mission that it actually was.
…This resulted in Starliner’s Reaction Control System thinking the Orbit Insertion Burn was underway and executing a series of burns to keep the vehicle oriented in the insertion burn attitude; however, the Orbit Insertion Burn was not actually occurring.
When mission controllers realized the issue, they sent manual commands to Starliner to perform an Orbit Insertion Burn in a backup window that came roughly eight minutes after the planned maneuver. However, a known and brief gap in NASA satellite communications caused a further delay.
By the time Starliner was finally able to burn its engines and get into a stable orbit, it had burned 25% more propellant than anticipated.
Boeing is certainly not having a good year. First it has had to shut down production on its new 737-Max airplane due to several crashes caused by software issues. Next its SLS rocket for NASA has had endless cost overruns and delays. Now Starliner fails during its first launch.
For ULA, however, the Atlas 5 rocket performed exactly as planned, so this launch gets listed as a success. They have now completed 5 launches this year.