Skip to content
StarshipDesk.

Field Journal / sourced daily

Explore
OverviewFlight history
Feed (Atom)

FIELD JOURNAL / MISSION

The flight archive.

From launch to outcome: the complete recorded flight history and upcoming targets.

FROM THE PHOTOGRAPHIC ARCHIVE

SN15 rises from a cloud of exhaust during its high-altitude flight test.
SN15 in flightArchive · 5 May 2021 · Starship SN15 High-Altitude Flight Test · SpaceX · CC BY-NC 2.0. Resized; display crop may apply.

Outcomes

Flights flown, booster catches, ship catches and orbital flights are counted only from confirmed outcome claims that agree. A flight with no outcome claim stays unknown. An unconfirmed outcome is shown on that flight and is left out of these counts.

1 flight has no outcome claim yet.

Flights flown

  1. F1 2023-04-20 c-21a8f721726d
  2. F2 2023-11-18 c-8e434e32d29c
  3. F3 2024-03-14 c-a2cbe6903b99
  4. F4 2024-06-06 c-651ccb304c04
  5. F5 2024-10-13 c-6229581009e1
  6. F6 2024-11-19 c-efa04be0475a
  7. F7 2025-01-16 c-95aeff943b80
  8. F8 2025-03-06 c-6bebbd589de6
  9. F9 2025-05-27 c-537f7c0fc125
  10. F10 2025-08-26 c-a2ea477e7df7
  11. F11 2025-10-13 c-bdab56392720
  12. F12 2026-05-22 c-1c676c13e2cf
  13. F13 2026-07-24 c-5cc373e24117
  14. F14 2026-09-28 c-0a2b5043ee66
  15. F15 2026-11-14 c-e55f1fc168e7

Booster catches

  1. F5 2024-10-13 c-6229581009e1
  2. F7 2025-01-16 c-95aeff943b80
  3. F8 2025-03-06 c-6bebbd589de6

Ship catches

  1. F15 2026-11-14 c-e55f1fc168e7

Orbital flights

  1. F14 2026-09-28 c-0a2b5043ee66
  2. F15 2026-11-14 c-e55f1fc168e7

No outcome claim yet

Flight history

15 flown flights, 11 stages each. Every coloured cell is a stage result read from a SpaceX flight page or another cited page; the details and links are in each flight's Flight history block below. A blank cell means no source was read for that stage, not that it failed or did not happen.

Stage results for every flown Starship flightRows are flights F1 to F15. Columns are stages from booster ascent to ship landing. Green is done, amber partial, blue started, orange aborted, red failed, grey not attempted, outlined not sourced.Booster ascentHot stagingBoostbackBooster landingShip ascent burnOrbit insertionPayload or doorPropellant transfer demoIn-space relightShip reentryShip landingF1F1 Booster ascent: FailedF1 Hot staging: no source readF1 Boostback: no source readF1 Booster landing: no source readF1 Ship ascent burn: no source readF1 Orbit insertion: no source readF1 Payload or door: no source readF1 Propellant transfer demo: no source readF1 In-space relight: no source readF1 Ship reentry: no source readF1 Ship landing: no source readF2F2 Booster ascent: DoneF2 Hot staging: DoneF2 Boostback: FailedF2 Booster landing: no source readF2 Ship ascent burn: FailedF2 Orbit insertion: no source readF2 Payload or door: no source readF2 Propellant transfer demo: no source readF2 In-space relight: no source readF2 Ship reentry: no source readF2 Ship landing: no source readF3F3 Booster ascent: DoneF3 Hot staging: DoneF3 Boostback: StartedF3 Booster landing: FailedF3 Ship ascent burn: DoneF3 Orbit insertion: no source readF3 Payload or door: DoneF3 Propellant transfer demo: StartedF3 In-space relight: Not attemptedF3 Ship reentry: FailedF3 Ship landing: no source readF4F4 Booster ascent: DoneF4 Hot staging: DoneF4 Boostback: DoneF4 Booster landing: DoneF4 Ship ascent burn: DoneF4 Orbit insertion: no source readF4 Payload or door: no source readF4 Propellant transfer demo: no source readF4 In-space relight: no source readF4 Ship reentry: DoneF4 Ship landing: DoneF5F5 Booster ascent: no source readF5 Hot staging: DoneF5 Boostback: DoneF5 Booster landing: DoneF5 Ship ascent burn: DoneF5 Orbit insertion: no source readF5 Payload or door: no source readF5 Propellant transfer demo: no source readF5 In-space relight: no source readF5 Ship reentry: DoneF5 Ship landing: DoneF6F6 Booster ascent: DoneF6 Hot staging: DoneF6 Boostback: DoneF6 Booster landing: AbortedF6 Ship ascent burn: DoneF6 Orbit insertion: no source readF6 Payload or door: no source readF6 Propellant transfer demo: no source readF6 In-space relight: DoneF6 Ship reentry: DoneF6 Ship landing: DoneF7F7 Booster ascent: DoneF7 Hot staging: DoneF7 Boostback: PartialF7 Booster landing: DoneF7 Ship ascent burn: FailedF7 Orbit insertion: no source readF7 Payload or door: no source readF7 Propellant transfer demo: no source readF7 In-space relight: no source readF7 Ship reentry: no source readF7 Ship landing: no source readF8F8 Booster ascent: DoneF8 Hot staging: DoneF8 Boostback: PartialF8 Booster landing: DoneF8 Ship ascent burn: FailedF8 Orbit insertion: no source readF8 Payload or door: no source readF8 Propellant transfer demo: no source readF8 In-space relight: no source readF8 Ship reentry: no source readF8 Ship landing: no source readF9F9 Booster ascent: DoneF9 Hot staging: DoneF9 Boostback: DoneF9 Booster landing: FailedF9 Ship ascent burn: DoneF9 Orbit insertion: no source readF9 Payload or door: FailedF9 Propellant transfer demo: no source readF9 In-space relight: Not attemptedF9 Ship reentry: FailedF9 Ship landing: no source readF10F10 Booster ascent: DoneF10 Hot staging: DoneF10 Boostback: DoneF10 Booster landing: DoneF10 Ship ascent burn: DoneF10 Orbit insertion: no source readF10 Payload or door: DoneF10 Propellant transfer demo: no source readF10 In-space relight: DoneF10 Ship reentry: DoneF10 Ship landing: DoneF11F11 Booster ascent: DoneF11 Hot staging: DoneF11 Boostback: PartialF11 Booster landing: DoneF11 Ship ascent burn: DoneF11 Orbit insertion: no source readF11 Payload or door: DoneF11 Propellant transfer demo: no source readF11 In-space relight: DoneF11 Ship reentry: DoneF11 Ship landing: DoneF12F12 Booster ascent: PartialF12 Hot staging: DoneF12 Boostback: PartialF12 Booster landing: FailedF12 Ship ascent burn: PartialF12 Orbit insertion: no source readF12 Payload or door: DoneF12 Propellant transfer demo: no source readF12 In-space relight: no source readF12 Ship reentry: DoneF12 Ship landing: DoneF13F13 Booster ascent: DoneF13 Hot staging: DoneF13 Boostback: PartialF13 Booster landing: FailedF13 Ship ascent burn: DoneF13 Orbit insertion: no source readF13 Payload or door: DoneF13 Propellant transfer demo: no source readF13 In-space relight: DoneF13 Ship reentry: DoneF13 Ship landing: DoneF14F14 Booster ascent: PartialF14 Hot staging: DoneF14 Boostback: PartialF14 Booster landing: DoneF14 Ship ascent burn: PartialF14 Orbit insertion: DoneF14 Payload or door: DoneF14 Propellant transfer demo: no source readF14 In-space relight: DoneF14 Ship reentry: DoneF14 Ship landing: DoneF15F15 Booster ascent: DoneF15 Hot staging: DoneF15 Boostback: PartialF15 Booster landing: PartialF15 Ship ascent burn: DoneF15 Orbit insertion: DoneF15 Payload or door: DoneF15 Propellant transfer demo: no source readF15 In-space relight: DoneF15 Ship reentry: DoneF15 Ship landing: DoneDonePartialStartedAbortedFailedNot attemptedNot sourced
Drawn from ledger/history/flights.json. Hover or tap a cell for its stage; tap a row to jump to that flight.

Flights

16 flights in the ledger (F1 to F16). 15 have a confirmed SpaceX schedule and pad.

Flight 1

  1. 2023-04-20 confirmed c-21a8f721726d

    Booster
    terminated
    Ship
    terminated
    Booster catch
    no
    Ship catch
    no
    Orbit
    not stated
    Payload
    not stated

    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.

    SpaceX Web page Confirms alone

Flight history

All boosters and ships

Liftoff
2023-04-20 13:33 UTC, UK 20 Apr 2023, 14:33 BST. Stated as 8:33 a.m. CT. SpaceX official
Pad
Starbase Pad 1 (from the schedule claim c-79dfbb3a9457)
Booster
B7 UNCONFIRMED (assign claim c-6b910ee23334)
Ship
S24 UNCONFIRMED (assign claim c-b4b72a5c4cf5)
Raptors
No sourced engine count.
  1. Failed Booster ascent Lifted off from the orbital launch pad and climbed to an apogee of about 39 km over the Gulf of Mexico. The vehicle had multiple engines out, lost altitude and began to tumble. The flight termination system was commanded on both the booster and the ship. SpaceX official

No source read for: Hot staging, Boostback, Booster landing, Ship ascent burn, Orbit insertion, Payload or door, Propellant transfer demo, In-space relight, Ship reentry, Ship landing. Blank means not sourced here, not that it did not happen.

FAA

  1. 2023-09-08 Mishap investigation closed 63 corrective actions. The FAA closed the mishap investigation. The final report cites multiple root causes and 63 corrective actions, including hardware redesigns to prevent leaks and fires, a redesigned launch pad, and more analysis and testing of the Autonomous Flight Safety System. FAA official

