Connect with us

News

SpaceX installs Raptor Vacuum engine on first orbital-class Starship

Starship S20's third round of Raptor Vacuum engine installation - hopefully for good. (NASASpaceflight - Nic Ansuini)

Published

on

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.

Advertisement

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.

Raptor Vacuum has identical plumbing but a far larger nozzle than its sea-level-optimized siblings. A larger nozzle boosts engine efficiency in or near vacuum.

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.

Advertisement

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

Elon Musk

NASA just gave SpaceX more crew missions because Boeing can’t certify

Published

on

By

NASA has filed a procurement notice announcing its intent to add six post-certification missions to SpaceX’s existing Commercial Crew Transportation Capability contract. The agency said it would order up to three of those missions immediately upon adding them to the contract, with the remaining three available as needed through the end of the International Space Station’s planned operations in 2030.

The reason for the expansion is straightforward. NASA cited recently shortened ISS mission durations, technical issues and schedule delays encountered by Boeing, the allocation of missions between Boeing and SpaceX, and the ongoing technical challenges of maintaining a reliable crew transportation capability as the driving factors behind the decision. Boeing’s CST-100 Starliner has still not been certified for crewed flights, and a cargo-only Starliner mission was not included on NASA’s most recent mission manifest. With Boeing effectively sidelined for the foreseeable future, SpaceX is the only American company capable of rotating crews to the station.

SpaceX Board has set a Mars bonus for Elon Musk

The history behind this contract tells the fuller story of how SpaceX got here. NASA originally awarded SpaceX its Commercial Crew contract in 2014 for $2.6 billion. In 2022 NASA modified the contract to add five missions covering Crew-10 through Crew-14, worth $1.436 billion, bringing the total contract value at that point to $4.9 billion. The recent May 18 filing by NASA extends that runway further, with Crew-12 currently docked at the station and Crew-13 assigned and targeting a mid-September 2026 launch.

According to a report by SpaceNews, NASA stated in its filing: “It is necessary to award additional PCMs to SpaceX given the recently shortened ISS mission durations, technical issues and schedule delays encountered by Boeing, the allocation of missions between Boeing and SpaceX, NASA’s projections for when an alternative crew transportation system may become available, and the ongoing technical challenges of maintaining a reliable capability for crewed flights to ISS.”

No dollar value for the new six missions has been publicly confirmed yet, but based on the 2022 precedent of roughly $287 million per mission, the new block could represent close to $1.7 billion in additional contract value. With SpaceX simultaneously preparing Starship as NASA’s Artemis lunar lander, filing its S-1 for a June IPO, and now absorbing more ISS crew rotation work, the company’s role as the primary contractor for American human spaceflight is no longer a matter of circumstance. It is NASA policy.

Continue Reading

Energy

Zuckerberg’s Meta taps Musk’s Tesla for massive clean energy project

Published

on

Credit: Tesla

In a notable intersection of Big Tech powerhouses, Meta, led by Mark Zuckerberg, has partnered with Canadian energy infrastructure giant Enbridge on a significant renewable energy initiative that will rely on battery technology from Elon Musk’s Tesla.

The project, which was announced this week, marks another step in Meta’s aggressive push to power its expanding data center operations with clean energy, dispelling many of the complaints people have about them.

This new development is located near Cheyenne, Wyoming, and will feature a 365-megawatt (MW) solar farm paired with a 200 MW/1,600 megawatt-hour (MWh) battery energy storage system, also known as BESS. Tesla is providing the batteries for the project, valued at roughly $200 million.

The story was originally reported by Utility Dive.

This Wyoming project represents the first phase of Enbridge and Meta’s joint “Cowboy Project.” Once operational, it will deliver power to Meta’s regional data centers through Cheyenne Light, Fuel, and Power under Wyoming’s Large Power Contract Service tariff.

This tariff, originally developed in collaboration with Microsoft and Black Hills Energy, is designed specifically for large loads like data centers. It ensures that the renewable supply serves hyperscale customers without impacting retail electricity rates for other users.

The battery system will operate under a long-term tolling agreement, providing dispatchable capacity that enhances grid reliability. During periods of high demand, the utility can access the backup generation, addressing one of the key challenges of integrating large-scale renewables with the explosive growth of data center electricity demand driven by artificial intelligence.

This latest collaboration builds on prior joint efforts between Enbridge and Meta in Texas, including the 600 MW Clear Fork Solar, 152 MW Easter Wind, and 300 MW Cone Wind projects. Together with the Wyoming initiative, the companies have now partnered on roughly 1.6 gigawatts (GW) of combined solar, wind, and storage capacity.

The deal highlights the intensifying demand for reliable, low-carbon power from technology giants. Meta has committed to supporting its data center growth with renewable energy, joining peers like Microsoft and Google in seeking large-scale solutions. Enbridge’s Allen Capps described the project as “one of the larger utility-scale battery installations supporting U.S. data center operations and growth.”

The involvement of Tesla’s battery technology adds an intriguing layer, linking two of the world’s most prominent tech leaders—Zuckerberg and Musk—in the clean energy transition.

As data centers continue to drive unprecedented electricity load growth across the United States, projects like this one illustrate how hyperscalers are turning to strategic partnerships with traditional energy players and innovative storage solutions to meet both sustainability goals and reliability needs.

Continue Reading

Elon Musk

SpaceX reveals reason for Starship v3 stand down, announces next launch date

Published

on

Credit: SpaceX

SpaceX has decided to stand down from what was supposed to be the first test launch of Starship’s v3 rocket tonight after a minor issue with a hydraulic pin delayed the flight once more.

The company scrubbed its first test flight of the upgraded Starship v3 on May 21 in the final minutes of the countdown. SpaceX CEO Elon Musk quickly took to social media platform X, explaining that a hydraulic pin on the launch tower’s “chopsticks” arm failed to retract properly.

Musk added that the company would fix the issue this evening. SpaceX will attempt another launch tomorrow night at 5:30 p.m. CT, 6:30 p.m. ET, and 3:30 p.m. PT.

The countdown for Starship Flight 12 — featuring the taller and more capable V3 stack with Booster 19 and Ship 39 — had been progressing smoothly until the late-stage issue surfaced. The Mechazilla tower arm, designed to secure the vehicle on the pad and eventually catch returning boosters, could not complete its retraction sequence.

SpaceX teams immediately began troubleshooting the hydraulic system for an overnight repair.

Starship V3 introduces several significant upgrades over earlier versions. These include greater propellant capacity, more powerful Raptor 3 engines, larger grid fins, enhanced heat shielding, and an improved fuel transfer system.

We covered the changes that were announced just days ago by SpaceX:

SpaceX unveils sweeping Starship V3 upgrades ahead of May 19 launch

The changes are intended to increase payload performance, support higher flight rates, and advance the vehicle toward operational missions, including Starlink deployments, NASA Artemis lunar landings, and future crewed Mars flights. The debut flight from Starbase’s new Launch Pad 2 marked an important milestone in scaling up the fully reusable Starship system.

This stand-down highlights the intricate challenges of preparing the world’s most powerful rocket for flight. Despite extensive pre-launch checks, a single component in the ground support equipment can force a scrub.

The incident aligns with Starship’s proven iterative development approach. Previous test flights have encountered both successes and setbacks, each providing critical data that refines hardware and procedures. Some outlets may call some of these flights “failures,” when in reality, they are all opportunities for SpaceX to learn for the next attempt.

With V3, SpaceX aims to reduce ground-system dependencies and increase launch cadence to meet ambitious long-term goals.

Continue Reading