Nerdy, sourced Starship tracking at every site

Claimstrip

06:14 CST at Starbase

booster UNCONFIRMED

B22 Booster 22

Body at Starbase Pad 2

UNCONFIRMED candidate body at Massey's test site c-17980b3cada0

Test static-fire at P2 on 2026-10-25.

Flights: F15 booster c-880a8ed89b9c.

Fleet pipeline

B22
Booster 22 build stagesB22 First section: no claim yetFirst sectionno claim yetB22 First stack: no claim yetFirst stackno claim yetB22 Cryo or proof: 2026-09-09 c-97e41ed079ec confirmedCryo or proof2026-09-09c-97e41ed079ecB22 Engines installed: no claim yetEngines installedno claim yetB22 Static fire: 2026-10-25 c-7497db7affd7 confirmedStatic fire2026-10-25c-7497db7affd7B22 Rollout to a pad: 2026-10-24 c-1ebcf26864d3 confirmedRollout to a pad2026-10-24c-1ebcf26864d3B22 Launch: no claim yetLaunchno claim yet

Build strip 3 Oct to 16 Nov, 29 marks. Hover or tap a mark for its claim.

Booster 22 (B22), 3 Oct to 16 NovMB1P2MB1P25 Oct12 Oct19 Oct26 Oct2 Nov9 Nov16 Nov2026-10-09 assign: Assign Booster 22 as the booster on Flight 15. NSF says Flight 15 is currently set to use S42 and B22. UNCONFIRMED2026-10-09 note at MB1: Booster 22 is still in Mega Bay 1 as of the 9 Oct NSF report, pending static fire readiness. UNCONFIRMED2026-10-16 note: Seen on a flyover: Booster 22 was waiting to roll out for pre-flight static fire testing. UNCONFIRMED2026-10-19 note: The OLM work platform has been removed from the OLM ahead of Booster 22's static fire campaign. The post does not name the pad. UNCONFIRMED2026-10-23 note: NSF says Booster 22 heads to Pad 2 overnight for a potential weekend static fire test, under a Production to Pad road delay from 23:59 to 04:00 CDT. UNCONFIRMED2026-10-23 note: The City of Starbase moved the Production to Pad road delay to Saturday 24 Oct, 02:00 to 06:00 CT (it was Friday 23:59 to Saturday 04:00 CT). UNCONFIRMED2026-10-24 move at P2: 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 note at P2: With cranes down, Booster 22 on the mount, BQDs engaged and blast doors closed, VickiCocks15 says Pad 2 looks locked up ahead of testing planned for 25 Oct. UNCONFIRMED2026-10-24 note at P2: Booster 22 was lifted onto the Pad 2 orbital launch mount and lowered onto it on the afternoon of 24 Oct.2026-10-25 note at P2: The booster transport stand left the Pad 2 launch site ahead of the Booster 22 static fire; VickiCocks15 says it was moved to gate D1 for safety.2026-10-25 test at P2: Booster 22 completed a static fire test on Pad 2 at Starbase. Blobifie reports the burn lasted more than 15 seconds.2026-10-25 assign: Assign Booster 22 as the booster on Flight 15. SpaceX called the Booster 22 static fire a static fire for Flight 15.2026-10-25 note at P2: Booster 22 was detanked after its static fire on Pad 2. UNCONFIRMED2026-10-25 note at P2: SpaceX called the Booster 22 static fire for Flight 15 a full duration 33-engine static fire.2026-10-25 note at P2: After the static fire, the Pad 2 chopsticks descended and closed in around Booster 22, as stated by VickiCocks15. UNCONFIRMED2026-10-25 note at P2: 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-10-26 move at MB1: Booster 22 was moved from Pad 2 back to Mega Bay 1 overnight after its static fire.2026-11-09 note: VickiCocks15 says the booster transport ring was delivered to Mega Bay 1 ahead of Booster 22 moving to the pad before launch, and that the road delay was pushed back to 20:00 local time on 9 Nov. UNCONFIRMED2026-11-09 note at MB1: VickiCocks15 says the Booster Transport Ring was delivered to Mega Bay 1 ahead of Booster 22 moving to the pad for launch, and that the booster lifting jig was moved into Mega Bay 1 on 8 Nov. UNCONFIRMED2026-11-09 move at P2: 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-10 note at P2: Booster 22 was lifted to the top of the Pad 2 tower, moved around on the chopsticks using the pusher system, and lowered onto the orbital launch mount. VickiCocks15 later described it as settled on the mount with the clamps lined up.2026-11-11 note at P2: The Pad 2 chopsticks released Booster 22 and descended the tower and the SQD arm was reset. Workers then spent several hours around B22's catch pins and grid fins, the booster transport stand returned to the build site, the SQD was retracted and the chopsticks went back to the booster support position.2026-11-11 note at P2: VickiCocks15 says the Pad 2 chopsticks released Booster 22 again on 11 Nov and returned to the side of the launch mount, with the crew lift that had worked on the grid fins moved away, then later the chopsticks moved back up the tower and hugged Booster 22 once more. She also says one of the chopstick sims was put back in the Super Crusher cage, suggesting testing of 43.1 is not finished. UNCONFIRMED2026-11-13 note: SpaceX says Super Heavy diverted to an offshore splashdown in the Gulf on Flight 15 instead of the planned catch; LabPadre logged the booster divert at T+00:06:35 and NASASpaceflight carried SpaceX's Dan Huot saying Booster 22 automatically aborted the return to Pad 2 due to a GNC issue.2026-11-14 note: TrackingTheSB says the remains of Booster 22 seem to have gone fully under the water during the night, citing NASASpaceflight imagery. UNCONFIRMED2026-11-14 note: LabPadre says Kate confirmed Booster 22's boostback burn ended early on a low fuel mass alarm, and the booster then autonomously judged itself out of position for a catch and diverted. UNCONFIRMED2026-11-14 note: 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.2026-11-14 note: 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. UNCONFIRMED2026-11-14 note: 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.

