"Raptor Shielding Failed!'' SpaceX Revealed WHY Starship Booster 19 Brutally Exploded...

The launch delivered one of the most dramatic Starship flights we've ever seen. B-19 faced serious problems during descent and was ultimately lost before splashdown. Meanwhile, S-39 delivered a surprisingly strong performance and completed several critical milestones that SpaceX has been trying to achieve for a very long time. Was Flight 12 a success? And if so, how successful? Some people are already calling it an 85-90% success rate. Others are arguing lower. So let's break down everything that happened on today's episode of Great SpaceX. Ironically, the story almost felt like a rewind of the previous day. Once again, everybody gathered for the countdown. Once again, excitement was sky high. Once again, viewers nervously stared at the clock after the previous scrub. But this time, something immediately felt different. There were no major delays, no endless sliding launch windows, no countdown limbo. 5.30pm Central arrived exactly as scheduled. And interestingly enough, this launch also featured a very important guest. NASA Administrator Jared Isaacman was present at Starbase for the flight, which added even more significance to the event. Because this was not just another Starship test anymore, this was becoming a serious demonstration of the future direction of American spaceflight. As the countdown continued, fueling operations began smoothly, and once again, the upgraded fueling systems at Pad 2 performed incredibly fast. Massive quantities of cryogenic methane and liquid oxygen rushed into the vehicle at astonishing speed. Engine chill procedures also occurred successfully. At this point, SpaceX's ground systems were already proving themselves, and that matters a lot. Because rapid fueling capability is essential if Starship is ever going to support high launch cadence operations in the future. Then came the moment that made everybody collectively tense up. T minus 40 seconds. The hold command appeared again. Immediately, viewers everywhere probably experienced flashbacks from the previous scrub. You could practically hear millions of people whispering, please not again. But this time, something different happened. The countdown resumed normally. No resets, no rollback, no scrub. The clock simply continued downward. That alone represented a major victory for the SpaceX team, because it confirmed they had successfully repaired the SQD system issues that caused the earlier cancellation. And honestly, solving a problem that quickly on such a massive and complex launch system is incredibly impressive, especially considering the scale of Starship operations. We're talking about the largest rocket ever built, not somebody rebooting a Wi-Fi router. Then came the moment everybody had been waiting months to see. Liftoff. Water erupted upward from the flame trench, creating an almost cinematic wall of spray surrounding the vehicle. Then all 33 Raptor engines ignited, and Starship Flight 12 finally rose into the sky. No immediate pad damage, no catastrophic launch mount failure, no tower impact. The vehicle climbed beautifully away from starbase, and that alone was already a huge improvement compared to earlier generations of Starship flights. The first phase of ascent looked remarkably smooth, but after that, the booster and ship began very different journeys. And B-19's story became significantly more dramatic. Initially, the booster performed well during ascent. However, at approximately T plus one minute and 43 seconds, one of the outer ring engines shut down unexpectedly. Immediately, speculation began. One of the leading theories involves the removal of protective shielding around the Raptor 3 engines. Previously, SpaceX included more extensive thermal shielding, but with V3, the company appeared confident enough in Raptor reliability to reduce some of that protection. Unfortunately, this may have introduced new vulnerabilities. Because even though the engines are more advanced, the environment around Super Heavy remains absolutely brutal. Extreme vibration, shock waves, heat, pressure, and enough mechanical violence to make a washing machine full of bricks seem relaxing. If one engine experienced damage or power instability, it may have triggered secondary issues affecting nearby systems, and that potentially contributed to later booster failures. Fortunately, Starship's multi-engine architecture gives it significant redundancy. Losing one engine during ascent does not automatically doom the mission. Performance decreases slightly, but the vehicle can still continue flying. And that is exactly what happened. B-19 successfully reached stage separation. At T plus two minutes and 23 seconds, the booster shut down most of its engines. Five remained operational, including three inner engines and two middle ring engines positioned symmetrically. Then things became extremely strange. Between approximately T plus two minutes and 32 seconds and T plus two minutes and 49 seconds, the booster engines began firing in a very unusual pattern. Some engines ignited, others shut down. Then additional engines reignited across different rings. The pattern looked almost random. At one point, the engine configuration barely resembled anything from previous Starship flights, and visually some thrust appeared asymmetrical. One side appeared stronger than the other, the booster almost looked like it was improvising. Like a shopping cart with one broken wheel trying its absolute best. This maneuver was likely part of SpaceX's new active flip procedure. Previous Starship versions relied heavily on hot staging exhaust dynamics to help rotate the booster after separation. But with the updated hot staging system, SpaceX appears to be transitioning toward a more engine-driven active flip maneuver. That means the booster itself now uses controlled engine thrust to rotate into the proper orientation for descent. It's more aggressive, more dynamic, and apparently much more complicated. Following the flip maneuver, B-19 continued descending toward the Gulf. The vehicle passed through transonic and subsonic flight regimes. As atmospheric pressure increased, strong airflow became visible around the engine section. Eventually, the ocean came into view. Then came the final landing sequence. At approximately T plus 6 minutes and 11 seconds, the landing burn initiated. Or at least partially initiated. The exact number of engines active remains unclear. But almost immediately, things looked wrong. At around 100 meters above the water, the booster was still traveling at roughly 1,455 kilometers per hour. That is not ideal. That is less controlled landing and more angry meteor with paperwork. The onboard camera feed suddenly stopped, which strongly suggests B-19 exploded before actually impacting the water. Later, SpaceX released a statement summarizing the situation. Following stage separation, the Super Heavy booster performed a directional flip maneuver and attempted its boostback burn. It was unable to light all planned engines and performed a partial boostback burn that ended early. Super Heavy attempted to reignite its engines for the landing burn before experiencing a hard splashdown in the Gulf of America. That explanation confirms several important things. Most notably, not all engines relit successfully during critical descent phases. And based on the timeline, the landing burn likely started too late. Compared to the previous flights, the timing was noticeably delayed. Earlier missions initiated landing burns more than 15 seconds before splashdown. This time, ignition occurred only seconds beforehand. That left insufficient time to slow the booster adequately. As a result, aerodynamic stress and extreme velocity likely destroyed the vehicle before water impact. So what caused the delayed landing burn? At the moment, there are several possibilities. One theory involves communication or command timing problems during high-pressure atmospheric descent. Another possibility is that the earlier active flip maneuvers affected engine reliability. Repeated ignition sequences may have damaged certain systems or reduced engine availability later in the flight. And considering how aggressively the engines were cycling during the flip, that possibility seems entirely plausible. Still, despite the loss of B-19, the mission continued. Because high above Earth, S-39 was having a much better day. At T plus 2 minutes and 27 seconds, the ship activated all six of its engines successfully. However, not everything remained perfect. At approximately T plus 3 minutes and 3 seconds, one Raptor vacuum engine appeared to fail. Later footage made this even more obvious. At T plus 7 minutes and 29 seconds, camera views of the engine compartment showed one engine inactive with unusual smoke surrounding the area. Clearly, something malfunctioned. But importantly, the remaining five engines continued operating normally. And critically, the ship still achieved its ascent objectives. SpaceX later confirmed ascent burn completion and successful orbital coast. At T plus 9 minutes, S-39 completed engine shutdown and entered one of the mission's most important phases, payload deployment. Around T plus 17 minutes, the payload door opened smoothly. And by T plus 19 minutes, the first payload deployed successfully. Additional payloads followed, including experimental observation and communication hardware. Some even carried cameras designed to film Starship itself. That produced one of the mission's most incredible moments, external selfie footage of Starship drifting through space. And I've gotta say, looks straight out of sci-fi. Meanwhile, the in-space engine relight also appears to have succeeded. Another major milestone for future orbital operations. Then came re-entry. Beginning around T plus 42 minutes, plasma built around the vehicle as S-39 endured nearly 20 minutes of extreme atmospheric heating. And remarkably, it handled the phase very well. By T plus 59 minutes, the ocean was visible below. Flaps remained operational and the heat shield appeared dramatically, dramatically improved compared to earlier flights. Some damage was still visible, but the massive oxidation streaking seen on previous missions was largely absent. A major sign of progress for reusability. Then came the landing burn. At T plus one hour six minutes, ship ignited only two engines for descent. According to SpaceX, this was intentional. To simulate an engine out landing scenario. Ship descended relatively gently into the ocean and initially remained structurally intact before rolling over and exploding on contact with the water. Which sounds catastrophic, except the destruction was planned. And the crowd at Starbase still cheered. Because despite losing the booster, flight 12 achieved a huge number of critical objectives. Successful ascent, stage separation, pale deployment, orbital coast, engine relight, improved heat shield performance, controlled re-entry, and an engine out landing test. For SpaceX, progress matters more than perfection. And flight 12 delivered a lot of progress. Now, while Starship continues evolving, NASA is also preparing for another extremely important technological milestone. Orbital refueling. Long tied to SpaceX and Starship, since the company's lunar plans rely on transferring cryogenic fuel in orbit, NASA is now pushing into the field as well. Later this year, NASA plans to launch LOXSAT aboard a rocket lab photon spacecraft on an electron rocket from New Zealand. The mission will study how liquid oxygen behaves in microgravity and test 11 cryogenic fluid management technologies over 9 months. The goal? Future orbital fuel depots. Basically, space gas stations. The project, developed with ETA Space, is especially important for Artemis. Both Starship and Blue Origin's blue moon lander depend on cryogenic propellants, yet long-term orbital fuel storage remains a major challenge. That is why LOXSAT matters. If successful, it could make orbital refueling a core part of future deep space travel, a concept that once sounded absurd, but now feels increasingly inevitable. That brings us to the end of today's episode. Thank you so much for tuning in. As always, this has been Kevin from GreatSpaceX. Until next time, keep looking up!