News
SpaceX fairing recovery ships return to port with Falcon 9 nosecone and battle scars
Four days after they headed out into the Atlantic Ocean, twin SpaceX fairing recovery ships Ms. Tree and Ms. Chief have returned to port with both halves of a Falcon 9 fairing, although they appear to have picked up some battle scars along the way.
Ms. Tree and its near-identical sibling Ms. Chief departed Port Canaveral on December 14th and arrived on station – 790 km (490 mi) off the coast of Florida – some 36 hours later. Each outfitted with a quartet of arms and pair of nets, it was the first time both ships successfully made it out into the Atlantic for a simultaneous fairing catch attempt, having been foiled by high seas during a prior November outing.
For unknown reasons, after the duo’s November false start, both ships stopped for almost two weeks at a South Carolina port, perhaps indicating that SpaceX was concerned about the structural integrity of the ships’ seemingly fragile net mechanism. In February 2019, Mr. Steven (now Ms. Tree) lost two of its four arms while heading downrange for an attempted catch, apparently broken off by pitching caused by high seas. Further strengthening the case that their net mechanisms are rather fragile, both Ms. Tree and Ms. Chief again suffered damage after their Kacific-1/JCSAT-18 Falcon 9 fairing recovery attempt.
Both ships arrived back at Port Canaveral on December 18th and were caught by Teslarati photographer Richard Angle while passing through the narrow mouth of the port. GO Ms. Chief took the lead, revealing a Falcon 9 fairing half snugly secured with a tarp on her deck – the ship’s very first launch vehicle hardware recovery.
First (partially) successful fairing recovery quite literally under wraps, Ms. Chief nevertheless did not make it through the rite of passage unscathed. Oddly, it appears that just one of the ship’s eight white arm supports is missing (the rear right or aft starboard arm), visibly resulting in the arm slouching a bit compared to its siblings. Intriguingly, it appears that the arm is partially stretching – and thus potentially resting on – Ms. Chief’s net and rigging.
The fact that only one of the arm’s two beams (of eight total) seems to have failed is more immediately indicative of possible human error during installation or a defective attachment mechanism, although it’s entirely possible that a fluke of weather could have damaged just the one beam.
Thankfully, Ms. Tree (formerly Mr. Steven) appears to have made it through the recovery mission with all four arms fully intact, although the ship clearly struggled with a separate mechanism. Notably, Ms. Tree seems to have struggled to use its secondary net to lift its fairing half out of the sea and onto her deck, with that smaller net clearly suffering a multitude of rips and tears at some point during the process. Her recovered fairing half is somewhat awkwardly strewn on the deck with no obvious attempt to rectify the issue, indicating that the net may have torn mid-lift, causing the fairing to fall maybe 5-10 feet.
If it did actually fall onto Ms. Tree’s deck, that will almost certainly be visible in the form of damage to its aluminum-composite honeycomb structure and white insulation coating.
Ultimately, fairing recovery continues to prove itself to be a major challenge, although SpaceX obviously has no intention of giving up. With two successful catches already in hand, it’s clear that fairing recovery is undeniably possible and is more a matter of tweaking existing systems than starting from scratch. Much like Falcon 9 booster recovery had and its fair share of failed landings even after the first success, it will likely take quite a while for SpaceX to optimize fairing recovery to the point that it can be considered reliable.
For now, routine fairing recovery and reuse will likely continue to be Falcon 9’s white whale, at worst adding to the excitement of every SpaceX satellite launch.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Tesla’s Automatic Collision Evasion feature can be seen in one of the first owner videos of it in action.
Tesla owner Spencer (@scotsrule08) posted on Monday that the feature “worked flawlessly,” saying FSD reengaged itself just as he was about to hit a curb. Ashok Elluswamy, who leads Tesla’s AI team, shared the clip and wrote, “A guardian angel always looking out for you.”
The video arrives in the middle of a staged rollout. Tesla first shipped Automatic Collision Evasion with FSD (Supervised) v14.3.9 in software update 2026.27.6 earlier this month, which Teslarati covered as it reached cars. Update 2026.27.10, which began going out on September 19, carried the feature improvements with FSD v14.3.10, according to release notes tracked by Not a Tesla App. The newer 2026.27.11 build is now reaching another wave of vehicles.
The new Automatic Collision Evasion feature worked flawlessly! FSD reengaged itself just as I was about to hit a curb.
Kudos @Tesla_AI team! 👏 pic.twitter.com/Fbp15HhpL2
— Spencer (@scotsrule08) September 28, 2026
The feature only runs on HW4 vehicles, and it requires an active FSD purchase or subscription with both FSD (Supervised) and Automatic Emergency Braking enabled. HW3 owners receive FSD v14.2 Lite in the same updates, but that build does not include collision evasion.
Tesla’s release notes describe two triggers. The first is an imminent frontal collision that braking alone may not prevent, in which case the car can activate FSD to steer, brake or accelerate around the hazard. That scenario is limited to highways below 85 mph, with no pedestrians or cyclists detected and no slippery road surface. The second covers a driver who appears inattentive, such as reaching into the back seat, or who seems to have switched off FSD by accident. Spencer’s curb clip appears to fall into that second category.
Tesla plans big safety improvements for Full Self-Driving v15
Once the system takes over, the accelerator is muted and light brake input will not cancel the maneuver. Drivers need to apply firm, deliberate steering force to take back control, and the car chimes to hand control back once the danger has passed.
Elluswamy recently noted that earlier hazard prediction, faster reaction time and better collision avoidance would arrive with FSD v15, the next major version.
Tesla is delaying its event for the Roadster, moving it from this Thursday, October 1, to Thursday, October 15, due to unfavorable weather.
The company has said it has been tracking the weather for this Thursday closely with local meteorologists, and because the event can only be held outside, Tesla is making the call to delay it:
“We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule. New date is October 15. Additional details to follow.”
Roadster event update
We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule.
New date is October 15. Additional details to…
— Tesla (@Tesla) September 28, 2026
We are sure that this is bringing back PTSD for some Tesla fans, and we know it is not ideal, but this also reveals some things about the event. Tesla said that this can only be held outdoors, meaning it bodes well for the rumors that the vehicle could potentially hover.
Some believe that this was essentially confirmed by the FAA airspace restriction they were granted, but this could have been for a drone show or to keep drones from spying on the event.
Tesla Roadster is available for order once again following brief hold
The Roadster event has been long-awaited, and it is unfortunate that the weather is going to keep us all waiting a little bit longer.
The Tesla Roadster will be unveiled in Waco, Texas.
Elon Musk
SpaceX turned a heralding moment for Starship into its greatest
Starship reached orbit despite losing an engine, deployed 26 Starlink V3 satellites on Flight 14.
SpaceX’s Starship reached orbit for the first time on Monday, and for a few nail-biting minutes it looked like it wouldn’t. During ascent on Flight 14, one of Ship 41’s six Raptor engines shut down early, and SpaceX’s livestream host Dan Huot told viewers the team had decided not to commit to orbit. Minutes later, after what Huot described as a lot of conversation in the control room, the final poll came back in favor, and a roughly 19 second burn of a single Raptor pushed the ship into orbit about 170 miles up.
The reversal matters because SpaceX had written the exit ramp into the mission plan. The company said it would only fire the orbital insertion burn if flight controllers confirmed enough backup hardware remained for the deorbit burn, a condition Teslarati laid out ahead of the flight. Losing an engine was exactly the scenario that rule was built for.
Pressing forward fits Elon Musk’s history. Falcon 1 failed three straight times before its fourth launch reached orbit in 2008, with SpaceX nearly out of money, and Starship was developed by flying prototypes until they broke. What changed this year SpaceX going public, and with $SPCX sliding below its IPO price in July when Flight 13 slipped, the short interest climbed significantly, as Teslarati reported at the time. A Starship potentially lost today with revenue generating next-gen Starlink satellites aboard would have landed directly on shareholders.
Splashdown confirmed. Congratulations to the entire SpaceX team on the first orbital flight of Starship! pic.twitter.com/urjmiwnvNl
— SpaceX (@SpaceX) September 28, 2026
That pressure showed up after orbit. SpaceX cut a flight planned to last nearly 10 hours to about three, moving splashdown from west of Chile to the North Pacific near Hawaii. SpaceX gave no reason, though Musk said this month the company was being extremely cautious about debris risk. The single Raptor for deorbit worked, and Ship 41 completed its flip and landing burn before breaking apart in the water, an outcome SpaceX expected. Musk has structured SpaceX’s governance to shield long term bets from market pressure.
The payload is the bigger business story. Musk posted that all 26 Starlink V3 satellites deployed and are “operating nominally.” Each V3 is rated for about 1 Tbps of downlink and 160 Gbps of uplink, so this single launch adds roughly 26 Tbps, about 10 times what a Falcon 9 load of V2 Mini satellites adds. The V3 is too large for Falcon 9, making Starship the only vehicle that can build out the planned 100,000 satellite constellation, at up to 60 per flight once it reaches routine service. Unlike the 20 V3 units on Flight 13, which reentered on a suborbital path, these will raise their orbits and could begin serving customers within weeks and bring in hundreds of millions of additional dollars in projected Starlink revenue.
SpaceX has already begun winding down Falcon 9 Starlink launches from Florida in favor of Starship. Reported targets put Flight 15 as early as October 19, leaving about three weeks to diagnose Monday’s engine shutdown before the next orbital attempt.
Starship’s 14th flight is set to launch on Monday, Sept 28. The 75-minute launch window opens at 7:15 a.m. CT. Live coverage of the mission starts ~35 minutes before launch → https://t.co/uQKQvgaTmJ
— SpaceX (@SpaceX) September 27, 2026
Watch Tesla’s “guardian angel” FSD feature take over for collision evasion
Tesla Roadster event gets delayed due to unfavorable weather
