Propulsion log
Raptor
28 claims whose own text names a Raptor, an RVac or an engine, across 10 boosters and 13 ships. Boosters first, newest serial first; each vehicle's claims run newest first. This page filters claim text. It does not count engines or infer an engine-out from a summary, so read each claim and its sources.
-
B2
Booster 21 B21
Assigned to F14 by a ledger claim.
2026-09-28 note about B21
On Flight 14, Booster 21 lost one Raptor on ascent, completed its flight, and splashed down in the Gulf rather than being caught.
2026-09-24 UNCONFIRMED note about B21
Flight 14 wet dress rehearsal completed: a full count with propellant fill and deluge firing, no Raptor ignition. The rehearsal was announced on 22 Sep.
-
B1
Booster 20 B20
Assigned to F13 by a ledger claim.
2026-07-24 UNCONFIRMED note about B20
On Flight 13, Booster 20 completed the high-thrust portion of boostback on all 33 engines, the first time for a Super Heavy V3, then ended that burn early. A subset of engines lit for the landing burn before a hard splashdown in the Gulf.
-
B1
Booster 19 B19
Assigned to F12 by a ledger claim.
2026-05-22 UNCONFIRMED note about B19
On Flight 12, Booster 19 lit all 33 Raptor 3 engines and shut one down during ascent. After separation it could not light every planned boostback engine, ended that burn early, and was lost in a hard splashdown in the Gulf of America.
-
B1
Booster 16 B16
Assigned to F10 by a ledger claim.
2025-08-26 UNCONFIRMED note about B16
On Flight 10, Booster 16 lifted off on all 33 Raptors, lost one engine during ascent, completed boostback and a landing burn, hovered above the water, then shut down and splashed down. NASASpaceflight says the drop into the water and the explosion were intentional.
-
B2
Booster 15 B15
Assigned to F8, F11 by a ledger claim.
2025-10-13 UNCONFIRMED note about B15
On Flight 11, Booster 15, on its second flight, completed boostback on 12 of 13 planned engines, then lit all 13 for the landing burn, hovered above the water, shut down, and splashed down off the Texas coast. NASASpaceflight says it then dropped into the Gulf and exploded.
2025-03-06 UNCONFIRMED note about B15
On Flight 8, Booster 15 lit 33 Raptors, relit 11 of 13 planned engines for boostback, then 12 of 13 at the start of the landing burn, and was caught by the tower arms. This was the third Super Heavy catch.
-
B2
Booster 14 B14
Assigned to F7, F9 by a ledger claim.
2025-05-27 UNCONFIRMED note about B14
On Flight 9, Booster 14 flew again after Flight 7, the first Super Heavy reflight. It completed ascent on all 33 Raptors and boostback, then contact was lost shortly after the landing burn began and the booster broke up about six minutes after launch over the Gulf of America.
2025-01-16 UNCONFIRMED note about B14
On Flight 7, Booster 14 relit 12 of 13 planned engines for boostback, then all 13 for the landing burn, and was caught by the launch and catch tower arms. This was the second Super Heavy catch.
-
B1
Booster 11 B11
Assigned to F4 by a ledger claim.
2024-06-06 UNCONFIRMED note about B11
On Flight 4, Booster 11 completed its flip, boostback burn, and hot-stage jettison, then a landing burn and soft splashdown in the Gulf of Mexico seven minutes and 24 seconds after liftoff. One of the 13 landing engines did not reignite. It later tipped over.
-
B1
Booster 10 B10
Assigned to F3 by a ledger claim.
2024-03-14 UNCONFIRMED note about B10
On Flight 3, Booster 10 flipped and initiated its boostback burn toward a splashdown point in the Gulf of Mexico (SpaceX says initiated, not completed), lit several engines for its first landing burn, and broke up just under seven minutes into the flight at about 462 meters altitude.
-
B1
Booster 9 B9
Assigned to F2 by a ledger claim.
2023-11-18 UNCONFIRMED note about B9
On Flight 2, Booster 9 started all 33 Raptors and completed a full-duration ascent burn. After hot-staging it began the boostback burn, then broke up more than three and a half minutes into the flight at about 90 km over the Gulf of Mexico.
-
B1
-
S1
Ship 44 S44
2026-10-09 UNCONFIRMED note at MB2 about S44
Ship 44 is on the Mega Bay 2 turntable and is missing only its transfer tubes and drive/engine section; the transfer tubes are sitting in Starfactory.
-
S2
Ship 42 S42
Assigned to F15 by a ledger claim.
2026-10-09 UNCONFIRMED note at MAS about S42
Reported by 9 Oct: SpaceX removed all six engines from S42 and rolled it to Massey's for a third time, onto the ship cryo-proof stand. NSF says this work needs thrust ram testing, not just a cryo proof, before a static fire.
2026-10-09 transport S42 from MB2 to MAS
Ship 42 rolled to Massey's on the ship cryo stand after all 6 engines were removed.
-
S2
Ship 40 S40
Assigned to F13 by a ledger claim.
2026-10-13 note about S40
SpaceX: S40, the first Starship to return to its launch site, is vertical alongside three other ships in a Mega Bay at Starbase and will give first-of-its-kind data on a flown heatshield, Raptor engines and avionics. The post does not name the bay.
2026-07-24 UNCONFIRMED note about S40
On Flight 13, Ship 40 completed a full-duration ascent burn on all six Raptors, deployed 20 Starlink V3 satellites, relit a single Raptor in space, and made a landing flip, landing burn, and soft splashdown in the Indian Ocean, coming to rest intact.
-
S1
Ship 39 S39
Assigned to F12 by a ledger claim.
2026-05-22 UNCONFIRMED note about S39
On Flight 12, Ship 39 lost one Raptor vacuum engine during ascent and still reached its planned trajectory. It deployed 20 Starlink simulators and two modified Starlink satellites, then made a landing flip, landing burn, and splashdown in the Indian Ocean on two Raptor engines. NASASpaceflight says the planned in-space Raptor relight was canceled after the early engine-out.
-
S1
-
S1
Ship 37 S37
Assigned to F10 by a ledger claim.
2025-08-26 UNCONFIRMED note about S37
On Flight 10, Ship 37 completed a full-duration ascent burn, deployed eight Starlink simulators, relit a Raptor in space, and made a landing flip, landing burn, and soft splashdown in the Indian Ocean. NASASpaceflight says the ship tipped over and exploded after splashdown.
-
S1
Ship 35 S35
Assigned to F9 by a ledger claim.
2025-05-27 UNCONFIRMED note about S35
On Flight 9, Ship 35 completed a full-duration ascent burn. The payload bay door did not open, so eight Starlink simulator satellites were not deployed. An attitude control error bypassed the Raptor relight. Contact was lost about 46 minutes into the flight, with debris expected inside the planned hazard area in the Indian Ocean.
-
S1
Ship 34 S34
Assigned to F8 by a ledger claim.
2025-03-06 UNCONFIRMED note about S34
On Flight 8, Ship 34 lit all six Raptors and separated. Before the end of the ascent burn, an energetic event in the aft section took out several Raptors. Attitude control and communications were lost. Final contact was about 9 minutes and 30 seconds after liftoff.
-
S1
-
S1
-
S1
Ship 29 S29
Assigned to F4 by a ledger claim.
2024-06-06 UNCONFIRMED note about S29
On Flight 4, Ship 29 made a controlled reentry and a soft splashdown in the Indian Ocean one hour and six minutes after launch, after a flip and landing burn on its three center Raptors. Plasma burned through a forward flap hinge during reentry, and the flap still moved for the landing flip.
-
S1
Ship 28 S28
Assigned to F3 by a ledger claim.
2024-03-14 UNCONFIRMED note about S28
On Flight 3, Ship 28 completed a full-duration ascent burn, opened and closed its payload door, and started a propellant transfer demonstration. It did not attempt the planned Raptor relight because of roll rates during coast, then was lost during reentry. The last telemetry was about 49 minutes into the flight.
-
S1