News
SpaceX recaps historic Starship landing in 4K as next ship readies for flight
SpaceX has published a new 4K video recapping Starship’s first intact landing after a high-altitude launch right as the company is preparing the next ship for flight.
On March 3rd, Starship serial number 10 (SN10) briefly became the first prototype to successfully launch to 10 km (6.2 mi), ‘skydive’ back to Earth, flip around, and land in one piece. Put simply, Starship SN10 made it unequivocally clear that the exotic, unproven method of landing selected by SpaceX could be made to work. Unfortunately, while Starship SN10 did land in one piece, the landing was much harder than planned.
Due to some combination of that hard landing and an apparent onboard fire that started in the last ~20 seconds of flight, SpaceX only had around six minutes to contemplate its success before Starship SN10’s propellant tanks were breached, violently depressurizing the rocket and causing a large explosion and fire.
Previously discussed on Teslarati, SpaceX CEO Elon Musk later took to Twitter to offer some educated guesses as to why Starship SN10 exploded.
“Starship SN9 ultimately failed a few seconds earlier than Starship SN8 when one of its Raptor engines failed to ignite, precluding a true flight test of the helium pressurization fix. As it turns out, Musk believes that that very fix may have doomed Starship SN10.
As Starship SN10 forged ahead past the points of failure that killed SN8 and SN9, the SpaceX CEO thinks that one or more of the vehicle’s three Raptor engines began to ingest some of that helium as they drained the methane header tank. As a result, engine thrust fell below expected values, preventing Starship SN10 from fully slowing down for a soft landing. Instead, the Starship hit the ground traveling a solid 25 mph (~10 m/s), obliterating its tiny landing legs and damaging its skirt section.”
Teslarati.com – March 10th, 2021
In other words, the losses of Starships SN8, SN9, and SN10 all share a relatively common point of failure – propulsion reliability. Technically, only Starship SN9’s failure can be blamed specifically on Raptor, one of which failed to ignite during its flip and landing maneuver. SN8 and SN10 both failed because of issues in the complex network of plumbing and pressurization systems responsible for feeding Raptors the right amount of propellant.
For SN8, the ship’s pressurization system failed to provide the necessary fuel head pressure at the last second, starving the Starship’s Raptors. SN10 ironically failed because the quick fix inspired by SN8’s failure – partially replacing a methane pressurant with helium – likely contaminated its methane fuel with helium, effectively watering down Raptor’s performance. While likely frustrating for SpaceX, the failures are still extremely valuable and loss of hardware remains a routine and intentional part of the company’s approach to iterative rocket development.
On the plus side, the FAA has already cleared SpaceX’s next Starship for flight after SN10’s momentary success and subsequent explosion. Spurred by that brief taste of total success, SpaceX wasted no time to prepare that next prototype – Starship SN11 – for flight and rolled the rocket to the launch pad mere days after SN10’s March 3rd flight. That very same day, SpaceX completed ambient pressure testing – a basic verification that Starship SN11 is leak-free.
A few days later, SN11 appeared to pass its first cryogenic proof test, replacing room-temperature gas with cryogenic liquid nitrogen. Three days after that, SpaceX attempted to put the Starship through its first triple-Raptor static fire test but appeared to suffer an abort milliseconds after a partial ignition of one or two of its three engines. Starship SN11 briefly caught fire and burned for at least 20-40 seconds after the abort, unsurprisingly triggering several days of delays. Nevertheless, if SN11 can make it through a second static fire attempt without issue on Thursday or Friday, the Starship is still well on track to take flight weeks earlier than any of its predecessors.
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
