News
SpaceX completes Falcon 9 test fire, space station supply mission up next
After almost exactly 15 months of dormancy, SpaceX’s Launch Complex 40 (LC-40) came to life with the roar of nine Merlin 1D rocket engines as Falcon 9 1035 conducted its second pre-launch static fire in preparation for the company’s 13th Commercial Resupply Services mission, CRS-13. Previously tasked with the launch of the CRS-11 Cargo Dragon, the booster completed its mission and returned safely to Landing Zone-1 (LZ-1) on June 3 2017. The path towards LC-40’s reactivation has delayed the launch approximately one week, but December 6th’s successful static fire bodes well for the current launch date, 11:46 AM on December 12.
Static fire test of Falcon 9 complete—targeting launch of CRS-13 on December 12 from Pad 40, followed by launch of Zuma from Pad 40 in early January.
— SpaceX (@SpaceX) December 6, 2017
On September 6 2016, LC-40 was effectively destroyed over the course of the Amos-6 failure. In months that followed, SpaceX reactivated LC-39A in order to continue chipping away at the company’s launch manifest, but also began the slow process of damage assessment and reconstruction of LC-40. It is safe to assume that almost every single component of the ground support equipment (GSE) was completely replaced, and interviews with Cape Canaveral’s 45th Space Wing commander suggest that SpaceX went further still, transforming the painful situation into an opportunity.
In an exclusive and frank conversation between Brig. Gen. Wayne Monteith and Florida Today’s Emre Kelly, the commander suggested that extensive design changes and additional hardening measures implemented during reconstruction are expected to make LC-40 exceptionally resilient to the rigors of rocket launches. Most tellingly, if perhaps overly optimistic, Monteith estimated that a second vehicle failure on the order of Amos-6 might only take two months to recover from, compared to the 15 months that followed Amos-6. He attributed this claim to GSE that is now largely buried underground, theoretically protecting the vast apparatus of hand-welded piping necessary to fuel the Falcon 9 launch vehicle. The replacement Transporter/Erector/Launcher (TEL) tasked with supporting Falcon 9 during integration and launch also appears to have been modernized, and will likely end up looking quite similar to the monolithic white TEL that resides at LC-39A.
Rocket and spacecraft for CRS-13 are flight-proven. Falcon 9’s first stage previously launched SpaceX’s eleventh resupply mission for @NASA, and Dragon flew to the @Space_Station in support of our sixth cargo resupply mission. pic.twitter.com/RY4F2TrWO2
— SpaceX (@SpaceX) December 6, 2017
With CRS-13’s static fire now complete, the mission is set to become the fifth operational reuse of a flight-proven Falcon 9 booster in 2017, thanks to NASA’s unusually rapid acceptance of the new practice. Further still, if Iridium-4’s December 22 launch date holds, and it does look to be stable for the moment, SpaceX will rather incredibly have conducted five commercial reuses of a Falcon 9 in its first year of operations, meaning that one third of SpaceX’s 2017 missions will have launched aboard flight-proven boosters. Also impressive is SpaceX’s full-stop move towards the reuse of Cargo Dragon capsules, and the company stated over the summer that it was hoping to almost completely redirect Cargo Dragon’s manufacturing facilities towards Dragon 2, also known as Crew Dragon. This was most recently reiterated several months ago and is presumed to still be the company’s goal moving forward, and CRS-12 is believed to have been the last “new” Cargo Dragon that will fly. CRS-13’s Dragon previously flew the CRS-6 mission in April 2015.

Photos shared privately with the author show CRS-13’s Falcon 9 to be covered in a graceful layer of soot from its previous recovery, similar in appearance to Falcon 9 1021 seen above. (Instagram/bambi_mydear)
In a December 6 tweet, SpaceX further confirmed that the deeply secretive Zuma mission, previously delayed from an early-November launch as a result of concerns about fairing defects, has now been moved from LC-39A to LC-40 and is understood to be targeting January 4 2018. This will give SpaceX approximately three weeks after the launch of CRS-13 to verify that everything is functioning nominally in what is essentially a new pad.
Meanwhile, with Zuma now officially moved to 40, LC-39A is completely free from routine operations, meaning that SpaceX’s ground crew can now work at will to ready the pad for the inaugural launch of Falcon Heavy, now aiming for early 2018. Aside from Falcon Heavy, recent FCC filings point to two additional SpaceX launches aiming for January, although slips are probable in light of CRS-13’s minor delays. Regardless, December and January are likely to be thrilling months for followers of the intrepid space exploration outfit.
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.