Skip to content
StarshipDesk.

Field Journal / sourced daily

Explore
Feed (Atom)

FIELD JOURNAL / F15

Flight 15

The mission dossier: target, assigned hardware, milestones and sources.

Recorded target
NET 13 Nov 2026 confirmed
Assigned hardware
B22 confirmed · S42 confirmed

FROM THE PHOTOGRAPHIC ARCHIVE

Starship beside its steel launch tower at sunset.
The tower at sunsetArchive · 15 Apr 2023 · Starship Test Flight Mission · SpaceX · CC BY-NC 2.0. Resized; display crop may apply.

Historical programme image. Open F15 source gallery →

All flights

Flight 15

  1. 2026-11-14 confirmed c-e55f1fc168e7

    Booster
    splashdown
    Ship
    caught
    Booster catch
    no
    Ship catch
    yes
    Orbit
    yes
    Payload
    starlink

    Flight 15 result: Ship 42 reached orbit with a Starlink V3 payload and was caught by the Pad 2 chopsticks at Starbase, the first ship catch; Booster 22 diverted to an offshore Gulf splashdown instead of a catch.

    @SpaceX X post Confirms alone @SpaceX X post Confirms alone

Flight history

All boosters and ships

Liftoff
2026-11-13 22:48 UTC, UK 13 Nov 2026, 22:48 GMT. Stated as 22:48 UTC (time of the SpaceX Liftoff post). @SpaceX official
Pad
Starbase Pad 2 (from the schedule claim c-638524a443e2)
Booster
B22 (assign claim c-880a8ed89b9c)
Ship
S42 (assign claim c-13766e95320e)
Raptors
33 on the booster, 6 on the ship. SpaceX official
  1. Done Booster ascent Super Heavy ascended from Pad 2 on 33 Raptor engines; SpaceX calls the first-stage ascent successful. SpaceX official
  2. Done Hot staging Hot-staging, then Starship continued on six Raptor engines. SpaceX official
  3. Partial Boostback 32 of the 33 planned engines relit for the boostback burn, which ended early due to low fuel mass; SpaceX says the root cause is under investigation. SpaceX official
  4. Partial Booster landing The booster GNC triggered an automated abort during coast and diverted to an offshore landing location. The landing burn ran with the engines cutting off while hovering over the Gulf, and the flight termination system was triggered at shutdown. No catch. SpaceX official
  5. Done Ship ascent burn Starship completed a nominal ascent burn. SpaceX official
  6. Done Orbit insertion After a brief coast a single Raptor relit for the orbital insertion burn and Starship reached orbit. SpaceX official
  7. Done Payload or door 26 Starlink V3 satellites deployed; SpaceX made contact with every one. SpaceX official
  8. Done In-space relight After more than 20 hours in orbit a single sea-level Raptor relit for the deorbit burn. SpaceX official
  9. Done Ship reentry Starship reentered and flew a final swoosh maneuver out over the Gulf back toward the launch site. SpaceX official
  10. Done Ship landing Three Raptors ignited for the landing flip, then Starship slowed into the Pad 2 chopsticks, which closed to catch it for the first time, 22.5 hours after launch. SpaceX official

No source read for: Propellant transfer demo. Blank means not sourced here, not that it did not happen.

FAA

No FAA mishap or licence statement cited for this flight.

NET 2026-11-13 at Starbase Pad 2

Revisions

  1. 2026-11-07 NET 2026-11-13 at Starbase Pad 2

