News
Elon Musk talks upgrades after SpaceX Starship launches, explodes in midair
SpaceX has completed its fourth Starship test flight in as many months, offering the latest glimpse into the often frustrating reality of a highly iterative, hardware-rich rocket development program.
Right on schedule, SpaceX Starship prototype serial number 11 (SN11) lifted off from Boca Chica, Texas at exactly 8am CDT (UTC-5) – all but completely cloaked in a thick layer of fog. While unfortunate for any unofficial observers (and possibly SpaceX’s own desire to gather video footage of a test flight), SpaceX has experience launching rockets (namely Falcon 9) in thick fog thanks to its Vandenberg Air Force Base launch site on the California coast.
As such, fog theoretically poses no fundamental threat to rockets like Starship, but SN11 still took the opportunity to explore new and exciting failure modes shortly before touchdown. CEO Elon Musk himself didn’t take long to weigh in and has even offered some details and a schedule for upgrades planned for SpaceX’s next-generation launch vehicle – upgrades hoped to alleviate whatever issues led to Starship SN11’s premature demise.
First and foremost, due to the fog, the general public saw virtually nothing throughout the launch attempt. Remote streaming cameras set up near SpaceX’s launch facilities – now, excitingly, with the company’s own permission – did manage to catch some level of detail, providing the bare minimum level of insight needed to speculate on SN11’s failed landing attempt.
Per an official webcast and NASASpaceflight’s unofficial “Danger-Close Camera,” installed a few hundred feet from the launch site with SpaceX’s permission, Starship lifted off at exactly 8am and had a seemingly nominal ascent, reaching a familiar 10 km (6.2 mi) apogee around four minutes later. SN11 then arced over onto its belly and free-fell for ~100 seconds. Aside from a few intermittent fires burning on some of the rocket’s three Raptor engines, not an uncommon sight since SN8 first flew, nothing appeared particularly out of the ordinary.
At T+5:49, however, things rapidly went wrong. Still belly-down, Starship SN11 attempted to reignite all three of its Raptor engines to propulsively flip into a vertical landing position. After at least one seemingly successful reignition, SpaceX immediately lost onboard video and telemetry feeds. Based on NASASpaceflight’s pad-adjacent camera, a substantial explosion followed one or two seconds after that attempted ignition, ending Starship SN11’s test flight around 20 seconds earlier than any of its three late siblings.
Debris began to visibly hit the ground another 5-10 seconds after that explosion was first heard, all but guaranteeing that Starship SN11 exploded in midair. At this time, it’s impossible to know what exactly went wrong, but there are two clear possibilities. Starship SN11 could have failed to reignite two or even all three Raptor engines, triggering onboard flight termination system (FTS) explosives designed to prevent the rocket from straying beyond a safe zone of operations. More likely, Starship suffered a substantial failure during that reignition and flip attempt, triggering an almost immediate explosion that tore the rocket apart around half a kilometer (~1500 ft) above the pad and landing zone.
Shortly after, Musk said that Raptor “engine #2 had issues on ascent” that were notable but not enough to explain a violent midair failure and confirmed that whatever went wrong came “shortly after landing burn start.”
Musk offers Starship upgrade schedule, details
Having suffered a failure a bit less than six minutes after launch, Starship SN11 – the fourth three-engine, high-altitude prototype – was ironically the farthest from a successful landing before something went wrong: one step forward, two steps back. While unfortunate, SpaceX still got some amount of data and uncovered one or several new failure modes – arguably the two of the most important primary goals of any developmental flight test program.
Further, Musk revealed that SpaceX intends to complete and roll Starship SN15 to the launch pad just “a few days” from now – certainly earlier than expected. While the SpaceX CEO didn’t go much into detail, he reaffirmed that SN15 would bring substantial upgrades, stating that “it has hundreds of design improvements across structures, avionics/software, & engine[s].”
Musk also touched on SpaceX’s near-term plans after SN15’s upgrade path, confirming that Starship prototypes from SN20 onwards will be “orbit-capable” with even more improvements. That seemingly delineates three clear ‘blocks’ of Starship prototypes, beginning with SN8 through SN11, proceeding with SN15 through SN19, and (nominally) gearing up for true orbital-class test flights with prototype SN20 and its successors. All told, SN11’s midair demise appears likely to be just a small blip in front of a jam-packed, well-structured series of Starship upgrades and flight tests just over the horizon.
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’
