Update: SpaceX says it and NASA are moving forward with plans to launch a Crew Dragon carrying US, Japanese, and Russian astronauts as early as noon EDT (16:00 UTC) on Wednesday, October 5th.
Concurring with a statement made on October 3rd, SpaceX has also called off a planned October 4th launch of its Starlink 4-29 mission. However, the company has delayed Starlink 4-29 just 24 hours and says that Falcon 9 will launch the latest batch of internet satellites out of California no earlier than (NET) 4:10 pm PDT (23:10 UTC) on October 5th. Intelsat has also confirmed that its Galaxy 33 and Galaxy 34 geostationary communications satellites are scheduled to launch on a Falcon 9 rocket as early as 7:07 pm EDT (23:07 UTC) on October 6th, leaving SpaceX on track to launch three Falcon 9 rockets from three launch pads in 31 hours.
The company achieved a similar feat earlier this year when it launched three Falcon 9 rockets in 36 hours. Three launches in 31 hours would break that record.
SpaceX is on the cusp of launching three Falcon 9 rockets in a handful of days. Minor issues with two of the three missions, however, have complicated the already hard process of coordinating so many launches at the same time.
For many reasons, rocket launches are an inherently difficult thing to schedule, and that difficulty only gets magnified when attempting to launch rockets as quickly as possible for customers with very different needs while using a fixed number of launch pads. SpaceX’s upcoming series of launches demonstrates the slippery nature of high-cadence rocket launch scheduling better than most.
Last month, SpaceX ran into issues (mainly bad weather) that delayed its Starlink 4-34, 4-35, and 4-36 missions by varying degrees. Before those delays, SpaceX had intended to break its LC-40 pad turnaround record with Starlink 4-35 and then repeat the feat with Starlink 4-36, but that opportunity closed when Starlink 4-34’s several weather delays pushed Starlink 4-35 from September 19th to the 24th and raised the risk of the next launch, Starlink 4-36, interfering with customer missions planned in the first half of October.
That burst of customer missions, all of which take priority over SpaceX’s own Starlink missions, meant that a few-day delay for a mission two launches prior ultimately pushed Starlink 4-36 from the end of September to no earlier than October 20th. It will launch out of Cape Canaveral Space Force Station’s (CCSFS) LC-40, the same pad that launched Starlink 4-35 on September 24th and will launch Intelsat’s Galaxy 33 and 34 satellites no earlier than (NET) October 6th and Eutelsat’s Hotbird 13F satellite NET October 13th. All four launches (including Starlink 4-36) are thus contingent upon each other, so a delay with one mission would likely delay each subsequent mission to leave enough time for pad turnaround and rocket processing.
Date Mission Rocket Location Pad 10/04/22 Starlink 4-29 Falcon 9 California VSFB SLC-4E 10/04/22 SES-20/21 Atlas V Florida CCSFS LC-41 10/05/22 Crew-5 Falcon 9 Florida KSC LC-39A 10/06/22 Galaxy 33/34 Falcon 9 Florida CCSFS LC-40 10/13/22 Hotbird 13F Falcon 9 Florida CCSFS LC-40 10/20/22 Starlink 4-36 Falcon 9 Florida CCSFS LC-40
SpaceX isn’t the only company that launches out of Cape Canaveral, Florida. Originally scheduled in late September, the United Launch Alliance’s (ULA) Atlas V launch of the SES-20 and SES-21 geostationary communication satellites was delayed by the same weather system that indirectly hampered Starlink 4-35 and 4-36. That mission is now set to launch NET 5:36 pm EDT (21:36 UTC) on October 4th.
Up first, however, is SpaceX’s Starlink 4-29 mission out of California’s Vandenberg Space Force Base (VSFB). Delayed to October 4th hours before its October 3rd target, the new schedule will give SpaceX “more time for pre-launch checkouts,” Falcon 9 will now lift off as early as 4:48 pm PDT (23:48 UTC), a little over two hours after Atlas V. However, making the whole situation even more interlinked, SpaceX says it will stand down from its October 4th Starlink launch attempt if its next Florida mission – Crew Dragon’s fifth operational NASA astronaut launch – remains on track for its current noon EDT (16:00 UTC), October 5th launch target.
In an October 3rd briefing following a mostly clean launch readiness review (LRR), NASA and SpaceX officials revealed that three new minor issues – “not showstoppers” – had appeared after a busy period of ground testing. An otherwise successful astronaut dry dress rehearsal and a subsequent wet dress rehearsal and static fire uncovered a possible fire extinguisher leak in the Dragon spacecraft and a minor issue with one of the Falcon 9 rocket booster’s nine Merlin 1D engines. A communications issue was also discovered on the SpaceX drone ship Crew-5’s rocket booster is meant to land on in the Atlantic Ocean.
SpaceX and NASA officials weren’t especially worried about the issues and were confident they would be resolved in time for an October 5th launch. If they aren’t and Crew-5 slips to October 6th, SpaceX should be able to launch Starlink 4-29 on October 4th, but then it’s unclear if the company will also be able to launch Intelsat’s Galaxy 33 and Galaxy 34 geostationary communications satellites on the same day as Crew-5. Galaxy 33/34 is scheduled to launch NET 7:07 pm EDT on October 6th, likely ~6 hours after Crew-5’s own October 6th launch window.
If Crew-5 slips and Galaxy 33/34 can’t launch on the same day, it would likely delay both Hotbird 13F and Starlink 4-36. It’s also unclear if Starlink 4-29 can launch on the same day as Crew-5 if it flies after Dragon. Either way, SpaceX could potentially end up launching Crew-5, Galaxy 33/34, and Starlink 4-29 on October 5th and 6th – potentially less than a day and a half apart.
As SpaceX continues to push the limits of what is possible with its existing Falcon launch and landing infrastructure, chaotic scheduling situations like this, where small issues impact large strings of launches, will become the norm instead of the exception
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.