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 has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.
Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.
Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
