Connect with us

SpaceX

SpaceX’s first Starship engine suffers “expected” damage during Raptor test fire

Sometimes you have to crack a few Raptor eggs to make a Starship omelette. (SpaceX)

Published

7 years ago

on

SpaceX CEO Elon Musk says that the first full-scale Starship engine to be tested has already been pushed to the point of damage less than three weeks after the campaign began, setting the stage for the second full-scale Raptor to take over in the near future.

According to Musk, while most of the damaged pathfinder Raptor’s components should still be easily reusable, the assembly of the second finalized engine is “almost done” and that Raptor will take over near-term testing rather than waiting for repairs to the first engine. This is undoubtedly an extraordinarily aggressive test program, particularly for such a new and cutting-edge rocket propulsion system, but these latest developments are ultimately far more encouraging than they are concerning.

Although the Raptor engine family began integrated subscale static fires way back in September 2016, SpaceX’s propulsion team finalized Raptor’s baseline design and completed assembly, shipment, and an integrated static fire of the first full-scale engine on February 3rd, considerably less than three weeks before Musk took to Twitter. Aside from confirming that the new Raptor had been damaged during its most recent static fire several days prior, Musk indicated that the failure (unsurprisingly) was primarily attributed to the engine reaching the highest chamber pressures yet.

Raptor’s main combustion chamber (the bit directly above the nozzle) has been designed to nominally operate at and reliably withstand extraordinary pressures of 250+ bar (3600+ psi), performance that demands even higher pressures in the components that feed hot methane and oxygen gas into Raptor’s combustion chamber. One prime example hinted at by Musk in a 2018 tweet is its oxygen preburner, used to convert liquid propellant into a high-velocity gas that can then feed a dedicated oxygen turbopump. Aside from the absurdly corrosive environment created by extremely hot gaseous oxygen, the preburner must also survive pressures that could peak as high as 800+ bar, or 12,000 psi.

 

Advertisement
-
-

A lack of technical detail means that it’s hard to know what thrust or main chamber pressure Musk had in mind when referring to exotic alloys that would be needed to survive those pressures, but the performance statistics of a Raptor with a preburner operating at 800+ bar would probably outstrip anything Musk has thus far described. In other words, it’s safe to assume that Raptor has probably not been pushed to those performance levels just yet, although it’s still a distant possibility. More likely is that 800+ bar in the oxygen preburner is an extreme stretch-goal that will take concerted research, development, and optimization to achieve, with Raptor having suffered damage somewhere below those levels while still reaching eye-watering performance figures.

For an engine as complex as Raptor, there are countless dozens of potential failure modes the appearance of which would come as little surprise for an engine just days into full-scale testing. Above all else, the Raptor test schedule held by SpaceX’s world-class propulsion team – be it self-motivated or driven by reckless management-by-spreadsheet – has been fast-paced in the extreme, taking the first high-performance Raptor ever built from standstill to more than 90% thrust and chamber pressures of almost 270 bar (3900 psi) in – quite literally – less than one week. In the same period of time, more than half a dozen static fire tests (ranging from 1-10 seconds) were performed.

Within a few days of that February 10th milestone, in which Raptor reached chamber pressures comparable with the most advanced modern engines (namely RD-180/190/191), the engine was apparently pushed dramatically higher still, reaching a chamber pressure (and thus thrust) that wrought damage on some of the more sensitive parts of the engine’s plumbing. Despite the fact that the second production Raptor is apparently already “almost done”, Musk suggested that it would already feature changes (of unknown gravity) to mitigate the failure modes experienced by Raptor SN01.

Advertisement
-
-

In an industry where NASA and contractors like Aerojet-Rocketdyne will spend months between static fire tests of Space Shuttle engines that have each literally flown multiple (if not) dozens of missions to orbit and have a demonstrated performance and reliability record that is measured in the hundreds of thousands of seconds, the speed and agility of SpaceX’s Raptor development and test program is breathtaking. What remains to be seen is just how comparably reliable and successful the end results (i.e. operational Raptor) will be, but an attitude that actively accepts and even pursues testing to destruction can ultimately only serve to benefit the finished product at the cost of destroyed hardware and many on-ground lessons learned the hard ways.

