News
Starhopper update: SpaceX’s ungainly Starship testbed survives night of fireballs, Raptor testing
SpaceX’s Starhopper appears to have come out the other end of an eventful night of fires, fireballs, and Raptor testing completely unscathed, although – as with all things rocketry – there is vastly more than meets the eye.
However, signs point towards Starhopper being almost entirely unharmed by its brief voyage inside a fireball – even if Boca Chica’s fire suppression system got a thorough workout and many a SpaceX onlooker likely suffered a partial heart attack. For the time being, it’s safe to assume that Starhopper’s planned flight activities have been indefinitely delayed as SpaceX technicians analyze the vehicle and engineers work to mitigate or completely prevent major fires from recurring.
According to NASASpaceflight.com’s well-informed sources, despite the spectacular fireworks that followed Raptor’s own impressive display, the engine’s static fire test was a full success – at least in terms of data produced by the engine. The large fireball was attributed to the ignition of a large methane vent that followed soon after Raptor’s shutdown.
For now, this means that Starhopper’s untethered flight test and hover test debut should not be expected to occur for several days, even in the event that the rocket, pad, and Raptor engine all made it through their July 16th ordeal completely undamaged. If there is zero damage, this accident will serve as an unfortunate but useful demonstration of a true stainless steel rocket’s theoretically exceptional sturdiness and heat resistance.
Despite suffering what looked like a serious fireball-related anomaly, #Starhopper appears to have been refueled and is visibly venting while the flare stack burns off excess methane. Very good sign that the issue looked worse than it is. Via @labpadrehttps://t.co/sOHShoRByb pic.twitter.com/cs6FSMcZ0T— TESLARATI (@Teslarati) July 17, 2019
It may seem more than a little ironic, but it’s likely less than a coincidence. If it comes to fruition as a truly functional, orbit-capable steel rocket, spaceship, and upper stage, Starship/Super Heavy will exist in their shiny, steel forms almost entirely because of the unintuitive tradeoffs that could theoretically make heat-resistant-but-dense steel more efficient than a ship built out of ultra-light carbon composites. If Starhopper’s newly demonstrated resilience is anything to go by, a very happy side-effect of that efficient, heat-resistant steel could be an almost unprecedented resilience in the face of serious fires, fireballs, and other fire-related anomalies.
For almost any other rocket, exposure – at least outside of the engine section – to large fireballs and quite literally having parts burning while motionless on the ground are deeply, deeply worrisome things and risk a major vehicle malfunction – potentially up to and including a catastrophic failure (i.e. explosion). ULA’s Delta IV rocket family is famous for self-immolating during ignition and liftoff, a minimal concern to the rockets’ thin, aluminum tankage thanks to several inches of thick, fire-retardant foam insulation.
For a rocket like Falcon 9, almost entirely (by surface area) composed of thin, aluminum propellant tanks and carbon composite structures, there is a constant struggle to balance the vehicle’s extreme performance with the low melting point of its primary structures (~720 degrees C). The 301-series stainless steel Starhopper and Starship(s) are built out of has a melting point of ~1400 degrees C, nearly double aluminum-lithium alloys.
In short, while it boggles the mind and is decidedly unintuitive to anyone who watched July 16th’s live coverage of the static fire, it’s actually not a huge surprise that Starhopper has suffered serious fire-related anomalies with essentially zero visible damage. In fact, it’s almost impossible to tell that anything at all happened, let alone discerning some subtle sign(s) of damage incurred by fires. It may sound ironic to say so, but rockets and fire just do not tend to like each other much at all.
Time will tell if Starhopper and Raptor are in as good a condition as they appear to be.
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
