News
SpaceX Starship destroyed during cryo test but the next ship is already on the way
SpaceX’s third full-scale Starship prototype has followed a little too closely in the footsteps of its predecessors, suffering a catastrophic failure during its first cryogenic test.
On April 2nd, SpaceX successfully put Starship SN3 through an ambient temperature pressure, allowing the ship to take its first breaths and ensuring that no leaks were present in its massive propellant tanks. Just a handful of hours later, Starship SN3 began its first attempted cryogenic proof test. Neutral liquid nitrogen was loaded into the ship’s liquid oxygen (LOX) tank for a brief period before SpaceX aborted the test due to frozen valves in the ground support equipment (GSE) tasked with feeding the rocket — confirmed by CEO Elon Musk around 7:30 pm PDT.
Around six hours after the first attempt, SpaceX presumably managed to alleviate GSE valve issues and began Starship SN3’s second attempted cryogenic proof test around 11pm local (04:00 UTC). While things started out somewhat normally, they did not end well for the rocket prototype.
For unknown reasons, SpaceX began the second cryo test attempt by only loading Starship’s upper (LOX) tank with supercool liquid nitrogen. Given that Starship is constructed out of stainless steel sheets only slightly thicker than two US quarters, the lower (methane) tank would have almost certainly had to be pressurized, too, likely relying on gaseous (ambient temperature) nitrogen. Already, for a rocket built out of near-continuous metal, that temperature differential could pose a major problem.
Still, for the better part of three hours, things seemed to go exactly as planned, with the rocket venting dozens of times and the upper tank visibly developing a coating of frost as it began to freeze the water vapor right out of the humid Texas air. Alas, around 2:07am local (07:07 UTC), things took a turn for the worse. The unfilled methane tank below the now-LN2-laden LOX tank appeared to crumple, beginning at a small dent that appeared over the course of the test. Gravity took over a few seconds later, further crumpling the methane tank and causing the top-heavy rocket to tip over and the LOX tank to burst.
While admittedly from the armchair, not a lot of this particular failure makes sense. If the bottom methane tank were significantly pressurized with gaseous nitrogen, a rapid loss of structural integrity would have likely been a far more violent ordeal as the gas attempted to escape. Instead, the failure was – relative to the possibilities – extremely gradual. In fact, it almost appeared as if the bottom methane tank was either never actually pressurized or not pressurized nearly enough to withstand the weight of several hundred tons of liquid nitrogen. Given SpaceX’s expertise and familiarity with rocketry, that option thankfully seems vanishingly unlikely.
All other possible explanations are at least as hard to parse, leaving it up to SpaceX or CEO Elon Musk to clarify what transpired if they choose to do so.
On a more positive note, SpaceX has continued to churn out steel rings and bulkheads and assemble them into sections of Starship SN4 – the rocket’s next full-scale prototype – for the last two or so weeks. If Starship SN1, SN2, and SN3 are anything to go by, the fourth full-scale Starship prototype could be ready to head to the pad for testing just a handful of weeks from now, picking up where Starship SN3 left off. Thankfully, the latter rocket’s April 3rd failure appears to have been relatively benign as far as pad hardware goes, likely requiring minimal repair work to be ready for its next test campaign.
While unfortunate, it’s critical to remember that this is all part of SpaceX’s approach to developing new and unprecedented technologies. Be it Falcon 1, Falcon 9 booster recovery, or Falcon 9 fairing recovery, all groundbreaking SpaceX efforts have begun with several consecutive failures before the first successes – and the first streaks of consecutive successes. Given Musk’s September 2019 claim that SpaceX is putting just ~5% of its resources into Starship, prototypes like Mk1, SN1, and SN3 are being fabricated for pennies on the dollar.
As a schedule setback, SpaceX is building ships so quickly that any single prototype failure shouldn’t cause more than a handful of weeks of delays, and the goal is to produce an entire Starship every week by the end of 2020. For now, SpaceX will hopefully learn from each failure during developmental testing and roll those lessons learned into each future prototype.
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
