Nerdy, sourced Starship tracking at every site

Claimstrip

06:14 CST at Starbase

MODEL / NOT A CLAIM

Next flights: projection from past cadence

Built as of 2026-11-16. A model of possible timing, not an announced date or a promise. Sourced flight dates remain on the flights sheet.

The latest completed flight needs an agreed outcome and flown date. Projection unavailable until its evidence is resolved in the ledger.

Readiness assumption

0 of 4 model signals have confirmed evidence. These four signals are a timing proxy, not a complete readiness checklist or clearance to fly. See the sourced flight record.

How to read this model

Use all positive gaps between consecutive numbered flights with both an agreed confirmed outcome and an agreed confirmed completed-flight schedule. The schedule supplies the flight day; a planned date alone never proves a flight. Missing flight numbers are not bridged. Conflicts, unconfirmed evidence and claims after the build date are excluded.

For the first future flight, keep only gaps longer than the wait since the last completed flight and subtract that wait. The minimum remaining wait is one quarter of the historical median gap per missing readiness signal, rounded up, with at least one day remaining. Here the median gap is unavailable days and that floor is 0 days. This readiness rule is an explicit modelling assumption, not a measured relationship. Static fires must be recorded as tests since the last completed flight; notes do not count.

For each later flight, independently add another full historical gap, sampled with replacement and equal weight. Enumerate every combination, then take the first whole-day value reaching 10%, 50% or 90% of the model paths. By P10, at least 10% of paths have occurred; P50 is the median; by P90, at least 90% have occurred. The span bounds the middle 80% of model paths; tied dates can include more. This is not an 80% guarantee about reality. Later flights assume a repeat of past cadence without their own readiness adjustment.

History may miss flights and test evidence. Vehicle changes, regulation, pad work and new failures can break this model. Fewer than 3 gaps withholds the band; fewer than 8 warns of a small sample. No surviving first-step gap also withholds the band. No random draws or current clock are used.

Ledger sample: 14 dated completed flights, 13 gaps

Newest flights first. Launch dates link to schedule claims. Each gap is measured from the preceding consecutive flight; outcome summaries are followed by links to their ledger claims.

  1. F14 Launch 2026-09-28 Gap from F13: 66 days

    On 28 Sep 2026 Starship lifted off from Starbase on its 14th flight. SpaceX calls this the first orbital Starship flight and the first to deliver payload to orbit, 26 Starlink V3 satellites. The ship first reached a passively safe suborbital trajectory, then performed an orbit insertion burn and entered orbit. It deployed the satellites, left orbit on a deorbit burn, and splashed down in the northern Pacific Ocean. Super Heavy splashed down in the Gulf. At booster landing-burn shutdown its flight termination system was triggered. Outcome claim c-0a2b5043ee66

  2. F13 Launch 2026-07-24 Gap from F12: 63 days

    On 24 Jul 2026 Starship lifted off from Starbase. Super Heavy ended its boostback early and had a hard splashdown in the Gulf. The ship deployed 20 Starlink V3 satellites, relit in space, then made a landing flip, a landing burn and a soft splashdown in the Indian Ocean, coming to rest intact. Outcome claim c-5cc373e24117

  3. F12 Launch 2026-05-22 Gap from F11: 221 days

    On 22 May 2026 Starship lifted off from Starbase on the first flight of the V3 vehicles and the first flight from Pad 2. Super Heavy could not complete boostback and had a hard splashdown in the Gulf of America. The ship reached its planned trajectory, deployed 20 Starlink simulators and two modified Starlink satellites on that same suborbital trajectory, then made a landing flip, a landing burn and a splashdown in the Indian Ocean. Outcome claim c-1c676c13e2cf

  4. F11 Launch 2025-10-13 Gap from F10: 48 days

    On 13 Oct 2025 Starship lifted off from Starbase on its eleventh flight test, the final flight of the second-generation ship and the first-generation Super Heavy, and the final launch from the current configuration of Pad 1. Super Heavy hovered above the water, shut down and splashed down off the Texas coast. The ship deployed eight Starlink simulators, relit in space, then made a landing flip, a landing burn and a soft splashdown in the Indian Ocean. SpaceX says the following vehicles are for the first Starship orbital flights. Outcome claim c-bdab56392720

  5. F10 Launch 2025-08-26 Gap from F9: 91 days

    On 26 Aug 2025 Starship lifted off from Starbase. Super Heavy completed boostback toward a splashdown zone, hovered above the water, shut down and splashed down. The ship flew a suborbital trajectory, deployed eight Starlink simulators, relit in space, then made a landing flip, a landing burn and a soft splashdown in the Indian Ocean. Outcome claim c-a2ea477e7df7

  6. F9 Launch 2025-05-27 Gap from F8: 82 days

    On 27 May 2025 Starship lifted off from Starbase on the first reflight of a Super Heavy booster. The booster relit for a landing burn toward a splashdown area in the Gulf of America, then contact was lost and it had a rapid unscheduled disassembly about 6 minutes after launch. The ship's payload bay door did not open, so eight Starlink simulator satellites were not deployed. Contact with the ship was lost about 46 minutes into the flight, with debris inside the planned hazard area in the Indian Ocean. Outcome claim c-537f7c0fc125

  7. F8 Launch 2025-03-06 Gap from F7: 49 days

    On 6 Mar 2025 Starship lifted off from Starbase. Super Heavy flew a boostback and a landing burn to the launch and catch tower and was caught by the tower arms, the third Super Heavy catch. An energetic event in the aft of the ship led to loss of attitude control and loss of communications. Final contact was about 9 minutes and 30 seconds after liftoff. Outcome claim c-6bebbd589de6

  8. F7 Launch 2025-01-16 Gap from F6: 58 days

    On 16 Jan 2025 Starship lifted off from Starbase. Super Heavy flew its boostback and landing burn back to the launch and catch tower and was caught by the tower arms, the second Super Heavy catch. Telemetry from the ship was lost after about eight and a half minutes, and a fire in the aft section led to a rapid unscheduled disassembly. Outcome claim c-95aeff943b80

  9. F6 Launch 2024-11-19 Gap from F5: 37 days

    On 19 Nov 2024 Starship lifted off from Starbase. Automated health checks on the launch and catch tower aborted the booster catch attempt. Super Heavy diverted, then made a landing burn and a soft splashdown in the Gulf of Mexico. The ship reignited in space, made it through reentry, and finished with a flip, a landing burn and a soft splashdown in the Indian Ocean. SpaceX calls data and flight learnings the primary payload, and places this flight before fully orbital missions. Outcome claim c-efa04be0475a

  10. F5 Launch 2024-10-13 Gap from F4: 129 days

    On 13 Oct 2024 Starship lifted off. Super Heavy returned after boostback, performed its landing burn, and was caught by the chopstick arms of the launch and catch tower at Starbase. The ship completed ascent into outer space, then a controlled reentry, a flip, a landing burn and a splashdown in the Indian Ocean. The flight ended 1 hour, 5 minutes and 40 seconds after launch. Outcome claim c-6229581009e1

  11. F4 Launch 2024-06-06 Gap from F3: 84 days

    On 6 Jun 2024 Starship lifted off from Starbase. Super Heavy finished with a landing burn and a soft splashdown in the Gulf of Mexico seven minutes and 24 seconds into the flight. The ship made a controlled reentry, a flip and a landing burn, then a soft splashdown in the Indian Ocean one hour and six minutes after launch. SpaceX says the payload for this test was the data. Outcome claim c-651ccb304c04

  12. F3 Launch 2024-03-14 Gap from F2: 117 days

    On 14 Mar 2024 Starship lifted off from Starbase. Super Heavy initiated a boostback burn toward a splashdown point in the Gulf of Mexico, lit a landing burn, and then had a rapid unscheduled disassembly at about 462 m, just under seven minutes into the mission. The ship completed its ascent burn, opened and closed its payload door, and did not attempt a relight. The last telemetry arrived about 49 minutes into the mission, during entry. Outcome claim c-a2cbe6903b99

  13. F2 Launch 2023-11-18 Gap from F1: 212 days

    On 18 Nov 2023 Starship lifted off from Starbase. After separation the Super Heavy booster completed its flip, initiated the boostback burn, and then broke up at about 90 km over the Gulf of Mexico. The ship reached outer space. Telemetry was lost near the end of the second stage burn, and a command destruct was triggered. Outcome claim c-8e434e32d29c

  14. F1 Launch 2023-04-20 No preceding gap for this flight

    Starship's first integrated flight test lifted off from the orbital launch pad at Starbase on 20 Apr 2023. It reached an apogee of ~39 km over the Gulf of Mexico, lost altitude and began to tumble. The flight termination system was commanded on both the booster and the ship. Outcome claim c-21a8f721726d

