News
SpaceX considers second Crew Dragon launch pad to reduce risk from Starship
Reuters reports that SpaceX has proposed modifying a second Florida launch pad to support Crew Dragon missions after NASA raised concerns about the threat posed by plans to launch Starship out of the only pad currently certified for Dragon.
After more than a year of downtime, SpaceX restarted the construction of an orbital Starship launch site at NASA’s Kennedy Space Center LC-39A pad in late 2021. SpaceX has leased Pad 39A since 2014 and conducted 49 Falcon rocket launches out of the facility since its first use in 2017. Prior to SpaceX’s lease, Pad 39A supported 82 Space Shuttle launches from 1981 to 2011 and every Apollo Program launch to the Moon in the 1960s and 1970s, making it one of the most storied and well-used launch sites in the history of US spaceflight.
In 2018, Pad 39A began supporting launches of SpaceX’s Falcon Heavy, which was and still is the most powerful and capable rocket currently in operation. In May 2020, a Falcon 9 rocket and Crew Dragon spacecraft lifted off with two NASA astronauts in tow, marking SpaceX’s first human spaceflight and the United States’ first domestic astronaut launch of any kind since 2011. The next era of the historic pad could include Starship, a fully-reusable two-stage rocket that SpaceX has been developing in earnest since the mid-2010s. However, NASA is worried that a failure of that immense and unproven rocket could almost instantly destroy what is currently the only launch pad on Earth capable of launching the space agency’s astronauts to the International Space Station (ISS).
One certainly can’t blame NASA for worrying. In its latest iteration, SpaceX’s Starship 39A launch mount will sit roughly 1000 feet (~300m) East of Pad 39A’s existing Falcon launch facilities, which include a tower and arm that are needed for astronauts and cargo to access and board Crew and Cargo Dragons. The Starship mount is also around 1600 feet (~500m) northeast of Pad 39A’s lone horizontal integration hangar, without which Falcon launch operations would become far more difficult or even impossible.
For the Falcon pad and tower, there is a slight consolation: Starship’s own skyscraper-sized launch tower will be located directly between those Falcon facilities and Starship before and during launches and could partially protect them from any hypothetical blast. The hangar will be fully unprotected, however.


NASA is worried that if a Starship fails before or shortly after launch and explodes at or near its adjacent launch mount, it could destroy or damage the infrastructure the space agency and SpaceX need to launch Crew Dragon to the International Space Station (ISS). At the moment, Boeing – NASA’s second Commercial Crew partner – is likely a year or more away from its first operational astronaut launch, during which Falcon 9 and Crew Dragon will remain a single point of failure that could theoretically sever the space agency’s connection to its own space station at any moment.
In response to NASA’s concern, NASA executive Kathy Lueders – in an interview with Reuters – says that SpaceX has begun working with the agency on plans to both “harden” Pad 39A and modify its Cape Canaveral Space Force Station (CCSFS) LC-40 pad to support Dragon launches. According to Reuters, however, receiving approval to put those plans into action “could take months.” Depending on how significant the facilities LC-40 would need are, there’s also a chance that SpaceX would need to complete a new FAA environmental review to construct a crew access tower.

Meanwhile, Pad 39A is also the only launch pad in the world capable of supporting Falcon Heavy, which has also become an extremely important rocket for uncrewed NASA spacecraft launches, NASA’s plans to get cargo to its lunar Gateway space station, and to the US military. Modifying one of SpaceX’s other pads to support Falcon Heavy would likely be even harder and take even longer than adding Crew Dragon capabilities to LC-40. In both cases, it’s likely that NASA and the US military would strongly prefer – if they don’t eventually outright require – that SpaceX have backup options already constructed and ready to go before risking the destruction of Pad 39A with its first Starship launch.
39A’s Starship facilities could easily require another 6-12 months of work before they’ll be ready for launch, however, leaving a good amount of time for SpaceX to alleviate the concerns of its US government customers before they might actually start to disrupt plans for East Coast Starship launches.
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.