Skip to main content Scroll Top
ULA’s Vulcan Failure Destroys 40 Amazon Leo Satellites and Puts Launch Plans Under Pressure

United Launch Alliance’s Vulcan rocket suffered an in-flight anomaly about ten minutes after liftoff on 15 November, failing to deliver 40 Amazon Leo broadband satellites to orbit. The loss is a major setback for Amazon’s satellite-internet programme and marks the first total mission failure in ULA’s history. The company says it has not yet analysed enough flight data to identify the cause, so the failure should not be attributed to a particular engine or stage before the investigation is complete.

40 satellitesAmazon Leo spacecraft lost with the mission
T+10 minutesULA placed the anomaly about ten minutes after liftoff
First total failureThe first complete mission failure in ULA’s history

A return-to-flight mission ends in a major loss

A United Launch Alliance Vulcan rocket failed to deliver its payload to orbit on 15 November 2026, destroying 40 Amazon Leo broadband satellites. The rocket lifted off from Space Launch Complex 41 at Cape Canaveral Space Force Station in Florida. ULA said the vehicle suffered an anomaly about ten minutes into flight and did not deliver the Amazon mission to orbit. The company’s statement came after the launch broadcast ended without a successful payload deployment.

The failure is significant for both companies. For ULA, it is the first total mission failure since the joint venture between Boeing and Lockheed Martin was formed in 2006. For Amazon, it removes a large batch of spacecraft from a constellation that is intended to compete in the satellite-internet market. The cause remains unknown, and the company has said it needs to analyse the flight data before identifying what went wrong.

What happened during the flight

The Vulcan mission, designated Amazon Leo LV-01, was carrying 40 broadband satellites in a single launch. The early part of the flight appeared to proceed normally: the solid rocket boosters separated, the first-stage BE-4 engines operated and the payload fairing was jettisoned. The anomaly occurred around ten minutes after liftoff, before the rocket could complete the planned sequence and deploy the satellites. ULA confirmed that the vehicle failed to deliver the mission to orbit.

The exact failure point has not been confirmed. Reports described unusual behaviour during the upper-stage phase, but ULA’s initial statement did not identify the affected component. It would be premature to conclude that the BE-4 engines, solid boosters or Centaur upper stage caused the failure. A rocket can lose a mission because of propulsion, guidance, separation, software, structural or other issues, and the investigation must distinguish the initiating event from any downstream effects.

Why the loss matters to Amazon Leo

Amazon Leo is building a low-Earth-orbit satellite network intended to provide broadband connectivity. The company has said the planned constellation will eventually include thousands of satellites, with spacecraft deployed in batches by several launch providers. The 40 satellites lost on Vulcan were a substantial payload, and the failure adds delay and uncertainty to a programme already competing against SpaceX’s Starlink, which has a much larger operating constellation.

Reuters reported that Amazon had deployed 398 of the 3,236 satellites it says are needed for global coverage at the time of the failure. The company had hoped to begin initial service during 2026, but the loss of a large batch makes the deployment schedule more difficult. Amazon has bought a series of Vulcan launches as part of its broader launch strategy, so the impact is not limited to one mission: future flights may depend on the outcome of the investigation and any corrective actions.

Vulcan’s role in the US launch market

Vulcan was developed to replace ULA’s Atlas V and Delta IV families for national security and commercial missions. It uses two Blue Origin BE-4 engines on the first stage and can be configured with solid rocket boosters to increase lift capability. The rocket is designed to support a range of payloads, from commercial satellites to national security spacecraft that require specific orbits and launch assurance.

The vehicle’s debut took place in 2024, and the November 2026 flight was its fifth mission. The failure therefore arrives at a sensitive point in the programme. Vulcan is intended to be a central part of ULA’s future manifest, including missions for the US Space Force and commercial customers. A lengthy investigation or grounding could complicate schedules for customers who have limited alternatives for particular payload sizes, orbits and security requirements.

The investigation will determine how long Vulcan stays grounded

ULA said it would work with Amazon and other appropriate organisations to identify the cause and determine corrective action. The company also said it had not yet analysed enough flight data to understand the anomaly. That is a normal early stage of a launch investigation: engineers first preserve telemetry, reconstruct the vehicle’s behaviour and identify when the flight began to depart from its planned trajectory. Only then can they narrow the likely causes and test them against hardware, software and manufacturing records.

The investigation may require analysis of recovered components if any are available, review of production and inspection records, and testing of similar hardware. Regulators and government customers may also review the findings before authorising a return to flight. The length of the process will depend on the complexity of the anomaly and whether the corrective action requires redesign, additional testing or changes to operating procedures. No reliable return-to-flight date can be given until those steps are complete.

A launch failure does not automatically implicate the engines

