News
SpaceX's latest Starship test was uneventful and that's great news for its flight debut
According to Elon Musk, SpaceX has successfully completed its latest Starship prototype test in a uniquely uneventful fashion, great news for the next-generation rocket’s next steps and first flight tests.
The SpaceX CEO revealed the news some 12 hours after the company wrapped up the Starship tank test at its Boca Chica, Texas facilities. Another excellent example of SpaceX’s preferred process of agile development, the test followed just nine days after the Starship SN01 prototype’s first cryogenic test unexpectedly unearthed a design flaw. SpaceX analyzed the results of Starship SN01’s unintentional launch debut and drew up plans to rapidly repurpose a Starship tank initially destined for the SN02 prototype.
By using existing hardware to test an upgraded iteration of the part that destroyed Starship SN01, SpaceX has now effectively retired the risk posed by that prior failure less than two weeks after it occurred. Elon Musk specifically noted that the former SN02 engine section “passed cryo pressure & engine thrust loads,” confirming that there was more to the exceptionally uneventful evening of March 8th than met the eye. While putting on much less of a show for local observers, this particular boring test is a great sign for the next few steps of SpaceX’s Starship development program.
SN2 (with thrust puck) passed cryo pressure & engine thrust load tests late last night— Elon Musk (@elonmusk) March 9, 2020
Simply put, despite successfully demonstrating that Starship’s improved “thrust puck” and engine section can survive flight-level tank pressures and the thrust of a Raptor engine, one would be hard-pressed to determine as much by inspecting the prototype that managed the feat. Such a visually uneventful test is a first for SpaceX’s post-Starhopper Starship testing, where “before” and “after” photos typically start with a shiny tank and finish with a well-distributed field of steel shrapnel.
Musk’s description of the test suggests that SpaceX’s intention with the SN02 test tank – built in just two weeks – was to stress it up to (and likely beyond) the pressures and mechanical stresses Starship engine sections will need to survive in flight. In simpler terms, they likely tried to burst the tank by pressurizing it with liquid nitrogen, a supercool cryogenic fluid. It’s unclear exactly how far SpaceX pushed the tank, but it’s safe to say that it went at least as high as past test tanks, meaning 7-8.5 bar or 100-125 psi. At a bare minimum, a test that failed to reach Starship’s minimum flight pressure of 6 bar (90 psi) would be of dubious value for the actual orbital ship.
A step further, SpaceX installed a hydraulic jack underneath the test tank in a bid to simulate the stresses it would experience with a single Raptor engine. Capable of producing approximately 150-200 tons (1500-2000 kN) of thrust, even Raptor is relatively minor compared to the Starship tank’s likely ~500 metric ton (1.1 million lb) mass. Still, the fact that the SN02 test tank survived the combination of a highly pressurized tank and the simulated thrust of a Raptor engine suggests that SpaceX is now ready for a more successful repeat of Starship SN01 testing.
Confirming those suspicions, Musk subsequently revealed that the Starship prototype integrated immediately after the SN02 test tank will likely attempt the first Raptor static fire tests and may even perform short flights further down the road. As always, SpaceX’s testing programs are fluid and likely to change as new results continuously shape the path forward, meaning that Starship SN03 could easily be destroyed during testing. Starship SN04, said by Musk to be the hopeful candidate for “longer [test] flights,” would thus be repurposed to continue SN03’s test campaign — and so on with SN05, SN06, and beyond.
Regardless, as the CEO notes, perhaps the most important aspect of all these rapid-fire tests is that SpaceX is quickly building up an impressive Starship production line. Before, during, and after SN02’s test campaign, SpaceX’s South Texas team has been simultaneously fabricating and stacking new steel rings, bulkheads, and noses for the next few Starship prototypes. As a result, Starship SN03’s tank section could be just a week or two away from complete integration, after which SpaceX will likely transport it to the launch pad to prepare for Raptor static fire testing.
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
