United Launch Alliance's Vulcan rocket failed to reach orbit Sunday, Nov. 15, losing all 40 Amazon Leo internet satellites it was carrying. The company said an anomaly struck about 10 minutes after liftoff from Cape Canaveral Space Force Station in Florida.
Spaceflight Now reported it was the first outright mission failure for ULA since the Boeing and Lockheed Martin venture was formed in 2006. The flight was Vulcan's first in nine months and the first of 38 Vulcan launches Amazon has purchased. The cause is not yet known.
Vulcan lifted off at 12:40 p.m. EST from Launch Complex 41, after a Friday scrub caused by a gaseous nitrogen plant outage and a Saturday delay tied to network problems between the rocket and ground systems. On Sunday, controllers also paused the countdown with 20 seconds left to resolve a technical issue. Reports say it is not known whether that issue played a role.
The six Northrop Grumman solid rocket boosters appeared to work normally, according to Spaceflight Now, and burned out and fell away less than two minutes into the flight. The first stage, powered by two BE-4 engines, appeared to burn longer than the pre-launch timeline called for. It also appeared to separate from the Centaur upper stage later than expected, and a telemetry-based animation showed the Centaur making unusual orientation adjustments early in its burn.
ULA's last public update, as reported by Florida Today, said the Centaur had ignited and the payload fairing had come off about six minutes after liftoff. At that point the rocket was 95 miles up and flying faster than 11,000 mph. The Centaur was planned to burn for 12 minutes 15 seconds, and Spaceflight Now said something went wrong during that burn.
ULA said it has no specific data yet on what happened and will work with Amazon and others to find the cause and return to flight quickly. "Today, we did not meet that standard," the company said, referring to its goal of mission success. Florida Today reported that NASA Administrator Jared Isaacman offered the agency's help with the investigation.
Amazon Leo, formerly Project Kuiper, is meant to compete with SpaceX's Starlink. Before Sunday, GeekWire reported, Amazon had launched 396 satellites on 14 missions since April 2025. Spaceflight Now said Sunday's flight would have raised the total to 436.
Amazon had described Vulcan as its main workhorse for the coming years. GeekWire reported the rocket is slated to carry more than 1,500 of the company's first-generation satellites. Amazon had also said a second Vulcan mission could fly within weeks, but that flight now has to wait for the investigation.
Other launch options are limited. New Glenn, on which Amazon has 24 launches reserved, has been grounded since the May explosion. Amazon's next scheduled launch is an Ariane 6 mission carrying 36 satellites, targeted for Nov. 23 at the earliest.
The Federal Communications Commission, GeekWire reported, gave Amazon permission in June to keep deploying satellites even if it missed a July 30 deadline to put 1,616 into service. Satellites not operational by then temporarily lose priority in key spectrum bands. Amazon has until July 30, 2029, to deploy and operate all 3,232 first-generation satellites, and it has said it plans an initial commercial service rollout this year.
The mission also carried more than 50,000 pounds, ULA's heaviest payload ever, and was the first to fly a shorter, optimized version of the Centaur V upper stage, according to Florida Today. Amazon's statement said launches carry risk, especially inaugural missions, and that it believes ULA will learn from this one.
ULA said Amazon and other customers will have visibility into its investigation. Spaceflight Now reported that Vulcan faces a potentially significant grounding while engineers review telemetry and implement fixes. No timeline for a return to flight has been given.
Around Prague, based on reporting by Florida Today, Spaceflight Now, GeekWire