News
SpaceX delays expendable Falcon 9 satellite launch for an unprecedented second static fire test
First reported by NASASpaceflight.com, SpaceX has delayed Falcon 9 B1047.2’s third and final launch due to issues with the booster’s Merlin 1D engines. Fascinatingly, the company has decided to perform an unprecedented second static fire test before going ahead with the launch of Spacecom’s AMOS-17 communications satellite.
As a result, AMOS-17’s nominal August 3rd launch date is now off the table as SpaceX prepares for a second Falcon 9 wet dress rehearsal (WDR) and booster ignition test. Assuming the issue(s) observed after the first static fire test on July 31st are fixed after test #2, scheduled no earlier than Friday, August 2nd, SpaceX will reconfirm Falcon 9’s new AMOS-17 launch date. According to payload manufacturer and launch liaison Boeing, AMOS-17 is now scheduled to lift off no earlier than Monday, August 5th.
In the ~10-year history of Falcon 9, a back-to-back preflight static fire of the same booster is unprecedented. Every SpaceX launch in history has been preceded by an on-pad wet dress rehearsal (WDR) and static fire test. This involves filling the integrated booster and upper stage (and payload, sometimes) to flight-levels with propellant and fluids (RP-1, LOx, helium, nitrogen, TEA/TEB) and performing a launch countdown that is a carbon copy up to the point of liftoff.
Including a brief ignition of the booster’s main engines, this test serves as a full-fidelity rehearsal that helps SpaceX empirically determine whether the rocket and launch pad are ready for flight. Of note, SpaceX’s wealth of integrated systems testing has uncovered hardware and software bugs that can then be fixed without adding any risk to expensive customer payloads.
SpaceX’s workhorse Falcon 9 has scrubbed and delayed pre-launch static fires many, many times in the past but a double-header static fire test with a flight-ready rocket is simply unprecedented. According to SpaceX, the decision to perform a second static fire prior to launching AMOS-17 was made because of a presumably faulty valve or valves associated with the booster’s (B1047) Merlin 1D propulsion, featuring nine semi-identical engines capable of producing more than 7600 kN (1.71m lbf) of thrust.
SpaceX says the questionable valve or valves were replaced less than 24 hours after the first static fire was completed and NASASpaceflight.com reports that the second static fire will occur no earlier than Friday, August 2nd. According to Boeing, a good second static fire will push the launch to NET August 5th, likely featuring a similar ~90-minute window in the late evening (EDT).
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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
