Key Highlights
- ULA’s Vulcan rocket suffered a booster problem during a classified launch.
- The issue affected one of the four solid-fuel strap-on boosters.
- The satellite was still delivered to its intended orbit despite the anomaly.
- This is the fourth launch of ULA’s new Vulcan rocket, with mixed results so far.
Yet here we are—another day in the life of United Launch Alliance (ULA), where nothing seems truly routine. The February 12th launch of a classified Space Force mission from Cape Canaveral was supposed to be smooth sailing. But as they say, even in the best-laid plans, something can—and often does—go awry.
Setting the Stage
The Vulcan rocket, ULA’s latest heavy-lifter, is no stranger to the spotlight. Its genesis was marked by promises of all-American components and a replacement for the venerable Atlas 5. But like any new tech venture, its debut hasn’t been without its hiccups.
Booster Problems
Thursday’s mission took off at 4:22 AM EST, with a roar that could be heard (and seen) across the Space Coast. The Blue Origin BE-4 engines and four Northrop Grumman solid-fuel boosters pushed the rocket to life. Then, just as smoothly as it began, things went sideways.
About 20 seconds into the flight, one of the strap-on GEM 63XL boosters experienced a burn-through in its nozzle.
The result was a jet of flame shooting out to one side, creating quite a spectacle. This wasn’t the first time either; this was the second booster failure for ULA’s Vulcan rocket.
The Mission Continues
But you might think this is new, but… it’s not. Despite the early signs of trouble, the mission continued its ascent. By the time the boosters were jettisoned as planned, the unusual rolling motion had ceased. “Early during flight, the team observed a significant performance anomaly on one of the four solid rocket motors,” Gary Wentz, ULA vice president, stated matter-of-factly.
“Despite the observation, the Vulcan booster and Centaur performed nominally.” He went on to say that the launch vehicle still managed to deliver its payload directly into geosynchronous orbit. A statement as direct as the mission itself—no hidden agendas here.
Next Steps
The next steps are clear: review technical data, establish a recovery team, and collect any debris. It’s a familiar process in the space industry, one where every anomaly leads to better understanding for future missions.
“We will conduct a thorough investigation, identify root cause, and implement necessary corrective actions before the next Vulcan mission,” Wentz added.
A Long History
The GSSAP satellite, built by Northrop Grumman, was the primary payload. This is part of an ongoing effort to monitor space surveillance in geosynchronous orbit. But this launch also carried another classified payload, known only as an ESPAStar, a solar-powered deployable platform capable of hosting various smaller satellites.
ULA’s plans for 2026 were ambitious: over 20 launches, including two to four Atlas 5 missions and up to 18 Vulcan flights. That was before the latest hiccup.
The Future?
It remains to be seen how this latest issue will impact ULA’s schedule. The company is no stranger to setbacks, but each one brings valuable lessons. For now, the focus is on recovery and preparation for future missions.
You might think that a booster problem would spell doom for the mission, but in the world of space launch, it’s just another day at the office. Or rather, another anomaly addressed with professionalism and resolve.
