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.
News
Verizon, AT&T and T-Mobile are trying to shut Starlink out before FCC vote
AT&T, Verizon and T-Mobile want 290 MHz cut from an FCC satellite plan before Thursday.
AT&T, Verizon and T-Mobile are asking the Federal Communications Commission to pull nearly 300 MHz of spectrum out of a proposal that would let satellite companies like SpaceX offer cell service directly to ordinary phones. The request lands one day before the agency votes on it.
The FCC will vote Thursday, October 29, on a notice of proposed rulemaking that would make an additional 482 MHz available for direct to device service, expanding the number of eligible bands from five to 13, according to the FCC fact sheet. It would also scrap the rule requiring a satellite operator to lease spectrum from carriers, replacing it with a certification that the operator has coexistence agreements in place or holds the terrestrial license itself.
That second path matters for SpaceX. As Teslarati reported earlier this month, SpaceX agreed to buy Grain Management’s nationwide 800 MHz portfolio to turn Starlink Mobile into a full US carrier, adding to the spectrum it already bought from EchoStar.
The carriers want two bands removed, 2.5 GHz and 3.45 GHz, which make up 290 MHz of the 482 MHz on the table. Through industry group CTIA, they argued that about 300 million users depend on those bands and that satellite operations in them are not technically feasible. T-Mobile, which calls 2.5 GHz the foundation of its Ultra Capacity 5G network, said in its own filing that satellite interference could wipe out up to 96% of a cell site’s uplink coverage area and cut uplink speeds by 88% to 99%.
Executives from all three carriers met with FCC staff on October 20, and T-Mobile CEO Srini Gopalan met separately with FCC Chairman Brendan Carr. T-Mobile’s role stands out because it is still SpaceX’s US launch partner for Starlink Mobile. The three carriers have also teamed up on their own satellite joint venture to pool spectrum, a move widely seen as a response to Starlink.
SpaceX is asking for the opposite. In an October 23 filing after meetings with FCC staff and commissioners’ offices, the company asked regulators to add the 902 to 928 MHz band to the proposal. “Doing so now saves time later,” SpaceX wrote. The company also asked the FCC to modernize interference rules and align satellite deployment requirements with those for terrestrial cell networks, saying the goal is to let satellite and ground networks work together so Americans stay connected wherever they are.
The carriers have not been shy about how they view SpaceX as a competitor. On Verizon’s third quarter earnings call Monday, its chief executive said Starlink Mobile “just can’t compete with a terrestrial network” and estimated SpaceX would need four to six years and $300 billion to $500 billion to build a full US carrier network.
Thursday’s vote will not settle which bands survive. Adopting the notice opens a public comment period, with final rules to come later in the proceeding. The FCC already considered and rejected 2.5 GHz for satellite coverage once, in 2024. SpaceX also is not the only satellite player watching: the FCC approved Amazon’s $11.6 billion acquisition of Globalstar on October 27, giving its planned direct to device fleet its own mobile satellite spectrum.
A Tesla Semi caught fire in Hayward, California, which caused both directions of traffic to shut down for hours before being completely reopened early on Wednesday, the California Highway Patrol said.
The fire occurred just after 5:30 local time in Hayward on Tuesday, as the Semi caught fire in the southbound lanes of I-880 before CHP officials made the decision to shut down both lanes of traffic due to potential risks from hazardous chemical smoke.
There were no injuries reported.
🚨 A Tesla Semi reportedly caught fire, with California Highway Patrol confirming. The Semi was on I-880 SB
An estimated 5,000 to 7,000 semi-truck and large commercial vehicle fires occur on U.S. roadways every year
— TESLARATI (@Teslarati) October 28, 2026
The cause of the fire is currently unknown, as neither Tesla nor the CHP have not determined a cause.
However, some images taken before the Semi was completely destroyed by the fire seem to indicate this might have been an older unit, as it appears to be one of the designs that Tesla shipped as part of its pilot program, before revising it and starting mass production just a month ago.
@Tslachan From on of the videos looks like it’s an old Semi (not the refresh version that recently started production) https://t.co/KzwmR2kXow
— Area Under The Curve 🎗️ (@AreaUnderCurve) October 28, 2026
At the time of publication, CHP had not returned our request for a comment for additional details, including the Semi involved and any potential collaboration on an investigation between the CHP and Tesla. We will update this story when we hear back from them.
The southbound lanes were reopened at 3:30 a.m. on Wednesday, with the northbound lanes opening last night a few hours after the fire began. The CHP did state that the lithium batteries were “incredibly difficult to extinguish,” according to NBC Bay Area.
The truck’s driver said that the Semi caught fire, but he did not have an explanation.
An estimated 5,000 to 7,000 semi-truck and large commercial vehicle fires occur on U.S. roadways every year.
Tesla’s launch of the “Emergency Drive Away” function a few months back offered owners a safe option to evacuate an area if they were in reasonable danger. The function finally got its first use in the real world, but it appears it was by mistake.
A video shared by u/Joshalander in the r/TeslaLounge subreddit recorded the instance from his vehicle and said the incident took place in Austin this past weekend during the city’s F1 Race.
“Was charging around 6 AM this past Sunday in Austin before heading to the F1 race and heard a pop. Looked over and saw the new emergency drive-away feature in action. Genuinely felt bad for the dude when he got out and realized what happened, since he looked exhausted and only seemed to half-read the prompts.”
🚨 Here’s the first look at Tesla’s Emergency Drive Away function in action:
Apparently this driver accidentally enabled it and drove forward; you can see the Supercharger pull with the car.
Tesla said previously this would cost up to $25k if not used properly. https://t.co/B4qQRrsO6B
— TESLARATI (@Teslarati) October 28, 2026
Emergency Drive Away unlatches the Supercharger connector from the vehicle, but still causes damage to both the car and the Supercharger. Tesla has said that it will cost up to $25,000 in repairs to have everything fixed back to normal.
Additionally, the company said that if it were not used in an emergency situation, the driver of the vehicle who activated the Emergency Drive Away feature would be responsible for all repair costs.
Tesla constitutes the following situations as reasonable justifications for activating the feature:
- You face an immediate threat to your life or personal safety.
- You must leave the area immediately.
- Exiting the vehicle is unsafe.
- Unplugging the charge connector would unreasonably delay your departure or expose you to a risk to your personal safety.
After using the feature, Tesla requires the driver to schedule Service so the car can be inspected.
Verizon, AT&T and T-Mobile are trying to shut Starlink out before FCC vote
Tesla Semi catches fire in California: what we know
