News
SpaceX’s next Starhopper flight needs more analysis for FAA go-ahead, says Elon Musk
According to SpaceX CEO Elon Musk, the company’s next major Starhopper flight test is still awaiting FAA approval due to a need for more hazard analysis, presumably required because Starhopper will be traveling much higher than before.
On August 9th, SpaceX completed a routine wet dress rehearsal (WDR) with Starhopper, loading the vehicle with propellant and fluids and replicating a launch countdown up to the point of Raptor ignition. Starhopper remains untethered in a sign that SpaceX doesn’t have plans for a static fire test before the low-fidelity rocket prototype’s next flight milestone. Originally scheduled for August 12th, that milestone – a 200m (650 ft) hop test – has been indefinitely delayed as SpaceX awaits an updated permit from the Federal Aviation Administration (FAA).
The oddity of the apparent difficulty SpaceX is having with the FAA’s experimental permit process is deepened by the fact that Starhopper is already permitted by the FAA and demonstrated its first successful flight just a few weeks ago, on July 25th. On top of the fact that the local Boca Chica and Brownsville, Texas airspace tends to be extremely quiet, it’s unclear what exactly is holding up SpaceX, the FAA, or both in what should otherwise be a relatively streamlined process.
A few weeks ago, after one false start on July 24th, Starhopper performed its first untethered flight ever on July 25th, successfully demonstrating its integrated steel propellant tanks, avionics, software, and Raptor propulsion over the course of 20 or so seconds of flight. Starhopper’s inaugural flight was delayed at least several weeks by a major bug with SpaceX’s next-gen Raptor engine, described by Elon Musk as a problem with a certain frequency of vibration (i.e. mechanical resonance).
According to Musk, said resonance failure mode was effectively solved with unspecified modifications made to the sixth Raptor engine produce (Raptor SN06). That engine became the first to successfully pass SpaceX’s regime of pre-hop static fires in McGregor, Texas around July 10th and was shipped south to Boca Chica and installed on Starhopper scarcely 24 hours later.
Assuming those vibration issues have been completely quashed, Musk has also stated that SpaceX is aiming to produce as many as two Raptor engines per day by the end of 2019. It’s believed that all engines preceding SN06 (SN01-05) were either damaged or destroyed during testing, be that a result of intentional testing-to-destruction or anomalous behavior during certain test regimes. It should be noted that full-scale Raptor is still undoubtedly in development and hardware failure during developmental testing is more predictable and valuable than it might seem. As long as the program can handle it, ‘hardware-rich’ development (i.e. moving fast and breaking things) can be equally – if not more – valuable than an extremely cautious get-it-right-the-first-time approach.
Regardless, once SpaceX’s propulsion engineering team is confident that the more major bugs that plagued early Raptor engines have been alleviated, they will likely give the go-ahead for the engine manufacturing team to begin ramping production rates. Musk believes that SpaceX could be ready for the first test flights of either or both of the company’s orbital Mk1 and Mk1 Starship prototypes as early as mid-September, milestones that will eventually require three sea-level Raptor engines and up to three vacuum Raptor engines per rocket.
Meanwhile, although SpaceX has yet to begin assembling the first Super Heavy booster(s), said boosters will require dozens of Raptor engines each for their first flights. Musk says that SpaceX will start out with something like 20 Raptor engines per booster to minimize losses and disruption in the event of a catastrophic failure, eventually expanding to as many as 35 engines per booster as confidence grows.
For now, Starhopper’s next flight test was scheduled from August 16th through the 18th but has since been tentatively rescheduled to Aug. 19-21. Starhopper will remain grounded until the FAA is satisfied with SpaceX’s updated hazard analyses for the rocket’s 200m flight test.
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
