News
SpaceX’s Mr. Steven crosses Panama Canal on 5000 mile journey to Florida
Iconic SpaceX vessel Mr. Steven has completed a successful transit of the Panama Canal as of February 7th, leaving the fairing recovery ship approximately 3-4 days from arrival at its new home in Port Canaveral, Florida.
Mr. Steven’s move from the West Coast to the East Coast comes shortly after a series of controlled fairing recovery tests – dropped by helicopter before deploying a parafoil – brought the vessel closer than ever before to successfully snagging a Falcon fairing out of the air. Thanks to webcams at the landmark, Mr. Steven’s trip through the Panama Canal also revealed that his arms were uninstalled for the coast swap, while two fairing halves – covered in tarps – stood out on the ship’s large deck.
Aaaaand the grand finale, a gif of Mr. Steven’s transit through the Panama Canal’s first western lock (Miraflores). Probably the last we’ll see of him until Port Canaveral, with an ETA around ~4 days from now 🙂#SpaceX pic.twitter.com/DIus6K5hK5
— Eric Ralph (@13ericralph31) February 7, 2019
Although the presence of two fairing halves could be a sign of something else, it could indicate that SpaceX has plans to continue its controlled fairing drop/recovery tests, albeit this time in the Atlantic Ocean. Thanks to a sharp-eyed local observer, it can be observed that, while topped with tarps and safely secured, the fairing halves aboard Mr. Steven had no additional protection against sea spray and the elements over the course of a 5000+ mile (~8000 km) journey at a cruising speed of roughly 20 mph (~32 km/h). In other words, they are most certainly not going to be reused.
If not for reuse, then the only reason Mr. Steven would need to bring fairings to Florida is if there is some need for fairing recovery development hardware (halves that can be abused without opportunity cost), either for more basic mechanical and interface tests with fairings and nets or to continue SpaceX’s program of experimental drop testing.
Is your #MrSteven here in Panama @elonmusk and @SpaceX ? pic.twitter.com/GvTNGYQU9K
— Hugo Tello (@soyhugotello) February 6, 2019
Intriguingly, although SpaceX released a second video of “one” of Mr. Steven’s final West Coast catch tests, some basic sleuthing can easily determine that the test shown in the January 29th video probably occurred more than two weeks earlier, on January 10th. This means that one final helicopter drop test was performed (January 26th) before SpaceX departed Port of LA for Florida on the 29th. Some might conclude, then, that SpaceX’s latest drop tweet was more than a little coy, perhaps indicating that the results of the Jan 26 test may have been appreciably different than the extreme near-miss experienced on the 10th.
While the company’s history – combined with CEO Elon Musk’s welcome tendency of sharing good news almost as soon as he hears it – suggests that the Jan 26 test was probably not a success, SpaceX could be playing its development cards close to its chest when it comes to fairing recovery.
One of Mr. Steven’s final West Coast fairing recovery tests before shipping out for the East Coast. Wait for it… pic.twitter.com/A7q37Gpllu
— SpaceX (@SpaceX) January 30, 2019
Regardless, SpaceX clearly has no plans to end its experimental fairing recovery program with success so agonizingly within reach. Mr. Steven’s move to Florida sets the vessel up for a dramatic increase in available post-launch fairing recovery attempts at the same time as Falcon fairings likely still cost around $3 million apiece and continue to pose the same conundrum Musk raised in mid-2017.
“Imagine if we had a $6 million pallet of cash falling through the sky. Would we try to catch it? I think the answer is yes.” – Elon Musk, July 2017
Although the cost of SpaceX’s fairing recovery program is probably several tens of millions of dollars at this point, it seems probable that Musk would still stand behind his thought experiment. Assuming SpaceX can cost-effectively reuse fairings once recovery is assured, a development program costing upwards of $50-100M could be entirely recouped after just 10-20 dual fairing recoveries, compared to the 21 fairings SpaceX flew in 2018 alone. As long as Falcon 9 and Heavy are likely to continue operating for several more years (all but guaranteed), fairing recovery should still prove worthwhile if SpaceX can close the recovery gap within the next 6-12 months.
Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes!
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:
Elon Musk
SpaceX issues statement on Starship V3 Booster 18 anomaly
The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX has issued an initial statement about Starship Booster 18’s anomaly early Friday. The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX’s initial comment
As per SpaceX in a post on its official account on social media platform X, Booster 18 was undergoing gas system pressure tests when the anomaly happened. Despite the nature of the incident, the company emphasized that no propellant was loaded, no engines were installed, and personnel were kept at a safe distance from the booster, resulting in zero injuries.
“Booster 18 suffered an anomaly during gas system pressure testing that we were conducting in advance of structural proof testing. No propellant was on the vehicle, and engines were not yet installed. The teams need time to investigate before we are confident of the cause. No one was injured as we maintain a safe distance for personnel during this type of testing. The site remains clear and we are working plans to safely reenter the site,” SpaceX wrote in its post on X.
Incident and aftermath
Livestream footage from LabPadre showed Booster 18’s lower half crumpling around the liquid oxygen tank area at approximately 4:04 a.m. CT. Subsequent images posted by on-site observers revealed extensive deformation across the booster’s lower structure. Needless to say, spaceflight observers have noted that Booster 18 would likely be a complete loss due to its anomaly.
Booster 18 had rolled out only a day earlier and was one of the first vehicles in the Starship V3 program. The V3 series incorporates structural reinforcements and reliability upgrades intended to prepare Starship for rapid-reuse testing and eventual tower-catch operations. Elon Musk has been optimistic about Starship V3, previously noting on X that the spacecraft might be able to complete initial missions to Mars.
Tesla CEO Elon Musk teases insane capabilities of next major FSD update
Tesla Full Self-Driving v14.2 – Full Review, the Good and the Bad
