News
SpaceX Starship just aced another explosive tank test and Elon Musk has the results [video]
SpaceX has successfully repaired a leak in a Starship prototype, filled the giant tank with an ultra-cold liquid, and pressurized it until it (spectacularly) popped — and Elon Musk has the preliminary results.
Designed to determine the quality and capabilities of SpaceX’s current manufacturing and integration procedures, the company technically performed its first explosive Starship test back in November 2019, when it decided that the first full-scale prototype – Starship Mk1 – was not fit to fly. Instead of entering the final stages of assembly with a vehicle that SpaceX simply couldn’t be sure would survive the rigors of even a low-stress flight test, the massive vehicle’s tank section was installed at the company’s South Texas launch facilities and pressurized with liquid nitrogen until it burst.
Built almost entirely unprotected on the South Texas coast, Starship Mk1 simply wasn’t up to the standards needed for SpaceX to trust that the giant rocket would survive the stresses of flight. Much like Falcon 9, Starship and its Super Heavy booster will be structurally stable while their tanks are empty, but a great deal of additional (and absolutely critical) structural strength will be added by pressurizing those tanks with a combination of liquid and gaseous propellant. Achieving the required pressures, however, can be a major challenge and the purpose of test tanks like the one above is to prove that the company is up to the challenge. According to Elon Musk, after tonight’s test, SpaceX almost certainly is.
In all truthfulness, the real start of explosive Starship pressure testing actually happened all the way back in 2017 when SpaceX intentionally pressurized a vast 12m-diameter (40 ft) carbon composite tank until it popped. Back then, Starship was known as Big Falcon Rocket (BFR) and was designed to use carbon fiber composites for nearly all of its structure — propellant tanks included.
According to CEO Elon Musk, said carbon composite tank met SpaceX’s expectations (i.e. the necessary pressures for flight) and was pushed to 2.3 bar (33 psi) before it burst in a rather spectacular fashion, launching almost 100 m (300 ft) into the air. Around 2.5 years after that test, it’s believed that Starship Mk1 reached something like 3-5 bar before it popped, and Musk recently revealed that the new steel Starship and Super Heavy designs will require tanks pressures of at least 6 bar (90 psi) to survive the stresses of orbital flight.
Thankfully, although Starship Mk1 didn’t achieve those necessary pressures, the prototype was effectively a worst-case scenario for manufacturing and assembly, revealing the rather unsurprising reality that SpaceX needed to improve its uniquely sparse methods of production and assembly. Although the stainless steel SpaceX settled on for Starship is much more tolerant than aluminum or most other metals when it comes to welding, steel welds still suffer if exposed to more than a minor breeze, as wind will cause the welded metal to cool less than uniformly.


With the latest series of steel Starship tank prototypes, SpaceX has significantly improved its production infrastructure, finally offering at least a semblance of protection against the elements. Based on the first test tank’s explosive performance on January 10th, those improvements have paid dividends. According to Musk, test tank #1 made it all the way to 7.1 bar (105 psi) before it burst and test tank #2 reportedly did even better.
Meanwhile, SpaceX’s South Texas team has already finished and partially tested a second Starship test tank, ultimately reaching 7.5 bar with water before a small leak sprung on January 27th. Over the last 24 hours, technicians have worked to repair the apparently minor damage and began filling the Starship tank with ultra-cold liquid nitrogen (boiling point: -196°C / -320°F) around 5:30 pm CST (23:30 UTC) on January 28th. After filling with liquid nitrogen, SpaceX kept the steel tank topped off for several hours. The likely purpose behind that otherwise odd move: something called cryogenic hardening. By exposing certain types of steel to liquid nitrogen temperatures, the material can be dramatically strengthened in some regards.

