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.
A new report from Reuters claims that a transport authority in Sweden is pushing back against the approval of Tesla’s Full Self-Driving suite because it will travel over speed limits.
The report says the Swedish Transport Administration (TRV) recommends the European Union votes against FSD’s approval. TRV believes it should not be approved until Tesla disables FSD’s ability to speed.
TRV sent a letter to the European Union’s Technical Committee on Motor Vehicles (TCMV), which is set to meet on June 30 to discuss the potential approval of the Tesla FSD suite in the country. Tesla, which has received various approvals in Europe over the past two months, has not provided a comment.
Teslas operating on FSD do travel over the speed limit, depending on the Speed Profile that is chosen. Drivers have the ability to disengage FSD at any point; Tesla specifically states that those supervising the suite are responsible for its actions.
Let’s cut to the chase: humans operating any vehicle speed almost daily in the United States. Realistically, speed limits in the U.S. are more frequently treated as speed minimums. However, other countries are different, and driving behaviors are less aggressive.
TRV believes that “allowing automated systems to systematically exceed legal speed limits…risks undermining both the legal framework and the expected safety benefits of vehicle automation,” the report stated. It’s surprising that Tesla has not received this claim from other countries previously.
This could be a good argument to bring Max Speed back, the setting that previously allowed the driver to choose the absolute fastest the car would travel.
This would still put the responsibility of supervision in the hands of the driver. It would allow the driver to choose whether the car would travel over the speed limit or not, acknowledging that they set the speed, and if they get pulled over, there would be no ability to argue it.
However, it does not seem as if this is something Tesla will do, especially considering many U.S. drivers have requested the feature in an effort to eliminate speeding or at least tone it down. The company has not shown any interest in bringing it back.
Tesla has approvals for FSD in Europe in Estonia, Lithuania, Denmark, the Netherlands, and Belgium.
Tesla is going to let you guide Full Self-Driving with Grok in 3 months, CEO Elon Musk confirmed on X.
The response from Musk, which revealed Tesla plans to allow drivers to effectively control the car and its navigation more explicitly using Grok, puts the feature for about September.
A Tesla owner said that Full Self-Driving is great, but owners should be able to “converse with Grok like we can with an Uber driver.” She then used examples like, “Grok, turn right here,” and “Drop us off right here, we’ll walk due to traffic,” and finally,” Drop at entrance first, then park far away.”
Coincidentally, the final piece of dialogue would also mean features like Banish are potentially on the way soon.
This functionality will be there in about 3 months or so
— Elon Musk (@elonmusk) June 18, 2026
Banish is also referred to as “Reverse Summon,” and would enable the car to self-park while dropping occupants off at their destination.
This would be a great way to improve the overall experience while supervising FSD. Navigation is already a major painpoint that many owners complain about. Manual overrides when a maneuver is requested or canceled (like using the turn signal stalk to override a navigation route), do not always work.
The feature could be especially useful in street parking scenarios in a city, where spots are sometimes tough to come by. Many of us who grab dinner in a more populated area will park a street or two over from wherever we’re going, because sometimes you know that’s the best you will get. If a driver using FSD could say, “Hey Grok, turn right here on Queen St. and park in that open spot on the right,” it could save a lot of confusion FSD might have on its own.
Musk teased that a similar feature was “coming” back in February:
Tesla Full Self-Driving set to get an awesome new feature, Elon Musk says
It is certainly surprising that Tesla is doing it at this point. The company’s more recent moves have been more evident of taking control and inputs away from humans and putting them in the AI’s hands more frequently. The biggest example of this was taking away Max Speed in AI4 cars, giving us Speed Profiles, and not having any input on the fastest speed the car will travel.
Of course, giving navigation preferences to Grok is availble already in Teslas, but not at the drop of a hat. Instead, you can suggest a certain route at the beginning of your drive.
Here’s an example of that from December:
🚨🏈 I am taking my parents and Fiancee to the @Ravens game next weekend and asked @Grok to help me route my @Tesla through a specific neighborhood to reach the correct Lot we will park in.
This is a great example of the new @grok nav integration with the Tesla Holiday Update: pic.twitter.com/rPp4I7q8Yv
— TESLARATI (@Teslarati) December 13, 2025
Finally, the original post that Musk responded to mentioned a parking preference after dropping off the occupants, which describes the Banish feature that Tesla has teased for years.
We’re not sure if Musk was responding more to the ability to guide the car with Grok, or whether he also was including Banish in the three-month prediction timeframe.
A close-up image of a Cybercab engineering vehicle in Peabody, Massachusetts, reveals a compact triangular side repeater camera housing equipped with an integrated washer mechanism.
This seemingly small hardware addition could prove to be one of the most critical components for achieving reliable, unsupervised Full Self-Driving (FSD) — not just for the dedicated Robotaxi but potentially for existing AI4-equipped vehicles as well.
The washer system’s importance cannot be overstated in Tesla’s vision-only autonomy approach. Cameras are the sole sensory input for the neural networks powering FSD, constantly interpreting the environment for safe navigation. In real-world conditions, however, lenses quickly accumulate rain, snow, mud, dust, or road spray.
Many of us Tesla owners, especially those who deal with any sort of winter weather at all, know the all-too-common alert that pops up when cameras are obstructed:
Even brief obstructions can drop perception confidence, trigger safety disengagements, or force the vehicle to pull over, although these are relatively rare. Instead, most of the time, the camera will need a wipe from the owner next time they stop the car.
But unlike human drivers who can manually clear their view, a Robotaxi operating 24/7 without a steering wheel or mirrors must maintain pristine vision autonomously. The Cybercab’s side repeater washer delivers targeted cleaning bursts precisely where needed for merging, lane changes, and blind-spot monitoring — functions that demand uninterrupted visibility from the external cameras:
And this is how the side camera and washer look like on a Cybercab. This is from an Engineering vehicle in Peabody MA. pic.twitter.com/Re8VknpmLM
— Tobias Goebel (Unsupervised) (@tpgoebel) June 17, 2026
This hardware directly tackles a known pain point in current FSD deployments. Owners frequently report camera-related alerts during inclement weather, which is understandable, but needs to be solved for a true autonomous experience.
For a production Robotaxi fleet aiming for high utilization and minimal downtime, robust washer systems represent a foundational reliability upgrade; essentially, they’re a must-have. Early sightings suggest the design may extend to rear cameras as well, creating a comprehensive cleaning architecture that keeps the entire vision suite operational in harsh environments.
Without it, even the most advanced neural nets struggle when their “eyes” are compromised.
What Does This Mean for AI4 Cars?
This Cybercab detail raises timely questions for AI4 cars already on the road. While Hardware 4 delivers superior compute and camera resolution compared to earlier versions, production models typically lack dedicated side and rear washers. Tesla has included them on Model Y robotaxis that it is using in the fleet:
Tesla Robotaxi has a highly-requested hardware feature not available on typical Model Ys
As Tesla refines unsupervised FSD for broader release, the gap in environmental resilience becomes evident. Software improvements can help mitigate issues, but they cannot fully replace physical cleaning in heavy rain or muddy conditions. Analysts and owners increasingly speculate that AI4 vehicles may eventually require similar washer retrofits — or a future AI4.5 variant — to match the Cybercab’s all-weather readiness and support the same level of autonomy.
As testing progresses, the Cybercab’s washer mechanism highlights Tesla’s pragmatic focus on real-world robustness. It may well become the hardware piece that determines how quickly and reliably FSD scales from prototypes to everyday vehicles.
Tesla faces Full Self-Driving pushback in EU over ‘speeding’
Tesla teases greater Grok FSD integration and ‘Banish’ feature ‘in about 3 months’
