News
Report: SpaceX to launch at least five back-to-back Crew Dragon missions for NASA
Update: Wasting no time at all, NASA has confirmed the Ars Technica report one day later, announcing that rookie astronauts Nicole Mann and Josh Cassada have been reassigned from Boeing Starliner missions to SpaceX’s Crew-5 Crew Dragon launch – currently no earlier than August 2022.
Ars Technica’s Eric Berger reports that NASA has begun the process of moving a number of astronauts assigned to Boeing’s ailing Starliner spacecraft to a SpaceX Crew Dragon mission scheduled no earlier than August 2022.
Per sources close to Berger, NASA has chosen to reassign two rookie astronauts to Crew Dragon as hopes of a crewed Starliner launch – and thus an opportunity for them to gain hands-on spaceflight experience – in the next 6-12 months continue to wither. Barring surprises, the implied change of plans behind those actions means that SpaceX now appears to be scheduled to fly five operational NASA Crew Dragon missions back to back before Boeing’s Starliner flies a single astronaut – let alone its first operational mission with four crew aboard.
In December 2019, nine months after Crew Dragon’s own uncrewed March 2019 debut, Starliner lifted off for the first time on a ULA Atlas V rocket. However, whereas Crew Dragon performed a practically flawless orbital launch, space station rendezvous, docking, departure, reentry, and splashdown on its first try, Starliner’s Orbital Flight Test (OFT) went horribly wrong as soon as it separated from Atlas V.
Due to shoddy prelaunch testing that failed to detect several gaping holes in Starliner’s software, the spacecraft effectively lost control as soon as it was under its own power. Aside from making ground communication and control far harder, Starliner burned through most of its propellant and pushed most of its maneuvering thrusters past their design limits in the first hour or two after launch. Due to the catastrophic software failure and lack of propellant margins, NASA unsurprisingly called off a planned space station rendezvous and docking attempt and Boeing ultimately ordered Starliner to reenter a few days after launch.
Mere hours before reentry, Boeing apparently detected and fixed another major software error at the last second, potentially preventing Starliner’s propulsion and service module from smashing into the capsule’s fragile heat shield and dooming the spacecraft to burn up during reentry. Ultimately, it’s likely that the only reason Boeing didn’t suffer a total loss of vehicle (LOV) during Starliner’s OFT debut spacecraft was dumb luck. Had the initial clock error been worse, Starliner could have failed to reach orbit entirely or burned through all of its propellant, resulting in an uncontrolled reentry. Had there been no clock issue, it’s hard to imagine that Boeing’s software team would have attempted the panicked, impromptu bug hunt that detected and fixed the service module recontact issue.
Now, 22 months after Starliner’s catastrophic OFT, Boeing has been forced to stand down from a second self-funded orbital flight test (OFT-2) due to the last-second discovery of more than a dozen malfunctioning valves on the second spacecraft’s service module. Aside from raising the question of how Boeing and NASA yet again failed to detect a glaring Starliner issue until the day of launch, Starliner’s valve issues appear likely to cause another multi-month delay as Boeing is forced to investigate the problem, find the root cause, and implement a fix on all impacted service modules.
NASA reassigning some of the astronauts scheduled to helm Starliner on its Crewed Flight Test (CFT) and first operational mission to Crew Dragon’s August 2022 Crew-5 launch seemingly implies that the space agency is not confident that Boeing will have completed Starliner OFT-2, passed extensive post-flight reviews, and readied another Starliner for CFT by Q3 2022. Given that NASA took some 14 months to OK Crew Dragon’s Demo-2 crewed flight test after Demo-1’s March 2019 success and a catastrophic April 2019 failure during a ground test of the recovered capsule, it’s not unreasonable to assume that NASA will take about a year after OFT-2 to approve Starliner’s first crewed flight test.
If significant issues arise during OFT-2, which is now unlikely to occur before early 2022, a year-long gap is even more likely. Ultimately, that means that there is now a significant chance that SpaceX’s Crew Dragon spacecraft will complete not just five – but six – back-to-back operational NASA astronaut launches before Starliner is ready for its first operational ferry mission. SpaceX, in other words, is now expected to singlehandedly hold the line and ensure biannual NASA access to and from the International Space Station (ISS) for more than two years despite charging NASA $2 billion less than Boeing (~$5B vs ~$3B) to develop Crew Dragon.
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
