Vulcan rocket failure derails Amazon launch, military hopes

The gist
A 10-minute Vulcan rocket failure destroyed Amazon’s first 40-satellite broadband batch and threw both commercial and military launch plans into turmoil.
What to know
- ULA’s Vulcan rocket lost Amazon’s entire 40-satellite Leo payload just minutes after liftoff on November 15, 2026, prompting immediate investigations.
- Telemetry shows a booster-stage breakdown caused the vehicle to spin, dooming the mission and raising fresh doubts about Vulcan’s reliability.
- The setback jeopardizes Amazon’s constellation rollout and stalls key Space Force certification, all amid a tightening global launch capacity crunch.
Amazon's Costly First Loss
The destruction of all 40 Amazon satellites on Vulcan’s debut flight instantly halted deployment plans and triggered a high-stakes investigation into ULA’s first total mission failure since 2006.
The urgency of the story begins with what was on the rocket: WUSF’s November 15 headline, “ULA's Vulcan Rocket Launches 40 Amazon Satellites After Day-Long Delay,” captured that this was Amazon’s first 40-satellite payload on the rocket’s debut flight, and by day’s end that entire batch was gone. As multiple reports put it, “Vulcan lifted off Sunday… carrying 40 Amazon Leo internet satellites,” but “the rocket failed about 10 minutes into flight” and “failed to reach orbit, losing 40 satellites for Amazon Leo,” meaning the November 15, 2026 Vulcan failure resulted in a total loss of Amazon’s first 40-satellite payload and turned a long-awaited deployment into an immediate total-loss event.
That is why the fallout was instant rather than theoretical: The Verge’s headline said flatly, “ULA’s Vulcan debut fails, wiping out 40 Amazon Leo broadband satellites on first flight,” while ULA said it did not yet have specific data and would work with Amazon and other organizations to find the cause and return to flight. The failure therefore triggered the investigation on day one, delayed the next mission pending that review, and cast a shadow over military clearance timing, all while Spaceflight Now noted it was “ULA’s first total mission failure since the Boeing–Lockheed Martin joint venture was formed in 2006.”
Booster Breakdown Shakes Trust
A catastrophic booster-stage malfunction—rather than a minor glitch—exposed deep vulnerabilities in Vulcan’s core systems and shattered confidence in its reliability for future launches.
The mechanism of the failure matters because it was not a marginal shortfall but a full breakdown of ascent performance: Vulcan’s fifth flight ended without reaching orbit, and ULA said “the Vulcan vehicle launched… suffered an anomaly 10 minutes into the flight and failed to deliver the Amazon mission to orbit.” Reuters reported that “10 minutes after launch, it ‘suffered an anomaly,’” while flight data pointed away from the strap-on solids and toward the core, with “sources familiar with the launch” saying the problem originated in the booster stage. The incident destroyed 40 Amazon Leo broadband satellites and, unlike its previous booster anomalies, resulted in the complete loss of the payload.
That focus on the booster is what most directly undermines confidence in Vulcan’s schedule commitments: Reuters said the six solid rocket boosters “appeared to operate normally during the initial ascent,” but later telemetry showed “unusual behavior involving the main booster stage,” including the two BE-4 engines running at least 30 seconds past expected shutdown before the vehicle began to spin. Telemetry also showed the upper stage’s RL10 engines igniting and vectoring thrust in an apparent recovery attempt, yet the mission still ended in complete payload loss, exposing unresolved propulsion or propellant-feed vulnerabilities on the rocket’s first flight in more than nine months.
Military Certification in Jeopardy
Recurring Vulcan booster failures have turned Space Force certification into a moving target, threatening to sideline national security launches until ULA proves lasting fixes.
What Amazon’s mission was supposed to prove went beyond a commercial deployment: it had become the Space Force’s practical readout on whether Vulcan could resume national-security work. After a booster nozzle failure on February 12, 2026, “On February 26, the Space Force announced it would fly no more national security missions on Vulcan until an investigation into the solid rocket motor issue was complete,” and although Vulcan had been “formally certified for National Security Space Launch missions” on March 26, 2025 after “a certification campaign spanning 52 criteria,” that formal status no longer settled the real question.
That is because the certification story had already turned into a test of whether Vulcan could get through recurring booster trouble without forcing the military back to the sidelines. The February 12 launch, the USSF-87 mission, was treated as a continuation of that pattern: it was “the second time in four Vulcan flights that a GEM 63XL nozzle had failed in flight,” after an October 2024 failure on the rocket’s second certification flight, and Tech Times noted that the nine-month grounding traced to Cert-2 was followed by another setback when, about 20 seconds after liftoff on USSF-87, one booster suffered nozzle burn-through, showing the post-Cert-2 remediation had not solved the underlying problem.
Launch Shortage Threatens Amazon
Losing 40 satellites is a critical blow for Amazon’s constellation, especially as a global launch bottleneck means replacement opportunities may be years away.
The immediate loss was limited in one sense: ULA launched from Space Launch Complex 41 carrying 40 satellites for Amazon Leo, and about 10 minutes into flight it suffered an anomaly and did not deliver the mission to orbit. But shattered.io explicitly ties those 40 spacecraft to Amazon’s constellation “math,” underscoring that this was not a symbolic setback; it removed a meaningful block of near-term capacity from a deployment plan that depends on repeated, timely launches rather than any single all-or-nothing mission.
That matters more because replacement capacity is scarce. NeoTeo, citing Ars Technica’s reporting on Quilty Space, says launch supply outside China is forecast to fall “about 150 launches short of demand from satellite operators and civil space agencies through 2030,” with the squeeze “sharpest in 2028,” and Caleb Henry said the shortfall “might not ease until sometime in the late 2030s”; meanwhile, Space Force demand has surged, with Lane 1 rising to about 170 launches and Lane 2 to 79, and that roughly 150-launch baseline excludes the cited increase in U.S. military demand.

