Early Vulcan data points to overlong first-stage engine burn
Initial telemetry suggests Vulcan's BE-4 engines ran too long before staging, while Amazon says its next Leo launch on Ariane 6 on 23 November is unaffected.
- What happened
- Early data from the failed 15 November Vulcan launch suggests the first-stage engines burned longer than planned before the upper stage lost the mission.
- What’s new
- Suspected causes have emerged, Amazon Leo has responded, and further Vulcan flights are expected to be grounded pending the investigation.
- Why it matters
- Amazon Leo relies on dozens of booked Vulcan flights to build out a constellation that remains far short of its regulatory and coverage targets.
The first clues to why United Launch Alliance's Vulcan rocket lost 40 Amazon Leo satellites on 15 November point to the first stage. ISPreview reports that ULA has said its early telemetry indicates the BE-4 engines ran beyond their planned burn time and that the vehicle had attitude problems around staging, after which the Centaur upper stage could not recover. These findings are preliminary and the cause has not been confirmed.
What the data suggests so far
Engadget, citing Spaceflight Now, reports that the methane-fuelled first-stage engines fired longer than ULA's own estimated timeline. The solid boosters, which had caused problems on two earlier flights, appeared to perform normally, according to Engadget. After separation, the hydrogen-fuelled Centaur began a planned 12.25-minute burn, and ULA said on its website that the anomaly apparently happened during that phase. ULA's formal statement was more cautious, saying it did not yet have specific data and would work with its customer to find the cause and return to flight.
Amazon's response and schedule
An Amazon Leo spokesperson told ISPreview that launch risk is especially high on inaugural missions such as LV-01, adding: "ULA has been a trusted partner for Amazon." ISPreview expects future Vulcan launches to be grounded until the cause is found and fixed, which it says will likely add some limited delay to Amazon Leo's planned commercial launch. ISPreview says the next launch, carrying 36 satellites on a European Ariane 64 rocket on 23 November, will not be affected.
How far Leo still has to go
The stakes for Amazon are large. Engadget reports that Leo has 38 Vulcan flights booked, following eight successful Atlas V missions, and that many are now likely to slip. ISPreview puts the constellation at 392 satellites launched, against at least 500 needed for basic global coverage. Engadget adds that the Federal Communications Commission had required 1,600 satellites in orbit by 31 July 2026, while Leo has around 390 in service.