News
SpaceX a big step closer to orbital Starship launches after passing FAA environmental review
SpaceX has secured environmental approval from the FAA and relevant federal, state, and local stakeholders to conduct orbital Starship launches on the South Texas coast.
After a relatively normal 12 months of work and half a dozen poorly communicated delays, the FAA has ultimately issued SpaceX an extremely favorable “Mitigated Finding of No Significant Impact” or Mitigated FONSI for its plans to conduct a very limited number of orbital Starship launches per year out of Boca Chica, Texas. With the receipt of that final programmatic environmental assessment (PEA), SpaceX has arguably hurdled the most difficult regulatory barrier for Texas orbital Starship launches and secured itself a foundation upon which it should be able to attempt to expand the scope of Starbase’s long-term utility.
To secure that favorable result, however, SpaceX ultimately agreed to dozens upon dozens of “mitigations” that will take a significant amount of work to complete and maintain in order to partially alleviate some of the launch site’s environmental impact. It’s also far from the last regulatory hurdle standing between SpaceX and orbital Starship launches.
In many ways, Starbase’s Final PEA is a bit simpler than what SpaceX initially requested in its September 2021 draft. As previously discussed, it was already known that SpaceX had withdrawn initial plans to build its own dedicated natural gas power plant, desalination plant, and natural gas refinery and liquefaction facilities at or near the launch site before the draft was finalized. The Final PEA goes a bit further, simplifying SpaceX’s initial request for two “phases” of annual Starship launch operations and settling on a single “operational phase” that allows up to five suborbital and five orbital Starship launches per year.
However, aside from the already expected removal of onsite methane fuel production and all associated facilities, the rest of the Final PEA appears to be surprisingly close – if not outright identical – to SpaceX’s Starbase Draft PEA. Crucially, SpaceX was not forced to reduce the number of permitted orbital launches, suborbital launches, or ship/booster static fire tests it originally pursued. While a maximum of five orbital launches will severely limit Starbase’s utility outside of early flight testing, it’s still a big improvement over a compromise for 1-4 annual launches.
Perhaps even more notably, the Final PEA also includes permission for up to 500 hours of highway closures for nominal operations and up to 300 hours of closures for emergency anomaly response per year – exactly what SpaceX requested in its Draft PEA. In 2014, SpaceX completed an even more thorough environmental impact statement (EIS) for Falcon rocket launches out of Boca Chica and received approval for no more than 180 hours of annual closures – a restriction that could have made Starbase virtually unusable as a hub for Starship development.
Of the dozens of mitigations SpaceX will have to implement to conduct Starship launches under its new Starbase PEA, a majority appear to be normal and reasonable. Most focus on specific aspects of things already discussed, like protecting turtles (lighting, beach cleanup, education, nest scouting and monitoring, etc.), safeguarding other protected species, respecting impacted areas of historical importance; ensuring that road closures avoid certain holidays and periods to limit Starbase’s impact on local use of public parks and beaches; and other common-sense extensions of existing rules and regulations. In a few cases, SpaceX has even agreed to deploy solar-powered Starlink internet terminals to enable “enhanced satellite monitoring” of wildlife for the US Fish and Wildlife Service and Peregrine Fund.
Others are oddly specific and read a bit more like local and state agencies taking advantage of their leverage to get SpaceX to manage and pay for basic infrastructure maintenance and improvement that any functional government should already be doing. The lengthy list of odd “mitigations” includes the following:
- Quarterly beach and highway cleanups
- Construct at least one highway wildlife crossing
- Construct a wildlife viewing platform along Highway 4
- Complete and maintain traffic control fencing demarcating the boundaries of TPWD land along said public highway
- $5,000 per year to “enhance” the Texas Parks and Wildlife Department’s (TPWD) fishing “Tackle Loaner Program”
- Prepare a history report on any events and activities of the Mexican War and Civil War that took place in all affected areas of historical importance
- Fund the development of five signs explaining the “history and significance” of those areas
- “[Replicate and install] the missing stars and wreaths on the Palmetto Pilings Historical Marker”
Ultimately, the Final PEA SpaceX received is an extremely positive outcome, and there should be little doubt that SpaceX will complete all mitigations requested of it and help improve aspects of Boca Chica, Texas as a result. Up next, SpaceX will need to secure an orbital Starship launch license from the FAA by demonstrating, to the agency’s satisfaction, that it meets “safety, risk, and financial responsibility requirements” in addition to all environmental requirements. The company has already begun that process with the FAA, but it could still take weeks or months after the Final PEA to secure an operator license or experimental permit. Any such license or permit will be conditional upon the completion of all mitigation requirements established by the PEA.
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
