"United Launch Alliance's Vulcan Centaur reached orbit on February 12 despite "a significant performance anomaly" that saw one of its four solid rocket boosters burn through its nozzle during ascent. Viewers of the launch from Cape Canaveral at 0422 EST (0922 UTC) were treated to some impressive fireworks as the part detached in a shower of fragments. It was the fourth launch of ULA's replacement for the Atlas V and Delta IV rocket, and the second in which an anomaly was noted with the booster."
"Despite the anomaly, the mission was a success, and the US Space Force payload was carried directly to geosynchronous orbit. ULA planned to ramp up Vulcan Centaur operations in 2026, with future launches including payloads for Amazon Leo (formerly Project Kuiper). It is not clear if those will need to be postponed while ULA investigates the cause of the burn-through and subsequent loss of at least part of the rocket nozzle."
"Gary Wentz, ULA vice president of Atlas and Vulcan Programs, said in a statement: "We will conduct a thorough investigation, identify root cause, and implement any corrective action necessary before the next Vulcan mission." The Vulcan Centaur is a heavy-lift vehicle, with a pair of Blue Origin BE-4 engines powering the first stage and up to six GEM 63XL solid rocket boosters providing additional thrust."
Vulcan Centaur reached orbit on February 12 despite a solid rocket booster burning through its nozzle and shedding fragments during ascent. The booster anomaly produced asymmetric thrust that the vehicle counteracted, allowing successful delivery of a US Space Force payload to geosynchronous orbit. This was the fourth Vulcan launch and the second instance of a booster-related anomaly following a similar nozzle shed in 2024; the 2025 mission proceeded without issue. ULA intends a thorough investigation to identify root cause and apply corrective actions. Vulcan uses two BE-4 engines and up to six GEM 63XL solid boosters; 2026 operations planned could include Amazon Leo payloads.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]