News
SpaceX Starship pop test opens the door for 60,000 foot hop [update]
SpaceX has successfully destroyed a Starship ‘test tank’ for the fourth time, opening the door for the first high-altitude prototype to roll to the launch pad as soon as tomorrow.
The culmination of three nights and more than 20 hours of concerted effort, SpaceX was finally able to fill Starship test tank SN7.1 with several hundred tons of liquid nitrogen before dawn on September 23rd. With just an hour left in the day’s test window, SpaceX closed the tank’s vents, allowing its cryogenic contents to boil into gas and expand with no outlet. At 4:57 am CDT, SN7.1 burst, bringing its lengthy test campaign to a decisive end.
A handful of hours later, new road closure notices revealed SpaceX’s plan to roll Starship SN8 – the first full-size prototype and first ship meant for high-altitude testing – from its Boca Chica factory to the launch site.
Update: All road closures planned for Starship SN8’s roll to the launch pad (Sept 24) and first test campaign (Sept 27-29) have been canceled. Stay tuned for updates on the high-altitude prototype’s test schedule.
Short of new information from SpaceX or CEO Elon Musk, little is known about the results of SN7.1’s lengthy test campaign, but the fact that it survived two nights of nondestructive testing – including the use of hydraulic rams to simulate Raptor thrust – effectively clears Starship SN8 for suborbital testing. Based on a speculative, amateur analysis of the aftermath of SN7.1’s burst test, it can also be tentatively concluded that the tank failed almost exactly where one would expect it to: the in-situ weld attaching the upper tank dome to SN7.1’s steel ring hull.
SN7.1’s forward dome appears to have cleanly sheared off around much of its circumferential weld joint – exactly what one would theoretically expect from a good, uniform weld. Assuming that SN7.1 reached pressures well above 8.5 bar (~125 psi) before it burst, the tank’s final test can likely be deemed a success.

The very same day SpaceX kicked off what would become Starship SN7.1’s last burst test attempt, teams worked to install functional flaps on a full-scale Starship prototype (SN8) for the first time ever. Effectively answering the question of whether SpaceX would fully outfit the ship with a nosecone and flaps before its first acceptance tests, SN7.1’s successful pop was followed by road closure notices for SN8’s transport to the launch pad around dawn on September 24th and cryptic “SN8 Testing” as early as September 27th.
As of September 23rd, SN8’s twin aft flaps – large aerodynamic control surfaces meant to stabilize free-falling Starships – have been fully installed alongside ‘aerocovers’ that will protect each flap’s control mechanisms. The only hardware Starship SN8 is missing is a ~20m (~60 ft) tall nosecone, two smaller forward flaps, and the plumbing needed to access a smaller liquid oxygen “header” tank located in the tip of said nose.
At the moment, SpaceX has installed one Starship nosecone prototype atop five unpressurized rings – creating a full nosecone stack. That particular prototype has no liquid oxygen header tank, however, meaning that SpaceX would likely need at least a day or two to weld one of the noses with a header tank atop one of several finished five-ring sections. In other words, to transport SN8 to the pad tomorrow, there’s almost no chance that SpaceX will have time to finish and install a proper nosecone on the prototype, meaning that the company has chosen to test the Starship before that milestone.


Doing so should reduce any inconvenience caused by vehicle failure in the event that Starship SN8’s acceptance test campaign doesn’t go as planned. In hindsight, the inclusion of Starship SN8’s aft flaps and aerocovers during the ship’s first major tests was likely a necessity, given that almost half of each flap and its support structure is installed directly to the skin of its liquid oxygen tank. Theoretically, when chilled to the temperature of liquid nitrogen or oxygen, the diameter of the stainless steel rings Starship SN8 is built out of could shrink by as much as 0.3% (~20 mm or ~0.8 in).
Only half of Starship SN8’s aft flaps will be directly subject to that tank contraction, resulting in a relatively complex environment for such a large, high-stress mechanical system. As such, testing flap actuation under cryogenic loads is likely a critical part of SN8’s cryogenic proof test, otherwise meant to demonstrate the structural integrity and functionality of Starship’s propellant tanks. If SN8 rolls to SpaceX’s launch facilities on schedule, the Starship’s first cryogenic proof test could begin as early as 9pm CDT (UTC-5) on Sunday, September 27th.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
News
Tesla Robotaxi gets sweeping but polarizing change
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.
News
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
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
Musk’s massive Terafab project will get final location soon
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.”

