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.
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’
