I set an alarm for 7:15am on a Thursday to watch a rocket. Not even a rocket I own stock in or have any real stake in. I just wanted to see it. That's the kind of thing this blog has apparently turned me into over twelve years, someone who sets alarms for rockets.
So: SpaceX's Starship, the biggest rocket ever assembled, lifted off from Starbase down in Boca Chica, Texas on Thursday morning, April 20th. Thirty-three Raptor engines on the booster alone, more thrust than the Saturn V, more thrust than anything humans have built before. It got off the pad around 8:33am Central. It flew for about four minutes. Then it started tumbling end over end, several thousand feet up, and SpaceX triggered the flight termination system and blew it up on purpose before it could do that on its own somewhere less convenient.
Everyone's already written the "here's what happened" post this week, so I'm not going to bother repeating the whole timeline. You've read it three times by now if you follow any tech news at all. What I keep coming back to instead is the parking lot.
See, the launch pad at Starbase doesn't have a flame diverter or a water deluge system yet (the giant trench-and-sprinkler setup that normally sits under a rocket to redirect all that engine exhaust somewhere safe). Starship didn't have one. So thirty-three engines lit up directly against a slab of reinforced concrete, and the concrete just... lost. It turned to dust and shrapnel and got thrown for miles. There are videos of a literal dust cloud rolling over Port Isabel, six miles away, coating cars and porches in a fine gray grit. Reports of chunks of concrete landing near a state park and starting a small brush fire. Someone posted a photo of their windshield with what looked like pea-gravel dents in it.
That's the part that stuck with me more than the tumble-and-explode footage, honestly. Not because it's a bigger deal than the actual test flight failing to stage (it isn't) but because it's such a specific, dumb, physical consequence that nobody really war-gamed out loud beforehand. Everyone was worried about the rocket. Almost nobody was talking about the pad eating itself and mailing pieces of Texas to the neighbors.
I watched the whole thing on the NASASpaceflight livestream with the chat scrolling by so fast it was basically unreadable, coffee going cold next to my keyboard, my cat deeply unbothered by any of it. And I'll admit the whole "well actually this is a success, we cleared the tower" framing that SpaceX and a lot of the coverage leaned into afterward rubbed me a little wrong at first. Call me old-fashioned but a rocket that ends in a fireball four minutes in feels like it should get to be called what it looks like. Then again (and I hate agreeing with the PR framing, I really do) that is genuinely how this company has built every vehicle it's ever flown. Blow it up, find out exactly why, fix that one thing, try again in a few months instead of a few years. Falcon 9 ate itself on a barge a bunch of times before it started landing like it was stepping off a curb. I've just never watched the "eating itself" part happen on a rocket this size, with this much concrete flying, live, at 8am on a weekday before I'd had a full cup of coffee.
The FAA has grounded any repeat attempt until there's an investigation, which, sure, obviously, you can't have a rocket sandblasting a fishing town every time you want to test something. I'd guess we're looking at months before the next full-stack attempt, not weeks. There's a whole redesigned pad system that apparently needs to go in now, deluge system and all, and that's not a quick pour.
Anyway. I'm glad I got up for it. I don't think I'll set an alarm for the next one unless someone tells me the pad's actually finished this time.