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.
Elon Musk
Tesla CEO Elon Musk sends rivals dire warning about Full Self-Driving
Tesla CEO Elon Musk revealed today on the social media platform X that legacy automakers, such as Ford, General Motors, and Stellantis, do not want to license the company’s Full Self-Driving suite, at least not without a long list of their own terms.
“I’ve tried to warn them and even offered to license Tesla FSD, but they don’t want it! Crazy,” Musk said on X. “When legacy auto does occasionally reach out, they tepidly discuss implementing FSD for a tiny program in 5 years with unworkable requirements for Tesla, so pointless.”
I’ve tried to warn them and even offered to license Tesla FSD, but they don’t want it! Crazy …
When legacy auto does occasionally reach out, they tepidly discuss implementing FSD for a tiny program in 5 years with unworkable requirements for Tesla, so pointless. 🤷♂️
🦕 🦕
— Elon Musk (@elonmusk) November 24, 2025
Musk made the remark in response to a note we wrote about earlier today from Melius Research, in which analyst Rob Wertheimer said, “Our point is not that Tesla is at risk, it’s that everybody else is,” in terms of autonomy and self-driving development.
Wertheimer believes there are hundreds of billions of dollars in value headed toward Tesla’s way because of its prowess with FSD.
A few years ago, Musk first remarked that Tesla was in early talks with one legacy automaker regarding licensing Full Self-Driving for its vehicles. Tesla never confirmed which company it was, but given Musk’s ongoing talks with Ford CEO Jim Farley at the time, it seemed the Detroit-based automaker was the likely suspect.
Tesla’s Elon Musk reiterates FSD licensing offer for other automakers
Ford has been perhaps the most aggressive legacy automaker in terms of its EV efforts, but it recently scaled back its electric offensive due to profitability issues and weak demand. It simply was not making enough vehicles, nor selling the volume needed to turn a profit.
Musk truly believes that many of the companies that turn their backs on FSD now will suffer in the future, especially considering the increased chance it could be a parallel to what has happened with EV efforts for many of these companies.
Unfortunately, they got started too late and are now playing catch-up with Tesla, XPeng, BYD, and the other dominating forces in EVs across the globe.
News
Tesla backtracks on strange Nav feature after numerous complaints
Tesla is backtracking on a strange adjustment it made to its in-car Navigation feature after numerous complaints from owners convinced the company to make a change.
Tesla’s in-car Navigation is catered to its vehicles, as it routes Supercharging stops and preps your vehicle for charging with preconditioning. It is also very intuitive, and features other things like weather radar and a detailed map outlining points of interest.
However, a recent change to the Navigation by Tesla did not go unnoticed, and owners were really upset about it.
For trips that required multiple Supercharger stops, Tesla decided to implement a naming change, which did not show the city or state of each charging stop. Instead, it just showed the business where the Supercharger was located, giving many owners an unwelcome surprise.
However, Tesla’s Director of Supercharging, Max de Zegher, admitted the update was a “big mistake on our end,” and made a change that rolled out within 24 hours:
The naming change should have happened at once, instead of in 2 sequential steps. That was a big miss on our end. We do listen to the community and we do course-correct fast. The accelerated fix rolled out last night. The Tesla App is updated and most in-car touchscreens should…
— Max (@MdeZegher) November 20, 2025
The lack of a name for the city where a Supercharging stop would be made caused some confusion for owners in the short term. Some drivers argued that it was more difficult to make stops at some familiar locations that were special to them. Others were not too keen on not knowing where they were going to be along their trip.
Tesla was quick to scramble to resolve this issue, and it did a great job of rolling it out in an expedited manner, as de Zegher said that most in-car touch screens would notice the fix within one day of the change being rolled out.
Additionally, there will be even more improvements in December, as Tesla plans to show the common name/amenity below the site name as well, which will give people a better idea of what to expect when they arrive at a Supercharger.
News
Dutch regulator RDW confirms Tesla FSD February 2026 target
The regulator emphasized that safety, not public pressure, will decide whether FSD receives authorization for use in Europe.
The Dutch vehicle authority RDW responded to Tesla’s recent updates about its efforts to bring Full Self-Driving (Supervised) in Europe, confirming that February 2026 remains the target month for Tesla to demonstrate regulatory compliance.
While acknowledging the tentative schedule with Tesla, the regulator emphasized that safety, not public pressure, will decide whether FSD receives authorization for use in Europe.
RDW confirms 2026 target, warns Feb 2026 timeline is not guaranteed
In its response, which was posted on its official website, the RDW clarified that it does not disclose details about ongoing manufacturer applications due to competitive sensitivity. However, the agency confirmed that both parties have agreed on a February 2026 window during which Tesla is expected to show that FSD (Supervised) can meet required safety and compliance standards. Whether Tesla can satisfy those conditions within the timeline “remains to be seen,” RDW added.
RDW also directly addressed Tesla’s social media request encouraging drivers to contact the regulator to express support. While thanking those who already reached out, RDW asked the public to stop contacting them, noting these messages burden customer-service resources and have no influence on the approval process.
“In the message on X, Tesla calls on Tesla drivers to thank the RDW and to express their enthusiasm about this planning to us by contacting us. We thank everyone who has already done so, and would like to ask everyone not to contact us about this. It takes up unnecessary time for our customer service. Moreover, this will have no influence on whether or not the planning is met,” the RDW wrote.
The RDW shares insights on EU approval requirements
The RDW further outlined how new technology enters the European market when no existing legislation directly covers it. Under EU Regulation 2018/858, a manufacturer may seek an exemption for unregulated features such as advanced driver assistance systems. The process requires a Member State, in this case the Netherlands, to submit a formal request to the European Commission on the manufacturer’s behalf.
Approval then moves to a committee vote. A majority in favor would grant EU-wide authorization, allowing the technology across all Member States. If the vote fails, the exemption is valid only within the Netherlands, and individual countries must decide whether to accept it independently.
Before any exemption request can be filed, Tesla must complete a comprehensive type-approval process with the RDW, including controlled on-road testing. Provided that FSD Supervised passes these regulatory evaluations, the exemption could be submitted for broader EU consideration.