News
SpaceX Crew Dragon In-Flight Abort test gets its first firm launch date
The day after questions arose around the targeted launch date of SpaceX’s Crew Dragon In-Flight Abort test (IFA), SpaceX and NASA have officially set the date for the spacecraft’s next major flight test.
On Friday, December 6th, a NASA Commercial Crew Program blog post confirmed a NET date of Saturday, January 4th, 2020 for the IFA test. The IFA test is one of the most notable final steps to be completed by the Crew Dragon capsule prior to supporting crewed astronaut flight to the International Space Station in 2020 as a part of NASA’s Commercial Crew Program.
Following an apparent incorrect statement made during SpaceX’s CRS-19 webcast that identified a February 2020 target date of the IFA test, SpaceX provided re-assurance that teams were very much still working toward a NET December launch date.
A January 4th date falls just short of SpaceX’s December goal but it still comes as little surprise. In addition to this week’s CRS-19 launch, SpaceX aims to support two more launches prior to year’s end – an internal mission to launch 60 more Starlink satellites and the launch of the JCSAT 18/Kacific 1 communications satellite for customers SKY Perfect JSAT Corp. of Japan and Kacific Broadband Satellites of Singapore. While completing four Falcon 9 launches and landings in a period of less than four weeks is certainly possible for SpaceX, it was rather ambitious, especially given that Crew Dragon’s abort test is almost certainly the company’s preeminent priority.
The targeted January launch date now encroaches into the first quarter of 2020, which SpaceX has adamantly stated is also the goal for Crew Dragon’s first NASA astronaut launch, known as Demo-2. With the IFA test now NET January 4th, it will be a major challenge for NASA and SpaceX to turn around and prepare Crew Dragon and Falcon 9 for Demo-2 just 4-12 weeks later. Of note, Boeing is preparing its own Starliner spacecraft for an uncrewed launch test NET December 20th and has also claimed that it wants to launch a crewed flight test (CFT, akin to SpaceX Demo-2) as early as February 2020, same as SpaceX.
It’s extremely unlikely that NASA will be able to preserve both of those schedules given the Commercial Crew Program’s fixed workforce and the vast quantity of paperwork it must complete before the agency can give the go-ahead for SpaceX and Boeing astronaut launches.
Unsurprisingly, the blog post confirmed that the IFA test would launch from Kennedy Space Center Launch Complex 39A (LC-39A). Pad 39A is the same facility that previously supported Crew Dragon’s March 2019 Demo-1 launch debut and is the only pad SpaceX intends to launch Crew Dragon from.
Interestingly, Pad 39A is also an active construction site – SpaceX is in the midst of building a new launch mount and modifying existing facilities to support future launches of SpaceX’s next-generation Starship vehicle. Construction has been underway for a few months and is situated directly beside Falcon 9 and Falcon Heavy’s exiting launch mount.
Although that construction will not be allowed to interfere with Crew Dragon launch activity, including the IFA test, construction on the Starship mount will likely be impacted. Construction crews will undoubtedly be expected to evacuate the area surrounding the launchpad during any Falcon 9 static fire test or launch, likely translating to a few days to a few weeks of downtime depending on how SpaceX handles the scheduling.
As 2019 comes to a close, SpaceX remains determined to launch Crew Dragon’s IFA test as quickly as is safely possible. If all goes perfectly during the upcoming abort test, SpaceX says it is seriously targeting Crew Dragon’s biggest test yet – its inaugural astronaut launch – less than two months later in February 2020. It should go without saying that that schedule is incredibly ambitious and highly liable to slip in March or Q2, but if the ambition is there, SpaceX believes it is technically possible.
For now, we have less than a month to wait for Crew Dragon’s next launch milestone and perhaps just 2-3 weeks before the spacecraft and its Falcon 9 rocket roll out to Pad 39A to prepare for a routine static fire test.
Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes.
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
