SpaceX Cancelled Starship Flight 13 at T 0 due to an Unexpected Serious Issue! No Launch until…

Confusing and disappointing. That's probably how Starship fans are feeling right now. After coming within seconds of liftoff, Flight 13 was suddenly aborted at T-minus zero because of an engine issue. So what exactly happened? How serious is the problem? And when can we expect the next launch attempt? We'll also cover B-21's latest milestone for Flight 14 and a notable Falcon 9 military mission. Let's dive in on today's episode of Great SpaceX to find out more. If there's one thing Starship has taught us, it's that no launch campaign is ever straightforward. Unexpected issues can appear right up until the final seconds, which is why following every update is so important. So if you haven't already, consider subscribing to join our community. You'll be among the first to hear the latest news from SpaceX and the aerospace industry as Starship enters one of the most important phases of its development. Now, back to today's story. Flight 13 was scheduled to launch at 5.45 PM on July 16th. The date carried extra significance because it marked the 57th anniversary of Apollo 11's historic launch. Leading up to liftoff, everything appeared to be going perfectly. The countdown stayed on schedule. The detonation suppression system test was successful. The shift flap checks were completed without issue. Propellant loading proceeded smoothly. The weather cooperated. Even during the planned T-60 hold, SpaceX remained confident, stating, All systems continue to look good for today's flight test, before resuming the countdown. Then came the moment everyone had been waiting for. Water flooded the launch mount. The engines began to ignite. Flames appeared beneath the booster, but Starship never left the pad. Something had gone wrong. A short time later, SpaceX officially called off the launch attempt. The obvious question became, what happened? The engine startup sequence tells the story. Although the ignition process began, not every Raptor came to life. At T-0, only 29 engines appeared to ignite on the engine status display. Four engines in the middle ring, arranged in two neighboring pairs, failed to light. Less than a second later, the onboard computer shut every engine down and automatically aborted the launch. Propellant was safely drained from the vehicle, and thankfully, no additional issues followed. Instead of a launch, Flight 13 accidentally turned into a very expensive mini-static fire. Soon afterward, Musk confirmed the cause, posting, Some of the engines didn't start, triggering an automatic launch abort, now offloading propellant. It's worth giving credit to SpaceX's launch software. Before anything else, it's worth giving credit to SpaceX's launch software. The system recognized the problem instantly and aborted the countdown before the rocket ever left the ground. That's exactly what it's designed to do. Nobody wants to see a launch scrub, but everyone would rather see one on the ground than watch a preventable failure unfold in the air. Failure unfold in the air. The bigger concern is what comes next. In another update, Musk wrote, Next launch attempt hopefully in a few days. The wording immediately suggested this wasn't a simple reset. If the issue could be fixed within hours, there would be little reason to wait several days. Then Musk shared another important update. To be confident of a good flight, two Raptors will be removed and replaced. That gives us a much clearer picture of what's ahead. Replacing Raptor engines isn't a quick task. The damaged engines must be removed, replacements installed, and everything thoroughly checked afterward. SpaceX may also choose to perform another static fire to verify the new engines before attempting another launch. There is even the possibility that Starship will need to be destabbed. Interestingly, both transport stands had already left the launch pad before the countdown, heading toward Sanchez. After the scrub, however, they returned to the pad, hinting that additional hardware work could be required. So what actually caused the problem? That's still the biggest mystery. B-20 had previously completed one of the longest static fires ever performed by a Super Heavy booster, running for roughly 25 seconds. The booster then returned to the production site for inspections before rolling back to the launch pad only two days later. Everything pointed toward a healthy vehicle. That raises two possibilities. Either something changed after the static fire, perhaps during transport or final preparations, or an issue existed that wasn't detected during inspections. Since only four individual engines failed while the rest behaved normally, the problem likely wasn't located in the main propellant tanks or central feed system. If it had been, many more engines would probably have been affected. Instead, the issue may have involved hardware unique to those individual engines. Possible candidates include the igniters, individual propellant lines, or injectors. There's another interesting possibility as well. SpaceX previously confirmed that some Raptor engines originally assigned to B-19 were reused on B-20. After B-19's interrupted static fire campaign, we don't know exactly where those engines were installed. It's possible that one, several, or even all four of the engines involved came from that earlier hardware set. If so, the underlying issue may not have been completely eliminated. Of course, that's still speculation. For now, only SpaceX knows the exact cause. What this does show is that achieving rapid, fully reusable rockets remains an enormous engineering challenge. Raptor 3 continues improving, but perfection takes time. Had those four engines failed during flight instead of during ignition, the consequences could have been severe. The booster would have lost a significant amount of thrust. The imbalance might have affected guidance and control. Landing capability could also have been compromised later in the mission. Fortunately, the system detected the problem before Starship ever left the ground. As frustrating as the delay may be, it's far better to replace two engines now than lose an entire vehicle during flight. So when will Flight 13 finally launch? Musk's latest guidance provides our best clue. After first saying a few days, he later added most probable launch timing is early next week. That points to a launch attempt around Monday or Tuesday, assuming repairs go smoothly. So while we enjoy the weekend and, for many fans, the closing matches of the 2026 FIFA World Cup, SpaceX engineers will likely be working around the clock to get Starship ready again. Let us know your prediction before SpaceX announces an official date. And if you'd like to encourage the team, leave a keep going in the comment section down below. This delay may be disappointing, but it could also make a successful launch even more satisfying when it finally happens. Now let's shift our attention to another piece of Starship hardware. While Flight 13 has everyone's attention, SpaceX is already preparing for Flight 14 in pursuit of the monthly launch cadence, Winshot well recently discussed. Work has been progressing steadily for weeks. S41 completed cryogenic testing between S40's own campaigns, and now B21 is taking its turn. B21 has finished stacking after its forward section arrived at Megabay 1 on June 22nd. A road closure was scheduled from the production site to Massey's between late July 16th and early July 17th. A booster transport stand also appeared that afternoon, making it very likely that B21 rolled out shortly afterward. The goal is straightforward. Complete cryogenic testing, return to the production site for inspections and engine installation, then prepare for static fire testing. If everything stays on schedule, B21 could reach the launch pad in early August. That timeline keeps Flight 14 on track for an August launch. S41 is progressing alongside it. After completing cryogenic tests, the vehicle is likely receiving its engines before beginning its own static fire campaign later this month. Assuming no major issues appear, both vehicles could be ready in time to support SpaceX's first monthly Starship launch cadence. So, buckle up! The second half of the year could be incredibly busy. Finally, let's talk about another successful mission from SpaceX. While attention was focused on Starship, Falcon 9 quietly completed an important launch for the U.S. military. The mission lifted off from California's Vandenberg Space Force Base at 4.32pm EDT on the 16th of July. Falcon 9 carried 21 satellites for the Space Development Agency's Tranche 1 transport layer constellation. The launch proceeded flawlessly. About eight and a half minutes after liftoff, the first stage landed safely aboard the drone ship Of Course I Still Love You in the Pacific Ocean. It marked the fourth flight for booster B1103. Meanwhile, the upper stage continued carrying the satellites toward low Earth orbit. At the request of the Space Development Agency, SpaceX ended its live webcast shortly after booster landing, so deployment details weren't shown publicly. These satellites are part of the Tranche 1 transport layer, a secure communications network operated by the U.S. Space Force's Space Development Agency. According to the SDA, the system will provide global communications access and deliver persistent regional encrypted connectivity in support of warfighter missions around the globe. The completed constellation will consist of 126 satellites built by York Space Systems, Lockheed Martin, and Northrop Grumman. With this mission, 63 of those satellites have now been launched across three Falcon 9 flights. The constellation itself is only one layer of a much larger project known as the Proliferated Warfighter Space Architecture. The SDA describes it as a proliferated constellation of hundreds of optically linked small satellites in low Earth orbit, delivering capability at speed to the warfighter. The agency also explained, SDA leverages spiral development to deploy and proliferate new capability into a new generation of the PWSA every two years, called a Tranche, to continually increase capability used by the warfighter. Once again, Falcon 9 demonstrated why it remains one of the world's most trusted launch vehicles for high priority missions. Now imagine what missions like these could look like once Starship reaches full operational capability. If you enjoyed today's breakdown of Flight 13's launch scrub, B-21's progress toward Flight 14, and Falcon 9's latest military mission, make sure to hit that like button. Subscribe and turn on notifications so you don't miss the next Starship launch attempt and all the latest developments from SpaceX and the aerospace industry. Now I'd love to hear what you think. What do you believe caused the Flight 13 abort? Do you think replacing the two Raptor engines will be enough for a successful launch early next week? And once Flight 13 finally flies, do you expect it to reach orbit or will SpaceX stick with another suborbital test? Leave your predictions in the comments below. It'll be fun to look back and see who called it before liftoff and I always enjoy reading your thoughts. Thanks for watching and here's hoping the next countdown ends with Starship climbing into the sky instead of shutting down on the pad. 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 and until next time, keep looking up!