News
Elon Musk says SpaceX’s orbital Starship debut headed for FAA faceoff in a few weeks
CEO Elon Musk says that SpaceX’s first completed Starship rocket could be ready for its orbital launch debut just “a few weeks” from now – far sooner than most expected.
On August 6th, SpaceX very stacked that same vehicle – Starship 20 (S20) and Super Heavy Booster 4 (B4) – to its full height for the first time ever, briefly creating the largest rocket ever assembled. However, the feat was equally a symbolic photo opportunity. SpaceX did install an unprecedented number of Raptor engines on Booster 4 and Ship 20 in a spectacularly short timeframe and both stages are technically meant for flight, but Starship S20 was demated less than an hour later and shipped back to the factory shortly thereafter.
Though they’d had Raptors installed and been stacked to their full ~120m (~390 ft) height, neither booster or ship were truly complete and at least 20% of their engines had yet to be qualified at SpaceX’s McGregor, Texas test campus. Both needed a week or two of additional work – mostly just wiring avionics and installing secondary and tertiary plumbing. Curiously, on August 13th, Starship S20 was once again rolled to SpaceX’s Boca Chica launch site in a partial state of completion, where it now sits beside the orbital launch mount for unknown reasons.
After several days of delays, SpaceX also removed Super Heavy B4 from the orbital launch mount and returned it to the build site on August 11th, where teams are still working to finish its secondary plumbing and avionics. Like Ship 20, all of its Raptors were removed soon after its return, freeing both to complete cryogenic proof testing without risking dozens of potentially flightworthy rocket engines.
Like all previous Starship prototypes, those ‘cryo proof’ tests will involved loading Ship 20 and Booster 4 with supercool liquid nitrogen (LN2), simulating the weight and extreme thermal stress of real liquid oxygen (LOx) and methane (LCH4) propellant without the risk of a catastrophic fire or explosion in the event of anomalies.
For more than a month, SpaceX also gradually outfitted one of two suborbital launch mounts with special hydraulic rams that would have simulated the thrust of Ship 20’s three sea level and three vacuum-optimized Raptor engines – the first Starship prototype with such a configuration. The same was true for Booster 4 and SpaceX had outfitted a new test jig with nine hydraulic rams labeled “B4” – clearly meant to simulate the thrust of nine engines pushing against the Super Heavy’s thrust puck. Additionally, a far larger structural test tool unofficially nicknamed the ‘can crusher’ has been more or less finished after ~6 weeks of work, leading many to assume that Booster 4 would be the first Super Heavy to be subjected to the immense simulated thrust of 29 Raptor engines.
However, earlier this week, SpaceX completely disassembled the six hydraulic rams installed on Mount B and removed all nine rams from the apparent Booster 4 jig. Starship S20 was then rolled back to spot beside the orbital launch mount – not the suborbital mount that had been carefully prepared for its test campaign mere days prior. At the time, the only practical explanation – save for some kind of catastrophic miscommunication – was that SpaceX had cancelled clear plans to cryo proof Ship 20 and Booster 4 with simulated Raptor thrust.
-
Up to now, every single major design change implemented on Starship’s engine section has resulted in the first prototype – and often one or several test tanks – being subjected to cryo proof testing with a complex series of hydraulic rams used to simulate thrust. That most recently peaked with SpaceX’s lone BN2.1 Super Heavy test tank, which seemingly passed a cryo proof, pressure test, and a jig capable of simulating the thrust of up to eight Raptor engines. However, SpaceX has never tested Super Heavy’s new nine-engine thrust puck and has certainly never subjected a Super Heavy booster skirt to the combined thrust of 20 outer engines and 9 center engines.
The fact that complex custom test stands and jigs had already been assembled and installed for Ship 20 and Booster 4 before they were removed or disassembled without use strongly implies that someone at SpaceX – presumably Elon Musk himself – has either decided that those tests are unnecessary or that skipping them is worth the substantial risk. Indeed, for Musk’s subsequent August 15th claim that Ship 20 and Booster 4 could be stacked and ready for flight just “a few weeks” from now to come true, 14-21 days is simply nowhere close to enough time to cryo proof, thrust sim, and static fire both vehicles; integrate the stages; and perform the first true integrate testing of a Starship stack – possibly up to and including some combination of a full-stack cryo proof, wet dress rehearsal, or static fire.
And, as Musk himself notes, that complex ballet of first-of-their-kind rocket prototypes might not even be the long straw for Starship’s orbital launch debut. Technically, short of some kind of major legal intervention, there is actually no way for Starship to launch in the next “few weeks.” In an absolute best-case scenario, the Federal Aviation Administration (FAA) would release a draft environmental review of SpaceX’s orbital Starship launch site today, accept public comments for the required 30 days, instantly clear Starbase with environmental approval within a few days of the public comment window, and then approve Starship’s South Texas orbital launch license as soon as the necessary environmental permissions are in hand.
In other words, the best-case ETA of regulatory approvals for Starship’s first orbital test flight is arguably late September and going off of FAA precedent, that optimistic scenario is also a fairy tale. In reality, a bare minimum of 2-3 months after the FAA releases its draft environmental impact statement is a more realistic best-case scenario for SpaceX. On the opposite end, it’s possible that the FAA will decide that SpaceX needs to complete an entirely new environmental review for its Starbase launch site, easily delaying Starship’s orbital launch debut by 6-12+ months. That doesn’t even account for the potential looming challenges SpaceX might have to surmount to secure an orbital Starship launch license.
Given the challenges SpaceX had in securing even a watered-down suborbital launch license for its medium-altitude Starship flight tests, it’s not out of the question that the FAA could attach some extremely onerous limitations to that license. Ultimately, only time (and the slightest hint of actual movement or urgency at the FAA) will tell and there is arguably nothing that would better apply pressure in the right places than the largest, most powerful, most ambitious rocket ever built sitting – ready for flight – at a brand new launch pad, waiting solely on regulatory approval.
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