Vehicle production cadence

Milestones stated by ledger claims. Dates are claim dates, not reconstructed event dates. Filled marks are CONFIRMED; hollow marks are UNCONFIRMED.

One row per ship or booster, newest serial first. Nearby marks are spread within their row. Test articles are excluded. Keyword method.

Stacking / section work stacked, installed or received sections Rollout / test move whole vehicle to Massey's, a stand or a pad Cryo / proof test cryo or proof test stated done Static fire static fire stated done Flight launched, flew or a past flight outcome

Vehicle milestone claims by dateShips and boosters share a date axis. Each linked circle is one milestone claim. A text table follows. 2023-04-20 2024-03-11 2025-02-01 2025-12-24 2026-11-15 Ships Boosters Ship 45Ship 452026-10-09 | Stacking / section work | Identify Ship 45. NSF reports its nose cone is stacked on its payload bay at Starfactory.2026-10-09 | Stacking / section work | NSF reports Ship 45 nose cone stacked on its payload bay at Starfactory, waiting for Ship 44 to finish stacking before S45 leaves the Starfactory turntable.2026-10-23 | Stacking / section work | Ship 45's forward section moved into Mega Bay 2 and was sleeved over the Pez Dispenser mechanism, having moved out of Starfactory the previous evening.2026-10-31 | Flight | VickiCocks15 says the Ship 45 common dome section was moved from Starfactory into Mega Bay 2 and was seen being lifted off its stand for integration with the ship.2026-11-10 | Stacking / section work | Ship 45 was sleeved over its transfer tubes in Mega Bay 2 and the jig removed, then the final Ship section arrived. VickiCocks15 describes the sequence; lewisknaggs42 says the nose cone rollout to the aft section took 19 days, credited to LabPadre. Ship 44Ship 442026-09-01 | Stacking / section work | Reported by 1 Sep 2026: Ship 44 nosecone TPS work complete, forward flaps installed, and the nosecone stacked onto the payload bay in Starfactory.2026-09-27 | Stacking / section work | Reported 27 Sep 2026: Ship 44 began main body assembly in the week of 21 Sep, with the N:3 and FX:4 rolling into Mega Bay 2.2026-10-05 | Stacking / section work | Ship 44 A2:4 rolled into Mega Bay 2.2026-10-17 | Stacking / section work | S44 has gained its transfer tubes.2026-10-17 | Stacking / section work | S44, with decals applied and transfer tubes installed or being installed, sits front and centre in Mega Bay 2 awaiting a lift to a work stand for further work.2026-10-18 | Stacking / section work | Ship 44, now fitted with its transfer tubes, was lifted clear of the transfer tube jig and moved to a work stand inside Mega Bay 2, and the jig went back to Starfactory.2026-10-20 | Stacking / section work | Ship 44's AX:4 aft section, its final section, moved from Starfactory into Mega Bay 2 for stacking.2026-10-22 | Stacking / section work | With the Mega Bay 2 centre stand vacated by Ship 43, raceways and the left aft flap were staged in place ahead of Ship 44 taking the spot.2026-10-22 | Stacking / section work | A crane in the Mega Bay 2 doorway was staging the right side aft flap ahead of Ship 44's move to the centre work stand.2026-10-23 | Stacking / section work | Ship 44's raceways have been staged ahead of install.2026-10-25 | Stacking / section work | TrackingTheSB weekly: Ship 44's AX:4 section completes its major body assembly, barring aft flap install. Ship 43Ship 432026-10-09 | Stacking / section work | Ship 43 is inside Mega Bay 2 finishing internals and is still missing its starboard-side aft flap. NSF says it was fully stacked on 15 Sep 2026.2026-10-22 | Rollout / test move | Ship 43 was lifted onto the ship cryo stand, rolled out of Mega Bay 2 and set off along Highway 4 to Massey's for cryogenic proof testing.2026-10-23 | Cryo / proof test | Ship 43 started its first cryogenic proof test at Massey's on the evening of 23 Oct.2026-10-23 | Cryo / proof test | Blobifie says Ship 43 completed two cryogenic proof tests at Massey's on 23 Oct.2026-10-26 | Rollout / test move | Ship 43 departed the production site and arrived at Pad 2 for chopstick testing. Ship 42Ship 422026-10-09 | Rollout / test move | 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 | Rollout / test move | Ship 42 rolled to Massey's on the ship cryo stand after all 6 engines were removed.2026-10-09 | Cryo / proof test | Ship 42 frosted on both tanks during cryo testing.2026-10-18 | Stacking / section work | 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.2026-10-25 | Static fire | VickiCocks15 expects Ship 44 to move to the centre stand and Ship 43 and Ship 42 to swap places at Massey's in the night transport move, for an S42 static fire test.2026-10-26 | Rollout / test move | Ship 42 rolled from the production site down Highway 4 to Massey's for static fire testing, followed by a ship aft barrel section with some tiles on it.2026-10-26 | Static fire | 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.2026-10-27 | Static fire | VickiCocks15 says Ship 42 lit only one engine in its static fire, so another static fire test may still come.2026-10-27 | Static fire | 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.2026-11-15 | Rollout / test move | Blobifie says Ship 42 was safed and its transport stand moved to the launch site, and later (04:22 UTC) that S42 was still hanging from the chopsticks attached to the SQD, with a beacon set up in the rocket garden where it will be displayed. Ship 41Ship 412026-09-22 | Rollout / test move | Flight 14 pad flow: Ship 41, the first orbital ship, followed Booster 21 to the pad a day later. The post does not name the pad.2026-09-26 | Stacking / section work | Flight 14 pad flow: Ship 41 was restacked on Booster 21.2026-09-28 | Flight | Identify Ship 41 as the Starship upper stage that flew Starship Flight 14.2026-09-28 | Flight | Flight 14 was the first orbital Starship flight and the first to deliver payload to orbit: 26 Starlink V3 satellites. Ship 41 entered orbit, deployed the satellites, deorbited, and splashed down in the Pacific Ocean. Ship 40Ship 402026-07-24 | Flight | 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.2026-11-07 | Rollout / test move | Ship 40 was lifted onto a transport stand in Mega Bay 2, rolled out of Mega Bay 2 and moved into a Gigabay work cell, the first vehicle to enter the Gigabay. The TrackingTheSB weekly says it went around Sanchez and the parking garage to the front of the Gigabay, with visible rust and damage to both flaps. Ship 39Ship 392026-05-22 | Flight | Identify Ship 39 as the Starship upper stage that flew Starship Flight 12, the first flight of a Block 3 ship.2026-05-22 | Flight | 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. Ship 38Ship 382025-10-13 | Flight | Identify Ship 38 as the Starship upper stage that flew Starship Flight 11.2025-10-13 | Flight | 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. Ship 37Ship 372025-08-26 | Flight | Identify Ship 37 as the Starship upper stage that flew Starship Flight 10.2025-08-26 | Flight | 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. Ship 36Ship 362025-08-15 | Static fire | Identify Ship 36. SpaceX names the Ship 36 static fire anomaly in its Flight 9 and Ship 36 investigation summary. Ship 35Ship 352025-05-27 | Flight | Identify Ship 35 as the Starship upper stage that flew Starship Flight 9.2025-05-27 | Flight | 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. Ship 34Ship 342025-03-06 | Flight | Identify Ship 34 as the Starship upper stage that flew Starship Flight 8 with Booster 15.2025-03-06 | Flight | 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. Ship 33Ship 332025-01-16 | Flight | Identify Ship 33 as the Starship upper stage that flew Starship Flight 7. NASASpaceflight describes it as the first Block 2 ship to fly.2025-01-16 | Flight | 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. Ship 31Ship 312024-11-19 | Flight | Identify Ship 31 as the Starship upper stage that flew Starship Flight 6.2024-11-19 | Flight | 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. Ship 30Ship 302024-10-13 | Flight | Identify Ship 30 as the Starship upper stage that flew Starship Flight 5.2024-10-13 | Flight | On Flight 5, Ship 30 completed a controlled reentry, a flip, a landing burn, and a splashdown in the Indian Ocean. The flight ended 1 hour, 5 minutes and 40 seconds after launch. NASASpaceflight reports a soft splashdown, then an explosion after the ship tipped over. Ship 29Ship 292024-06-06 | Flight | Identify Ship 29 as the Starship upper stage that flew Starship Flight 4.2024-06-06 | Flight | 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. Ship 28Ship 282024-03-14 | Flight | Identify Ship 28 as the Starship upper stage that flew Starship Flight 3.2024-03-14 | Flight | 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. Ship 25Ship 252023-11-18 | Flight | Identify Ship 25 as the Starship upper stage that flew Starship Flight 2.2023-11-18 | Flight | 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. Ship 24Ship 242023-04-20 | Flight | Identify Ship 24 as the Starship upper stage that flew Starship Flight 1.2023-04-20 | Flight | On Flight 1, Ship 24 did not separate from the booster. The flight termination system was commanded on the ship after the stack tumbled. The flight reached an apogee of about 39 km. Booster 25Booster 25 Booster 24Booster 242026-09-27 | Stacking / section work | Reported 27 Sep 2026: Booster 24 began construction in the week of 21 Sep, with its A2:4 section rolling into Mega Bay 1.2026-10-02 | Stacking / section work | Booster 24 A5:4 rolled from Starfactory to Mega Bay 1. Initially misidentified as A6.2026-10-07 | Stacking / section work | Booster 24 A6:4 rolled from Starfactory to Mega Bay 1.2026-10-07 | Stacking / section work | Booster 24 methane landing tank and lower transfer tube rolled from Starfactory to Mega Bay 1.2026-10-08 | Stacking / section work | Booster 24 full transfer tube rolled into Mega Bay 1.2026-10-16 | Stacking / section work | Seen on a flyover: Booster 24 was getting its LOX landing tank installed, with Booster 22 behind it. The post does not name the building.2026-10-18 | Stacking / section work | TrackingTheSB weekly: in Mega Bay 1, Booster 24 received its final aft section (AX:2) and its landing tank, completing the lower half of the booster that makes up the LOX tank. CH4 tank stacking and mating the two halves come next.2026-10-22 | Stacking / section work | TrackingTheSB weekly: Booster 24 received its forward section this week, F2:4 on 20 Oct, HS-FX:3 on 22 Oct and F3:4 on 24 Oct.2026-10-29 | Stacking / section work | VickiCocks15 reports the booster LOX landing tank install jig was brought back towards Mega Bay 1, and reads it as crews being about ready to stack the two halves of Booster 24; the jig supports the tank during stacking.2026-10-30 | Stacking / section work | VickiCocks15 reports the LOX landing tank jig, moved into position the day before, was moved back inside Mega Bay 1 this morning for Booster 24 stacking ops.2026-10-31 | Stacking / section work | VickiCocks15 says the LOX landing tank jig was removed from MB-1 again, which she reads as Booster 24 now being fully stacked inside the bay. Booster 23Booster 232026-09-08 | Stacking / section work | Booster 23 AX:2 section rolled across from Starfactory into Mega Bay 1, before its landing tank had been seen.2026-09-09 | Stacking / section work | Booster 23 F2:4 section rolled into Mega Bay 1, the start of its CH4 tank.2026-09-20 | Stacking / section work | Reported 20 Sep 2026: Booster 23 received its integrated hot stage ring and forward dome section, the second step in stacking its CH4 tank after F2.2026-09-21 | Stacking / section work | Booster 23 received its F3:4 section, completing the liquid methane tank section. The post does not name the bay.2026-09-25 | Stacking / section work | Booster 23 CH4 tank stack was stacked on top of its aft section, completing major construction; outfitting comes next, ahead of cryo proof.2026-10-12 | Rollout / test move | Booster 23 lifted onto the booster cryo / thrust sim stand.2026-10-13 | Rollout / test move | Booster 23 rolled from the production site to Massey's for its initial cryo proof testing.2026-10-15 | Cryo / proof test | Booster 23 underwent its first cryogenic proof test at Massey's.2026-10-18 | Cryo / proof test | 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.2026-10-18 | Cryo / proof test | TrackingTheSB weekly: Booster 23 completed only one cryogenic proof test at Massey's before rolling back to the production site. Every previous booster apart from BN3 in 2021 did at least two; the cause of the early end is not known. Booster 22Booster 222026-09-08 | Rollout / test move | Booster 22 rolled from Mega Bay 1 to the Massey's test site and was lifted onto the cryo stand for cryo proof testing.2026-09-09 | Cryo / proof test | Booster 22 completed a full cryo test at Massey's, filled and held at pressure before detanking, from the afternoon into the night of 9 Sep.2026-09-11 | Cryo / proof test | Blobifie says Booster 22 completed what looked to have been a partial cryo test at Massey's and was then detanked.2026-10-24 | Rollout / test move | Booster 22 was lifted onto a transport stand, left Mega Bay 1, drove Highway 4 and arrived at the launch site (Pad 2) on the morning of 24 Oct ahead of its static fire campaign.2026-10-24 | Rollout / test move | Booster 22 was lifted onto the Pad 2 orbital launch mount and lowered onto it on the afternoon of 24 Oct.2026-10-25 | Static fire | Booster 22 completed a static fire test on Pad 2 at Starbase. Blobifie reports the burn lasted more than 15 seconds.2026-10-25 | Static fire | SpaceX called the Booster 22 static fire for Flight 15 a full duration 33-engine static fire.2026-10-25 | Flight | Booster 22 was lifted off the Pad 2 launch mount to catch height at the top of the tower, then set on the booster transport ring for its trip back to Mega Bay 1 for final flight preparations.2026-11-09 | Rollout / test move | Booster 22 left the production site and arrived at the Pad 2 launch site on the evening of 9 Nov (Texas time), for Flight 15. Trackers posted it as T-93 hours.2026-11-14 | Flight | 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. Booster 21Booster 212026-09-21 | Rollout / test move | Flight 14 pad flow: Booster 21 rolled to the pad and was stacked the same day. The post does not name the pad.2026-09-28 | Flight | Identify Booster 21 as the Super Heavy booster that flew Starship Flight 14.2026-09-28 | Flight | On Flight 14, Booster 21 lost one Raptor on ascent, completed its flight, and splashed down in the Gulf rather than being caught. Booster 20Booster 202026-07-24 | Flight | Identify Booster 20 as the Super Heavy booster that flew Starship Flight 13, the second flight of a Block 3 booster.2026-07-24 | Flight | 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. Booster 19Booster 192026-05-22 | Flight | Identify Booster 19 as the Super Heavy booster that flew Starship Flight 12, the first flight of a Block 3 booster.2026-05-22 | Flight | 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. Booster 18Booster 18 Booster 16Booster 162025-08-26 | Flight | Identify Booster 16 as the Super Heavy booster that flew Starship Flight 10.2025-08-26 | Flight | 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. Booster 15Booster 152025-03-06 | Flight | Identify Booster 15 as the Super Heavy booster that flew Starship Flight 8 with Ship 34.2025-03-06 | Flight | 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.2025-10-13 | Flight | 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. Booster 14Booster 142025-01-16 | Flight | Identify Booster 14 as the Super Heavy booster that flew Starship Flight 7. NASASpaceflight describes it as a Block 1 booster.2025-01-16 | Flight | 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.2025-05-27 | Flight | 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. Booster 13Booster 132024-11-19 | Flight | Identify Booster 13 as the Super Heavy booster that flew Starship Flight 6.2024-11-19 | Flight | On Flight 6, an automated health check of hardware on the launch and catch tower aborted the catch attempt for Booster 13. The booster diverted and made a landing burn and soft splashdown in the Gulf of Mexico. Booster 12Booster 122024-10-13 | Flight | Identify Booster 12 as the Super Heavy booster that flew Starship Flight 5.2024-10-13 | Flight | On Flight 5, Booster 12 returned to the launch site after boostback and was caught by the chopstick arms of the launch and catch tower at Starbase, the first Super Heavy catch. Booster 11Booster 112024-06-06 | Flight | Identify Booster 11 as the Super Heavy booster that flew Starship Flight 4.2024-06-06 | Flight | 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. Booster 10Booster 102024-03-14 | Flight | Identify Booster 10 as the Super Heavy booster that flew Starship Flight 3.2024-03-14 | Flight | 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. Booster 9Booster 92023-11-18 | Flight | Identify Booster 9 as the Super Heavy booster that flew Starship Flight 2.2023-11-18 | Flight | 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. Booster 7Booster 72023-04-20 | Flight | Identify Booster 7 as the Super Heavy booster that flew Starship Flight 1.2023-04-20 | Flight | 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.

