News
SpaceX aims for a burst of December launches despite recent delays
Originally scheduled to launch on December 4, SpaceX’s thirteenth resupply mission to the International Space Station (ISS) has been pushed back to no earlier than Friday, December 15 after routine preflight checks identified potential contaminants in the Falcon 9 launch vehicle’s upper stage fuel lines.
The past six weeks have been something of an outlier in an otherwise relentless series of 2017 launches for SpaceX. In early November, defects in payload fairings were discovered at the company’s Hawthorne, CA factory and quickly traced to the Zuma mission’s fairing, at that point already vertical and prepared to launch from Kennedy Space Center. SpaceX chose to pause its launch indefinitely as it investigated the fairings already delivered to its several launch pads and began the process of either repairing or replacing those impacted. The CRS-13 Cargo Dragon mission soon took precedent as Zuma remained on hold.
A panorama of SpaceX’s newly-reactivated Launch Complex 40. Falcon 9 and Dragon can be seen in the center. (Tom Cross/Teslarati)
Although CRS-13 does not require a payload fairing and was thus unaffected by SpaceX’s ongoing investigation, the mission was scheduled to be launched from Launch Complex-40, essentially a new pad after ten months of extensive repairs and upgrades. This translated into a few days of additional delays as the SpaceX launch crew thoroughly tested the pad’s new systems and pushed towards static fire of the flight proven Falcon 9 booster, successfully completed on December 6 after an additional handful of days of pad-related delays. This pushed the launch date from the 4th to the 8th, then the 12th and the 13th to accommodate further limited testing in order to ensure pad readiness. However, routine tests revealed a possible fuel line contamination in Falcon 9’s second stage, and SpaceX delayed the mission an additional 48 hours to resolve the problem. CRS-13 is now aiming for launch no earlier than 7:35am/10:35am PST/EST on December 15, but the window is instantaneous and any additional delays would push the launch into late December, at which point Cape Canaveral Air Force Station returns to operational status with the conclusion of winter holidays.
Although LC-40 suffered through its own teething period of bugs and testing while returning to life, there is a certain irony in the fact that a bug in the only wholly new component of CRS-13’s Falcon 9 rocket has been the most recent cause of delay; both the Falcon 9 booster and Cargo Dragon capsule are refurbished, flight-proven hardware, although both the trunk and heat shield of the Dragon were likely replaced with new components. There is something to be said about the logical nature of truly “flight-proven” hardware being more trustworthy than completely new alternatives, but it is far more likely that the upper stage contamination can be largely traced back to the new pad hardware.
A refurbished Dragon perched upon its flight-proven Falcon 9 first stage, separated by the uncooperative second stage. (Tom Cross/Teslarati)
Although Teslarati’s launch photographer Tom Cross has been battered about by Zuma and CRS-13 delays, SpaceX has demonstrated an admirable level of patience and caution, risking significant delays to their launch manifest in order to best ensure the safety and reliability of their launch services. While delays are painful in the spaceflight fan business, they are impermanent and secondary to safety and success. SpaceX will undoubtedly return to their regular programming in no time at all, with the West-coast launch of Iridium-4 and first pad rollout of Falcon Heavy up next on the docket. Stay tuned!
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
