ULA Vulcan Fails on First Amazon Leo Mission

United Launch Alliance’s Vulcan rocket failed to deliver Amazon Leo’s first dedicated mission to orbit on 15 November. In a post on X at 18:30 GMT, ULA said: “Based on data received by our Launch Director, we confirm that the Vulcan vehicle launched from Space Launch Complex 41 suffered an anomaly 10 minutes into the flight and failed to deliver the Amazon mission to orbit.”

The payload was 40 broadband satellites on a flight Amazon Leo calls LV-01. Amazon Leo, quoting ULA’s post at 19:11 GMT, said: “There is risk with any launch, and that’s especially true for inaugural missions like LV-01. ULA has been a trusted partner for Amazon, and we believe they’ll learn from this mission and deliver on their long-term plans for Vulcan.”

ULA has confirmed the failure, not the cause

ULA has not identified what went wrong. The same post said: “Every flight generates data, and every flight teaches us something. Since the anomaly just occurred, we don’t have any specific data yet to understand what occurred today.” It added that the company “will work closely with our customer and other appropriate organizations to find the cause, determine the appropriate corrective action, and return to flight as quickly as possible,” and that it would provide further updates when new information becomes available.

A ULA blog post on 10 November, written ahead of the flight, described Vulcan Leo 1 as the first of 38 heavy-lift missions for expansion of the Amazon Leo broadband constellation, carrying 40 satellites from Space Launch Complex 41 at Cape Canaveral Space Force Station. The post said Vulcan was returning to flight after a solid rocket booster nozzle anomaly on a launch in February, and that changes to the nozzle design and manufacture had been incorporated into the boosters for this mission. ULA president and CEO Mark Peller, quoted in that blog, also used the line that “every flight generates data and every flight teaches us something.” The blog referred to “our first four Vulcan missions.”

William Harwood at Spaceflight Now reported that this was the first outright failure of a ULA rocket since the company was formed in 2006, and only the fifth flight of a Vulcan, the first in nine months. He wrote that the problem appeared to occur during the Centaur upper-stage burn. Spaceflight Now also reported that NASA Administrator Jared Isaacman offered NASA’s help with the investigation on X. Those points are Spaceflight Now’s reporting. ULA’s official statement does not name a failed stage or a cause.

The 10 November blog had already placed this flight in a longer Amazon Leo build-out. TSN’s earlier space roundup noted that Amazon Leo was nearing launch, and the FCC’s approval of Amazon Leo’s takeover of Globalstar’s satellite licences sits on a separate, regulatory track from the launch itself, alongside the earlier authorisation of Globalstar’s C-3 system.

A missing cause is not a temporary gap in the confirmation

The official record on the afternoon of 15 November is short and, on the point that matters most to a later investigation, deliberately incomplete. ULA has said the vehicle lifted off from Space Launch Complex 41, that an anomaly occurred 10 minutes into the flight, and that the Amazon mission was not delivered to orbit. It has also said, in the same post, that it does not yet have specific data to explain what happened. That is a confirmation of a failed mission, not a finding about a stage, a component or a weather or range factor.

The pre-launch record should be kept in the same box. The 10 November blog is a useful source for what this flight was meant to be: the first of 38 Vulcan missions for Amazon Leo, a 40-satellite load, and a return to flight after the February solid-rocket-booster nozzle anomaly. It is not a source for what failed on 15 November. The February nozzle work, the first four Vulcan flights, and the new LEO-optimised Centaur described in that blog are background. Treating any of them as the cause would go beyond what ULA has said.

Spaceflight Now’s account fills in context that ULA has not itself put in the failure statement: that this was, in that outlet’s telling, ULA’s first outright failure since 2006, Vulcan’s fifth flight and the first in nine months, and that the problem appeared to occur during the Centaur burn. Those are attributed reports, and the Centaur timing is consistent with an anomaly at the 10-minute mark on the pre-launch timeline, but it remains reporting rather than an official finding. Isaacman’s offer of NASA help, also reported there, is likewise not a finding about the hardware.

Until ULA, Amazon or a formal investigation names a cause, the facts that can be stated are the ones already on the official channels: a Vulcan lifted off from SLC-41, an anomaly occurred 10 minutes later, and 40 Amazon Leo satellites on LV-01 were not delivered to orbit. Further updates, ULA said, will come when new information becomes available.