Modern rocketry is somewhere between WWI and WWII aviation. We’re beginning to mass manufacture, but the leading edge advances so quickly that learning curves have limited runtime. Alongside new designs, new materials are being invented and deployed across America and China (and to a limited degree Europe.)<p>Most importantly, we can tune risk and and reward across the production line; the crewed Falcon 9/Dragon launches are <i>far</i> more conservative than their Starlink + rideshare ones.
Tangentially related: Most journalists - especially in tech these days - seem to be doing practically no original or investigative work and simply rehash what they read on Twitter & co. Are there any decent apps that do the same thing? For example I'd like to say "Follow everything SpaceX-related from these primary sources and give me regular updates/summaries". I don't care to read people's opinions on it, just the aggregated raw info would be nice.
> A few minutes after liftoff of SpaceX's Starlink 9-3 mission, veteran observers of SpaceX launches noticed an unusual build-up of ice around the top of the Merlin Vacuum engine, which consumes a propellant mixture of super-chilled kerosene and cryogenic liquid oxygen. [...]<p>> Numerous chunks of ice fell away from the rocket as the upper stage engine powered into orbit, but the Merlin Vacuum, or M-Vac, engine appeared to complete its first burn as planned. A leak in the oxidizer system or a problem with insulation could lead to ice accumulation, although the exact cause, and its possible link to the engine malfunction later in flight, will be the focus of SpaceX's investigation into the failure.<p>> A second burn with the upper stage engine was supposed to raise the perigee, or low point, of the rocket's orbit well above the atmosphere before releasing 20 Starlink satellites [...].<p>> "Upper stage restart to raise perigee resulted in an engine RUD for reasons currently unknown," Musk wrote...<p>For Falcon 9 <i>manned</i> launches, there are a whole series of abort modes and we-didn't-get-to-orbit splashdown locations:<p><a href="https://www.nasaspaceflight.com/2020/05/examining-crew-dragons-launch-abort-modes-and-splashdown-locations/" rel="nofollow">https://www.nasaspaceflight.com/2020/05/examining-crew-drago...</a><p>It'd be interesting to know where in this mission's flight profile, <i>if</i> it had been manned, the launch director would have ordered an abort. That LOX leaks often lead to explosions is Rocket Science 101.
I'd argue that going for 0 failures in virtually any domain will lead to inefficiency. You need some failures to get the feedback that you've "under-engineered" something. Without failures, you can guarantee that you've over-engineered it.<p>In a similar vein, I think proper risk acceptance policies shouldn't say "security/safety is our #1 priority", just like a good SLA doesn't guarantee 100% uptime. When you set a 99.9% uptime SLA, make sure you're actually down sometimes. When you want efficient rockets, you have to see some of them crash.
It doesn’t take rocket science to understand that rockets eventually have a success rate of less than 100% .
(Edited changed failure rate to success from child comment)
Amazing to me that it's <i>not</i> the reused element that failed. It's as though re-flying hardware that's already proven to work is more reliable!