News
SpaceX’s Crew Dragon settles on Feb 9 launch debut as Falcon 9 nears static fire
Update: NASASpaceflight.com is reporting that ISS planning documents suggest that Crew Dragon’s first launch has slipped into the second half of February, perhaps February 16th.
In the midst of several confusing delays, schedule updates, and official statements, the orbital debut of SpaceX’s Crew Dragon spacecraft has made its way onto the Eastern range’s planning schedule for the first time, placing Falcon 9 B1051’s static fire and Crew Dragons launch no earlier than (NET) January 23rd and February 9th, respectively.
As the brand new spacecraft’s first attempted trip to orbit, the demonstration mission (Demo-1/DM-1) will be performed without crew aboard, allowing SpaceX and NASA an opportunity to fully verify performance and explore Crew Dragon’s capabilities without risking the lives of the astronauts that will step inside a nearly identical vehicle as early as June or July.
Obviously preliminary, but the Eastern Range is now showing the Static Fire for the DM-1 mission's Falcon 9 (B1051.1) as NET January 23, (and still showing NET February 9 as the launch date). As always, but especially this one, all very much subject to change. pic.twitter.com/EWOEpbpI9o
— NSF – NASASpaceflight.com (@NASASpaceflight) January 17, 2019
The US government has been shut down for more than four weeks as a consequence of the inability of elected representatives to pass and sign a funding bill, now the longest shutdown in the country’s history. As a result, more than 95% of NASA’s workforce has been furloughed, leaving around 800 people left working (without pay) across the agency in positions or groups deemed absolutely essential to avoid loss of life or property damage.
How NASA defines “essential” is unknown but it seemed improbable that the Commercial Crew Program – around six months away from actually launching astronauts and presently marked by NASA’s attempts to complete reams of approval and certification paperwork – would fall under that extremely narrow umbrella. Delays to Crew launches are unlikely to harm hardware or directly risk harm to astronauts, although a very tenuous case could be made that delays to the program now would snowball and cause the debut of operational crewed launches to slip so far into 2019 (or even 2020) that NASA could lose assured access to the International Space Station (ISS) for several months. Again, there is no obvious way that a slip like that would actually increase the risk to life or limb for astronauts and hardware/infrastructure.
Apparently, Demo-1 and 2 don't need FAA launch licenses (under auspices of NASA, like TESS launch. Post-certification missions will require FAA license, like CRS flights today
— Irene Klotz (@Free_Space) January 16, 2019
Despite the logical improbability that NASA’s Commercial Crew Program (CCP) would – at this point in time – remain operating at full capacity during an extended government shutdown, NASA provided a statement to The Atlantic earlier this week more or less implying that CCP was deemed essential and has continued to operate for the last several weeks. There is certainly some wiggle room in NASA spokesman Bob Jacobs’ comments, enough to make it ambiguous if they are primarily PR spin, frank honesty, or something in between.
A SpaceX spokesperson added [paraphrased by The Atlantic] that “if NASA made the call, the company would carry out the uncrewed [DM-1] launch”, a tactical nonanswer that redirects the impetus to NASA. It’s not clear if the people at NASA that would ‘make the call’ to launch are furloughed or not – they certainly would not be essential in the sense described by NASA’s own overview of the current shutdown’s impact. Originally targeting a launch sometime in mid to late January, an official NASA update posted on January 10th showed that Crew Dragon’s first launch had slipped into February (on the launch range for February 9th).
- DM-1 and Falcon 9 were greeted by an extraordinary – albeit mildly bittersweet – dawn during their first-ever trip out to Pad 39A. (SpaceX)
- The integrated DM-1 Crew Dragon ‘stack’ rolled out to Pad 39A for the first time in the first few days of 2019. (SpaceX)
- Falcon 9 B1051 and Crew Dragon vertical at Pad 39A. (SpaceX)
- Crew Dragon shows off its conformal (i.e. curved) solar array while connected to SpaceX’s sleek Crew Access Arm (CAA). (SpaceX)
- DM-2 astronauts Bob Behnken and Doug Hurley train for their first flight in Crew Dragon. (NASA)
“NASA and SpaceX are now targeting no earlier than February for the launch of Demo-1 to complete hardware testing and joint reviews.” – NASA, 01/10/2019
“Hardware testing” likely refers to the need for Falcon 9 to complete a static fire at Pad 39A, a test now scheduled for January 23rd. It’s ambiguous whether SpaceX can actually perform a static fire test – a complete launch rehearsal involving full propellant loads and the ignition of all nine Merlin 1D engines – at Kennedy Space Center, a NASA operated with federal funding that does not currently exist. Although the Air Force-helmed range is operating at a normal capacity, KSC must still perform a number of basic tasks ranging from infrastructure maintenance to roadblock setup to allow a static fire test – let alone a launch – to occur. I
f SpaceX completes its NET January 23rd static fire with no problems, then it would appear to be the case that some sort of SpaceX-side delay – perhaps augmented or slowed down by NASA operating at 5% capacity – caused the slip from mid-January to mid-February. Stay tuned to find out!
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
