News
SpaceX installs Starship Mk1 rocket’s flaps for the second time in build-up to flight debut
A little over a month after SpaceX CEO Elon Musk presented an update on Starship in Boca Chica, Texas and technicians dressed the rocket up for the show, SpaceX has begun to install Starship Mk1’s flaps for the second time.
This time, with any luck, those flaps are here to stay until Starship Mk1’s inaugural launch debut, an ambitious flight test with a target altitude of 20 km (12 mi).
Around the second half of September, SpaceX technicians appeared to begin working around the clock to fully assemble Starship, outfitting the exterior with the beginnings of plumbing, power lines, and avionics harnesses, stacking the Mk1 prototype’s two halves, and installing the vehicle’s large fore and aft flaps. During SpaceX CEO Elon Musk’s September 28th Starship update, what looked to be the largely finished Starship Mk1 served as the main backdrop – an undeniably impressive one, at that.
As would soon become clear, SpaceX’s September 2019 Starship Mk1 integration was actually more of a mock-assembly – all the parts involved appear to genuinely be real flight hardware, but almost all of it was only temporarily attached to Starship to give the partial appearance of a finished ship. By October 1st, technicians began removing Starship Mk1’s four flaps, flap shrouds, and leg shrouds, finally culminating in the separation of the rocket prototype’s upper and lower halves.
The fact that neither Musk or SpaceX spokespersons noted that Starship wasn’t actually complete is at least a little unsavory, although it’s admittedly unsurprising given CEO Elon Musk’s known affinity for grand gestures and events. On a positive note, Starship’s mock-assembly likely served as an excellent learning experience for the Boca Chica team and thankfully only seems to have caused a week or two of delay.
Rapid progress in Boca Chica
Despite the mild disruption of dressing Starship Mk1 up for Musk’s presentation, SpaceX Boca Chica has made a huge amount of progress in the five weeks since. Barely three weeks after the rocket’s forward flaps (canards) were removed, SpaceX technicians began the reinstallation process with one major visible difference: a massive motorcycle-sized actuator.
On the first round of installations-for-show, Starship Mk1’s flaps featured no such mechanism, confirming suspicions that much of the hardware installed at the last second was not quite finished or was only being installed for Musk (and practice). The appearance of a previously unseen actuator mechanism on the first reinstalled canard suggests that this time around, SpaceX is installing Starship’s flaps with their final purpose of controlling Starship’s free-fall in mind.
Instead of copying Falcon 9’s proven method of vertical launch and vertical landing, SpaceX is taking a more radical approach with Starship that will see the spacecraft reenter Earth’s atmosphere belly-first, slow its forward speed to near-zero, and fall directly down for approximately 25 km (15.5 mi), using its flaps like a skydiver’s limbs. Perhaps just a few hundred meters above the ground, Starship will finally perform an aggressive flip maneuver, igniting its Raptors while sideways, swerving to neutralize that horizontal velocity, and finally landing on six small legs.
In this sense, although they certainly look the part, Starship’s aerodynamic control surfaces are very explicitly not wings and are instead meant to interact with the atmosphere at an almost 90-degree angle of attack (AoA). In line with that strategy, they only have to actuate with a single degree of freedom, drastically simplifying Starship’s control surfaces.
Similar to Starship Mk1’s newly filled-out canard actuators, SpaceX technicians have installed two massive hinges/mounts for Starship’s larger after flaps. Aft flap installation will likely start as soon as SpaceX technicians have installed the bulk of Starship Mk1’s external plumbing and wiring, a milestone that appears to be fast approaching.
Starship Mk1’s lower half was unexpectedly moved about a mile to SpaceX’s nearby launch facilities prior to the installation of its nose section, meaning that SpaceX will likely have to transport the nose to the launch pad for final mating. It’s unclear what tests SpaceX specifically plans to kick off Starship Mk1’s pre-flight preparations with, but it’s safe to assume that the most imminent milestone is a wet dress rehearsal (WDR), possibly preceded by a tank proof test.
The latter procedure would be designed to prove that Starship Mk1’s pressure vessel is both leakproof and structurally sound and would nominally involve filling the spacecraft’s tanks with a neutral fluid (likely water or liquid nitrogen). A WDR would see SpaceX load Starship as if preparing for launch (requiring liquid oxygen, methane, nitrogen, and helium) but stopping just prior to the engine ignition and liftoff that would otherwise follow. Although unlikely, a WDR could result in a massive fire or explosion if Starship were to lose structural integrity during the test, which is why the aforementioned neutral testing is typically performed first when handling brand new launch vehicles.
Finally, assuming Starship Mk1 successfully passes the above tests, SpaceX will use the vehicle to perform Raptor’s first triple-engine static fire test. That static fire will likely be the final major test activity before SpaceX readies Starship Mk1 for its 20-km flight debut, which will serve as a more or less full-fidelity test of Starship’s exotic skydiver-like landing.
Regardless of how exactly Starship Mk1’s imminent test campaign will play out, SpaceX has road closures scheduled on November 7th, 8th, and 12th. Right now, it’s anyone’s guess what is planned for Thursday and Friday, but it could potentially involve a tank proof test, launch pad checkouts, propellant loading, or something more benign, like transporting Starship’s nose section to the pad for final installation. Stay tuned!
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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.
News
Tesla says Europe could finally get FSD in 2026, and Dutch regulator RDW is key
As per Tesla, a Dutch regulatory exemption targeted for February 2026 could very well be the key gateway for a Europe-wide rollout of FSD.
Tesla has shared its most detailed timeline yet for bringing Full Self-Driving (Supervised) to Europe. The electric vehicle maker posted its update through the official X account of Tesla Europe & Middle East.
As per Tesla, a Dutch regulatory exemption targeted for February 2026 could very well be the key gateway for a Europe-wide rollout of FSD.
Tesla pushes for EU approval
Tesla stated that it has spent more than 12 months working directly with European authorities and delivering FSD demonstrations to regulators in several EU member state. Tesla highlighted a number of its efforts for FSD’s release in Europe, such as safety documentation for FSD, which is now included in its latest public Safety Report, and over 1 million kilometers of internal testing conducted on EU roads across 17 countries.
To unlock approval, Tesla is relying on the Netherlands’ approval authority RDW. The process requires proving compliance with UN-R-171 for driver-assist systems while also filing Article 39 exemptions for behaviors that remain unregulated in Europe, such as hands-off system-initiated lane changes and Level 2 operation on roads that are not fully covered by current rules. Tesla argued that these functions cannot be retrofitted or adjusted into existing frameworks without compromising safety and performance.
“Some of these regulations are outdated and rules-based, which makes FSD illegal in its current form. Changing FSD to be compliant with these rules would make it unsafe and unusable in many cases. While we have changed FSD to be maximally compliant where it is logical and reasonable, we won’t sacrifice the safety of a proven system or materially deteriorate customer usability,” Tesla wrote in its post.
Tesla targets February 2026 approval
According to Tesla, real-world safety data alone has not been considered sufficient by EU regulators, prompting the company to gather evidence to get exemptions on a specific rule-by-rule basis. RDW has reportedly committed to issuing a Netherlands National approval in February 2026, which could pave the way for other EU countries to recognize the exemption and possibly authorize local deployment of FSD.
“Currently, RDW has committed to granting Netherlands National approval in February 2026. Please contact them via link below to express your excitement & thank them for making this happen as soon as possible. Upon NL National approval, other EU countries can immediately recognize the exemption and also allow rollout within their country. Then we will bring it to a TCMV vote for official EU-wide approval. We’re excited to bring FSD to our owners in Europe soon!” Tesla wrote in its post.
Tesla backtracks on strange Nav feature after numerous complaints
Dutch regulator RDW confirms Tesla FSD February 2026 target
