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.
SpaceX has updated its target for the thirteenth integrated flight test of Starship, aiming for as early as Thursday, July 23. The 90-minute launch window opens at 5:45 p.m. CT from the company’s Starbase facility in South Texas.
The target flight was initially rescheduled for today, but SpaceX pushed it back again.
This latest adjustment follows an aborted attempt earlier in the week and reflects the iterative, rapid-development approach that has defined the Starship program. With the vehicle already stacked and ground teams making final preparations, the mission represents another step toward proving the full reusability of the world’s most powerful rocket system.
Now targeting to launch Starship’s thirteenth flight test as early as Thursday, July 23 → https://t.co/Rp7VwBzpWx pic.twitter.com/Y0YNzfc5zk
— SpaceX (@SpaceX) July 19, 2026
The original launch attempt on July 16 was scrubbed at T-0 when several Raptor engines on the Super Heavy booster failed to ignite properly. The automatic abort system triggered just as the engines began their startup sequence, preventing liftoff.
SpaceX CEO Elon Musk confirmed that some engines did not start as expected, prompting the decision to replace two Raptors on Booster 20 to ensure reliability. The issue occurred despite a successful full-duration static fire earlier, highlighting the complexities of coordinating 33 engines under flight conditions.
This cautious approach underscores SpaceX’s commitment to safety amid an aggressive test cadence.
Flight 13 builds directly on the lessons from Flight 12 in May 2026. The Super Heavy booster’s primary goals include a successful liftoff, ascent, stage separation, boostback burn, and controlled splashdown in the Gulf of America.
Hardware and software modifications address the off-nominal flip and boostback burn problems from the prior flight, where propellant slosh and engine relight issues led to an uncontrolled impact.
For the Starship upper stage, objectives include deploying 20 operational Starlink V3 satellites, the first real payload of this type, performing a single Raptor engine relight in space, and executing a controlled entry, descent, and splashdown in the Indian Ocean. Propulsion upgrades aim to improve engine-out capability after one vacuum Raptor was lost on Flight 12.
Additional test elements focus on heat shield performance. Six satellites carry cameras to image the tiles during flight, while white-painted tiles and upgraded attachments on flaps and the aft skirt will gather data for future reusability.
The FAA completed its mishap investigation into Flight 12 earlier this month, clearing the regulatory path.
This suborbital mission, the second with V3 vehicles, advances Starship toward operational missions, including potential crewed flights and support for NASA’s Artemis program. Success would mark significant progress in rapid reusability and satellite deployment from the massive system.
Elon Musk dismissed reports claiming SpaceX had placed a massive order for NVIDIA GPUs worth $52 billion. The denial came hours after Taiwanese media, citing unnamed industry sources, reported that SpaceX planned to acquire approximately 13,000 AI server racks, equating to roughly 1 million GB300 GPUs, from Foxconn.
Each rack was estimated at around $4 million, with deliveries potentially starting in late 2025.
The story suggested this would mark SpaceX’s first major foray into Foxconn-manufactured NVIDIA hardware, breaking from suppliers like Supermicro and Dell. Musk responded bluntly on X:
This is fake news
— Elon Musk (@elonmusk) July 20, 2026
Despite the denial, the rumored scale aligns with SpaceX’s explosive growth in AI infrastructure. NVIDIA’s GB300 (successor to the GB200 NVL) racks deliver unprecedented performance for large-scale training and inference. A $52 billion commitment would dwarf most corporate AI budgets and provide the compute muscle needed for frontier models.
SpaceX already operates gigawatt-scale terrestrial clusters like Colossus in Memphis, Tennessee, and has monetized them aggressively through leasing deals.
SpaceX’s newest Starmind will make earth data centers obsolete
Major customers include Anthropic (paying ~$1.25 billion monthly for 220,000+ GPUs), Google (~$920 million monthly for 110,000 GPUs), and Reflection AI. These arrangements are projected to generate tens of billions in annual revenue, far outpacing traditional SpaceX businesses.
Such an investment would fuel internal AI efforts, particularly Grok models under the integrated SpaceXAI division, while supporting ambitious orbital data center plans. SpaceX envisions launching thousands of AI-optimized satellites powered by solar energy and cooled in space, bypassing terrestrial power and land constraints.
This “Starmind” constellation could position the company as a leader in space-based computing.
SpaceX as an Emerging AI Powerhouse
Once primarily known for reusable rockets and Starlink satellite internet, SpaceX has transformed into a multifaceted AI player.
The 2026 acquisition of xAI integrated Grok development directly into the company. Starlink’s low-latency global network complements massive compute clusters, enabling efficient data flow for training and serving AI models.
Musk has long argued that AI scaling demands solutions beyond Earth, citing things like real estate and electricity limits on the ground.
While the Foxconn deal may not be in the cards, SpaceX’s trajectory is continuing on the path of blending aerospace engineering with hyperscale AI to dominate both launches and intelligence infrastructure.
Elon Musk shed more details on the upcoming improvements to Tesla’s Full Self-Driving suite, specifically one that the CEO mentioned last week, which should help owners see fewer interventions.
Last week, Musk hinted that one major improvement that Tesla planned to roll out to Full Self-Driving users was the car’s ability “to remember your specific interventions and match each person’s individual preferences.”
Elon Musk says your Tesla will start to learn your individual preferences
This small bit of detail was linked to a post from Tesla community member Whole Mars, who said that FSD’s tendency to exit the carpool lane, a feature that owners can turn on but at times the car will disregard.
It sounds like, based on Musk’s two responses since that original post, it is safe to say the things FSD will start to remember are wide-ranging. However, it seems the biggest differences will be noticed with parking performance, which Musk continues to mention.
Highway Lane Preferences
The initial post Musk mentioned, with these new remembered preferences soon to arrive for Tesla owners everywhere, was the Carpool/Express Lane.
Tesla has a setting in the FSD menu that lets drivers enable HOV Lane travel. However, the car won’t always stay in that suggested or preferred lane.
The car will start to remember your specific interventions and match each person’s individual preferences
— Elon Musk (@elonmusk) July 18, 2026
Some owners have also complained of left lane camping, an illegal maneuver in at least some states. Cruising in the passing lane has resulted in tickets for some, as it is illegal in over 30 states in the U.S.
Tesla did not confirm if these preferences would also be included in new FSD behaviors, but it would certainly help move the company toward fewer interventions.
Parking Preferences
This seems to be the real focus of the entire operation, as Musk stated several weeks ago that parking was overwhelmingly the most frequent reason for interventions.
The major issue with parking is not necessarily the parking “performance,” as FSD is generally good at parking. It definitely has its issues; we’ve recorded plenty of them, including this one as recent as last week:
Yeah it seems like FSD v14.3.5 is having some issues with parking early on https://t.co/Bw5ULfVmDq pic.twitter.com/RHdpjOEpIo
— TESLARATI (@Teslarati) July 13, 2026
However, the changes coming are more about preferences, meaning where you park and how your car enters the spot, either pulling in or backing in. Owners have also reported that pulling into the correct driveway is a relatively rare thing for FSD, something else that needs to be confronted.
Musk basically confirmed that all of these things would be part of Tesla’s plan to address driver preferences with FSD:
Yes
— Elon Musk (@elonmusk) July 20, 2026
It’s obvious there is something big coming with FSD, and the company’s focus seems to be eliminating any intervention that would be related to preferences. This is probably the biggest bottleneck between Tesla and being fully autonomous. Critical interventions do occur, but they are much less frequent.
The only time a driver should be taking over is because of a critical intervention; this seems to be the goal of Tesla right now.
This all seems to be a priority as Tesla continues to move closer to the prospect of unsupervised driving.
SpaceX adjusts Starship Flight 13 test launch target date once again
Elon Musk debunks $52 billion SpaceX-NVIDIA GPU deal
