News
SpaceX recaps historic Starship landing in 4K as next ship readies for flight
SpaceX has published a new 4K video recapping Starship’s first intact landing after a high-altitude launch right as the company is preparing the next ship for flight.
On March 3rd, Starship serial number 10 (SN10) briefly became the first prototype to successfully launch to 10 km (6.2 mi), ‘skydive’ back to Earth, flip around, and land in one piece. Put simply, Starship SN10 made it unequivocally clear that the exotic, unproven method of landing selected by SpaceX could be made to work. Unfortunately, while Starship SN10 did land in one piece, the landing was much harder than planned.
Due to some combination of that hard landing and an apparent onboard fire that started in the last ~20 seconds of flight, SpaceX only had around six minutes to contemplate its success before Starship SN10’s propellant tanks were breached, violently depressurizing the rocket and causing a large explosion and fire.
Previously discussed on Teslarati, SpaceX CEO Elon Musk later took to Twitter to offer some educated guesses as to why Starship SN10 exploded.
“Starship SN9 ultimately failed a few seconds earlier than Starship SN8 when one of its Raptor engines failed to ignite, precluding a true flight test of the helium pressurization fix. As it turns out, Musk believes that that very fix may have doomed Starship SN10.
As Starship SN10 forged ahead past the points of failure that killed SN8 and SN9, the SpaceX CEO thinks that one or more of the vehicle’s three Raptor engines began to ingest some of that helium as they drained the methane header tank. As a result, engine thrust fell below expected values, preventing Starship SN10 from fully slowing down for a soft landing. Instead, the Starship hit the ground traveling a solid 25 mph (~10 m/s), obliterating its tiny landing legs and damaging its skirt section.”
Teslarati.com – March 10th, 2021
In other words, the losses of Starships SN8, SN9, and SN10 all share a relatively common point of failure – propulsion reliability. Technically, only Starship SN9’s failure can be blamed specifically on Raptor, one of which failed to ignite during its flip and landing maneuver. SN8 and SN10 both failed because of issues in the complex network of plumbing and pressurization systems responsible for feeding Raptors the right amount of propellant.
For SN8, the ship’s pressurization system failed to provide the necessary fuel head pressure at the last second, starving the Starship’s Raptors. SN10 ironically failed because the quick fix inspired by SN8’s failure – partially replacing a methane pressurant with helium – likely contaminated its methane fuel with helium, effectively watering down Raptor’s performance. While likely frustrating for SpaceX, the failures are still extremely valuable and loss of hardware remains a routine and intentional part of the company’s approach to iterative rocket development.
On the plus side, the FAA has already cleared SpaceX’s next Starship for flight after SN10’s momentary success and subsequent explosion. Spurred by that brief taste of total success, SpaceX wasted no time to prepare that next prototype – Starship SN11 – for flight and rolled the rocket to the launch pad mere days after SN10’s March 3rd flight. That very same day, SpaceX completed ambient pressure testing – a basic verification that Starship SN11 is leak-free.
A few days later, SN11 appeared to pass its first cryogenic proof test, replacing room-temperature gas with cryogenic liquid nitrogen. Three days after that, SpaceX attempted to put the Starship through its first triple-Raptor static fire test but appeared to suffer an abort milliseconds after a partial ignition of one or two of its three engines. Starship SN11 briefly caught fire and burned for at least 20-40 seconds after the abort, unsurprisingly triggering several days of delays. Nevertheless, if SN11 can make it through a second static fire attempt without issue on Thursday or Friday, the Starship is still well on track to take flight weeks earlier than any of its predecessors.
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
