News
SpaceX’s Starbase environmental review is inches from the finish line
Update: Just two days after the FAA’s latest delay announcement, an online portal documenting SpaceX’s Starbase environmental assessment progress has been updated to show that the last step requiring “interagency consultations” was completed on June 2nd.
In theory, that means that to successfully complete its Programmatic Environmental Assessment (PEA) for orbital Starship launches, SpaceX merely needs to incorporate all recommendations, requirements, or mitigations added during the interagency review process into one final draft and presumably secure the approval of all relevant stakeholders one last time. Once those documents are complete, approved, and published, all Starbase will need to begin orbital Starship test flights is an FAA launch license.
Securing that launch license is its own can of worms with plenty of unique challenges, but it’s highly unlikely that SpaceX and the FAA won’t be able to come to some kind of agreement allowing the company to begin those test flights within a month or two of receiving a good environmental review. According to the FAA, the final results of the Starbase PEA are scheduled to be released on June 13th.
The US Federal Aviation Administration says that its environmental review of SpaceX’s plan to conduct orbital Starship launches out of South Texas has been delayed for the fifth time in five months.
However, despite the chronic delays and the FAA’s odd decision to announce a new delay every month instead of simply acknowledging that it doesn’t know when the process will be finished, there are now even more reasons to expect a positive outcome.
Even though there were attempts to spin the new information into something negative, a document acquired through the Freedom Of Information Act (FOIA) by Bloomberg revealed that the US Fish and Wildlife Service (FWS) had decided to approve its portion of the Starbase environmental review. Their only condition: that SpaceX implement a few small mitigation measures, “including contracting with a qualified biologist to conduct monitoring of vegetation and birds, operating an employee shuttle between the launch facility site and nearby town of Brownsville, reducing vehicle traffic, and adjusting lights to minimize the impact on sea turtles.” Bloomberg chose not to publish the documents it received through the FOIA process.
In the same set of documents, the FWS also revealed that SpaceX has removed a request for permission to build a small desalination plant, a natural gas production and liquefaction plant, and a natural gas power plant at or near Starbase’s launch site from Starbase’s first Programmatic Environmental Assessment (PEA). That change comes as little surprise. In fact, SpaceX’s decision to pursue a “programmatic” assessment instead of a more common standalone assessment means that the company will be able to pursue additions to a basic Starbase environmental approval without having to rebuild the foundation each time.
In this case, a “basic approval” would mean the ability to conduct at least a few orbital Starship launches per year. Once that foundation is secured, SpaceX should be able to tier new environmental assessments on top of it and pursue permission for a desalination plant, natural gas production, more annual launches, or any other additions that might benefit Starbase. The simpler the foundation, the harder it should be for environmental stakeholders and agencies to protest or prevent SpaceX from receiving a good outcome.
“The FAA now plans to release the Final PEA on June 13, 2022 to account for ongoing interagency consultations concerning Section 4(f) of the Department of Transportation Act. All other consultations and analysis have been completed at this time.”
Another cause for optimism: after four delays of one or two months, the FAA’s latest delay announcement only pushes the conclusion of the review from May 31st to June 13th. Additionally, the FAA confirmed that only one small component of the entire review remains unfinished. Every other major component has been completed successfully and will likely result in a Finding Of No Significant Impact (FONSI) or Mitigated FONSI that would greenlight the environmental side of conducting orbital Starship launches out of Boca Chica, Texas.
When the draft PEA was first published, the FAA noted several points of contention over Section 4(f) compliance, which is designed to “protect significant publicly owned public parks, recreation areas, and wildlife and waterfowl refuges, as well as significant historic sites, whether they are publicly or privately owned.” At the time, the main problem was SpaceX’s request to close the public Boca Chica Beach and the only highway to it for up to 500 hours (~42 days), as well as a contingency that would allow for another 300 hours of closures to safely respond to emergencies.
Thanks to an even more in-depth environmental impact statement (EIS) completed in 2014 for a Falcon 9 and Falcon Heavy launch pad where Starship’s launch site now stands, we know that SpaceX has already met Section 4(f) demands with a plan for up to 180 hours of road closures per year. In the absolute worst-case scenario, SpaceX should be able to drastically reduce its road closure request to satisfy the Department of Transportation. Subsisting on roughly 20-30 days of closures per year would undoubtedly maim Starbase’s utility but it would at least allow SpaceX to conduct a few basic orbital test flights and some limited ground testing while it rapidly redirects most of its effort to finishing alternative Starship production and launch facilities in Florida.
Regardless, it’s now quite likely that SpaceX’s Starbase environmental review will finally be over by the end of June, freeing up the FAA and SpaceX to focus fully on the launch license side of the equation. Meanwhile, SpaceX still has weeks or even months of work ahead of it to prepare a Starship and Super Heavy pair for their first orbital launch attempt, so (for now) there is no risk of the company being forced to sit around and wait for the gears of bureaucracy to turn.
Tesla has extended its Bay Area ride-hailing service to include pickups and drop-offs at San Francisco International Airport (SFO). The update, shared via the company’s official channels on July 21, allows users in the region to request rides directly to and from one of California’s busiest airports.
The expansion builds on Tesla’s secured limousine permit for SFO operations. Public records show the permit became effective March 20, 2026, and remains active through January 31, 2027. Tesla vehicles operating the service now display authorized limousine permits issued by the City and County of San Francisco.
Our Bay Area rideshare service now goes to SFO ✈️
— Tesla AI (@Tesla_AI) July 21, 2026
Tesla’s ride-hailing program in California relies on Model Y vehicles equipped with Full Self-Driving (Supervised) technology. Human safety drivers remain present in compliance with state regulations, distinguishing the service from fully driverless operations.
The Bay Area geofence covers a broad area spanning north of San Francisco to south of San Jose, offering extensive connectivity across the region.
UPDATE: Elon Musk reveals why Tesla didn’t say ‘Robotaxi’ upon California launch
This SFO addition follows earlier progress at other Bay Area airports. Tesla previously expanded service to San Jose Mineta International Airport (SJC) in late 2025. The company had engaged with SFO, SJC, and Oakland International Airport officials as early as September 2025 to secure necessary approvals for passenger transport.
The service provides a new option for travelers seeking electric, app-based transportation integrated with Tesla’s ecosystem. Rides are booked through Tesla’s dedicated ride-hailing application, which handles matching, routing, and payments. Pricing follows standard ride-hailing models, with potential adjustments based on distance, time, and demand.
Tesla’s California ride-hailing program launched in July 2025 with an initial invite-only rollout in the Bay Area. It started alongside operations in Austin, Texas, marking the company’s second major U.S. market.
The Bay Area remains a primary focus in California, with service centered on high-demand corridors connecting residential, commercial, and now major transportation hubs. This latest airport integration represents a practical step in Tesla’s broader mobility ambitions within the state.
Tesla has officially revealed its 2026 Summer Update, which comes with a variety of crazy new features, including Navigation fixes that owners have been wanting for months.
Tesla routinely releases a larger update with the Spring, Summer, Fall, and Winter updates, where it ships a variety of new features, bug fixes, and other additions to customer cars.
The 2026 Spring Update featured things like “Hey Grok” voice assistance, a redesigned self-driving app, Unreal Engine visual upgrades, and more.
🚨 TESLA’S SUMMER UPDATE FOR 2026 IS HERE:
Featuring:
✅ Self-Driving Stats in Mobile App
✅ Caraoke with Scoring
✅ Automatic Navigation
✅ Preferred Routes
✅ Set Arrival Energy from Mobile App
✅ Send Custom Wraps from Mobile App
✅ Rear Display Lock
✅ Other Improvements
🔌… https://t.co/C9IW3egEhH
— TESLARATI (@Teslarati) July 21, 2026
Tesla’s Summer Release has about ten new features; we’ll show you each and detail them below:
New Grok Voice Commands
“Grok can now make phone calls, search and play music, adjust climate, open the glovebox, and answer questions about your Tesla.”
Self-Driving Stats in Mobile App
“View and share self-driving stats from the mobile app.”
Caraoke With Scoring
“Caraoke now scores your singing while in Park. High scores are saved to your Tesla profile.”
Automatic Navigation
“Automatic Navigation now adapts to your routine.
In addition to Home, Work, and upcoming calendar events, your vehicle can now suggest and route to places you visit regularly – like a school drop-off on the way to work, or the gym on the way home.”
Preferred Routes
“For a more personalized experience, navigation now prioritizes routes that you’ve taken before”
Set Arrival Energy from Mobile App
“Set your desired Arrival Energy from your phone.”
Send Custom Wraps from Mobile App
“Skip the USB drive and upload a custom wrap of your car from the mobile app. Instructions for creating a custom wrap here: https://github.com/teslamotors/custom-wraps.”
Rear Display Lock
“Kids can watch content on the rear screen, but only the front row can control it through the rear screen app.”
Other Improvements
- Find Superchargers by name when searching for a destination
- Add Apple Music songs to queue from search and artist page
- Set your preferred zoom level for the Self-Driving visualization
- Intro animations for new Model 3 and Y
Tesla’s reason for Starlink integration on Cybercab might surprise you, as the company’s Head of AI, Ashok Elluswamy, finally shed some light on the reason they are putting a satellite internet terminal on its ride-hailing-geared vehicle.
On Monday, Tesla officially confirmed that it would integrate Starlink V5 terminals into Cybercab vehicles, something many Tesla fans had figured the company would do, as the vehicle is primarily geared toward giving rides without any passenger intervention.
Starlink V5 directly integrated in Cybercab pic.twitter.com/FxzTtzjB6I
— Tesla (@Tesla) July 20, 2026
The ability to access the internet would allow riders to work or play in the car with their devices. It seemed like a more-than-reasonable feature to add to the Cybercab, which made its way off the production lines for the first time earlier this year.
Tesla reveals first vehicle model to receive Starlink integration
However, the move is not for the rider, as Elluswamy confirmed on Monday night. Instead, it’s actually for Tesla to be able to have a constant connection to the cars in the Robotaxi fleet so it can troubleshoot issues, contact riders, or resolve other issues.
Elluswamy said:
“It is still not required for safe operation of the vehicle. Connectivity is primarily meant for navigation, customer service and, in general, fleet management.”
It is still not required for safe operation of the vehicle. Connectivity is primarily meant for navigation, customer service and, in general, fleet management.
— Ashok Elluswamy (@aelluswamy) July 20, 2026
Many initially assumed the option of constant connectivity would be enabled on the Cybercab for passenger entertainment or work. With the Cybercab, passengers won’t be doing anything but enjoying the ride, so it seemed more than logical that they would be hanging out with Starlink internet access as an amenity.
However, Tesla’s primary concern with Robotaxi is safety, and nailing these first unsupervised rides is a crucial step to setting a good narrative on how effective driverless transportation can be.
Being able to get in touch with passengers or a vehicle if something is wrong is a crucial part of the overall experience, and preventative measures are being taken by Tesla to ensure a smooth process, even in the worst-case.
Tesla expands ridesharing service in California to new hotspot
Tesla reveals 2026 Summer Update with crazy fixes to Nav and more
