News
SpaceX Starship booster heads to launch pad for the fifth time
For the fifth time in five months, SpaceX has transported its most advanced Starship booster prototype from the Starbase factory to the launch pad, setting the stage for another round of testing.
Super Heavy Booster 7 (B7) returned to the factory for the fourth time on August 12th after becoming the first prototype of any kind to perform a static fire engine test while installed on SpaceX’s orbital Starship launch mount. In the days prior, the booster completed two back-to-back static fire tests with one of the 20 Raptor engines installed on the rocket, both of which apparently gave SpaceX enough confidence to prepare for the next phase of testing.
That relatively cautious progress only came after SpaceX attempted to test all 33 of the prototype’s Raptors at once during its first engine test. Whether it was the fault of overzealous managers or executives or a genuine oversight is not clear, but the combined behavior of Super Heavy and the orbital launch pad was not properly characterized before testing began. As a result, the cloud of flammable gas the rocket released during its attempted 33-engine ‘spin-prime’ test found an ignition source and violently exploded on July 11th, causing damage throughout Booster 7’s aft engine section that required several weeks of repairs between July 15th and August 6th.
When the Super Heavy rolled to the pad for the fourth time on August 6th, it was missing all 13 center Raptors, leaving only the outer ring of 20 Raptor Boost engines partially installed for the tests that followed. Thankfully, things went much better on the second try and Booster 7 completed two spin-prime tests with a single Raptor engine, followed by two successful static fire tests on August 9th and 11th. The latter test was the longest Starbase static fire ever (by a factor of ~3) and lasted about 20 seconds, allowing SpaceX to test Booster 7’s autogenous pressurization. That system pressurizes Super Heavy’s tanks by turning small quantities of cryogenic liquid propellant into gas, ensuring that its tanks remain stable as they’re rapidly drained of thousands of tons of propellant.
On August 12th, Booster 7 returned to the factory, where workers installed the rocket’s 13 center engines for the second time. Booster 7 headed back to the orbital launch site (OLS) on August 23rd and the pad’s robotic launch tower used a pair of arms to lift the rocket off its transport stand and place it on the launch mount by the end of the day.
In addition to readying Booster 7 for its next phase of static fire testing, teams of SpaceX workers took advantage of the unplanned lull in testing to modify the orbital launch mount. It’s impossible to know what exactly was done without official confirmation, but it’s likely that SpaceX was attempting to quickly fix the shortcoming(s) that allowed the July 11th explosion to happen. Without a fix, it’s unlikely that SpaceX would want to proceed with plans to ignite large numbers of Raptor engines simultaneously – a series of tests that must be completed before Starship can safely attempt its first orbital launch.
It’s unclear what exactly that fix entails, but it could involve a system to constantly flood the engine section with fire-stopping nitrogen gas or potentially take the shape of a system of vents that will connect to every Raptor engine and remove methane gas before it can turn into flammable clouds.
It’s possible that Booster 7 has returned to the launch pad solely for fit checks or some other basic proof-of-concept testing. It’s also possible that the returns signifies that SpaceX is confident in its quick launch mount fix and ready to restart static fire testing.
As Booster 7 prepares for that next phase of testing, SpaceX may also be ready to restart static fire testing with Starship S24, which paused shortly before Super Heavy returned to the factory. SpaceX appears to be modifying the suborbital launch mount and test stand Ship 24 is installed on, which could explain the lack of ship testing since August 11th. SpaceX has 12-hour test windows tentatively scheduled on August 24th and 25th, either of which could be used to test either or both prototypes.
If all goes to plan, Ship 24 and Booster 7 will eventually complete all the qualification testing SpaceX can throw at them and be ready to support Starship’s first orbital launch attempt sometime before the end of 2022.
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’
