News
SpaceX’s Crew Dragon gets tentative NASA target for first astronaut launch
New information from both NASA and the US Government Accountability Office (GAO) confirm that SpaceX is currently targeting – at least very tentatively so – Crew Dragon’s first launch with astronauts aboard no earlier than November 15th, 2019.
SpaceX is currently in the midst of a complex, high-stakes anomaly investigation after its flight-proven DM-1 Crew Dragon capsule suffered a catastrophic failure on April 20th. That investigation is nowhere near full closure due to the fact that the interests of NASA and the Commercial Crew Program (CCP) are equally interwoven into the work involved. Given the potential consequences of a similar failure occurring with astronauts (public or private) aboard, NASA is unlikely to accept anything less than a no-stone-left-unturned analysis and failure resolution, including any necessary design changes to Crew Dragon, no matter how far-reaching.
As NASASpaceflight.com’s Chris Gerbhardt notes, the Crew Dragon-related dates included in the NASA Flight Planning Integration Panel (FPIP) document are extremely tentative. They’re really only there to serve as placeholders for longer-term International Space Station planning, already a necessarily uncertain endeavor. Nevertheless, NASA’s NET November 15th 2019 planning date for Crew Dragon DM-2 (the first crewed test flight) was likely okayed by SpaceX – if not provided outright by the company – before going into an official FPIP.
In other words, November 15th is probably a real target but should be treated as an absolutely-positively-no-earlier-than launch date for Crew Dragon’s first astronaut-laden mission to the ISS. Back in late March (after DM-1’s successfully completion but before the capsule’s ground failure), anonymous Russian space industry sources confirmed that NASA’s DM-2 planning date was July 25th, while also indicating that the space agency was already preparing for delays that could push DM-2 as late as November 2019.
Specifically, an anonymous Roscosmos source told Russian outlet TASS that “the [DM-2] launch of Crew Dragon is likely to be postponed to November”. Given that that delay was rumored – albeit quasi-officially – and reported on nearly a month before Crew Dragon capsule C201 catastrophically exploded during testing, it doesn’t exactly inspire confidence in a November 2019 DM-2 planning date officially released by NASA more three months later.
Crew Dragon stumbles, but optimism remains
As is often said, things were going perfectly up to the point that they weren’t. Despite 2-3 months of NASA paperwork and review-related delays, SpaceX’s first flightworthy Crew Dragon performed flawlessly during orbital rendezvous, docking, departure, and reentry to the extent that NASA and SpaceX officials were joking on-webcast about their partial disbelief. NASA’s lengthy post-mission review effectively concluded as much, although there is always room for improvement.
Due to those aforementioned DM-1 delays (roughly early January to early March), DM-2’s Crew Dragon assembly and integration was delayed in turn to preserve access in case DM-1 revealed flaws or necessary changes. Things didn’t quite go as planned, but the delayed integration has turned out to be beneficial, preserving access to most of Dragon 2’s critical subsystems without requiring major disassembly before any anomaly-related changes are implemented.

Per a late-May update from CCP manager Kathy Lueders, SpaceX has effectively shifted its Crew Dragon hardware assignments over one to account for the loss of the DM-1 capsule, C201. The vehicle previously assigned to DM-2 has been reassigned to a critical in-flight abort (IFA) test, previously meant to use flight-proven C201. Per charts provided during Lueders’ presentation, SpaceX’s replacement DM-2 capsule (likely the capsule previously assigned to the following mission, Crew-1) is in a sort of holding pattern to allow for modifications that may be required after the DM-1 failure investigation concludes.
Per a previous December 2018 update from Lueders, SpaceX’s original DM-2 spacecraft (now assigned to IFA) was expected to be fully assembled, shipped to Pad 39A, and ready for launch by June 2019. Accounting for DM-1’s delays, that spacecraft could likely be ready for the abort test as early as July or August, which meshes with post-anomaly indications that IFA is now scheduled no earlier than fall (September 2019)

All things considered, a pragmatic analysis suggests that Crew Dragon‘s DM-2 launch will most likely happen no earlier than Q1 2020, although miracles (and nightmares) are certainly possible. For the time being, all that really matters to SpaceX is wrapping up the C201 failure investigation as quickly and accurately as possible. Only after the company has publicly announced the results of that investigation should any IFA or DM-2 launch dates be taken with anything less than a full shaker of salt.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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.
Elon Musk
Tesla gears up Cybercab with Starlink for public debut, but with notable changes
Tesla is gearing up Cybercab, its all-electric and fully autonomous ride-hailing vehicle, for a very public debut as it plans to start customer deliveries in December. However, the units that rolled out of Gigafactory Texas this morning seem to differ from what we have seen previously.
Aerial images captured by drone photographer Joe Tegtmeyer at Giga Texas on November 18 reveal a noticeable update to the appearance of Tesla’s Cybercabs equipped with Starlink. Rows of gold production vehicles sit in the outbound lot, each carrying a flush-mounted Starlink V5 terminal on the rear hatch that looks more refined than the version first shown months earlier.
When Tesla first unveiled the integration in July and displayed a physical example in August, the Starlink hardware appeared as a relatively distinct rectangular panel on the hatch. Later September footage of large numbers of Cybercabs leaving the factory still showed a lighter, more obvious rectangular cover that roughly matched the vehicle’s gold paint:

Images via Joe Tegtmeyer
The newest batch stands out for how cleanly the cover blends into the roof’s character lines. Observers and replies to Tegtmeyer’s post describe the result as tighter and more intentional, sitting flush and following the body contours rather than reading as an added panel.
All of the Cybercabs in the latest images also wear prominent “Cybercab” logos on the doors and rear hatch, confirming these are finished production units rather than early prototypes. They are staged near the factory building, end-of-line areas, and covered transport trailers, with some already lined up for shipment.
The scale and consistency of the installation point to factory tooling rather than retrofit work.
A secondary detail noted in related sightings is a darker tone to the Starlink cover compared with earlier lighter panels. Tegtmeyer himself left open whether the darker finish is deliberate. There are a variety of explanations for it: perhaps for thermal performance, signal characteristics, or simple visual identification—or simply a batch variation still being refined.
Either way, the overall effect is a more integrated, production-ready appearance. For a Robotaxi that relies on Starlink for fleet connectivity, passenger services, and backup data links in areas with weak cellular coverage, the cleaner hatch design is more than cosmetic.
It signals that Tesla is polishing the final visual and hardware details as Cybercab volumes continue to climb at Giga Texas ahead of broader Robotaxi deployment. The vehicles now look to be built with Starlink instead of it being added afterward.


