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 briefly offered one Robotaxi part in its Parts Catalog for your personal car, only to remove it just a short time after it was first noticed.
Tesla’s Robotaxi camera washer apparatus was briefly available for purchase on the company’s Online Parts Catalog. The camera washer was first noticed on Model Y Robotaxi vehicles about six months ago in Austin.
🚨 Tesla looks to have installed Camera Washers on the side repeater cameras on Robotaxis in Austin
pic.twitter.com/xemRtDtlRR— TESLARATI (@Teslarati) January 23, 2026
First noticed by Not a Tesla App, the Camera Washer entries appeared for the new “Juniper” Model Y under a category called “Halo,” which has also now disappeared. Interestingly, Halo probably is related to Tesla’s internal “Project Halo,” which was a project that aimed to retrofit customer-owned Model Ys into functional Robotaxis.
This hardware addition would likely be required for the vehicle to operate as a Robotaxi, as the Camera Washer seems to be a non-negotiable part of the vision-based system Tesla utilizes for self-driving efforts.
However, this part has since been removed and is no longer visible on the EPC.
Now the true question lingers: Why would Tesla add this Camera Washer to the Model Y parts catalog? Is it planning to make it available for owners to utilize on their own cars for personal use, or will it become a prerequisite for Robotaxi operation in customer-owned cars?
While discussing the upgrade options for Hardware 3 vehicles during the Q1 Earnings Call, Tesla CEO Elon Musk had said that the company could establish small, satellite shops that would upgrade cameras and self-driving computers. Perhaps this same strategy could be utilized for vehicles that want to be included in Robotaxi but do not have the correct hardware.
AI4 is currently represented as capable of unsupervised self-driving, and the same was said about HW3 at one point, only for Tesla to admit last quarter that it would, unfortunately, not be possible. Perhaps AI4 vehicles might need this camera washer as a prerequisite, just as HW3 cars will need that camera and computer upgrade.
This could be the first hint of that’s where we are headed.
Tesla has started rolling out a broader change to the ride experience for its Robotaxi fleet by silencing turn signals, but the change is certainly polarizing.
Tesla has generally made it clear that its purpose-built ride-hailing platform, Robotaxi, will cater to the rider in nearly every way possible. This includes having climate preferences, music, and other personal settings loaded up in the car as the rider enters.
But Tesla is taking it a step further by muting turn signal chimes altogether, a change that appears to be a way to make the ride more peaceful:
Tesla has finally turned off the blinker/turn signal noises in their Model Y Robotaxis.
This is a small update, but will definitely be noticeable for riders. It didn’t really make much sense to leave the turn signal sound on when it’s Unsupervised. pic.twitter.com/ITwx60PAMO
— Sawyer Merritt (@SawyerMerritt) July 27, 2026
However, there are a handful of people who are not thrilled about this change. Turn signals are a conditioned part of the human mind for those who ride in a car regularly.
Taking a turn without one feels strange and odd, and not hearing it click while activated could set off some alarms for riders, who might use the noise as confirmation that other drivers know of their intention to turn.
I kind of like it being on, threw me off when riding with Zoox who has had it disabled
— Dan Burkland (@DBurkland) July 27, 2026
Turn signal noises are still audible in customer cars, so if you use FSD in your personal vehicle, you will still hear the turn signal.
The move is certainly one that is unique, but not one that separates it from other ride-sharing services. In a normal car, the clicking sound confirms to the driver that the blinker is active. In a fully driverless Robotaxi, that feedback serves no purpose for passengers, other than peace of mind.
Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.
Tesla briefly offered this Robotaxi part for your personal car
Tesla Robotaxi gets sweeping but polarizing change