NET 2023-04-20 at Starbase Pad 1

Revisions

  1. 2023-04-20 NET 2023-04-20 at Starbase Pad 1

Assignment

  • B7 booster UNCONFIRMED
  • S24 ship UNCONFIRMED
  1. 2023-04-20 outcome F1 booster terminated (no), ship terminated (no)

    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.

    SpaceX Web page Confirms alone

  2. 2023-04-20 UNCONFIRMED assign S24 as ship on F1

    Assign Ship 24 as the ship on Flight 1.

    NASASpaceflight Web page Counts with a second source NASASpaceflight Web page Counts with a second source

  3. 2023-04-20 UNCONFIRMED assign B7 as booster on F1

    Assign Booster 7 as the booster on Flight 1.

    NASASpaceflight Web page Counts with a second source NASASpaceflight Web page Counts with a second source

  4. 2023-04-20 Flight 1 F1 NET 2023-04-20 at P1

    Flight 1 lifted off from the orbital launch pad at Starbase, which the SpaceX launches list names Pad 1, on 20 Apr 2023 at 8:33 a.m. CT.

    SpaceX Web page Confirms alone SpaceX Web page Confirms alone

  5. 2023-04-20 identify flight Flight 1

    Identify Flight 1 as Starship's first integrated flight test.

    SpaceX Web page Confirms alone

Pad flow

Claims about B7 and S24 from L-30 days to the NET day (L-0, 2023-04-20). 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-0 2023-04-20: 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.B7L-0 2023-04-20: 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.S24

Assigned vehicle notes

Claims that name B7 or S24, the vehicles assigned above.

  1. 2023-04-20 UNCONFIRMED note about S24

    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.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-55b38fe77a4d

  2. 2023-04-20 UNCONFIRMED note about B7

    On Flight 1, Booster 7 had several Raptor engines fail after a fire in the engine section. The stack did not separate, lost altitude, and tumbled. The flight termination system was commanded on the booster.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-1183489a8f78

Flight 2

  1. 2023-11-18 confirmed c-8e434e32d29c

    Booster
    lost
    Ship
    terminated
    Booster catch
    no
    Ship catch
    no
    Orbit
    not stated
    Payload
    not stated

    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.

    SpaceX Web page Confirms alone

Flight history

All boosters and ships

Liftoff
2023-11-18 13:02 UTC, UK 18 Nov 2023, 13:02 GMT. Stated as 7:02 a.m. CT. SpaceX official
Pad
Starbase Pad 1 (from the schedule claim c-78db71b30a1e)
Booster
B9 UNCONFIRMED (assign claim c-574f9578fca6)
Ship
S25 UNCONFIRMED (assign claim c-72ff7aa51515)
Raptors
33 on the booster, 6 on the ship. SpaceX official
  1. Done Booster ascent All 33 Raptor engines started and, for the first time, completed a full-duration burn during ascent. SpaceX official
  2. Done Hot staging First successful hot-stage separation: all but three booster Raptors powered down and the six ship Raptors ignited before separation. SpaceX official
  3. Failed Boostback The booster completed its flip and began the boostback burn, then broke up more than three and a half minutes into the flight at about 90 km over the Gulf of Mexico. SpaceX official
  4. Failed Ship ascent burn All six ship Raptors started. The ship reached about 150 km and about 24,000 km/h, the first Starship in space, and nearly completed its burn. Telemetry was lost after more than eight minutes, before engine cutoff, and a command destruct was triggered. SpaceX official

No source read for: Booster landing, Orbit insertion, Payload or door, Propellant transfer demo, In-space relight, Ship reentry, Ship landing. Blank means not sourced here, not that it did not happen.

FAA

  1. 2024-02-26 Mishap investigation closed 17 corrective actions. The FAA closed the SpaceX-led mishap investigation and accepted 17 corrective actions: seven for the Super Heavy booster and ten for the Starship vehicle. SpacePolicyOnline other

NET 2023-11-18 at Starbase Pad 1

Revisions

  1. 2023-11-18 NET 2023-11-18 at Starbase Pad 1

Assignment

  • B9 booster UNCONFIRMED
  • S25 ship UNCONFIRMED
  1. 2023-11-18 outcome F2 booster lost (no), ship terminated (no)

    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.

    SpaceX Web page Confirms alone

  2. 2023-11-18 UNCONFIRMED assign S25 as ship on F2

    Assign Ship 25 as the ship on Flight 2.

    NASASpaceflight Web page Counts with a second source NASASpaceflight Web page Counts with a second source

  3. 2023-11-18 UNCONFIRMED assign B9 as booster on F2

    Assign Booster 9 as the booster on Flight 2.

    NASASpaceflight Web page Counts with a second source NASASpaceflight Web page Counts with a second source

  4. 2023-11-18 Flight 2 F2 NET 2023-11-18 at P1

    Flight 2 lifted off from Starbase Pad 1 on 18 Nov 2023 at 7:02 a.m. CT.

    SpaceX Web page Confirms alone SpaceX Web page Confirms alone

  5. 2023-11-18 identify flight Flight 2

    Identify Flight 2 as Starship's second flight test.

    SpaceX Web page Confirms alone

Pad flow

Claims about B9 and S25 from L-30 days to the NET day (L-0, 2023-11-18). 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-0 2023-11-18: 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.B9L-0 2023-11-18: 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.S25

Assigned vehicle notes

Claims that name B9 or S25, the vehicles assigned above.

  1. 2023-11-18 UNCONFIRMED note about S25

    On Flight 2, Ship 25 was the first Starship to reach outer space after a hot-staging separation. Telemetry was lost near the end of the second-stage burn, and a command destruct was triggered before engine cutoff.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-107235b4efa6

  2. 2023-11-18 UNCONFIRMED note about B9

    On Flight 2, Booster 9 started all 33 Raptors and completed a full-duration ascent burn. After hot-staging it began the boostback burn, then broke up more than three and a half minutes into the flight at about 90 km over the Gulf of Mexico.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-521addab083b

Flight 3

  1. 2024-03-14 confirmed c-a2cbe6903b99

    Booster
    lost
    Ship
    lost
    Booster catch
    no
    Ship catch
    no
    Orbit
    not stated
    Payload
    not stated

    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.

    SpaceX Web page Confirms alone

Flight history

All boosters and ships

Liftoff
2024-03-14 13:25 UTC, UK 14 Mar 2024, 13:25 GMT. Stated as 8:25 a.m. CT. SpaceX official
Pad
Starbase Pad 1 (from the schedule claim c-46e23605cf75)
Booster
B10 UNCONFIRMED (assign claim c-868bdc7e5b4a)
Ship
S28 UNCONFIRMED (assign claim c-3cdc6e921e7c)
Raptors
33 on the booster, 6 on the ship. SpaceX official
  1. Done Booster ascent For the second time all 33 booster Raptors started and completed a full-duration burn. SpaceX official
  2. Done Hot staging Second successful hot-stage separation. SpaceX official
  3. Started Boostback The booster completed its flip and initiated the boostback burn toward its splashdown point in the Gulf of Mexico. SpaceX official
  4. Failed Booster landing Several engines lit for the first ever landing burn, then the booster broke up (RUD) at about 462 m altitude, just under seven minutes into the mission. SpaceX official
  5. Done Ship ascent burn All six ship Raptors started and completed the first full-duration Starship ascent burn. SpaceX official
  6. Done Payload or door The payload door (the pez dispenser) opened and closed during coast. SpaceX official
  7. Started Propellant transfer demo A propellant transfer demonstration was initiated during coast. SpaceX official
  8. Not attempted In-space relight The planned in-space Raptor relight was not attempted because of vehicle roll rates during coast. SpaceX official
  9. Failed Ship reentry First ever entry from space. The last telemetry came via Starlink at about 49 minutes into the mission. SpaceX official

No source read for: Orbit insertion, Ship landing. Blank means not sourced here, not that it did not happen.

FAA

  1. 2024-03-14 Mishap investigation required. The FAA said the mishap involved both the Super Heavy booster and the Starship vehicle and that it would oversee the SpaceX-led investigation. FAA official
  2. 2024-05-28 Public safety determination. The FAA found no public safety issues in the OFT-3 anomaly (SpaceX notified on 24 May), so Starship could return to flight while the investigation stayed open. FAA official

NET 2024-03-14 at Starbase Pad 1

Revisions

  1. 2024-03-14 NET 2024-03-14 at Starbase Pad 1

Assignment

  • B10 booster UNCONFIRMED
  • S28 ship UNCONFIRMED
  1. 2024-03-14 outcome F3 booster lost (no), ship lost (no)

    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.

    SpaceX Web page Confirms alone

  2. 2024-03-14 UNCONFIRMED assign S28 as ship on F3

    Assign Ship 28 as the ship on Flight 3.

    NASASpaceflight Web page Counts with a second source NASASpaceflight Web page Counts with a second source

  3. 2024-03-14 UNCONFIRMED assign B10 as booster on F3

    Assign Booster 10 as the booster on Flight 3.

    NASASpaceflight Web page Counts with a second source NASASpaceflight Web page Counts with a second source

  4. 2024-03-14 Flight 3 F3 NET 2024-03-14 at P1

    Flight 3 lifted off from Starbase Pad 1 on 14 Mar 2024 at 8:25 a.m. CT.

    SpaceX Web page Confirms alone SpaceX Web page Confirms alone

  5. 2024-03-14 identify flight Flight 3

    Identify Flight 3 as Starship's third flight test.

    SpaceX Web page Confirms alone

Pad flow

Claims about B10 and S28 from L-30 days to the NET day (L-0, 2024-03-14). 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-0 2024-03-14: 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.B10L-0 2024-03-14: 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.S28

Assigned vehicle notes

