Market
ULA’s Vulcan rocket fails about 10 minutes after liftoff and 40 Amazon Leo satellites are lost, in the company’s first mission failure
ULA’s Vulcan suffered an anomaly about 10 minutes into its November 15 flight and 40 Amazon Leo satellites were lost. The cause is not yet known.
United Launch Alliance’s Vulcan rocket suffered an anomaly about 10 minutes into its flight on Sunday, November 15, 2026, and failed to deliver 40 Amazon Leo satellites to orbit, which were lost. Reuters and Spaceflight Now describe it as the first outright mission failure since ULA, the Boeing and Lockheed Martin joint venture, was formed in 2006. The cause had not been established in the coverage we read.
The essentials
- The flight: liftoff at 12:40 p.m. EST from Cape Canaveral’s Space Launch Complex 41, carrying 40 Amazon Leo satellites, per Space.com.
- The anomaly: ULA said the vehicle suffered an anomaly 10 minutes into the flight and failed to deliver the mission, per Space.com.
- What was seen: the solid boosters appeared to perform normally, while the first stage seemed to burn longer than planned and the Centaur made unusual attitude moves, per Spaceflight Now.
- The record: the first outright failure of a ULA rocket since 2006, per Reuters and Spaceflight Now; it was also the fifth Vulcan flight.
What is known about the failure
Spaceflight Now says the boosters separated normally, then the first stage appeared to burn long and separate late from the Centaur, which made unusual orientation changes early in a planned burn of about 12 minutes. A hold at T-20 seconds occurred; reporters noted it may or may not be related. ULA said it would work with its customer to find the cause and return to flight quickly.
What it means for Amazon and ULA
This was the first of 38 Vulcan launches Amazon bought for its Leo constellation, per Spaceflight Now, so the investigation weighs on both schedules. The same report notes earlier Vulcan flights in 2024 and February 2026 had booster nozzle problems yet reached orbit, and that the Space Force paused national security launches. Whether those issues relate to this loss is not established.
What is not established
- The root cause of the failure: not established; ULA had not named one.
- Whether the T-20 second hold or the first stage’s long burn contributed: unclear in what we read.
- Whether the earlier booster nozzle issues are linked: not established.
- How long Vulcan will be grounded: no timeline found.
Summary table
| Point | What is stated as of November 7, 2026 | Source |
|---|---|---|
| Launch | Sunday November 15, 2026, 12:40 p.m. EST, Space Launch Complex 41 | Space.com |
| Payload | 40 Amazon Leo satellites, all lost | Inquisitr |
| Anomaly timing | About 10 minutes into flight, per ULA | Space.com |
| Record | First outright ULA mission failure since the 2006 formation | Reuters |
| Vehicle history | Fifth Vulcan flight; first of 38 Amazon launches | Spaceflight Now |
FAQ
Is this really ULA’s first failure?
Reuters and Spaceflight Now both call it the first outright mission failure since ULA formed in 2006. Earlier Vulcan booster anomalies still reached orbit.
Why did it fail?
The cause is not known yet. ULA said it would investigate with its customer and other organizations.
Were any satellites saved?
No. Coverage says all 40 satellites aboard were lost.
Method and limits
Checked on November 16, 2026. We read the Spaceflight Now report directly; Space.com, Reuters (via a Yahoo relay) and Inquisitr were read through excerpts. Amazon’s own statement was not quoted in what we read.
Sources
- Spaceflight Now: ULA suffers first outright failure with loss of Vulcan rocket carrying 40 Amazon Leo satellites (verified 2026-11-08)
- Space.com: Vulcan Centaur rocket fails during return-to-flight launch, 40 Amazon satellites lost (verified 2026-11-08)
- Reuters: Rocket from Boeing-Lockheed firm fails mid-flight, destroys payload of Amazon satellites (verified 2026-11-08)
- Inquisitr: ULA’s Vulcan rocket fails to reach orbit, losing 40 Amazon Leo satellites (verified 2026-11-08)
Spotted an error in this article? Report it · Our corrections policy