Scivillage.com Casual Discussion Science Forum

Full Version: Vulcan Centaur rocket fails during return-to-flight launch, 40 Amazon satellites lost
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
First total mission failure out of only five flights since 2024.
- - - - - - - - -

Vulcan Centaur rocket fails during return-to-flight launch, 40 Amazon satellites lost
https://www.space.com/space-exploration/...ite-launch

INTRO: United Launch Alliance's Vulcan Centaur rocket suffered an anomaly during its launch today (Nov. 15), resulting in the loss of 40 Amazon internet satellites. The Vulcan Centaur lifted off from Florida's Cape Canaveral Space Force Station today at 12:40 p.m. ET (1740 GMT), hauling 40 satellites for the Amazon Leo broadband constellation toward low Earth orbit (LEO). But they never got there.

"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," ULA said in an update on X today, 50 minutes after launch. "Since the anomaly just occurred, we don’t have any specific data yet to understand what occurred today."

Today's launch was supposed to be a bounce-back mission for the Vulcan Centaur, the successor to ULA's workhorse Atlas V rocket.

Vulcan debuted in January 2024 and had four total flights under its belt before today. On two of those missions — its second, in October 2024, and its fourth, in February of this year — the rocket experienced an issue with one of its solid rocket boosters (SRBs).

In both cases, an SRB nozzle burned through and fell off about 30 seconds after launch. Vulcan Centaur overcame the problem on both launches, successfully delivering its payloads to their designated orbits. But the U.S. Space Force was concerned enough that it decided to pause national security launches on Vulcan until ULA addressed the problem. (Vulcan's third and fourth launches were Space Force missions.)

ULA worked hard on that front and got Vulcan ready to return to flight, which finally occurred today after nine months..

"The integrated team has made great strides in improving our understanding of the SRB anomaly that occurred on the previous Vulcan flight and have identified several potential contributors, which have been mitigated through design and process improvements to the nozzle," the company said in an Oct. 28 update.

That nozzle work apparently paid off: The SRBs appeared to perform as expected during today's launch. But a different, more serious problem cropped up today, and Vulcan Centaur could not overcome it... (MORE - detais)

What went wrong? ... https://youtu.be/YN4n5UUxqRE


The angry astronaut ... https://youtu.be/wp_yJu69GP8
The Vulcan rocket failure could haunt U.S. spaceflight for years to come
https://tech.yahoo.com/science/articles/...00267.html

EXCERPT: The loss is only the latest in a longer string of interconnected misfortunes. This was intended to be Vulcan's triumphant return to flight: the launcher had been grounded after its previous flight, in February, had worrisome malfunctions in a Northrop Grumman–made solid rocket booster. On its first stage, Vulcan also uses two advanced methane-burning BE-4 engines, which are supplied by Blue Origin, another would-be SpaceX rival bankrolled by Amazon's Jeff Bezos. And Blue Origin is recovering from its own catastrophe in May, when its massive New Glenn rocket—also equipped with BE-4 engines—blew up during a launchpad test. New Glenn is still grounded, but company officials are targeting January 2027 for its return to flight.

For its part, SpaceX so far seems on track to continue its dominance, with a historic first successful catch of its Starship on its Texas launch tower after that fully reusable vehicle flawlessly delivered a batch of the company's Starlink satellites into orbit during the test flight. Stymied by Vulcan's mounting mishaps, Amazon's competing Amazon Leo service is far behind schedule in its rollout, and the company had already booked 37 more Vulcan launches to deliver more of its satellites into orbit.

If Blue Origin's BE-4 engines are the culprits for Vulcan's failure, this could compound delays for the company's Blue Moon lunar lander, which NASA needs for its Artemis program moon landings and must launch on New Glenn rockets. And Vulcan's second stage, called the Centaur V, is also integral to future flights of the space agency's Artemis-supporting Space Launch System (SLS) rocket; any significant problems with ULA's Centaur V could lead to more delays for future SLS launches.

Julie Arnold, a ULA spokesperson, tells Scientific American that "ULA exists to provide assured access to space for our nation and for the customers who depend on us. That purpose is why we take on some of the hardest missions in spaceflight and why we hold ourselves to the standard of mission success. Today we did not meet that standard." The comments reiterated what the company previously posted on X.

Vulcan's return to flight on Sunday initially looked like a routine launch from Space Launch Complex 41 at Cape Canaveral Space Force Station in Florida. Unlike ULA's four previous Vulcan launches, this one was the first to use six solid rocket boosters rather than two or four. Unlike some of those earlier launches, this one saw no obvious problems with those boosters, which peeled off and fell back to Earth as planned about one and a half minutes into the flight.

But at about five minutes after takeoff, Vulcan's BE-4-powered first stage fired 30 seconds longer than planned. "That's a long time, because in launches, everything is timed to the second," says Paul Ronney, an aerospace engineer at the University of Southern California. It suggests that the first stage underperformed and had to continue firing to compensate, he says.

ULA appeared to confirm as much in a statement posted on its website on November 17: "Early indications are that just after liftoff the launch vehicle experienced low [first-stage] performance, resulting in stage separation occurring when the vehicle was low in altitude and below minimal velocity to reach orbit," it said.

"Blue Origin is working closely with ULA to investigate and determine the root cause," a company spokesperson told Scientific American. NASA's chief Jared Isaacman also expressed support for the investigation in a response on X to ULA's public statement on the anomaly: "The team at NASA is available to assist in all matters related to the investigation and remediation effort," Isaacman said. "Artemis, Moon Base, and the nation need ULA. We are in your corner and here to help."

SpaceX head Elon Musk also weighed in, replying to ULA's post, "Hope you are back to flight soon." (MORE - missing details)