Claims that name B10 or S28, the vehicles assigned above.

  1. 2024-03-14 UNCONFIRMED note about S28

    On Flight 3, Ship 28 completed a full-duration ascent burn, opened and closed its payload door, and started a propellant transfer demonstration. It did not attempt the planned Raptor relight because of roll rates during coast, then was lost during reentry. The last telemetry was about 49 minutes into the flight.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-a0c555d347ee

  2. 2024-03-14 UNCONFIRMED note about B10

    On Flight 3, Booster 10 flipped and initiated its boostback burn toward a splashdown point in the Gulf of Mexico (SpaceX says initiated, not completed), lit several engines for its first landing burn, and broke up just under seven minutes into the flight at about 462 meters altitude.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-e2c333773393

Flight 4

  1. 2024-06-06 confirmed c-651ccb304c04

    Booster
    splashdown
    Ship
    splashdown
    Booster catch
    no
    Ship catch
    no
    Orbit
    not stated
    Payload
    data

    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.

    SpaceX Web page Confirms alone

Flight history

All boosters and ships

Liftoff
2024-06-06 12:50 UTC, UK 6 Jun 2024, 13:50 BST. Stated as 7:50 a.m. CT. SpaceX official
Pad
Starbase Pad 1 (from the schedule claim c-c1d4f6e77437)
Booster
B11 UNCONFIRMED (assign claim c-8b148a2a34c1)
Ship
S29 UNCONFIRMED (assign claim c-82ae4ae622c0)
Raptors
No sourced engine count.
  1. Done Booster ascent The booster completed a full-duration ascent burn. SpaceX official
  2. Done Hot staging Hot-stage separation: all but three booster Raptors powered down and the six ship Raptors ignited. SpaceX official
  3. Done Boostback The booster completed its flip, its boostback burn toward the splashdown zone and the jettison of the hot-stage adapter. SpaceX official
  4. Done Booster landing Landing burn and soft splashdown in the Gulf of Mexico 7 minutes 24 seconds into the flight. SpaceX official
  5. Done Ship ascent burn The six ship Raptors put the vehicle on its planned trajectory for coast. SpaceX official
  6. Done Ship reentry Controlled reentry through peak heating and max aerodynamic pressure, steered by the flaps at hypersonic speed. SpaceX official
  7. Done Ship landing The three center Raptors lit for the first flip and landing burn since the suborbital campaign, then a soft splashdown in the Indian Ocean about one hour and six minutes after launch. SpaceX official

No source read for: Orbit insertion, Payload or door, Propellant transfer demo, In-space relight. Blank means not sourced here, not that it did not happen.

FAA

  1. 2024-06-05 Licence. The FAA approved the Flight 4 license authorization, with three test induced damage exceptions for the Starship entry. FAA official

NET 2024-06-06 at Starbase Pad 1

Revisions

  1. 2024-06-06 NET 2024-06-06 at Starbase Pad 1

Assignment

  • B11 booster UNCONFIRMED
  • S29 ship UNCONFIRMED
  1. 2024-06-06 outcome F4 booster splashdown (no), ship splashdown (no), payload data

    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.

    SpaceX Web page Confirms alone

  2. 2024-06-06 UNCONFIRMED assign S29 as ship on F4

    Assign Ship 29 as the ship on Flight 4.

    NASASpaceflight Web page Counts with a second source

  3. 2024-06-06 UNCONFIRMED assign B11 as booster on F4

    Assign Booster 11 as the booster on Flight 4.

    NASASpaceflight Web page Counts with a second source

  4. 2024-06-06 Flight 4 F4 NET 2024-06-06 at P1

    Flight 4 lifted off from Starbase Pad 1 on 6 Jun 2024 at 7:50 a.m. CT.

    SpaceX Web page Confirms alone SpaceX Web page Confirms alone

  5. 2024-06-06 identify flight Flight 4

    Identify Flight 4 as Starship's fourth flight test.

    SpaceX Web page Confirms alone

Pad flow

Claims about B11 and S29 from L-30 days to the NET day (L-0, 2024-06-06). 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-0 2024-06-06: 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.B11L-0 2024-06-06: 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.S29

Assigned vehicle notes

Claims that name B11 or S29, the vehicles assigned above.

  1. 2024-06-06 UNCONFIRMED note about S29

    On Flight 4, Ship 29 made a controlled reentry and a soft splashdown in the Indian Ocean one hour and six minutes after launch, after a flip and landing burn on its three center Raptors. Plasma burned through a forward flap hinge during reentry, and the flap still moved for the landing flip.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-38dfa4d86b22

  2. 2024-06-06 UNCONFIRMED note about B11

    On Flight 4, Booster 11 completed its flip, boostback burn, and hot-stage jettison, then a landing burn and soft splashdown in the Gulf of Mexico seven minutes and 24 seconds after liftoff. One of the 13 landing engines did not reignite. It later tipped over.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source NASASpaceflight Web page Counts with a second source

    c-6cefbad49ccf

Flight 5

  1. 2024-10-13 confirmed c-6229581009e1

    Booster
    caught
    Ship
    splashdown
    Booster catch
    yes
    Ship catch
    no
    Orbit
    not stated
    Payload
    not stated

    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.

    SpaceX Web page Confirms alone

Flight history

All boosters and ships

Liftoff
2024-10-13 12:25 UTC, UK 13 Oct 2024, 13:25 BST. Stated as 7:25 a.m. CDT. NASASpaceflight tracker
Pad
Starbase Pad 1 (from the schedule claim c-30ce77b2360d)
Booster
B12 UNCONFIRMED (assign claim c-1e68919d87ab)
Ship
S30 UNCONFIRMED (assign claim c-f6671c54ce4b)
Raptors
No sourced engine count.
  1. Done Hot staging Hot-staging separation, with the ship igniting its six Raptor engines. SpaceX official
  2. Done Boostback Liftoff, ascent, stage separation, boostback burn and coast all succeeded. SpaceX official
  3. Done Booster landing The booster performed its landing burn and was caught by the chopstick arms of the launch and catch tower, on the first attempt. SpaceX official
  4. Done Ship ascent burn The ship completed its ascent into space. SpaceX official
  5. Done Ship reentry Controlled reentry through peak heating and maximum aerodynamic pressure. SpaceX official
  6. Done Ship landing Flip, landing burn and splashdown at the target area in the Indian Ocean, 1 hour 5 minutes 40 seconds after launch. SpaceX official

No source read for: Booster ascent, Orbit insertion, Payload or door, Propellant transfer demo, In-space relight. Blank means not sourced here, not that it did not happen.

FAA

No FAA mishap or licence statement cited for this flight.

NET 2024-10-13 at Starbase Pad 1

Revisions

  1. 2024-10-13 NET 2024-10-13 at Starbase Pad 1

Assignment

  • B12 booster UNCONFIRMED
  • S30 ship UNCONFIRMED
  1. 2024-10-13 outcome F5 booster caught (yes), ship splashdown (no)

    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.

    SpaceX Web page Confirms alone

  2. 2024-10-13 UNCONFIRMED assign S30 as ship on F5

    Assign Ship 30 as the ship on Flight 5.

    NASASpaceflight Web page Counts with a second source

  3. 2024-10-13 UNCONFIRMED assign B12 as booster on F5

    Assign Booster 12 as the booster on Flight 5.

    NASASpaceflight Web page Counts with a second source

  4. 2024-10-13 Flight 5 F5 NET 2024-10-13 at P1

    Flight 5 lifted off from Starbase Pad 1 on 13 Oct 2024.

    SpaceX Web page Confirms alone SpaceX Web page Confirms alone

  5. 2024-10-13 identify flight Flight 5

    Identify Flight 5 as Starship's fifth flight test.

    SpaceX Web page Confirms alone

Pad flow

