News
SpaceX’s Starbase environmental review suffers third delay
The Federal Aviation Administration (FAA) has announced that the completion of a crucial ‘environmental assessment’ SpaceX needs to begin orbital-class Starship launch attempts out of South Texas has been delayed for the third time.
Official known as a programmatic environmental assessment or PEA, the FAA says it started the process in late June 2021 with the goal of verifying that SpaceX’s Starbase orbital launch site (OLS) was mostly benign before the end of 2021. Compared to a regular EA, the programmatic nature of SpaceX’s Starbase review would theoretically allow the company to start small and gradually expand and add new facilities and capabilities without having to restart the arduous review process for each change.
Along those lines, SpaceX’s first draft PEA requested permission for no more than five full-stack Starship launches per year compared to the maximum of 12 Falcon 9 launches or nine Falcon 9 and three Falcon Heavy launches out of Boca Chica that SpaceX had already received permission for from the FAA in 2014.
Unfortunately, even at the time that the start of the process was announced, completing a full PEA in half a year was already unbelievably optimistic. No comparable review, of which there are effectively none, has been completed anywhere close to that quickly. In the face of substantial local opposition, like in the case of Georgia’s Camden Spaceport, even an FAA environmental review for a relatively small rocket launch facility can make little progress after years of tooth-and-nail fighting.
However, the best possible comparison has always been SpaceX’s own environmental assessment for an almost identical orbital-class Starship launch site at Florida’s Kennedy Space Center. Despite the fact that no untouched ground would be broken and even with the apparent might of NASA behind it, it took the FAA and SpaceX about a full year to complete a Pad 39A EA for up to 24 Starship launches per year. As such, the idea that the FAA would be able to complete a PEA for Boca Chica Starship launches in six months was always almost unimaginable.
It should come as no surprise, then, that nine months after SpaceX and the FAA began their Starbase PEA, they appear to be only marginally closer to completing the review. Days before the original December 31st, 2021 deadline, the FAA announced a delay to February 28th, 2022. On February 14th, the FAA announced a second delay to March 28th. Most recently, on March 25th, the FAA announced a third delay to April 29th.
Put simply, the FAA is effectively saying that it is actually further away from completing SpaceX’s South Texas Starship PEA than it was in December 2021. The extraordinarily opaque nature of the process also means that anyone outside of the loop or without internal sources is left to simply guess what is causing those delays or why the FAA keeps pushing the goalposts back just one or two months at a time when it’s unclear that anyone can actually predict when the process will be completed.
Without journalists filing Freedom of Information Act (FOIA) requests, the full extent of public knowledge about what is causing those delays would be the FAA’s scant few statements on the process. The most valuable information provided thus far is that the FAA is “reviewing the Final PEA,” which does seem to imply some degree of progress. Nonetheless, the agency still included a boilerplate statement noting that it’s “completing consultation and coordination with agencies at the local, State, and Federal level,” making it hard to actually say if any progress has been made. In February 2022, the FAA said it was “continuing consultation and coordination with other agencies.”
In December 2021, the FAA stated that it was “continuing consultation and coordination with other agencies at the local, State, and Federal level” while “SpaceX continues to prepare the Final PEA for…FAA review and acceptance.” By using such vague and unspecific language, the FAA makes what little it does say virtually impossible to parse and barely better than nothing. Solely thanks to documents secured through FOIA, we know that the FAA itself may not actually be to blame for most or all of the PEA’s four months of delays.
Instead, the US Department of the Interior (DOI), Fish and Wildlife Services (FWS), and National Park Services (NPS) may be partially responsible through their required coordination with the FAA, which they appear to be taking full advantage of to exert some form of control over the outcome. Bureaucrats are being bureaucratic, in other words.
Outside of email chains and boardrooms, however, it’s no longer clear that completing the PEA and securing an FAA launch license are the limiting factor for the first orbital Starship test flights. SpaceX CEO Elon Musk recently announced that SpaceX is changing the prototypes assigned to the first full-stack launch – likely to Booster 7 and Ship 24. Super Heavy B7 has yet to begin any kind of testing and Starship S24 is still in several pieces, so it’s safe to say that SpaceX’s new pair are months of concerted testing away from launch readiness.
If anything goes wrong during those tests, any significant design issues are discovered, or any damage is caused, it’s entirely possible that what Elon Musk says could take as few as two months will actually take more like four to six. Only time will tell. For now, the FAA likely has a few months before Starship’s South Texas PEA and full-stack launch license truly become the limiting factor for the rocket’s first orbital launch attempt.
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
