News
SpaceX Starship go for nosecone installation after historic static fire
SpaceX CEO Elon Musk has confirmed that Starship and Raptor’s first triple-engine static fire was a success, opening the door for nosecone installation.
Around 3:13 am CDT, October 20th, Starship serial number 8 (SN8) successfully fired up three Raptor engines less than two hours after completing the first successful three-engine preburner test. With zero direct human intervention, SpaceX remotely detanked the rocket’s cryogenic liquid methane and oxygen propellant – the remnants now too warm to be used again in a controlled manner. In an hour or less, SpaceX engineers combed through the data produced and concluded that all three Raptor engines were healthy after their partial ignition test.
Effectively reset to a stable state, SpaceX once again proceeded to load Starship SN8’s propellant tanks with a small amount of supercooled LOx and LCH4, almost exactly mirroring the preburner test. Around 50 minutes after the recycle commenced and 25 minutes after propellant loading kicked off, Starship SN8 ignited three Raptors simultaneously – a major milestone for any rocket engine. Static fire now completed, Starship SN8 has been cleared to become the first operational prototype to reach its full 50m (~165 ft) height.
Shortly before Musk confirmed SN8’s static fire success, SpaceX canceled a preexisting October 20th static fire window and scheduled several new road closures on Wednesday, October 21st. Unlike the company’s recent static fire closures, all but one of which ran from 9pm to 6am, SpaceX’s new Wednesday closures are scheduled from 7am to noon and 3pm to 5pm local (CDT).
While a minor data point, in context with Starship SN8’s static fire success, the closures alone made it clear that SpaceX planned to begin installing Starship SN8’s nosecone on October 21st. Musk confirmed that assumption a few hours after those road closures were published.
It’s not entirely clear but most observers are assuming that Wednesday’s 7am-12pm window is needed to transport a large, new crane the ~2 miles between SpaceX’s Boca Chica factory and launch facilities. Starship SN8’s stacked nose section would then likely be installed on the same self-propelled mobile transporters (SPMT) and rolled to the launch pad from 3pm to 5pm, after which the nose would be lifted and stacked atop Starship SN8.
SpaceX has only fully stacked a Starship prototype once before when Mk1’s nose section was temporarily mated to its tank section to be the centerpiece of CEO Elon Musk’s October 2019 Starship event. It’s unclear why SpaceX wouldn’t simply use one of the mobile cranes its rented for Starship tank section operations (and stacking Mk1) in the past, so it remains to be seen what Wednesday’s road closures will actually be used for.
SpaceX’s road closure plans end with a wildcard, however. Once installed, the plan is to perform a second triple-Raptor static fire while only drawing propellant from SN8’s header tanks – small internal tanks designed to hold landing propellant, one of which is situated at the tip of Starship’s nosecone. On October 21st and 22nd, SpaceX still has two 9pm-6am closures scheduled for “SN8 static fire” testing. Filed early on October 20th, before SN8’s successful static fire, the most likely explanation is a simple clerical error or miscommunication, with Cameron County or SpaceX failing to properly communicate that those subsequent static fire test windows are no longer needed.
If retaining the static fire closures was intentional, it would mean that SpaceX – likely at Musk’s urging – intends to install Starship SN8’s nosecone in a matter of hours. It’s almost inconceivable that Starship SN8’s nosecone – outfitted with multiple gas thrusters, forward flaps powered by Tesla motors, a liquid oxygen header tank, vents, and plenty of plumbing – can be installed and made ready for testing in less than 12 hours. Barring a surprise method of mating SN8’s nose and tank sections, the nosecone will have to be welded to the rest of SN8 and the weld inspected – typically a multi-day process.
Regardless, given how quickly SpaceX moves and how dead-set CEO Elon Musk is at pushing limits and breaking barriers, it seems reasonable to assume that Starship SN8 may be fully integrated and ready for a second static fire test just a handful of days from now. Once completed, SN8 will be ready to attempt Starship’s first high-altitude flight test, launching to ~15 km (~9.3 mi) to attempt an untested skydiver-style descent and landing.
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
