News
SpaceX operational astronaut launch debut back on track after “nail polish” delay
In a new NASA briefing, SpaceX vice president of build and flight reliability Hans Koenigsmann was able to explain in far more detail why a recent last-second Falcon 9 launch abort happened and how it wound up delaying the company’s first operational astronaut launch.
Now scheduled to lift off no earlier than (NET) 7:49 pm EST (00:49 UTC) on Saturday, November 14th, SpaceX’s Crew Dragon Crew-1 mission was originally expected to launch in late September, October 23rd, and October 31st. On October 2nd, however, a new Falcon 9 booster – sibling to Crew-1’s own new booster – automatically aborted its GPS III SV04 satellite launch attempt just two seconds before liftoff. The rare last-second abort was quickly blamed on “unexpected pressure rise in the turbomachinery gas generator” by CEO Elon Musk.
Likely built side-by-side with faulty GPS III SV04 Falcon 9 booster B1062 at SpaceX’s Hawthorne, California factory, Crew-1 Falcon 9 booster B1061 was almost immediately inspected to search for any commonality once the cause of the abort was better understood.
Just one week before the latest briefing, NASA human spaceflight program administrator and former Commercial Crew Program manager Kathy Lueders revealed in a statement on Twitter that SpaceX was still analyzing the cause of the abort but had already determined that at least one Crew-1 booster engine would need to be replaced, as well as one engine on Falcon 9 booster B1063.
Now, during NASA’s October 28th Crew-1 briefing, SpaceX’s Koenigsmann revealed that the company had ultimately decided to replace not one but two of Crew-1 booster B1061’s nine Merlin 1D engines. Thanks to Falcon 9’s namesake nine-engine booster design and SpaceX’s prolific rocket factory, that process was completed extraordinarily quickly, simply requiring the redirection of already qualified Merlin 1D engines from a fairly large pool. Based on Koenigsmann’s phrasing, SpaceX has already installed both replacement engines on the Crew-1 booster.
What, though, caused GPS III SV04’s launch abort and how did that affect Crew-1?
Rocket engine vs. “nail polish”
According to Koenigsmann, in the course of the rapid and complex mechanical and electrical ballet preceding Falcon 9 first stage ignition, the rocket’s autonomous flight computer observed that two of the GPS III SV04 booster’s nine Merlin 1D engines appeared to be running ahead of schedule, so to speak. The computer immediately halted the ignition process to avoid what could have otherwise been a “hard” (i.e. stressful or damaging) start. SpaceX quickly began inspecting the rocket within 24 hours but was unable to detect anything physically or electrically wrong with Falcon 9’s Merlin 1D engines and engine section.
Out of an abundance of caution, SpaceX removed both misbehaving engines and shipped them to its McGregor, Texas development and test facilities where – somewhat miraculously – the same premature startup behavior was replicated on the test stand. After a great deal of increasingly granular inspections, SpaceX finally narrowed the likely cause down to a tiny plumbing line feeding one of the engine’s gas generator relief valves. In a seemingly random subset of relatively new Merlin 1D engines, SpaceX eventually discovered that a supplier-provided relief valve line was sometimes clogged by a protective lacquer Koenigsmann likened to “red nail polish.”
Used to selectively exclude parts of the engine tubing during a surface finishing process known as anodization, the lacquer was either unsuccessfully removed on a random selection of engine parts or was accidentally channeled into a blockage by over-enthusiastic cleaning. Ultimately, for whatever, reason that miniscule blockage was enough to cause affected Merlin 1D engines to consistently attempt to ignite a tiny fraction of a second early.
Crucially, when SpaceX discovered the possible cause and cleaned out the blocked plumbing, each previously affected Merlin 1D engine performed perfectly, all but directly confirming both the cause and the cure for Falcon 9’s October 2nd abort.
Astronauts enter quarantine
In anticipation of SpaceX seemingly simple solution to the gas generator problem, NASA Commercial Crew Program manager Steve Stich revealed that SpaceX’s Crew-1 mission astronauts – Shannon Walker, Victor Glover, and Mike Hopkins, and JAXA (Japanese) astronaut Soichi Noguchi – had begun routine prelaunch quarantine procedures in anticipation of a November 14th launch.
Stich also offered a more specific Crew-1 schedule, beginning with an integrated Falcon 9 and Crew Dragon static fire test NET November 9th and a full dry dress rehearsal on November 11th before the first launch attempt on November 14th. Notably, thanks to coincidental orbital dynamics, a successful launch on November 14th would enable Crew Dragon to raise its orbit and rendezvous with the International Space Station a brisk eight and a half hours after liftoff – three times quicker than the more common 27.5-hour transit.
Stay tuned for updates as the mission’s launch date approaches.
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