Claims about B12 and S30 from L-30 days to the NET day (L-0, 2024-10-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-0 2024-10-13: 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.B12L-0 2024-10-13: 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.S30

Assigned vehicle notes

Claims that name B12 or S30, the vehicles assigned above.

  1. 2024-10-13 UNCONFIRMED note about S30

    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.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-76d73a812723

  2. 2024-10-13 UNCONFIRMED note about B12

    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.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-59cc5081f358

Flight 6

  1. 2024-11-19 confirmed c-efa04be0475a

    Booster
    splashdown
    Ship
    splashdown
    Booster catch
    no
    Ship catch
    no
    Orbit
    no
    Payload
    data

    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.

    SpaceX Web page Confirms alone

Flight history

All boosters and ships

Liftoff
2024-11-19 22:00 UTC, UK 19 Nov 2024, 22:00 GMT. Stated as 4 pm CST. NASASpaceflight tracker
Pad
Starbase Pad 1 (from the schedule claim c-4b4c882617ff)
Booster
B13 UNCONFIRMED (assign claim c-a587f0633836)
Ship
S31 UNCONFIRMED (assign claim c-1390fd704ecf)
Raptors
33 on the booster. SpaceX official
  1. Done Booster ascent Lifted off at the start of the window with all 33 Raptor engines. SpaceX official
  2. Done Hot staging Nominal ascent and stage separation. SpaceX official
  3. Done Boostback The booster transitioned to its boostback burn to return to the launch site. SpaceX official
  4. Aborted Booster landing Automated health checks of hardware on the launch and catch tower aborted the catch. The booster flew a pre-planned divert, a landing burn and a soft splashdown in the Gulf of Mexico. SpaceX official
  5. Done Ship ascent burn Another successful ascent onto the expected trajectory. SpaceX official
  6. Done In-space relight The ship reignited a single Raptor engine in space. SpaceX official
  7. Done Ship reentry The ship made it through reentry with live views relayed by Starlink. SpaceX official
  8. Done Ship landing Flip, landing burn and soft splashdown in the Indian Ocean. SpaceX official

No source read for: Orbit insertion, Payload or door, 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 2024-11-19 at Starbase Pad 1

Revisions

  1. 2024-11-19 NET 2024-11-19 at Starbase Pad 1

Assignment

  • B13 booster UNCONFIRMED
  • S31 ship UNCONFIRMED
  1. 2024-11-19 outcome F6 booster splashdown (no), ship splashdown (no), orbit no, payload data

    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.

    SpaceX Web page Confirms alone

  2. 2024-11-19 UNCONFIRMED assign S31 as ship on F6

    Assign Ship 31 as the ship on Flight 6.

    NASASpaceflight Web page Counts with a second source

  3. 2024-11-19 UNCONFIRMED assign B13 as booster on F6

    Assign Booster 13 as the booster on Flight 6.

    NASASpaceflight Web page Counts with a second source

  4. 2024-11-19 Flight 6 F6 NET 2024-11-19 at P1

    Flight 6 lifted off from Starbase Pad 1 on 19 Nov 2024.

    SpaceX Web page Confirms alone SpaceX Web page Confirms alone

  5. 2024-11-19 identify flight Flight 6

    Identify Flight 6 as Starship's sixth flight test.

    SpaceX Web page Confirms alone

Pad flow

Claims about B13 and S31 from L-30 days to the NET day (L-0, 2024-11-19). 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-0 2024-11-19: 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.B13L-0 2024-11-19: 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.S31

Assigned vehicle notes

Claims that name B13 or S31, the vehicles assigned above.

  1. 2024-11-19 UNCONFIRMED note about S31

    On Flight 6, Ship 31 relit a single Raptor engine in space, then made it through reentry and a flip, landing burn, and soft splashdown in the Indian Ocean.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-98e454c3dcb0

  2. 2024-11-19 UNCONFIRMED note about B13

    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.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-dffa9925413e

Flight 7

  1. 2025-01-16 confirmed c-95aeff943b80

    Booster
    caught
    Ship
    lost
    Booster catch
    yes
    Ship catch
    no
    Orbit
    not stated
    Payload
    not stated

    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.

    SpaceX Web page Confirms alone

Flight history

All boosters and ships

Liftoff
2025-01-16 22:37 UTC, UK 16 Jan 2025, 22:37 GMT. Stated as 4:37 p.m. CT. SpaceX official
Pad
Starbase Pad 1 (from the schedule claim c-c65fa659f9ae)
Booster
B14 UNCONFIRMED (assign claim c-9aa5d6089cbf)
Ship
S33 UNCONFIRMED (assign claim c-a595457f7171)
Raptors
33 on the booster, 6 on the ship. SpaceX official
  1. Done Booster ascent All 33 Raptor engines powered a nominal ascent. SpaceX official
  2. Done Hot staging Successful hot-stage separation. SpaceX official
  3. Partial Boostback 12 of the 13 planned Raptor engines relit for the boostback burn. SpaceX official
  4. Done Booster landing All 13 planned engines relit for the landing burn, including the one that missed boostback, and the booster was caught by the tower arms: the second booster catch. SpaceX official
  5. Failed Ship ascent burn All six ship Raptors lit, but telemetry was lost about eight and a half minutes in, before the burn finished. Initial data pointed to a fire in the aft section and a rapid unscheduled disassembly. SpaceX official

No source read for: Orbit insertion, Payload or door, Propellant transfer demo, In-space relight, Ship reentry, Ship landing. Blank means not sourced here, not that it did not happen.

FAA

  1. 2025-01-17 Mishap investigation required. The FAA required a mishap investigation into the loss of the Starship vehicle and activated a Debris Response Area. FAA official
  2. 2025-02-26 Return to flight. The FAA determined Starship could return to flight while the Flight 7 investigation stayed open, and issued the Flight 8 license modification. FAA official
  3. 2025-03-28 Mishap investigation closed 11 corrective actions. Investigation closed. Probable root cause: stronger than anticipated vibrations stressed and failed propulsion system hardware. SpaceX identified 11 corrective actions. One confirmed report of minor vehicle damage in the Turks and Caicos Islands. FAA official

NET 2025-01-16 at Starbase Pad 1

Revisions

  1. 2025-01-16 NET 2025-01-16 at Starbase Pad 1

Assignment

  • B14 booster UNCONFIRMED
  • S33 ship UNCONFIRMED
  1. 2025-01-16 outcome F7 booster caught (yes), ship lost (no)

    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.

    SpaceX Web page Confirms alone

  2. 2025-01-16 UNCONFIRMED assign S33 as ship on F7

    Assign Ship 33 as the ship on Flight 7.

    NASASpaceflight Web page Counts with a second source

  3. 2025-01-16 UNCONFIRMED assign B14 as booster on F7

    Assign Booster 14 as the booster on Flight 7.

    NASASpaceflight Web page Counts with a second source

  4. 2025-01-16 Flight 7 F7 NET 2025-01-16 at P1

    Flight 7 lifted off from Starbase Pad 1 on 16 Jan 2025 at 4:37 p.m. CT.

    SpaceX Web page Confirms alone SpaceX Web page Confirms alone

  5. 2025-01-16 identify flight Flight 7

    Identify Flight 7 as Starship's seventh flight test, the first Starship flight test of 2025.

    SpaceX Web page Confirms alone

Pad flow

Claims about B14 and S33 from L-30 days to the NET day (L-0, 2025-01-16). 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-0 2025-01-16: 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.B14L-0 2025-01-16: 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.S33

Assigned vehicle notes

Claims that name B14 or S33, the vehicles assigned above.

  1. 2025-05-27 UNCONFIRMED note about B14

    On Flight 9, Booster 14 flew again after Flight 7, the first Super Heavy reflight. It completed ascent on all 33 Raptors and boostback, then contact was lost shortly after the landing burn began and the booster broke up about six minutes after launch over the Gulf of America.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-3fef1ccf1258

  2. 2025-05-27 UNCONFIRMED assign B14 as booster on F9

    Assign Booster 14 as the booster on Flight 9. NASASpaceflight calls this second flight Booster 14-2. SpaceX says the booster had previously launched on the seventh flight test.

    NASASpaceflight Web page Counts with a second source SpaceX Web page Confirms alone

    c-7d0ad0b29c3b

  3. 2025-01-16 UNCONFIRMED note about S33

    On Flight 7, Ship 33 lit all six Raptors after separation. A fire in the aft section led to a breakup during ascent, and telemetry was lost after about eight and a half minutes of flight.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-cecaf3a7521e

  4. 2025-01-16 UNCONFIRMED note about B14

    On Flight 7, Booster 14 relit 12 of 13 planned engines for boostback, then all 13 for the landing burn, and was caught by the launch and catch tower arms. This was the second Super Heavy catch.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-51c95f88a48f

Flight 8

  1. 2025-03-06 confirmed c-6bebbd589de6

    Booster
    caught
    Ship
    lost
    Booster catch
    yes
    Ship catch
    no
    Orbit
    not stated
    Payload
    not stated

    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.

    SpaceX Web page Confirms alone

Flight history

All boosters and ships

Liftoff
2025-03-06 23:30 UTC, UK 6 Mar 2025, 23:30 GMT. Stated as 5:30 p.m. CT. SpaceX official
Pad
Starbase Pad 1 (from the schedule claim c-b377cfd90471)
Booster
B15 UNCONFIRMED (assign claim c-3421a657219c)
Ship
S34 UNCONFIRMED (assign claim c-ff270c9839ae)
Raptors
33 on the booster, 6 on the ship. SpaceX official
  1. Done Booster ascent The booster lit its 33 Raptor engines for a nominal first-stage ascent. SpaceX official
  2. Done Hot staging All but three booster Raptors shut down as planned and the ship lit its six Raptors and separated. SpaceX official
  3. Partial Boostback 11 of the 13 planned Raptor engines relit for the boostback burn back to the launch site. SpaceX official
  4. Done Booster landing 12 of the 13 planned engines relit for the landing burn and the booster was caught by the tower arms: the third booster catch. SpaceX official
  5. Failed Ship ascent burn Before the end of the ascent burn an energetic event in the aft section took out several Raptor engines, then attitude control and communications were lost. Final contact came about 9 minutes 30 seconds after liftoff. SpaceX official

No source read for: Orbit insertion, Payload or door, Propellant transfer demo, In-space relight, Ship reentry, Ship landing. Blank means not sourced here, not that it did not happen.

FAA

  1. 2025-03-06 Mishap investigation required. The FAA required a mishap investigation into the loss of the Starship vehicle. FAA official
  2. 2025-05-22 Return to flight. The FAA approved Starship return to flight and authorized Flight 9. FAA official
  3. 2025-06-12 Mishap investigation closed 8 corrective actions. Investigation closed. Probable root cause: a hardware failure in one Raptor engine led to inadvertent propellant mixing and ignition. SpaceX identified eight corrective actions. FAA official

NET 2025-03-06 at Starbase Pad 1

Revisions

  1. 2025-03-06 NET 2025-03-06 at Starbase Pad 1

Assignment

  • B15 booster UNCONFIRMED
  • S34 ship UNCONFIRMED
  1. 2025-03-06 outcome F8 booster caught (yes), ship lost (no)

    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.

    SpaceX Web page Confirms alone

  2. 2025-03-06 UNCONFIRMED assign S34 as ship on F8

    Assign Ship 34 as the ship on Flight 8.

    NASASpaceflight Web page Counts with a second source

  3. 2025-03-06 UNCONFIRMED assign B15 as booster on F8

    Assign Booster 15 as the booster on Flight 8.

    NASASpaceflight Web page Counts with a second source

  4. 2025-03-06 Flight 8 F8 NET 2025-03-06 at P1

    Flight 8 lifted off from Starbase Pad 1 on 6 Mar 2025 at 5:30 p.m. CT.

    SpaceX Web page Confirms alone SpaceX Web page Confirms alone

  5. 2025-03-06 identify flight Flight 8

    Identify Flight 8 as Starship's eighth flight test.

    SpaceX Web page Confirms alone

Pad flow

Claims about B15 and S34 from L-30 days to the NET day (L-0, 2025-03-06). 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-0 2025-03-06: 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.B15L-0 2025-03-06: 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.S34

Assigned vehicle notes

Claims that name B15 or S34, the vehicles assigned above.

  1. 2025-10-13 UNCONFIRMED note about B15

    On Flight 11, Booster 15, on its second flight, completed boostback on 12 of 13 planned engines, then lit all 13 for the landing burn, hovered above the water, shut down, and splashed down off the Texas coast. NASASpaceflight says it then dropped into the Gulf and exploded.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-0ff98b6f31c0

  2. 2025-10-13 UNCONFIRMED assign B15 as booster on F11

    Assign Booster 15 as the booster on Flight 11. NASASpaceflight calls this second flight Booster 15-2 and says the booster first flew on Flight 8 with Ship 34.

    NASASpaceflight Web page Counts with a second source NASASpaceflight Web page Counts with a second source

    c-0e3b0d48c452

  3. 2025-03-06 UNCONFIRMED note about S34

    On Flight 8, Ship 34 lit all six Raptors and separated. Before the end of the ascent burn, an energetic event in the aft section took out several Raptors. Attitude control and communications were lost. Final contact was about 9 minutes and 30 seconds after liftoff.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-32a4eb9d16e9

  4. 2025-03-06 UNCONFIRMED note about B15

    On Flight 8, Booster 15 lit 33 Raptors, relit 11 of 13 planned engines for boostback, then 12 of 13 at the start of the landing burn, and was caught by the tower arms. This was the third Super Heavy catch.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-19478c89efad

Flight 9

  1. 2025-05-27 confirmed c-537f7c0fc125

    Booster
    lost
    Ship
    lost
    Booster catch
    no
    Ship catch
    no
    Orbit
    not stated
    Payload
    simulators

    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.

    SpaceX Web page Confirms alone

Flight history

All boosters and ships

Liftoff
2025-05-27 23:36 UTC, UK 28 May 2025, 00:36 BST. Stated as 6:36 p.m. CT. SpaceX official
Pad
Starbase Pad 1 (from the schedule claim c-19314e83ec26)
Booster
B14 UNCONFIRMED (assign claim c-7d0ad0b29c3b)
Ship
S35 UNCONFIRMED (assign claim c-658ec636df4c)
Raptors
33 on the booster, 6 on the ship. SpaceX official
  1. Done Booster ascent First reflight of a Super Heavy booster (it first flew on Flight 7). Full-duration ascent burn on all 33 Raptor engines. SpaceX official
  2. Done Hot staging Hot-staging separation, with the first deterministic booster flip. SpaceX official
  3. Done Boostback The booster flew its boostback burn, then tested a higher angle of attack on descent. SpaceX official
  4. Failed Booster landing 12 of 13 center and middle ring engines relit for the landing burn. Contact was lost shortly after, in a rapid unscheduled disassembly about 6 minutes after launch. SpaceX official
  5. Done Ship ascent burn The ship lit all six Raptor engines and completed a full-duration ascent burn. SpaceX official
  6. Failed Payload or door The payload bay door did not open, so the eight Starlink simulators were not deployed. SpaceX official
  7. Not attempted In-space relight An attitude control error led to the Raptor relight being bypassed. SpaceX official
  8. Failed Ship reentry The ship could not reach its reentry attitude and was safed. Contact was lost about 46 minutes into the flight. SpaceX official

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

FAA

  1. 2025-05-30 Mishap investigation required. The FAA required a mishap investigation into the loss of the Starship vehicle only. The booster loss was covered by an approved test induced damage exception. FAA official
  2. 2025-08-15 Mishap investigation closed. Investigation closed. Probable root cause: failure of a fuel component. Flight 10 could proceed. FAA official

NET 2025-05-27 at Starbase Pad 1

Revisions

  1. 2025-05-27 NET 2025-05-27 at Starbase Pad 1

Assignment

  • B14 booster UNCONFIRMED
  • S35 ship UNCONFIRMED
  1. 2025-05-27 outcome F9 booster lost (no), ship lost (no), payload simulators

    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.

    SpaceX Web page Confirms alone

  2. 2025-05-27 UNCONFIRMED assign S35 as ship on F9

    Assign Ship 35 as the ship on Flight 9.

    NASASpaceflight Web page Counts with a second source

  3. 2025-05-27 UNCONFIRMED assign B14 as booster on F9

    Assign Booster 14 as the booster on Flight 9. NASASpaceflight calls this second flight Booster 14-2. SpaceX says the booster had previously launched on the seventh flight test.

    NASASpaceflight Web page Counts with a second source SpaceX Web page Confirms alone

  4. 2025-05-27 Flight 9 F9 NET 2025-05-27 at P1

    Flight 9 lifted off from Starbase Pad 1 on 27 May 2025 at 6:36 p.m. CT.

    SpaceX Web page Confirms alone SpaceX Web page Confirms alone

  5. 2025-05-27 identify flight Flight 9

    Identify Flight 9 as Starship's ninth flight test.

    SpaceX Web page Confirms alone

  6. 2025-05-15 filing FAA ea on F9

    FAA published the Final Tiered EA and FONSI/ROD for Updates to Airspace Closures for the Flight 9 Mission Profile at the Boca Chica Launch Site, with the associated license modification. Its Aircraft Hazard Area and NOTAM close airspace over part of the Bahamas and the Turks and Caicos Islands.

    FAA Web page Confirms alone

Pad flow

Claims about B14 and S35 from L-30 days to the NET day (L-0, 2025-05-27). 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-0 2025-05-27: 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.B14L-0 2025-05-27: 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.S35

Assigned vehicle notes

Claims that name B14 or S35, the vehicles assigned above.

  1. 2025-05-27 UNCONFIRMED note about S35

    On Flight 9, Ship 35 completed a full-duration ascent burn. The payload bay door did not open, so eight Starlink simulator satellites were not deployed. An attitude control error bypassed the Raptor relight. Contact was lost about 46 minutes into the flight, with debris expected inside the planned hazard area in the Indian Ocean.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-4ba932b6e2e5

  2. 2025-05-27 UNCONFIRMED note about B14

    On Flight 9, Booster 14 flew again after Flight 7, the first Super Heavy reflight. It completed ascent on all 33 Raptors and boostback, then contact was lost shortly after the landing burn began and the booster broke up about six minutes after launch over the Gulf of America.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-3fef1ccf1258

  3. 2025-01-16 UNCONFIRMED note about B14

    On Flight 7, Booster 14 relit 12 of 13 planned engines for boostback, then all 13 for the landing burn, and was caught by the launch and catch tower arms. This was the second Super Heavy catch.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-51c95f88a48f

  4. 2025-01-16 UNCONFIRMED assign B14 as booster on F7

    Assign Booster 14 as the booster on Flight 7.

    NASASpaceflight Web page Counts with a second source

    c-9aa5d6089cbf

Flight 10

  1. 2025-08-26 confirmed c-a2ea477e7df7

    Booster
    splashdown
    Ship
    splashdown
    Booster catch
    no
    Ship catch
    no
    Orbit
    no
    Payload
    simulators

    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.

    SpaceX Web page Confirms alone

Flight history

All boosters and ships

Liftoff
2025-08-26 23:30 UTC, UK 27 Aug 2025, 00:30 BST. Stated as 6:30 p.m. CT. SpaceX official
Pad
Starbase Pad 1 (from the schedule claim c-e98875e23500)
Booster
B16 UNCONFIRMED (assign claim c-15300615774f)
Ship
S37 UNCONFIRMED (assign claim c-066b480ec36a)
Raptors
33 on the booster, 6 on the ship. SpaceX official
  1. Done Booster ascent All 33 Raptor engines ignited for liftoff and ascent. SpaceX official
  2. Done Hot staging Hot-staging, with the six ship Raptors igniting to separate. SpaceX official
  3. Done Boostback The booster completed its boostback burn toward a pre-planned splashdown zone. SpaceX official
  4. Done Booster landing Landing burn with one of the three center engines intentionally disabled and a middle ring engine used as backup, then a hover and splashdown. SpaceX official
  5. Done Ship ascent burn Full-duration ascent burn onto a suborbital trajectory. SpaceX official
  6. Done Payload or door Eight Starlink simulators deployed: the first successful payload demonstration from Starship. SpaceX official
  7. Done In-space relight Second ever in-space Raptor relight. SpaceX official
  8. Done Ship reentry Reentry with the heatshield and structure intentionally stressed. SpaceX official
  9. Done Ship landing Landing flip, landing burn and soft splashdown at the target point in the Indian Ocean. SpaceX official

No source read for: Orbit insertion, 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 2025-08-26 at Starbase Pad 1

Revisions

  1. 2025-08-26 NET 2025-08-26 at Starbase Pad 1

Assignment

  • B16 booster UNCONFIRMED
  • S37 ship UNCONFIRMED
  1. 2025-08-26 outcome F10 booster splashdown (no), ship splashdown (no), orbit no, payload simulators

    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.

    SpaceX Web page Confirms alone

  2. 2025-08-26 UNCONFIRMED assign S37 as ship on F10

    Assign Ship 37 as the ship on Flight 10.

    NASASpaceflight Web page Counts with a second source

  3. 2025-08-26 UNCONFIRMED assign B16 as booster on F10

    Assign Booster 16 as the booster on Flight 10.

    NASASpaceflight Web page Counts with a second source

  4. 2025-08-26 Flight 10 F10 NET 2025-08-26 at P1

    Flight 10 lifted off from Starbase Pad 1 on 26 Aug 2025 at 6:30 p.m. CT.

    SpaceX Web page Confirms alone SpaceX Web page Confirms alone

  5. 2025-08-26 identify flight Flight 10

    Identify Flight 10 as Starship's tenth flight test.

    SpaceX Web page Confirms alone

Pad flow

Claims about B16 and S37 from L-30 days to the NET day (L-0, 2025-08-26). 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-0 2025-08-26: 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.B16L-0 2025-08-26: 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.S37

Assigned vehicle notes

Claims that name B16 or S37, the vehicles assigned above.

  1. 2025-08-26 UNCONFIRMED note about S37

    On Flight 10, Ship 37 completed a full-duration ascent burn, deployed eight Starlink simulators, relit a Raptor in space, and made a landing flip, landing burn, and soft splashdown in the Indian Ocean. NASASpaceflight says the ship tipped over and exploded after splashdown.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-ec88a4546a58

  2. 2025-08-26 UNCONFIRMED note about B16

    On Flight 10, Booster 16 lifted off on all 33 Raptors, lost one engine during ascent, completed boostback and a landing burn, hovered above the water, then shut down and splashed down. NASASpaceflight says the drop into the water and the explosion were intentional.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-f248b8baf946

Flight 11

  1. 2025-10-13 confirmed c-bdab56392720

    Booster
    splashdown
    Ship
    splashdown
    Booster catch
    no
    Ship catch
    no
    Orbit
    no
    Payload
    simulators

    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.

    SpaceX Web page Confirms alone

Flight history

All boosters and ships

Liftoff
2025-10-13 23:23 UTC, UK 14 Oct 2025, 00:23 BST. Stated as 6:23 p.m. CT. SpaceX official
Pad
Starbase Pad 1 (from the schedule claim c-a5ca421f05fc)
Booster
B15 UNCONFIRMED (assign claim c-0e3b0d48c452)
Ship
S38 UNCONFIRMED (assign claim c-70ba254dfc3d)
Raptors
33 on the booster, 6 on the ship. SpaceX official
  1. Done Booster ascent All 33 Raptor engines ignited. Final flight of the second-generation ship and first-generation booster, and the last launch from Pad 1 in its current configuration. SpaceX official
  2. Done Hot staging Hot-staging, with the six ship Raptors igniting. SpaceX official
  3. Partial Boostback Boostback toward a splashdown zone off Texas on 12 of the 13 planned engines. SpaceX official
  4. Done Booster landing All 13 planned engines lit for the landing burn, including the one that missed boostback. The booster hovered above the water, shut down and splashed down. SpaceX official
  5. Done Ship ascent burn Full-duration ascent burn to the planned velocity and trajectory. SpaceX official
  6. Done Payload or door Eight Starlink simulators deployed. SpaceX official
  7. Done In-space relight Third in-space Raptor relight. SpaceX official
  8. Done Ship reentry Reentry with the heatshield intentionally stressed, then a dynamic banking maneuver. SpaceX official
  9. Done Ship landing Landing flip, landing burn and soft splashdown in the Indian Ocean. SpaceX official

No source read for: Orbit insertion, 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 2025-10-13 at Starbase Pad 1

Revisions

  1. 2025-10-13 NET 2025-10-13 at Starbase Pad 1

Assignment

  • B15 booster UNCONFIRMED
  • S38 ship UNCONFIRMED
  1. 2025-10-13 outcome F11 booster splashdown (no), ship splashdown (no), orbit no, payload simulators

    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.

    SpaceX Web page Confirms alone

  2. 2025-10-13 UNCONFIRMED assign S38 as ship on F11

    Assign Ship 38 as the ship on Flight 11.

    NASASpaceflight Web page Counts with a second source

  3. 2025-10-13 UNCONFIRMED assign B15 as booster on F11

    Assign Booster 15 as the booster on Flight 11. NASASpaceflight calls this second flight Booster 15-2 and says the booster first flew on Flight 8 with Ship 34.

    NASASpaceflight Web page Counts with a second source NASASpaceflight Web page Counts with a second source

  4. 2025-10-13 Flight 11 F11 NET 2025-10-13 at P1

    Flight 11 lifted off from Starbase Pad 1 on 13 Oct 2025 at 6:23 p.m. CT.

    SpaceX Web page Confirms alone SpaceX Web page Confirms alone

  5. 2025-10-13 identify flight Flight 11

    Identify Flight 11 as Starship's eleventh flight test, the final flight of the second-generation Starship and first-generation Super Heavy, and the final launch from the then-current Pad 1 configuration.

    SpaceX Web page Confirms alone

Pad flow

Claims about B15 and S38 from L-30 days to the NET day (L-0, 2025-10-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-0 2025-10-13: 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.B15L-0 2025-10-13: 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.S38

Assigned vehicle notes

Claims that name B15 or S38, the vehicles assigned above.

  1. 2025-10-13 UNCONFIRMED note about S38

    On Flight 11, Ship 38 completed a full-duration ascent burn, deployed eight Starlink simulators, relit a Raptor in space, and made a landing flip, landing burn, and soft splashdown in the Indian Ocean.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-44da580f8ad4

  2. 2025-10-13 UNCONFIRMED note about B15

    On Flight 11, Booster 15, on its second flight, completed boostback on 12 of 13 planned engines, then lit all 13 for the landing burn, hovered above the water, shut down, and splashed down off the Texas coast. NASASpaceflight says it then dropped into the Gulf and exploded.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-0ff98b6f31c0

  3. 2025-03-06 UNCONFIRMED note about B15

    On Flight 8, Booster 15 lit 33 Raptors, relit 11 of 13 planned engines for boostback, then 12 of 13 at the start of the landing burn, and was caught by the tower arms. This was the third Super Heavy catch.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-19478c89efad

  4. 2025-03-06 UNCONFIRMED assign B15 as booster on F8

    Assign Booster 15 as the booster on Flight 8.

    NASASpaceflight Web page Counts with a second source

    c-3421a657219c

Flight 12

  1. 2026-05-22 confirmed c-1c676c13e2cf

    Booster
    splashdown
    Ship
    splashdown
    Booster catch
    no
    Ship catch
    no
    Orbit
    no
    Payload
    simulators and starlink

    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.

    SpaceX Web page Confirms alone

Flight history

All boosters and ships

Liftoff
2026-05-22 22:30 UTC, UK 22 May 2026, 23:30 BST. Stated as 5:30 p.m. CT. SpaceX official
Pad
Starbase Pad 2 (from the schedule claim c-3cf9efbc11f3)
Booster
B19 UNCONFIRMED (assign claim c-1eea5bab414e)
Ship
S39 UNCONFIRMED (assign claim c-c991b2b738ba)
Raptors
33 on the booster, 6 on the ship, Raptor 3. SpaceX official
  1. Partial Booster ascent First flight of the V3 vehicles and Raptor 3, and the first from Pad 2. All 33 Raptor 3 engines ignited and a single engine shut down during ascent. SpaceX official
  2. Done Hot staging Hot-staging, with the six ship Raptors igniting. SpaceX official
  3. Partial Boostback The booster could not light all planned engines and flew a partial boostback burn that ended early. SpaceX official
  4. Failed Booster landing The booster tried to reignite for the landing burn, then had a hard splashdown in the Gulf of America. SpaceX official
  5. Partial Ship ascent burn The ship lost one Raptor 3 vacuum engine during the ascent burn but still reached its planned trajectory. SpaceX official
  6. Done Payload or door All 20 Starlink simulators and two modified Starlink satellites that imaged Starship were deployed. SpaceX official
  7. Done Ship reentry Reentry with heatshield and structural data, a rear flap stress maneuver and a dynamic banking move. SpaceX official
  8. Done Ship landing Landing flip, landing burn and splashdown on two Raptor engines in the pre-planned zone in the Indian Ocean. SpaceX official

No source read for: Orbit insertion, Propellant transfer demo, In-space relight. Blank means not sourced here, not that it did not happen.

FAA

  1. 2026-05-22 Anomaly statement. The FAA said an anomaly involved the Super Heavy booster during its flyback over the Gulf of America and activated a Debris Response Area; the debris fell inside the hazard area. FAA official
  2. 2026-05-27 Mishap investigation required. The FAA determined the flight resulted in a mishap involving the Super Heavy booster and required a mishap investigation. FAA official
  3. 2026-07-13 Mishap investigation closed 4 corrective actions. Investigation closed. The FAA statement cites two most probable root causes for the loss of the Super Heavy booster: heat effects on propulsion system components during ascent and erroneous engine alarm system settings. SpaceX identified four corrective actions. Flight 13 could proceed. FAA official

NET 2026-05-22 at Starbase Pad 2

Revisions

  1. 2026-05-22 NET 2026-05-22 at Starbase Pad 2

Assignment

  • B19 booster UNCONFIRMED
  • S39 ship UNCONFIRMED
  1. 2026-05-22 outcome F12 booster splashdown (no), ship splashdown (no), orbit no, payload simulators-and-starlink

    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.

    SpaceX Web page Confirms alone

  2. 2026-05-22 UNCONFIRMED assign S39 as ship on F12

    Assign Ship 39 as the ship on Flight 12.

    NASASpaceflight Web page Counts with a second source NASASpaceflight Web page Counts with a second source

  3. 2026-05-22 UNCONFIRMED assign B19 as booster on F12

    Assign Booster 19 as the booster on Flight 12.

    NASASpaceflight Web page Counts with a second source NASASpaceflight Web page Counts with a second source

  4. 2026-05-22 Flight 12 F12 NET 2026-05-22 at P2

    Flight 12 lifted off from Starbase Pad 2 on 22 May 2026 at 5:30 p.m. CT.

    SpaceX Web page Confirms alone SpaceX Web page Confirms alone

  5. 2026-05-22 identify flight Flight 12

    Identify Flight 12 as Starship's twelfth flight test, the first flight of the Version 3 vehicles and the first flight from Pad 2.

    SpaceX Web page Confirms alone

Pad flow

Claims about B19 and S39 from L-30 days to the NET day (L-0, 2026-05-22). 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-0 2026-05-22: 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.B19L-0 2026-05-22: 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.S39

Assigned vehicle notes

Claims that name B19 or S39, the vehicles assigned above.

  1. 2026-05-22 UNCONFIRMED note about S39

    On Flight 12, Ship 39 lost one Raptor vacuum engine during ascent and still reached its planned trajectory. It deployed 20 Starlink simulators and two modified Starlink satellites, then made a landing flip, landing burn, and splashdown in the Indian Ocean on two Raptor engines. NASASpaceflight says the planned in-space Raptor relight was canceled after the early engine-out.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-82f547533d17

  2. 2026-05-22 UNCONFIRMED note about B19

    On Flight 12, Booster 19 lit all 33 Raptor 3 engines and shut one down during ascent. After separation it could not light every planned boostback engine, ended that burn early, and was lost in a hard splashdown in the Gulf of America.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-1c2db72ab0dc

Flight 13

  1. 2026-07-24 confirmed c-5cc373e24117

    Booster
    splashdown
    Ship
    splashdown
    Booster catch
    no
    Ship catch
    no
    Orbit
    not stated
    Payload
    starlink

    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.

    SpaceX Web page Confirms alone

Flight history

All boosters and ships

Liftoff
2026-07-24 22:51 UTC, UK 24 Jul 2026, 23:51 BST. Stated as 5:51 p.m. CT. SpaceX official
Pad
Starbase Pad 2 (from the schedule claim c-7bf904a1def2)
Booster
B20 UNCONFIRMED (assign claim c-42d3b5fbbbf6)
Ship
S40 UNCONFIRMED (assign claim c-57b3f8aa2274)
Raptors
33 on the booster, 6 on the ship, Raptor 3. SpaceX official
  1. Done Booster ascent Second flight of the V3 vehicles. All 33 Raptor 3 engines ignited for ascent. SpaceX official
  2. Done Hot staging Hot-staging, with the six ship Raptors igniting. SpaceX official
  3. Partial Boostback The booster completed the high thrust part of the boostback burn on all 33 engines, a first for a V3 booster, then ended the burn early. SpaceX official
  4. Failed Booster landing A subset of engines relit for the landing burn before a hard splashdown in the Gulf. SpaceX official
  5. Done Ship ascent burn Full-duration ascent burn on all six Raptor engines. SpaceX official
  6. Done Payload or door All 20 Starlink V3 satellites deployed, the first Starlink V3 deployment. SpaceX official
  7. Done In-space relight A single Raptor engine was reignited in space. SpaceX official
  8. Done Ship reentry Reentry with heatshield data and a dynamic banking move. SpaceX official
  9. Done Ship landing All three Raptor engines relit for the landing flip and burn, then a soft splashdown. The ship came to rest intact, giving the first views of an intact heatshield. SpaceX official

No source read for: Orbit insertion, 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-07-24 at Starbase Pad 2

Revisions

  1. 2026-07-24 NET 2026-07-24 at Starbase Pad 2

Assignment

  • B20 booster UNCONFIRMED
  • S40 ship UNCONFIRMED
  1. 2026-07-24 outcome F13 booster splashdown (no), ship splashdown (no), payload starlink

    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.

    SpaceX Web page Confirms alone

  2. 2026-07-24 UNCONFIRMED assign S40 as ship on F13

    Assign Ship 40 as the ship on Flight 13.

    NASASpaceflight Web page Counts with a second source

  3. 2026-07-24 UNCONFIRMED assign B20 as booster on F13

    Assign Booster 20 as the booster on Flight 13.

    NASASpaceflight Web page Counts with a second source

  4. 2026-07-24 Flight 13 F13 NET 2026-07-24 at P2

    Flight 13 lifted off from Starbase Pad 2 on 24 Jul 2026 at 5:51 p.m. CT.

    SpaceX Web page Confirms alone SpaceX Web page Confirms alone

  5. 2026-07-24 identify flight Flight 13

    Identify Flight 13 as Starship's thirteenth flight test, the second flight of the Version 3 vehicles and the first to deploy Starlink V3 satellites.

    SpaceX Web page Confirms alone

Pad flow

Claims about B20 and S40 from L-30 days to the NET day (L-0, 2026-07-24). 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-0 2026-07-24: 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.B20L-0 2026-07-24: 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.S40

Assigned vehicle notes

Claims that name B20 or S40, the vehicles assigned above.

  1. 2026-10-31 UNCONFIRMED note at MB2 about S40

    RGVaerialphotos posted a photo of Ship 40 inside Mega Bay 2.

    @RGVaerialphotos X post Counts with a second source

    c-089c297c31ec

  2. 2026-10-18 note at MB2 about S40

    TrackingTheSB weekly: after its tip-up, Ship 40 was moved into Mega Bay 2 and placed onto one of the work stands in the building. The post says SpaceX's plans for it are unknown, and whether it goes on display or is scrapped is not known.

    @TrackingTheSB X post Confirms alone

    c-03e79892d4e8

  3. 2026-10-15 UNCONFIRMED note at MB2 about S40

    NSF Starbase summary: S40 now stands inside Mega Bay 2 with three future flight vehicles, naming the bay SpaceX left unnamed on 13 Oct. NSF footage shows a hexagonal breakover frame pinned to the base of S40 so it pivoted on rollers as the front bridge crane raised it.

    @NASASpaceflight X post Counts with a second source

    c-55b6cf830a8b

  4. 2026-10-13 note about S40

    SpaceX: S40, the first Starship to return to its launch site, is vertical alongside three other ships in a Mega Bay at Starbase and will give first-of-its-kind data on a flown heatshield, Raptor engines and avionics. The post does not name the bay.

    @SpaceX X post Confirms alone

    c-dfc4f52f6820

  5. 2026-07-24 UNCONFIRMED note about S40

    On Flight 13, Ship 40 completed a full-duration ascent burn on all six Raptors, deployed 20 Starlink V3 satellites, relit a single Raptor in space, and made a landing flip, landing burn, and soft splashdown in the Indian Ocean, coming to rest intact.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-64ee78a608cd

  6. 2026-07-24 UNCONFIRMED note about B20

    On Flight 13, Booster 20 completed the high-thrust portion of boostback on all 33 engines, the first time for a Super Heavy V3, then ended that burn early. A subset of engines lit for the landing burn before a hard splashdown in the Gulf.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-fc92de05629a

Flight 14

  1. 2026-09-28 confirmed c-0a2b5043ee66

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

    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.

    SpaceX Web page Confirms alone

Flight history

All boosters and ships

Liftoff
2026-09-28 12:48 UTC, UK 28 Sept 2026, 13:48 BST. Stated as 7:48 a.m. CT. SpaceX official
Pad
Starbase Pad 2 (from the schedule claim c-74fa6c3e2628)
Booster
B21 (assign claim c-5f0748a457e4)
Ship
S41 (assign claim c-93f001a7d57f)
Raptors
33 on the booster, 6 on the ship, Raptor 3. SpaceX official
  1. Partial Booster ascent All 33 Raptor 3 engines ignited. A single booster engine shut down during the climb. SpaceX official
  2. Done Hot staging Hot-staging, with all six ship Raptors igniting. SpaceX official
  3. Partial Boostback 31 of the 33 planned engines relit for a boostback burn designed to burn through the remaining liquid oxygen in the main tank. SpaceX official
  4. Done Booster landing 11 of the 13 planned engines relit for the high thrust part of the landing burn, then five, then three, before splashdown in the Gulf. The flight termination system was then triggered as a demonstration. SpaceX official
  5. Partial Ship ascent burn A single Raptor vacuum engine shut down early. The other five burned longer and the ship still reached its planned suborbital trajectory. SpaceX official
  6. Done Orbit insertion A single sea-level Raptor relit for an orbit insertion burn and Starship entered orbit for the first time. SpaceX official
  7. Done Payload or door All 26 Starlink V3 satellites deployed and contacted. SpaceX official
  8. Done In-space relight A single sea-level Raptor relit for the first ever Starship deorbit burn, after a shortened time on orbit. SpaceX official
  9. Done Ship reentry Atmospheric reentry and descent to the intended splashdown point. SpaceX official
  10. Done Ship landing All three sea-level Raptors relit for the landing burn and flip, then a splashdown on target in the Pacific Ocean. 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-09-28 at Starbase Pad 2

Revisions

  1. 2026-09-28 NET 2026-09-28 at Starbase Pad 2

Assignment

  1. 2026-09-28 outcome F14 booster splashdown (no), ship splashdown (no), orbit yes, payload starlink

    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.

    SpaceX Web page Confirms alone

  2. 2026-09-28 assign S41 as ship on F14

    Assign Ship 41 as the ship on Flight 14.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

  3. 2026-09-28 assign B21 as booster on F14

    Assign Booster 21 as the booster on Flight 14.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

  4. 2026-09-28 Flight 14 F14 NET 2026-09-28 at P2

    Flight 14 lifted off from Starbase Pad 2 on 28 Sep 2026 at 7:48 a.m. CT.

    SpaceX Web page Confirms alone

  5. 2026-09-28 identify flight Flight 14

    Identify Flight 14 as Starship Flight 14, the first orbital Starship flight.

    SpaceX Web page Confirms alone

Pad flow

Claims about B21 and S41 from L-30 days to the NET day (L-0, 2026-09-28). 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-7 2026-09-21: Flight 14 pad flow: Booster 21 rolled to the pad and was stacked the same day. The post does not name the pad.B21L-6 2026-09-22: 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.S41L-4 2026-09-24: Flight 14 wet dress rehearsal completed: a full count with propellant fill and deluge firing, no Raptor ignition. The rehearsal was announced on 22 Sep.B21L-3 2026-09-25: Flight 14 pad flow: after the wet dress rehearsal, Ship 41 was destacked from Booster 21 for one last quick checkout.S41L-2 2026-09-26: FAA launch licence for Flight 14 arrived on Saturday 26 Sep, after airspace and marine notices for ascent, the Hawaii return and the planned return off Chile through the week. TrackingTheSB says the licence removed the lightning rule.B21L-2 2026-09-26: Flight 14 pad flow: Ship 41 was restacked on Booster 21.S41L-0 2026-09-28: 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.S41L-0 2026-09-28: On Flight 14, Booster 21 lost one Raptor on ascent, completed its flight, and splashed down in the Gulf rather than being caught.B21

Assigned vehicle notes

Claims that name B21 or S41, the vehicles assigned above.

  1. 2026-09-28 note about B21

    On Flight 14, Booster 21 lost one Raptor on ascent, completed its flight, and splashed down in the Gulf rather than being caught.

    SpaceX Web page Confirms alone NASASpaceflight Web page Counts with a second source

    c-950e644bc753

  2. 2026-09-28 note about S41

    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.

    SpaceX Web page Confirms alone

    c-9d35c17b0239

  3. 2026-09-26 UNCONFIRMED note about S41

    Flight 14 pad flow: Ship 41 was restacked on Booster 21.

    @TrackingTheSB X post Confirms alone

    c-a71c8ef60810

  4. 2026-09-26 UNCONFIRMED note about B21

    FAA launch licence for Flight 14 arrived on Saturday 26 Sep, after airspace and marine notices for ascent, the Hawaii return and the planned return off Chile through the week. TrackingTheSB says the licence removed the lightning rule.

    @TrackingTheSB X post Confirms alone

    c-4d55fc8171cc

  5. 2026-09-25 UNCONFIRMED note about S41

    Flight 14 pad flow: after the wet dress rehearsal, Ship 41 was destacked from Booster 21 for one last quick checkout.

    @TrackingTheSB X post Confirms alone

    c-955c57425367

  6. 2026-09-24 UNCONFIRMED note about B21

    Flight 14 wet dress rehearsal completed: a full count with propellant fill and deluge firing, no Raptor ignition. The rehearsal was announced on 22 Sep.

    @TrackingTheSB X post Confirms alone

    c-2bc0503173e3

  7. 2026-09-22 UNCONFIRMED note about S41

    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.

    @TrackingTheSB X post Confirms alone

    c-d7f6157af215

  8. 2026-09-21 UNCONFIRMED note about B21

    Flight 14 pad flow: Booster 21 rolled to the pad and was stacked the same day. The post does not name the pad.

    @TrackingTheSB X post Confirms alone

    c-590a6d0e73a3

Flight notes

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

  1. 2026-10-20 note about F14

    SpaceX Q3 2026 results: Flight 14 was the first orbital Starship flight and the first revenue-generating Starship mission, delivering 26 Starlink V3 satellites, about 10x the downlink capacity added by a Falcon 9 Starlink launch.

    SEC EDGAR Web page Confirms alone @SpaceX X post Confirms alone

    c-8c06a0a25c82

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

Flight 16 (Starlink 30-1)

No outcome claim yet.

Readiness board

NET 2026-12-10 at LC-39A UNCONFIRMED

Revisions

No confirmed revision.

Assignment

  • S43 ship UNCONFIRMED
  • B23 booster UNCONFIRMED
  1. 2026-10-09 UNCONFIRMED assign B23 as booster on F16

    Assign Booster 23 as the booster on Flight 16. NSF names B23 with S43 for the first LC-39A Starship flight; on 15 Oct NSF again tied B23 cryo at Massey's to Flight 16.

    NASASpaceflight Web page Counts with a second source @NASASpaceflight X post Counts with a second source

  2. 2026-10-09 UNCONFIRMED assign S43 as ship on F16

    Assign Ship 43 as the ship on Flight 16. NSF names S43 with B23 for the first LC-39A Starship flight (Starlink Group 30-1).

    NASASpaceflight Web page Counts with a second source @NASASpaceflight X post Counts with a second source

  3. 2026-10-08 UNCONFIRMED Flight 16 (Starlink 30-1) F16 NET 2026-12-10 at 39A

    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

Assigned vehicle notes

Claims that name S43 or B23, the vehicles assigned above.

  1. 2026-11-03 UNCONFIRMED note at P2 about S43

    FelixSchlang says SpaceX recently lifted Ship 43 to catch height at Pad 2 for catch practice (photo by Jordan Guidry, WAI Media).

    @FelixSchlang X post Counts with a second source

    c-a459d50add72

  2. 2026-10-28 UNCONFIRMED note at MAS about B23

    FelixSchlang says Booster 23 is expected to begin a second round of cryogenic testing at Massey's, where it sat alongside Ship 42.

    @FelixSchlang X post Counts with a second source

    c-0965be309f20

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

    c-3a07c5d16bc0

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

    c-c65eaa010472

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

    c-eec7f163ae4b

  6. 2026-10-26 UNCONFIRMED note about S43

    Ship 43 left the production site heading to Pad 2 under a Production to Pad road delay; NASASpaceflight and lewisknaggs42 say it is likely for chopstick catch tests.

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

    c-fd74ff2412b0

  7. 2026-10-26 UNCONFIRMED note at MB2 about S43

    Ship 43 was lifted from the cryo stand at Mega Bay 2 as Booster 22 returned, and the cryo stand then rolled back to Sanchez.

    @VickiCocks15 X post Counts with a second source

    c-c6eb3bcc838c

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

    c-a78aa194f37e

  9. 2026-10-23 UNCONFIRMED note at MAS about S43

    Blobifie says Ship 43 completed two cryogenic proof tests at Massey's on 23 Oct.

    @Blobifie X post Counts with a second source

    c-c039a9b72031

  10. 2026-10-23 cryo S43 at MAS

    Ship 43 started its first cryogenic proof test at Massey's on the evening of 23 Oct.

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

    c-92e826155d19

  11. 2026-10-22 UNCONFIRMED note at MB2 about S43

    VickiCocks15 reports the ship thrust sim stand moved into Mega Bay 2 overnight and Ship 43 was loaded onto it before leaving for Massey's for cryo testing.

    @VickiCocks15 X post Counts with a second source

    c-f40a40a79002

  12. 2026-10-22 UNCONFIRMED note about S43

    VickiCocks15 says it is possible, though impossible to tell, that Ship 43 was proof tested with ambient temperature gas; after farm vents, testing moved to test tank S39.1, where frost was just visible, its 17th test.

    @VickiCocks15 X post Counts with a second source

    c-6c3228dba175

  13. 2026-10-22 UNCONFIRMED note at MAS about S43

    Ship 43 moved its flaps at Massey's.

    @VickiCocks15 X post Counts with a second source

    c-4edb697fe1fb

  14. 2026-10-18 note about B23

    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.

    @TrackingTheSB X post Confirms alone

    c-59ce046b7e06

  15. 2026-10-18 UNCONFIRMED note at MB1 about B23

    NSF (18 Oct): Booster 23's cryo testing at Massey's concluded over the weekend with a Sunday morning trip back to Mega Bay 1 for engine installation.

    NASASpaceflight Web page Counts with a second source

    c-386222a51fc6

  16. 2026-10-15 UNCONFIRMED note at MAS about B23

    Aerial view shows Booster 23 at Massey's.

    @RGVaerialphotos X post Counts with a second source

    c-07048f4196b6

  17. 2026-10-15 cryo B23 at MAS

    Booster 23 underwent its first cryogenic proof test at Massey's.

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

    c-1bef3acffd6a

  18. 2026-10-09 UNCONFIRMED note at MB2 about S43

    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.

    NASASpaceflight Web page Counts with a second source

    c-e4ebe3ab392b

  19. 2026-09-25 note about B23

    Booster 23 CH4 tank stack was stacked on top of its aft section, completing major construction; outfitting comes next, ahead of cryo proof.

    @TrackingTheSB X post Confirms alone

    c-722494cd2662

  20. 2026-09-21 note about B23

    Booster 23 received its F3:4 section, completing the liquid methane tank section. The post does not name the bay.

    @TrackingTheSB X post Confirms alone

    c-298cd3aa0b22

  21. 2026-09-20 note about B23

    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.

    @TrackingTheSB X post Confirms alone

    c-95b9e3ec757d

Flight notes

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

  1. 2026-11-16 note about F16

    Elon Musk says Starship V4 will be about 70 m long, roughly a 40% length increase allowing more than 60% more propellant load, with the engine count raised to 9 by adding 3 Raptor Vacuum engines, and the V4 engines will be higher thrust.

    @elonmusk X post Confirms alone

    c-e2161433021d

  2. 2026-10-25 UNCONFIRMED note at GB-FL about F16

    NSF (25 Oct): SpaceX is pushing to launch Flight 16 from LC-39A as soon as possible, and is preparing the Roberts Road Gigabay to host Booster 23 and Ship 43, both of which have completed cryo proof testing, once they ship from Starbase.

    NASASpaceflight Web page Counts with a second source @NASASpaceflight X post Counts with a second source

    c-2b360efbb778

  3. 2026-10-25 UNCONFIRMED note at 39A about F16

    TrackingTheSB weekly: LC-39A is in final testing ahead of its first vehicle, set for Flight 16; the presumed Flight 16 pairing is Booster 23 and Ship 43.

    @TrackingTheSB X post Confirms alone

    c-ac08e1d70645

  4. 2026-10-23 UNCONFIRMED note about F16

    NSF: Flight 16's vehicles are expected to head to KSC for a launch from LC-39A.

    @NASASpaceflight X post Counts with a second source

    c-d37a128ac7fa

  5. 2026-10-18 UNCONFIRMED note about F16

    NSF (18 Oct): Flight 16 is currently aimed for December and could become the first Starship launch from LC-39A. NSF says current activity points to Booster 23 and Ship 43 as the likely vehicles. If that campaign proceeds, each vehicle would need to be shipped individually to the KSC turn basin aboard You'll Thank Me Later and then roll to Roberts Road before moving to 39A for testing.

    NASASpaceflight Web page Counts with a second source

    c-ff4214a0fb49