News
SpaceX wants to launch its next Starship ASAP
Contrary to recent comments from CEO Elon Musk, SpaceX appears to be forging ahead at full speed in a bid to launch its next Starship ASAP.
Known as Starship serial number 10 (SN10), the prototype is the latest in a series of four ships SpaceX has ultimately set aside from low(er)-altitude development testing. Starship SN8 – the first functional prototype to reach its full height – debuted on December 8th, 2020, blowing expectations out of the water with a failure mere seconds before the end of a more than six-minute flight test. According to Musk, had a fuel tank remained properly pressurized from start to finish, SN8 could have very well stuck the landing on the first try.
Two months later, after the better part of two weeks of licensing and static fire test delays, Starship SN9 attempted to carry the torch forward but suffered an unrelated failure slightly earlier than SN8’s. One of two Raptor engines failed to ignite for a high-risk flip and landing burn, causing the Starship to impact the ground even more violently than its predecessor. It’s unclear why the ill-fated Raptor failed to ignite or why the engine that did ignite appeared to experience a major failure shortly thereafter but rocket propulsion is extraordinarily difficult – and Raptor is near – or at – the end of that scale.
While SpaceX obviously hasn’t spun around and fixed a complex Starship propulsion issue in a matter of days, Musk eventually revealed his opinion that he, his engineers, or some combination of both “were too dumb” to exploit one obvious way to mitigate the risk of engine failure during flip and landing. That ‘obvious’ tweak: reignite all three of Starship’s available landing engines, not just two.
In theory, with a fast-enough response time, Starship could ignite all three Raptors, perform a supercharged flip from a belly- to tail-down orientation, and selectively shut off one of the engines based on the data from what is essentially a midair static fire. In the event that all three engines are performing nominally, Starship would shut down the least useful engine (i.e. the Raptor with the least leverage) for a gentle two-engine landing burn.
That said, the ship landing burn has a clear solution. My greatest concern is achieving good payload to orbit with rapid & full reusability, without which we shall forever be confined to Earth.— Elon Musk (@elonmusk) February 5, 2021
Impressively, Musk said that SpaceX would implement those changes immediately, attempting the first three-engine reignition as early as Starship SN10’s launch debut. Already at the launch pad when Starship SN9 lifted off, SpaceX revealed plans to launch SN10 as early as February 2021 at the end of SN9’s test flight webcast.
A few days prior to SN9’s ill-fated test flight, Musk had also stated that Starship SN10 would perform a “cryoproof” test and only then have its three Raptor engines installed. Instead, in an apparent change of plans, SpaceX installed Starship SN10’s Raptors – SN39, SN50, and an unknown third engine – from February 5th to 7th.
On Sunday, local longtime resident Mary (aka BocaChicaGal) received an official safety alert from SpaceX, signaling plans for an explosive Starship test of some kind as early as Monday, February 8th. Historically, those overpressure safety warnings have only been distributed when SpaceX is preparing for a Starship static fire attempt. In other words, it’s possible that Starship SN10’s very first test could be a live wet dress rehearsal (WDR) with flammable liquid oxygen and methane propellant. If that WDR goes well, SpaceX could move directly into a one, two, or three-engine static fire.
Of course, as SN9’s lengthy test period rubbed in, Starship is still in the prototype stage and is far from a mature system, meaning that it’s always safer to expect delays than an on-time performance. To be clear, it’s far more likely that SpaceX will perform a familiar “cryo proof” test with non-flammable liquid nitrogen – perhaps hoping to complete a cryoproof and static fire in the same test window.
Either way, stay tuned for updates and follow along with NASASpaceflight’s excellent live coverage in the event that SpaceX really is prepared to static fire Starship SN10 between 9am and 6pm CST (UTC-6) on Monday.
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
