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.
Tesla has started rolling out a broader change to the ride experience for its Robotaxi fleet by silencing turn signals, but the change is certainly polarizing.
Tesla has generally made it clear that its purpose-built ride-hailing platform, Robotaxi, will cater to the rider in nearly every way possible. This includes having climate preferences, music, and other personal settings loaded up in the car as the rider enters.
But Tesla is taking it a step further by muting turn signal chimes altogether, a change that appears to be a way to make the ride more peaceful:
Tesla has finally turned off the blinker/turn signal noises in their Model Y Robotaxis.
This is a small update, but will definitely be noticeable for riders. It didn’t really make much sense to leave the turn signal sound on when it’s Unsupervised. pic.twitter.com/ITwx60PAMO
— Sawyer Merritt (@SawyerMerritt) July 27, 2026
However, there are a handful of people who are not thrilled about this change. Turn signals are a conditioned part of the human mind for those who ride in a car regularly.
Taking a turn without one feels strange and odd, and not hearing it click while activated could set off some alarms for riders, who might use the noise as confirmation that other drivers know of their intention to turn.
I kind of like it being on, threw me off when riding with Zoox who has had it disabled
— Dan Burkland (@DBurkland) July 27, 2026
Turn signal noises are still audible in customer cars, so if you use FSD in your personal vehicle, you will still hear the turn signal.
The move is certainly one that is unique, but not one that separates it from other ride-sharing services. In a normal car, the clicking sound confirms to the driver that the blinker is active. In a fully driverless Robotaxi, that feedback serves no purpose for passengers, other than peace of mind.
Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.
Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.
“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.
Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry
Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.
The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.
In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.
However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.
Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.
The sheer scale of TERAFAB is going to be insane.
Elon said it wouldn’t be suitable for anywhere on Giga Texas property because it’s too big:
“We couldn’t possibly fit the Terafab on the GigaTexas campus. It will be far bigger than everything else combined there.
Several… pic.twitter.com/79GbhNNuf4
— TESLARATI (@Teslarati) March 23, 2026
Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.
“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”
He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”
Tesla silences Robotaxi turn signals in sweeping but polarizing change
Tesla claims supplier is holding Cybertruck production hostage
