News
Elon Musk says SpaceX’s orbital Starship debut headed for FAA faceoff in a few weeks
CEO Elon Musk says that SpaceX’s first completed Starship rocket could be ready for its orbital launch debut just “a few weeks” from now – far sooner than most expected.
On August 6th, SpaceX very stacked that same vehicle – Starship 20 (S20) and Super Heavy Booster 4 (B4) – to its full height for the first time ever, briefly creating the largest rocket ever assembled. However, the feat was equally a symbolic photo opportunity. SpaceX did install an unprecedented number of Raptor engines on Booster 4 and Ship 20 in a spectacularly short timeframe and both stages are technically meant for flight, but Starship S20 was demated less than an hour later and shipped back to the factory shortly thereafter.
Though they’d had Raptors installed and been stacked to their full ~120m (~390 ft) height, neither booster or ship were truly complete and at least 20% of their engines had yet to be qualified at SpaceX’s McGregor, Texas test campus. Both needed a week or two of additional work – mostly just wiring avionics and installing secondary and tertiary plumbing. Curiously, on August 13th, Starship S20 was once again rolled to SpaceX’s Boca Chica launch site in a partial state of completion, where it now sits beside the orbital launch mount for unknown reasons.
After several days of delays, SpaceX also removed Super Heavy B4 from the orbital launch mount and returned it to the build site on August 11th, where teams are still working to finish its secondary plumbing and avionics. Like Ship 20, all of its Raptors were removed soon after its return, freeing both to complete cryogenic proof testing without risking dozens of potentially flightworthy rocket engines.
Like all previous Starship prototypes, those ‘cryo proof’ tests will involved loading Ship 20 and Booster 4 with supercool liquid nitrogen (LN2), simulating the weight and extreme thermal stress of real liquid oxygen (LOx) and methane (LCH4) propellant without the risk of a catastrophic fire or explosion in the event of anomalies.
For more than a month, SpaceX also gradually outfitted one of two suborbital launch mounts with special hydraulic rams that would have simulated the thrust of Ship 20’s three sea level and three vacuum-optimized Raptor engines – the first Starship prototype with such a configuration. The same was true for Booster 4 and SpaceX had outfitted a new test jig with nine hydraulic rams labeled “B4” – clearly meant to simulate the thrust of nine engines pushing against the Super Heavy’s thrust puck. Additionally, a far larger structural test tool unofficially nicknamed the ‘can crusher’ has been more or less finished after ~6 weeks of work, leading many to assume that Booster 4 would be the first Super Heavy to be subjected to the immense simulated thrust of 29 Raptor engines.
However, earlier this week, SpaceX completely disassembled the six hydraulic rams installed on Mount B and removed all nine rams from the apparent Booster 4 jig. Starship S20 was then rolled back to spot beside the orbital launch mount – not the suborbital mount that had been carefully prepared for its test campaign mere days prior. At the time, the only practical explanation – save for some kind of catastrophic miscommunication – was that SpaceX had cancelled clear plans to cryo proof Ship 20 and Booster 4 with simulated Raptor thrust.
Up to now, every single major design change implemented on Starship’s engine section has resulted in the first prototype – and often one or several test tanks – being subjected to cryo proof testing with a complex series of hydraulic rams used to simulate thrust. That most recently peaked with SpaceX’s lone BN2.1 Super Heavy test tank, which seemingly passed a cryo proof, pressure test, and a jig capable of simulating the thrust of up to eight Raptor engines. However, SpaceX has never tested Super Heavy’s new nine-engine thrust puck and has certainly never subjected a Super Heavy booster skirt to the combined thrust of 20 outer engines and 9 center engines.
The fact that complex custom test stands and jigs had already been assembled and installed for Ship 20 and Booster 4 before they were removed or disassembled without use strongly implies that someone at SpaceX – presumably Elon Musk himself – has either decided that those tests are unnecessary or that skipping them is worth the substantial risk. Indeed, for Musk’s subsequent August 15th claim that Ship 20 and Booster 4 could be stacked and ready for flight just “a few weeks” from now to come true, 14-21 days is simply nowhere close to enough time to cryo proof, thrust sim, and static fire both vehicles; integrate the stages; and perform the first true integrate testing of a Starship stack – possibly up to and including some combination of a full-stack cryo proof, wet dress rehearsal, or static fire.
And, as Musk himself notes, that complex ballet of first-of-their-kind rocket prototypes might not even be the long straw for Starship’s orbital launch debut. Technically, short of some kind of major legal intervention, there is actually no way for Starship to launch in the next “few weeks.” In an absolute best-case scenario, the Federal Aviation Administration (FAA) would release a draft environmental review of SpaceX’s orbital Starship launch site today, accept public comments for the required 30 days, instantly clear Starbase with environmental approval within a few days of the public comment window, and then approve Starship’s South Texas orbital launch license as soon as the necessary environmental permissions are in hand.
In other words, the best-case ETA of regulatory approvals for Starship’s first orbital test flight is arguably late September and going off of FAA precedent, that optimistic scenario is also a fairy tale. In reality, a bare minimum of 2-3 months after the FAA releases its draft environmental impact statement is a more realistic best-case scenario for SpaceX. On the opposite end, it’s possible that the FAA will decide that SpaceX needs to complete an entirely new environmental review for its Starbase launch site, easily delaying Starship’s orbital launch debut by 6-12+ months. That doesn’t even account for the potential looming challenges SpaceX might have to surmount to secure an orbital Starship launch license.
Given the challenges SpaceX had in securing even a watered-down suborbital launch license for its medium-altitude Starship flight tests, it’s not out of the question that the FAA could attach some extremely onerous limitations to that license. Ultimately, only time (and the slightest hint of actual movement or urgency at the FAA) will tell and there is arguably nothing that would better apply pressure in the right places than the largest, most powerful, most ambitious rocket ever built sitting – ready for flight – at a brand new launch pad, waiting solely on regulatory approval.
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
