News
SpaceX completes Falcon 9 test fire, space station supply mission up next
After almost exactly 15 months of dormancy, SpaceX’s Launch Complex 40 (LC-40) came to life with the roar of nine Merlin 1D rocket engines as Falcon 9 1035 conducted its second pre-launch static fire in preparation for the company’s 13th Commercial Resupply Services mission, CRS-13. Previously tasked with the launch of the CRS-11 Cargo Dragon, the booster completed its mission and returned safely to Landing Zone-1 (LZ-1) on June 3 2017. The path towards LC-40’s reactivation has delayed the launch approximately one week, but December 6th’s successful static fire bodes well for the current launch date, 11:46 AM on December 12.
Static fire test of Falcon 9 complete—targeting launch of CRS-13 on December 12 from Pad 40, followed by launch of Zuma from Pad 40 in early January.
— SpaceX (@SpaceX) December 6, 2017
On September 6 2016, LC-40 was effectively destroyed over the course of the Amos-6 failure. In months that followed, SpaceX reactivated LC-39A in order to continue chipping away at the company’s launch manifest, but also began the slow process of damage assessment and reconstruction of LC-40. It is safe to assume that almost every single component of the ground support equipment (GSE) was completely replaced, and interviews with Cape Canaveral’s 45th Space Wing commander suggest that SpaceX went further still, transforming the painful situation into an opportunity.
In an exclusive and frank conversation between Brig. Gen. Wayne Monteith and Florida Today’s Emre Kelly, the commander suggested that extensive design changes and additional hardening measures implemented during reconstruction are expected to make LC-40 exceptionally resilient to the rigors of rocket launches. Most tellingly, if perhaps overly optimistic, Monteith estimated that a second vehicle failure on the order of Amos-6 might only take two months to recover from, compared to the 15 months that followed Amos-6. He attributed this claim to GSE that is now largely buried underground, theoretically protecting the vast apparatus of hand-welded piping necessary to fuel the Falcon 9 launch vehicle. The replacement Transporter/Erector/Launcher (TEL) tasked with supporting Falcon 9 during integration and launch also appears to have been modernized, and will likely end up looking quite similar to the monolithic white TEL that resides at LC-39A.
Rocket and spacecraft for CRS-13 are flight-proven. Falcon 9’s first stage previously launched SpaceX’s eleventh resupply mission for @NASA, and Dragon flew to the @Space_Station in support of our sixth cargo resupply mission. pic.twitter.com/RY4F2TrWO2
— SpaceX (@SpaceX) December 6, 2017
With CRS-13’s static fire now complete, the mission is set to become the fifth operational reuse of a flight-proven Falcon 9 booster in 2017, thanks to NASA’s unusually rapid acceptance of the new practice. Further still, if Iridium-4’s December 22 launch date holds, and it does look to be stable for the moment, SpaceX will rather incredibly have conducted five commercial reuses of a Falcon 9 in its first year of operations, meaning that one third of SpaceX’s 2017 missions will have launched aboard flight-proven boosters. Also impressive is SpaceX’s full-stop move towards the reuse of Cargo Dragon capsules, and the company stated over the summer that it was hoping to almost completely redirect Cargo Dragon’s manufacturing facilities towards Dragon 2, also known as Crew Dragon. This was most recently reiterated several months ago and is presumed to still be the company’s goal moving forward, and CRS-12 is believed to have been the last “new” Cargo Dragon that will fly. CRS-13’s Dragon previously flew the CRS-6 mission in April 2015.
Photos shared privately with the author show CRS-13’s Falcon 9 to be covered in a graceful layer of soot from its previous recovery, similar in appearance to Falcon 9 1021 seen above. (Instagram/bambi_mydear)
In a December 6 tweet, SpaceX further confirmed that the deeply secretive Zuma mission, previously delayed from an early-November launch as a result of concerns about fairing defects, has now been moved from LC-39A to LC-40 and is understood to be targeting January 4 2018. This will give SpaceX approximately three weeks after the launch of CRS-13 to verify that everything is functioning nominally in what is essentially a new pad.
Meanwhile, with Zuma now officially moved to 40, LC-39A is completely free from routine operations, meaning that SpaceX’s ground crew can now work at will to ready the pad for the inaugural launch of Falcon Heavy, now aiming for early 2018. Aside from Falcon Heavy, recent FCC filings point to two additional SpaceX launches aiming for January, although slips are probable in light of CRS-13’s minor delays. Regardless, December and January are likely to be thrilling months for followers of the intrepid space exploration outfit.
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
