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.
A new report from Reuters claims that a transport authority in Sweden is pushing back against the approval of Tesla’s Full Self-Driving suite because it will travel over speed limits.
The report says the Swedish Transport Administration (TRV) recommends the European Union votes against FSD’s approval. TRV believes it should not be approved until Tesla disables FSD’s ability to speed.
TRV sent a letter to the European Union’s Technical Committee on Motor Vehicles (TCMV), which is set to meet on June 30 to discuss the potential approval of the Tesla FSD suite in the country. Tesla, which has received various approvals in Europe over the past two months, has not provided a comment.
Teslas operating on FSD do travel over the speed limit, depending on the Speed Profile that is chosen. Drivers have the ability to disengage FSD at any point; Tesla specifically states that those supervising the suite are responsible for its actions.
Let’s cut to the chase: humans operating any vehicle speed almost daily in the United States. Realistically, speed limits in the U.S. are more frequently treated as speed minimums. However, other countries are different, and driving behaviors are less aggressive.
TRV believes that “allowing automated systems to systematically exceed legal speed limits…risks undermining both the legal framework and the expected safety benefits of vehicle automation,” the report stated. It’s surprising that Tesla has not received this claim from other countries previously.
This could be a good argument to bring Max Speed back, the setting that previously allowed the driver to choose the absolute fastest the car would travel.
This would still put the responsibility of supervision in the hands of the driver. It would allow the driver to choose whether the car would travel over the speed limit or not, acknowledging that they set the speed, and if they get pulled over, there would be no ability to argue it.
However, it does not seem as if this is something Tesla will do, especially considering many U.S. drivers have requested the feature in an effort to eliminate speeding or at least tone it down. The company has not shown any interest in bringing it back.
Tesla has approvals for FSD in Europe in Estonia, Lithuania, Denmark, the Netherlands, and Belgium.
Tesla is going to let you guide Full Self-Driving with Grok in 3 months, CEO Elon Musk confirmed on X.
The response from Musk, which revealed Tesla plans to allow drivers to effectively control the car and its navigation more explicitly using Grok, puts the feature for about September.
A Tesla owner said that Full Self-Driving is great, but owners should be able to “converse with Grok like we can with an Uber driver.” She then used examples like, “Grok, turn right here,” and “Drop us off right here, we’ll walk due to traffic,” and finally,” Drop at entrance first, then park far away.”
Coincidentally, the final piece of dialogue would also mean features like Banish are potentially on the way soon.
This functionality will be there in about 3 months or so
— Elon Musk (@elonmusk) June 18, 2026
Banish is also referred to as “Reverse Summon,” and would enable the car to self-park while dropping occupants off at their destination.
This would be a great way to improve the overall experience while supervising FSD. Navigation is already a major painpoint that many owners complain about. Manual overrides when a maneuver is requested or canceled (like using the turn signal stalk to override a navigation route), do not always work.
The feature could be especially useful in street parking scenarios in a city, where spots are sometimes tough to come by. Many of us who grab dinner in a more populated area will park a street or two over from wherever we’re going, because sometimes you know that’s the best you will get. If a driver using FSD could say, “Hey Grok, turn right here on Queen St. and park in that open spot on the right,” it could save a lot of confusion FSD might have on its own.
Musk teased that a similar feature was “coming” back in February:
Tesla Full Self-Driving set to get an awesome new feature, Elon Musk says
It is certainly surprising that Tesla is doing it at this point. The company’s more recent moves have been more evident of taking control and inputs away from humans and putting them in the AI’s hands more frequently. The biggest example of this was taking away Max Speed in AI4 cars, giving us Speed Profiles, and not having any input on the fastest speed the car will travel.
Of course, giving navigation preferences to Grok is availble already in Teslas, but not at the drop of a hat. Instead, you can suggest a certain route at the beginning of your drive.
Here’s an example of that from December:
🚨🏈 I am taking my parents and Fiancee to the @Ravens game next weekend and asked @Grok to help me route my @Tesla through a specific neighborhood to reach the correct Lot we will park in.
This is a great example of the new @grok nav integration with the Tesla Holiday Update: pic.twitter.com/rPp4I7q8Yv
— TESLARATI (@Teslarati) December 13, 2025
Finally, the original post that Musk responded to mentioned a parking preference after dropping off the occupants, which describes the Banish feature that Tesla has teased for years.
We’re not sure if Musk was responding more to the ability to guide the car with Grok, or whether he also was including Banish in the three-month prediction timeframe.
A close-up image of a Cybercab engineering vehicle in Peabody, Massachusetts, reveals a compact triangular side repeater camera housing equipped with an integrated washer mechanism.
This seemingly small hardware addition could prove to be one of the most critical components for achieving reliable, unsupervised Full Self-Driving (FSD) — not just for the dedicated Robotaxi but potentially for existing AI4-equipped vehicles as well.
The washer system’s importance cannot be overstated in Tesla’s vision-only autonomy approach. Cameras are the sole sensory input for the neural networks powering FSD, constantly interpreting the environment for safe navigation. In real-world conditions, however, lenses quickly accumulate rain, snow, mud, dust, or road spray.
Many of us Tesla owners, especially those who deal with any sort of winter weather at all, know the all-too-common alert that pops up when cameras are obstructed:
Even brief obstructions can drop perception confidence, trigger safety disengagements, or force the vehicle to pull over, although these are relatively rare. Instead, most of the time, the camera will need a wipe from the owner next time they stop the car.
But unlike human drivers who can manually clear their view, a Robotaxi operating 24/7 without a steering wheel or mirrors must maintain pristine vision autonomously. The Cybercab’s side repeater washer delivers targeted cleaning bursts precisely where needed for merging, lane changes, and blind-spot monitoring — functions that demand uninterrupted visibility from the external cameras:
And this is how the side camera and washer look like on a Cybercab. This is from an Engineering vehicle in Peabody MA. pic.twitter.com/Re8VknpmLM
— Tobias Goebel (Unsupervised) (@tpgoebel) June 17, 2026
This hardware directly tackles a known pain point in current FSD deployments. Owners frequently report camera-related alerts during inclement weather, which is understandable, but needs to be solved for a true autonomous experience.
For a production Robotaxi fleet aiming for high utilization and minimal downtime, robust washer systems represent a foundational reliability upgrade; essentially, they’re a must-have. Early sightings suggest the design may extend to rear cameras as well, creating a comprehensive cleaning architecture that keeps the entire vision suite operational in harsh environments.
Without it, even the most advanced neural nets struggle when their “eyes” are compromised.
What Does This Mean for AI4 Cars?
This Cybercab detail raises timely questions for AI4 cars already on the road. While Hardware 4 delivers superior compute and camera resolution compared to earlier versions, production models typically lack dedicated side and rear washers. Tesla has included them on Model Y robotaxis that it is using in the fleet:
Tesla Robotaxi has a highly-requested hardware feature not available on typical Model Ys
As Tesla refines unsupervised FSD for broader release, the gap in environmental resilience becomes evident. Software improvements can help mitigate issues, but they cannot fully replace physical cleaning in heavy rain or muddy conditions. Analysts and owners increasingly speculate that AI4 vehicles may eventually require similar washer retrofits — or a future AI4.5 variant — to match the Cybercab’s all-weather readiness and support the same level of autonomy.
As testing progresses, the Cybercab’s washer mechanism highlights Tesla’s pragmatic focus on real-world robustness. It may well become the hardware piece that determines how quickly and reliably FSD scales from prototypes to everyday vehicles.
Tesla faces Full Self-Driving pushback in EU over ‘speeding’
Tesla teases greater Grok FSD integration and ‘Banish’ feature ‘in about 3 months’