First dated claims by vehicle

Ship 45: Stacking / section work: 2026-10-09 (UNCONFIRMED); Flight: 2026-10-31 (UNCONFIRMED).

Ship 44: Stacking / section work: 2026-09-01 (CONFIRMED).

Ship 43: Stacking / section work: 2026-10-09 (UNCONFIRMED); Rollout / test move: 2026-10-22 (CONFIRMED); Cryo / proof test: 2026-10-23 (CONFIRMED).

Ship 42: Stacking / section work: 2026-10-18 (CONFIRMED); Rollout / test move: 2026-10-09 (UNCONFIRMED); Cryo / proof test: 2026-10-09 (CONFIRMED); Static fire: 2026-10-25 (UNCONFIRMED).

Ship 41: Stacking / section work: 2026-09-26 (UNCONFIRMED); Rollout / test move: 2026-09-22 (UNCONFIRMED); Flight: 2026-09-28 (CONFIRMED).

Ship 40: Rollout / test move: 2026-11-07 (CONFIRMED); Flight: 2026-07-24 (UNCONFIRMED).

Ship 39: Flight: 2026-05-22 (UNCONFIRMED).

Ship 38: Flight: 2025-10-13 (UNCONFIRMED).

Ship 37: Flight: 2025-08-26 (UNCONFIRMED).

