Connect with us

News

SpaceX adds new ship to fleet after fairing catcher Ms. Tree nails second recovery in a row

Ms. Chief (right) is likely about to become an almost identical twin to fairing recovery vessel Ms. Tree (formerly Mr. Steven). (SpaceX, Gulf Craft, LLC)

Published

7 years ago

on

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).

Falcon 9 and Heavy fairings are a relatively small portion of the overall cost of launch, but they are by no means cheap. (SpaceX)

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.

USAF photographer James Rainier's remote camera captured this spectacular view of Falcon Heavy Block 5 side boosters B1052 and B1053 returning to SpaceX Landing Zones 1 and 2. (USAF - James Rainier)
This did not come cheaply. Neither, it seems, has fairing recovery. (USAF)

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).

With a bit of luck, Mr Steven will likely return to about 24 hours after Iridium-6/GRACE-FO's launch, hopefully with a fairing half in two. (Pauline Acalin)
Not nearly enough net, as it turned out. (Pauline Acalin, May 2018)
Mr. Steven is pictured here just days before departing for the Panama Canal and a new home at Port Canaveral. (Pauline Acalin, 01/22/19)

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.

Advertisement

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

Related Topics:

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

Elon Musk

Elon Musk reveals unfortunate truth of Tesla Full Self-Driving development

In a candid reply to a dramatic video of Tesla’s Full Self-Driving (FSD) system averting disaster, Elon Musk laid bare a harsh reality facing autonomous vehicle technology.

Published

7 minutes ago

on

April 7, 2026

By

Tesla’s Full Self-Driving suite is one of the most significant technological developments in terms of passenger travel in decades, but it is not all sunshine and rainbows, even with major strides in safety, CEO Elon Musk revealed.

In a candid reply to a dramatic video of Tesla’s Full Self-Driving (FSD) system averting disaster, Elon Musk laid bare a harsh reality facing autonomous vehicle technology.

The clip shows a Model 3 traveling at over 65 mph on a foggy, rain-soaked highway when a pedestrian suddenly steps into traffic.

Full Self-Driving instantly detects the threat and swerves safely, preventing what could have been a fatal collision for both the pedestrian and the driver’s cousin.

Musk’s response was unequivocal:

“Tesla self-driving saves a lot of lives – the statistics are unequivocal. That doesn’t mean it’s perfect, of course.” Even with a projected 10x safety improvement over human drivers, FSD would still prevent roughly 90% of the world’s approximately one million annual auto fatalities. The remaining 10%—roughly 100,000 deaths—would expose Tesla to relentless lawsuits. Meanwhile, the vast majority of lives saved would go unnoticed. “The 90% who are still alive mostly won’t even know that Tesla saved them. Nonetheless, it is the right thing to do.”

This “unfortunate truth,” as Musk implicitly framed it, highlights a fundamental asymmetry in how society perceives safety technology. Human drivers cause the overwhelming majority of crashes through distraction, fatigue, or error.

Yet when FSD errs, the incident becomes headline news and a courtroom target. Prevented tragedies, by contrast, leave no trace.

Survivors simply continue their journeys, unaware of the split-second intervention that kept them alive. The result is a distorted public narrative that amplifies failures while rendering successes invisible.

We have seen this through various headlines throughout the years, including the mainstream media’s obsession with only mentioning the manufacturer’s name in the instance of an accident when it is “Tesla.”

Opinion: Tesla Autopilot NHTSA investigation headlines are out of control

The video’s real-world example underscores FSD’s current capabilities. In near-zero visibility, the system’s cameras and neural network reacted faster than any human could, demonstrating the life-saving potential Musk cites.

Tesla’s latest safety data already shows FSD (Supervised) performing significantly better than the U.S. average, with crashes occurring far less frequently per mile driven.

Still, regulatory scrutiny, liability concerns, and media focus on edge-case failures continue to slow widespread adoption. Musk’s frank admission suggests Tesla is prepared to push forward despite the legal and perceptual headwinds.

As FSD edges closer to unsupervised autonomy, Musk’s post serves as both a progress report and a reality check. The technology is already saving lives today.

