News
SpaceX Starship booster survives explosion
A SpaceX Super Heavy booster was rocked by a substantial explosion and subjected to multiple fires at the launch pad during the rocket’s latest round of testing.
As of 9 pm CDT, July 11th, the fate of the upgraded Super Heavy – known as Booster 7 or B7 – is leaning towards survival but and it won’t be certain until the rocket is drained of all cryogenic propellant and potentially flammable gas and safe for SpaceX employees to approach. The incident began around 4:20 pm CDT, when Super Heavy Booster 7 (or its launch mount) unintentionally ignited a cloud of flammable gas produced during flow test involving most or all of its 33 Raptor engines. In the past, SpaceX has performed “spin prime” tests with Raptors installed on Starship prototypes, flowing high-pressure gas through the engines’ turbines to get them up to operating speeds and pressures. Booster 7’s test ended a bit differently.
When the resulting cloud of well-mixed methane and oxygen gas was accidentally ignited, it functioned like a small fuel-air bomb, rapidly combusting to produce a violent explosion and shockwave. After the initial explosion, the fire also expanded to burn as much of the resulting gas as possible, producing a fireball that briefly reached 80-90 meters (~260-300 ft) in height. CEO Elon Musk – apparently not directly participating in the test – initially stated that the explosion and fire was planned, implying that it was more or less a nominal outcome. Virtually everyone with experience observing Starship testing felt otherwise, however.
To preserve the safety of the few local residents still living at Boca Chica Village, SpaceX is required to issue printed safety warnings well in advance of Starship tests that could create a shockwave capable of shattering glass and injuring locals. SpaceX has never intentionally performed such a test without distributing those warnings and did not distribute a warning before July 11th, all but guaranteeing that no ignition event was planned. A few hours later, Musk deleted his original tweet and posted a different one, confirming that the explosion was “actually not good” and that SpaceX is “assessing the damage.”
For the most part, Booster 7 and the Starbase Orbital Launch Site (OLS) exceeded viewers’ expectations of their sturdiness, exhibiting very little off-nominal behavior after being subjected to a unexpected explosion, shockwave, and fire. Immediately after the event, B7 quickly depressurized its propellant tanks and appeared to leave those vents open, reducing the chances of the booster destroying itself if SpaceX were to lose control. SpaceX also appeared to intentionally avoid using the orbital launch mount’s (OLM) umbilical mechanism to remove propellant from the Super Heavy’s tanks, perhaps concerned that the shockwave might have weakened its connection to B7.
About an hour after the explosion, Booster 7 dumped a large amount of cryogenic liquid out of a new vent located on its aft end, producing a flood that spread around the adjacent pad. It’s unclear if that liquid was nitrogen or oxygen but either way, the emergency propellant dump appeared to cause a fire to start about 100 feet (~30m) from the booster and launch mount. That fire proceeded to burn intermittently for the next two hours, all the while posing a clear and present danger to the rest of the pad and booster if it were to spread in the wrong direction or breach the wrong underground pipe. Instead, SpaceX got lucky and the fire eventually self-extinguished.
In a worst-case scenario, Super Heavy’s engine section and 33 Raptor engines could have been seriously damaged, while the subsequent pad fire(s) could have also significantly damaged crucial pad systems, requiring weeks of repairs. The booster could even be beyond repair. More optimistically, given that SpaceX appears to have gotten lucky enough to avoid a total loss of vehicle, Booster 7 may be fine after some inspections and moderate repairs. The pad damage could also be limited to a single isolated, non-critical piece of equipment catching fire and burning to a crisp
Regardless, SpaceX will need to figure out what exactly caused the explosion and make sure that that failure mode does not appear again. In the meantime, the company recently finished stacking Super Heavy Booster 8, and Starship S24 – installed on a nearby suborbital test stand – is ready to begin its own static fire test campaign in the near future.
Tesla’s Automatic Collision Evasion feature can be seen in one of the first owner videos of it in action.
Tesla owner Spencer (@scotsrule08) posted on Monday that the feature “worked flawlessly,” saying FSD reengaged itself just as he was about to hit a curb. Ashok Elluswamy, who leads Tesla’s AI team, shared the clip and wrote, “A guardian angel always looking out for you.”
The video arrives in the middle of a staged rollout. Tesla first shipped Automatic Collision Evasion with FSD (Supervised) v14.3.9 in software update 2026.27.6 earlier this month, which Teslarati covered as it reached cars. Update 2026.27.10, which began going out on September 19, carried the feature improvements with FSD v14.3.10, according to release notes tracked by Not a Tesla App. The newer 2026.27.11 build is now reaching another wave of vehicles.
The new Automatic Collision Evasion feature worked flawlessly! FSD reengaged itself just as I was about to hit a curb.
Kudos @Tesla_AI team! 👏 pic.twitter.com/Fbp15HhpL2
— Spencer (@scotsrule08) September 28, 2026
The feature only runs on HW4 vehicles, and it requires an active FSD purchase or subscription with both FSD (Supervised) and Automatic Emergency Braking enabled. HW3 owners receive FSD v14.2 Lite in the same updates, but that build does not include collision evasion.
Tesla’s release notes describe two triggers. The first is an imminent frontal collision that braking alone may not prevent, in which case the car can activate FSD to steer, brake or accelerate around the hazard. That scenario is limited to highways below 85 mph, with no pedestrians or cyclists detected and no slippery road surface. The second covers a driver who appears inattentive, such as reaching into the back seat, or who seems to have switched off FSD by accident. Spencer’s curb clip appears to fall into that second category.
Tesla plans big safety improvements for Full Self-Driving v15
Once the system takes over, the accelerator is muted and light brake input will not cancel the maneuver. Drivers need to apply firm, deliberate steering force to take back control, and the car chimes to hand control back once the danger has passed.
Elluswamy recently noted that earlier hazard prediction, faster reaction time and better collision avoidance would arrive with FSD v15, the next major version.
Tesla is delaying its event for the Roadster, moving it from this Thursday, October 1, to Thursday, October 15, due to unfavorable weather.
The company has said it has been tracking the weather for this Thursday closely with local meteorologists, and because the event can only be held outside, Tesla is making the call to delay it:
“We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule. New date is October 15. Additional details to follow.”
Roadster event update
We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule.
New date is October 15. Additional details to…
— Tesla (@Tesla) September 28, 2026
We are sure that this is bringing back PTSD for some Tesla fans, and we know it is not ideal, but this also reveals some things about the event. Tesla said that this can only be held outdoors, meaning it bodes well for the rumors that the vehicle could potentially hover.
Some believe that this was essentially confirmed by the FAA airspace restriction they were granted, but this could have been for a drone show or to keep drones from spying on the event.
Tesla Roadster is available for order once again following brief hold
The Roadster event has been long-awaited, and it is unfortunate that the weather is going to keep us all waiting a little bit longer.
The Tesla Roadster will be unveiled in Waco, Texas.
Elon Musk
SpaceX turned a heralding moment for Starship into its greatest
Starship reached orbit despite losing an engine, deployed 26 Starlink V3 satellites on Flight 14.
SpaceX’s Starship reached orbit for the first time on Monday, and for a few nail-biting minutes it looked like it wouldn’t. During ascent on Flight 14, one of Ship 41’s six Raptor engines shut down early, and SpaceX’s livestream host Dan Huot told viewers the team had decided not to commit to orbit. Minutes later, after what Huot described as a lot of conversation in the control room, the final poll came back in favor, and a roughly 19 second burn of a single Raptor pushed the ship into orbit about 170 miles up.
The reversal matters because SpaceX had written the exit ramp into the mission plan. The company said it would only fire the orbital insertion burn if flight controllers confirmed enough backup hardware remained for the deorbit burn, a condition Teslarati laid out ahead of the flight. Losing an engine was exactly the scenario that rule was built for.
Pressing forward fits Elon Musk’s history. Falcon 1 failed three straight times before its fourth launch reached orbit in 2008, with SpaceX nearly out of money, and Starship was developed by flying prototypes until they broke. What changed this year SpaceX going public, and with $SPCX sliding below its IPO price in July when Flight 13 slipped, the short interest climbed significantly, as Teslarati reported at the time. A Starship potentially lost today with revenue generating next-gen Starlink satellites aboard would have landed directly on shareholders.
Splashdown confirmed. Congratulations to the entire SpaceX team on the first orbital flight of Starship! pic.twitter.com/urjmiwnvNl
— SpaceX (@SpaceX) September 28, 2026
That pressure showed up after orbit. SpaceX cut a flight planned to last nearly 10 hours to about three, moving splashdown from west of Chile to the North Pacific near Hawaii. SpaceX gave no reason, though Musk said this month the company was being extremely cautious about debris risk. The single Raptor for deorbit worked, and Ship 41 completed its flip and landing burn before breaking apart in the water, an outcome SpaceX expected. Musk has structured SpaceX’s governance to shield long term bets from market pressure.
The payload is the bigger business story. Musk posted that all 26 Starlink V3 satellites deployed and are “operating nominally.” Each V3 is rated for about 1 Tbps of downlink and 160 Gbps of uplink, so this single launch adds roughly 26 Tbps, about 10 times what a Falcon 9 load of V2 Mini satellites adds. The V3 is too large for Falcon 9, making Starship the only vehicle that can build out the planned 100,000 satellite constellation, at up to 60 per flight once it reaches routine service. Unlike the 20 V3 units on Flight 13, which reentered on a suborbital path, these will raise their orbits and could begin serving customers within weeks and bring in hundreds of millions of additional dollars in projected Starlink revenue.
SpaceX has already begun winding down Falcon 9 Starlink launches from Florida in favor of Starship. Reported targets put Flight 15 as early as October 19, leaving about three weeks to diagnose Monday’s engine shutdown before the next orbital attempt.
Starship’s 14th flight is set to launch on Monday, Sept 28. The 75-minute launch window opens at 7:15 a.m. CT. Live coverage of the mission starts ~35 minutes before launch → https://t.co/uQKQvgaTmJ
— SpaceX (@SpaceX) September 27, 2026
Watch Tesla’s “guardian angel” FSD feature take over for collision evasion
Tesla Roadster event gets delayed due to unfavorable weather
