News
SpaceX preps Starship, Super Heavy for another week of Raptor testing
SpaceX continues to work around the clock to prepare its latest Starship and Super Heavy booster prototypes for another week of testing – likely focused on firing up the Raptor engines installed on each vehicle.
Known as Booster 7 and Ship 24, SpaceX has been slowly testing both prototypes for approximately four months, beginning in April and May, respectively. Only in early August did the company cautiously begin attempting to ignite their Raptor engines as part of a process known as static fire testing – by far the most difficult and important part of qualifying both vehicles for flight.
Thanks to progress made in 2021, SpaceX already has significant experience testing an earlier orbital-class Starship prototype on the ground, but the process of testing Ship 24 is still fresh and unfamiliar for a number of reasons. For Booster 7, the challenges are even greater.
On top of major design changes made to Starship and Super Heavy over the last year as SpaceX continues to refine the rocket, the company also developed a substantially different version of its Raptor engine. Compared to Raptor V1, Raptor V2 almost looks like a new engine and can produce around 25% more thrust (230 tons versus 185 tons). SpaceX has also tweaked how the engine operates, particularly around startup and shutdown, further weakening the value of past experience testing Raptor V1 and V1.5 engines on Ship 20 and Boosters 3 and 4.
In other words, with Ship 24 and Booster 7 engine testing, it’s possible that SpaceX is effectively starting from scratch. Many aspects of testing – propellant conditioning, thermal characteristics, tanking, detanking, certain test stands – are likely mostly unchanged, but almost every aspect of a rocket is affected by its engines.
Before SpaceX began testing Raptor V2 engines on Starship and booster prototypes, it wasn’t clear if the changes between V1.5 and V2 would invalidate a lot of prior testing. After the start of Booster 7 and Ship 24 static fire testing, it’s now clear that a lot of that earlier work has to be redone. It’s also clear that despite some of the simplifications in Raptor V2’s design, operating the engine on Starship and Super Heavy is much harder get get right.
Since mid-July, SpaceX has completed around 15-20 ‘spin-prime’ tests between Ship 24 and Booster 7 – more of that kind of test than any other prototype in the history of Starbase has performed. Spin-prime tests flow high-pressure gas through Raptor’s pumps to spin them up without igniting anything. It’s unclear why so many of those tests are being done, what SpaceX is gaining from it, or why the company appears to have completely stopped conducting preburner tests (a more life-like spin-prime with partial combustion).
Regardless, eight weeks after the start of engine testing, Booster 7 has only performed three static fires (two with one engine, one with a max of three or four engines), and Ship 24 has only completed one static fire with two engines. Before either vehicle can be considered ready for flight, a day that could easily never come, each will likely need to conduct multiple successful static fires with all of their Raptor engines (6 on S24 and 33 on B7).
If the pace of Booster 7 testing doesn’t change, the vehicle could be months away from a full 33-engine static fire attempt – perhaps the single most important and uncertain test standing between SpaceX and Starship’s first orbital launch attempt. Ship 24’s path to flight readiness should be simpler, but it appears to be struggling almost as much.
According to CEO Elon Musk, “an intense effort is underway” to ensure that Super Heavy B7’s Raptor engines are well contained during anomalies, so that one engine violently failing won’t damage or destroy the booster, other engines, or the launch pad. That could certainly complicate the process of testing Booster 7, and it’s likely that SpaceX is taking some of the same actions to protect Ship 24.
In early September, after a partially successful Booster 7 static fire (its first multi-engine test) and numerous additional Ship 24 tests that failed to achieve ignition, SpaceX replaced engines on both vehicles. Booster 7 had one of 13 Raptor Center engines swapped out, while Ship 24 had one of its three Raptor Vacuum engines replaced.
On September 5th, SpaceX distributed a safety alert to Boca Chica’s few remaining residents, confirming that it wants to restart testing as early as Tuesday, September 6th. Especially as of late, that alert guarantees nothing, but it does at least open the door for SpaceX if Ship 24, Booster 7, and the positions of the stars happen to be in the right mood between 8am and 8pm CDT. Additional opportunities are available on September 7th, 8th, 9th, and 12th.
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’