The unfortunate truth is that proving it and scaling it responsibly will require society to value statistical lives saved as much as dramatic stories of those lost. In the race toward safer roads, perception may prove as formidable an obstacle as the fog and rain in that viral video.

Continue Reading

News

Tesla Full Self-Driving v14.3: First Impressions

Published

2 hours ago

on

April 7, 2026

By

Tesla started rolling out Full Self-Driving v14.3 to Early Access Program (EAP) members earlier today, and I had the opportunity to see some of the improvements that were made from v14.2.2.5.

While a lot of things got better, and I truly enjoyed using Full Self-Driving again after being stuck with the widely confusing and frustrating v14.2.2.5, Tesla still has one major problem on its hands, and it has to do with Navigation and Routing. I truly believe those issues will be the biggest challenges Tesla will face with autonomy: the car simply going the correct way, not conflicting with what the navigation says, and taking the simplest and most ideal route to a destination.

Here’s what I noticed as an improvement with my first hour with v14.3. This is not a full review, nor is it reflective of everything I will likely experience with this new version. This is simply what I saw as a noticeable improvement from the past version, v14.2.2.5.

There is also a more streamlined version on X, available at the thread below:

Yellow Light Behavior is Significantly Better

On v14.2.2.5, I had so many instances of the car slamming the brakes on to stop at a yellow light when it was clearly the safer option to proceed through. There were several times when the car would be about 20 feet from the line, traveling at 15-20 MPH, the light would turn yellow, and it would slam the brakes to stop. I would nudge it through yellow lights constantly because of this by putting my foot on the accelerator.

The instances I’m talking about here would not have been close calls — the car would have likely moved through the intersection completely before the light would turn red.

On multiple occasions this evening, FSD proceeded through yellow lights safely, without hesitation or any brake stabbing. It was refreshing:

This was a huge complaint with v14.2.2.5. Sometimes, it’s a safer option to go through a yellow light, especially when you have traffic behind you. It’s a great way to get rear-ended.

Parking Performance

I had four instances of parking, and FSD v14.3 really did a flawless job. I was very impressed with how solid it was, but also with how efficiently it moved into the spot. When there was traffic around with past versions, I usually chose to park manually just because FSD took its time getting into a spot. I don’t see that being an issue anymore.

I complained about parking a lot and shared several images on X and Facebook of those examples:

No issues with it this evening. 4/4. Here are two looks:

Highway Performance

FSD v14.3 passed the five cars shown in this image:

The sixth was 200-300 yards ahead of the fifth. In v14.2.2.5, FSD would usually stay in the left lane, especially on Hurry and Mad Max. It did not do that, as it instead chose to get back over in the right lane after passing the final car.

Speed was not much of a concern here, even though it was going 21 MPH over. Although it was fast, I did have a line of cars behind me traveling at the same speed, and FSD had just merged about a half mile prior, so I chose to let it continue.

There were no instances of camping in the left lane for extended periods of time. I do want to do more testing with the Speed Profiles because they were in need of some work with the previous version. I am starting to side with those who want a Max Speed setting, which was removed last year.

Navigation and Routing Still Need Work

I was heading back toward where I came from, so I turned “Avoid Highways” on to take a different way. This confused the Routing system, and instead of turning left, then right, as the Routing said, the car turned right, then indicated for another right, basically going in a big rectangle. The car ignored the second right-hand turn and continued straight. I ended up turning “Avoid Highways” off and letting the car pick the same routing option as what took me here.

I have truly complained so much about Navigation and Routing that I’m starting to feel sort of bad. It is obviously such a massive challenge for some reason, but I am confident it will improve. I recall seeing Tesla hiring someone for this role a few months back, so perhaps there is hope for it to get better.

Smarter Behavior When Approaching Exits/Routing

This probably should be grouped in with Highway Behavior, but I wanted to highlight it on its own.

The highway exit pictured was always frustrating for v14.2.2.5. In the Hurry speed profile, I have seen it try to execute passes on multiple cars with as little as 0.6 miles to spare before taking the exit.

With three cars ahead of it, it chose to reduce speed and just wait until the exit. It was refreshing to see an improvement here, so I hope this behavior persists. Sometimes there’s just no reason to pass when you’re less than a mile from getting off the highway anyway.