Around four hours after Tuesday evening’s testing began, the Starship tank prototype appeared to develop a significant leak in its upper dome, hemorrhaging liquid nitrogen that immediately produced large clouds after coming into contact with the South Texas air. As it turns out, whatever was observed was almost certainly not a leak: 30 or so minutes later, the tank was pressurized to failure, releasing a spectacular tidal wave of liquid nitrogen that doused the surrounding area, temporarily killing nearby floodlights and creating a near-zero-visibility storm of fog.
We’ll have to wait for dawn tomorrow to see the extent of the damage, but it appears that Test Tank #2’s demise was dramatically more violent than its predecessor — a largely expected side effect of performing the pressure test with a cryogenic liquid. In fact, just minutes after it appeared to fail, Elon Musk revealed that the second test tank had burst around 8.5 bar (~125 psi), soundly trouncing all records set by earlier tests and suggesting SpaceX is unequivocally ready to begin building the first orbital Starships. Critically, Musk had previously indicated that if Starship’s tanks could survive up to 8.5 bar, SpaceX would have the minimum safety margins it needs to deem Starship safe enough for astronauts.
In other words, if Test Tank #2 really did reach 8.5 bar, SpaceX has effectively solved the biggest structural engineering challenge its Starship program faces, kicking the doors wide open for the more or less immediate mass-production of the first giant orbital-class spacecraft. As it turns out, what Musk has deemed as the first “orbital” Starship prototype – ‘SN01’ – is already under construction, and it’s safe to say that any lessons learned from January 28th’s cryogenic pressure test will be fed back into SN01 and all future prototypes.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Elon Musk
Tesla Cybercabs narrowly miss deadly Amazon cargo plane crash
An Amazon cargo plane crash near Miami’s airport stopped feet from dozens of Tesla Cybercabs.
An Amazon Prime Air Boeing 767 cargo jet overran the runway at Miami International Airport on Sunday afternoon, killing five people and injuring five more. The jet, operated by North Carolina based carrier 21 Air as Flight 7598, touched down around 2 p.m. after arriving from San Juan, Puerto Rico, then crossed the airport perimeter, plowed across NW 67th Avenue and struck multiple vehicles before catching fire, according to the Associated Press.
Photos and video from the scene show the aircraft’s nose stopped within meters of a fenced staging lot holding dozens of gold painted Tesla Cybercabs, the steering wheel free robotaxi Tesla began putting on public roads in Austin last week. Miami-Dade Fire Rescue has confirmed the plane struck “multiple vehicles” but has not said whether any Cybercabs were among them, and neither Tesla nor airport officials have addressed the fleet directly.
The Cybercabs had not yet entered commercial service in Miami. Tesla’s existing Robotaxi operation there runs on modified Model Y vehicles and has been unsupervised since Ashok Elluswamy confirmed the detail on X in July.
Footage of the plane crash from earlier today | #ONLYinDADE pic.twitter.com/iGoOtnd6cD
— ONLY in DADE (@ONLYinDADE) September 6, 2026
Elon Musk offered the briefest of reactions. Replying to a Zero Hedge post about the Cybercabs sitting so close to the wreckage, he wrote a single word: “Weird.” He has not commented further, and Tesla has not issued a statement.
The timing puts Tesla’s newest vehicle near an unrelated but highly visible tragedy just days after its Austin debut, a launch that had already drawn scrutiny from federal regulators. The National Highway Traffic Safety Administration opened an audit how Tesla certified the Cybercab as compliant with federal vehicle safety standards, a process Teslarati covered after the vehicle’s September 3 launch event. That inquiry concerns the car’s lack of a steering wheel and pedals, not the Miami crash.
Investigators from the FAA and NTSB are focused on the plane, not the parking lot beside it. Flight data reviewed by outlets including Simple Flying show the 767 touched down around 170 knots, well above the 135 to 140 knot range typical for the aircraft, though investigators have not determined a cause. Amazon said it is working with authorities and that its priority is the safety of everyone affected.
Whether any Cybercabs were damaged, and what Tesla plans for the fleet parked near one of the country’s busiest airports, remain open questions.
News
Tesla crosses major Unsupervised Self-Driving milestone
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.
News
Tesla Robotaxi will be a 24/7 service: here’s when
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.