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’s Automatic Collision Evasion feature can be seen in one of the first owner videos of it in action.
Tesla owner Spencer (@scotsrule08) posted on Monday that the feature “worked flawlessly,” saying FSD reengaged itself just as he was about to hit a curb. Ashok Elluswamy, who leads Tesla’s AI team, shared the clip and wrote, “A guardian angel always looking out for you.”
The video arrives in the middle of a staged rollout. Tesla first shipped Automatic Collision Evasion with FSD (Supervised) v14.3.9 in software update 2026.27.6 earlier this month, which Teslarati covered as it reached cars. Update 2026.27.10, which began going out on September 19, carried the feature improvements with FSD v14.3.10, according to release notes tracked by Not a Tesla App. The newer 2026.27.11 build is now reaching another wave of vehicles.
The new Automatic Collision Evasion feature worked flawlessly! FSD reengaged itself just as I was about to hit a curb.
Kudos @Tesla_AI team! 👏 pic.twitter.com/Fbp15HhpL2
— Spencer (@scotsrule08) September 28, 2026
The feature only runs on HW4 vehicles, and it requires an active FSD purchase or subscription with both FSD (Supervised) and Automatic Emergency Braking enabled. HW3 owners receive FSD v14.2 Lite in the same updates, but that build does not include collision evasion.
Tesla’s release notes describe two triggers. The first is an imminent frontal collision that braking alone may not prevent, in which case the car can activate FSD to steer, brake or accelerate around the hazard. That scenario is limited to highways below 85 mph, with no pedestrians or cyclists detected and no slippery road surface. The second covers a driver who appears inattentive, such as reaching into the back seat, or who seems to have switched off FSD by accident. Spencer’s curb clip appears to fall into that second category.
Tesla plans big safety improvements for Full Self-Driving v15
Once the system takes over, the accelerator is muted and light brake input will not cancel the maneuver. Drivers need to apply firm, deliberate steering force to take back control, and the car chimes to hand control back once the danger has passed.
Elluswamy recently noted that earlier hazard prediction, faster reaction time and better collision avoidance would arrive with FSD v15, the next major version.
Tesla is delaying its event for the Roadster, moving it from this Thursday, October 1, to Thursday, October 15, due to unfavorable weather.
The company has said it has been tracking the weather for this Thursday closely with local meteorologists, and because the event can only be held outside, Tesla is making the call to delay it:
“We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule. New date is October 15. Additional details to follow.”
Roadster event update
We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule.
New date is October 15. Additional details to…
— Tesla (@Tesla) September 28, 2026
We are sure that this is bringing back PTSD for some Tesla fans, and we know it is not ideal, but this also reveals some things about the event. Tesla said that this can only be held outdoors, meaning it bodes well for the rumors that the vehicle could potentially hover.
Some believe that this was essentially confirmed by the FAA airspace restriction they were granted, but this could have been for a drone show or to keep drones from spying on the event.
Tesla Roadster is available for order once again following brief hold
The Roadster event has been long-awaited, and it is unfortunate that the weather is going to keep us all waiting a little bit longer.
The Tesla Roadster will be unveiled in Waco, Texas.
Elon Musk
SpaceX turned a heralding moment for Starship into its greatest
Starship reached orbit despite losing an engine, deployed 26 Starlink V3 satellites on Flight 14.
SpaceX’s Starship reached orbit for the first time on Monday, and for a few nail-biting minutes it looked like it wouldn’t. During ascent on Flight 14, one of Ship 41’s six Raptor engines shut down early, and SpaceX’s livestream host Dan Huot told viewers the team had decided not to commit to orbit. Minutes later, after what Huot described as a lot of conversation in the control room, the final poll came back in favor, and a roughly 19 second burn of a single Raptor pushed the ship into orbit about 170 miles up.
The reversal matters because SpaceX had written the exit ramp into the mission plan. The company said it would only fire the orbital insertion burn if flight controllers confirmed enough backup hardware remained for the deorbit burn, a condition Teslarati laid out ahead of the flight. Losing an engine was exactly the scenario that rule was built for.
Pressing forward fits Elon Musk’s history. Falcon 1 failed three straight times before its fourth launch reached orbit in 2008, with SpaceX nearly out of money, and Starship was developed by flying prototypes until they broke. What changed this year SpaceX going public, and with $SPCX sliding below its IPO price in July when Flight 13 slipped, the short interest climbed significantly, as Teslarati reported at the time. A Starship potentially lost today with revenue generating next-gen Starlink satellites aboard would have landed directly on shareholders.
Splashdown confirmed. Congratulations to the entire SpaceX team on the first orbital flight of Starship! pic.twitter.com/urjmiwnvNl
— SpaceX (@SpaceX) September 28, 2026
That pressure showed up after orbit. SpaceX cut a flight planned to last nearly 10 hours to about three, moving splashdown from west of Chile to the North Pacific near Hawaii. SpaceX gave no reason, though Musk said this month the company was being extremely cautious about debris risk. The single Raptor for deorbit worked, and Ship 41 completed its flip and landing burn before breaking apart in the water, an outcome SpaceX expected. Musk has structured SpaceX’s governance to shield long term bets from market pressure.
The payload is the bigger business story. Musk posted that all 26 Starlink V3 satellites deployed and are “operating nominally.” Each V3 is rated for about 1 Tbps of downlink and 160 Gbps of uplink, so this single launch adds roughly 26 Tbps, about 10 times what a Falcon 9 load of V2 Mini satellites adds. The V3 is too large for Falcon 9, making Starship the only vehicle that can build out the planned 100,000 satellite constellation, at up to 60 per flight once it reaches routine service. Unlike the 20 V3 units on Flight 13, which reentered on a suborbital path, these will raise their orbits and could begin serving customers within weeks and bring in hundreds of millions of additional dollars in projected Starlink revenue.
SpaceX has already begun winding down Falcon 9 Starlink launches from Florida in favor of Starship. Reported targets put Flight 15 as early as October 19, leaving about three weeks to diagnose Monday’s engine shutdown before the next orbital attempt.
Starship’s 14th flight is set to launch on Monday, Sept 28. The 75-minute launch window opens at 7:15 a.m. CT. Live coverage of the mission starts ~35 minutes before launch → https://t.co/uQKQvgaTmJ
— SpaceX (@SpaceX) September 27, 2026
Watch Tesla’s “guardian angel” FSD feature take over for collision evasion
Tesla Roadster event gets delayed due to unfavorable weather
