Vulcan Centaur
Satellites launched
None yet.
In the news
- Vulcan failure caused by inadequate fuel supply to engines, ULA saysArs Technica · Nov 18, 2026
ULA said on Nov. 18 that an initial integrated review of flight data from the Nov. 15 Leo 1 (Amazon Leo) Vulcan failure indicates the low booster thrust came from inadequate fuel supply from the vehicle to the BE-4 engines, not from engine performance; the exact cause is still under investigation. ULA said the Centaur V upper stage and its RL10 engines started and ran normally and the solid rocket boosters performed normally. Blue Origin issued a matching statement. Corroborated by RocketCityNow (WZDX) reporting of the same ULA update. Preliminary findings only.
Read at Ars Technica ↗ - ULA: Investigation Into Amazon Leo 1 Failure Focusing On Core StageTalk of Titusville · Nov 17, 2026
In a Nov. 17 update on its blog (blog.ulalaunch.com/blog/vulcan-leo-1-updates), ULA said early data show Vulcan's core/booster stage had low performance just after liftoff on the Nov. 15 Amazon Leo 1 mission, so stage separation came at too low an altitude and velocity to reach orbit; telemetry and the mission were lost about 10 minutes into flight. The Centaur V upper stage and RL10 engines started and performed nominally, and the six GEM 63XL solid boosters appear nominal after nozzle fixes. ULA has not named a root cause (it has not blamed the BE-4 engines specifically); the FAA is overseeing the ULA-led investigation and Vulcan remains grounded. Early findings only, confirmed by ULA's own update and by RocketCityNow reporting.
Read at Talk of Titusville ↗ - ULA suffers first total mission failure with loss of Vulcan rocket carrying 40 Amazon Leo satellitesSpaceflight Now · Nov 15, 2026
United Launch Alliance's Vulcan Centaur lifted off from Space Launch Complex 41 at Cape Canaveral Space Force Station at 12:40 p.m. ET on Nov. 15, 2026, carrying 40 satellites for the Amazon Leo broadband constellation (formerly Project Kuiper) on the Vulcan Leo 1 return-to-flight mission after a nine-month stand-down. Liftoff came later than the original 12:11 p.m. ET target after a countdown hold. In a statement about 50 minutes after launch, ULA said the vehicle suffered an anomaly 10 minutes into the flight and failed to deliver the Amazon mission to orbit; the company said it did not yet have specific data on the cause and would investigate with its customer and return to flight as quickly as possible. Space.com, Aviation Week, and SpaceNews independently reported the same failure and the loss of the 40 satellites. Spaceflight Now reported this as ULA's first outright failure since the company was formed in 2006, and said the anomaly occurred during the Centaur upper-stage burn; the cause is not yet public.
Read at Spaceflight Now ↗ - Vulcan Return-To-Flight Launch Reset For Nov. 15Aviation Week · Nov 14, 2026
ULA scrubbed the Saturday, Nov. 14 attempt to launch Vulcan's return-to-flight mission (Amazon Leo LV-01, 40 broadband satellites) from SLC-41 at Cape Canaveral after a network communication issue between ground equipment and the rocket needed reconfiguration beyond the 29-minute window. It was the second scrub in two days, after a nitrogen-plant power interruption halted Friday's attempt. ULA said the vehicle and satellites are healthy; the next attempt is planned for Sunday, Nov. 15 at 12:11 p.m. EST. Corroborated by Space Coast Wire and Spaceflight Now. The launch is still only planned, not flown.
Read at Aviation Week ↗
Linked in the graph
status: stub