News
SpaceX already clearing Starship debris, preparing for next rocket rollout
Update: Half a day after Starship serial number 10 (SN10) became the first prototype to land in one piece, SpaceX has begun clearing its remains and preparing to roll the next rocket to the launch pad.
Never one to rest on its laurels, SpaceX appears to be wasting no time moving forward from Starship SN10’s successful landing and subsequent explosion. Almost a month ago, SpaceX stacked SN10’s successor – Starship SN11 – to its full height and has spent the last four weeks closing out the virtually identical rocket. As of SN10’s launch debut, Starship SN11 has been more or less finished and ready to roll to the launch pad for at least a week.
At the same time as SpaceX teams have begun the process of recovering SN10’s remains, the company also transported a large crane to the launch site – the same crane used to install Starships SN8, SN9, and SN10 at the launch pad. Stay tuned for updates as SpaceX prepares SN11 for a fourth high-altitude launch and landing attempt – this time with the goal of keeping the rocket intact after landing.
In a classically spectacular fashion, a SpaceX Starship prototype has successfully touched down in one piece for the first time ever, only to explode minutes later after catching itself on fire.
Rolled from SpaceX Boca Chica Starship factory to test and launch facilities just a mile down the road on January 28th, Starship SN10 lifted off just five weeks later – the fastest factory-to-launch flow yet. The speed of that turnaround was mainly made possible thanks to an exceptionally smooth test campaign, passing cryogenic proof and static fire tests after only a few attempts.
Prior to its second launch attempt, Starship SN10 automatically aborted a few seconds prior to its first attempt after the rocket’s flight computer determined that its three Raptor engines were producing more thrust than expected. Within half an hour of the abort, CEO Elon Musk took to Twitter to reveal the cause and stated that SpaceX would be tweaking the flight software’s thrust limits and recycling for another shot at launch around two hours later.
Up to the last 20 or so seconds of the 6.5-minute flight test, Starship SN10’s launch debut was virtually identical to Starships SN8 and SN9, both of which made it just one or two dozen seconds away from a soft landing. However, after SN9, SpaceX optimized the landing process to add additional redundancy, meaning that SN10 reignited all three of its Raptor engines – instead of just two – for its flip and landing burn.
Exactly as planned, SN10 fired up those engines, autonomously analyzed their performance, and then shut down two Raptors to leave the best-behaving engine to complete the final landing burn. Unlike SN8 and SN9, that maneuver went about as well as it could have, nearly slowing SN10 to a hover with one (seemingly) healthy engine to take it the rest of the way to the ground.
After all that heroic effort and for the first time ever, Starship SN10 proceeded to touch down in one piece. Through the eyes of a drone hovering far away from the launch complex, the landing couldn’t exactly be considered ‘soft,’ however, and SN10 impacted the landing zone with some substantial momentum – likely far too much for its tiny legs to handle.
However, more importantly, SN10 appeared to ignite one or two of its own gaseous oxygen or methane vents, triggering a fire that remained visible until well after the hard – but intact – landing. From official and unofficial views of the landed vehicle, Starship SN10 had a significant lean and appeared to have no more than a few inches to a foot of clearance between its aft skirt and the concrete pad. Remote-controlled firefighting spigots were able to extinguish any external sign of fire but that lack of clearance may have prevented the water from doing much inside the skirt, ultimately dooming Starship SN10.
Regardless of where exactly that fire ‘broke through,’ so to speak, the original cause of the fire – accidentally igniting a vent plume – is unlikely to be a hard problem to fix, and it’s safe to say that SN10’s intact landing is an extraordinary success for SpaceX. In its official webcast, SpaceX engineer John Insprucker confirmed that Starship SN11 is all but complete and could roll out to the launch pad to pick up where SN10 left off almost as soon as it’s safe to do so.
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
