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.
Elon Musk
FAA turned down free Starlink offer before nationwide ground stop, Elon Musk says
Elon Musk says the FAA declined free Starlink terminals before last week’s nationwide ground stop.
Elon Musk says the Federal Aviation Administration could have had Starlink backing up its air traffic communications for free, and he is pointing to last week’s nationwide ground stop as proof it was needed. “As I was saying … Free Starlinks for FAA were offered to Sec Duffy, but he said they were not needed. As it turns out, they were,” Musk wrote on X Monday.
Musk was quoting his own post from February 2025, when he wrote that “the ancient system that is rapidly declining in capability was made L3Harris,” while a newer replacement system from Verizon was “not yet operational.” The Department of Transportation has not responded publicly to Musk’s account of the offer.
The outage behind the post began at about 3:30 p.m. ET on Friday, November 13. According to the FAA’s own account, its legacy equipment became unstable when data began flooding its FAA Telecommunications Infrastructure network at a rate of 1,000 connection attempts every four to five seconds. The agency traced the flood to two locations, a radar site in Amarillo, Texas, and a radio communications site in El Dorado, Arkansas, where L3Harris had been installing a new router.
Instability spread across 17 of the FAA’s 22 Air Route Traffic Control Centers. The agency grounded departures nationwide while about 3,500 aircraft already in the air landed safely, and lifted the stop at 8:15 p.m. ET. Operators canceled roughly 12,462 flights that day, though the FAA notes not all of those were directly caused by the ground stop. L3Harris blocked the two sites to stabilize the network, and the FAA disabled the same router function on about 60 similar units. Officials found no sign of a cyberattack.
Transportation Secretary Sean Duffy has blamed prior administrations and dated systems, and has called on Congress to fund a $50 billion overhaul of the system.
Musk’s history with the FAA network goes back to early 2025, when he was leading the Department of Government Efficiency. He claimed on X that the system was failing and putting air travelers at risk, initially blaming Verizon before correcting himself to name L3Harris. The FAA confirmed at the time it was testing Starlink terminals, one at its Atlantic City, New Jersey facility and two at “non-safety critical sites” in Alaska. SpaceX said it was providing the kits at no cost and had no intent to take over any existing FAA contract.
Duffy described Starlink then as “part of a solution” rather than a replacement. By July 2025, the FAA told lawmakers it was not considering replacing its L3Harris and Verizon telecommunications contracts with Starlink.
Whether Starlink would have prevented Friday’s disruption is not clear. The FAA described a fault inside its terrestrial network rather than a loss of connectivity, and Musk did not explain how satellite links would have been used. His post does put SpaceX back in the conversation as Washington debates how to pay for the next air traffic control system. SpaceX already supplies Starlink to commercial airlines for inflight connectivity, and United’s rollout required FAA certification for each aircraft type.
News
Tesla makes $3.3 billion Cybercab bet at Giga Berlin
It is no secret Tesla is prioritizing Cybercab production as it plans to launch a fleet of fully autonomous vehicles without steering wheels or pedals across the world. Today, it made a €3 billion bet to do so in Europe.
Tesla announced on November 16, that it will invest €3 billion (approximately $3.3 billion) to expand its Gigafactory in Grünheide near Berlin, its only vehicle manufacturing site in Europe.
🚨 BIG NEWS: Tesla will invest €3 billion (~$3.3B) to expand Giga Berlin.
A new production building could eventually build up to 1 million Cybercabs a year. Construction targeted for H1 2027, production in 2029. Permit filing comes later this year. https://t.co/hsM8kNaJRR
— TESLARATI (@Teslarati) November 16, 2026
The investment will fund a major new production building—roughly twice the size of the existing main hall—and supporting infrastructure, including an additional wastewater treatment plant. The new facility is designed to produce up to one million Cybercabs annually once fully scaled, alongside continued Model Y output.
Tesla plans to file the building permit application before the end of 2026, according to Tagesspiegel, drawing on a broader expansion application submitted in 2023 that targets one million vehicles per year overall. Construction is scheduled to begin in the first half of 2027, with Cybercab production starting in 2029.
The company is already recruiting several hundred workers for construction and production planning. The site currently employs about 12,600 people after recent hiring of roughly 2,000, and it is ramping Model Y production toward 7,500 vehicles per week (around 375,000 annually).
This vehicle expansion comes just days after plant manager André Thierig indicated at the Automobilwoche Congress on November 11 that full battery cell production at Grünheide is on track for mid-2027.
The factory already produces electrodes, which are currently shipped to Texas for cell assembly and returned; the goal is to complete 4680-format cells on site using Tesla’s dry-electrode process, targeting up to 18 GWh annually.
The cumulative investment in the cell operation approaches €1 billion and is expected to create more than 1,500 jobs. Once operational, Giga Berlin would become the first plant in Europe to produce everything from battery cells to finished vehicles under one roof, raising the European content of its Model Ys to roughly 90 percent.
For Tesla’s German operations, the twin moves deepen vertical integration and reduce dependence on transatlantic and Chinese supply chains.
They also contrast sharply with the broader German automotive industry, which faces high costs, weak demand, and job cuts; Brandenburg officials have welcomed the investment as a significant economic boost that creates hundreds of new positions and strengthens the region as a manufacturing hub.
Tesla’s expansion advances its strategic pivot toward autonomy and robotaxis. The Cybercab is intended to become a high-volume product; adding major European capacity diversifies production beyond the United States and supports Elon Musk’s vision of autonomous vehicles comprising the majority of Tesla’s future output.
Combined with localized 4680 cell production, the plans position Giga Berlin as a more self-sufficient, technologically advanced European base, enhancing competitiveness as regulatory and market conditions favor higher local content.
Elon Musk
Elon Musk is already planning a bigger Starship, and the Moon may be why
Elon Musk revealed Starship V4 specs that could reshape how fast SpaceX reaches the Moon.
A day after SpaceX caught a Starship upper stage for the first time, Elon Musk laid out how much bigger the next version will get. “Starship V4 will be ~70m long, which is roughly a 40% length increase and allows >60% more propellant load,” Musk wrote on X Sunday evening. “Engine count will be raised to 9, with 3 more Raptor-Vacuum engines added, and these will be higher thrust V4 engines.”
The current V3 ship that flew on Flight 15 stands about 52 meters tall with six Raptors, three built for sea level and three for vacuum. V4 stretches the ship and doubles its vacuum engines. Musk first said in August 2025 that V4 would add three engines to “a significantly longer ship” and fly in 2027. Sunday’s post is the most specific look at the ship so far.
The payload jump is the headline for the rest of the industry. SpaceX said in its IPO prospectus that V3 is expected to carry about 100 metric tons to orbit, while future generations could reach 200 metric tons, potentially as soon as V4. For comparison, a reusable Falcon 9 carries roughly 17 metric tons to low Earth orbit.
The bigger impact may be on the Moon. Every Starship lunar mission depends on filling a propellant depot in orbit with a string of tanker flights before the lander departs. A NASA safety panel member put that number at around 22 flights last month, while Musk countered that it would be “more like 6 to 8,” as Teslarati reported. Much of that gap comes down to which ship is doing the hauling. Musk has said a V4 tanker could deliver more than 200 tons of propellant per flight, which by his math brings a lunar refill down to five or six launches.
Fewer tankers per landing means more landings per year. SpaceX already advertises cargo flights to the lunar surface starting no earlier than 2028 at $100 million per metric ton, with a Starship lander able to put up to 100 tons on the surface. In February, Musk said SpaceX had shifted its focus to “a self-growing city on the Moon,” which he believes could be done in under 10 years, as Teslarati covered. NASA’s Artemis IV landing is targeted for 2028, and the White House has called for work on a permanent lunar outpost to begin by 2030.
Starship V4 will be ~70m long, which is roughly a 40% length increase and allows >60% more propellant load. Engine count will be raised to 9, with 3 more Raptor-Vacuum engines added, and these will be higher thrust V4 engines. — Elon Musk (@elonmusk) November 16, 2026
None of that works without ships that fly more than once, which is where Ship 42 comes in. Musk spent part of Sunday at the pad inspecting the vehicle caught on Saturday. “I was going over the whole Starship heat shield earlier today. Overall, it looks great. The engines look great too. Ship 42 could probably be reflown with a few weeks of refurbishment,” he wrote. He added that “many small fixes are needed to achieve immediate reusability (like an airplane).”
SpaceX has never reflown a ship. Its two booster reflights each came months apart, so a Ship 42 return to flight within weeks would be a first for the program. Flight 15 already showed the ship can survive a full orbital mission and come home to the tower, as Teslarati reported Saturday.