News
SpaceX scraps Starship SN8 wreckage, clears landing zone for next launch
In spite of tentative plans for preservation, SpaceX has fully scrapped the wreckage of the first high-altitude Starship prototype, clearing the landing zone it impacted for its successor’s imminent launch debut.
Known as serial number 8 or SN8, the Starship prototype was the first of any kind to fly beyond 150 meters (~500 ft), reaching an altitude of 12.5 km (~7.8 mi) on December 9th during its breathtaking launch debut. In an unexpected twist, SpaceX kept Starship SN8’s thrust to weight ratio as low as possible, stretching what could have been a two or three-minute test into an almost seven-minute ordeal with three consecutive Raptor engine cutoffs during the ascent.
At apogee, SN8 used cold gas thrusters to flip into a belly-down orientation and free-fell ~95% of the way back to Earth before igniting two of its three Raptor engines, performing a wild powered flip back into a vertical landing position and nearly securing a soft landing. Unfortunately, around 10-20 seconds before that planned landing, what Musk later described as low methane header tank pressure starved the Starship’s engines of fuel and more or less cut all appreciable thrust, causing SN8 to reach its landing zone traveling about 40 m/s (~90 mph) too fast. The rocket impacted the concrete pad, crumpled, and exploded.
By all accounts, success was one of the less likely outcomes SpaceX expected from SN8’s high-altitude debut, with Musk himself estimating the odds of total success to be just 33%. Additionally, Starship SN8 effectively made it all the way to a low-speed landing regime that Starships SN5 and SN6 all but flawlessly demonstrated with back-to-back 150m hops and landings in August and September 2020.
In other words, despite the explosive end, SN8’s high-altitude launch debut was a spectacular success for SpaceX’s Starship program – possibly even preferable to a perfect landing given that it uncovered an unexpected issue with fuel tank pressurization. Beyond the landing failure, the Starship checked every single box on SpaceX’s test flight list, successfully debuting multiple Raptors, demonstrating multiple in-flight engine shutdowns and engine relights; proving that an unprecedented ‘skydiver-style’ landing maneuver is possible and viable; and successfully testing Starship’s ability to control itself in that bellyflop orientation with thrusters and four massive flaps.
Speaking in a recent interview with Ars Technica, in the words of pragmatic SpaceX COO and President Gwynne Shotwell, SN8’s launch debut “de-risked [the Starship] program pretty massively.” According to Musk, SpaceX engineers were quickly able to determine why Starship SN8’s methane header tank was unable to maintain the fuel flow (pressure) needed for Raptor’s landing burn(s) and quickly implemented a solution.
Instead of pressurizing autogenously with methane gas, Starship SN9 will use helium to pressurize its fuel header tank, serving as a temporary fix while SpaceX determines what changes need to be made to get rid of that helium crutch. Landing pad now cleared of Starship remains and SN8’s impact crater more or less repaired, the only thing standing between Starship SN9 and its own 12.5 km launch debut is a triple-Raptor static fire test. Originally expected as early as January 4th, SpaceX never made it more than a few minutes into the attempt, while a backup window on January 5th was canceled later that evening. The test could now occur no earlier than (NET) Wednesday, January 6th.
Thankfully, although SpaceX was unable to save the entirety of Starship SN8’s wrecked nose section, the company did manage to extract a largely intact nose flap. The rest of the remains were scrapped on site and trucked away but it’s possible that certain significant components of SN8 – particularly the recovered flap – will eventually find themselves on display at one or more SpaceX facilities.
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.
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 Cybercabs narrowly miss deadly Amazon cargo plane crash
Tesla crosses major Unsupervised Self-Driving milestone