Confirmed place by day

  1. MB1 3 Oct to 23 Oct
  2. P2 24 Oct to 25 Oct
  3. MB1 26 Oct to 8 Nov
  4. P2 9 Nov to 16 Nov

History

Status: Splashdown on F15. All vehicles

Flights

  1. F15 as booster (assign c-880a8ed89b9c): Splashdown (outcome c-e55f1fc168e7)

Milestones

  1. 2026-10-25 Static fire SpaceX posts a full-duration 33-engine static fire of the Super Heavy booster preparing for Flight 15. The post names F15, not the serial; B22 comes from the F15 assign claim. @SpaceX official
Booster 22 B22UNCONFIRMED

Body

  1. 2026-09-12 from masseys to mb1 claim
  2. 2026-10-24 from mb1 to pad2 claim
  3. 2026-10-26 from pad2 to mb1 claim
  4. 2026-11-09 from mb1 to pad2 claim

Sections

No section claims.

Tape

  1. 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

  2. 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

  3. 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

  4. 2026-11-14 UNCONFIRMED note about B22

    LabPadre says Kate confirmed Booster 22's boostback burn ended early on a low fuel mass alarm, and the booster then autonomously judged itself out of position for a catch and diverted.

    @LabPadre X post Counts with a second source

  5. 2026-11-14 UNCONFIRMED note about B22

    TrackingTheSB says the remains of Booster 22 seem to have gone fully under the water during the night, citing NASASpaceflight imagery.

    @TrackingTheSB X post Confirms alone

  6. 2026-11-13 note about B22

    SpaceX says Super Heavy diverted to an offshore splashdown in the Gulf on Flight 15 instead of the planned catch; LabPadre logged the booster divert at T+00:06:35 and NASASpaceflight carried SpaceX's Dan Huot saying Booster 22 automatically aborted the return to Pad 2 due to a GNC issue.

    @SpaceX X post Confirms alone @NASASpaceflight X post Counts with a second source @LabPadre X post Counts with a second source

  7. 2026-11-11 UNCONFIRMED note at P2 about B22

    VickiCocks15 says the Pad 2 chopsticks released Booster 22 again on 11 Nov and returned to the side of the launch mount, with the crew lift that had worked on the grid fins moved away, then later the chopsticks moved back up the tower and hugged Booster 22 once more. She also says one of the chopstick sims was put back in the Super Crusher cage, suggesting testing of 43.1 is not finished.

    @VickiCocks15 X post Counts with a second source @VickiCocks15 X post Counts with a second source @VickiCocks15 X post Counts with a second source

  8. 2026-11-11 note at P2 about B22

    The Pad 2 chopsticks released Booster 22 and descended the tower and the SQD arm was reset. Workers then spent several hours around B22's catch pins and grid fins, the booster transport stand returned to the build site, the SQD was retracted and the chopsticks went back to the booster support position.

    @VickiCocks15 X post Counts with a second source @VickiCocks15 X post Counts with a second source @Blobifie X post Counts with a second source @Blobifie X post Counts with a second source

  9. 2026-11-10 note at P2 about B22

    Booster 22 was lifted to the top of the Pad 2 tower, moved around on the chopsticks using the pusher system, and lowered onto the orbital launch mount. VickiCocks15 later described it as settled on the mount with the clamps lined up.

    @RGVaerialphotos X post Counts with a second source @LabPadre X post Counts with a second source @TrackingTheSB X post Confirms alone @Blobifie X post Counts with a second source @VickiCocks15 X post Counts with a second source

  10. 2026-11-09 UNCONFIRMED note at MB1 about B22

    VickiCocks15 says the Booster Transport Ring was delivered to Mega Bay 1 ahead of Booster 22 moving to the pad for launch, and that the booster lifting jig was moved into Mega Bay 1 on 8 Nov.

    @VickiCocks15 X post Counts with a second source @VickiCocks15 X post Counts with a second source

  11. 2026-11-09 UNCONFIRMED note about B22

    VickiCocks15 says the booster transport ring was delivered to Mega Bay 1 ahead of Booster 22 moving to the pad before launch, and that the road delay was pushed back to 20:00 local time on 9 Nov.

    @VickiCocks15 X post Counts with a second source

  12. 2026-11-09 transport B22 from MB1 to P2

    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.

    @LabPadre X post Counts with a second source @TrackingTheSB X post Confirms alone @RGVaerialphotos X post Counts with a second source @StarshipGazer X post Counts with a second source

  13. 2026-10-26 transport B22 from P2 to MB1

    Booster 22 was moved from Pad 2 back to Mega Bay 1 overnight after its static fire.

    @VickiCocks15 X post Counts with a second source @Blobifie X post Counts with a second source

  14. 2026-10-25 note at P2 about B22

    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.

    @RGVaerialphotos X post Counts with a second source @Blobifie X post Counts with a second source @NASASpaceflight X post Counts with a second source

  15. 2026-10-25 UNCONFIRMED note at P2 about B22

    After the static fire, the Pad 2 chopsticks descended and closed in around Booster 22, as stated by VickiCocks15.

    @VickiCocks15 X post Counts with a second source

  16. 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.

    @SpaceX X post Confirms alone @NASASpaceflight X post Counts with a second source

  17. 2026-10-25 UNCONFIRMED note at P2 about B22

    Booster 22 was detanked after its static fire on Pad 2.

    @Blobifie X post Counts with a second source

  18. 2026-10-25 note at P2 about B22

    The booster transport stand left the Pad 2 launch site ahead of the Booster 22 static fire; VickiCocks15 says it was moved to gate D1 for safety.

    @Blobifie X post Counts with a second source @LabPadre X post Counts with a second source @NASASpaceflight X post Counts with a second source @VickiCocks15 X post Counts with a second source

  19. 2026-10-25 assign B22 as booster on F15

    Assign Booster 22 as the booster on Flight 15. SpaceX called the Booster 22 static fire a static fire for Flight 15.

    @SpaceX X post Confirms alone

  20. 2026-10-25 static-fire B22 at P2

    Booster 22 completed a static fire test on Pad 2 at Starbase. Blobifie reports the burn lasted more than 15 seconds.

    @NASASpaceflight X post Counts with a second source @LabPadre X post Counts with a second source @Blobifie X post Counts with a second source @FelixSchlang X post Counts with a second source @VickiCocks15 X post Counts with a second source @SpaceX X post Confirms alone

  21. 2026-10-24 note at P2 about B22

    Booster 22 was lifted onto the Pad 2 orbital launch mount and lowered onto it on the afternoon of 24 Oct.

    @NASASpaceflight X post Counts with a second source @Blobifie X post Counts with a second source @Blobifie X post Counts with a second source @LabPadre X post Counts with a second source

  22. 2026-10-24 UNCONFIRMED note at P2 about B22

    With cranes down, Booster 22 on the mount, BQDs engaged and blast doors closed, VickiCocks15 says Pad 2 looks locked up ahead of testing planned for 25 Oct.

    @VickiCocks15 X post Counts with a second source

  23. 2026-10-24 transport B22 from MB1 to P2

    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.

    @Blobifie X post Counts with a second source @NASASpaceflight X post Counts with a second source @NASASpaceflight X post Counts with a second source @Blobifie X post Counts with a second source @VickiCocks15 X post Counts with a second source @FelixSchlang X post Counts with a second source

  24. 2026-10-23 UNCONFIRMED note about B22

    The City of Starbase moved the Production to Pad road delay to Saturday 24 Oct, 02:00 to 06:00 CT (it was Friday 23:59 to Saturday 04:00 CT).

    @FelixSchlang X post Counts with a second source @VickiCocks15 X post Counts with a second source

  25. 2026-10-23 UNCONFIRMED note about B22

    NSF says Booster 22 heads to Pad 2 overnight for a potential weekend static fire test, under a Production to Pad road delay from 23:59 to 04:00 CDT.

    @NASASpaceflight X post Counts with a second source @lewisknaggs42 X post Counts with a second source @VickiCocks15 X post Counts with a second source

  26. 2026-10-19 UNCONFIRMED note about B22

    The OLM work platform has been removed from the OLM ahead of Booster 22's static fire campaign. The post does not name the pad.

    @Blobifie X post Counts with a second source

  27. 2026-10-16 UNCONFIRMED note about B22

    Seen on a flyover: Booster 22 was waiting to roll out for pre-flight static fire testing.

    @RGVaerialphotos X post Counts with a second source

  28. 2026-10-09 UNCONFIRMED note at MB1 about B22

    Booster 22 is still in Mega Bay 1 as of the 9 Oct NSF report, pending static fire readiness.

    NASASpaceflight Web page Counts with a second source

  29. 2026-10-09 UNCONFIRMED assign B22 as booster on F15

    Assign Booster 22 as the booster on Flight 15. NSF says Flight 15 is currently set to use S42 and B22.

    NASASpaceflight Web page Counts with a second source

  30. 2026-10-09 UNCONFIRMED identify vehicle Booster 22

    Identify Booster 22 as the Super Heavy NSF names for Starship Flight 15.

    NASASpaceflight Web page Counts with a second source

  31. 2026-09-12 transport B22 from MAS to MB1

    Booster 22 finished cryo proof testing at Massey's and was moved back to Mega Bay 1 at the production site.

    @TrackingTheSB X post Confirms alone @VickiCocks15 X post Counts with a second source

  32. 2026-09-11 UNCONFIRMED note at MAS about B22

    Blobifie says Booster 22 completed what looked to have been a partial cryo test at Massey's and was then detanked.

    @Blobifie X post Counts with a second source

  33. 2026-09-09 cryo B22 at MAS

    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.

    @Blobifie X post Counts with a second source @LabPadre X post Counts with a second source @VickiCocks15 X post Counts with a second source

  34. 2026-09-08 UNCONFIRMED transport B22 from MB1 to MAS

    Booster 22 rolled from Mega Bay 1 to the Massey's test site and was lifted onto the cryo stand for cryo proof testing.

    @Blobifie X post Counts with a second source @Blobifie X post Counts with a second source