News
SpaceX almost loses Falcon 9 booster at sea
After more than a week at sea, the SpaceX Falcon 9 booster responsible for the company’s 100th successful landing finally returned to port on Wednesday, revealing that it nearly toppled into the sea during the recovery process.
Falcon 9 B1069 completed its first launch without issue early on December 21st, carrying a reused Cargo Dragon capsule into space and sending it on its way towards orbit and the International Space Station (ISS). Nine minutes after liftoff, it touched down on drone ship Just Read The Instructions (JRTI) without any apparent issue, more or less hitting the platform’s painted bullseye. While it’s difficult to determine with certainty, B1069 appeared to be in fine condition after landing, standing roughly straight up with all nine Merlin 1D engines well above the drone ship’s deck.
That was decidedly not the case when the once-flown Falcon 9 booster finally sailed into Port Canaveral eight and a half days later.

There remains plenty of ambiguity about how exactly things transpired after the landing but when B1069 was finally within eyeshot, the booster was significantly damaged, riding low on all four legs, inches away from falling off the drone ship’s deck, and only partially attached to the “Octagrabber” robot tasked with securing it. Based on photos of the damaged rocket taken by Teslarati photographer Richard Angle, most or all of B1069’s nine Merlin 1D (M1D) engines suffered likely irreparable damage to their fragile bell nozzles.

From the ragged nature of the damage to those nozzles, it appears that B1069 somehow fell on top of the drone ship’s Octagrabber robot during or after its recovery attempt, as the creases would be far cleaner if the booster had merely landed hard and pressed its M1D nozzles against the deck. But a very short fall onto Octagrabber still doesn’t quite explain the apparent damage to one of the booster’s landing legs or the fact that it’s sitting lower to the deck than usual – both potentially indicative of a hard landing.

What is clear, though, is that SpaceX struggled to secure the rocket shortly after its first landing. Per the CRS-24 webcast, B1069 landed just shy of dead center. Likely as a result of poor sea conditions, SpaceX was unable to quickly grab the booster with Octagrabber, which uses giant clamps and its own weight to hold Falcon first stages in place. B1069 then clearly slid around drone ship JRTI’s deck at the whim of the ocean. Before SpaceX could secure it, the booster slammed into the side of the drone ship hard enough to partially flatten a steel safety barrier that runs along its port and starboard beams – a barrier specifically put in place to prevent wayward boosters from sliding off the deck.
Thankfully, above all else, there is no obvious reason that SpaceX won’t be able to repair the damage that was wrought. Replacing all nine of B1069’s engines will heavily delay the booster’s return to flight and probably singlehandedly cost SpaceX at least $5-10 million, but that cost is still far less than scrapping it and building a new booster. Aside from that, it’s possible that B1069’s fall will preclude strict customers like NASA or the US military from reusing the booster to launch their payloads, which the booster would have otherwise been a shoo-in for with just a single NASA launch on its record.

