News
SpaceX shuffles Starships, gears up for more Super Heavy static fires
SpaceX is busy preparing for the orbital launch debut its next-generation Starship rocket, but the company’s South Texas rocket factory is also working around the clock to prepare several more sets of ships and boosters for the flight testing that will follow.
That was more obvious than usual on November 8th, when SpaceX made moves to prepare both of its finished Starships for new phases of testing. SpaceX kicked off the busy day by removing Starship S25 – a newer prototype that arrived at the launch site just three weeks prior – a stand dedicated to proof testing ships. Three hours later, after spending three of the last four weeks sitting on top of Super Heavy Booster 7, Starship S24 was ‘destacked’ (lifted off of B7 and lowered onto a stand on the ground) in the early afternoon.
Booster 7, Ship 24, and Ship 25 have all been busy since mid-October. SpaceX stacked Booster 7 and Ship 24 for the first time on October 11th and then attempted to test the fully-stacked rocket on October 13th. By some accounts, although almost nothing was visible to the public, the first full-stack test may have gone poorly, potentially even endangering pad technicians that approached the rocket to troubleshoot. On October 16th, SpaceX fully destacked Ship 24, and CEO Elon Musk noted that the company was “proceeding very carefully” to avoid an explosion that could set “Starship progress back by ~6 months.”
But if there was a major issue on October 13th, SpaceX didn’t show it, and Ship 24 was reinstalled atop Booster 7 on October 20th without any obvious maintenance or repairs. SpaceX then kicked off an unusual series of tests on October 24th, during which it only filled the liquid oxygen (LOx) or liquid methane (LCH4) tanks of Super Heavy B7, Ship 24, or both vehicles at once. A rare NASA briefing on October 31st later called them “single-species prop[ellant]” tests – a kind of extra-cautious testing that had never been seen before at Starbase. A few days prior, a member of NASA’s Aerospace Safety Advisory Panel (ASAP) noted that an accidental explosion that damaged Booster 7 in July had caused SpaceX to “increase [the rigor of its] systems engineering and risk management,” explaining the sudden influx of unusually conservative testing.
By the time Ship 24 was destacked from Booster 7 on November 8th, SpaceX had completed seven single-species tests, four of which involved loading LOx or LCH4 into both stages and three of which only tested Super Heavy. Booster 7 and Ship 24’s tanks were fully filled and LCH4 and LOx were never simultaneously loaded on either stage.
NASA’s October 31st briefing reported that SpaceX had plans to destack Ship 24 before conducting additional static fire testing with Booster 7. While B7 completed 1, 3, and 7-engine static fires in August and September, those tests were nowhere close to the full 33-engine static fire required to properly qualify the most powerful rocket in history. According to NASASpaceflight.com managing editor Chris Bergin, SpaceX’s next goal is to fire up approximately half of Super Heavy B7’s Raptors.
Strangely, although Ship 24 was believed to have completed all of the standalone testing needed to clear it for flight, SpaceX installed the vehicle on a stand used for Starship static fire testing on November 9th, implying that more standalone testing may be required. For now, that shouldn’t pose a problem as long as SpaceX wraps up any additional Starship testing around the same time as Booster 7’s next static fire campaign wraps up, but it could delay full-stack launch readiness if it takes any longer.
Finally, after Ship 25 was removed from SpaceX’s other Starship test stand on November 8th, it was rolled back to Starbase’s Starship factory. Ship 25 first rolled to the launch site on October 19th and has since completed four visible tests. On October 28th, Ship 25 survived a pneumatic proof test that showed that its tanks were leak-free and capable of surviving flight pressures (roughly 6-8.5 bar or 90-125 psi). Three cryogenic proof tests followed on November 1st, 2nd, and 7th. The first cryoproof was likely just that – a test that pressurized Ship 25’s tanks and filled them with cryogenic liquid nitrogen (LN2) or a combination of liquid oxygen and LN2.
The next two tests likely took advantage of the customized test stand, which has been semi-permanently outfitted with a set of hydraulic rams that allow SpaceX to simulate the thrust of six Raptor engines while Starship’s structures are chilled to cryogenic temperatures and loaded with roughly 1000 tons (~2.2M lb) of cryogenic fluids. If a Starship can survive those stresses on the ground, the assumption is that it will likely survive similar stresses in flight.
Assuming that Ship 25’s first several proof tests were successful, which they appear to have been, SpaceX returned the prototype to its Starbase factory to install six Raptor engines and a series of shields and firewalls that will protect those engines from each other. Once fully outfitted, Ship 25 will return to the launch site for static fire testing and take Ship 24’s place on Suborbital Pad B. Ship 24 took approximately two months to go from its last cryoproof to its first static fire. But its testing got off to a relatively rocky start, so Ship 25 could be ready sooner.
SpaceX could begin the next phases of Booster 7 and Ship 24 testing as early as November 10th or November 13th.
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’
