News
SpaceX Super Heavy tank prototype survives crush testing
A tank prototype similar to SpaceX’s next-generation Super Heavy rocket booster has survived a series of tests that repeatedly attempted to destroy it.
Known as Booster 7.1 or B7.1, the tank is the latest in a long line of ‘test tanks’ designed to verify the performance of Starship and Super Heavy and qualify new designs and manufacturing techniques without risking an entire upper stage or booster. In general, that means that test tanks are as minimal as possible and much shorter than either Starship stage, but they’re also assembled out of nine-meter-wide (30 ft) steel barrels and domes almost identical to the sections that make up Starship and Super Heavy.
For most of the duration of SpaceX’s steel Starship program, ‘test tank’ work has followed a fairly consistent and linear development path, where tanks were used to verify design changes before those changes were implemented on more expensive prototypes. B7.1 firmly ignored that norm.
While it’s not an exact match, the tank – built out of two stacked rings and dome sections and measuring about 11 meters (~36 ft) tall – has a Super Heavy thrust structure (where Raptor engines would attach) and external stiffeners known as stringers that are (mostly) exclusive to Starship boosters.
As its name suggests, B7.1 shares many of the significant design changes that SpaceX had already implemented on Super Heavy Booster 7 (B7). The company began testing B7 months before B7.1, subjecting the full-size booster to multiple cryogenic proof tests and Raptor thrust simulation testing to qualify its new thrust ‘puck’ and several other structural changes. SpaceX began testing B7.1 in late June, shortly before Super Heavy Booster 7 was damaged by an unplanned explosion that halted its first Raptor engine test campaign. B7.1 testing then restarted in mid-July and was completed by the end of the month.
For unknown reasons, SpaceX’s decision to build and test Booster 7 before B7.1 meant that any significant issues discovered during subsequent B7.1 testing could disqualify the booster for flight testing, potentially wasting the months of work and tens of millions of dollars already invested in the prototype. Ultimately, though, B7.1 appeared to sail through multiple cryogenic proofs and crush tests without any catastrophic issues. Only on the last crush test did any part of the test tank finally give way, and the resulting damage was minor.
B7.1’s testing made use of a relatively new two-piece stand. The tank was first installed on a sturdy base using clamps similar to those on the Starbase orbital launch site’s (OLS) launch mount. Then, a hat-like structure was placed on top of the tank, resting on the surface that a Starship upper stage would sit on during launch. Massive ropes were finally dropped down to attach to hydraulic cylinders on the base. Once B7.1 was loaded with benign cryogenic liquid nitrogen (LN2), replicating most of the thermal and mechanical stresses of real oxygen/methane propellant, the hydraulic cylinders retracted, pulling the cap down to evenly exert massive crushing forces down the vertical axis of the test tank. Simultaneously, additional rams installed underneath B7.1 may have simulated the thrust of 13 central Raptor engines.
It’s unclear what exactly SpaceX was testing. The goal of the test could have been as simple as verifying that Super Heavy Booster 7 can withstand the weight of a fully-fueled Starship (~1350 tons / ~3M lb) sitting on top of it. It could have also been used to simulate an entire orbital launch from Super Heavy’s perspective, replicating many of the forces Starship boosters will experience between liftoff and landing. Given that Booster 7’s upgraded thrust puck had already made it through stress testing, B7.1 didn’t have much to add there, but it may have been useful for estimating the compressive strength of the current Super Heavy booster design.
Regardless of what B7.1 did or didn’t prove, it did so with very little drama. After four long days of testing, at least two of which involved attempting to crush the tank, the only truly noteworthy visual event was evidence of a slight buckle near the top of the tank during its last crush test. A few days later, with the test stand ‘cap’ removed, B7.1 survived one final test in which SpaceX likely attempted to pressurize the tank until it burst. Instead, the tank didn’t so much as develop a leak, reiterating – contrary to their occasional tin-can-like appearances – just how sturdy Starship and Super Heavy really are.
With nothing more to give, SpaceX will likely scrap B7.1. Meanwhile, Super Heavy Booster 7 remains stuck inside one of SpaceX’s Starbase assembly bays after being forced back to the factory by unintentionally explosive testing. The fate of that booster is unclear but SpaceX has removed all or most of its 33 Raptor engines over the last few weeks while simultaneously expediting work on Booster 8, which may ultimately take B7’s place.
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’
