Next flight
Flight 15 readiness
No outcome claim yet.
The next flight whose NET is on or after 2026-11-03. Vehicles, test steps, the launch pad, ground notes, filings and launch notices are ledger claims. A test step uses the same words as /tests/. A launch notice closes only when a filing, a notice or an official post states that step. Open means that step is not in the ledger. An open box is not a date and not a prediction. A dated box means the ledger recorded that step, not that it passed, and the steps are a reading guide, not a required launch sequence. A dashed box with a date is a mention, not a structured test record.
NET 2026-11-12 at Starbase Pad 2 UNCONFIRMED c-f99b81d052de
| Step | Status | Date | Claim |
|---|---|---|---|
| booster B22 | assigned | 2026-10-25 | c-880a8ed89b9c |
| ship S42 | assigned | 2026-10-28 | c-13766e95320e |
| B22 cryo | test | 2026-09-09 | c-97e41ed079ec |
| B22 proof | mention | 2026-09-12 | c-27f4f91731a7 |
| B22 static fire | test | 2026-10-25 | c-7497db7affd7 |
| B22 spin prime | open | open | not in the ledger |
| B22 wet dress | open | open | not in the ledger |
| B22 thrust sim | open | open | not in the ledger |
| B22 burst | open | open | not in the ledger |
| S42 cryo | test | 2026-10-09 | c-099be62ead13 |
| S42 proof | mention | 2026-10-09 | c-9b6ec52e1fb0 UNCONFIRMED |
| S42 static fire | test | 2026-10-27 | c-73b91bdc20fc |
| S42 spin prime | open | open | not in the ledger |
| S42 wet dress | open | open | not in the ledger |
| S42 thrust sim | open | open | not in the ledger |
| S42 burst | open | open | not in the ledger |
| S42 other | test | 2026-09-12 | c-3c911339ea58 |
| S42 other | test | 2026-09-10 | c-5e1953d56a83 |
| Starbase Pad 2 | pad | 2026-10-29 | c-f99b81d052de UNCONFIRMED |
| deluge | note | 2026-10-22 | c-26bf5a57aaaf UNCONFIRMED |
| chopsticks | note | 2026-10-27 | c-3a07c5d16bc0 |
| BQD | note | 2026-10-24 | c-eab5f4451ac8 UNCONFIRMED |
| SQD | note | 2026-10-27 | c-3a07c5d16bc0 |
| FAA Notice | filing | 2026-10-29 | c-c8b519508708 UNCONFIRMED |
| FCC Experimental licence | filing | 2026-08-25 | c-58242193ce26 UNCONFIRMED |
| NOTAM, launch area | open | open | not in the ledger |
| NOTAM, ship splashdown | open | open | not in the ledger |
| USCG notice to mariners | open | open | not in the ledger |
| NGA navigational warning | open | open | not in the ledger |
| FAA operations advisory | filing | 2026-10-29 | c-c8b519508708 UNCONFIRMED |
| launch road closure | open | open | not in the ledger |
| wet dress rehearsal | open | open | not in the ledger |
| payload loaded | open | open | not in the ledger |
Vehicles
2026-10-25 booster B22 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
2026-10-28 ship S42 assign S42 as ship on F15
Assign Ship 42 as the ship on Flight 15. SpaceX called Ship 42 the Starship preparing for Flight 15.
@SpaceX X post Confirms alone
B22 test steps
B22, booster. Test log. A TEST is a test effect. A MENTION is a claim whose own text names a test word and is not a test effect. Same grouping as /tests/.
2026-10-26 MENTION B22 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
2026-10-25 MENTION B22 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
2026-10-25 MENTION B22 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
2026-10-25 MENTION B22 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
2026-10-25 MENTION B22 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
2026-10-25 TEST static-fire B22 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
2026-10-25 MENTION B22 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
2026-10-24 MENTION B22 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
2026-10-23 MENTION B22 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
2026-10-19 MENTION B22 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
2026-10-16 MENTION B22 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
2026-10-09 MENTION B22 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
2026-09-12 MENTION B22 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
2026-09-11 MENTION B22 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
2026-09-09 TEST cryo B22 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
2026-09-08 MENTION B22 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
S42 test steps
S42, ship. Test log. A TEST is a test effect. A MENTION is a claim whose own text names a test word and is not a test effect. Same grouping as /tests/.
2026-10-29 MENTION S42 transport S42 from MAS to MB2
Ship 42 left Massey's on Highway 4 late on 28 Oct (local time) after completing its static fire testing campaign, arrived back at the production site early on 29 Oct, was moved into Mega Bay 2 and lifted off its stand.
@TrackingTheSB X post Confirms alone @VickiCocks15 X post Counts with a second source @LabPadre X post Counts with a second source @RGVaerialphotos X post Counts with a second source
2026-10-28 MENTION S42 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.
@SpaceX X post Confirms alone @FelixSchlang X post Counts with a second source
2026-10-28 MENTION S42 UNCONFIRMED note at MAS about S42
VickiCocks15 says it looks like Ship 42 will be coming back to Mega Bay 2 on the night of 28 Oct (local time), after its static fire testing at Massey's.
@VickiCocks15 X post Counts with a second source
2026-10-27 TEST static-fire S42 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.
@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 MENTION S42 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 TEST static-fire S42 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.
@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 MENTION S42 UNCONFIRMED note at MAS about S42
Ship 42 was detanked after its single-engine static fire at Massey's.
@Blobifie X post Counts with a second source
2026-10-26 MENTION S42 transport S42 to MAS
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.
@Blobifie X post Counts with a second source @VickiCocks15 X post Counts with a second source @RGVaerialphotos X post Counts with a second source @FelixSchlang X post Counts with a second source
2026-10-25 MENTION S42 note at MB2 about S42
Ship 42 was lifted onto the ship static fire stand and left Mega Bay 2 to take Ship 43's place at Massey's for its static fire.
@Blobifie X post Counts with a second source @NASASpaceflight X post Counts with a second source @CeaserG33 X post Counts with a second source
2026-10-25 MENTION S42 note at MB2 about S42
The ship static fire test stand was moved into Mega Bay 2 for Ship 42, and a road closure was posted for Ship 43's return from Massey's and Ship 42's trip there.
@Blobifie X post Counts with a second source @VickiCocks15 X post Counts with a second source
2026-10-25 MENTION S42 UNCONFIRMED note at MAS about S42
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.
@VickiCocks15 X post Counts with a second source
2026-10-18 MENTION S42 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.
@TrackingTheSB X post Confirms alone
2026-10-09 TEST cryo S42 cryo S42 at MAS
Ship 42 frosted on both tanks during cryo testing.
@TrackingTheSB X post Confirms alone
2026-10-09 MENTION S42 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.
NASASpaceflight Web page Counts with a second source
2026-10-09 MENTION S42 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
2026-09-12 TEST other S42 other S42 at P2
Ship catch rehearsal at Pad 2: S42 was lifted to catch height and back down to SQD height, the SQD rotated in and connected, then S42 was rotated, flaps tucked, and lowered onto its transport stand.
@TrackingTheSB X post Confirms alone
2026-09-10 TEST other S42 other S42 at P2
Ship catch rehearsal at Pad 2: S42 was placed deep in the chopsticks and lifted a few meters, then the chopstick pushers moved it to the stabilizer engagement position and the stabilizers were engaged.
@TrackingTheSB X post Confirms alone
Pad
2026-10-29 UNCONFIRMED Flight 15 F15 NET 2026-11-12 at P2
Flight 15 (Booster 22 and Ship 42) moved 4 days to NET 12 Nov 2026 per CADENA and a new FAA planning slide, which earlier listed 8 Nov. The FAA slide is a planning date, not a SpaceX date, and no Flight 15 launch licence is public yet.
@LabPadre X post Counts with a second source @FelixSchlang X post Counts with a second source @lewisknaggs42 X post Counts with a second source @NASASpaceflight X post Counts with a second source @StarshipGazer X post Counts with a second source
Ground notes
Notes at Starbase Pad 2 whose own text names deluge, chopsticks, BQD or SQD. Newest first. A kind with no note stays open on the strip.
2026-10-27 note at P2 about S43
Ship 43 was lifted by the Pad 2 chopsticks with the landing rails deployed and moved back and forth, checking the rails and push rods after the previous night's SQD interface tests; Blobifie says this post-catch pusher test went much smoother than with Ship 42.
@VickiCocks15 X post Counts with a second source @Blobifie X post Counts with a second source @FelixSchlang X post Counts with a second source
2026-10-27 UNCONFIRMED note at P2 about S43
Blobifie says Ship 43 was moved to the middle of the Pad 2 chopsticks and lifted, a test simulating moving the ship forward after a catch so the stabilizer arms can engage.
@Blobifie X post Counts with a second source
2026-10-26 note at P2 about S43
At Pad 2 the chopsticks lifted Ship 43 above its transport stand and up to the top of the tower, then lowered it to the height of the ship quick disconnect (SQD) arm, which connected to it: practice for post-catch safing operations.
@Blobifie X post Counts with a second source @Blobifie X post Counts with a second source @NASASpaceflight X post Counts with a second source @FelixSchlang X post Counts with a second source @RGVaerialphotos X post Counts with a second source @VickiCocks15 X post Counts with a second source @Blobifie X post Counts with a second source
2026-10-26 UNCONFIRMED note at P2 about S43
Blobifie says Ship 43 went back onto its transport stand after the Pad 2 SQD connection test, and that the post-flight safing practice went much smoother than the same test with Ship 42.
@Blobifie X post Counts with a second source
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
2026-10-25 UNCONFIRMED note at P2
Ahead of the Booster 22 static fire, the Pad 2 chopsticks were opened and raised to launch position and the DSS was tested, as stated by VickiCocks15.
@VickiCocks15 X post Counts with a second source
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
2026-10-22 UNCONFIRMED note at P2
In the same Pad 2 test thread, the hold down clamps were tested with a few individual retract and extend moves and a simultaneous retract, then one visible clamp extended and retracted alone; the deluge was then tested without the top deck.
@VickiCocks15 X post Counts with a second source @VickiCocks15 X post Counts with a second source
2026-10-22 UNCONFIRMED note at P2
The booster quick disconnects (BQDs) at Pad 2 were tested with a few slow extend and retract moves, ending in a fast retract.
@VickiCocks15 X post Counts with a second source
2026-10-22 UNCONFIRMED note at P2
Pad 2 completed another launch and landing deluge test.
@Blobifie X post Counts with a second source
2026-10-21 note at P2
Pad 2 ran two water deluge tests about seven to eight minutes apart, one simulating a launch and one a catch, for the second day running. VickiCocks15 says the pressure looked higher than the day before.
@VickiCocks15 X post Counts with a second source @RoughRidersShow X post Counts with a second source @FelixSchlang X post Counts with a second source @RGVaerialphotos X post Counts with a second source
2026-10-21 UNCONFIRMED note at P2
Booster quick disconnects (BQDs) at Starbase Pad 2 purging, which the post hopes is ahead of Booster 22 arriving soon.
@NASASpaceflight X post Counts with a second source
2026-10-20 note at P2
Chopstick testing at the top of the Pad 2 tower, with the deluge system activated during it; Blobifie reports both a launch and a landing deluge test.
@VickiCocks15 X post Counts with a second source @VickiCocks15 X post Counts with a second source @Blobifie X post Counts with a second source @RoughRidersShow X post Counts with a second source
2026-10-18 UNCONFIRMED note at P2
TrackingTheSB weekly: late on 18 Oct the dancefloor service structure was removed from Pad 2 after post Flight 14 checkouts, then four full deluge tests including the top plate ran over 48 hours and the booster quick disconnects did a purge.
@TrackingTheSB X post Confirms alone
2026-10-16 UNCONFIRMED note at P2 about pad2-chopsticks
Further chopstick testing at Pad 2.
@VickiCocks15 X post Counts with a second source
2026-10-15 UNCONFIRMED note at P2 about pad2-chopsticks
Blobifie: SpaceX ran catch testing with the Pad 2 chopsticks at the top of the tower, and workers were seen celebrating at the top of the tower later in the day. NSF's Starbase summary of 15 Oct also shows the chopsticks run to the top of Tower 2 for high-speed tests.
@Blobifie X post Counts with a second source @NASASpaceflight X post Counts with a second source @VickiCocks15 X post Counts with a second source
2026-10-14 UNCONFIRMED note at P2
After damper work on 14 Oct (local), the Pad 2 chopsticks were raised and lowered a few times with checks in one pause; no arm swings were seen. The Deadline balcony at the base of Tower 2 received extra cladding the same day.
@VickiCocks15 X post Counts with a second source @VickiCocks15 X post Counts with a second source
2026-09-12 note at P2 about pad2-sqd
Pad 2 SQD arm rotated in and connected to S42 at SQD height during catch rehearsal, a rehearsal of post-catch ship safing.
@TrackingTheSB X post Confirms alone
2026-09-10 note at P2 about pad2-chopsticks
Pad 2 chopsticks held S42 deep in the arms and lifted it a few meters during catch rehearsal.
@TrackingTheSB X post Confirms alone
2026-09-10 note at P2
Pad 2 OLM ran a further deluge test.
@TrackingTheSB X post Confirms alone
2026-09-08 note at P2
Pad 2 OLM ran a full launch-to-catch deluge operation.
@TrackingTheSB X post Confirms alone
Filings
Filing claims whose effect names F15. Docket.
2026-10-29 FAA notice UNCONFIRMED filing FAA notice on F15
FAA ATO Space Operations (AJR-1800) slide in the CADENA Operations Planning Web Conference deck for Thursday, 29 Oct 2026, 1400 UTC, under Upcoming High-Profile Missions, lists SpX Starship FLT-15 on NOV 12. The same slide lists SpX Starship Starlink 30-1 on DEC 10 and Blue Origin New Glenn 4.1 on DEC 28.
CADENA Web page Counts with a second source
2026-08-25 FCC experimental UNCONFIRMED filing FCC experimental 1679-EX-ST-2026 on F15
FCC Experimental Licensing System filing 1679-EX-ST-2026 (call sign WA8XLZ), a Special Temporary Authority application from SpaceX filed 25 Aug 2026 for Starship Flight 15 vehicle communications launching from Starbase TX: a sub-orbital first stage booster and an orbital second stage, plus an additional power level for the 2056/2062 MHz uplink frequencies for static beam and tracking beam use. Requested operation 28 Sep 2026 to 28 Mar 2027. The record shows status Set Aside dated 10 Sep 2026 and lists a grant e-mail notification of 10 Sep 2026.
FCC.report Web page Counts with a second source
Launch notices
NOTAM launch area, NOTAM ship splashdown, USCG notice to mariners, NGA navigational warning, FAA operations advisory, launch road closure, wet dress rehearsal and payload loaded. Each stays open until a filing, a notice or an official post states it. A tracker mention does not close one. The same filing can also sit in the docket above.