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 Full Self-Driving has officially landed in a new country today, its seventh overall after it launched in both Australia and New Zealand earlier this year.
On Sunday, Tesla owners in South Korea reported that the company’s Full Self-Driving (Supervised) had started arriving in their vehicles. Owners reported that it was v14.1.4, which is not the latest version available in other countries, but is one of the most recent releases Tesla has deployed to drivers:
From 6 to 7
Tesla Full Self-Driving has launched in South Korea; the 7th country to have FSD https://t.co/X6gm1SyoxV
— TESLARATI (@Teslarati) November 23, 2025
This marks the seventh country in which Tesla has enabled its Full Self-Driving suite, following the United States and Puerto Rico, Canada, China, Mexico, Australia, and New Zealand.
Tesla launched Full Self-Driving most recently in Australia and New Zealand about three months ago. The expansion is a major breakthrough for the company as it aims to launch Full Self-Driving on a global scale.
However, the company’s biggest challenge thus far has been getting European regulatory agencies to handle the red tape that has inhibited Tesla from launching its semi-autonomous driving suite on the continent. Recently, it admitted that it sees a pathway through Dutch regulatory bodies, which seem to be the most willing to work with Tesla to get FSD in Europe.
Tesla Full Self-Driving appears to be heading to Europe soon
The company said that it has driven over 1 million kilometers safely on European roads across 17 different countries in internal testing. But its path to success will be by “partnering with the Dutch approval authority RDW to gain exemption for the feature. This involves proving compliance with existing regulations (UN-R-171 DCAS) + filing an exemption (EU Article 39) for yet-to-be-regulated behaviors like Level 2 systems off-highway, system-initiated lane changes with hands-off the wheel, etc.”
Perhaps the expansion into Europe will be the biggest challenge for Tesla, but it could also yield major results and advantages for the company moving forward. Tesla said it hopes to have FSD available in Europe sometime early next year.
For now, the expansion in South Korea is the latest win for Tesla and its self-driving efforts. In the U.S., it now turns its focus toward fully autonomous operation, as it works with state agencies to launch Robotaxi outside of Texas, California, and most recently, Arizona.
Tesla CEO Elon Musk teased the insane capabilities of the next major Full Self-Driving update just hours after the company rolled out version 14.2 to owners.
Tesla Full Self-Driving v14.2 had some major improvements from the previous iteration of v14.1.x. We were on v14.1.7, the most advanced configuration of the v14.1 family, before Tesla transitioned us and others to v14.2.
However, Musk has said that the improvements coming in the next major update, which will be v14.3, will be where “the last big piece of the puzzle finally lands.”
14.3 is where the last big piece of the puzzle finally lands
— Elon Musk (@elonmusk) November 21, 2025
There were some major improvements with v14.2, most notably, Tesla seemed to narrow in on the triggers that caused issues with hesitation and brake stabbing in v14.1.x.
One of the most discussed issues with the past rollout was that of brake stabbing, where the vehicle would contemplate proceeding with a route as traffic was coming from other directions.
We experienced it most frequently at intersections, especially four-way stop signs.
Elon Musk hints at when Tesla can fix this FSD complaint with v14
In our review of it yesterday, it was evident that this issue had been resolved, at least to the extent that we had no issues with it in a 62-minute drive, which you can watch here.
Some owners also reported a more relaxed driver monitoring system, which is something Tesla said it was working on as it hopes to allow drivers to text during operation in the coming months. We did not test this, as laws in Pennsylvania prohibit the use of phones at any time due to the new Paul Miller’s Law, which took effect earlier this year.
However, the improvements indicate that Tesla is certainly headed toward a much more sentient FSD experience, so much so that Musk’s language seems to be more indicative of a more relaxed experience in terms of overall supervision from the driver, especially with v14.3.
Musk did not release or discuss a definitive timeline for the release of v14.3, especially as v14.2 just rolled out to Early Access Program (EAP) members yesterday. However, v14.1 rolled out to Tesla owners just a few weeks ago in late 2025. There is the potential that v14.3 could be part of the coming Holiday Update, or potentially in a release of its own before the New Year.
Tesla rolled out Full Self-Driving version 14.2 yesterday to members of the Early Access Program (EAP). Expectations were high, and Tesla surely delivered.
With the rollout of Tesla FSD v14.2, there were major benchmarks for improvement from the v14.1 suite, which spanned across seven improvements. Our final experience with v14.1 was with v14.1.7, and to be honest, things were good, but it felt like there were a handful of regressions from previous iterations.
While there were improvements in brake stabbing and hesitation, we did experience a few small interventions related to navigation and just overall performance. It was nothing major; there were no critical takeovers that required any major publicity, as they were more or less subjective things that I was not particularly comfortable with. Other drivers might have been more relaxed.
With v14.2 hitting our cars yesterday, there were a handful of things we truly noticed in terms of improvement, most notably the lack of brake stabbing and hesitation, a major complaint with v14.1.x.
However, in a 62-minute drive that was fully recorded, there were a lot of positives, and only one true complaint, which was something we haven’t had issues with in the past.
The Good
Lack of Brake Stabbing and Hesitation
Perhaps the most notable and publicized issue with v14.1.x was the presence of brake stabbing and hesitation. Arriving at intersections was particularly nerve-racking on the previous version simply because of this. At four-way stops, the car would not be assertive enough to take its turn, especially when other vehicles at the same intersection would inch forward or start to move.
This was a major problem.
However, there were no instances of this yesterday on our lengthy drive. It was much more assertive when arriving at these types of scenarios, but was also more patient when FSD knew it was not the car’s turn to proceed.
Can report on v14.2 today there were ZERO instances of break stabbing or hesitation at intersections today
It was a significant improvement from v14.1.x
— TESLARATI (@Teslarati) November 21, 2025
This improvement was the most noticeable throughout the drive, along with fixes in overall smoothness.
Speed Profiles Seem to Be More Reasonable
There were a handful of FSD v14 users who felt as if the loss of a Max Speed setting was a negative. However, these complaints will, in our opinion, begin to subside, especially as things have seemed to be refined quite nicely with v14.2.
Freeway driving is where this is especially noticeable. If it’s traveling too slow, just switch to a faster profile. If it’s too fast, switch to a slower profile. However, the speeds seem to be much more defined with each Speed Profile, which is something that I really find to be a huge advantage. Previously, you could tell the difference in speeds, but not in driving styles. At times, Standard felt a lot like Hurry. Now, you can clearly tell the difference between the two.
It seems as if Tesla made a goal that drivers should be able to tell which Speed Profile is active if it was not shown on the screen. With v14.1.x, this was not necessarily something that could be done. With v14.2, if someone tested me on which Speed Profile was being used, I’m fairly certain I could pick each one.
Better Overall Operation
I felt, at times, especially with v14.1.7, there were some jerky movements. Nothing that was super alarming, but there were times when things just felt a little more finicky than others.
v14.2 feels much smoother overall, with really great decision-making, lane changes that feel second nature, and a great speed of travel. It was a very comfortable ride.
The Bad
Parking
It feels as if there was a slight regression in parking quality, as both times v14.2 pulled into parking spots, I would have felt compelled to adjust manually if I were staying at my destinations. For the sake of testing, at my first destination, I arrived, allowed the car to park, and then left. At the tail-end of testing, I walked inside the store that FSD v14.2 drove me to, so I had to adjust the parking manually.
This was pretty disappointing. Apart from parking at Superchargers, which is always flawless, parking performance is something that needs some attention. The release notes for v14.2. state that parking spot selection and parking quality will improve with future versions.
Any issues with parking on your end? 14.1.7 didn’t have this trouble with parking pic.twitter.com/JPLRO2obUj
— TESLARATI (@Teslarati) November 21, 2025
However, this was truly my only complaint about v14.2.
You can check out our full 62-minute ride-along below:
Tesla Full Self-Driving lands in a new country, its 7th
Tesla CEO Elon Musk teases insane capabilities of next major FSD update
