United Launch Alliance confirmed Tuesday morning that the return-to-flight mission of its Vulcan rocket began failing almost as soon as it left the pad. The company says it lost both telemetry and the mission roughly 10 minutes into the flight. For a launch meant to restore confidence in the vehicle, it is about the worst way the day could have gone.
ULA’s own account is blunt. “While we appear to have lost telemetry and the mission at approximately 10 minutes into flight, early indications are that just after liftoff, the launch vehicle experienced low booster performance, resulting in stage separation occurring when the vehicle was low in altitude and below minimal velocity to reach orbit,” the company said. Ars Technica separately reported, citing sources, that the investigation into the anomaly is complex.

What ULA says went wrong
The statement lays out a chain of events, and it is worth reading slowly. The trouble started just after liftoff, with thrust that came in lower than it should have. Because the vehicle was underperforming, it was still low and slow when the moment for stage separation arrived. At that point it did not have the velocity needed to reach orbit.
Staging is a timed event. The rocket separates when the first-stage hardware has done its work and the vehicle is high enough and fast enough for the upper stage to take over. If the boosters deliver less than planned, the vehicle reaches that moment short on both altitude and speed. Separating low and below minimum velocity means the upper stage inherits a starting point it cannot recover from.
ULA also confirmed what Ars had reported: the Centaur V upper stage and the solid rocket boosters performed nominally. That detail narrows the picture, but it also muddies it. The company says “low booster performance,” yet the solid rocket boosters are listed among the parts that behaved as expected. The statement does not say which element fell short. By elimination, the remaining piece of the stack is the first-stage core, though ULA has not named it.
A stage that did its job on a doomed trajectory
It would be easy to read “Centaur V performed nominally” as good news, and in a narrow sense it is. The upper stage did what it was told. But nominal performance on a trajectory that cannot reach orbit does not rescue a mission. An upper stage can only add so much velocity, and it cannot make up for a deficit built in during the first minutes of flight.
That is the likely reason the flight ended with a lost mission and not a degraded one. Reaching orbit means getting to a specific altitude and sustaining a specific speed. Fall short on both at the handoff and no amount of good behavior downstream closes the gap.

Why the investigation will not be quick
Ars Technica describes the investigation as complex, and the available facts show why. ULA has an unambiguous symptom: low booster performance right after liftoff. It also has a confirmed list of systems that worked. What it does not yet have, at least publicly, is the reason for the shortfall. Closing that gap means going back through the flight data, and that data stopped at about the 10-minute mark when telemetry was lost.
Telemetry is the only record investigators get of a vehicle that is gone. Every sensor reading, pressure trace and engine parameter streamed down during ascent becomes evidence. When the feed ends abruptly, whatever was happening in the final seconds may be missing. The part of the flight that matters most to the inquiry, the climb right after liftoff, happened early enough that data should exist. The ambiguity is in interpreting it.
The wording of the statement also hints at how much is unresolved. ULA says “early indications” and “appear to have lost.” That is the language of a company that has a working theory and is not ready to call it a conclusion. A low-thrust event can have more than one root cause, and the fact that the solid boosters and upper stage were fine leaves a narrower but still open field of suspects. Complexity here probably means separating a cause from its symptoms, not simply gathering more data.
The stakes extend past one lost flight. This was meant to be the mission that put Vulcan back in service, and a second setback on a return-to-flight attempt raises its own questions. ULA has not said what happens to upcoming launches, and the source material does not either.

For now there is a short list of confirmed facts: a launch that went wrong just after liftoff, a separation that came too early and too slow, and two stages that did exactly what they were supposed to. What made the third piece fall short?






