United Launch Alliance is renowned for its highly reliable Atlas V rocket, but its newest heavy‑lift vehicle, the Vulcan, has encountered a serious malfunction. The rocket failed during ascent yesterday, resulting in the loss of a 40‑satellite batch intended for Amazon’s Leo internet constellation.
“Based on data received by our Launch Director, we confirm that the Vulcan vehicle launched from Space Launch Complex 41 suffered an anomaly 10 minutes into the flight and failed to deliver the Amazon mission to orbit,” the company said in a post on X. “We will work closely with our customer and other appropriate organizations to find the cause, determine the appropriate corrective action, and return to flight as quickly as possible.”
Although launch failures are an inherent risk, ULA had never before experienced a mishap since its formation in 2006 as a joint venture between Boeing and Lockheed Martin, where the Atlas V earned a reputation for exceptional dependability. The latest failure has prompted a thorough engineering review of the more powerful and complex Vulcan, which could face grounding pending the investigation.
“Every flight generates data, and every flight teaches us something. Since the anomaly just occurred, we don’t have any specific data yet to understand what occurred today,” ULA wrote. “We are committed to full transparency with our customers, who will have visibility into the investigation process, which utilizes rigorous methodology and corrective actions.”
After a refueling issue caused a postponement of a planned Friday launch, the mission was rescheduled for Sunday, 15 November, with a launch window opening around noon ET. Controllers called a hold at T‑minus 20 seconds due to an unidentified technical problem, but the issue was resolved and the rocket ignited at 12:40 PM ET. The solid boosters, which had experienced complications on two prior flights, appeared to function normally. However, the first‑stage methane engines burned longer than anticipated based on ULA’s timeline, as Spaceflight Now noted. Following first‑stage separation, the hydrogen‑powered Centaur upper stage initiated its planned 12.25‑minute burn, during which the anomaly occurred, according to ULA’s statement.
The loss represents a significant setback for United Launch Alliance and dramatically impacts Amazon’s Leo satellite project, which aims to compete with SpaceX’s Starlink. Leo has secured 38 Vulcan launch contracts and eight successful Atlas V missions, but many of these launches are now likely to be delayed.
Amazon also relies on Jeff Bezos’s Blue Origin, which faced its own launchpad explosion in May during a test of the New Glenn rocket. Blue Origin holds 24 launch agreements with Amazon, adding another layer of uncertainty to the company’s deployment schedule.
The Federal Communications Commission mandates that Amazon Leo achieve 1,600 satellites in orbit by 31 July 2026, with a broader goal of 3,232 satellites by July 2029. Currently, only around 390 satellites are operational, and the recent Vulcan failure threatens to widen the gap. In a July statement, Amazon noted, “No operator could have predicted that all three core heavy‑lift launch programs…would experience repeated, concurrent scheduling slips severe enough to exhaust the buffers Amazon Leo had built in.” The latest mishap compounds an already challenging situation for the constellation’s rollout.
Also Read
- The Animal You’d Most Like to Communicate With If You Could
- Vitamin C May Limit Stomach Formation of Cancer-Linked Compounds, Mathematical Model Suggests
- South Korean Tax Accountancy Exam Top Scorer Confesses to Cheating via AI and Hidden Devices
- Voyager 1’s Jupiter Flyby Rewrote the Book on the Solar System’s Giant

