The world's biggest rocket, on its 13th flight, got one second from liftoff before the engines said no. SpaceX's Starship scrubbed Thursday's test flight after a partial engine ignition failure triggered an automatic abort, leaving the 407-foot rocket sitting on the pad while ground crews drained its fuel. Elon Musk, never one to underplay his timeline optimism, hopped on X to promise another attempt 'hopefully in a few days.'
What Actually Happened on the Pad
The New York Post reports that SpaceX's launch webcast caught the whole thing from a drone hovering high above the pad. Engine ignition began three seconds before planned liftoff. Then, something went wrong. Whichever engines managed to fire shut down almost immediately, and the rocket stayed exactly where it was, clamped to the launch structure like nothing had happened.
The launch team moved quickly into abort procedures, which at a facility like SpaceX's Starbase in Texas means starting the long, careful process of draining thousands of tons of propellant from a rocket that was, moments ago, trying to light itself on fire. Flight 13 was over before it began.
Musk posted on X that the company needs to 'figure out what went wrong' before flying again. That's a refreshingly honest framing from someone who once famously predicted Starship would reach orbit within months of its first rollout, a timeline that turned out to be a few years optimistic.
What Was Actually Riding on This Thing
This wasn't just a hardware test. According to the New York Post, SpaceX had 20 of its newest and most advanced Starlink internet satellites packed aboard for the planned one-hour flight. The plan was to release them mid-flight, have them try communicating with Starlinks already in orbit, and use the opportunity to photograph Starship's heat shield from the outside.
Neither the first-stage booster nor the upper-stage spacecraft were going to be recovered on this flight. Both were planned to splash down in the ocean, which is either a sign that SpaceX is still learning or a sign that they can afford to throw away hardware that would make other rocket companies weep. Probably both.
The payload loss is real, though. Twenty next-generation Starlinks sitting in a rocket that didn't go anywhere is not a great Thursday.
The Moon Is Waiting and It Is Not Patient
Here is where the stakes get genuinely high. NASA has bet an enormous amount of its Artemis program on SpaceX getting Starship to actually work. As the New York Post reports, the agency has hired both SpaceX and Jeff Bezos' Blue Origin to build and fly the lunar landers that will take astronauts back to the moon's surface for the first time since 1972.
Both landers, Starship and Blue Origin's Blue Moon, need to be ready to fly by next year. The reason is specific and the timeline is not flexible: the newly named Artemis III crew needs to practice docking their Orion capsule with the landers in Earth orbit before anyone tries doing it near the actual moon. That's not a ceremonial milestone. That's a safety prerequisite.
The mission after that, Artemis IV, is planned for no earlier than 2028 and would use one of those landers to put two astronauts down at the moon's south polar region. So Starship going 0-for-1 on a test flight in July 2026, with engines that wouldn't start, is the kind of setback that has ripple effects through a program measured in years.
Flight 13's Unlucky Number Energy
Look, nobody is superstitious. Rocket science runs on physics and fluid dynamics and about 40,000 lines of code, not numerology. But if you were writing a screenplay about a cursed rocket program, you would absolutely set the big engine failure on Flight 13, one second from liftoff.
Starship has had a complicated testing history. Early flights ended in dramatic explosions that SpaceX cheerfully called 'rapid unscheduled disassembly,' a phrase that deserves its own entry in the lexicon of corporate euphemism. The program has made genuinely impressive progress since those early fireball-heavy days, successfully catching the booster with the launch tower's mechanical arms in a trick that still seems impossible every time the footage plays. But 'progress' and 'ready to land humans on the moon' are not the same sentence, and Thursday was a reminder of that gap.
The Dingo Take
The thing about Starship is that it represents the most technically ambitious thing anyone in the private space industry has ever attempted, and it is being rushed, because of course it is, by a timeline set by a government program that has its own history of laughably optimistic scheduling. NASA's Artemis program has slipped so many launch dates at this point that 'no earlier than' has become the de facto unit of time in the human spaceflight business. So when SpaceX's most important rocket can't get its engines to fire one second from launch, it lands differently than a routine scrub.
Musk will say the fixes are close. He always says the fixes are close. Sometimes he's right, and sometimes 'a few days' becomes a few months, and the astronaut community sits in a conference room somewhere quietly updating their contingency plans. The honest answer is that nobody outside of SpaceX's propulsion team knows yet what actually failed Thursday, and until they do, any timeline is a guess dressed up as a forecast.
What's not in question is that the world's biggest rocket, carrying the world's most consequential lunar lander program, sat on a pad in South Texas and refused to go anywhere. NASA is counting on this thing. The Artemis III crew is counting on this thing. The entire political argument for why America is going back to the moon before China does is partly built on this thing working. One second to liftoff. Then silence. That's not a catastrophe yet. But it's not nothing, either.
