News
SpaceX Starship blew its top during rocket fueling test (updated)
Update: SpaceX has released an official statement indicating that Starship Mk1’s November 20th failure came after a decision to intentionally pressurize the rocket prototype to its limits. This likely means that the test was to max flight pressures and not an intentional burst test, so Starship’s dome failure is still a significant concern and was definitely not planned.
More importantly, SpaceX says that it had already decided to retire Starship Mk1 before any kind of flight testing, treating the vehicle as a pathfinder. Instead, SpaceX will build and use Starship Mk3 – the next Boca Chica prototype – for Starship’s first attempted skydiver-style landing and 20 km (12 mi) flight test.
SpaceX statement on the above test and incident: pic.twitter.com/r1ReRYhUhz— Michael Sheetz (@thesheetztweetz) November 21, 2019
SpaceX’s first full-scale Starship prototype has suffered a significant failure during testing, destroying or severely damaging large sections of the rocket. However, SpaceX CEO Elon Musk has already commented on the anomaly and is not all that concerned.
On November 20th, SpaceX – having canceled a planned road closure the day prior – unexpectedly requested a last-second road closure and entered into a much more serious round of testing with Starship Mk1, the rocket’s first full-scale prototype. This followed testing on November 18th that concluded with Starship Mk1’s very first ‘breath’ – some venting activity near the end of a tank proof test. SpaceX technicians spent the next 36 or so hours inspecting and working on Mk1, presumably looking for and patching minor leaks along its tank section.
The November 20th testing progressed far faster than the previous round of tests and Starship Mk1 was quickly venting again. Soon after that, frost began to appear on the exterior of its steel liquid oxygen and methane tanks, a telltale sign that some form of cryogenic testing was ongoing. Based on a distinct lack of activity at the nearby flare stack, SpaceX was using liquid oxygen (LOX) or liquid nitrogen (LN2) to verify that Starship performs as expected when filled with supercool propellant.
After initial venting and visible frost formation, SpaceX appeared to push forward, rapidly loading Starship Mk1 with LOX or LN2. This progress was easily visible thanks to the fact that the mass and pressure of all that cryogenic liquid made quick work of the slight imperfections on the exterior of Starship’s steel hull, turning the vehicle’s reflection from a speckled patchwork to an almost mirror-like finish. Roughly half an hour later, the otherwise peaceful scene was interrupted by the rapid failure of Starship Mk1’s upper LOX tank dome, instantly thrown several hundred feet into the air.
Seconds later, the crumpled upper half of Starship Mk1’s tank section appeared out of the clouds created and began hemorrhaging a huge volume of liquid oxygen, immediately boiling and vaporizing as it was exposed to the Earth’s comparatively white-hot atmosphere. Impressively, Starship appeared to remain functional after its top quite literally blew off, and the vehicle rapidly detanked and appeared to safe itself. Some ten minutes after the overpressure event, the freed liquid oxygen had boiled to nothing and Starship appeared to be quiet.
By all appearances, Starship Mk1 appeared to perform extremely well as an integrated system up to the point that its upper tank dome failed. The first frame from LabPadre’s stream with anything visibly amiss explicitly implicates the weld connecting the LOX dome to the cylindrical body of Starship’s LOX tank, point to a bad weld joint as the likeliest source of the failure. Although that hardware failure is unfortunate, Mk1’s loss will hopefully guide improvements in Starship’s design and manufacturing procedures.
Moving forward
Minutes after the anomaly was broadcast on several unofficial livestreams of SpaceX’s Boca Chica facilities, SpaceX CEO Elon Musk acknowledged Starship Mk1’s failure in a tweet, telegraphing a general lack of worry. Of note, Musk indicated that Mk1 was valuable mainly as a manufacturing pathfinder, entirely believable but also partially contradicting his September 2019 presentation, in which he pretty clearly stated that Mk1 would soon be launched to ~20 km to demonstrate Starship’s exotic new skydiver landing strategy.
Musk says that instead of repairing Starship Mk1, SpaceX’s Boca Chica team will move directly to Starship Mk3, a significantly more advanced design that has benefitted from the numerous lessons learned from building and flying Starhopper and fabricating Starship Mk1. The first Starship Mk3 ring appears to have already been prepared, but SpaceX’s South Texas focus has clearly been almost entirely on preparing Starship Mk1 for wet dress rehearsal, static fire, and flight tests. After today’s failure, it sounds like Mk1 will most likely be retired early and replaced as soon as possible by Mk3.
Above all else, the most important takeaway from today’s Starship Mk1 anomaly is that the vehicle was a very early prototype and SpaceX likely wants to have vehicle failures occur on the ground or in-flight. As long as no humans are at risk, pushing Starship to failure (or suffering unplanned failures like today’s) can only serve to benefit and improve the vehicle’s design, especially when the failed hardware can be recovered intact (ish) and carefully analyzed.
A step further, SpaceX is simultaneously building a second (and third) Starship prototype at its companion Cocoa, Florida facilities, and Starship Mk2 is nearly finished. Coincidentally, technicians installed its last tank dome – the same dome that failed on Mk1 – just days ago, and any insight that the Boca Chica team can gather from Mk1’s troubles will almost certainly be applied to Mk2, whether that means reinforcing its existing domes or fully replacing the upper dome with an improved design.
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
