News
SpaceX President updates schedule for Starship’s orbital launch debut
SpaceX COO and President Gwynne Shotwell says that the company now expects Starbase to be ready for Starship’s first orbital launch attempt as early as June or July, pushing the schedule back another month or two.
To accomplish that feat, SpaceX will need to more or less ace a wide range of challenging and unproven tests and pass a series of exhaustive bureaucratic reviews, significantly increasing the odds that Starship’s orbital launch debut is actually closer to 3-6 months away. While SpaceX could technically pull off a miracle or even attempt to launch hardware that has only been partially tested, even the most optimistic of hypothetical scenarios are still contingent upon things largely outside of the company’s control.
Will FAA or won’t FAA?
Both revolve around the Federal Aviation Administration (FAA), which – in SpaceX’s case – is responsible for completing a ‘programmatic environmental assessment’ (PEA) of orbital Starship launches out of Boca Chica, Texas and issuing a launch license for the largest and most powerful rocket ever built. In some ways, both tasks are unprecedented, but the bureaucratic processes involved are still largely the same as those SpaceX has successfully navigated over the last two decades.
First up, the FAA’s environmental review. Until very recently, the fate of Starbase’s PEA was almost completely indeterminable and could have gone any number of ways – most of which would not be favorable for SpaceX. However, just a few days ago and about a week after the FAA’s latest one-to-two-month PEA delay announcement, the agency updated an online dashboard to show that the fourth of five main PEA processes had been completed successfully. The most important part of the update is the implication that SpaceX and the FAA have now completed almost every aspect of the PEA that requires cooperation with other federal agencies and local stakeholders.
Only one more cooperative process – ensuring “Section 4(f)” compliance – still needs to be completed. Without delving into the details, there is no convincing evidence to suggest that that particular step will be a showstopper, though SpaceX might have to compromise on certain aspects of Starbase operations to complete it. Once Section 4(f) is behind them, the only thing standing between the FAA and SpaceX and a Final PEA is the completion and approval of all relevant paperwork. In other words, for the first time ever, the FAA’s targeted completion date – currently May 31st, 2022 – may actually be achievable.
Still, as the FAA itself loves to repeatedly point out, “the completion of the PEA will not guarantee that the FAA will issue a launch license – SpaceX’s application must also meet FAA safety, risk, and financial responsibility requirements.” Even if the PEA is perfect, SpaceX still has to secure an FAA launch license for the largest and most powerful rocket in history. It’s unclear if SpaceX and the FAA have already begun that painful back-and-forth or if some tedious fine print prevents it from starting before an environmental review is in place. Without knowing more, launch licensing could take anywhere from a few days to several months.
A series of tubes
Without the FAA’s launch license and environmental approval, any Starship SpaceX builds cannot legally launch from Starbase. On the other side of the coin, though, it’s just as true that the FAA’s nods of approval are worth about as much as the paper they’re written on without a rocket that’s ready to launch. In a perfect world, SpaceX would have a Starship and Super Heavy booster fully qualified, stacked, and sitting at Starbase’s orbital launch site when the FAA finally gives a green light. However, that’s not quite what SpaceX’s reality is today.
-
First Starship orbital flight will be with Raptor 2 engines, as they are much more capable & reliable. 230 ton or ~500k lb thrust at sea level.
We’ll have 39 flightworthy engines built by next month, then another month to integrate, so hopefully May for orbital flight test.— Elon Musk (@elonmusk) March 21, 2022
SpaceX has made a significant amount of progress in the last month and a half, but contrary to CEO Elon Musk’s hopes as of March 21st, the company will absolutely not be ready to attempt an orbital launch by the end of May. Nonetheless, Shotwell’s estimate of “June or July” may not be completely out of reach. Since Musk’s tweet, SpaceX finished assembling Super Heavy Booster 7, rolled the rocket to the launch site on March 31st, and completed several major tests in early April. However, during the last test, an apparent operator error significantly damaged a large part installed inside the booster, forcing SpaceX to return Super Heavy B7 to Starbase’s build site. After two and a half weeks of repairs, Booster 7 returned to the launch site on May 6th and completed another ‘cryoproof’ test, seemingly verifying that those quick repairs did the job.
Had Booster 7 not required repairs, it’s not impossible (but still hard) to imagine that SpaceX could have had a Super Heavy booster ready to launch by the end of May. Still, the static fire testing Booster 7 needs to complete is almost entirely unprecedented and could take months to complete. To date, SpaceX has never ignited more than six Raptors at once on a Starship prototype, while Super Heavy will likely need to complete multiple 33-engine tests before it can be safely considered ready for flight. Worse, there is no guarantee that SpaceX actually wants to fly Booster 7 after the damage it suffered. If Booster 8 carries the torch forward instead, Starship’s orbital launch debut could easily slip to late Q3 or Q4 2022.
Meanwhile, Super Heavy is only half of the rocket. When Musk tweeted his “hopefully May” estimate, SpaceX was nowhere close to finishing the Starship – Ship 24 – that is believed to have been assigned to the orbital launch debut. However, SpaceX finally accelerated Ship 24 assembly within the last few weeks and ultimately finished stacking the upgraded Starship on May 8th. A great deal of work remains to truly complete Ship 24, but SpaceX should be ready to send it to a test stand within a week or two. Even though the testing Ship 24 will need to complete has been done before by Ship 20, making its path forward less risky than Booster 7’s, Ship 24 will debut a number of major design changes and likely needs at least two months of testing to reach a basic level of flight readiness.
Last but not least, there’s the question of the orbital launch site (OLS) itself. Is the launch mount ready to survive a full Super Heavy static fire? Is the pad’s tank farm ready to fill Starship and Super Heavy with several thousand tons of flammable, explosive cryogenic propellant? If it’s a goal of the test flight, is the launch tower ready for a Super Heavy booster to attempt to land in its arms? While there are reasons to believe that the answer to some of those questions is “yes,” plenty of uncertainty remains and plenty of work is still incomplete.
Ultimately, Shotwell’s June goal is almost certainly unachievable. Late July, however, might be within the realm of possibility, but only in the unlikely event that all Booster 7 and Ship 24 testing is completed almost perfectly and without further delay. For the pragmatic reader, August or September is a safer bet. Thankfully, at least one thing is certain: activity at Starbase is about to get significantly more exciting.
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
