News
SpaceX adds new ship to fleet after fairing catcher Ms. Tree nails second recovery in a row
In a telltale sign that SpaceX is growing much more confident in its ability to consistently recover Falcon 9 fairings, the company has accepted delivery of second recovery ship almost identical to GO Ms. Tree (formerly Mr. Steven) just days after nailing its second fairing catch in a row.
Previously known as M/V Captain Elliott, the new ship appears to have been acquired (or leased) by Guice Offshore (GO) from SEACOR Marine, who purchased Elliott from struggling marine services company Seatran Marine in 2017. One way or another, SpaceX now has a pair of Port Canaveral-based fairing recovery ships in hand – named Ms. Tree and Ms. Chief – and is thus making excellent progress towards catching and reusing both halves of the same Falcon 9 (or Heavy) fairing.
Splurging on ‘ships
Put simply, whoever is paying for or has paid for the two fast supply vessels (FSVs) that are now a part of SpaceX’s rocket recovery fleet has/had a tidy sum to spend. For ships as large, new, and high-performance as Ms. Tree and Ms. Chief, both completed in the mid-2010s, SpaceX or GO would be lucky to pay less than $10M apiece and each ship could easily cost more than $20M, depending on a variety of unknowns. Previous owner Seatran Marine is/was admittedly in dire financial straits, so that could have resulted in an effective fire-sale discount.
Regardless, this is to say that SpaceX was likely willing to splurge and open its wallet wide for extremely high-quality fairing recovery vessels because of just how expensive those fairings are. According to CEO Elon Musk circa 2017, it costs SpaceX $5-6M total to produce a set of Falcon fairing halves, equivalent to roughly 10% of the cost of a Falcon 9 launch ($50M-60M).
As an example, assume that SpaceX paid a full $50M for Ms. Tree and Ms. Chief – effectively a worst-case cost scenario. Assume that recovering and reusing net-caught Falcon fairings still costs half as much as building new fairings ($3M for two halves), also likely a worst-case scenario given the relative mechanical and propulsive simplicity of fairings.
In this mediocre-at-best scenario, it would still take SpaceX less than 20 launches with both halves recovered to completely recoup the cost of both fairing recovery ships. In the event that reusing caught fairings is only 25% as expensive as building new fairings, SpaceX could recoup its fleet investments in just 10 launches. In fact, cost reduction may even be a secondary consideration next to the potential for effectively doubling fairing production with the same facilities. From that perspective, spending, say, $50M on development and another $50M on cutting-edge recovery vessels could easily be a bargain, especially compared to the $1B+ SpaceX has spent deloping Falcon 9 booster reusability.
Fairing-catcher Mk4
With GO Ms. Chief’s August 10th arrival at Port Canaveral, SpaceX’s team of Florida-based recovery engineers and technicians will now be tasked with modifying the ship for Falcon fairing catching. SpaceX completed its first fairing recovery-focused modifications back in late 2017, likely producing what was the first version of fairing recovery tech (Mk1). The net proved to be far too small and was replaced in summer 2018 with a net and arms likely 4X larger (Mk2).
Roughly half a year and several missed catches after Mr. Steven’s Mk2 net was installed, the ship transited the Panama Canal and arrived at Port Canaveral in February 2019. Barely a week or two later, Mr. Steven suffered a failure at sea – well before a planned catch attempt – that saw the ship limp back to port missing the entirety of its net and two of four arms.
After another four months in port, SpaceX installed a third net and arms system on Mr. Steven, featuring distinct differences and apparent upgrades that likely make it Mk3. Shortly after installation and a quick renaming from Mr. Steven to GO Ms. Tree, Ms. Tree’s inaugural Mk3 recovery attempt culminated in SpaceX’s first and second successful fairing catches – back-to-back – on June 24th and August 6th.
Finally, this brings us to the blank slate that is GO Ms. Chief. Compared to Ms. Tree, both vessels are nearly identical: both are built by Gulf Craft, LLC, both are 205 ft x 34 ft (62m x 10m), both have decks rated for ~405 metric tons (900,000 lb), and have top speeds of 26-32 knots (30-37 mph, 50-60 km/h; fully-loaded vs. empty). The lone point of difference is power: Ms. Chief’s engines produce 500 more horsepower and its generators produce an additional 120 kW of power, respective improvements of 5% and 16% relative to Ms. Tree (Mr. Steven).
Despite both ships being nearly identical, SpaceX is unlikely to simply copy and paste Ms. Tree’s thus far successful arms and net, likely instead doing what the company is famous for and fabricating a new and improved variant of the fairing recovery mechanism. This would presumably translate to Mk4. Conveniently, SpaceX appears to be heading into a rare period of no launches, likely stretching almost three months from August 6th (AMOS-17) to late October.
If Mr. Steven and Ms. Tree’s transformations are anything to go by, that hefty chunk of time that should be more than sufficient to fully outfit Ms. Chief with a fresh fairing recovery mechanism, assuming SpaceX has been simultaneously fabricating the hardware in anticipation of Ms. Chief’s arrival.
For now, we’ll have to wait and see if SpaceX’s next launches – both believed to be 60-satellite Starlink missions – will mark the recovery debut of Ms. Chief, as well as the first attempted catch of both Falcon fairing halves. Additionally, following SpaceX’s second successful fairing half catch on August 6th, it’s possible that the company has two recovered halves capable of making a full, flight-proven fairing. Either way, a Starlink launch will likely support the flight-debut of a reused fairing and will almost certainly host the first attempted simultaneous recovery of both fairing halves.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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
