- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
In a major setback for United Launch Alliance, the company’s new heavy-lift Vulcan rocket carrying a batch of Amazon Leo internet satellites, malfunctioned during the climb to space Sunday, dooming the payload and throwing a costly wrench into the launch schedule of both companies…
The solids appeared to work normally Sunday, helping boost the rocket out of the dense lower atmosphere before burning out and falling away. The two methane-burning BE-4 engines powering the Vulcan’s first stage then continued the climb toward orbit, but they appeared to fire longer than expected based on ULA’s pre-launch timeline…
The first stage also appeared to separate from the rocket’s hydrogen-fueled Centaur upper stage later than expected and telemetry-driven animation showed the Centaur making unusual orientation adjustments early in the burn.
ULA’s launch commentators, however, did not mention any problems and the launch broadcast came to an end without confirming whether the Centaur’s first planned engine firing went for the full duration…



The first stage engines burning longer than anticipated suggests they were operating at less than full throttle.
The likely consequence is lighting the second stage at lower than expected speed and altitude. Gravity would have tipped the nose over sideways faster than planned, resulting in a shallower trajectory through thicker than planned atmosphere. Atmospheric drag and gravity losses would have robbed the launch of critical delta-v.
After being released too low and slow, the upper stage would have tried to compensate by pitching its nose up more than planned to keep from falling back to the ground, which just delays the inevitable - it does not have enough power to keep itself airborne and the less efficient offset from prograde robs more delta-v from the mission.
The upper stage and its payload probably got toasted during its trip back into the thick lower atmosphere, probably somewhere over the eastern Atlantic Ocean.
It will be interesting to hear about the cause. Could be a software problem, damaged turbine, or more problems with the valves.