On a Sunday in Florida, a Vulcan rocket climbed off the pad at Cape Canaveral carrying forty satellites meant to knit Amazon's internet network closer to the globe, and ten minutes later it fell silent over its own promise. Launches have always been a wager against physics, and this one ended as many do, with a rocket that did not finish its sentence and cargo that will never reach orbit. The cause is still hidden in the telemetry, and the engineers who built and flew the machine are now the ones who must read what it left behind. For the American effort to put a web of machines above the eart
Boeing-Lockheed Vulcan Rocket Fails Mid-Flight, Losing 40 Amazon Leo Satellites
Every flight teaches us something, ULA said, ten minutes after losing 40 satellites
Forty satellites gone in one launch. Why does this one land so hard for ULA?
Because it's the first total mission failure since the company formed in 2006. Until Sunday, its record of successful deliveries was unbroken.
And this was Vulcan's fifth flight, after a nine-month gap?
Yes. The gap followed investigations into the solid rocket boosters and the BE-4 engines, which Blue Origin supplies.
Careful with the engines, though. Does the reporting say they caused this?
No. It says it's unclear whether the BE-4s played any role. ULA itself says it has no specific data yet.
So the cause is simply unknown right now. The earlier valve problem is background, not an explanation.
What does it mean for the Space Force?
Its national security launches were already paused. Sunday's flight was supposed to supply data toward clearing Vulcan, and now that picture is murkier.
And the claim that Vulcan could be grounded for months is an expectation, not an announced timeline.
Right. What about Amazon?
It had 398 satellites up, about 12% of the 3,236 needed, and hoped to begin service this year. Starlink has more than 11,000.
The Pulse
- A Vulcan rocket lost all forty Amazon Leo satellites about ten minutes after liftoff from Cape Canaveral, a total mission failure that has no precedent in ULA's history.
- The launch was supposed to open a steady run of flights for Amazon's internet network, and now that schedule has been torn open just as rivals race ahead.
- Vulcan had only just returned to flight after nine months of investigations into its boosters and Blue Origin-supplied engines, leaving engineers to ask whether old problems resurfaced.
- The Space Force's pause on national security launches may now stretch for months, while US launch capacity narrows as SpaceX stops taking new bookings for Falcon 9.
- Engineers are combing through flight data to find the cause, and Amazon is calling the failure a risk of new rockets and promising the partnership will endure.
On a Sunday in Florida, a Vulcan rocket climbed off the pad at Cape Canaveral carrying forty satellites meant to knit Amazon's internet network closer to the globe, and ten minutes later it fell silent over its own promise. Launches have always been a wager against physics, and this one ended as many do, with a rocket that did not finish its sentence and cargo that will never reach orbit. The cause is still hidden in the telemetry, and the engineers who built and flew the machine are now the ones who must read what it left behind. For the American effort to put a web of machines above the earth, it is one more reminder that the sky remains a patient and unforgiving teacher.
About ten minutes after a Vulcan rocket lifted off from Cape Canaveral Space Force Station in Florida on Sunday, something went wrong. The rocket never delivered its 40 Amazon Leo internet satellites to orbit, and all of them were lost.
The Vulcan is flown by United Launch Alliance, the joint venture of Boeing and Lockheed Martin. The company said it had no data yet to explain the anomaly, noting that every flight generates data and teaches something. It is the first total mission failure in ULA's history, a record that had held since the company was formed in 2006. The flight was also meant to start a regular cadence for Amazon's satellite program, making the loss a serious setback for ULA's flagship rocket.
Sunday's flight was only Vulcan's fifth since its 2024 debut and its first in nine months. That gap followed investigations into the solid rocket boosters and the BE-4 engines supplied by Blue Origin. Whether those engines played a role on Sunday remains unclear. The Space Force had already paused its national security launches, and this mission was expected to provide data before any decision to resume them. A lengthy investigation could now ground Vulcan for months.
The timing is difficult for US launch capacity, and Amazon trails SpaceX's Starlink, which has more than 11,000 satellites. Amazon said launches always carry risk, especially inaugural ones, and expressed confidence in ULA. The cause of the failure and the length of the grounding are the questions to watch.
About ten minutes after a Vulcan rocket lifted off from Space Launch Complex 41 at Cape Canaveral Space Force Station in Florida on Sunday, something went wrong. The rocket never delivered its cargo of 40 Amazon Leo internet satellites to orbit, and all of them were lost.
The Vulcan is flown by United Launch Alliance, a joint venture of Boeing and Lockheed Martin. In a statement, ULA said its Launch Director had confirmed, based on the data received, that the vehicle suffered an anomaly ten minutes into the flight and failed to deliver the Amazon mission. The company said it had no specific data yet to explain what happened, adding that every flight generates data and teaches something.
The failure is the first total mission failure in ULA's history. The company was formed in 2006 by merging Boeing's Delta rocket program with Lockheed Martin's Atlas program, and until Sunday it had a record of successful deliveries since then. The launch was also meant to begin a regular cadence of flights for Amazon's growing satellite internet program, so the loss is a significant setback for ULA's new flagship rocket.
Sunday's flight was Vulcan's fifth since its debut in 2024 and its first in nine months. That gap followed separate investigations into the rocket's solid rocket boosters and its core BE-4 engines, which are supplied by Blue Origin, the company founded by Amazon's founder, Jeff Bezos. The boosters had drawn scrutiny after anomalies on Vulcan's previous two flights, including a February 2026 mission for the US Space Force. Both of those missions still put their payloads into orbit. The engine investigation traced a problem to the engine's main oxygen valve. Blue Origin developed modifications, and ULA officials said the engines installed on Vulcan were retrofitted. Whether the BE-4 engines played any role on Sunday remains unclear.
The Space Force had paused Vulcan's national security launches pending the investigation and corrective measures. Sunday's Amazon mission was expected to supply more data before the military decided whether to clear the rocket for those flights. A lengthy technical investigation is now expected, and it could ground Vulcan for months.
That comes at a tight moment for US launch capacity. Other rockets have failed, the industry faces wider challenges, and the future availability of SpaceX's Falcon 9, the world's most active rocket, is uncertain. SpaceX is no longer accepting bookings for it. Blue Origin's New Glenn exploded in May during a ground test, just days before it was due to launch Amazon Leo satellites.
Amazon, in a statement, said there is risk with any launch, especially inaugural missions like this one, designated LV-01. It called ULA a trusted partner and said it believes the company will learn from the mission and deliver on its long-term plans for Vulcan.
The losses compound Amazon's difficulty competing with SpaceX's Starlink, which has more than 11,000 satellites and millions of customers worldwide. SpaceX launches on its own rockets, while rivals depend on outside providers, which adds cost and complexity. According to Reuters, Amazon had launched 398 Leo satellites across 14 missions since 2025 before Sunday, about 12% of the 3,236 it needs for global coverage. It had hoped to begin initial internet service this year. The cause of Sunday's failure, and how long Vulcan stays on the ground, are the questions to watch.
Notable Quotes
Since the anomaly just occurred, we don't have any specific data yet to understand what occurred today.— United Launch Alliance statement
Amazon said it believes ULA will learn from the mission and deliver on its long-term plans for Vulcan.— Amazon statement