Given the immense success of SpaceX’s Merlin family of engines and the aggressive strategy of development and continuous improvement that brought it from Merlin 1A to 1D and MVacD, SpaceX is clearly not fumbling around in the dark when it comes to Raptor R&D.

Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes!

Related Topics:

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

SpaceX wants to catch Starship for launch 14, Elon Musk says

Published

2 days ago

on

July 25, 2026

By

Credit: SpaceX

Just hours after Starship Flight 13 achieved a successful soft splashdown of its upper stage in the Indian Ocean on July 24, Elon Musk announced an ambitious next step for the company’s next launch of the rocket.

“Unless we discover problems after mission data review, SpaceX will attempt to catch the ship with the tower on [the] next flight,” the SpaceX CEO posted on X on Friday.

That “next flight” is expected to be Flight 14. The plan involves returning the Starship upper stage, commonly called the “ship,” to the Starbase launch tower in Texas and catching it mid-air using the same mechanical “chopsticks” arms that have already proven themselves with the Super Heavy booster.

A successful catch would mark the first time an orbital-class upper stage has been recovered this way, advancing SpaceX’s goal of full and rapid reusability for the entire vehicle.

SpaceX has already demonstrated the tower-catch technique multiple times with Super Heavy. The first successful catch came on Flight 5 in October 2024, when Booster 12 was plucked from the sky by the Mechazilla arms. Subsequent flights, including those involving Boosters 14 and 15, repeated the feat. Several of those recovered boosters were later inspected, refurbished, and flown again, proving the system’s viability for quick turnaround.

Advertisement
-
-

Traditional reusable rockets, such as SpaceX’s own Falcon 9 or Blue Origin’s New Shepard, land on legs either on land or droneships. Rocket Lab has recovered its small Electron first stages by helicopter, but those are far lighter vehicles.

SpaceX Starship just nailed something it’s never done before

The China Academy of Launch Vehicle Technology (CALT), a subsidiary of the China Aerospace Science and Technology Corp. (CASC), completed a catch of its booster on July 10. They are the only entity besides SpaceX to attempt and complete the feat.

Flight 13 provided encouraging data. The ship executed a controlled reentry, flipped, and soft-landed intact in the ocean after deploying Starlink satellites, offering the first clear post-splashdown views of an undamaged heat shield. The Super Heavy booster, meanwhile, experienced a harder splashdown in the Gulf of Mexico.

Musk has previously stressed that ship catches would only follow multiple successful soft ocean landings to minimize risk of debris over land.

If Flight 14 succeeds, SpaceX would take a major stride toward routine, rapid reuse of both stages—critical for lowering launch costs and supporting ambitious plans for lunar and Mars missions. For now, teams are reviewing the Flight 13 data. Should everything check out, the next Starship flight could deliver one of the most spectacular recoveries in aerospace history.

Advertisement
-
-
Continue Reading

Elon Musk

SpaceX Starship just nailed something it’s never done before

SpaceX’s Starship flew successfully Friday, landing both stages and deploying its first Starlink V3 satellites.

Published

2 days ago

on

July 24, 2026

By

Starship’s thirteenth test flight delivered exactly what SpaceX needed with a clean liftoff, two successful stage recoveries, and the first real payload the vehicle has ever carried to space. Booster 20 and Ship 40 lifted off at 5:51 p.m. CT from Starbase, and by the time the mission wrapped roughly an hour later, both halves of the rocket had done exactly what they were supposed to do.

Booster 20 separated from Ship 40 a few minutes into the flight and stuck a controlled splashdown in the Gulf of Mexico about six minutes after liftoff. That is a meaningful turnaround from Flight 12 in May, when the booster lost several engines during its boostback burn before a hard water landing attempt.


