Spaceflight & Missions

ULA’s Vulcan lost with 40 Amazon Leo satellites in first outright failure

United Launch Alliance’s Vulcan rocket failed to reach orbit on Sunday, destroying a payload of 40 Amazon Leo broadband satellites. The failure, about 10 minutes into flight, will ground a vehicle that is replacing ULA’s Atlas 5 and complicates Amazon’s plans to build its internet constellation.

ULA said roughly 50 minutes after liftoff that the rocket, launched from Space Launch Complex 41 at Cape Canaveral Space Force Station, had suffered an anomaly and did not deliver the Amazon mission to orbit. The company said it would work with its customer and other organizations to identify the cause, decide on corrective action and return to flight quickly. It is the first outright failure of a ULA rocket since the Boeing–Lockheed Martin partnership was formed in 2006.

What the flight data suggest

The cause has not been identified. The 214-foot Vulcan lifted off at 12:40 p.m. EST on a northeasterly path, using about 3.8 million pounds of thrust from six Northrop Grumman solid rocket boosters and two methane-fueled BE-4 first-stage engines. The solids appeared to perform normally and fell away about 1 minute 40 seconds after liftoff.

The first stage then appeared to burn longer than ULA’s pre-launch timeline called for, and it seemed to separate from the hydrogen-fueled Centaur upper stage later than expected. Telemetry-based animation showed the Centaur making unusual orientation adjustments early in its planned 12-minute 15-second burn. ULA’s commentators did not mention problems, and the broadcast ended without confirming that the burn ran its full length. ULA’s statement indicated the problem occurred during the Centaur firing, but it gave no details.

The countdown was also troubled. A Friday attempt was scrubbed after a gaseous nitrogen plant serving multiple launch providers went offline, and Saturday’s try was delayed by network problems between the rocket and ground systems. On Sunday, controllers held at T-minus 20 seconds for an unexplained technical issue. ULA resolved it and launched at the very end of the window. Whether that issue relates to the failure is unknown.

A difficult run for Vulcan

This was only the fifth Vulcan flight and the first in nine months. ULA and Northrop Grumman had spent that time working on solid booster nozzle problems that affected flights in 2024 and in February. ULA CEO Mark Peller said before launch that three credible causes had been identified and mitigated. The U.S. Space Force had paused Vulcan launches of national security payloads pending further analysis, though commercial flights were allowed to continue.

Peller also said Blue Origin, which builds the BE-4, had retrofitted the engines on this rocket with a design improvement addressing an oxygen valve issue. That valve problem was behind the May on-pad explosion of Blue Origin’s New Glenn, which uses seven BE-4s. Blue Origin is working through ULA’s engine inventory.

Impact on Amazon Leo

The mission was the first of 38 Vulcan launches Amazon bought for Leo, which is intended to compete with SpaceX’s Starlink. ULA has already flown eight Leo missions on Atlas 5. Amazon has also booked 24 launches on New Glenn, 24 on Ariane 6 and 13 on Falcon 9. The constellation needs more than 3,300 satellites, and Sunday’s launch would have brought the number launched to 436.

Amazon must now wait for ULA’s investigation before flying on Vulcan again, while New Glenn remains sidelined after its failure. ULA said Amazon and other customers will have visibility into the investigation. NASA Administrator Jared Isaacman offered the agency’s help with the investigation and remediation, saying on X that Artemis and the nation’s Moon Base plans need ULA.

Source: spaceflightnow.com

Related Articles

0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
Back to top button