News
SpaceX set to finish three Starship prototypes in the same month
SpaceX appears to be on track to complete its third Starship prototype in a month just days after the company finished testing a new steel tank and at the same time as it prepares to roll another full-scale ship to the launch pad.
Postponed by several weeks after the (fleeting) success of the Starship serial number 4 (SN4) prototype, violently destroyed by a minor testing mishap on May 29th, SpaceX’s fifth full-scale Starship tank section (SN5) could roll to an adjacent testing facility at any point in the next few days. In fact, SN4’s successor has likely been ready to begin tank proof and static fire testing for several weeks since it was stacked to its full height on May 12th. SN4 rolled to the launch pad on April 23rd and remained SpaceX’s top Starship priority until its demise more than a month later.
As it turns out, the explosion that destroyed the ship also launched a ~25 metric ton (~55,000 lb) counterweight installed a few days prior some 100m (300+ ft) into the air, where it proceeded to fall back to earth and obliterate the steel mount Starship SN4 sat on. The loss of that pad hardware necessitated its own several-week delay but SpaceX appears to be nearly done installing and outfitting replacements as of June 18th – an incredible turnaround given the scale and complexity of everything involved. Of course, the whole purpose of those rapid repairs is to get back to the business of testing Starships as quickly as possible.
SN5
Initially expected as early as 8am local on June 17th, Starship SN5’s trip to the launch pad has been a long time coming. Completed around May 20th after approximately a month of concerted effort, the ~30m (100 ft) tall tank departed SpaceX’s Vehicle Assembly Building (VAB) for the first on June 13th, although it was quickly moved back inside as technicians simultaneously worked to complete Starship SN6.
Previously scheduled to become the first Starship to reach its full height with the installation of a functional nosecone, SN5 will likely pick up where SN4 left off, instead. That process will effectively be no different, albeit sans nosecone, starting with ambient and cryogenic proof (pressure) tests and eventually moving to one or several static fires with either one or three Raptor engines. Testing the quick disconnect umbilical port that caused SN4’s demise will also likely be a priority. If all goes according to plan in that first week or two of tests, SpaceX may finally be ready to launch a full-scale Starship prototype for the first time, performing a 150m (~500 ft) hop test with SN5.
However, since CEO Elon Musk first discussed plans for an initial 150m hop test, SpaceX received a surprise suborbital launch license from the FAA, rather than the limited experimental permit most expected. That license effectively allows SpaceX to perform an unlimited number of Starship tests as long as the trajectory follows the administration’s strict safety guidelines and remains suborbital. Unless SpaceX’s ~150m target was based in some technical limitation, the sky is quite literally the limit for a more ambitious flight debut if the company believes Starship SN5 can handle it.
SN6
In the event that Starship SN5 follows its predecessor into a less early (but still early) grave, SpaceX thankfully won’t have to wait long at all to continue its hardware-rich test program. When Starship SN5 first departed the VAB on June 13th, it did so to give SpaceX room to finish Starship SN6, placing its aft engine section on a stand inside the building and stacking the upper two-thirds of the ship’s tank on top.
Several days to a week or more of internal and external work remain to fully mate the two Starship SN6 sections, but the vast majority of its assembly is now behind SpaceX. SpaceX continues to refine its methods with each successive prototype, gradually producing Starships that are getting closer and closer to the ideal finished product. There’s a chance that, unlike Starship SN4, SN5 can be modified with the installation of a nosecone and flaps to support more ambitious 2-20 km (~1.2-12 mi) flight tests if it makes it over the 150m hurdle unscathed but if not, SN6 could become the first Starship to have a nosecone installed.
SN7
Last but absolutely not least, SpaceX recently built a new Starship test tank for the first time since March. While stouter than an actual Starship-class methane or oxygen tank, this particular test tank is maybe only 25% shorter than the methane tanks installed on Starship prototypes. According to Musk and effectively confirmed by writing all over the prototype, this particular test tank – formerly Starship SN7 – was built to determine if a different kind of steel could be preferable for future ships.
Shortly after the June 15th test began to wind down, Musk announced that the new material (304L stainless steel) had performed quite well, reaching 7.6 bar (110 psi) before it sprung a leak. The fact alone that it sprung a leak instead of violently depressurizing is already a major sign that 304L is preferable to 301L, as it means that Starships built out of it could fail much more gracefully in the event of a leak instead of collapsing or violently exploding. A step further, SpaceX has already managed to repair the leak on SN7 and will likely test the tank again in the next few days.
Meanwhile, Musk says that a second improved 304L test tank is already on its way, after which SpaceX will likely attempt to build and test the first fully-304L Starship prototype. Further down the line, SpaceX intends to develop its own custom steel alloy, optimized specifically for Starship’s needs. The first tests of that ’30X’ alloy could begin as early as August 2020 according to a February Musk tweet.
-
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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.”
SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.
Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.
All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.
— Elon Musk (@elonmusk) July 25, 2026
However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.
Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:
This flight intentionally had much higher acceleration to test how well the heat shield tiles would remain attached at high dynamic pressure.
Test was successful.
— Elon Musk (@elonmusk) July 25, 2026
SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.
Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.
The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.
Tesla claims supplier is holding Cybertruck production hostage
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