Ship 36: Static fire: 2025-08-15 (CONFIRMED).

Ship 35: Flight: 2025-05-27 (UNCONFIRMED).

Ship 34: Flight: 2025-03-06 (UNCONFIRMED).

Ship 33: Flight: 2025-01-16 (UNCONFIRMED).

Ship 31: Flight: 2024-11-19 (UNCONFIRMED).

Ship 30: Flight: 2024-10-13 (UNCONFIRMED).

Ship 29: Flight: 2024-06-06 (UNCONFIRMED).

Ship 28: Flight: 2024-03-14 (UNCONFIRMED).

Ship 25: Flight: 2023-11-18 (UNCONFIRMED).

Ship 24: Flight: 2023-04-20 (UNCONFIRMED).

Booster 25: no dated milestone claims.

Booster 24: Stacking / section work: 2026-09-27 (CONFIRMED).

Booster 23: Stacking / section work: 2026-09-08 (CONFIRMED); Rollout / test move: 2026-10-12 (CONFIRMED); Cryo / proof test: 2026-10-15 (CONFIRMED).

Booster 22: Rollout / test move: 2026-09-08 (UNCONFIRMED); Cryo / proof test: 2026-09-09 (CONFIRMED); Static fire: 2026-10-25 (CONFIRMED); Flight: 2026-10-25 (CONFIRMED).

Booster 21: Rollout / test move: 2026-09-21 (UNCONFIRMED); Flight: 2026-09-28 (CONFIRMED).

Booster 20: Flight: 2026-07-24 (UNCONFIRMED).

Booster 19: Flight: 2026-05-22 (UNCONFIRMED).

Booster 18: no dated milestone claims.

Booster 16: Flight: 2025-08-26 (UNCONFIRMED).

Booster 15: Flight: 2025-03-06 (UNCONFIRMED).

Booster 14: Flight: 2025-01-16 (UNCONFIRMED).

Booster 13: Flight: 2024-11-19 (UNCONFIRMED).

Booster 12: Flight: 2024-10-13 (UNCONFIRMED).

Booster 11: Flight: 2024-06-06 (UNCONFIRMED).

Booster 10: Flight: 2024-03-14 (UNCONFIRMED).

Booster 9: Flight: 2023-11-18 (UNCONFIRMED).

Booster 7: Flight: 2023-04-20 (UNCONFIRMED).

Consecutive serial claims

Compare the same kind only. These are days between claims, not elapsed time between real events. Negative values mean the newer serial has an earlier claim.

Days between first like-kind claimsNewer serials run left to right within ships and boosters. Each row has a zero line; negative gaps sit below it. Text comparisons follow. Ships: newer serial in build orderShipsS25S29S30S31S34S35S38S39S40S41S42S43S44S45Section workSection workS41 to S42 | Stacking / section work | 2026-09-26 to 2026-10-18 | 22 days22S42 to S43 | Stacking / section work | 2026-10-18 to 2026-10-09 | -9 days-9S43 to S44 | Stacking / section work | 2026-10-09 to 2026-09-01 | -38 days-38S44 to S45 | Stacking / section work | 2026-09-01 to 2026-10-09 | 38 days38RolloutRolloutS40 to S41 | Rollout / test move | 2026-11-07 to 2026-09-22 | -46 days-46S41 to S42 | Rollout / test move | 2026-09-22 to 2026-10-09 | 17 days17S42 to S43 | Rollout / test move | 2026-10-09 to 2026-10-22 | 13 days13Cryo / proofCryo / proofS42 to S43 | Cryo / proof test | 2026-10-09 to 2026-10-23 | 14 days14Static fireStatic fireFlightFlightS24 to S25 | Flight | 2023-04-20 to 2023-11-18 | 212 days212S28 to S29 | Flight | 2024-03-14 to 2024-06-06 | 84 days84S29 to S30 | Flight | 2024-06-06 to 2024-10-13 | 129 days129S30 to S31 | Flight | 2024-10-13 to 2024-11-19 | 37 days37S33 to S34 | Flight | 2025-01-16 to 2025-03-06 | 49 days49S34 to S35 | Flight | 2025-03-06 to 2025-05-27 | 82 days82S37 to S38 | Flight | 2025-08-26 to 2025-10-13 | 48 days48S38 to S39 | Flight | 2025-10-13 to 2026-05-22 | 221 days221S39 to S40 | Flight | 2026-05-22 to 2026-07-24 | 63 days63S40 to S41 | Flight | 2026-07-24 to 2026-09-28 | 66 days66 Boosters: newer serial in build orderBoostersB10B11B12B13B14B15B16B20B21B22B23B24Section workSection workB23 to B24 | Stacking / section work | 2026-09-08 to 2026-09-27 | 19 days19RolloutRolloutB21 to B22 | Rollout / test move | 2026-09-21 to 2026-09-08 | -13 days-13B22 to B23 | Rollout / test move | 2026-09-08 to 2026-10-12 | 34 days34Cryo / proofCryo / proofB22 to B23 | Cryo / proof test | 2026-09-09 to 2026-10-15 | 36 days36Static fireStatic fireFlightFlightB9 to B10 | Flight | 2023-11-18 to 2024-03-14 | 117 days117B10 to B11 | Flight | 2024-03-14 to 2024-06-06 | 84 days84B11 to B12 | Flight | 2024-06-06 to 2024-10-13 | 129 days129B12 to B13 | Flight | 2024-10-13 to 2024-11-19 | 37 days37B13 to B14 | Flight | 2024-11-19 to 2025-01-16 | 58 days58B14 to B15 | Flight | 2025-01-16 to 2025-03-06 | 49 days49B15 to B16 | Flight | 2025-03-06 to 2025-08-26 | 173 days173B19 to B20 | Flight | 2026-05-22 to 2026-07-24 | 63 days63B20 to B21 | Flight | 2026-07-24 to 2026-09-28 | 66 days66B21 to B22 | Flight | 2026-09-28 to 2026-10-25 | 27 days27
Days between first dated claims, not elapsed time between real events. Filled circles mean both claims are CONFIRMED; hollow circles mean at least one is UNCONFIRMED. Dashed lines mark zero. Day scales are shared within each kind. Circles link newer claims; day labels link older claims.

S44 to S45, Stacking / section work: 38 days between first dated claims (2026-09-01 to 2026-10-09). Older claim; newer claim.

S43 to S44, Stacking / section work: -38 days between first dated claims (2026-10-09 to 2026-09-01). Older claim; newer claim.

S42 to S43, Stacking / section work: -9 days between first dated claims (2026-10-18 to 2026-10-09). Older claim; newer claim.

S42 to S43, Rollout / test move: 13 days between first dated claims (2026-10-09 to 2026-10-22). Older claim; newer claim.

S42 to S43, Cryo / proof test: 14 days between first dated claims (2026-10-09 to 2026-10-23). Older claim; newer claim.

S41 to S42, Stacking / section work: 22 days between first dated claims (2026-09-26 to 2026-10-18). Older claim; newer claim.

S41 to S42, Rollout / test move: 17 days between first dated claims (2026-09-22 to 2026-10-09). Older claim; newer claim.

S40 to S41, Rollout / test move: -46 days between first dated claims (2026-11-07 to 2026-09-22). Older claim; newer claim.

S40 to S41, Flight: 66 days between first dated claims (2026-07-24 to 2026-09-28). Older claim; newer claim.

S39 to S40, Flight: 63 days between first dated claims (2026-05-22 to 2026-07-24). Older claim; newer claim.

S38 to S39, Flight: 221 days between first dated claims (2025-10-13 to 2026-05-22). Older claim; newer claim.

S37 to S38, Flight: 48 days between first dated claims (2025-08-26 to 2025-10-13). Older claim; newer claim.