Assignment

  1. 2026-11-14 outcome F15 booster splashdown (no), ship caught (yes), orbit yes, payload starlink

    Flight 15 result: Ship 42 reached orbit with a Starlink V3 payload and was caught by the Pad 2 chopsticks at Starbase, the first ship catch; Booster 22 diverted to an offshore Gulf splashdown instead of a catch.

    @SpaceX X post Confirms alone @SpaceX X post Confirms alone

  2. 2026-11-12 UNCONFIRMED filing FAA notam on F15

    LabPadre lists new NOTAMs ahead of Flight 15 on 12 and 13 Nov, including 11/144 and 11/145 for Starbase, TX on 14 Nov 16:45 to 18:40 CST, 11/164 for Starbase, TX on 15 Nov 16:45 to 18:40 CST and Oakland Oceanic FIR notices for 15 Nov, and says one batch covers potential re-entry locations and catch of Starship 42.

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

  3. 2026-11-09 filing FAA notice on F15

    FAA operations advisory (ATCSCC ADVZY 064 DCC, Operations Plan, 9 Nov 2026) lists SpaceX Starship FLT-15 from Starbase, primary 13 Nov 2245Z to 0040Z and backup 14 Nov 2245Z to 0040Z, and FLT-15 reentry, primary 14 Nov 2056Z to 0014Z and backup 15 Nov 2056Z to 0014Z.

    FAA Web page Confirms alone @VickiCocks15 X post Counts with a second source @lewisknaggs42 X post Counts with a second source

  4. 2026-11-07 F15 NET 2026-11-13 at P2

    SpaceX says Flight 15 is preparing to launch as soon as Friday 13 Nov 2026, pending regulatory approval, from Starbase. NSF says SpaceX tested the launch site systems ahead of rolling both vehicles to Pad 2.

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

  5. 2026-11-05 UNCONFIRMED Flight 15 F15 NET 2026-11-13 at P2

    Flight 15 moved one day to NET 13 Nov 2026 per the Nov 5 CADENA FAA planning slide (was 12 Nov). LabPadre, FelixSchlang and lewisknaggs42 all cite the slide; LabPadre notes these are tentative planning dates, not NOTAMs. 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

  6. 2026-10-29 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

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

  8. 2026-10-28 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

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

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

  11. 2026-10-09 UNCONFIRMED assign S42 as ship on F15

    Assign Ship 42 as the ship on Flight 15. NSF says Flight 15 is currently set to use S42 and B22.

    NASASpaceflight Web page Counts with a second source

  12. 2026-10-08 UNCONFIRMED Flight 15 F15 NET 2026-11-08 at P2

    CADENA advisory: Flight 15 from Starbase Pad 2 NET 8 Nov 2026; Flight 16 (Starlink 30-1), potentially LC-39A, NET 10 Dec 2026.

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

  13. 2026-08-25 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

Pad flow

Claims about B22 and S42 from L-30 days to the NET day (L-0, 2026-11-13). One plate per claim, stacked when several share a day. Dashed plates are unconfirmed. Hover or tap a plate for the claim.

L-30L-25L-20L-15L-10L-5L-0L-28 2026-10-16: Seen on a flyover: Booster 22 was waiting to roll out for pre-flight static fire testing.B22L-26 2026-10-18: 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.S42L-25 2026-10-19: 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.B22L-21 2026-10-23: 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.B22L-21 2026-10-23: 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).B22L-20 2026-10-24: 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.B22L-20 2026-10-24: Booster 22 was lifted onto the Pad 2 orbital launch mount and lowered onto it on the afternoon of 24 Oct.B22L-20 2026-10-24: LewisKnaggs42 says Ship 42 could go to Massey's on the night of 24 Oct if Ship 43 returns; FelixSchlang later reports the City of Starbase took down the Production to Massey's road delay for Sat 24 Oct 23:59 to Sun 04:00 CT.S42L-19 2026-10-25: 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.B22L-19 2026-10-25: Booster 22 completed a static fire test on Pad 2 at Starbase. Blobifie reports the burn lasted more than 15 seconds.B22L-19 2026-10-25: Booster 22 was detanked after its static fire on Pad 2.B22L-19 2026-10-25: 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.S42L-19 2026-10-25: SpaceX called the Booster 22 static fire for Flight 15 a full duration 33-engine static fire.B22L-19 2026-10-25: 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.S42L-19 2026-10-25: After the static fire, the Pad 2 chopsticks descended and closed in around Booster 22, as stated by VickiCocks15.B22L-19 2026-10-25: 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.S42L-19 2026-10-25: 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.B22L-19 2026-10-25: TrackingTheSB weekly: SpaceX said on 23 Oct that an upgraded Raptor 3 debuts on Flight 15, which is why Ship 42's engines were removed and swapped.S42L-18 2026-10-26: Ship 42 was detanked after its single-engine static fire at Massey's.S42L-18 2026-10-26: 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.S42L-17 2026-10-27: VickiCocks15 says Ship 42 lit only one engine in its static fire, so another static fire test may still come.S42L-17 2026-10-27: 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.S42L-16 2026-10-28: 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.S42L-16 2026-10-28: 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.S42L-16 2026-10-28: VickiCocks15 says Ship 42's flaps were retracted on the morning of 28 Oct, and that afternoon the ship left the test station and moved a short way towards the Massey's exit to wait for the trip back to Mega Bay 2.S42L-15 2026-10-29: Elon Musk wrote that Starship 42 will be the first tower catch.S42L-4 2026-11-09: 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.B22L-4 2026-11-09: 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.B22L-3 2026-11-10: VickiCocks15 says a Ship lift jig was raised and translated across to the right-hand side of Mega Bay 2, theoretically for Ship 42. She notes ships have previously been moved onto a STR for payload bay satellite loading.S42L-3 2026-11-10: 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.B22L-2 2026-11-11: 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.B22L-2 2026-11-11: 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.B22L-1 2026-11-12: Ship 42 was driven to the Starbase launch site on 12 Nov, lifted onto Booster 22 at Pad 2 and stacked for Flight 15. SpaceX posted that Ship 42 moves to the Starbase pad ahead of launch, and NASASpaceflight posted the Ship 42 lift.S42L-1 2026-11-12: Ship 42 was lifted onto a transport stand and left Mega Bay 2 on the evening of 11 Nov (Texas time) while the Starlink speed loader and loading box came over from the Starfactory to the ring yard; the loader was then lifted into Mega Bay 2, and on 12 Nov Ship 42 was moved back inside Mega Bay 2 to have its 26 Starlink V3 satellites installed.S42L-0 2026-11-13: SpaceX says Starship began deploying a payload of 26 Starlink V3 satellites on Flight 15, a sequence taking about 42 minutes.S42L-0 2026-11-13: TrackingTheSB says what looks to be alignment markers have been added to Ship 42, and that it is unclear whether they are for general operations or specific to post-catch operations.S42L-0 2026-11-13: SpaceX says Starship performed its orbital insertion burn with a single Raptor engine and entered an orbit of Earth (about 275 km planned), after the ascent burn left it on a planned suborbital trajectory.S42L-0 2026-11-13: 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.B22L-0 2026-11-13: VickiCocks15 says the SQD access platform was retracted, the SQD attached to Ship 42, and a fast retract and reattach test performed. TrackingTheSB also says the SQD was being connected to Ship 42.S42

Assigned vehicle notes

Claims that name B22 or S42, the vehicles assigned above.

  1. 2026-11-16 UNCONFIRMED note at MB2 about S42

    Blobifie says Ship 42 was moved into Mega Bay 2 via Sanchez, the first time a caught ship has returned to the build site and the second time a flown ship has been inside Mega Bay 2. TrackingTheSB says S42 rolled back to the production site early on 16 Nov.

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

    c-313341020e01

  2. 2026-11-15 note about S42

    Elon Musk says he went over the whole Starship heat shield and it looks great overall, the engines look great too, and Ship 42 could probably be reflown with a few weeks of refurbishment, but many small fixes are needed for airplane-like immediate reusability. LabPadre relayed the reflight line.

    @elonmusk X post Confirms alone @LabPadre X post Counts with a second source

    c-e05cd3af7489

  3. 2026-11-15 UNCONFIRMED note about S42

    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.

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

    c-bdc922fbd2f7

  4. 2026-11-15 UNCONFIRMED note about S42

    AshleyKillip says a band about 19 tiles wide on Ship 42, running from the bottom of the liquid oxygen tank up to the forward dome, has a distinct matte look where plasma appears to have ablated the layer that usually makes the tiles glossy.

    @AshleyKillip X post Counts with a second source

    c-a8839e007d3c

  5. 2026-11-15 note about S42

    Ship 42 was lowered onto its ship transport stand at Pad 2 after the Ship QD arm retracted and a flap was retracted, then rolled back to the production site, arriving around 23:15 UTC on 15 Nov (NASASpaceflight, RGV Aerial Photography, LabPadre).

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

    c-63a41295a22b

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

    c-f412e7e0cfed

  7. 2026-11-14 UNCONFIRMED note at P2 about S42

    LabPadre says the stabilizer pins engaged on Ship 42 as it lowered to connect the SQD, and later that the SQD attached to S42 and residual detanking began; Blobifie also says the SQD arm attached to allow detanking and safing.

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

    c-ed6998be1b80

  8. 2026-11-14 note about S42

    SpaceX says Ship 42 completed a good deorbit burn and was on course to reenter ahead of a planned catch at Starbase about an hour later.

    @SpaceX X post Confirms alone

    c-de461999103c

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

    c-b2697042cfc0

  10. 2026-11-14 UNCONFIRMED note about S42

    NASASpaceflight posted a Cybertruck procession with the Ship Transport Stand after the catch, and AshleyKillip says the stand was on the way to the launch site to collect S42.

    @NASASpaceflight X post Counts with a second source @AshleyKillip X post Counts with a second source

    c-88e69e285426

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

    c-83d97922fdf7

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

    c-34dd195abd35

  13. 2026-11-14 note about S42

    SpaceX says Starship and its heatshield are healthy in orbit and that a planned return to launch site catch at Starbase is about 22.5 hours after launch.

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

    c-2c617b6a88c5

  14. 2026-11-14 UNCONFIRMED note about S42

    LabPadre says Ship 42 deployed 26 V3 Starlink satellites by T+01:17:40 and closed its payload bay door.

    @LabPadre X post Counts with a second source

    c-0dc28e746487

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

    c-06303d04e62c

  16. 2026-11-13 UNCONFIRMED note at P2 about S42

    VickiCocks15 says the SQD access platform was retracted, the SQD attached to Ship 42, and a fast retract and reattach test performed. TrackingTheSB also says the SQD was being connected to Ship 42.

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

    c-e45478ef161b

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

    c-ad7379af8d81

  18. 2026-11-13 note about S42

    SpaceX says Starship performed its orbital insertion burn with a single Raptor engine and entered an orbit of Earth (about 275 km planned), after the ascent burn left it on a planned suborbital trajectory.

    @SpaceX X post Confirms alone @SpaceX X post Confirms alone

    c-a80c552639c5

  19. 2026-11-13 UNCONFIRMED note about S42

    TrackingTheSB says what looks to be alignment markers have been added to Ship 42, and that it is unclear whether they are for general operations or specific to post-catch operations.

    @TrackingTheSB X post Confirms alone

    c-96a8fef42cf2

  20. 2026-11-13 note about S42

    SpaceX says Starship began deploying a payload of 26 Starlink V3 satellites on Flight 15, a sequence taking about 42 minutes.

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

    c-8364b4f3a2fa

  21. 2026-11-12 note at MB2 about S42

    Ship 42 was lifted onto a transport stand and left Mega Bay 2 on the evening of 11 Nov (Texas time) while the Starlink speed loader and loading box came over from the Starfactory to the ring yard; the loader was then lifted into Mega Bay 2, and on 12 Nov Ship 42 was moved back inside Mega Bay 2 to have its 26 Starlink V3 satellites installed.

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

    c-cdc5e5060159

  22. 2026-11-12 note at P2 about S42

    Ship 42 was driven to the Starbase launch site on 12 Nov, lifted onto Booster 22 at Pad 2 and stacked for Flight 15. SpaceX posted that Ship 42 moves to the Starbase pad ahead of launch, and NASASpaceflight posted the Ship 42 lift.

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

    c-a66e8f14aa7d

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

    c-ae0cf69044a0

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

    c-0858d3b8b1aa

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

    c-b531e3eed92a

  26. 2026-11-10 UNCONFIRMED note at MB2 about S42

    VickiCocks15 says a Ship lift jig was raised and translated across to the right-hand side of Mega Bay 2, theoretically for Ship 42. She notes ships have previously been moved onto a STR for payload bay satellite loading.

    @VickiCocks15 X post Counts with a second source

    c-aa23ca14742e

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

    c-a54f571b4468

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

    c-31ab4319b994

  29. 2026-10-29 note about S42

    Elon Musk wrote that Starship 42 will be the first tower catch.

    @elonmusk X post Confirms alone

    c-5598e1f45452

  30. 2026-10-28 UNCONFIRMED note at MAS about S42

    VickiCocks15 says Ship 42's flaps were retracted on the morning of 28 Oct, and that afternoon the ship left the test station and moved a short way towards the Massey's exit to wait for the trip back to Mega Bay 2.

    @VickiCocks15 X post Counts with a second source

    c-de2439a3bda4

  31. 2026-10-28 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

    c-7fdf4861b7e6

  32. 2026-10-28 note at MAS about S42

    SpaceX said Ship 42's static fires are complete: the Starship preparing for Flight 15 performed a full-duration six-engine static fire and fired a single Raptor engine to simulate a deorbit burn.

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

    c-2082215ccf2e

  33. 2026-10-27 static-fire S42 at MAS

    Ship 42 completed a six-engine, full-duration static fire test at Massey's on 27 Oct (local time), about 60 seconds long, following its single-engine static fire the evening before.

    @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

    c-73b91bdc20fc

  34. 2026-10-27 UNCONFIRMED note about S42

    VickiCocks15 says Ship 42 lit only one engine in its static fire, so another static fire test may still come.

    @VickiCocks15 X post Counts with a second source

    c-6d7e71f3a577

  35. 2026-10-26 static-fire S42 at MAS

    Ship 42 completed a single-engine static fire test at Massey's on the evening of 26 Oct (local time), after a depress vent signalled a single-engine burn.

    @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

    c-974fb64c590a

  36. 2026-10-26 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

    c-45ef1080c51d

  37. 2026-10-25 UNCONFIRMED note about S42

    TrackingTheSB weekly: SpaceX said on 23 Oct that an upgraded Raptor 3 debuts on Flight 15, which is why Ship 42's engines were removed and swapped.

    @TrackingTheSB X post Confirms alone

    c-58fb6c06e71d

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

    c-74a0e6a4213e

  39. 2026-10-25 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

    c-345c570a6e79

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

    c-e02fc7cffe65

  41. 2026-10-25 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

    c-018d841e508a

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

    c-f3863dfdbddf

  43. 2026-10-25 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

    c-5e0917eade99

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

    c-e368e18c7435

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

    c-2ed4b5250957

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

    c-7497db7affd7

  47. 2026-10-24 UNCONFIRMED note about S42

    LewisKnaggs42 says Ship 42 could go to Massey's on the night of 24 Oct if Ship 43 returns; FelixSchlang later reports the City of Starbase took down the Production to Massey's road delay for Sat 24 Oct 23:59 to Sun 04:00 CT.

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

    c-2a0addcfb6f5

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

    c-27f38f636d95

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

    c-eab5f4451ac8

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

    c-cbea2e7de2a3

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

    c-177147c08e9c

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

    c-ae6d4bf7deb3

  53. 2026-10-18 note at MB2 about S42

    TrackingTheSB weekly: inside Mega Bay 2, Ship 42 has engines installed again ahead of its static fire campaign for Flight 15, after all of its engines were removed following Flight 14. The post says the reason for the removal is not known.

    @TrackingTheSB X post Confirms alone

    c-3ed97de7367e

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

    c-cd10d791cb45

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

    c-30ede1c7e807

  56. 2026-10-09 cryo S42 at MAS

    Ship 42 frosted on both tanks during cryo testing.

    @TrackingTheSB X post Confirms alone

    c-099be62ead13

  57. 2026-10-09 UNCONFIRMED note at MAS about S42

    Reported by 9 Oct: SpaceX removed all six engines from S42 and rolled it to Massey's for a third time, onto the ship cryo-proof stand. NSF says this work needs thrust ram testing, not just a cryo proof, before a static fire.

    NASASpaceflight Web page Counts with a second source

    c-9b6ec52e1fb0

  58. 2026-09-12 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

    c-3c911339ea58

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

    c-2d19b3126d8e

  60. 2026-09-10 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

    c-5e1953d56a83

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

    c-97e41ed079ec

Flight notes

Notes that name this flight. A note does not set a NET or an outcome.

  1. 2026-11-14 note about F15

    SpaceX says Starship is in a long coast phase and that teams intend to stay in orbit about 21 hours, with a few early deorbit options available if needed.

    @SpaceX X post Confirms alone

    c-69845031e014

  2. 2026-11-13 note about F15

    SpaceX posted 'Liftoff of Starship!' at 22:48 UTC on 13 Nov for Flight 15 (Booster 22 and Ship 42 per LabPadre), the Flight 15 liftoff from Starbase.

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

    c-fb26417f4e19

  3. 2026-11-13 UNCONFIRMED note about F15

    Blobifie says the FAA has yet to issue SpaceX a licence for Flight 15 launch, 12 hours before the window.

    @Blobifie X post Counts with a second source

    c-b8a193ece22b

  4. 2026-11-09 UNCONFIRMED note about F15

    LabPadre reports a new NAVAREA IV marine hazard area for Starship Flight 15, 13 Nov 16:45 to 18:40 CST, linking the USCG NAVCEN chart.

    @LabPadre X post Counts with a second source

    c-9bdeb365571e

  5. 2026-11-07 note about F15

    SpaceX Flight 15 page: the booster's primary objective is launch, ascent, stage separation, boostback and return to the launch site for catch, the first catch attempt for a Super Heavy V3 booster. The ship's primary objectives are deploying 26 Starlink V3 satellites and the first return to launch site and catch at Starbase, after about 14 orbits at about 275 km over more than 22 hours. The ship returns only if the systems critical for reentry, landing burn and tower approach are healthy.

    SpaceX Web page Confirms alone

    c-f3c041b185f8

  6. 2026-11-07 note about F15

    SpaceX's Flight 15 page says Ship 42 is to deploy 26 Starlink V3 satellites, three of them carrying cameras to scan the heatshield, then orbit at about 275 km for about 14 orbits over more than 22 hours before returning to Starbase for the first ship catch. The page calls it the first flight planned to return both Starship and Super Heavy for catch.

    SpaceX Web page Confirms alone @TrackingTheSB X post Confirms alone

    c-e21c16d3b9a0

  7. 2026-11-07 UNCONFIRMED note about F15

    LabPadre reports NOTAM A0106/26 in the Mauritius FIR, 13 Nov 16:53 CST to 19 Nov 19:14 CST, which VickiCocks15 calls a NOTAM for Starship reentry.

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

    c-1f7ff748d3a6

  8. 2026-11-07 note about F15

    SpaceX Flight 15 page: the 75-minute launch window opens at 4:45 p.m. CT on Friday 13 Nov (17:45 to 19:00 ET), and the live webcast starts about 30 minutes before liftoff on spacex.com and on X @SpaceX, with coverage planned through ship catch.

    SpaceX Web page Confirms alone

    c-0e9343bc7e86

  9. 2026-11-06 note about F15

    SpaceX released the Go For Orbit episode, calling the upcoming launch the first orbital Starship launch carrying advanced Starlink satellites bound for space.

    @SpaceX X post Confirms alone

    c-19dc42ebd0e2

  10. 2026-11-06 note about F15

    Elon Musk says SpaceX will attempt to catch both the Super Heavy booster and Starship on the upcoming flight, and that if both succeed it will be the first time all parts of an orbital rocket return to Earth intact.

    @elonmusk X post Confirms alone

    c-59d05c620fbc

  11. 2026-10-25 UNCONFIRMED note about F15

    TrackingTheSB weekly: Flight 15 is No Earlier Than 8 Nov, and SpaceX will attempt to catch both Booster 22 and Ship 42 at Pad 2.

    @TrackingTheSB X post Confirms alone

    c-d1546295a4b2

  12. 2026-10-24 UNCONFIRMED note about F15

    FelixSchlang reports NASA's Parsons as saying Flight 15, expected to fly Booster 22, is probably in November.

    @FelixSchlang X post Counts with a second source

    c-5cd00c422ea3

  13. 2026-10-23 UNCONFIRMED note about F15

    NSF: SpaceX is working on dual flows for upcoming Starship missions, with Flight 15 set for mid-November from Pad 2.

    @NASASpaceflight X post Counts with a second source

    c-bce4ec33ed20

  14. 2026-10-20 UNCONFIRMED note about F15

    NSF on the empty pad at sunrise: it could be Ship 43 (Flight 16) first, for potential chopstick tests, then Booster 22 (Flight 15), and finally Ship 42, joining forces for a November launch.

    @NASASpaceflight X post Counts with a second source

    c-d7595cc354eb

  15. 2026-10-20 UNCONFIRMED note about F15

    On the SpaceX Q3 2026 results webcast, Elon Musk said Flight 15 will attempt to catch both the booster and the ship.

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

    c-b21f69100c11

  16. 2026-10-18 UNCONFIRMED note about F15

    NSF (18 Oct): Flight 15 is targeting November with the goal of catching both the booster and the ship. That projected cadence would result in five Starship launches in 2026, which NSF relates to the move from Block 2 to Block 3 vehicles.

    NASASpaceflight Web page Counts with a second source

    c-e1d72f0d437e

  17. 2026-10-10 UNCONFIRMED note about F15

    At the X Takeover on 10 Oct 2026, Elon Musk said four to six weeks is about right for Flight 15, that it probably launches a little bit before Thanksgiving, and that SpaceX will try to catch the ship for the first time. SpaceX has not announced a Flight 15 date.

    The Grid Fin Web page Counts with a second source

    c-3b3734de9a21

SOURCE GALLERY

F15 in pictures & reporting

All 46 linked sources ↗

Original posts linked to F15 claims. Load a post to see the publisher's photographs, video or text.