News
SpaceX installs Raptor Vacuum engine on first orbital-class Starship
Update: Providing the best views yet of the Raptor Vacuum installation process, SpaceX began installing one of Starship S20’s six engines (one of at least two recently trucked to the launch site) on Monday morning.
It remains to be seen exactly how many engines will be installed on Ship 20 or how many will be ignited during its first static fire test but barring the delivery of more Raptors, signs currently point to an initial test of two engines – one sea-level-optimized Raptor Center (RC) and one Raptor Vacuum with a much larger nozzle. Whenever Ship 20 does fire up those engines, it will be the first static fire of a RVac engine installed on a Starship and the first simultaneous, side-by-side static fire of two different Raptor variants. Since publishing time, SpaceX has cancelled a Tuesday road closure, pushing Starship S20’s first static fire attempt to no earlier than (NET) Wednesday evening.
For the third time in two months, SpaceX has begun installing Raptor engines on its first orbital-class Starship prototype – hopefully for good.
In no uncertain terms, Starship 20’s (S20) path to what could be its last Raptor installations has been about as windy and mysterious as they come. Starship 20 (S20) left the Starbase factory floor for the first time in early August – all six Raptors installed in another program first – for a brief fit check and photo op. After spending about an hour installed on top of Super Heavy Booster 4 (B4), Ship 20 was removed and returned to the build site, where teams removed all six engines and finished wiring and plumbing the vehicle.
Days before the ship’s long-anticipated trip to Starbase’s suborbital launch site for qualification testing, the mount SpaceX prepared for the process quickly had hydraulic rams – used to safely simulate Raptor thrust – were abruptly removed. Starship S20 was then installed on the Pad B mount, where SpaceX proceeded to reinstall six Raptors. Weeks later, after slow heat shield repairs neared completion, SpaceX again removed Ship 20’s Raptors and reinstalled the hydraulic rams it had removed – unused – the month prior. Finally, on September 30th, some seven weeks after the prototype arrived at the suborbital launch site, SpaceX put Starship S20 through its first major test – a lengthy ‘cryoproof’.
Now, ten days after completing a seemingly flawless cryoproof test on its first try, SpaceX has once again trucked multiple Raptors – at least one sea level and one vacuum engine – from the Starbase build site to Starship S20’s suborbital test stand. From the outside looking in, it’s hard not to view the contradictory path S20 took to its first tests – and is still taking to its first static fire(s) – as an unusually visible sign of some kind of internal tug of war or major communication failure between different SpaceX groups or executives.
It’s impossible to determine anything specific beyond the apparent fact that several of the steps taken from Ship 20’s first factory departure to its first cryoproof and static fire tests could have probably been deleted entirely with no harm done and many dozens of hours of work saved. At the end of the day, Starship S20 completed cryoproof testing without issue on the first try and is now seemingly on track to begin its first static fire test campaign later this month.
At the moment, SpaceX has three possible static fire test windows scheduled from 5pm to midnight CDT on Tuesday, Wednesday, and Thursday (Oct 12-14). A similar Monday window was canceled days ago on October 7th, suggesting that more cancellations are probably on the horizon. For now, there’s a chance that Starship S20 – with anywhere from two to all six Raptor engines installed – will fire up for the first time before next weekend. It’s hard to say how exactly SpaceX will proceed. It’s not inconceivable that SpaceX will install all six engines and gradually ramp up to a full six-engine static fire over several tests.
Given that SpaceX has already static fired three Raptor Center (RC) engines on multiple Starship and Super Heavy prototypes, odds are good that Starship S20’s test campaign will be similar – beginning with a three-Raptor static fire, in other words. SpaceX could then add one, two, or all three Raptor Vacuum engines into the fray for one or more additional tests with 4-6 engines total. It’s also possible that suborbital launch mount and pad limitations will prevent more than three engines from firing at once, in which case SpaceX would presumably perform two separate tests of Ship 20’s Raptor Center and Raptor Vacuum engines.
Given that two Raptor variants have never been static fired simultaneously on the same vehicle, it’s hard to imagine that SpaceX won’t also want to perform one or several combined static fires with Raptor Vacuum and Raptor Center engines on Ship 20.
Tesla has secured regulatory approval for its Full Self-Driving (Supervised) system in Denmark, marking a significant step in the technology’s expansion across Europe.
Announced on June 9, the approval positions Denmark as the fourth European country to greenlight FSD Supervised, following the Netherlands, Lithuania, and Estonia.
Rollout to Danish vehicle owners is expected to begin soon, the company said.
The Danish Road Traffic Authority granted provisional approval after reviewing the original type approval issued by the Dutch vehicle authority (RDW) on April 10, 2026.
FSD Supervised now approved in Denmark 🇩🇰
Rollout will begin soon pic.twitter.com/Xpxwcme10k
— Tesla Europe, Middle East & Africa (@teslaeurope) June 9, 2026
This national recognition approach allows individual countries to bypass slower EU-wide harmonization processes, accelerating deployment. Lithuania activated the system on May 20, with Estonia following on May 29, demonstrating a rapid domino effect across the region.
FSD Supervised enables advanced driver assistance capabilities, including automatic steering, acceleration, braking, lane changes, and navigation through complex urban and rural environments. The system is designed for supervised use, as its name states, meaning drivers must remain attentive and ready to intervene at all times.
It adapts to diverse conditions, such as rain, night driving, and varied road types common in Denmark, but it is important to note that the tech is not fully autonomous.
Following a launch in Europe just a few months ago, with its first approval coming in the Netherlands, Tesla is just now highlighting the successful start.
Early data from the Netherlands highlights strong safety performance. Between April 10 and June 5, vehicles using FSD Supervised recorded 3.5 times fewer collisions than manual driving overall, with zero crashes reported on highways across more than 16.6 million kilometers driven.
These results underscore the potential of the technology to enhance road safety when properly supervised.
Tesla’s European push builds on its global footprint, now reaching 12 countries with FSD Supervised availability. The software receives continuous over-the-air updates, improving performance based on real-world data from millions of miles.
In Denmark, owners with compatible hardware—particularly newer vehicles equipped with Hardware 4 (HW4)—are anticipated to gain access first, though exact timelines and eligibility details will be confirmed during rollout.
This approval reflects growing regulatory confidence in supervised autonomy across Europe. As more nations recognize the Dutch certification, Tesla continues to demonstrate how its AI-driven approach can navigate real-world driving scenarios effectively. Denmark’s addition strengthens Tesla’s position in the region, paving the way for broader adoption on a continent that his been surprisingly slow to adopt the technology.
With FSD Supervised now approved in four European markets in just two months, the technology is steadily advancing toward wider availability. Tesla aims to refine the system further through ongoing data collection and software iterations, supporting its vision for safer and more efficient transportation.
Tesla has apparently revised the policy it previously had listed for Full Self-Driving transfers on the newest All-Wheel-Drive Cybertruck that the company had sold for a steal price of just $59,000 earlier this year.
After initially stating that customers who bought the pickup would be able to transfer FSD purchases, Tesla recently changed the language in those terms and conditions to reflect that this would no longer be the case.
Tesla launches new Cybertruck trim with more features than ever for a low price
The adjustment in terminology has caused a handful of orderers to cancel their reservations due to the loss of FSD transfer:
Just cancelled my 59k CT order today. My screenshot from that day of order (feb 20th) clearly shows that it would be eligible.
Terms were retroactively modified. Our 2020 Y and 2023 S are just fine for now. pic.twitter.com/D9PFnId1B4
— Ryan Scanlan 👥 (@Xenius) June 8, 2026
Tesla said orders for the new Cybertruck AWD must be placed by March 31, 2026, to qualify for the FSD transfer. The language in the document from earlier this year explicitly states that they “may qualify” for the transfer program, but the date of March 31 is explicitly mentioned.
Additionally, Tesla Delivery Advisors reached out to some orderers of the AWD Cybertruck, who were told there was “an update to the eligibility of the Full Self-Driving (Supervised) transfer.” Tesla stated they could:
- proceed without the transfer,
- upgrade to a Premium or Cyberbeast trim and request an FSD Transfer
- cancel the order and be refunded the $250 order fee.
Tesla turning around and changing these terms will undoubtedly result in a handful of cancellations on the part of those who have placed an order for this truck. They could pay $99 per month for an FSD subscription, which is now the only option available, but having purchased the suite outright on another vehicle and being told the transfer policy would be upheld, only to have it cancelled, is a tough pill to swallow.
These moves were also made by Tesla just before deliveries were set to begin on the Cybertruck AWD configuration. Reservation holders have started receiving VINs for their trucks, and Tesla is preparing to hand over the first units.
It’s a disappointing move from Tesla that will undoubtedly make some of its fans who have bought the truck frustrated.
In the world of autonomous ride-hailing, there are only a handful of names. Among those few companies lies a strategy play by each to keep the opposition on their toes. Tesla, on the other hand, already tipped its hand at where it is headed next.
Tesla has signaled its next major push in the autonomous ride-hailing market by filing for an Autonomous Vehicle Network Company permit in Nevada (Docket 26-05015). Through Tesla Robotaxi, LLC, the company seeks approval to operate up to 5,000 robotaxis in Clark County, including high-traffic areas like Las Vegas and Henderson airports, within the first 12 months of launch.
This filing builds on Tesla’s earlier testing approvals from the Nevada DMV in September 2025 and preparations such as maintenance hubs in the Las Vegas area. Nevada represents a strategic expansion into a major tourist destination, where high visitor volumes could drive strong utilization and showcase the reliability of unsupervised autonomy to a broad audience.
We’d have to assume this means Tesla is targeting Las Vegas, and it’s a great move from a business perspective.
Vegas is such a melting pot of people from all around the country and the world. It will expose people from all corners of the globe to Tesla’s autonomy capabilities https://t.co/Qz3fQmhULF pic.twitter.com/Du5pj2RyWC
— TESLARATI (@Teslarati) June 6, 2026
Approval would mark a significant step toward commercial operations in a new state, following progress in Texas.
Tesla’s shareholder decks and earnings calls have clearly outlined these ambitions. In the Q4 2025 shareholder deck, the company listed planned Robotaxi coverage for the first half of 2026, explicitly naming Las Vegas alongside Phoenix, Miami, Orlando, and Tampa, with Dallas and Houston already advancing. Austin was noted as “ramping unsupervised,” while the Bay Area remained in safety-driver mode.
By Q1 2026, the deck updated statuses to reflect launches in Dallas and Houston, with “preparations underway” for the remaining cities, including Las Vegas. Paid Robotaxi miles nearly doubled sequentially in Q1, underscoring momentum even as broader timelines adjusted slightly for regulatory and operational readiness.
On earnings calls, CEO Elon Musk and executives have emphasized a phased rollout prioritizing safety. Unsupervised operations in Texas have shown strong results with no reported accidents or injuries in the program. Tesla continues groundwork in additional major U.S. metros through testing and permitting, positioning it to scale quickly once approvals clear.
This Nevada move aligns with Tesla’s vision of transforming from an EV maker into an AI and robotics leader. The forthcoming Cybercab, which started production at Giga Texas in April, is expected to eventually dominate the fleet, replacing many Model Y vehicles and driving down costs to enable affordable rides.
For investors and the industry, this signals Tesla’s intent to dominate key Sun Belt and tourist markets where weather, regulations, and demand favor rapid scaling. Success in Las Vegas could validate the model for denser urban and high-tourism environments, accelerating the shift toward a future where robotaxis generate meaningful revenue.
Las Vegas will also expand knowledge among the general public at Tesla’s capabilities, helping people experience driverless ride-hailing from several companies during their time on The Strip.
Tesla Full Self-Driving is taking over Europe: fourth country gets FSD approval
Tesla revises FSD transfer policy on new Cybertruck trim, causing cancellations
