News
Elon Musk reveals SpaceX Falcon 9 survived a water landing test
Following the picture-perfect launch of GovSat-1 on Wednesday afternoon, SpaceX CEO Elon Musk took to Twitter with an extremely unusual bit of news. After separating from the second stage, events relating to Falcon 9’s first stage recovery operations were heard live in the background of SpaceX’s live coverage, leading to some additional intrigue around an already odd situation.
B1032, a flight-proven (reused) booster tasked with launching GovSat-1 on its second mission, was seen with landing legs and grid fins on its sooty exterior – a confusing appearance due to SpaceX’s statement that the core would be expended into the ocean after launch. Thankfully, Elon Musk’s tweets provide at least the beginning of an answer for the several oddities.
This rocket was meant to test very high retrothrust landing in water so it didn’t hurt the droneship, but amazingly it has survived. We will try to tow it back to shore. pic.twitter.com/hipmgdnq16
— Elon Musk (@elonmusk) January 31, 2018
As stated above, GovSat-1’s Falcon 9 booster (1032) was apparently being used to test an exceptionally aggressive landing burn in lieu of a drone ship beneath it. The lack of drone ship begins to make more sense with the added knowledge that 1032 was testing experimental landing procedures: in the relatively likely eventuality that something went wrong, the massive booster would have likely impacted Of Course I Still Love You at an extremely high velocity. Similar impacts have occurred before as SpaceX gradually perfected the new technologies and operational knowledge necessary to recover orbital-class rockets, but a basic understanding of rocketry implies that 1032’s OCISLY impact would have been uniquely destructive, likely taking the ship out of action for at least several weeks of repairs.
This would pose an inherent problem for the imminent launch of Falcon Heavy, with the center of three first stages currently scheduled to attempt a landing aboard the very same drone ship in less than a week. Under optimum conditions (sans huge explosions and general destruction), OCISLY and its entourage of support vessels simply could not complete the journey back to Port Canaveral and the subsequent return to sea that would have been necessary to recovery both GovSat-1 and Falcon Heavy’s center core. Add in the potential need for repairs and expending GovSat-1 was a no-brainer for the launch company: Falcon Heavy’s center core could easily see at least one additional launch after it is recovered, whereas the twice-used 1032 effectively reached the end of its useful life after it separated from the second stage and GovSat payload earlier today.
Falcon 9 1038 aboard Just Read The Instructions after the launch of Formosat-5. (SpaceX)
As a result, SpaceX appears to have continued a trend of exploiting flight test opportunities to the greatest extent practicable by tasking B1032 with an experimental landing attempt. More specifically, Elon quickly added that the landing burn attempted by 1032 involved the ignition of three of the booster’s nine Merlin 1D engines during landing, whereas all SpaceX landings up to this point have occurred with a single Merlin 1D ignition. While the company already routinely utilizes three engines during some boostback and reentry burns, landing burns have always featured a single engine. However, by using three engines, it is entirely possible that SpaceX hopes to eventually move towards even more aggressive landing burns. While the obvious downsides likely include difficulty maintaining control and increased stresses on the booster, the benefits are also pretty inherent. By using more engines, the length of the landing burn could be drastically shortened, resulting in far more efficient propellant usage by minimizing losses to gravity (every second the rocket is trying to go upwards is a second fighting against Earth’s gravity, which pulls the rocket down at ~9.8 meters/second squared).
Incredibly, the booster somehow managed to pull off that three engine landing burn with some success, made apparent by the fact that it is intact and floating in the Atlantic, with some hope of being towed back to land. This is almost certainly the first time SpaceX has ever successfully landed a booster in the ocean without a subsequent breakup, an incredible achievement for a rocket that likely experienced exceptional stresses during reentry and landing. Time will tell how this impacts SpaceX’s future recovery efforts, but it is certainly promising as a method of extracting just a little extra performance from reusable Falcon 9s. In other words, future Falcon 9 missions might be able to carry heavier payloads into higher orbits while still being able to land at sea or even on land. Exciting times!
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
