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.
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.
Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.
Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