S34 to S35, Flight: 82 days between first dated claims (2025-03-06 to 2025-05-27). Older claim; newer claim.

S33 to S34, Flight: 49 days between first dated claims (2025-01-16 to 2025-03-06). Older claim; newer claim.

S30 to S31, Flight: 37 days between first dated claims (2024-10-13 to 2024-11-19). Older claim; newer claim.

S29 to S30, Flight: 129 days between first dated claims (2024-06-06 to 2024-10-13). Older claim; newer claim.

S28 to S29, Flight: 84 days between first dated claims (2024-03-14 to 2024-06-06). Older claim; newer claim.

S24 to S25, Flight: 212 days between first dated claims (2023-04-20 to 2023-11-18). Older claim; newer claim.

B23 to B24, Stacking / section work: 19 days between first dated claims (2026-09-08 to 2026-09-27). Older claim; newer claim.

B22 to B23, Rollout / test move: 34 days between first dated claims (2026-09-08 to 2026-10-12). Older claim; newer claim.

B22 to B23, Cryo / proof test: 36 days between first dated claims (2026-09-09 to 2026-10-15). Older claim; newer claim.

B21 to B22, Rollout / test move: -13 days between first dated claims (2026-09-21 to 2026-09-08). Older claim; newer claim.

B21 to B22, Flight: 27 days between first dated claims (2026-09-28 to 2026-10-25). Older claim; newer claim.

B20 to B21, Flight: 66 days between first dated claims (2026-07-24 to 2026-09-28). Older claim; newer claim.

B19 to B20, Flight: 63 days between first dated claims (2026-05-22 to 2026-07-24). Older claim; newer claim.

B15 to B16, Flight: 173 days between first dated claims (2025-03-06 to 2025-08-26). Older claim; newer claim.

B14 to B15, Flight: 49 days between first dated claims (2025-01-16 to 2025-03-06). Older claim; newer claim.

B13 to B14, Flight: 58 days between first dated claims (2024-11-19 to 2025-01-16). Older claim; newer claim.

B12 to B13, Flight: 37 days between first dated claims (2024-10-13 to 2024-11-19). Older claim; newer claim.

B11 to B12, Flight: 129 days between first dated claims (2024-06-06 to 2024-10-13). Older claim; newer claim.

B10 to B11, Flight: 84 days between first dated claims (2024-03-14 to 2024-06-06). Older claim; newer claim.

B9 to B10, Flight: 117 days between first dated claims (2023-11-18 to 2024-03-14). Older claim; newer claim.

Milestone claim table