Larger Visibility Warnings

Tesla seems to have increased the size of these “Camera Visibility Limited” warnings. Previously, they were just small thumbnails:

Stop Sign Behavior

This is probably the biggest improvement of all, because how it behaved at Stop Signs in v14.2.2.5 was so incredibly terrible and disruptive to the flow of a busy intersection.

There are several four-way, all-stop intersections near me. In the past, FSD would stop well behind the Stop Sign or the white-painted line on the road. It would then inch forward, stopping again at this line, essentially making two stops at a single intersection.

If there is visibility, I don’t truly care where FSD stops, as long as it stops once. Stopping twice just isn’t ideal or logical. I can’t imagine many humans would do it, I know I wouldn’t.

I didn’t have that issue this evening:

This was pretty tight, too, in the sense that both my car and the other one got to the intersection at the same time. FSD may have stopped first, but the other vehicle was probably around the same point that I was when FSD decided to stop. I was happy to see the assertiveness to proceed; it felt like it was ideal to just go through. I was happy it didn’t stop a second time up at the line. I’d be fine if it stopped at the line, as long as that was the only stop it made.

Continue Reading

News

Tesla Full Self-Driving v14.3 rolls out: here’s what’s new

We are in EAP and will be on the road with v14.3 in the coming hours, so we’ll have a lot of things to discuss over the next few days, especially coming from v14.2.2.5, which I called the most “confusing” FSD release of all time.

Published

7 hours ago

on

April 7, 2026

By

Tesla has officially started rolling out Full Self-Driving v14.3 to Early Access Program (EAP) members, and there are a lot of new improvements.

We are in EAP and will be on the road with v14.3 in the coming hours, so we’ll have a lot of things to discuss over the next few days, especially coming from v14.2.2.5, which I called the most “confusing” FSD release of all time.

Tesla brought out a lot of improvements, according to the v14.3 release notes, which list a vast number of fixes, new features, and new capabilities.

Here’s what Tesla’s release notes for the v14.3 release state:

  • Improved parking location pin prediction, now shown on a map with a P icon.
  •  Increased decisiveness of parking spot selection and maneuvering.
  • Rewrote the Al compiler and runtime from the ground up with MLIR, resulting in 20% faster reaction time and improving model iteration speed.
  • Enhanced response to emergency vehicles, school buses, right-of-way violators, and other rare vehicles.
  • Mitigated unnecessary lane biasing and minor tailgating behaviors.
  • Improved handling of small animals by focusing RL training on harder examples and adding rewards for better proactive safety.
  • Improved traffic light handling at complex intersections with compound lights, curved roads, and yellow light stopping – driven by training on hard RL examples sourced from the Tesla fleet.
  • Upgraded the Reinforcement Learning (RL) stage of training the FSD neural network, resulting in improvements in a wide variety of driving scenarios.
  • Upgraded the neural network vision encoder, improving understanding in rare and low-visibility scenarios, strengthening 3D geometry understanding, and expanding traffic sign understanding.
  • Improved handling for rare and unusual objects extending, hanging, or leaning into the vehicle path by sourcing infrequent events from the fleet.
  • Improved handling of temporary system degradations by maintaining control and automatically recovering without driver intervention, reducing unnecessary disengagements.

Tesla also listed a handful of future improvements as well:

  • Expand reasoning to all behaviors beyond destination handling
  • Add pothole avoidance
  • Improve driver monitoring system sensitivity with better eye gaze tracking, eye wear handling, and higher accuracy in variable lighting situations

CEO Elon Musk has said that v14.3 could be “where the last big piece of the puzzle finally lands.” We have high expectations for this release because, in a lot of ways, v14.2’s final version was extremely disappointing and seemed to be a regression more than anything.

Nevertheless, Full Self-Driving v14.3 is going to be quite an interesting test, considering this is also the first time Musk has stated it will feel like the car will be “sentient.”

Reasoning will be a bigger piece of the puzzle with this release, although there were some elements of it in v14.2.

Tesla AI Head says future FSD feature has already partially shipped

We plan to travel plenty of miles with it over the next few days, so we’ll keep you posted on what our thoughts are.

Continue Reading