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.
Elon Musk
Tesla Cybercabs narrowly miss deadly Amazon cargo plane crash
An Amazon cargo plane crash near Miami’s airport stopped feet from dozens of Tesla Cybercabs.
An Amazon Prime Air Boeing 767 cargo jet overran the runway at Miami International Airport on Sunday afternoon, killing five people and injuring five more. The jet, operated by North Carolina based carrier 21 Air as Flight 7598, touched down around 2 p.m. after arriving from San Juan, Puerto Rico, then crossed the airport perimeter, plowed across NW 67th Avenue and struck multiple vehicles before catching fire, according to the Associated Press.
Photos and video from the scene show the aircraft’s nose stopped within meters of a fenced staging lot holding dozens of gold painted Tesla Cybercabs, the steering wheel free robotaxi Tesla began putting on public roads in Austin last week. Miami-Dade Fire Rescue has confirmed the plane struck “multiple vehicles” but has not said whether any Cybercabs were among them, and neither Tesla nor airport officials have addressed the fleet directly.
The Cybercabs had not yet entered commercial service in Miami. Tesla’s existing Robotaxi operation there runs on modified Model Y vehicles and has been unsupervised since Ashok Elluswamy confirmed the detail on X in July.
Footage of the plane crash from earlier today | #ONLYinDADE pic.twitter.com/iGoOtnd6cD
— ONLY in DADE (@ONLYinDADE) September 6, 2026
Elon Musk offered the briefest of reactions. Replying to a Zero Hedge post about the Cybercabs sitting so close to the wreckage, he wrote a single word: “Weird.” He has not commented further, and Tesla has not issued a statement.
The timing puts Tesla’s newest vehicle near an unrelated but highly visible tragedy just days after its Austin debut, a launch that had already drawn scrutiny from federal regulators. The National Highway Traffic Safety Administration opened an audit how Tesla certified the Cybercab as compliant with federal vehicle safety standards, a process Teslarati covered after the vehicle’s September 3 launch event. That inquiry concerns the car’s lack of a steering wheel and pedals, not the Miami crash.
Investigators from the FAA and NTSB are focused on the plane, not the parking lot beside it. Flight data reviewed by outlets including Simple Flying show the 767 touched down around 170 knots, well above the 135 to 140 knot range typical for the aircraft, though investigators have not determined a cause. Amazon said it is working with authorities and that its priority is the safety of everyone affected.
Whether any Cybercabs were damaged, and what Tesla plans for the fleet parked near one of the country’s busiest airports, remain open questions.
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.
Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.
Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla Cybercabs narrowly miss deadly Amazon cargo plane crash
Tesla crosses major Unsupervised Self-Driving milestone
