News
SpaceX ship Mr. Steven renamed ahead of Falcon Heavy fairing catch attempt
In a pleasant, last-minute surprise, SpaceX fairing recovery vessel Mr. Steven has departed Port Canaveral for its first Falcon fairing catch attempt in more than half a year. The speedy ship has already traveled more than 1250 km (800 mi) in ~48 hours and should soon be in position to attempt recovery of Falcon Heavy Flight 3’s payload fairing halves.
In another surprise, Mr. Steven has been renamed to GO Ms. Tree, a strong indicator that Guice Offshore (GO) – a company SpaceX is heavily involved with – has acquired the vessel from financially troubled owner/operator Sea-Tran Marine. With this likely acquisition, nearly all of SpaceX’s non-drone ship vessels are now leased from – and partially operated by – GO. The name change is undeniably bittersweet for those that have been following Mr. Steven’s fairing recovery journey from the beginning. However, it’s also more than a little fitting given that the vessel switched coasts and suffered an accident that forced SpaceX to replace the entirety of its arm-boom-net assembly. Much of Mr. Steven – now GO Ms. Tree – has been replaced in the last few months and with any luck, the vessel is better equipped than ever before to snag its first Falcon fairing(s) out of the air. Falcon Heavy is scheduled to lift off no earlier than (NET) 11:30 pm ET (03:30 UTC), June 24th.
♫ [Mr. Steven] would [sail nine] hundred miles ♫
Not one to dip his/her toes in first, Mr. Steven/GO Ms. Tree’s first fairing recovery attempt since crossing the Panama Canal will be a record-breaker. In yet another last-second surprise, Falcon Heavy Flight 3 – assigned to the US Air Force’s Space Test Program 2 (STP-2) mission – had its center core recovery profile radically modified just days ago, moving the booster’s drone ship landing from ~40 km offshore to more than 1240 km (770 mi) off the coast of Florida.
Given that the upper stage and its fairing-shrouded payload inherently separate after the center stage, after which the two fairing halves are ejected, those fairings will end up even further downrange than the center stage. In the case of Falcon Heavy’s STP-2 mission, the fairing halves could end up splashing down (or, hopefully, landing in a net) anywhere from 1400-1600 km (870-1000 mi) downrange from SpaceX’s Pad 39A Cape Canaveral launch facilities.
Records on records
With a fairing recovery attempt more than ~1400 km downrange and an attempted Falcon Heavy center core landing nearly 1250 km off the Florida coast, Falcon Heavy’s STP-2 mission is chock-full of records. As discussed previously on Teslarati, aside from the surprise recovery records-to-be, STP-2 will be a milestone launch attempt for several additional reasons.
“To successfully complete STP-2, the upper stage will be subjected to ‘four separate upper-stage engine burns, three separate deployment orbits, a final propulsive passivation maneuver, and a total mission duration of over six hours.‘ It will likely be SpaceX’s most technically-challenging launch ever.”
— Teslarati.com, 06/19/2019
“The US Air Force has decided that STP-2 presents an excellent opportunity to begin the process of certifying flight-proven SpaceX rockets for military launches. The STP-2-related work is more of a preliminary effort for the USAF to actually figure out how to certify flight-proven commercial rockets, but it will still be the first time a dedicated US military mission has flown on a flight-proven launch vehicle. Down the road, the processes set in place thanks – in part – to STP-2 and Falcon Heavy may also apply to aspirational rockets like Blue Origin’s New Glenn and ULA’s “SMART” proposal for Vulcan reuse.”
— Teslarati.com, 06/16/2019
In almost every conceivable way, STP-2 will absolutely be the most challenging launch SpaceX has ever attempted. Success would effectively confirm beyond any reasonable doubt that SpaceX is just as capable as – if not more capable than – its sole US competitor, Lockheed Martin and Boeing’s United Launch Alliance (ULA). On top of being able to compete for and perform all mission profiles required by the US military and NASA, SpaceX will also remain the only entity (private or public) in the world that is actively launching, landing, and refusing orbital-class rocket hardware.
Tune in to SpaceX’s hosted webcast around 11:15 pm ET (03:15 UTC), June 24th to watch Falcon Heavy’s third launch ever and (hopefully) catch a glimpse of multiple record-breaking recovery attempts and Falcon S2’s most challenging mission ever.
Want to remember the awesomeness of Falcon Heavy every single day? Consider a limited-edition set of high-quality prints, signed by both Teslarati photographers to commemorate the rocket’s inaugural Starman launch.
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
