Half the Rocket Made History, Half Blew Up: What Starship Flight 15 Taught Me About Shipping

Yesterday, November 14, 2026, a spaceship spent about 22 hours in orbit, came back to Texas, and the tower that launched it caught it in mid-air.

On the same flight, the other half of the rocket blew up over the Gulf of Mexico.

I've been shipping software for 15+ years, and I've had release days like that. I just never had one filmed by half the planet.

What actually happened

SpaceX launched Starship Flight 15 from Starbase in South Texas. According to Engadget, the plan was a double catch. The Super Heavy booster would come back to the tower first, and the upper stage (the "Ship") would try its own catch about a day later.

The Ship went to orbit, deployed 26 Starlink V3 satellites, and stayed up for roughly 22 hours. Then it came back, and the tower's arms, nicknamed "chopsticks", caught it. Teslarati reports that this is the first time a company has returned an orbital upper stage to its launch site and caught it.

The booster had a worse day. Its guidance system detected a problem during descent and aborted the catch. Both reports say it was destroyed over the Gulf before it reached the water. Teslarati quotes Elon Musk blaming slightly underperforming engines that left too little fuel for the trip back.

One half made history and the other half became fireworks.

Why a non-space person should care

Most rockets are like buying a car, driving it once, and pushing it off a cliff.

SpaceX already lands the bottom stage of its Falcon 9 rockets, which is why launch prices fell over the last decade. The top stage still gets thrown away on almost every flight in the industry. That top stage is the part that actually goes to orbit, and it's full of expensive engines and electronics.

A top stage you can catch is one you can inspect, refuel and fly again. If that becomes routine, getting things into space starts to look less like a one-off project and more like running an airline. That's the whole bet, and yesterday was the first time it worked for real.

One catch is not a system, though, and I'll come back to that.

The part every developer recognises

What I liked most wasn't the catch. It was the mess around it.

In my experience, real launches rarely go clean. One feature you were nervous about works perfectly, and the boring part you didn't worry about falls over. Then the team spends an hour arguing about whether to call it a success.

I've shipped releases where the headline feature landed and the billing job quietly broke the same evening. Those days feel bad in the moment. Looking back, I learned more from those than from the clean ones.

SpaceX seems to work the same way, just with much louder bugs. They fly, something breaks, they fix it and fly again. The booster loss doesn't erase the catch, and the catch doesn't excuse the booster loss. Both are data.

The fair criticism

Skeptics have a point, and I don't want to skip it.

One successful catch doesn't make a reliable system. Airlines don't celebrate the first time a plane lands. They celebrate the ten-thousandth boring landing. Losing a booster also costs real money, and a fireball on every other flight isn't a business.

There's also a habit in tech of treating every "first" as if the problem is solved. It isn't. The hard part now is doing this again and again without drama.

Still, I'd rather see a team learn in public with half the rocket intact than one that polishes something for years and never launches.

What I'm taking from it

The lesson I'd steal for my own work isn't about rockets. It's about the top stage.

In most projects there's an expensive piece we rebuild every time because reusing it feels hard. It might be a setup script, an onboarding flow, a deployment process, or a pitch deck rebuilt from zero for every investor. We throw it away after one use because catching it would take effort.

So here's a small check you can do this week: