Propulsion log
Raptor
51 claims whose own text names a Raptor, an RVac or an engine, across 12 boosters and 14 ships; 15 name a site. Boosters first, newest serial first; each vehicle's claims run newest first. A claim with an at links that site (McGregor stand notes land here too). 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.
Claim lanes
One lane per vehicle, one mark per claim whose own summary names a Raptor, an RVac or an engine. The lane is the one vehicle that claim names. Other is a claim that names none, or more than one. Filled marks are confirmed. Hollow marks are unconfirmed, and the table keeps the UNCONFIRMED stamp. A mark links its claim. This chart does not count engines, installs, or a status the summary does not state.
- Filled: confirmed claim
- Hollow: unconfirmed claim
| Date | Vehicle | Summary | Claim |
|---|---|---|---|
| 2026-10-18 | B23 | NSF (18 Oct): Booster 23's cryo testing at Massey's concluded over the weekend with a Sunday morning trip back to Mega Bay 1 for engine installation. | c-386222a51fc6 UNCONFIRMED |
| 2026-10-25 | B22 | SpaceX called the Booster 22 static fire for Flight 15 a full duration 33-engine static fire. | c-f3863dfdbddf |
| 2026-11-14 | B22 | Elon Musk says the green flame on Flight 15 came from burning copper from depleting fuel in the regenerative cooling circuit as the main combustion chamber went oxygen-rich, caused by slight engine underperformance. | c-83d97922fdf7 |
| 2026-11-14 | B22 | Blobifie says Dan Huot stated the Booster 22 landing abort was a GNC issue that led to a self abort and a Gulf splashdown, and that the flight termination system triggered after engine cutoff. | c-b2697042cfc0 UNCONFIRMED |
| 2026-11-14 | B22 | Elon Musk says the booster is meant to land with tiny residuals, so the fix is better engine performance and consistency (underway with Raptor V3.2) plus flight software that does MECO1 about one second earlier to leave enough propellant for boostback and landing. | c-f412e7e0cfed |
| 2026-09-24 | 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. | c-2bc0503173e3 UNCONFIRMED |
| 2026-09-28 | B21 | On Flight 14, Booster 21 lost one Raptor on ascent, completed its flight, and splashed down in the Gulf rather than being caught. | c-950e644bc753 |
| 2026-07-24 | 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. | c-fc92de05629a UNCONFIRMED |
| 2026-05-22 | 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. | c-1c2db72ab0dc UNCONFIRMED |
| 2025-08-26 | 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. | c-f248b8baf946 UNCONFIRMED |
| 2025-03-06 | 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. | c-19478c89efad UNCONFIRMED |
| 2025-10-13 | 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. | c-0ff98b6f31c0 UNCONFIRMED |
| 2025-01-16 | 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. | c-51c95f88a48f UNCONFIRMED |
| 2025-05-27 | 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. | c-3fef1ccf1258 UNCONFIRMED |
| 2024-06-06 | 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. | c-6cefbad49ccf UNCONFIRMED |
| 2024-03-14 | 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. | c-e2c333773393 UNCONFIRMED |
| 2023-11-18 | 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. | c-521addab083b UNCONFIRMED |
| 2023-04-20 | B7 | On Flight 1, Booster 7 had several Raptor engines fail after a fire in the engine section. The stack did not separate, lost altitude, and tumbled. The flight termination system was commanded on the booster. | c-1183489a8f78 UNCONFIRMED |
| 2026-11-07 | S45 | Ship 45's transfer tubes, pre-loaded on the installation jig, rolled through the Gigabay into Mega Bay 2. VickiCocks15 says the four point lifter went into Mega Bay 2 first to lift S45, then the transfer tube jig, then a single Raptor engine. | c-e9c47abea2ea |
| 2026-10-09 | 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. | c-b9ae8512388e UNCONFIRMED |
| 2026-10-09 | 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. | c-9b6ec52e1fb0 UNCONFIRMED |
| 2026-10-09 | S42 | Ship 42 rolled to Massey's on the ship cryo stand after all 6 engines were removed. | c-a5f8bc8925a1 |
| 2026-10-18 | S42 | TrackingTheSB weekly: inside Mega Bay 2, Ship 42 has engines installed again ahead of its static fire campaign for Flight 15, after all of its engines were removed following Flight 14. The post says the reason for the removal is not known. | c-3ed97de7367e |
| 2026-10-25 | S42 | TrackingTheSB weekly: SpaceX said on 23 Oct that an upgraded Raptor 3 debuts on Flight 15, which is why Ship 42's engines were removed and swapped. | c-58fb6c06e71d UNCONFIRMED |
| 2026-10-26 | S42 | Ship 42 was detanked after its single-engine static fire at Massey's. | c-45ef1080c51d UNCONFIRMED |
| 2026-10-26 | S42 | Ship 42 completed a single-engine static fire test at Massey's on the evening of 26 Oct (local time), after a depress vent signalled a single-engine burn. | c-974fb64c590a |
| 2026-10-27 | S42 | VickiCocks15 says Ship 42 lit only one engine in its static fire, so another static fire test may still come. | c-6d7e71f3a577 UNCONFIRMED |
| 2026-10-27 | S42 | Ship 42 completed a six-engine, full-duration static fire test at Massey's on 27 Oct (local time), about 60 seconds long, following its single-engine static fire the evening before. | c-73b91bdc20fc |
| 2026-10-28 | S42 | SpaceX said Ship 42's static fires are complete: the Starship preparing for Flight 15 performed a full-duration six-engine static fire and fired a single Raptor engine to simulate a deorbit burn. | c-2082215ccf2e |
| 2026-11-13 | S42 | SpaceX says Starship performed its orbital insertion burn with a single Raptor engine and entered an orbit of Earth (about 275 km planned), after the ascent burn left it on a planned suborbital trajectory. | c-a80c552639c5 |
| 2026-11-15 | S42 | Elon Musk says he went over the whole Starship heat shield and it looks great overall, the engines look great too, and Ship 42 could probably be reflown with a few weeks of refurbishment, but many small fixes are needed for airplane-like immediate reusability. LabPadre relayed the reflight line. | c-e05cd3af7489 |
| 2026-07-24 | 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. | c-64ee78a608cd UNCONFIRMED |
| 2026-10-13 | 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. | c-dfc4f52f6820 |
| 2026-05-22 | 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. | c-82f547533d17 UNCONFIRMED |
| 2025-10-13 | S38 | On Flight 11, Ship 38 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. | c-44da580f8ad4 UNCONFIRMED |
| 2025-08-26 | 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. | c-ec88a4546a58 UNCONFIRMED |
| 2025-05-27 | 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. | c-4ba932b6e2e5 UNCONFIRMED |
| 2025-03-06 | 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. | c-32a4eb9d16e9 UNCONFIRMED |
| 2025-01-16 | S33 | On Flight 7, Ship 33 lit all six Raptors after separation. A fire in the aft section led to a breakup during ascent, and telemetry was lost after about eight and a half minutes of flight. | c-cecaf3a7521e UNCONFIRMED |
| 2024-11-19 | S31 | On Flight 6, Ship 31 relit a single Raptor engine in space, then made it through reentry and a flip, landing burn, and soft splashdown in the Indian Ocean. | c-98e454c3dcb0 UNCONFIRMED |
| 2024-06-06 | 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. | c-38dfa4d86b22 UNCONFIRMED |
| 2024-03-14 | 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. | c-a0c555d347ee UNCONFIRMED |
| 2023-11-18 | S25 | On Flight 2, Ship 25 was the first Starship to reach outer space after a hot-staging separation. Telemetry was lost near the end of the second-stage burn, and a command destruct was triggered before engine cutoff. | c-107235b4efa6 UNCONFIRMED |
| 2026-10-07 | Other | Raptor North Stand at the McGregor test site; NSF reported a 557-second Raptor firing there. | c-0c29bfd3c695 UNCONFIRMED |
| 2026-10-07 | Other | Identify the Raptor North Stand at McGregor as hardware; NSF reported a 557-second Raptor firing on that stand. | c-95d2e036b37c UNCONFIRMED |
| 2026-10-07 | Other | NASASpaceflight: a Raptor fired for 557 seconds on the Raptor North Stand at McGregor, the second-longest firing on record and the longest that was not a run to failure. | c-ae9d2371b5a3 UNCONFIRMED |
| 2026-10-13 | Other | NASA's 13 Oct 2026 preliminary draft programmatic environmental assessment covers a roughly 400 acre SpaceX Starship campus at Kennedy Space Center near Roberts Road (SpaceX leases about 167 acres there now), with manufacturing and maintenance buildings, a payload processing facility and a Starship test stand for pressure testing and engine firings before vehicles go to the launch sites. FelixSchlang reads its noise study as assuming a Massey's-like stand with up to 20 static fires a year, 10 of them at night. Not an approval. | c-085f2806788d UNCONFIRMED |
| 2026-10-22 | Other | RGVaerialphotos says the ship static fire stand was moved back to the production site on 22 Oct, ahead of Ship 42 engine testing. | c-99af592807f3 UNCONFIRMED |
| 2026-10-23 | Other | RGVaerialphotos says the booster lifting jig was raised in Mega Bay 1 ahead of being attached to Booster 22 for its engine testing campaign at the launch site, with the booster transport ringwall sitting outside. | c-6968fce68c00 UNCONFIRMED |
| 2026-10-26 | Other | Elon Musk says SpaceX can only reliably get to around 230 tf of thrust with Raptor 3, and that Raptor 4 will be 300 tons of thrust at sea level, hopefully at about the same mass. | c-553f710d5299 |
| 2026-11-16 | Other | Elon Musk says Starship V4 will be about 70 m long, roughly a 40% length increase allowing more than 60% more propellant load, with the engine count raised to 9 by adding 3 Raptor Vacuum engines, and the V4 engines will be higher thrust. | c-e2161433021d |
-
B1
Booster 23 B23
Flight assignments, each from its own ledger claim: F16 booster UNCONFIRMED c-b95baad8d0df.
2026-10-18 UNCONFIRMED note at MB1 about B23
NSF (18 Oct): Booster 23's cryo testing at Massey's concluded over the weekend with a Sunday morning trip back to Mega Bay 1 for engine installation.
at MB1
NASASpaceflight Web page Counts with a second source
-
B4
Booster 22 B22
Flight assignments, each from its own ledger claim: F15 booster c-880a8ed89b9c.
2026-11-14 note about B22
Elon Musk says the booster is meant to land with tiny residuals, so the fix is better engine performance and consistency (underway with Raptor V3.2) plus flight software that does MECO1 about one second earlier to leave enough propellant for boostback and landing.
@elonmusk X post Confirms alone
2026-11-14 UNCONFIRMED note about B22
Blobifie says Dan Huot stated the Booster 22 landing abort was a GNC issue that led to a self abort and a Gulf splashdown, and that the flight termination system triggered after engine cutoff.
@Blobifie X post Counts with a second source
2026-11-14 note about B22
Elon Musk says the green flame on Flight 15 came from burning copper from depleting fuel in the regenerative cooling circuit as the main combustion chamber went oxygen-rich, caused by slight engine underperformance.
@elonmusk X post Confirms alone
2026-10-25 note at P2 about B22
SpaceX called the Booster 22 static fire for Flight 15 a full duration 33-engine static fire.
at P2
@SpaceX X post Confirms alone @NASASpaceflight X post Counts with a second source
-
B2
Booster 21 B21
Flight assignments, each from its own ledger claim: F14 booster c-5f0748a457e4.
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.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
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.
@TrackingTheSB X post Confirms alone
-
B1
Booster 20 B20
Flight assignments, each from its own ledger claim: F13 booster UNCONFIRMED c-42d3b5fbbbf6.
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.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
-
B1
Booster 19 B19
Flight assignments, each from its own ledger claim: F12 booster UNCONFIRMED c-1eea5bab414e.
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.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
-
B1
Booster 16 B16
Flight assignments, each from its own ledger claim: F10 booster UNCONFIRMED c-15300615774f.
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.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
-
B2
Booster 15 B15
Flight assignments, each from its own ledger claim: F8 booster UNCONFIRMED c-3421a657219c, F11 booster UNCONFIRMED c-0e3b0d48c452.
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.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
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.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
-
B2
Booster 14 B14
Flight assignments, each from its own ledger claim: F7 booster UNCONFIRMED c-9aa5d6089cbf, F9 booster UNCONFIRMED c-7d0ad0b29c3b.
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.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
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.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
-
B1
Booster 11 B11
Flight assignments, each from its own ledger claim: F4 booster UNCONFIRMED c-8b148a2a34c1.
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.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source NASASpaceflight Web page Counts with a second source
-
B1
Booster 10 B10
Flight assignments, each from its own ledger claim: F3 booster UNCONFIRMED c-868bdc7e5b4a.
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.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
-
B1
Booster 9 B9
Flight assignments, each from its own ledger claim: F2 booster UNCONFIRMED c-574f9578fca6.
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.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
-
B1
Booster 7 B7
Flight assignments, each from its own ledger claim: F1 booster UNCONFIRMED c-6b910ee23334.
2023-04-20 UNCONFIRMED note about B7
On Flight 1, Booster 7 had several Raptor engines fail after a fire in the engine section. The stack did not separate, lost altitude, and tumbled. The flight termination system was commanded on the booster.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
-
S1
Ship 45 S45
2026-11-07 note at MB2 about S45
Ship 45's transfer tubes, pre-loaded on the installation jig, rolled through the Gigabay into Mega Bay 2. VickiCocks15 says the four point lifter went into Mega Bay 2 first to lift S45, then the transfer tube jig, then a single Raptor engine.
at MB2
@VickiCocks15 X post Counts with a second source @VickiCocks15 X post Counts with a second source @TrackingTheSB X post Confirms alone
-
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.
at MB2
NASASpaceflight Web page Counts with a second source
-
S11
Ship 42 S42
Flight assignments, each from its own ledger claim: F15 ship c-13766e95320e.
2026-11-15 note about S42
Elon Musk says he went over the whole Starship heat shield and it looks great overall, the engines look great too, and Ship 42 could probably be reflown with a few weeks of refurbishment, but many small fixes are needed for airplane-like immediate reusability. LabPadre relayed the reflight line.
@elonmusk X post Confirms alone @LabPadre X post Counts with a second source
2026-11-13 note about S42
SpaceX says Starship performed its orbital insertion burn with a single Raptor engine and entered an orbit of Earth (about 275 km planned), after the ascent burn left it on a planned suborbital trajectory.
2026-10-28 note at MAS about S42
SpaceX said Ship 42's static fires are complete: the Starship preparing for Flight 15 performed a full-duration six-engine static fire and fired a single Raptor engine to simulate a deorbit burn.
at MAS
@SpaceX X post Confirms alone @FelixSchlang X post Counts with a second source
2026-10-27 static-fire S42 at MAS
Ship 42 completed a six-engine, full-duration static fire test at Massey's on 27 Oct (local time), about 60 seconds long, following its single-engine static fire the evening before.
at MAS
@NASASpaceflight X post Counts with a second source @TrackingTheSB X post Confirms alone @LabPadre X post Counts with a second source @Blobifie X post Counts with a second source @RoughRidersShow X post Counts with a second source @StarshipGazer X post Counts with a second source @VickiCocks15 X post Counts with a second source @SpaceX X post Confirms alone
2026-10-27 UNCONFIRMED note about S42
VickiCocks15 says Ship 42 lit only one engine in its static fire, so another static fire test may still come.
@VickiCocks15 X post Counts with a second source
2026-10-26 static-fire S42 at MAS
Ship 42 completed a single-engine static fire test at Massey's on the evening of 26 Oct (local time), after a depress vent signalled a single-engine burn.
at MAS
@NASASpaceflight X post Counts with a second source @LabPadre X post Counts with a second source @Blobifie X post Counts with a second source @RGVaerialphotos X post Counts with a second source @FelixSchlang X post Counts with a second source @CeaserG33 X post Counts with a second source @VickiCocks15 X post Counts with a second source @FelixSchlang X post Counts with a second source
2026-10-26 UNCONFIRMED note at MAS about S42
Ship 42 was detanked after its single-engine static fire at Massey's.
at MAS
@Blobifie X post Counts with a second source
2026-10-25 UNCONFIRMED note about S42
TrackingTheSB weekly: SpaceX said on 23 Oct that an upgraded Raptor 3 debuts on Flight 15, which is why Ship 42's engines were removed and swapped.
@TrackingTheSB X post Confirms alone
2026-10-18 note at MB2 about S42
TrackingTheSB weekly: inside Mega Bay 2, Ship 42 has engines installed again ahead of its static fire campaign for Flight 15, after all of its engines were removed following Flight 14. The post says the reason for the removal is not known.
at MB2
@TrackingTheSB X post Confirms alone
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.
at MAS
NASASpaceflight Web page Counts with a second source
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.
@TrackingTheSB X post Confirms alone @StarshipGazer X post Counts with a second source
-
S2
Ship 40 S40
Flight assignments, each from its own ledger claim: F13 ship UNCONFIRMED c-57b3f8aa2274.
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.
@SpaceX X post Confirms alone
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.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
-
S1
Ship 39 S39
Flight assignments, each from its own ledger claim: F12 ship UNCONFIRMED c-c991b2b738ba.
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.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
-
S1
Ship 38 S38
Flight assignments, each from its own ledger claim: F11 ship UNCONFIRMED c-70ba254dfc3d.
2025-10-13 UNCONFIRMED note about S38
On Flight 11, Ship 38 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.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
-
S1
Ship 37 S37
Flight assignments, each from its own ledger claim: F10 ship UNCONFIRMED c-066b480ec36a.
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.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
-
S1
Ship 35 S35
Flight assignments, each from its own ledger claim: F9 ship UNCONFIRMED c-658ec636df4c.
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.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
-
S1
Ship 34 S34
Flight assignments, each from its own ledger claim: F8 ship UNCONFIRMED c-ff270c9839ae.
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.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
-
S1
Ship 33 S33
Flight assignments, each from its own ledger claim: F7 ship UNCONFIRMED c-a595457f7171.
2025-01-16 UNCONFIRMED note about S33
On Flight 7, Ship 33 lit all six Raptors after separation. A fire in the aft section led to a breakup during ascent, and telemetry was lost after about eight and a half minutes of flight.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
-
S1
Ship 31 S31
Flight assignments, each from its own ledger claim: F6 ship UNCONFIRMED c-1390fd704ecf.
2024-11-19 UNCONFIRMED note about S31
On Flight 6, Ship 31 relit a single Raptor engine in space, then made it through reentry and a flip, landing burn, and soft splashdown in the Indian Ocean.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
-
S1
Ship 29 S29
Flight assignments, each from its own ledger claim: F4 ship UNCONFIRMED c-82ae4ae622c0.
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.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
-
S1
Ship 28 S28
Flight assignments, each from its own ledger claim: F3 ship UNCONFIRMED c-3cdc6e921e7c.
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.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
-
S1
Ship 25 S25
Flight assignments, each from its own ledger claim: F2 ship UNCONFIRMED c-72ff7aa51515.
2023-11-18 UNCONFIRMED note about S25
On Flight 2, Ship 25 was the first Starship to reach outer space after a hot-staging separation. Telemetry was lost near the end of the second-stage burn, and a command destruct was triggered before engine cutoff.
SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source
-
?8
Not tied to one vehicle
2026-11-16 note about F16
Elon Musk says Starship V4 will be about 70 m long, roughly a 40% length increase allowing more than 60% more propellant load, with the engine count raised to 9 by adding 3 Raptor Vacuum engines, and the V4 engines will be higher thrust.
@elonmusk X post Confirms alone
2026-10-26 note at MCG
Elon Musk says SpaceX can only reliably get to around 230 tf of thrust with Raptor 3, and that Raptor 4 will be 300 tons of thrust at sea level, hopefully at about the same mass.
at MCG
@elonmusk X post Confirms alone @elonmusk X post Confirms alone @FelixSchlang X post Counts with a second source
2026-10-23 UNCONFIRMED note at MB1
RGVaerialphotos says the booster lifting jig was raised in Mega Bay 1 ahead of being attached to Booster 22 for its engine testing campaign at the launch site, with the booster transport ringwall sitting outside.
at MB1
@RGVaerialphotos X post Counts with a second source
2026-10-22 UNCONFIRMED note at SFC
RGVaerialphotos says the ship static fire stand was moved back to the production site on 22 Oct, ahead of Ship 42 engine testing.
at SFC
@RGVaerialphotos X post Counts with a second source
2026-10-13 UNCONFIRMED filing NASA ea
NASA's 13 Oct 2026 preliminary draft programmatic environmental assessment covers a roughly 400 acre SpaceX Starship campus at Kennedy Space Center near Roberts Road (SpaceX leases about 167 acres there now), with manufacturing and maintenance buildings, a payload processing facility and a Starship test stand for pressure testing and engine firings before vehicles go to the launch sites. FelixSchlang reads its noise study as assuming a Massey's-like stand with up to 20 static fires a year, 10 of them at night. Not an approval.
WESH Web page Counts with a second source @FelixSchlang X post Counts with a second source
2026-10-07 UNCONFIRMED note at MCG
NASASpaceflight: a Raptor fired for 557 seconds on the Raptor North Stand at McGregor, the second-longest firing on record and the longest that was not a run to failure.
at MCG
@NASASpaceflight X post Counts with a second source
2026-10-07 UNCONFIRMED note at MCG about mcgregor-raptor-north
Raptor North Stand at the McGregor test site; NSF reported a 557-second Raptor firing there.
at MCG
@NASASpaceflight X post Counts with a second source
2026-10-07 UNCONFIRMED identify hardware Raptor North Stand
Identify the Raptor North Stand at McGregor as hardware; NSF reported a 557-second Raptor firing on that stand.
@NASASpaceflight X post Counts with a second source