SpaceX is about to run Starship's 13th test flight.
The rocket will fly higher, pressurize its tanks harder, and push closer to orbital velocity than before. The company is also deploying actual Starlink satellites on the flight — moving from dummy payloads to real hardware.
This is being covered as incremental progress. It is. But the framing conceals something worth examining. The assumption is that you can learn how to build a reusable orbital rocket primarily by launching it repeatedly, rather than by systematically breaking it on the ground first.
Every previous rocket designed for reuse operated under a different principle. The Space Shuttle's main engines, the RS-25, went through thousands of hours of ground testing before a single flight. Engineers ran them to failure in controlled environments. Mapping the exact temperatures and pressures at which turbine blades would crack, where seals would rupture, what margin of safety actually existed. They learned by destroying dozens of engines methodically.
This saves time and money. It also assumes something unproven. Orbital testing can compress the knowledge-building that destruction normally provides. You can find your failure modes by pushing incrementally rather than catastrophically. The assumption has not been tested because testing it requires either a flight failure or abandoning the whole method. And neither proves anything. If a Starship flight succeeds, the method looks sound. If it explodes, the method produced an expensive learning. Either way, SpaceX gets data, but the question is whether iteration in space can do the job that destruction on the ground has always done. Nobody knows yet, because if it fails, the difference between learning something and this approach not working becomes a matter of narrative, not measurement.