News
SpaceX making good progress towards Super Heavy static fire campaign
SpaceX appears to be making great progress towards the start of its first full Super Heavy static fire campaign, building upon extensive Starship testing and a single booster static fire completed in July 2021.
On May 14th, upgraded Super Heavy booster B7 was moved back to SpaceX’s South Texas Starbase Starship factory after completing a successful round of tests and smoothing out an otherwise rocky start to its life. It was not the booster’s first time on that journey: after first leaving the Starbase ‘nest’ on March 31st, Booster 7 suffered significant internal damage during a structural stress test on April 14th and was forced to return to the factory for repairs. Impressively, despite the cramped environment and extremely limited access to the interior of the Super Heavy’s primary and secondary propellant tanks, SpaceX engineers and technicians somehow completed those repairs and Booster 7 sailed through a new round of ‘cryoproof’ testing on May 9th and 11th.
In the ~20 days since its second return, SpaceX teams have been hard at work preparing Super Heavy B7 for its next major challenges – the results of which could determine whether the massive rocket helps launch a Starship into space later this year.
That goal, same as it has been for half a year, is to qualify the first Super Heavy booster for flight. To do so, SpaceX must – at long last – static fire a Super Heavy with all necessary Raptor engines installed. For Booster 7 and its near-term successors, that means 33 new “Raptor 2” engines capable of generating a total of ~7600 metric tons (~16.7M lbf) of thrust.
That’s exactly what SpaceX workers have been focused on doing since Booster 7’s second return to a Starbase assembly bay. Bit by bit, they have spent every day since installing Raptor 2 engines one at a time. Unfortunately, due to the Super Heavy’s relocation inside a brand new assembly building known as the Megabay, High Bay 2, or Wide Bay, the half-dozen or so unaffiliated photographers who have come to regularly photograph Starbase have yet to find an angle that shows the state of that engine installation progress.
Two weeks later, it’s clear that SpaceX is taking its time, which likely also implies that the company is simultaneously encasing Booster 7’s Raptors and engine section in shrouds that will protect them during static fire testing; as well as during launch, reentry, and landing if B7 makes it that far. That’s not guaranteed, however, and it could also simply be that installing 33 engines on the first attempt at installing any Raptor 2s on any rocket has proven much harder than expected.
On June 1st, CEO Elon Musk appeared to confirm that engines are still being installed on Super Heavy B7, but he also verified that “all Raptor 2 engines needed for [the] first orbital flight are complete.” That could include Starship S24, which needs three sea-level Raptor 2s and three vacuum-optimized Raptor 2s, but it’s still great news even if he only means it for Booster 7. SpaceX has been spotted delivering at least a handful of new Raptor 2 engines a week for the last month or two, which means that all 33 engines may already be onsite at Starbase. If some are still undergoing proof testing at SpaceX’s McGregor, Texas facilities, it could be a few more weeks before all necessary engines are onsite, but that milestone is likely close at hand if it hasn’t already been reached.
For Super Heavy Booster 4, which was inexplicably never static-fired, installation of all 29 of its Raptor 1 engines took just a few days, but the installation of a heat shield around those engines took at least a few weeks. On June 1st, SpaceX also began installing grid fins on Super Heavy B7, further indicating the company’s growing confidence in the booster.
Outside of booster outfitting, SpaceX has also been aggressively refilling the Starbase orbital launch site’s (OLS) massive tank farm, which is capable of storing, subcooling, and distributing thousands of tons of liquid oxygen (LOx), liquid methane (LCH4), liquid nitrogen (LN2), and a variety of gases. For a full wet dress rehearsal (WDR), which has also never been done with Super Heavy, SpaceX would need to fill the booster with around 3400 tons (7.5M lb) of propellant. Out of an abundance of caution, Super Heavy B7 will likely have far less propellant aboard during almost all of its static fire tests, but a full static fire with a full load of propellant – simulating most prelaunch conditions – will likely be one of the last main goals of any static fire campaign. At full thrust, 33 Raptor 2 engines will likely burn around 25 tons (~55,000 lb) of propellant per second, so a huge amount of propellant will be needed regardless.
In the same series of June 1st tweets, Musk also confirmed that SpaceX intends to proceed cautiously into its first true Super Heavy static fire campaign, testing engines “just one at a time at first.” Musk probably isn’t being literal, as a campaign in which Booster 7 tested every one of its 33 Raptors individually could easily take weeks, so it’s likely safe to interpret his words to mean that SpaceX is not going to leap straight from the first limited test of one or a few engines to all 13 center engines, all 20 outer ‘boost’ engines, or all 33 engines at once.
Almost three weeks into the process of engine and heat shield installation, Booster 7 could potentially be ready to return to the orbital launch site any day now, though there’s probably an equal chance that it’s still a few weeks away. Nonetheless, SpaceX is on the cusp of kicking off one of the most exciting and important test campaigns in the history of Starship.
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’
