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 CEO Elon Musk revealed today on the social media platform X that legacy automakers, such as Ford, General Motors, and Stellantis, do not want to license the company’s Full Self-Driving suite, at least not without a long list of their own terms.
“I’ve tried to warn them and even offered to license Tesla FSD, but they don’t want it! Crazy,” Musk said on X. “When legacy auto does occasionally reach out, they tepidly discuss implementing FSD for a tiny program in 5 years with unworkable requirements for Tesla, so pointless.”
I’ve tried to warn them and even offered to license Tesla FSD, but they don’t want it! Crazy …
When legacy auto does occasionally reach out, they tepidly discuss implementing FSD for a tiny program in 5 years with unworkable requirements for Tesla, so pointless. 🤷♂️
🦕 🦕
— Elon Musk (@elonmusk) November 24, 2025
Musk made the remark in response to a note we wrote about earlier today from Melius Research, in which analyst Rob Wertheimer said, “Our point is not that Tesla is at risk, it’s that everybody else is,” in terms of autonomy and self-driving development.
Wertheimer believes there are hundreds of billions of dollars in value headed toward Tesla’s way because of its prowess with FSD.
A few years ago, Musk first remarked that Tesla was in early talks with one legacy automaker regarding licensing Full Self-Driving for its vehicles. Tesla never confirmed which company it was, but given Musk’s ongoing talks with Ford CEO Jim Farley at the time, it seemed the Detroit-based automaker was the likely suspect.
Tesla’s Elon Musk reiterates FSD licensing offer for other automakers
Ford has been perhaps the most aggressive legacy automaker in terms of its EV efforts, but it recently scaled back its electric offensive due to profitability issues and weak demand. It simply was not making enough vehicles, nor selling the volume needed to turn a profit.
Musk truly believes that many of the companies that turn their backs on FSD now will suffer in the future, especially considering the increased chance it could be a parallel to what has happened with EV efforts for many of these companies.
Unfortunately, they got started too late and are now playing catch-up with Tesla, XPeng, BYD, and the other dominating forces in EVs across the globe.
Tesla is backtracking on a strange adjustment it made to its in-car Navigation feature after numerous complaints from owners convinced the company to make a change.
Tesla’s in-car Navigation is catered to its vehicles, as it routes Supercharging stops and preps your vehicle for charging with preconditioning. It is also very intuitive, and features other things like weather radar and a detailed map outlining points of interest.
However, a recent change to the Navigation by Tesla did not go unnoticed, and owners were really upset about it.
For trips that required multiple Supercharger stops, Tesla decided to implement a naming change, which did not show the city or state of each charging stop. Instead, it just showed the business where the Supercharger was located, giving many owners an unwelcome surprise.
However, Tesla’s Director of Supercharging, Max de Zegher, admitted the update was a “big mistake on our end,” and made a change that rolled out within 24 hours:
The naming change should have happened at once, instead of in 2 sequential steps. That was a big miss on our end. We do listen to the community and we do course-correct fast. The accelerated fix rolled out last night. The Tesla App is updated and most in-car touchscreens should…
— Max (@MdeZegher) November 20, 2025
The lack of a name for the city where a Supercharging stop would be made caused some confusion for owners in the short term. Some drivers argued that it was more difficult to make stops at some familiar locations that were special to them. Others were not too keen on not knowing where they were going to be along their trip.
Tesla was quick to scramble to resolve this issue, and it did a great job of rolling it out in an expedited manner, as de Zegher said that most in-car touch screens would notice the fix within one day of the change being rolled out.
Additionally, there will be even more improvements in December, as Tesla plans to show the common name/amenity below the site name as well, which will give people a better idea of what to expect when they arrive at a Supercharger.
News
Dutch regulator RDW confirms Tesla FSD February 2026 target
The regulator emphasized that safety, not public pressure, will decide whether FSD receives authorization for use in Europe.
The Dutch vehicle authority RDW responded to Tesla’s recent updates about its efforts to bring Full Self-Driving (Supervised) in Europe, confirming that February 2026 remains the target month for Tesla to demonstrate regulatory compliance.
While acknowledging the tentative schedule with Tesla, the regulator emphasized that safety, not public pressure, will decide whether FSD receives authorization for use in Europe.
RDW confirms 2026 target, warns Feb 2026 timeline is not guaranteed
In its response, which was posted on its official website, the RDW clarified that it does not disclose details about ongoing manufacturer applications due to competitive sensitivity. However, the agency confirmed that both parties have agreed on a February 2026 window during which Tesla is expected to show that FSD (Supervised) can meet required safety and compliance standards. Whether Tesla can satisfy those conditions within the timeline “remains to be seen,” RDW added.
RDW also directly addressed Tesla’s social media request encouraging drivers to contact the regulator to express support. While thanking those who already reached out, RDW asked the public to stop contacting them, noting these messages burden customer-service resources and have no influence on the approval process.
“In the message on X, Tesla calls on Tesla drivers to thank the RDW and to express their enthusiasm about this planning to us by contacting us. We thank everyone who has already done so, and would like to ask everyone not to contact us about this. It takes up unnecessary time for our customer service. Moreover, this will have no influence on whether or not the planning is met,” the RDW wrote.
The RDW shares insights on EU approval requirements
The RDW further outlined how new technology enters the European market when no existing legislation directly covers it. Under EU Regulation 2018/858, a manufacturer may seek an exemption for unregulated features such as advanced driver assistance systems. The process requires a Member State, in this case the Netherlands, to submit a formal request to the European Commission on the manufacturer’s behalf.
Approval then moves to a committee vote. A majority in favor would grant EU-wide authorization, allowing the technology across all Member States. If the vote fails, the exemption is valid only within the Netherlands, and individual countries must decide whether to accept it independently.
Before any exemption request can be filed, Tesla must complete a comprehensive type-approval process with the RDW, including controlled on-road testing. Provided that FSD Supervised passes these regulatory evaluations, the exemption could be submitted for broader EU consideration.
Tesla CEO Elon Musk sends rivals dire warning about Full Self-Driving
Tesla backtracks on strange Nav feature after numerous complaints
