Modern comic book cover illustration in bright royal purple, neon orange, white and black ink. A lone bold black silhouette of a person seen from behind stands at the centre with one arm raised toward a radiant white and neon orange burst of straight radiating ink rays above a smooth flat violet ground band. Heavy black ink linework with Ben-Day halftone dot shading, flat cel-shaded colour, no text or lettering anywhere.

Vulcan launch failure destroys 40 Amazon Leo broadband satellites

The Vulcan launch failure destroyed 40 Amazon Leo broadband internet satellites when United Launch Alliance’s 214-foot rocket malfunctioned about 10 minutes after lifting off from Space Launch Complex 41 at the Cape Canaveral Space Force Station. The rocket launched at 12:40 p.m. EST on Sunday, November 15, 2026, but the mission failed to reach orbit. Globetv reported that the accident was the first total mission failure for the Boeing and Lockheed Martin joint venture since it formed in 2006.

Vulcan launch failure: Failure Comes During Centaur Burn

United Launch Alliance said the Vulcan vehicle suffered an anomaly 10 minutes into the flight. The failure occurred during the first burn of the hydrogen-fuelled Centaur upper stage, which had been scheduled to fire for 12 minutes and 15 seconds. Globetv said flight tracking graphics showed the upper stage swinging into an unexpected attitude soon after it lit. The rocket reached an altitude of 95 miles, 150 kilometres, and completed the first phase of its flight before the mission was lost.

The early stages appeared to proceed largely as planned. The solid rocket boosters separated about a minute and 40 seconds into flight and helped the rocket out of the dense lower atmosphere. However, the two methane-burning BE-4 engines on the first stage seemed to burn longer than the pre-launch timeline called for, while stage separation also came later than expected. Globetv cited Spaceflight Now for those observations. United Launch Alliance has not publicly established a cause for the failure.

There was also an unexplained issue before ignition. Launch controllers paused the count at T-minus 20 seconds, resolved the problem and launched at the end of the window. Globetv said it is not yet known whether that issue played a role in the failure. An earlier Friday launch attempt had been scrubbed because of a refuelling problem before the mission was moved to Sunday. The launch was only the fifth flight of a Vulcan rocket and its first in nine months, following work by United Launch Alliance and Northrop Grumman on solid-booster nozzle problems that affected two earlier flights.

Amazon Loses a Major Mission

The mission, code-named LV-01, was the first of 38 Vulcan launches Amazon has purchased for Leo. It was also the first Amazon launch using a rocket designed specifically for carrying broadband satellites into low Earth orbit. The Register reported that Amazon had already flown eight Leo batches on the older Atlas 5. Sunday’s payload would have raised the number launched to 436, while the wider constellation requires more than 3,300 satellites.

Amazon has also booked 24 Leo launches on Blue Origin’s New Glenn, 24 on Europe’s Ariane 6 and 13 on SpaceX’s Falcon 9. The loss therefore affects a broader deployment program rather than a single isolated flight. The Register said LV-02 and plans for larger configurations on subsequent missions were probably on hold after the anomaly. Inside Deep Tech reported that Amazon Leo had hoped to launch its satellite broadband service this year and planned 20 or more launches in 2027.

Amazon Leo said it still viewed Vulcan as a long-term launch partner. Amazon said: ULA has been a trusted partner for Amazon, and we believe they’ll learn from this mission and deliver on their long-term plans for Vulcan. That statement did not provide a timetable for replacing the lost satellites or completing the affected manifest.

Deployment Deadline Becomes Harder

The failure lands as Amazon Leo trails its Federal Communications Commission deployment schedule. The FCC required Amazon Leo to have 1,600 satellites in orbit by July 31, 2026, but Amazon has only around 390 in service. Inside Deep Tech said the original licence milestone was 1,616 satellites by July 30, 2026. Amazon still planned to have 3,232 satellites in orbit by July 2029, and an Amazon Leo guide said about 396 production satellites had reached orbit on Atlas V, Falcon 9 and Ariane 6 flights, roughly 12 percent of the total required by the licence.

The FCC granted Amazon a limited waiver on its halfway milestone but retained the July 30, 2029 deadline for all 3,232 satellites. Inside Deep Tech said satellites launched after the missed milestone lose spectrum priority against other systems from the same processing rounds for 20 months, until March 30, 2028, or until Amazon reaches 50 percent deployment. The window is shortened to 15 months if Amazon certifies that it has built the satellites and secured the launches needed for 50 percent deployment. The penalty gives Amazon an incentive to move quickly without removing the final deployment obligation.

Orbitalpha calculated that Amazon needed 1,220 more satellites to reach the halfway mark after counting 396 in orbit. Its review of published Ariane 6 and Falcon 9 bookings produced about 996 satellites, leaving a gap of 224. Orbitalpha said Amazon cannot reach the halfway mark on those contracts unless Vulcan or New Glenn flies again. The review also found that both rockets depend on the Blue Origin BE-4 engine, making a BE-4 finding central to whether New Glenn’s schedule would also be affected.

Launch Supply Is the Bottleneck

Amazon has said it has built more than 1,000 satellites, meaning more than half of its manufactured spacecraft are in storage. The company has identified rides rather than factories as the main constraint. Inside Deep Tech reported that Amazon’s Kirkland, Washington factory can build up to five satellites per day and that the company had cited production capacity of about 30 satellites per week. Even so, the loss of a 40-satellite mission and delays to planned launches leave ready hardware without a launch path.

Blue Origin cannot immediately fill that gap. Its New Glenn rocket suffered a catastrophic on-pad explosion in May, which was traced to an oxygen valve problem in one of the seven BE-4 engines on that rocket. ULA chief executive Mark Peller told Aviation Week before the Vulcan launch that Blue Origin had developed a design change and retrofitted the engines assigned to the mission. Globetv said Amazon was waiting for New Glenn flights to resume, while Inside Deep Tech reported that the first Leo mission on the vehicle had no confirmed date.

Consequences for ULA and National Security

The Vulcan launch failure places additional pressure on a rocket already carrying strategic responsibilities. The Vulcan is on contract to launch roughly half of the US military’s national security space missions in the next few years. The US Space Force had paused national security payloads on Vulcan pending additional analysis. Globetv said the pause had already been in place over the earlier booster nozzle issue, with commercial flights allowed to continue. Sunday’s accident may lead the Space Force to maintain or widen that restriction once investigators have more information.

United Launch Alliance said it would work closely with Amazon and other appropriate organizations to find the cause, determine the appropriate corrective action and return to flight as quickly as possible. The company also said that every flight generates data and that it did not yet have specific data explaining what occurred. With the investigation unresolved and no return-to-flight date supplied, the Vulcan launch failure leaves both Amazon Leo’s deployment schedule and United Launch Alliance’s broader manifest facing further uncertainty.

Leave a Comment

Your email address will not be published. Required fields are marked *