While CRS-24 and B1069’s dramatic return was SpaceX’s last launch and booster recovery of the year, the company did safely recovery several other boosters sans damage in the days and weeks prior. On December 14th, Falcon 9 B1061 was spotted being craned onto dry land after its fifth launch – NASA’s tiny IXPE X-ray space telescope.
Falcon 9 booster B1067 arrived at Port Canaveral not long after but spent most of the winter holiday sitting on drone ship A Shortfall of Gravitas (ASOG) as many SpaceX employees took a well-deserved break. The thrice-flown booster was ultimately lifted onto the dock and broken over a few days before B1069 finally sailed into port, setting it up for a fourth launch in the very near future.
Ultimately, while the damage B1069 and JRTI’s Octagrabber seemingly suffered are a significant annoyance and will take a good deal of time and money to fix, SpaceX still has ten other operational Falcon 9 boosters ready to support a potentially record-breaking 2022 launch manifest.
News
Tesla’s Cybercab fleet just had its biggest day ever
Tesla registered a record 200 Cybercabs in one day, and Dallas could be next up.
Tesla added a record 200 Cybercabs to its Texas Robotaxi fleet in a single day, pushing the purpose-built two-seater past 750 registered units in the state. The batch landed on the Texas Department of Motor Vehicles automated vehicle register at 3:45 p.m. CT on November 17 and included 200 Cybercabs and one Model Y. Tesla’s Cybercab count had sat at 573 since late October before the jump.
The additions also put Tesla back ahead of Waymo on the register. Tesla now has 1,507 vehicles registered for driverless operation in Texas against Waymo’s 1,321, a lead of 186. Waymo had been ahead by 15 vehicles before the batch arrived. Tesla first passed Waymo on November 10, as Teslarati reported, before Waymo briefly moved back in front.
🚨 There are more CYBERCABS in the Tesla Robotaxi fleet in Texas than Model Y! https://t.co/BdRK2LnnAP — TESLARATI (@Teslarati) November 18, 2026
Cybercabs now make up 51.3 percent of Tesla’s registered Texas fleet, at 773 units against 734 Model Ys. Waymo’s fleet in the state is split between 874 Jaguar I-PACEs and 447 Ojai vehicles.
The register does not say where vehicles will operate, and registration does not mean a car is carrying riders. Still, the timing lines up with Tesla’s plans for Dallas. On the company’s third quarter earnings call in October, AI chief Ashok Elluswamy said, “next month, we’ll be launching in Dallas,” and a video posted over the weekend showed more than 50 Cybercabs parked in rows at a Dallas lot, with more on a car carrier nearby. Tesla has not announced a start date.
Dallas is already one of Tesla’s busiest Robotaxi markets. Model Y Robotaxis there have run without anyone in the driver’s seat around the clock since November 11, and the city logged 608,130 miles with no safety monitor between January 22 and October 18, second only to Austin, according to Tesla’s first Robotaxi Safety Report. Public Cybercab rides have been limited to Austin since the vehicle joined the service in September.
The fleet growth comes as Tesla shifts more of its factory capacity toward the Cybercab. The company is winding down Cybertruck production at Giga Texas by the end of summer 2027 to make room, and announced this week a €3 billion expansion of Giga Berlin with a new building designed to produce up to 1 million Cybercabs a year starting in 2029, as Teslarati covered.
Some Cybercabs will soon go to private owners too. Tesla began inviting select customers to buy the vehicle for personal use last week at $29,990 with a required $299 monthly Autonomy Subscription, with deliveries targeted for December in the same five Texas cities where Robotaxi operates.
News
Tesla Robotaxi takes over for Uber credits and loaners at Service locations
Tesla is now utilizing its in-house Robotaxi platform to give those waiting for their vehicles during Service visits rides instead of offering Uber credits or Loaner vehicles.
Tesla owners in Austin who bring vehicles in for service are receiving in-app prompts to use the company’s Robotaxi network while their cars are being worked on.
One recent notification, sent during a frunk repair, carried the heading “Try Robotaxi During Your Service Visit” and stated that while the vehicle is being serviced, the customer can take an autonomous Robotaxi ride to the next destination in Austin and download the Robotaxi app to get started.
Interesting. While my frunk gets fixed Tesla suggests taking a Robotaxi 😇 https://t.co/QiUbAmrp4a
— Wadesmith (@LanceWade) November 17, 2026
The suggestion arrives as Tesla has long relied on two main ways to keep customers mobile during longer service visits. Service centers have typically offered loaner vehicles drawn from a limited fleet; when those vehicles were unavailable, centers have issued Uber or Lyft credits. Uber credits were widely eliminated years ago, but some locations will still give them out.
Both approaches carry costs: loaner cars occupy inventory that could otherwise be sold, and third-party credits generate recurring expense.
Code discovered in Tesla app version 4.60.5 in September 2026 already listed “sv_transport_robotaxi” among the transportation options available for service appointments, alongside paid loaners and other alternatives, indicating the company had been preparing to route customers through its own autonomous fleet.
Your Tesla could be in the Robotaxi fleet next month, Elon Musk claims
Austin provides the clearest early example. The city remains Tesla’s primary Robotaxi market, with unsupervised Model Y and Cybercab vehicles operating across an expanded zone of roughly 400–440 square miles and running 24/7 since November 11. Public driverless service is also live in Dallas, Fort Worth, Houston, San Antonio, Miami, Orlando, and Tampa.
Directing service customers into this network keeps the vehicles utilized and reduces reliance on external rideshare credits, while giving owners practical experience with the Robotaxi app and vehicles during the repair window. Once service is complete, the same network can be used for the return trip without a staffed loaner handoff.
The Austin notification is the first public instance of the capability the September app code previewed. As Robotaxi expands into additional U.S. markets and the fleet grows, service centers in those cities are positioned to follow the same pattern, presenting autonomous rides as a primary transportation option during the service appointment rather than defaulting to loaner vehicles or third-party credits.
For customers, the change preserves mobility without the logistics of arranging a temporary car; for Tesla, it links the service operation more tightly to the expanding Robotaxi business.
Elon Musk
Sean Duffy fires back at Elon Musk over free Starlink
Sean Duffy says the FAA picked a ground network over Starlink, and Musk isn’t impressed.
Transportation Secretary Sean Duffy has responded to Elon Musk’s claim that the Federal Aviation Administration turned down free Starlink terminals before last week’s nationwide ground stop, saying the department chose a ground-based network after running into problems with an earlier version of the satellite service. Musk’s reply was a single emoji: “🤦♂️.”
Speaking at a press conference, Duffy said Starlink had been useful in some parts of the system. “I’ve worked well with Elon, and he, Starlink was a great solution for some of our assets in Alaska, but we sent Starlink, in one of its prior iterations, to our tech lab, and, there was some issues that we had to navigate, and we thought that the best method is to have a network that’s based on the ground,” Duffy said, according to a transcript published by ZeroHedge. “Now, I think what he’s doing with Starlink and the speed is remarkable, but, our airspace is very big. We have assets everywhere. And so, again, we used him for different parts of the airspace.”
Duffy did not dispute that the offer was made. He also did not say what problems the FAA found during testing.
The exchange started Monday, when Musk wrote on X, “Free Starlinks for FAA were offered to Sec Duffy, but he said they were not needed. As it turns out, they were,” as Teslarati reported. That post came three days after the FAA grounded departures nationwide on November 13, when its legacy equipment became unstable as data flooded its telecommunications network at 1,000 connection attempts every four to five seconds. The FAA traced the flood to a radar site in Amarillo, Texas, and a radio site in El Dorado, Arkansas, where L3Harris had been installing a new router. Roughly 12,462 flights were canceled that day.
As I was saying …
Free Starlinks for FAA were offered to Sec Duffy, but he said they were not needed. As it turns out, they were.
— Elon Musk (@elonmusk) November 16, 2026
Duffy has also signaled frustration with L3Harris, which runs the FAA’s current network. “I want to get away from L3Harris and get to a new one, but they own the network,” he said. “I can’t cancel the network that they own.” He has asked Congress for $50 billion to modernize air traffic control, arguing against “a patchwork, a fix to a system that’s critical for every single family.”
The FAA’s position on satellite links predates this week. In a July 2025 letter to lawmakers, FAA Administrator Bryan Bedford said the agency “would not use Starlink (or any satellite service) as the sole communications technology” for safety-critical air traffic services. Reuters reported at the time that the FAA was not considering replacing its L3Harris and Verizon contracts with Starlink. Verizon’s FAA Enterprise Network Services contract, awarded in 2023, is valued at up to $2.4 billion over 15 years.
Musk first pressed the issue in February 2025, while he was leading the Department of Government Efficiency, writing that “the Verizon system is not working and so is putting air travelers at serious risk” before correcting himself days later to blame L3Harris. SpaceX said at the time it was supplying Starlink kits to the FAA at no cost and had no intent to take over any existing contract.