The BE-4 engines are a visible part of Vulcan’s architecture because they power the first stage, but the available information does not establish that they caused this failure. ULA’s statement placed the anomaly around ten minutes into the flight, after the initial ascent phase. That timing may focus investigators on the upper-stage sequence, but a timeline alone cannot identify the cause. A fault in an earlier system can also produce symptoms later in the flight.

Blue Origin, which manufactures the BE-4 engines, is expected to assist with the investigation as part of the wider programme partnership. That does not mean the engines are responsible. A rigorous inquiry will examine all relevant systems and avoid assigning blame before the evidence is complete. The same discipline applies to the solid boosters, stage separation hardware, guidance systems and the Centaur upper stage.

The failure follows earlier technical scrutiny

Vulcan’s return-to-flight mission came after a nine-month gap from its previous flight and earlier reviews involving a solid rocket booster nozzle issue. ULA and Northrop Grumman had carried out testing and made changes to the booster nozzle design and manufacturing process before the November mission. The flight was also the first Vulcan launch to use six solid rocket boosters, giving the vehicle a high-energy configuration for the large Amazon Leo payload.

The earlier technical work should not be conflated with the current failure. ULA has not said that the booster nozzle issue caused the November anomaly. It is possible that the investigation will identify an unrelated issue in another stage or system. What the history does show is that a new launch vehicle can face several qualification and operational challenges as it moves from early flights into regular service.

The wider consequences for commercial satellite deployment

The loss of 40 satellites is a setback for Amazon’s constellation, but it also highlights the concentration risk that comes with large batch launches. Sending many spacecraft on one rocket can lower deployment costs and speed up constellation buildout, but a single launch failure can remove a large portion of planned capacity at once. Operators therefore balance the economics of rideshare and batch deployment against the risk of losing many satellites together.

Amazon has contracted multiple launch providers, including ULA, to reduce reliance on a single rocket family. However, the available alternatives have different payload capacities, launch schedules and mission constraints. If Vulcan remains grounded for an extended period, Amazon may need to rearrange deployment plans, use other providers where possible or accept delays. The incident could also prompt customers to review how they distribute spacecraft across launch vehicles and how much spare capacity they keep in orbit.

What it means for competition with Starlink

The Amazon Leo programme is intended to compete in a market where SpaceX has a major head start. Starlink already operates a large network and has developed a high launch cadence using reusable Falcon 9 rockets. Amazon’s strategy relies on a mix of launch providers and a large satellite constellation, but it must still reach sufficient scale to offer reliable coverage and compete on performance, pricing and service availability.

The Vulcan failure does not decide the outcome of that competition. Amazon has other contracted launch options and the company can adjust its schedule. But the loss of a 40-satellite batch adds cost and delays at a time when deployment pace matters. It also underlines the importance of launch reliability: a constellation can only grow as quickly as its satellites can be manufactured, integrated and delivered to the correct orbits.

The next milestones to watch

The immediate milestones are ULA’s preliminary investigation updates, any public findings about the flight anomaly and decisions by the relevant authorities about Vulcan’s status. Customers will want to know whether the issue is confined to one vehicle configuration or points to a wider design or process problem. The next launch date should not be treated as firm until the investigation has produced a clear corrective-action plan and the required testing is complete.

For Amazon, the key questions are how quickly replacement satellites can be built and launched, whether the initial service timeline changes, and how the company distributes future spacecraft across providers. For ULA, the priority is to demonstrate that the failure has been understood and that corrective measures work. The long-term credibility of Vulcan will depend less on the first statement after the anomaly than on the quality and transparency of the investigation and the performance of subsequent flights.

Frequently asked questions

How many Amazon Leo satellites were lost?

Forty Amazon Leo satellites were aboard the Vulcan rocket and were lost when the vehicle failed to deliver the mission to orbit.

What caused the Vulcan rocket failure?

The cause has not been established. ULA said the rocket suffered an anomaly about ten minutes after liftoff and that it needed to analyse the flight data before identifying what happened.

Will Vulcan be grounded?

A return-to-flight decision will depend on the investigation and corrective actions. No reliable return date can be confirmed until ULA and relevant authorities complete their reviews.

Related Posts
Clear Filters

Starship Flight 15 completed 14 Earth orbits and returned its ship stage to a successful tower catch, while the Super Heavy booster aborted its own catch attempt and splashed down in the Gulf of Mexico.

ESA’s Hera spacecraft is approaching the Didymos system to measure the aftermath of NASA’s DART impact. Its close-up survey could improve how scientists plan future asteroid-deflection missions.

Perseverance has confirmed macromolecular organic carbon in two ancient Jezero crater mudstones. The finding strengthens the case for widespread ancient Martian chemistry, but does not prove life existed on Mars.

Synspective has released the first test imagery from its 12th StriX synthetic-aperture-radar satellite, showing observations of Rio de Janeiro, Perth and Tokyo. The images mark a commissioning milestone, not the start of full commercial operations.

Add Comment