News
SpaceX Falcon Heavy testing delayed after government shutdown
As the U.S. Senate’s majority party searches for ten additional votes in order to end a federal government shutdown that began late Saturday, all “non-essential” activities at the country’s numerous government-operated space launch facilities have ground to an immediate halt and will remain in limbo until a funding bill compromise is hammered out.
While SpaceX is a wholly private space launch company, it relies almost unilaterally upon launch support and range expertise provided by NASA and the US Air Force, both in Cape Canaveral, FL and Vandenberg, CA. Sadly, the Air Force personnel SpaceX depend upon to conduct launches, static fires, and other ignition tests at its launch pads are not considered “essential” under regulations that prevent the federal government from coming to a complete halt in the event of a funding-related shutdown.
Unfortunately, a budget agreement wasn't reached, resulting in a gov't shutdown. This will unfortunately disrupt the lives and operations here at Patrick AFB. Go to https://t.co/yvmNBH1LMy for info on the current shutdown, impact on base resources, & financial resource options.
— Space Launch Delta 45 (@SLDelta45) January 20, 2018
SpaceX did appear to complete the most thorough round of Falcon Heavy testing yet late Saturday evening, the US Senate’s failure to either pass a continuing resolution or a new funding bill for the fiscal year led to a complete federal government shutdown soon after. As a result, nearly all of the US Air Force’s 45th Space Wing – a crucial backbone of East coast range and launch operations – was furloughed indefinitely, pending new funding from Congress. SpaceX had previously requested a new static fire date for Falcon Heavy on Monday, January 22 (today), a date that is now clearly going to move right for at least as long as the government lacks funding for basic launch operations.
Thankfully, activities like the extensive propellant loading tests that occurred on Saturday night do not technically require range support, so long as no engine ignition or static fire components are included. In the event of a catastrophic failure, the government-run range would be tasked with ensuring the safety of those in the vicinity and coordinating the emergency response that would immediately follow. This policy is brought somewhat into question by the failure of Amos-6 – although that Falcon 9 was being prepared for a static fire test, its highly-destructive failure is understood to have occurred at least five or more minutes before the planned point of ignition. Nevertheless, SpaceX will be able to continue some level of testing with Falcon Heavy, if needed.
Elsewhere, instability
While SpaceX’s Falcon Heavy has undoubtedly garnered magnitudes more eyeballs than the company’s Falcon 9 activities, the government shutdown could be far more consequential for SpaceX’s customers if it cannot be halted within a handful of days. A federal shutdown lasting several days is a hugely disruptive and damaging event on its own, lack of range support on the East coast could quickly begin to eat into SpaceX’s GovSat-1 preparations, the launch of which is targeting NET late January/January 30. For GovSat-1’s flight-proven booster, a static fire at the launch site is unlikely to be bypassed (SpaceX has never skipped a prelaunch static fire), and would typically occur no fewer than four or five days before launch. As a result, in the somewhat unlikely event that the shutdown stretches beyond the next several days, SpaceX customers SES and GovSat could see their launch delayed, an event that would likely bring financial consequences to the public-private satellite venture.
Looking slightly farther into the future, SpaceX’s flight-proven launch of PAZ and two of its own prototype communications satellites is just about two weeks away from its own static fire test, this time at the West Coast’s Vandenberg Air Force Base. Such an extended shutdown would be utterly unprecedented, but if 2017 and 2018 have done anything at all, they’ve tempered tendencies towards knee-jerk claims of “that’ll never happen!”
-
- A panorama of LC-39A in November 2017. (Tom Cross/Teslarati)
-
- SpaceX’s Vandenberg launch complex, SLC-4E, depends upon an Air Force range to operate. (SpaceX)
-
- LC-40, located in Cape Canaveral Air Force Station, is SpaceX’s second pad. (Tom Cross)
Here’s to hoping that Congress can get their act together and return to those they represent the bare minimum of federal stability, for both federal employees and those that depend upon them.
Update: After a solid two days of shutdown, the Senate has apparently reached an agreement to pass a continuing resolution that will maintain funding for another three weeks, after which a new FY2018 budget must be passed to avoid another shutdown. While this thankfully means that the impact to the Space Coast and the Air Force’s 45th Space Wing should be relatively small, I have left my above thoughts on the potential impacts of a longer shutdown untouched for posterity.
Senate has voted on an amended bill to fund U.S. government for 3 weeks. Bill now heads back to the House for debate & vote. If it passes the House without changes, the President then needs to sign it into law. Once all those things happen, the government reopens. Then… 1/2
— Chris G (@ChrisG_SpX) January 22, 2018
Follow along live as launch photographer Tom Cross and I cover these exciting proceedings as close to live as possible.
Teslarati – Instagram – Twitter
Tom Cross – Instagram
Eric Ralph – Twitter
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
