News
SpaceX’s first orbital Starship launch “highly likely” in November, says Elon Musk
CEO Elon Musk says that it’s “highly likely” SpaceX will be ready to attempt its first orbital Starship launch in November 2022, and possibly as early as late October. But many major hurdles remain.
Adding to a welcome burst of insight into SpaceX’s fully-reusable Starship rocket program, Musk took to Twitter on September 21st to provide a bit more specific insight into the company’s next steps towards a crucial orbital launch debut. On September 19th, the CEO revealed that SpaceX would roll the Starship booster (B7) currently assigned to that debut back to the factory for mysterious “robustness upgrades” – an unexpected move right after a seemingly successful and record-breaking static fire test.
Two days later, Musk has indicated that those upgrades might involve fortifying Super Heavy Booster 7’s thrust section to ensure it can survive Raptor engine failures. With 33 Raptor V2 engines powering it and plenty of evidence that those Raptors are far from perfect reliability, the concern is understandable, even if the response is a bit different than SpaceX’s norm.
Prior to the start of preparations for Starship’s orbital launch debut, SpaceX sped through Starship development like it wanted to destroy as many rockets as possible – which, to some extent, it did. Rather than spend 6-12 months fiddling with the same few prototypes without a single launch attempt, SpaceX churned out Starships and test articles and aggressively tested them. A few times, SpaceX pushed a little too hard and made avoidable mistakes, but most of the failures produced large amounts of data that was then used to improve future vehicles.
The holy grail of that project was high-altitude Starship flight testing, which saw SpaceX finish, test, and launch a new Starship five times in six months, and culminated in the first fully successful high-altitude Starship launch and landing in May 2021.
In comparison, SpaceX’s orbital flight test preparations have been almost unrecognizable. While a good amount of progress has been made in the 16 months since SN15’s successful launch and landing, it’s clear that SpaceX has decided against taking significant risks. After spending more than six months slowly finishing and testing Super Heavy Booster 4 and Starship 20, the first orbital-class pair, SpaceX never even attempted a single Booster 4 static fire and unceremoniously retired both prototypes without attempting to fly either.
Without info from Musk or SpaceX, we may never know why SpaceX stood down B4 and S20, or why the company appears to have revised its development approach to be a bit more conservative after clearly demonstrating the efficacy of moving fast and taking big risks. It’s possible that winning a $3 billion contract that places Starship front and center in NASA’s attempt to return astronauts to the Moon has encouraged a more careful approach. SpaceX won that contract in April 2021.
-
Even in its more cautious third phase, Starship development is still extraordinarily hardware-rich, moving quickly, and uncovering many problems on the ground in lieu of learning from flight tests. But that doesn’t change the fact that the third phase of Starship development (H2 2021 – today) is proceeding more carefully than the first (Q4 2018 to Q4 2019) and second (Q1 2020 – Q2 2021) phases.
Nonetheless, SpaceX appears to finally be getting closer to Starship’s first orbital launch. According to Musk, the company could be ready for the first launch attempt as early as late October, but a November attempt is “highly likely.” He believes that SpaceX will have two pairs of orbital-class Starships and Super Heavy boosters (B7/S24; B8/S25) “ready for orbital flight by then,” potentially enabling a rapid return to flight after the first attempt. Musk is also excited about Super Heavy Booster 9, which has “many design changes” and a thrust section that will fully isolate all 33 Raptors from each other – crucial for preventing the failure of one engine from damaging others.
Meanwhile, as Musk forecasted, Super Heavy Booster 8 rolled to the launch pad on September 19th and will likely be proof tested in the near future while Booster 7 is upgraded back at the factory.
Encouraging as that may be, history has shown that reality – particularly when it involves Starship’s orbital launch debut – can be quite a bit different than the pictures Elon Musk paints. In September 2021, for example, Musk predicted that SpaceX would conduct the first Super Heavy static fire at Starbase’s orbital launch pad later that month. In reality, that crucial test occurred 11 months later (August 9th, 2022) and used an entirely different booster.
This is to say that significant progress has been made in the last few months, but SpaceX has a huge amount of work left, almost all of which lies in uncharted terrain. Starship 24, which completed its first six-engine static fire earlier this month, is currently undergoing strange modifications that seem to imply that the upper stage is not living up to SpaceX’s expectations. It’s unclear if additional testing will be required.
Super Heavy B7 is headed back to the factory for additional work after a successful seven-Raptor static fire. Once it returns to the pad, the sequencing isn’t clear, but SpaceX will need to complete the first full Super Heavy wet dress rehearsal (fully loading the booster with thousands of tons of flammable propellant) and the first full 33-Raptor static fire. It remains to be seen if SpaceX will continue its conservative approach (i.e. testing one, three, and seven engines over six weeks) or jump straight from seven- to 33-engine testing.
It’s also unclear where Ship 24 fits into that picture. SpaceX will eventually need to (or should) conduct a full wet dress rehearsal of the fully stacked Starship and may even want to attempt a 33-engine static fire with that fully-fueled two-stage vehicle to truly test the rocket under the same conditions it will launch under. Will SpaceX fully stack B7 and S24 as soon as the booster returns to the pad, risking a potentially flightworthy Starship during the riskiest Super Heavy tests yet?
-
SpaceX’s last year of activity suggests that the company will choose caution and conduct wet dress rehearsals and 33-engine static fires before and after stacking, potentially doubling the amount of testing required. One or several more tests will also be required if SpaceX decides to gradually build up to 33 engines, which is the approach that all Booster 7 activity to date suggests SpaceX will take.
Either way, it will be a major challenge for SpaceX to have a fully-stacked Starship ready to launch by the end of November. If any significant problems arise during any of the several unprecedented tests described above, Musk’s predicted schedule will likely become impossible. As a wildcard, the Federal Aviation Administration (FAA) has yet to issue SpaceX a license or experimental permit for orbital Starship launches, either of which is contingent upon dozens of “mitigations.”
This isn’t to say that it’s impossible for an orbital Starship launch attempt to occur in November. But factoring in the many issues Booster 7 and Ship 24 have experienced during much simpler tests, it’s becoming increasingly implausible that SpaceX will be ready to launch the pair before the end of 2022. Stay tuned.
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