Starship 40’s performance was arguably the bigger win. The vehicle deployed the first 20 operational Starlink V3 satellites Starship has ever carried, then flew a suborbital arc to a landing in the Indian Ocean that SpaceX commentator Dan Huot called the company’s softest splashdown yet. “This is a dream scenario for this team that’s trying to get this heat shield data,” Huot said on the live broadcast, according to Space.com’s live coverage. “I’m a little over the moon right now. Wow. Lucky number 13.”

Unlike the mass simulators SpaceX flew on Flight 12, these were production Starlink V3 satellites, meant to extend solar arrays and antennas and attempt to link with the broader constellation before reentering minutes later. Getting real hardware through a full deploy sequence on only the second flight of the V3 generation keeps Starship on schedule for the payload work NASA is counting on for future Artemis lunar landings.

— TESLARATI (@Teslarati) July 25, 2026

The flight also arrives at a moment when SpaceX needed a win. SPCX has traded below its $135 IPO price since mid-July, as Teslarati reported when the mission slipped to Friday, and short interest has climbed to roughly a third of the tradable float. A clean flight will not fix a balance sheet, but it does answer the one question SpaceX absolutely needed answered this week: whether the fixes made after the July 16 abort would hold up under real flight conditions. They did, on both stages, on the first try after the redesign.

SpaceX has not set a target date for Flight 14, though the company has said it wants to push toward an orbital attempt on the next mission. After Friday, that goal looks a lot more within reach.

Continue Reading

News

SpaceX Starship Flight 13 faces wrath of the Texas skies

SpaceX pushed Starship Flight 13 to Friday, blaming weather instead of the previous engine issues.

Published

3 days ago

on

July 23, 2026

By

SpaceX called off Thursday’s launch attempt of Starship Flight 13, pushing the mission to Friday because of weather tied to Tropical Storm Bertha. The company confirmed the delay on X, noting “Now targeting Friday, July 24 for Starship’s thirteenth flight test, due to weather. A key objective for the flight test is to get clear imagery from the ground of Starship’s heatshield as it flies at a higher dynamic pressure during ascent, which won’t be possible with today’s weather conditions.”

This is the second delay for Flight 13 in two weeks. SpaceX first tried to launch the mission on July 16, but the countdown ended in an automated abort at T-0 when four of Super Heavy Booster 20’s 33 Raptor engines failed to ignite. Musk said at the time that two Raptors would need to be removed and replaced, as Teslarati reported. The company spent the following week destacking Ship 40 and Booster 20, swapping engines, and running leak checks before restacking the vehicle on Pad 2 Wednesday night, according to Spaceflight Now’s live coverage.

Elon Musk debunks $52 billion SpaceX-NVIDIA GPU deal

 

Unlike the engine problem, Thursday’s delay has nothing to do with the hardware. SpaceX wants clean footage of Starship’s heat shield captured from the ground as the vehicle flies through max dynamic pressure, something the storm’s cloud cover over South Texas would not allow. The company said visibility should improve for Friday’s attempt, with the same 90 minute window opening at 5:45 p.m. CT.

Flight 13 will be the second outing for the V3 versions of Starship and Super Heavy, following their debut on Flight 12 in May. The mission carries 20 production Starlink V3 satellites, the first time SpaceX has flown operational satellites rather than mass simulators on Starship. Six of those satellites are fitted with cameras to inspect the heat shield from a different angle during ascent, giving engineers a second data source beyond the ground imagery the weather is currently blocking.

Booster 20 will attempt a boostback burn and a splashdown landing burn in the Gulf of America, while Ship 40 follows a suborbital trajectory toward a landing in the Indian Ocean. The flight plan largely mirrors Flight 12, though the booster will run a more aggressive ascent burn after max Q this time, and the ship’s heat shield includes load sensing tiles meant to measure stress at the higher dynamic pressure SpaceX is targeting.

Advertisement
-
-

If Friday’s attempt succeeds, Flight 13 could be the last suborbital test in the program. SpaceX is already looking to push for an orbital flight on Flight 14.

Continue Reading