News
SpaceX just blew up a Starship tank on purpose and Elon Musk says the results are in
Before dawn on January 10th, SpaceX technicians and engineers intentionally blew up a miniature Starship tank in order to test recently-upgraded manufacturing and assembly methods, likely to be used to build the first Starships bound for flight tests and orbit.
SpaceX CEO Elon Musk quickly weighed in on Twitter later the same day, revealing some crucial details about the Starship tank test and effectively confirming that it was a success. While somewhat unintuitive, this is the second time SpaceX has intentionally destroyed largely completed Starship hardware in order to determine the limits of the company’s current methods of production and assembly.
Most notably, on November 20th, SpaceX is believed to have intentionally overpressurized the Starship Mk1 prototype in a very similar – albeit larger-scale – test, destroying the vehicle and sending its top tank dome flying hundreds of feet into the air. It’s generally believed that SpaceX (or perhaps even just Musk) decided that Starship Mk1 was not fit to fly, leading the company to switch gears and deem the prototype a “manufacturing pathfinder” rather than the first Starship to fly – which Musk had explicitly stated just a few months prior.
Bopper (Baby StarPopper) this morning after the overpressure event at SpaceX Boca Chica. ??@NASASpaceflight https://t.co/nCG7E9XtKM pic.twitter.com/PRTDQvvlRh— Mary (@BocaChicaGal) January 10, 2020
Dome to barrel weld made it to 7.1 bar, which is pretty good as ~6 bar is needed for orbital flight. With more precise parts & better welding conditions, we should reach ~8.5 bar, which is the 1.4 factor of safety needed for crewed flight.— Buff Mage (@elonmusk) January 10, 2020
Instead, Starship Mk1 suffered irreparable damage during its pressurization test and was rapidly scrapped in the weeks following, although several segments were thankfully salvaged – perhaps for use on future prototypes. Along those lines, it can arguably be said that the results from the mini Starship tank’s Jan. 10 pop test have paved the way for SpaceX to build the first truly flightworthy Starship prototypes – potentially all the way up to the first spaceworthy vehicles.
Hours after the test, Musk revealed that the Starship test tank failed almost exactly where and how SpaceX expected it would, bursting when the weld joining the upper dome and tank wall failed. Critically, the tank reached a maximum sustained pressure of 7.1 bar (103 psi), some 18% over the operating pressure (6 bar/87 psi) Musk says Starship prototypes will need to be declared fully capable of orbital test flights. In other words, given the tank’s size, it survived an incredible ~20,000 metric tons (45 million lbf) of force spread out over its surface area, equivalent to about 20% the weight of an entire US Navy aircraft carrier.
Musk also revealed that SpaceX will require Starships to survive a minimum of 140% of that operating pressure before the company will allow the spacecraft to launch humans.
Some have less than generously taken to smugly noting that several modern spaceflight and engineering standards require that launch vehicle tankage be rated to survive no less than 125% of their operating pressure, while this test tank would be rated for less than 118% under identical conditions. However, this ignores several significant points of interest. First and foremost, the Starship test tank intentionally destroyed on January 10th was assembled from almost nothing – going from first weld to a completed pressurization test – in less than three weeks (20 days).
Second, all visible welding and assembly work was performed outside in the South Texas elements with only a minor degree of protection from the coastal winds and environment. Although some obvious tweaks were made to the specific methods used to assembly the prototype tank, it also appears that most of the welding was done by hand. For the most part, in other words, the methods used to build this improved test article were largely unchanged compared to Starship Mk1, which is believed to have failed around 3-5 bar (40-75 psi).
Additionally, it appears that almost all aspects of this test tank have smaller structural margins, meaning that the tank walls and domes are likely using steel stock that is substantially thinner than what was used on Starship Mk1. Nevertheless, thanks to the addition of continuous (single-weld) steel rings, a tweaked dome layout, and slightly refined welding, this test tank has performed anywhere from 20% to 200+% better than Starship Mk1 – again, all while coming together from scratch in a period of less than three weeks.
As Musk notes, with relatively minor improvements to welding conditions and the manufacturing precision of Starship rings and domes, SpaceX can likely ensure that Starships (and thus Super Heavy boosters) will be able to survive pressures greater than 8.5 bar (125 psi), thus guaranteeing a safety margin of at least 40%. Even a minor improvement of ~6% would give vehicles a safety margin of 125%, enough – in the eyes of engineering standards committees – to reasonably certify Starships for orbital test flights.
All things considered, it’s safe to assume that SpaceX is going to begin building and assembling Starship SN01 (formerly Mk3) hardware almost immediately. Given that this test tank took just 20 days to assemble, it’s safe to say that the upgraded prototype’s tank section could be completed in just a handful of weeks. Stay tuned for progress reports.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Tesla Full Self-Driving v14.3.3 driver monitoring was reportedly scaled back in recent releases, but a new version that was released in the early hours of June 3 aimed to do a better job of keeping those in control of their cars honest, according to release notes.
The release notes for FSD v14.3.3, via Software Version 2026.14.6.7 added:
“Improved driver monitoring system sensitivity with better eye gaze tracking, eye wear handling, and higher accuracy in variable lighting conditions.”
However, Tesla said this was already enabled in the first rollout of FSD v14.3.3 in late May. We tested it anyway, especially as the Standard Speed Profile seemed less-than-worried about what you were doing during operation.
I decided to try out the Hurry and Mad Max Speed Profiles for this test, and it gave me results that I would have expected. Tesla has evidently ramped up driver monitoring based on the Speed Profile you are using to travel.
The more aggressive the Speed Profile, the more on the hook you will be for taking your attention away from the road. Our testing showed that Mad Max was less likely to allow you to do normal things like change music or adjust navigation without getting an on-screen warning or nag from the driver monitoring system.
Hurry Mode Results
On Hurry, the driver monitoring system on FSD v14.3.3, via Software Version 2026.14.6.7, was more restrictive than Standard but less restrictive than Mad Max. I found that I could scroll through music options for a considerable amount of time, more than 30 seconds:
Roughly :31 between first touching the center screen and getting the first nag
— TESLARATI (@Teslarati) June 3, 2026
Standard gave me about 80 seconds of phone scrolling with absolutely no nags or warnings in a previous test. It is worth noting that this was a previous branch of v14.3.3, but Standard is such a goodie-two-shoes on the road that it is my impression it would not change much.
Here’s an 80-second phone nag test on Tesla FSD v14.3.3.
No alerts, no nagging, no annoyance. https://t.co/1dxvTOw5Cn pic.twitter.com/vYViFpjfoK— TESLARATI (@Teslarati) May 29, 2026
Mad Max Results
I spent the majority of the drive on Mad Max to see how it truly reacted to the driver having their attention elsewhere. While I did do a short phone test, I am aiming to steer away from those and use the center screen. I think it is a valid criticism that the phone test is dangerous and, not to mention, illegal in Pennsylvania. Changing the navigation and music is a more reasonable, more responsible, and safer test.
With Mad Max being the fastest and most aggressive Speed Profile, I anticipated this being the quickest mode to give me an alert that I needed to look at the road. That was the case with music:
🎥 Testing Tesla FSD v14.3.3 (via 2026.14.6.7) nags on Mad Max https://t.co/qZALU2OujY pic.twitter.com/XddOJ0D47x
— TESLARATI (@Teslarati) June 3, 2026
As well as adjusting Navigation, when I received two nags:
🎥 Testing Tesla FSD v14.3.3 (via 2026.14.6.7) nag while adjusting navigation
Two nags here https://t.co/qZALU2OujY pic.twitter.com/xa3dtaDG1L— TESLARATI (@Teslarati) June 3, 2026
These nags were more than reasonable, and I think it’s probably good that Tesla is ramping up the driver monitoring. I do believe that it should be relatively strict across all of the Speed Profiles, especially with phone use. When using the center screen, the nag intervals should be based on the speed profile you are utilizing at the time.
These driver monitoring adjustments are a great thing to have while FSD is still under its “Supervised” moniker, but I expect Tesla to continue pushing the limits on what it will allow, especially considering CEO Elon Musk has hinted that phone use is capable with the more recent versions.
You can watch the full drive on YouTube below:
Tesla has responded to the skeptics of its Robotaxi program by launching a massive expansion of the unsupervised program in its initial rollout city of Austin.
The company’s geofence, the enabled area of operation for rides, now covers the entire Austin Metropolitan area, an incredible move just days after media headlines attempted to discredit the ride-hailing service.
Those who have access to the Tesla Robotaxi app on their smartphones can now request a ride in any portion of the Austin Metro area. The company confirmed this on the social media platform X:
Unsupervised Robotaxi now in the entire Austin Metro area https://t.co/eXNBdarvVS
— Tesla Robotaxi (@robotaxi) June 3, 2026
This is Tesla’s fifth expansion of the geofence, with the others occurring in July, early August, late August, and late October 2025. It has remained at that size since October 26, but Tesla has now more than doubled that size.
It is now covering the entire area, including suburbs like Pflugerville and Manor, as well as I-35 highways, Gigafactory Texas, and the Austin-Bergstrom Airport.
The move comes just days after various media outlets highlighted the small fleet size of Tesla’s Robotaxi fleet in Austin, something that is a reasonable criticism but an understandable move on the company’s part to prioritize safety.
Tesla has expanded its Robotaxi geofence many times, but its fleet has remained at a relatively conservative size as the company continues to push safety as its most crucial metric.
The latest expansion is a key indicator of Tesla’s comfort level to expand the ride-hailing service. The move shows Tesla is scaling unsupervised autonomy, as it demonstrates that the company’s Full Self-Driving system has reached sufficient reliability for a broader real-world deployment, which is something the company has worked on extensively.
It also shows Tesla is game for a competition with its rivals in the autonomous ride-hailing sector. Tesla has often matched or exceeded competitors like Waymo in coverage area, despite its smaller fleet. This step highlights Tesla’s iterative, data-driven progress toward a high-margin, app-based Robotaxi network.
It’s not the absolute largest area expansion ever, but achieving full unsupervised operations across a major metro is a key moment in the Robotaxi story. It shifts the program from limited pilot/testing toward a more mature commercial service, while gathering the miles needed for faster growth.
Tesla has improved Dashcam playback with an awesome new addition, as the company has launched a web-based version that is potentially easier to navigate and operate.
The tool is available at dashcam.tesla.com and will be enabled as your vehicle receives the 2026.20 Software Version. Clips that are captured by your Tesla will be available on the Online Dashcam Clip Viewer once the files on your car’s storage drive are encrypted.
Not a Tesla App first noticed the new feature, and states that once your Tesla updates to 2026.20, the car will automatically protect the clips with an encryption key that is uniquely tied to your owner account.
Tesla Launches New Web-Based Dashcam Viewer https://t.co/AlJKXYxujJ pic.twitter.com/4igicYpvkX
— Not a Tesla App (@NotATeslaApp) June 2, 2026
The web-based viewer should be easier to operate for most. All you will do is head over to dashcam.tesla.com and log in using your account credentials.
Ensure your vehicle is updated to 2026.20 in order for the web-based viewer tool to fetch your vehicle’s saved dashcam clips.
Currently, only a small percentage of owners are updated to this, so it may be a couple of weeks until a majority of owners in the fleet are able to access this feature.
Watching Dashcam clips on the Tesla smartphone app is quick and convenient, as they can also be easily downloaded and stored right on your smartphone.
However, the clips are sometimes tougher to navigate, and in order to get details like self-driving activation, speed, and turn signals, owners have to screen record the Tesla app and crop out the rest of the screen.
It could also be a massive storage saver as you’ll be able to download the Dashcam clips from the online viewer and save them to your laptop, desktop, a flash drive, or even an external hard drive. This will keep all your clips in one place.
Tesla Full Self-Driving v14.3.3 driver monitoring: We tested it
Tesla responds to Robotaxi skeptics with a massive move in Austin