DateVehicleKindConfidenceClaim summary
2026-11-15S42Rollout / test moveUNCONFIRMEDBlobifie says Ship 42 was safed and its transport stand moved to the launch site, and later (04:22 UTC) that S42 was still hanging from the chopsticks attached to the SQD, with a beacon set up in the rocket garden where it will be displayed.
2026-11-14B22FlightUNCONFIRMEDBlobifie 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.
2026-11-10S45Stacking / section workCONFIRMEDShip 45 was sleeved over its transfer tubes in Mega Bay 2 and the jig removed, then the final Ship section arrived. VickiCocks15 describes the sequence; lewisknaggs42 says the nose cone rollout to the aft section took 19 days, credited to LabPadre.
2026-11-09B22Rollout / test moveCONFIRMEDBooster 22 left the production site and arrived at the Pad 2 launch site on the evening of 9 Nov (Texas time), for Flight 15. Trackers posted it as T-93 hours.
2026-11-07S40Rollout / test moveCONFIRMEDShip 40 was lifted onto a transport stand in Mega Bay 2, rolled out of Mega Bay 2 and moved into a Gigabay work cell, the first vehicle to enter the Gigabay. The TrackingTheSB weekly says it went around Sanchez and the parking garage to the front of the Gigabay, with visible rust and damage to both flaps.
2026-10-31B24Stacking / section workUNCONFIRMEDVickiCocks15 says the LOX landing tank jig was removed from MB-1 again, which she reads as Booster 24 now being fully stacked inside the bay.
2026-10-31S45FlightUNCONFIRMEDVickiCocks15 says the Ship 45 common dome section was moved from Starfactory into Mega Bay 2 and was seen being lifted off its stand for integration with the ship.
2026-10-30B24Stacking / section workUNCONFIRMEDVickiCocks15 reports the LOX landing tank jig, moved into position the day before, was moved back inside Mega Bay 1 this morning for Booster 24 stacking ops.
2026-10-29B24Stacking / section workUNCONFIRMEDVickiCocks15 reports the booster LOX landing tank install jig was brought back towards Mega Bay 1, and reads it as crews being about ready to stack the two halves of Booster 24; the jig supports the tank during stacking.
2026-10-27S42Static fireUNCONFIRMEDVickiCocks15 says Ship 42 lit only one engine in its static fire, so another static fire test may still come.
2026-10-27S42Static fireCONFIRMEDShip 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.
2026-10-26S42Rollout / test moveCONFIRMEDShip 42 rolled from the production site down Highway 4 to Massey's for static fire testing, followed by a ship aft barrel section with some tiles on it.
2026-10-26S42Static fireCONFIRMEDShip 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.
2026-10-26S43Rollout / test moveCONFIRMEDShip 43 departed the production site and arrived at Pad 2 for chopstick testing.
2026-10-25B22Static fireCONFIRMEDBooster 22 completed a static fire test on Pad 2 at Starbase. Blobifie reports the burn lasted more than 15 seconds.
2026-10-25B22FlightCONFIRMEDBooster 22 was lifted off the Pad 2 launch mount to catch height at the top of the tower, then set on the booster transport ring for its trip back to Mega Bay 1 for final flight preparations.
2026-10-25B22Static fireCONFIRMEDSpaceX called the Booster 22 static fire for Flight 15 a full duration 33-engine static fire.
2026-10-25S42Static fireUNCONFIRMEDVickiCocks15 expects Ship 44 to move to the centre stand and Ship 43 and Ship 42 to swap places at Massey's in the night transport move, for an S42 static fire test.
2026-10-25S44Stacking / section workUNCONFIRMEDTrackingTheSB weekly: Ship 44's AX:4 section completes its major body assembly, barring aft flap install.
2026-10-24B22Rollout / test moveCONFIRMEDBooster 22 was lifted onto a transport stand, left Mega Bay 1, drove Highway 4 and arrived at the launch site (Pad 2) on the morning of 24 Oct ahead of its static fire campaign.
2026-10-24B22Rollout / test moveCONFIRMEDBooster 22 was lifted onto the Pad 2 orbital launch mount and lowered onto it on the afternoon of 24 Oct.
2026-10-23S43Cryo / proof testCONFIRMEDShip 43 started its first cryogenic proof test at Massey's on the evening of 23 Oct.
2026-10-23S43Cryo / proof testUNCONFIRMEDBlobifie says Ship 43 completed two cryogenic proof tests at Massey's on 23 Oct.
2026-10-23S44Stacking / section workUNCONFIRMEDShip 44's raceways have been staged ahead of install.
2026-10-23S45Stacking / section workCONFIRMEDShip 45's forward section moved into Mega Bay 2 and was sleeved over the Pez Dispenser mechanism, having moved out of Starfactory the previous evening.
2026-10-22B24Stacking / section workUNCONFIRMEDTrackingTheSB weekly: Booster 24 received its forward section this week, F2:4 on 20 Oct, HS-FX:3 on 22 Oct and F3:4 on 24 Oct.
2026-10-22S43Rollout / test moveCONFIRMEDShip 43 was lifted onto the ship cryo stand, rolled out of Mega Bay 2 and set off along Highway 4 to Massey's for cryogenic proof testing.
2026-10-22S44Stacking / section workUNCONFIRMEDWith the Mega Bay 2 centre stand vacated by Ship 43, raceways and the left aft flap were staged in place ahead of Ship 44 taking the spot.
2026-10-22S44Stacking / section workUNCONFIRMEDA crane in the Mega Bay 2 doorway was staging the right side aft flap ahead of Ship 44's move to the centre work stand.
2026-10-20S44Stacking / section workCONFIRMEDShip 44's AX:4 aft section, its final section, moved from Starfactory into Mega Bay 2 for stacking.
2026-10-18B23Cryo / proof testUNCONFIRMEDNSF (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.
2026-10-18B23Cryo / proof testCONFIRMEDTrackingTheSB weekly: Booster 23 completed only one cryogenic proof test at Massey's before rolling back to the production site. Every previous booster apart from BN3 in 2021 did at least two; the cause of the early end is not known.
2026-10-18B24Stacking / section workCONFIRMEDTrackingTheSB weekly: in Mega Bay 1, Booster 24 received its final aft section (AX:2) and its landing tank, completing the lower half of the booster that makes up the LOX tank. CH4 tank stacking and mating the two halves come next.
2026-10-18S42Stacking / section workCONFIRMEDTrackingTheSB 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.
2026-10-18S44Stacking / section workUNCONFIRMEDShip 44, now fitted with its transfer tubes, was lifted clear of the transfer tube jig and moved to a work stand inside Mega Bay 2, and the jig went back to Starfactory.
2026-10-17S44Stacking / section workUNCONFIRMEDS44 has gained its transfer tubes.
2026-10-17S44Stacking / section workUNCONFIRMEDS44, with decals applied and transfer tubes installed or being installed, sits front and centre in Mega Bay 2 awaiting a lift to a work stand for further work.
2026-10-16B24Stacking / section workUNCONFIRMEDSeen on a flyover: Booster 24 was getting its LOX landing tank installed, with Booster 22 behind it. The post does not name the building.
2026-10-15B23Cryo / proof testCONFIRMEDBooster 23 underwent its first cryogenic proof test at Massey's.
2026-10-13B23Rollout / test moveCONFIRMEDBooster 23 rolled from the production site to Massey's for its initial cryo proof testing.
2026-10-12B23Rollout / test moveCONFIRMEDBooster 23 lifted onto the booster cryo / thrust sim stand.
2026-10-09S42Cryo / proof testCONFIRMEDShip 42 frosted on both tanks during cryo testing.
2026-10-09S42Rollout / test moveUNCONFIRMEDReported 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-09S42Rollout / test moveCONFIRMEDShip 42 rolled to Massey's on the ship cryo stand after all 6 engines were removed.
2026-10-09S43Stacking / section workUNCONFIRMEDShip 43 is inside Mega Bay 2 finishing internals and is still missing its starboard-side aft flap. NSF says it was fully stacked on 15 Sep 2026.
2026-10-09S45Stacking / section workUNCONFIRMEDIdentify Ship 45. NSF reports its nose cone is stacked on its payload bay at Starfactory.
2026-10-09S45Stacking / section workUNCONFIRMEDNSF reports Ship 45 nose cone stacked on its payload bay at Starfactory, waiting for Ship 44 to finish stacking before S45 leaves the Starfactory turntable.
2026-10-08B24Stacking / section workCONFIRMEDBooster 24 full transfer tube rolled into Mega Bay 1.
2026-10-07B24Stacking / section workCONFIRMEDBooster 24 methane landing tank and lower transfer tube rolled from Starfactory to Mega Bay 1.
2026-10-07B24Stacking / section workCONFIRMEDBooster 24 A6:4 rolled from Starfactory to Mega Bay 1.
2026-10-05S44Stacking / section workCONFIRMEDShip 44 A2:4 rolled into Mega Bay 2.
2026-10-02B24Stacking / section workCONFIRMEDBooster 24 A5:4 rolled from Starfactory to Mega Bay 1. Initially misidentified as A6.
2026-09-28B21FlightCONFIRMEDIdentify Booster 21 as the Super Heavy booster that flew Starship Flight 14.
2026-09-28B21FlightCONFIRMEDOn Flight 14, Booster 21 lost one Raptor on ascent, completed its flight, and splashed down in the Gulf rather than being caught.
2026-09-28S41FlightCONFIRMEDIdentify Ship 41 as the Starship upper stage that flew Starship Flight 14.
2026-09-28S41FlightCONFIRMEDFlight 14 was the first orbital Starship flight and the first to deliver payload to orbit: 26 Starlink V3 satellites. Ship 41 entered orbit, deployed the satellites, deorbited, and splashed down in the Pacific Ocean.
2026-09-27B24Stacking / section workCONFIRMEDReported 27 Sep 2026: Booster 24 began construction in the week of 21 Sep, with its A2:4 section rolling into Mega Bay 1.
2026-09-27S44Stacking / section workCONFIRMEDReported 27 Sep 2026: Ship 44 began main body assembly in the week of 21 Sep, with the N:3 and FX:4 rolling into Mega Bay 2.
2026-09-26S41Stacking / section workUNCONFIRMEDFlight 14 pad flow: Ship 41 was restacked on Booster 21.
2026-09-25B23Stacking / section workCONFIRMEDBooster 23 CH4 tank stack was stacked on top of its aft section, completing major construction; outfitting comes next, ahead of cryo proof.
2026-09-22S41Rollout / test moveUNCONFIRMEDFlight 14 pad flow: Ship 41, the first orbital ship, followed Booster 21 to the pad a day later. The post does not name the pad.
2026-09-21B21Rollout / test moveUNCONFIRMEDFlight 14 pad flow: Booster 21 rolled to the pad and was stacked the same day. The post does not name the pad.
2026-09-21B23Stacking / section workCONFIRMEDBooster 23 received its F3:4 section, completing the liquid methane tank section. The post does not name the bay.
2026-09-20B23Stacking / section workCONFIRMEDReported 20 Sep 2026: Booster 23 received its integrated hot stage ring and forward dome section, the second step in stacking its CH4 tank after F2.
2026-09-11B22Cryo / proof testUNCONFIRMEDBlobifie says Booster 22 completed what looked to have been a partial cryo test at Massey's and was then detanked.
2026-09-09B22Cryo / proof testCONFIRMEDBooster 22 completed a full cryo test at Massey's, filled and held at pressure before detanking, from the afternoon into the night of 9 Sep.
2026-09-09B23Stacking / section workCONFIRMEDBooster 23 F2:4 section rolled into Mega Bay 1, the start of its CH4 tank.
2026-09-08B22Rollout / test moveUNCONFIRMEDBooster 22 rolled from Mega Bay 1 to the Massey's test site and was lifted onto the cryo stand for cryo proof testing.
2026-09-08B23Stacking / section workCONFIRMEDBooster 23 AX:2 section rolled across from Starfactory into Mega Bay 1, before its landing tank had been seen.
2026-09-01S44Stacking / section workCONFIRMEDReported by 1 Sep 2026: Ship 44 nosecone TPS work complete, forward flaps installed, and the nosecone stacked onto the payload bay in Starfactory.
2026-07-24B20FlightUNCONFIRMEDIdentify Booster 20 as the Super Heavy booster that flew Starship Flight 13, the second flight of a Block 3 booster.
2026-07-24B20FlightUNCONFIRMEDOn 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.
2026-07-24S40FlightUNCONFIRMEDOn 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.
2026-05-22B19FlightUNCONFIRMEDOn 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.
2026-05-22B19FlightUNCONFIRMEDIdentify Booster 19 as the Super Heavy booster that flew Starship Flight 12, the first flight of a Block 3 booster.
2026-05-22S39FlightUNCONFIRMEDIdentify Ship 39 as the Starship upper stage that flew Starship Flight 12, the first flight of a Block 3 ship.
2026-05-22S39FlightUNCONFIRMEDOn 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.
2025-10-13B15FlightUNCONFIRMEDOn 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-10-13S38FlightUNCONFIRMEDOn 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.
2025-10-13S38FlightUNCONFIRMEDIdentify Ship 38 as the Starship upper stage that flew Starship Flight 11.
2025-08-26B16FlightUNCONFIRMEDIdentify Booster 16 as the Super Heavy booster that flew Starship Flight 10.
2025-08-26B16FlightUNCONFIRMEDOn 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.
2025-08-26S37FlightUNCONFIRMEDIdentify Ship 37 as the Starship upper stage that flew Starship Flight 10.
2025-08-26S37FlightUNCONFIRMEDOn 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.
2025-08-15S36Static fireCONFIRMEDIdentify Ship 36. SpaceX names the Ship 36 static fire anomaly in its Flight 9 and Ship 36 investigation summary.
2025-05-27B14FlightUNCONFIRMEDOn 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-05-27S35FlightUNCONFIRMEDOn 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.
2025-05-27S35FlightUNCONFIRMEDIdentify Ship 35 as the Starship upper stage that flew Starship Flight 9.
2025-03-06B15FlightUNCONFIRMEDOn 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.
2025-03-06B15FlightUNCONFIRMEDIdentify Booster 15 as the Super Heavy booster that flew Starship Flight 8 with Ship 34.
2025-03-06S34FlightUNCONFIRMEDOn 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.
2025-03-06S34FlightUNCONFIRMEDIdentify Ship 34 as the Starship upper stage that flew Starship Flight 8 with Booster 15.
2025-01-16B14FlightUNCONFIRMEDOn 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.
2025-01-16B14FlightUNCONFIRMEDIdentify Booster 14 as the Super Heavy booster that flew Starship Flight 7. NASASpaceflight describes it as a Block 1 booster.
2025-01-16S33FlightUNCONFIRMEDIdentify Ship 33 as the Starship upper stage that flew Starship Flight 7. NASASpaceflight describes it as the first Block 2 ship to fly.
2025-01-16S33FlightUNCONFIRMEDOn 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.
2024-11-19B13FlightUNCONFIRMEDOn Flight 6, an automated health check of hardware on the launch and catch tower aborted the catch attempt for Booster 13. The booster diverted and made a landing burn and soft splashdown in the Gulf of Mexico.
2024-11-19B13FlightUNCONFIRMEDIdentify Booster 13 as the Super Heavy booster that flew Starship Flight 6.
2024-11-19S31FlightUNCONFIRMEDOn 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.
2024-11-19S31FlightUNCONFIRMEDIdentify Ship 31 as the Starship upper stage that flew Starship Flight 6.
2024-10-13B12FlightUNCONFIRMEDIdentify Booster 12 as the Super Heavy booster that flew Starship Flight 5.
2024-10-13B12FlightUNCONFIRMEDOn Flight 5, Booster 12 returned to the launch site after boostback and was caught by the chopstick arms of the launch and catch tower at Starbase, the first Super Heavy catch.
2024-10-13S30FlightUNCONFIRMEDIdentify Ship 30 as the Starship upper stage that flew Starship Flight 5.
2024-10-13S30FlightUNCONFIRMEDOn Flight 5, Ship 30 completed a controlled reentry, a flip, a landing burn, and a splashdown in the Indian Ocean. The flight ended 1 hour, 5 minutes and 40 seconds after launch. NASASpaceflight reports a soft splashdown, then an explosion after the ship tipped over.
2024-06-06B11FlightUNCONFIRMEDOn 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.
2024-06-06B11FlightUNCONFIRMEDIdentify Booster 11 as the Super Heavy booster that flew Starship Flight 4.
2024-06-06S29FlightUNCONFIRMEDOn 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.
2024-06-06S29FlightUNCONFIRMEDIdentify Ship 29 as the Starship upper stage that flew Starship Flight 4.
2024-03-14B10FlightUNCONFIRMEDIdentify Booster 10 as the Super Heavy booster that flew Starship Flight 3.
2024-03-14B10FlightUNCONFIRMEDOn 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.
2024-03-14S28FlightUNCONFIRMEDOn 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.
2024-03-14S28FlightUNCONFIRMEDIdentify Ship 28 as the Starship upper stage that flew Starship Flight 3.
2023-11-18B9FlightUNCONFIRMEDIdentify Booster 9 as the Super Heavy booster that flew Starship Flight 2.
2023-11-18B9FlightUNCONFIRMEDOn 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.
2023-11-18S25FlightUNCONFIRMEDOn 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.
2023-11-18S25FlightUNCONFIRMEDIdentify Ship 25 as the Starship upper stage that flew Starship Flight 2.
2023-04-20B7FlightUNCONFIRMEDOn 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.
2023-04-20B7FlightUNCONFIRMEDIdentify Booster 7 as the Super Heavy booster that flew Starship Flight 1.
2023-04-20S24FlightUNCONFIRMEDOn Flight 1, Ship 24 did not separate from the booster. The flight termination system was commanded on the ship after the stack tumbled. The flight reached an apogee of about 39 km.
2023-04-20S24FlightUNCONFIRMEDIdentify Ship 24 as the Starship upper stage that flew Starship Flight 1.