News
SpaceX Starship launch delayed to Tuesday by poor FAA planning
Update: CEO Elon Musk says that SpaceX’s fourth high-altitude Starship launch has been delayed from Monday to Tuesday after an FAA inspector – recently required to be onsite for launches – was inexplicably more than six hours late.
While the smallest grain of salt is warranted given Musk’s recently vitriolic relationship with the FAA, the CEO has every reason not to lie about a federal regulatory agency that SpaceX almost fundamentally depends on. As such, the implication is that a lone FAA inspector – only recently required by the FAA itself to be onsite for SpaceX Starship launches – was somehow more than four or five hours away from Boca Chica, Texas by 11am CDT, March 29th.
The only possible explanation for such a delay is that a single inspector – lacking virtually any of the resources afforded to large government agency – missed a flight on a public airline, had a flight canceled at the last second, or was somehow stranded in the middle of nowhere by car issues. As any sane human familiar with air or car travel would know, those issues happen and should always be anticipated. Knowing full well that it had just changed SpaceX’s Starship launch license just two weeks prior to prevent flights without an inspector present, the FAA does not appear to have prepared for those issues in even the most basic sense, failing to ensure alternate methods of transport or two redundant inspectors.
In essence, due either to severe underfunding, general ineptitude, some childish attempt to assert dominance, or some combination of all three, the FAA has explicitly disrespected the hundreds of (possibly 1000+) SpaceX employees working around the clock for weeks to launch Starship SN11 as quickly as possible. Given that the FAA itself distributed Temporary Flight Restrictions (TFRs) for SN11’s Monday launch on Saturday and noted plans for the launch more than a day prior, the giant regulatory agency had no less than 24-48 hours of prior warning even if they’d somehow ignored or missed SpaceX’s own CEO announcing a delay to March 29th on March 26th.
If a regulatory agency like the FAA is incapable of ensuring that an inspector can stand around at a launch the agency itself required an inspector be present for days prior, the same apparatus assuredly should not and cannot be trusted to regulate systems as complex as modern aircraft, spacecraft, and rockets. If the FAA is, in fact, up to the challenge of responsibly regulating those systems with the public’s best interest in mind, then failing a task as simple as ensuring its own inspector is transported, on time, from Point A to Point B is a conscious decision or mistake. Either way, something clearly needs to change.
CEO Elon Musk says that SpaceX has delayed Starship serial number 11’s (SN11) high-altitude launch debut from Friday to Monday to best ensure that the company can “land & fully recover” the 50-meter-tall steel rocket.
First and foremost, the weekend will allow SpaceX times time for “additional checkouts” and scour Starship SN11 and the data it’s produced during testing for any red flags or minor issues. While plans for a same-day static fire and launch didn’t pan out on Friday, March 26th, SpaceX did manage the first half, firing up just one of Starship’s three Raptors to verify the health of the replacement engine after a Thursday Raptor swap. The test marked the first time SpaceX has intentionally fired up just one of the Raptors installed on a three-engine Starship prototype, so the delay will provide extra time to ensure that all three are still looking good.
Standing down SN11 until probably Monday. Additional checkouts are needed. Doing our best to land & fully recover.— Elon Musk (@elonmusk) March 26, 2021
The weather in Boca Chica, Texas has also taken a turn for the worse in the last few days, so the extra few days will also (hopefully) allow time for wind, visibility, and precipitation conditions to improve. According to Musk, Starship SN11 is now scheduled to fly as early as Monday “afternoon” and, as usual, SpaceX will offer live coverage of the fourth high-altitude launch and landing attempt beginning a few minutes before liftoff.
With a little luck, the Starship prototype will be able to continue a trend of iterative improvement and one-up Starship SN10 with a slightly softer landing and no explosion minutes after touchdown. Stay tuned for updates both here and on SpaceX’s social media platforms to catch the official webcast.
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
