News
NASA says SpaceX astronaut launch debut is still on track despite pandemic, engine failure
Despite a global pandemic and Falcon 9’s first in-flight engine failure in almost eight years, NASA administrator Jim Bridenstine remains confident that SpaceX and the space agency are still on track for Crew Dragon’s astronaut launch debut.
For the third time in about a month, NASA has officially confirmed that SpaceX’s Crew Dragon ‘Demo-2’ mission – the company’s first astronaut launch ever – is still tracking towards a liftoff in May 2020. While there are several good reasons to expect further delays, Bridenstine acknowledged and discounted those pressing risks in an April 9th interview with Spaceflight Now, explicitly stating that “if [Demo-2 does] slip, it’ll probably be into June. It won’t be much.”
Excluding several minor to moderate technical risks that have popped up in recent weeks, this suggests that the NASA administrator is also confident that one of the biggest sources of imminent schedule uncertainty – closed-door paperwork completion and joint reviews – will actually be smooth sailing.
On March 2nd, 2019, Falcon 9 lifted off for the first time with SpaceX’s upgraded Crew Dragon spacecraft on its inaugural orbital launch. Known as Demo-1, the mission was ultimately a flawless success, with Dragon performing exactly as expected throughout launch, orbit-raising, space station rendezvous, docking, departure, deorbit, reentry, and splashdown operations.
As Crew Dragon’s only orbital launch and space station docking, it also serves as the best and only glimpse into how long the more nebulous review and paperwork aspects of launch preparation can take. For Demo-1, Falcon 9 and Crew Dragon rolled out to Launch Pad 39A and completed a successful static fire on January 24th, 2019. The mission was then scheduled for launch no earlier than (NET) February 23rd and wound up being pushed back another week to March 2nd. In almost every case, Falcon 9 and Falcon Heavy launch less than a week after a successful preflight static fire and do not attempt a static fire until a given rocket and payload are both ready to go.
If there were technical challenges that lead to that six-week delay between Crew Dragon’s Demo-1 static fire and launch, they have never been broached publicly, making it more likely that NASA spent at least a month simply finishing up final paperwork and reviews. Hopefully, that substantial gap was mainly due to the fact that it was the first time NASA and SpaceX had to work together to launch Crew Dragon.
For Crew Dragon’s second Falcon 9 launch, successfully completed on January 19th, 2020, the rocket wrapped up its static fire test on January 11th — a major improvement compared to Demo-1. That suborbital In-Flight Abort (IFA) test isn’t directly comparable to Crew Dragon’s orbital launch debut, but it does encourage at least a little confidence that Demo-1’s six-week review period was an outlier.
Thankfully, Bridenstine says that all major Crew Dragon issues have been effectively closed out or are very close to closure as of April 2020. A SpaceX contractor was recently forced to prematurely drop a Crew Dragon parachute test vehicle on March 25th, destroying the mockup capsule before it could complete two final tests. The NASA administrator now says that all parties have agreed to complete those tests with a different mockup and will use a C-130 cargo plane instead of a helicopter.
Bridenstine is also confident that the coronavirus pandemic – hampering almost all forms of industry in every afflicted country – will also have little to no impact on Crew Dragon’s astronaut launch debut schedule. NASA and SpaceX have put in place strict new rules and changed a number of procedures to further mitigate risk, helped by the fact that astronaut launches to the International Space Station (ISS) already operate with cleanliness and disease prevention as a major priority.
Finally, the NASA administrator also stated that SpaceX’s March 18th in-flight engine failure was “not going to impact our commercial crew launch,” confirming that SpaceX already has “a really good understanding of” what went wrong. Most likely, this means that Falcon 9 B1048’s stumble was directly related to the fact that the booster was flying for the fifth time – a first for a SpaceX rocket and orbital-class rocket boosters in general. Crew Dragon Demo-2 will be Falcon 9 booster B1058’s first launch.
Ultimately, while there are certainly good reasons to remain skeptical of NASA’s increasingly frequent assurances that Crew Dragon’s astronaut launch debut remains on track for late-May or June 2020, there are at least as many good reasons to stay confident.
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 launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.
Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
