News
SpaceX’s Starbase environmental review delayed another month
The FAA says that it will take at least another month to complete a crucial environmental review of orbital Starship launches from SpaceX’s South Texas Starbase facilities.
The agency now expects that Starbase’s Programmatic Environmental Assessment (PEA) will be completed no earlier than March 28th, 2022, delaying the process at least another four weeks on top of an initial delay from December 31st, 2021 to February 28th, 2022. However, while the FAA gained some infamy for repeatedly delay SpaceX Starbase launch operations in late 2020 and early 2021, there is growing evidence that other US government agencies – not the FAA itself – are primarily responsible for most of the review’s delays.
Namely, information acquired through a Freedom Of Information Act (FOIA) request indicates that US Departments of Fish and Wildlife Services (FWS) and National Parks Services (NPS) are the primary sources of recent delays and the only real sources of discord this late in the process. As an example, as of the end of October 2021, the NPS had a list of at least 31 comments on SpaceX’s Starbase Draft PEA, each of which would have required a detailed response and additional back-and-forth to refine each response. The critiques and requests cover virtually every aspect of orbital Starship launches from Starbase, including FAA launch license details, recent SpaceX land acquisitions, impacts on a local Civil War battlefield landmark, pad lighting, air quality, noise, paint colors, road closures, Raptor thrust, contingency plans, and more.
Meanwhile, in a general review, the Department of the Interior (DOI) – speaking on behalf of the FWS and NPS – raised concerns about “launch site blast area hazards, closure of FWS and NPS lands, environmental justice (EJ) concerns, NHPA Section 106 and 110(f), [endangered] species, air quality emissions, and climate change impacts. It’s difficult to say how many of the concerns raised are actually serious. For example, the point repeatedly made by the DOI, FWS, and NPS is that hypothetical emissions from a natural gas power plant SpaceX proposed to build in its Draft PEA would violate EPA rules.
However, since that draft was published, there is growing evidence that SpaceX is behind a brand new power distribution line set to connect Boca Chica and Brownsville, Texas. The new lines appear to be sized to provide Starbase with enough power to entirely preclude the need for the construction of any dedicated power plants on site. Only a backup power source of some kind would be necessary. Assuming SpaceX is actually behind the development, it’s difficult to believe that the company hasn’t communicated that change of plans to the FAA and other Starbase PEA stakeholders.
As another example, the Fish and Wildlife Services’ own list of complaints includes the bizarre request that SpaceX increase its estimate for the number of failures that will occur during future Starship testing fivefold from 10% (already an extremely pessimistic figure) to 50% because “[nine] of 16 tests or hops that have occurred [at Starbase]…resulted in some type of anomaly with fire or debris.” While true that many of SpaceX’s developmental Starship tests have resulted in major failures or explosions, the FWS appears to fundamentally misunderstand the purpose of those failures and SpaceX’s approach to development, which is to learn from failures and prevent their reoccurrence. Something would have to go terribly wrong for half of all future Starship ground and flight tests to result in failure when SpaceX’s goal is to develop Starship into a reliable launch vehicle – not to futilely test prototypes forever.
Ultimately, it remains to be seen if SpaceX and the FAA will be able to secure the DOI, FWS, and NPS approvals required to finish the Starbase PEA. If the parties can’t come to some kind of agreement, SpaceX may be forced to effectively restart the environmental review process from scratch and pursue a more thorough Environmental Impact Statement (EIS). Completing an EIS could easily take years, potentially forcing SpaceX to give up on South Texas as a site for regular orbital Starship launches.
While CEO Elon Musk recently implied that SpaceX would never abandon Starbase and might use the site as a sort of dedicated research and development facility, it’s difficult to believe that the cost of operating and maintaining an entire Starship factory and orbital launch site would make sense from a programmatic or financial perspective given that SpaceX appears likely to build a Florida Starbase for East Coast Starship launches. SpaceX already has full environmental approval to launch 24 Starships per year from its Kennedy Space Center Pad 39A facilities.
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 launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.
Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
