News
SpaceX rolls Super Heavy booster to orbital launch mount
For the third time in four months, SpaceX has rolled the first potentially flightworthy Super Heavy booster towards Starbase’s orbital launch mount.
Combined with a large crane – fitted with a jig solely used to lift boosters – moving to a spot just beside the booster, it’s clear that SpaceX is preparing to reinstall Super Heavy Booster 4 (B4) on the orbital launch mount. In the context of its unusual history, though, what happens next to the first more or less finished prototype of the largest rocket booster ever built is less clear.
After a shockingly quick assembly over the course of six summer weeks, Super Heavy Booster 4 rolled out of Starbase’s ‘high bay’ facility and headed to the nearby orbital launch complex, where it was installed on a custom ‘mount’ designed to support booster testing and orbital launches. It’s now clear that during that early August photo opportunity and fit test, Booster 4 was nowhere close to finished. Nor, apparently, was it anywhere close to complete one month later when it returned to the orbital pad for the second time after another few weeks of work back at the high bay.
Three months (almost 14 weeks or 100 days) after the Super Heavy prototype’s second trip to the pad, SpaceX has yet to attempt to put the booster through a single proof test. There also appears to be a significant amount of work left to finish installing external ‘aerocovers’ and a heat shield meant to enclose all 29 of its Raptor engines. In the three-year history of Starbase, there isn’t a single prototype of the roughly two-dozen SpaceX has built, tested, and even flown that’s spent even half as long as Super Heavy B4 between apparent structural completion and its first test. Perhaps the fact that Booster 4 is a first-of-its-kind pathfinder explains SpaceX’s uncharacteristic sluggishness or reluctance to actually test the rocket.
In every other instance, SpaceX’s approach to Starship development has been to move incredibly quickly, build a large number of prototypes, and rapidly test those prototypes – often resulting in catastrophic failures. Data is gathered from those failures (SN1, SN3, SN4, SN8, SN9, SN10, SN11, and half a dozen smaller test tanks serve as examples), changes are made, and then the new and improved prototypes that follow repeat the process until SpaceX arrives at a successful design.
Super Heavy B4’s circuitous path has been almost nothing like those of its predecessors. That could also be partly explained by the unavailability of a stand or facilities capable of truly proof testing a Super Heavy, which necessitates a supply of around 3200 tons (7M lb) of liquid nitrogen (LN2; for a cryogenic proof test with full tanks), another 3200 tons of a combination of liquid methane (LCH4) and oxygen (LOx), and the ability to ignite – and survive – as many as 29 to 33 Raptor engines. The suborbital stands SpaceX has used to proof Starships and even Super Heavy Booster 3 don’t even have half the storage capacity required to fully test a booster and the mounts and their surroundings would likely be catastrophically damaged or destroyed by the thrust and blast created by dozens of Raptors.
Still, SpaceX could have theoretically put Booster 4 through a partial cryoproof and maybe fired up as many as nine Raptors at once – not a replacement for full proof testing but still plenty to ensure Super Heavy’s structural integrity and gather invaluable data on clustered Raptor performance. Instead, of course, Super Heavy B4 has sat at Starbase’s former landing zone for more than three months while teams removed engines, reinstalled engines, half-installed a full Raptor heat shield; and installed two of six or seven ‘aerocovers’ needed to protect heat exchangers, racks of pressure vessels, and hydraulic systems installed on the booster’s aft.
This is all to say that from the outside looking in, Booster 4’s path towards testing and flight has been almost entirely different from that of any other Starship prototype. While still quick in comparison with other launch vehicle development programs, relative to other Starship and Super Heavy prototypes, the rate of B4 progress has been far slower – strongly implying that something is seriously wrong with the booster, that SpaceX no longer feels that partial testing is worth the effort, that finishing Booster 4 just hasn’t been a priority for several months, or some combination of the above.
What that ultimately means is that it’s almost impossible to predict what Super Heavy B4’s future holds beyond the clear evidence that SpaceX will soon reinstall to reinstall it on an orbital launch mount that’s much closer to completion than it was the last time B4 was installed. At this point, it’s just as likely that the booster’s third launch mount installation will just be another mechanical fit test, though the hope is that it will kick off full-scale pneumatic and cryogenic proof testing. It could even culminate in the static fire of some or all of its 29 Raptor engines, which have been installed for several months.
-
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 Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
Musk’s massive Terafab project will get final location soon
