Vulcan rocket suffers first total failure, destroying 40 Amazon satellites
A mission meant to end United Launch Alliance's nine-month grounding instead became the company's first outright launch failure in two decades, complicating Pentagon launch plans and Amazon's satellite-internet rollout.

A rocket built to carry some of the Pentagon's most sensitive satellites failed outright on Sunday, destroying 40 broadband satellites bound for Amazon's internet constellation and handing United Launch Alliance the first total mission failure in its 20-year history.
The Vulcan Centaur rocket lifted off at 12:40 p.m. Eastern time from Space Launch Complex 41 at Cape Canaveral Space Force Station, after a countdown already delayed twice by ground equipment trouble. The flight appeared routine through the first minute and a half, as its six strap-on solid rocket boosters burned out and separated normally. But about ten minutes into the flight, the company said, the vehicle "suffered an anomaly" and failed to deliver its payload to orbit, according to a company statement reported by SpacePolicyOnline. All 40 satellites were lost.
The 214-foot rocket, powered by two Blue Origin BE-4 main engines generating roughly 3.8 million pounds of thrust, was flying its fifth mission overall and its first in nine months. It was meant to be a comeback flight. Instead, it became what Spaceflight Now described as ULA's first outright mission failure since the company was formed in 2006 out of Boeing and Lockheed Martin's rocket divisions — a streak that had survived more than 170 combined launches of the Atlas V, Delta II, Delta IV and Vulcan families.
A launch that unraveled in slow motion
By the accounts gathered from launch-day reporting, nothing about the failure looked dramatic in real time. The six Northrop Grumman solid boosters, the component that caused ULA's two previous in-flight problems, performed exactly as planned and separated on schedule. The trouble emerged afterward: the BE-4 engines on the rocket's first stage appeared to burn longer than their pre-launch timeline called for, and the first stage separated from the Centaur upper stage later than expected.
The Centaur stage then made unusual orientation adjustments early in what was supposed to be a 12-minute, 15-second burn to reach orbit. ULA has not said what happened inside that burn, only that it ended in failure roughly ten minutes after liftoff. The company issued its first public acknowledgment about 50 minutes after launch and said it would "work closely with our customer and other appropriate organizations to find the cause."
Grounded for nine months, cleared to fly, grounded again
Sunday's mission, internally designated Vulcan Leo 1, was supposed to close the book on a difficult stretch for the rocket. Vulcan's two prior flights, in October 2024 and in February of this year, each suffered a nozzle problem on one of their Northrop Grumman solid boosters. After the February incident — which occurred on a national-security mission — the Space Force halted the use of Vulcan for its most sensitive payloads while ULA, Northrop Grumman and the Space Force investigated.
ULA's new president, Mark Peller, had said the company identified "three credible causes" for the booster nozzle issue and had mitigated all of them, clearing the way for Sunday's flight. The rocket's BE-4 engines had also been retrofitted by Blue Origin to fix an unrelated valve problem found on earlier flights. None of those fixes addressed what went wrong this time: the boosters worked fine, and the failure instead struck a part of the vehicle, the core stage and Centaur, that had no documented history of trouble.
"Today, we did not meet that standard," United Launch Alliance said in its statement, referring to the mission-success record the company has built its reputation on.
A costly setback for Amazon and for the Pentagon
The immediate loser is Amazon, which has committed to as many as 38 future Vulcan launches as part of what ULA itself has called "the world's largest commercial launch agreement", alongside separate contracts for Blue Origin's New Glenn, Arianespace's Ariane 6 and SpaceX's Falcon 9. Amazon is racing against its own federal deadline: its license from the Federal Communications Commission originally required half of its planned 3,232-satellite constellation, 1,616 satellites, in orbit by July 30 of this year. The commission's Space Bureau granted a limited waiver of that milestone in June, citing a "near-term shortage of available rockets," but left the full-constellation deadline of July 30, 2029, in place and stripped the company's spectrum-priority status on undeployed satellites in the meantime. Sunday's failure removes one more rocket from an already strained launch schedule, and Amazon must now wait for ULA's investigation to run its course before trying Vulcan again — just as it is separately waiting for Blue Origin's New Glenn to return to flight after an on-pad explosion in May.
The setback also lands at an awkward moment for the Pentagon. Vulcan and SpaceX's Falcon and Starship rockets are the two primary vehicles the Space Force relies on to launch national-security payloads under its multibillion-dollar launch-services program, and officials had only recently signaled willingness to resume assigning high-value military satellites to Vulcan after the nine-month pause. Several national-security missions have already shifted to SpaceX during Vulcan's grounding, and Sunday's failure is likely to intensify pressure on ULA at a time when it holds a shrinking share of the national launch market compared with SpaceX's cadence.
NASA has also expressed informal interest in the outcome, since the Vulcan line underpins a cooperative agreement on a Centaur upper stage for the agency's Artemis program. NASA Administrator Jared Isaacman, a former private astronaut who flew to orbit twice before taking over the agency, posted publicly that he appreciated the company "quickly keeping the public and your partners informed," a modest show of support from a federal customer with its own stake in the rocket's reliability.
What happens next
ULA has not set a timetable for its investigation or for Vulcan's next flight, saying only that it intends to be transparent with customers and to return to flight "as quickly as possible." Historically, that process has taken months rather than weeks: the February booster anomaly kept Vulcan grounded for nine months while ULA, Northrop Grumman and the Space Force worked through the review. Given that this failure struck an entirely different part of the vehicle, investigators will likely need to start largely from scratch rather than build on the prior probe's findings.
In the meantime, Vulcan is expected to sit idle, Amazon's satellite rollout slows further against a federal deadline it has already had to renegotiate once, and the Pentagon is left weighing how much of its most sensitive national-security payload manifest it can still afford to split between two launch providers rather than one.

Outages Hit Chase, Bank of America and Other Major Lenders Nationwide

North Atlantic right whale population falls to 382, reversing years of slow recovery

Bomb found at Peoria ethanol plant forces mile-wide evacuation
