
AFalcon 9 first-stage booster is a reusable rocketbooster used on theFalcon 9 andFalcon Heavy orbitallaunch vehicles manufactured bySpaceX. The manufacture of first-stage booster constitutes about 60% of the launch price of a single expended Falcon 9[1] (and three of them over 80% of the launch price of an expended Falcon Heavy), which led SpaceX to develop aprogram dedicated to recovery and reuse of these boosters. After multiple attempts, some as early as 2010, at controlling the re-entry of the first stage after its separation from the second stage, the first successful controlled landing of a first stage occurred on December 22, 2015, on the first flight of theFull Thrust version. Since then, Falcon 9 first-stage boosters have been landed and recovered 523 times out of 536 attempts, includingsynchronized recoveries of the side-boosters of most Falcon Heavy flights.
In total 51 recovered boosters have been refurbished and subsequently flown at least a second time, with a record of 31 launches and landings carried out by a single booster. SpaceX intentionally limited Block 3 and Block 4 boosters to flying only two missions each,[2][3] but the company indicated in 2018 that they expected the Block 5 versions to achieve at least ten flights, with only minor refurbishment between missions. The ten flight milestone was first achieved by Booster B1051 on the Starlink 27 mission in 2021.[4] The twenty flight milestone was first achieved by Booster B1062 on the Starlink Group 6-49 mission in 2024. The thirty flight milestone was first achieved by Booster B1067 on the Starlink Group 10-11 mission in 2025.
All boosters in Block 4 and earlier have been retired, expended, or lost. The last flight of a Block 4 booster was in June 2018. Since then all boosters in the active fleet are Block 5.
Booster names are a B followed by a four-digit number. The first Falcon 9 version, v1.0, had boosters B0001 to B0007. All following boosters were numbered sequentially starting at B1001, the number 1 standing for first-stage booster.
SpaceX attempted parachute of the Falcon 9 v1.0 first stage on flights 1 and 2, however on both attempts the boosters disintegrated on re-entry, and the plans were abandoned in favor of propulsive landings. Boosters B0002 (Grasshopper) and B1002 (F9R Dev1) were modified to make short propulsive hops at test sites to demonstrate landing technologies, and were not used on orbital missions. Three boosters successfully made soft ocean touchdowns on orbital flights but were not recovered.
| S/N[a] | Version | Launch date (UTC)[6] | Flight No.[b] | Payload[c] | Launch (pad) | Landing | Fate |
|---|---|---|---|---|---|---|---|
| B0001 | v1.0 test | Manufactured in 2007[7] | — | — | — | — | — |
| B0002 | v1.0 test | September 2012–October 2013 (8 test flights)[8][9] | — | — | Suborbital | 8 test landings achieved[10] | Retired[11] |
| B0003 | v1.0 | June 4, 2010 | F9-001 | Dragon Spacecraft Qualification Unit | Success (SLC‑40)[12] | Failure (parachute) | Destroyed[13] |
| B0004 | v1.0 | December 8, 2010 | F9-002 | COTS Demo Flight 1 (Dragon C101) | Success (SLC‑40) | Failure (parachute) | Destroyed[14] |
| B0005 | v1.0 | May 22, 2012 | F9-003 | COTS Demo Flight 2 (Dragon C102) | Success (SLC‑40) | No attempt | Expended |
| B0006 | v1.0 | October 8, 2012 | F9-004 | CRS-1 (Dragon C103) | Partial success (SLC‑40)[15] | No attempt | Expended |
| B0007 | v1.0 | March 1, 2013 | F9-005 | CRS-2 (Dragon C104) | Success (SLC‑40) | No attempt | Expended |
| B1001 | v1.1 test | Manufactured in 2012[16] | — | — | — | — | — |
| B1002 | v1.1 test | April–August 2014 (5 test flights)[17][18] | — | — | Suborbital | 4 test landings achieved[10] | Destroyed[19] |
| B1003 | v1.1 | September 29, 2013 | F9-006 | CASSIOPE | Success (SLC‑4E) | No attempt | Expended |
| B1004 | v1.1 | December 3, 2013 | F9-007 | SES-8 | Success (SLC‑40) | No attempt | Expended[20] |
| B1005 | v1.1 | January 6, 2014 | F9-008 | Thaicom 6 | Success (SLC‑40) | No attempt | Expended[20] |
| B1006 | v1.1 | April 18, 2014 | F9-009 | CRS-3 (Dragon C105) | Success (SLC‑40) | No attempt | Expended |
| B1007 | v1.1 | July 14, 2014 | F9-010 | Orbcomm OG2 × 6 | Success (SLC‑40) | No attempt | Expended |
| B1008 | v1.1 | August 5, 2014 | F9-011 | AsiaSat 8 | Success (SLC‑40) | No attempt | Expended[21] |
| B1009 | v1.1 test | Manufactured in 2014[22] | — | — | — | — | Never completed[23] |
| B1010 | v1.1 | September 21, 2014 | F9-013 | CRS-4 (Dragon C106.1) | Success (SLC‑40) | No attempt | Expended |
| B1011 | v1.1 | September 7, 2014 | F9-012 | AsiaSat 6 / Thaicom 7 | Success (SLC‑40) | No attempt | Expended[20] |
| B1012 | v1.1 | January 10, 2015 | F9-014 | CRS-5 (Dragon C107) | Success (SLC‑40) | Failure (JRTI) | Destroyed |
| B1013 | v1.1 | February 11, 2015 | F9-015 | DSCOVR | Success (SLC‑40) | No attempt | Expended |
| B1014 | v1.1 | March 2, 2015 | F9-016 | ABS-3A /Eutelsat 115 West B | Success (SLC‑40) | No attempt | Expended[20] |
| B1015 | v1.1 | April 14, 2015 | F9-017 | CRS-6 (Dragon C108.1) | Success (SLC‑40) | Failure (JRTI) | Destroyed |
| B1016 | v1.1 | April 27, 2015 | F9-018 | TürkmenÄlem 52°E / MonacoSAT | Success (SLC‑40) | No attempt | Expended[20] |
| B1017 | v1.1 | January 17, 2016 | F9-021 | Jason-3 | Success (SLC‑4E) | Failure (JRTI) | Destroyed |
| B1018 | v1.1 | June 28, 2015 | F9-019 | CRS-7 (Dragon C109) | Failure (SLC‑40) | Precluded | Destroyed |
Falcon 9 Full Thrust (version 1.2 / Block 3) was the first version of the Falcon 9 to successfully land. Changes included a larger fuel tank, uprated engines andsupercooled propellant and oxidizer to increase performance. Block 3 and Block 4 are found in this list while the active Block 5 is listed separately. Block 4 was a test version that included new hardware such astitaniumgrid fins later carried over to the current Block 5. Flights of all Falcon 9 rockets up to Block 4 were limited to 2 flights only, with a total of 14 second flights of these variants. The boosters were either retired or expended after that second launch.
Boosters B1023 and B1025 were originally Falcon 9 boosters which were converted to Falcon Heavy side boosters for theFalcon Heavy test flight.
| S/N | Version | Launch date (UTC)[6] | Flight No.[a] | Turnaround | Payload[b] | Launch (pad) | Landing (location) | Fate |
|---|---|---|---|---|---|---|---|---|
| B1019 | FT | December 22, 2015 | F9-020 | — | Orbcomm OG2 × 11 | Success (SLC‑40) | Success (LZ‑1)[24] | Retired On display atSpaceX headquarters[25][26] |
| B1020 | FT | March 4, 2016 | F9-022 | — | SES-9 | Success (SLC‑40) | Failure (OCISLY) | Destroyed[27] |
| B1021 | FT | April 8, 2016 | F9-023 | — | CRS-8 (Dragon C110.1)[28] | Success (SLC‑40) | Success (OCISLY) | Retired[29] On display atDish Network headquarters[30][31] |
| March 30, 2017 | F9-032 | 356 days | SES-10[28] | Success (LC‑39A) | Success (OCISLY)[32][33] | |||
| B1022 | FT | May 6, 2016 | F9-024 | — | JCSAT-14 | Success (SLC‑40) | Success (OCISLY) | Retired |
| B1023 | FT | May 27, 2016 | F9-025 | — | Thaicom 8[34] | Success (SLC‑40) | Success (OCISLY)[35] | Retired[36] On display atKennedy Space Center Visitor Complex[37][38] |
| FH side | February 6, 2018 | FH-001 | 620 days | Tesla Roadster | Success (LC‑39A) | Success (LZ‑1) | ||
| B1024 | FT | June 15, 2016 | F9-026 | — | ABS-2A /Eutelsat 117 West B | Success (SLC‑40) | Failure (OCISLY) | Destroyed[39] |
| B1025 | FT | July 18, 2016 | F9-027 | — | CRS-9 (Dragon C111.1)[40] | Success (SLC‑40) | Success (LZ‑1) | Retired[36] |
| FH side | February 6, 2018 | FH-001 | 568 days | Tesla Roadster | Success (LC‑39A) | Success (LZ‑2) | ||
| B1026 | FT | August 14, 2016 | F9-028 | — | JCSAT-16 | Success (SLC‑40) | Success (OCISLY)[41] | Retired[36] |
| B1027 | FH test | Manufactured in 2016[42][43] | — | — | — | — | — | — |
| B1028 | FT | September 3, 2016[44] | —[c] | — | AMOS-6 | Precluded[46] | Precluded | Destroyed in launch pad explosion[46] |
| B1029 | FT | January 14, 2017 | F9-029 | — | Iridium NEXT × 10 (NEXT-1)[47] | Success (SLC‑4E) | Success (JRTI) | Retired[36] |
| June 23, 2017 | F9-036 | 160 days | BulgariaSat-1[48] | Success (LC‑39A) | Success (OCISLY)[49] | |||
| B1030 | FT | March 16, 2017 | F9-031 | — | EchoStar 23[50] | Success (LC‑39A) | No attempt[51] | Expended |
| B1031 | FT | February 19, 2017 | F9-030 | — | CRS-10 (Dragon C112.1)[52] | Success (LC‑39A) | Success (LZ‑1)[53] | Retired[36] |
| October 11, 2017 | F9-043 | 234 days | SES-11[53] | Success (LC‑39A) | Success (OCISLY) | |||
| B1032 | FT | May 1, 2017 | F9-033 | — | USA-276 (NROL-76)[54] | Success (LC‑39A) | Success (LZ‑1) | Expended[55] |
| January 31, 2018 | F9-048 | 275 days | GovSat-1 / SES-16[56] | Success (SLC‑40) | No attempt[d] | |||
| B1033 | FH core | February 6, 2018 | FH-001 | — | Tesla Roadster | Success (LC‑39A) | Failure (OCISLY) | Destroyed[57] |
| B1034 | FT | May 15, 2017 | F9-034 | — | Inmarsat-5 F4[58] | Success (LC‑39A) | No attempt[51] | Expended |
| B1035 | FT | June 3, 2017 | F9-035 | — | CRS-11 (Dragon C106.2)[59] | Success (LC‑39A) | Success (LZ‑1) | Retired[36] On display atSpace Center Houston[60][61] |
| December 15, 2017 | F9-045 | 195 days | CRS-13 (Dragon C108.2)[62] | Success (SLC‑40) | Success (LZ‑1)[63] | |||
| B1036 | FT | June 25, 2017 | F9-037 | — | Iridium NEXT × 10 (NEXT-2)[64] | Success (SLC‑4E) | Success (JRTI) | Expended |
| December 23, 2017 | F9-046 | 181 days | Iridium NEXT × 10 (NEXT-4)[65] | Success (SLC‑4E) | No attempt | |||
| B1037 | FT | July 5, 2017 | F9-038 | — | Intelsat 35e[66] | Success (LC‑39A) | No attempt[51] | Expended |
| B1038 | FT | August 24, 2017 | F9-040 | — | Formosat-5[67] | Success (SLC‑4E) | Success (JRTI) | Expended |
| February 22, 2018 | F9-049 | 182 days | Paz | Success (SLC‑4E) | No attempt[51] | |||
| B1039 | F9 B4 | August 14, 2017 | F9-039 | — | CRS-12 (Dragon C113.1)[68] | Success (LC‑39A) | Success (LZ‑1) | Expended |
| April 2, 2018 | F9-052 | 231 days | CRS-14 (Dragon C110.2)[69] | Success (SLC‑40) | No attempt[70] | |||
| B1040 | F9 B4 | September 7, 2017 | F9-041 | — | Boeing X-37B (OTV-5)[71] | Success (LC‑39A) | Success (LZ‑1) | Expended |
| June 4, 2018 | F9-056 | 270 days | SES-12[72] | Success (SLC‑40)[73] | No attempt[51] | |||
| B1041 | F9 B4 | October 9, 2017 | F9-042 | — | Iridium NEXT × 10 (NEXT-3)[74][75] | Success (SLC‑4E) | Success (JRTI) | Expended |
| March 30, 2018 | F9-051 | 172 days | Iridium NEXT × 10 (NEXT-5)[76][77] | Success (SLC‑4E) | No attempt[76] | |||
| B1042 | F9 B4 | October 30, 2017 | F9-044 | — | Koreasat 5A[78] | Success (LC‑39A) | Success (OCISLY) | Retired[3] |
| B1043 | F9 B4 | January 8, 2018 | F9-047 | — | Zuma[79] | Success (SLC‑40)[80] | Success (LZ‑1) | Expended |
| May 22, 2018 | F9-055 | 134 days | Iridium NEXT × 5 (NEXT-6) /GRACE-FO × 2 | Success (SLC‑4E) | No attempt[51] | |||
| B1044 | F9 B4 | March 6, 2018 | F9-050 | — | Hispasat 30W-6 | Success (SLC‑40) | No attempt[69] | Expended |
| B1045 | F9 B4 | April 18, 2018 | F9-053 | — | TESS[69] | Success (SLC‑40) | Success (OCISLY) | Expended |
| June 29, 2018 | F9-057 | 72 days | CRS-15 (Dragon C111.2)[3] | Success (SLC‑40)[81] | No attempt[3] | |||
There are three booster types: Falcon 9 (F9), Falcon Heavy core (FH core) boosters, and Falcon Heavy side (FH side) boosters. Falcon 9 and Falcon Heavy side boosters are reconfigurable to each other. A Falcon Heavy core booster is manufactured with structural supports for the side boosters and cannot be converted to Falcon Heavy side booster, although it can be converted to a lower performance Falcon 9 core booster. The interstage mounting hardware was changed after B1056. The newer interstage design features fewer pins holding the interstage on, reducing the amount of work needed to convert a Falcon 9 booster to a Falcon Heavy side booster.[82]
Block 5 is the latest iteration of the Falcon 9 and Falcon Heavy boosters. Changes include a strongerheat shield, upgraded engines, newcarbon composite sections (landing legs, engine sections,raceways,RCS thrusters and interstage), retractable landing legs, titanium grid fins, and other additions that simplify refurbishment and allow for easier reusability.[citation needed]
Block 5 boosters were initially certified for 10 launches[83] which was increased to 15. A "deep-dive" examination has been performed onFalcon 9 B1058 and B1060 after their 15th flight,[84] and SpaceX certified Falcon 9 boosters for 20 missions. SpaceX has further increased the Falcon re-flight certification to 40 flights per booster, since 20 flights of some boosters are reached.[85][86]
B1058, first launched on May 30, 2020 (Crew Dragon Demo-2), was the only booster with NASA logos. On September 11, 2022, during a Starlink mission, it became the first to complete fourteen launches and landings to become the fleet leader. With another 5 Starlink missions, B1058 achieved 15, 16, 17, 18 & 19 launches and landings, the first to do so.B1062 had been the first to achieve 20th, 21st, 22nd & 23rd launches and landings of a booster.Guinness World Records holderB1067 is the current fleet leader after completing 24th, 25th, 26th, 27th, 28th, 29th, 30th, and 31st launch & landings, the first to do so.[87] Amongst all B5 boosters, B1058 holds the record for most spacecraft (869) launched to orbit, while the record for most spacecraft mass launched to orbit by a single booster is held byB1069 (401,140 kg (884,360 lb)).B1063 is currently and of all time, the oldest surviving booster in the Falcon 9 fleet.
As of 24 October 2025[update], SpaceX has put into service a total of 52 new B5 boosters, of which 30 have been destroyed (21 have been expended, six have been lost due to failed landings, and three have been lost during recovery).
| S/N | Type | Launches | Launch date (UTC)[6] | Flight No.[a] | Turnaround time | Payload[b] | Launch (pad) | Landing (location) | Fate |
|---|---|---|---|---|---|---|---|---|---|
| B1046 | F9 B5 | 4 | May 11, 2018 | F9-054 | — | Bangabandhu-1[88] | Success (LC‑39A) | Success (OCISLY) | Intentionally destroyed in Crew Dragon In-Flight Abort Test |
| August 7, 2018 | F9-060 | 88 days | Telkom-4Merah Putih[89] | Success (SLC‑40) | Success (OCISLY) | ||||
| December 3, 2018 | F9-064 | 118 days | SHERPA (SSO-A) (65 Sats)[88][90] | Success (SLC‑4E) | Success (JRTI) | ||||
| January 19, 2020[91] | F9-079 | 412 days | In-Flight Abort Test (Dragon C205)[92] | Success (LC‑39A) | No attempt | ||||
| B1047 | F9 B5 | 3 | July 22, 2018 | F9-058 | — | Telstar 19V[93] | Success (SLC‑40) | Success (OCISLY) | Expended[94] |
| November 15, 2018 | F9-063 | 116 days | Es'hail 2[95] | Success (LC‑39A) | Success (OCISLY) | ||||
| August 6, 2019[96] | F9-074 | 263 days | AMOS-17[97] | Success (SLC‑40) | No attempt | ||||
| B1048 | F9 B5 | 5 | July 25, 2018 | F9-059 | — | Iridium NEXT × 10 (NEXT-7)[93] | Success (SLC‑4E) | Success (JRTI) | Destroyed in landing failure[c] |
| October 8, 2018 | F9-062 | 75 days | SAOCOM 1A[98] | Success (SLC‑4E) | Success (LZ‑4) | ||||
| February 22, 2019 | F9-068 | 137 days | Nusantara Satu /Beresheet[99][100] | Success (SLC‑40) | Success (OCISLY) | ||||
| November 11, 2019 | F9-075 | 262 days | Starlink × 60 (v1.0 L1) | Success (SLC‑40) | Success (OCISLY) | ||||
| March 18, 2020 | F9-083 | 128 days | Starlink × 60 (v1.0 L5)[101] | Success (LC‑39A) | Failure (OCISLY) | ||||
| B1049 | F9 B5[d] | 11 | September 10, 2018 | F9-061 | — | Telstar 18V /Apstar 5C[104] | Success (SLC‑40) | Success (OCISLY) | Expended |
| January 11, 2019 | F9-067 | 123 days | Iridium NEXT × 10 (NEXT-8)[105] | Success (SLC‑4E) | Success (JRTI) | ||||
| May 24, 2019 | F9-071 | 133 days | Starlink × 60 (v0.9)[106] | Success (SLC‑40) | Success (OCISLY) | ||||
| January 7, 2020 | F9-078 | 228 days | Starlink × 60 (v1.0 L2)[107] | Success (SLC‑40) | Success (OCISLY) | ||||
| June 4, 2020 | F9-086 | 149 days | Starlink × 60 (v1.0 L7)[108] | Success (SLC‑40) | Success (JRTI) | ||||
| August 18, 2020 | F9-091 | 75 days | Starlink × 58 (v1.0 L10) + Skysat 19-21[109] | Success (SLC‑40) | Success (OCISLY) | ||||
| November 25, 2020 | F9-100 | 99 days | Starlink × 60 (v1.0 L15)[110] | Success (SLC‑40) | Success (OCISLY) | ||||
| March 4, 2021 | F9-109 | 99 days | Starlink × 60 (v1.0 L17)[111] | Success (LC‑39A) | Success (OCISLY) | ||||
| May 4, 2021[112] | F9-116 | 61 days | Starlink × 60 (v1.0 L25) | Success (LC‑39A) | Success (OCISLY) | ||||
| September 14, 2021 | F9-125 | 133 days | Starlink × 51 (Group 2-1) | Success (SLC‑4E) | Success (OCISLY) | ||||
| November 23, 2022 | F9-186 | 435 days | Eutelsat 10B | Success (SLC‑40) | No attempt | ||||
| B1050 | F9 B5 | 1 | December 5, 2018 | F9-065 | — | CRS-16 (Dragon C112.2)[88] | Success (SLC‑40) | Failure (LZ‑1) | Landing attempt aborted to ocean; scrapped[e] |
| B1051 | F9 B5 | 14 | March 2, 2019[113] | F9-069 | — | Demo-1 (Dragon C204) | Success (LC‑39A) | Success (OCISLY) | Expended |
| June 12, 2019 | F9-072 | 102 days | RCM × 3[114] | Success (SLC‑4E) | Success (LZ‑4) | ||||
| January 29, 2020 | F9-080 | 231 days | Starlink × 60 (v1.0 L3) | Success (SLC‑40) | Success (OCISLY) | ||||
| April 22, 2020 | F9-084 | 84 days | Starlink × 60 (v1.0 L6)[115] | Success (LC‑39A) | Success (OCISLY) | ||||
| August 7, 2020 | F9-090 | 107 days | Starlink × 57 (v1.0 L9) | Success (LC‑39A) | Success (OCISLY) | ||||
| October 18, 2020 | F9-095 | 72 days | Starlink × 60 (v1.0 L13) | Success (LC‑39A) | Success (OCISLY) | ||||
| December 13, 2020 | F9-102 | 56 days | SXM 7[116] | Success (SLC‑40) | Success (JRTI) | ||||
| January 20, 2021 | F9-105 | 38 days | Starlink × 60 (v1.0 L16)[117] | Success (LC‑39A) | Success (JRTI) | ||||
| March 14, 2021 | F9-111 | 53 days | Starlink × 60 (v1.0 L21)[118] | Success (LC‑39A) | Success (OCISLY) | ||||
| May 9, 2021[119] | F9-117 | 56 days | Starlink × 60 (v1.0 L27) | Success (SLC‑40) | Success (JRTI) | ||||
| December 18, 2021[120][121] | F9-132 | 228 days | Starlink × 52 (Group 4-4)[122] | Success (SLC‑4E) | Success (OCISLY) | ||||
| March 19, 2022[120] | F9-145 | 91 days | Starlink × 53 (Group 4-12) | Success (SLC‑40) | Success (JRTI) | ||||
| July 17, 2022 | F9-165 | 120 days | Starlink × 53 (Group 4-22) | Success (SLC‑40) | Success (JRTI) | ||||
| November 12, 2022 | F9-185 | 118 days | Galaxy 31 & 32[123] | Success (SLC‑40) | No attempt | ||||
| B1052 | FH side | 8 | April 11, 2019 | FH-002 | — | Arabsat-6A[114] | Success (LC‑39A) | Success (LZ‑1)[124] | Expended |
| June 25, 2019 | FH-003 | 75 days | COSMIC-2 (STP-2)[114] | Success (LC‑39A) | Success (LZ‑2)[124] | ||||
| F9 B5[f] | January 31, 2022 | F9-138 | 951 days | CSG-2[126] | Success (SLC‑40) | Success (LZ‑1) | |||
| March 9, 2022 | F9-144 | 37 days | Starlink × 48 (Group 4-10)[127] | Success (SLC‑40) | Success (ASOG) | ||||
| May 18, 2022 | F9-155 | 70 days | Starlink × 53 (Group 4-18)[128] | Success (LC‑39A) | Success (ASOG) | ||||
| August 4, 2022 | F9-168 | 78 days | Danuri (KPLO)[129] | Success (SLC‑40) | Success (JRTI) | ||||
| September 5, 2022 | F9-174 | 32 days | Starlink × 51 (Group 4-20) + Varuna-TDM[130] | Success (SLC‑40) | Success (JRTI) | ||||
| FH side | May 1, 2023[131] | FH-006 | 238 days | ViaSat-3 Americas[131] | Success (LC‑39A) | No attempt[132] | |||
| B1053 | FH side | 3 | April 11, 2019 | FH-002 | — | Arabsat-6A[114] | Success (LC‑39A) | Success (LZ‑2)[124] | Expended |
| June 25, 2019 | FH-003 | 75 days | COSMIC-2 (STP-2)[114] | Success (LC‑39A) | Success (LZ‑1)[124] | ||||
| May 1, 2023[131] | FH-006 | 1406 days | ViaSat-3 Americas[133][131] | Success (LC‑39A) | No attempt[132] | ||||
| B1054 | F9 B5 | 1 | December 23, 2018 | F9-066 | — | GPS III SV01[134] | Success (SLC‑40) | No attempt[135] | Expended |
| B1055 | FH core | 1 | April 11, 2019 | FH-002 | — | Arabsat-6A | Success (LC‑39A) | Success[g] (OCISLY) | Destroyed during recovery[g] |
| B1056 | F9 B5 | 4 | May 4, 2019 | F9-070 | — | CRS-17 (Dragon C113.2) | Success (SLC‑40) | Success (OCISLY) | Sunk after unintentional water landing[137] |
| July 25, 2019 | F9-073 | 82 days | CRS-18 (Dragon C108.3)[138] | Success (SLC‑40) | Success (LZ‑1) | ||||
| December 17, 2019 | F9-077 | 146 days | JCSAT-18 / Kacific-1[139] | Success (SLC‑40) | Success (OCISLY) | ||||
| February 17, 2020 | F9-081 | 62 days | Starlink × 60 (v1.0 L4)[140] | Success (SLC‑40) | Failure (OCISLY) | ||||
| B1057 | FH core | 1 | June 25, 2019 | FH-003 | — | COSMIC-2 (STP-2)[139] | Success (LC‑39A) | Failure (OCISLY) | Destroyed in landing failure |
| B1058 | F9 B5 | 19 | May 30, 2020[141] | F9-085 | — | Demo-2 (Dragon C206‑1Endeavour)[142] | Success (LC‑39A) | Success (OCISLY) | Destroyed during recovery[h] |
| July 20, 2020 | F9-089 | 51 days | ANASIS-II | Success (SLC‑40) | Success (JRTI) | ||||
| October 6, 2020[144] | F9-094 | 78 days | Starlink × 60 (v1.0 L12) | Success (LC‑39A) | Success (OCISLY) | ||||
| December 6, 2020[145] | F9-101 | 60 days | CRS-21 (Dragon C208‑1) | Success (LC‑39A) | Success (OCISLY) | ||||
| January 24, 2021 | F9-106 | 49 days | Transporter-1 (143 Sats)[146] | Success (SLC‑40) | Success (OCISLY) | ||||
| March 11, 2021 | F9-110 | 46 days | Starlink × 60 (v1.0 L20)[147] | Success (SLC‑40) | Success (JRTI) | ||||
| April 7, 2021 | F9-113 | 27 days | Starlink × 60 (v1.0 L23) | Success (SLC‑40) | Success (OCISLY) | ||||
| May 15, 2021 | F9-118 | 38 days | Starlink × 52 (v1.0 L26) + Rideshare | Success (LC‑39A) | Success (OCISLY) | ||||
| November 13, 2021[148] | F9-128 | 182 days | Starlink × 53 (Group 4-1)[149][150] | Success (SLC‑40) | Success (JRTI) | ||||
| January 13, 2022 | F9-136 | 61 days | Transporter-3 (105 Sats)[151] | Success (SLC‑40) | Success (LZ‑1) | ||||
| February 21, 2022 | F9-141 | 39 days | Starlink × 46 (Group 4-8) | Success (SLC‑40) | Success (ASOG) | ||||
| May 6, 2022 | F9-152 | 73 days | Starlink × 53 (Group 4-17) | Success (LC‑39A) | Success (ASOG) | ||||
| July 7, 2022 | F9-162 | 62 days | Starlink × 53 (Group 4-21)[152] | Success (SLC‑40) | Success (JRTI) | ||||
| September 11, 2022 | F9-175 | 66 days | Starlink × 34 (Group 4-2) +BlueWalker 3[153] | Success (LC‑39A) | Success (ASOG) | ||||
| December 17, 2022 | F9-192 | 97 days | Starlink × 54 (Group 4-37)[154] | Success (LC‑39A) | Success (JRTI) | ||||
| July 10, 2023 | F9-238 | 205 days | Starlink v2 × 22 (Group 6-5) | Success (SLC‑40) | Success (JRTI) | ||||
| September 20, 2023 | F9-257 | 72 days | Starlink v2 × 22 (Group 6-17) | Success (SLC‑40) | Success (ASOG) | ||||
| November 4, 2023 | F9-269 | 45 days | Starlink v2 × 23 (Group 6-26) | Success (SLC‑40) | Success (ASOG) | ||||
| December 23, 2023 | F9-283 | 49 days | Starlink v2 × 23 (Group 6-32) | Success (SLC‑40) | Success[h] (JRTI) | ||||
| B1059 | F9 B5 | 6 | December 5, 2019 | F9-076 | — | CRS-19 (Dragon C106.3) | Success (SLC‑40) | Success (OCISLY) | Destroyed in landing failure[i] |
| March 7, 2020[155] | F9-082 | 93 days | CRS-20 (Dragon C112.3) | Success (SLC‑40) | Success (LZ‑1) | ||||
| June 13, 2020 | F9-087 | 98 days | Starlink × 58 (v1.0 L8)+ Skysat 16-18 | Success (SLC‑40) | Success (OCISLY) | ||||
| August 30, 2020 | F9-092 | 78 days | SAOCOM 1B+ Rideshare[109] | Success (SLC‑40) | Success (LZ‑1) | ||||
| December 19, 2020 | F9-103 | 111 days | NROL-108[156] | Success (LC‑39A) | Success (LZ‑1) | ||||
| February 16, 2021 | F9-108 | 59 days | Starlink × 60 (v1.0 L19)[157] | Success (SLC‑40) | Failure (OCISLY) | ||||
| B1060 | F9 B5 | 20 | June 30, 2020[158] | F9-088 | — | GPS III SV03 | Success (SLC‑40) | Success (JRTI) | Expended |
| September 3, 2020 | F9-093 | 65 days | Starlink × 60 (v1.0 L11)[159] | Success (LC‑39A) | Success (OCISLY) | ||||
| October 24, 2020 | F9-096 | 51 days | Starlink × 60 (v1.0 L14) | Success (SLC‑40) | Success (JRTI) | ||||
| January 8, 2021 | F9-104 | 76 days | Türksat 5A[160] | Success (SLC‑40) | Success (JRTI) | ||||
| February 4, 2021 | F9-107 | 27 days | Starlink × 60 (v1.0 L18)[161] | Success (SLC‑40) | Success (OCISLY) | ||||
| March 24, 2021 | F9-112 | 48 days | Starlink × 60 (v1.0 L22)[162] | Success (SLC‑40) | Success (OCISLY) | ||||
| April 29, 2021 | F9-115 | 36 days | Starlink × 60 (v1.0 L24)[163] | Success (SLC‑40) | Success (JRTI) | ||||
| June 30, 2021 | F9-123 | 62 days | Transporter-2 (88 Sats)[164] | Success (SLC‑40) | Success (LZ‑1) | ||||
| December 2, 2021 | F9-130 | 155 days | Starlink × 48 (Group 4-3) + BlackSky Global 12-13 | Success (SLC‑40) | Success (ASOG) | ||||
| January 19, 2022 | F9-137 | 48 days | Starlink × 49 (Group 4-6) | Success (LC‑39A) | Success (ASOG) | ||||
| March 3, 2022 | F9-143 | 43 days | Starlink × 47 (Group 4-9) | Success (LC‑39A) | Success (JRTI) | ||||
| April 21, 2022 | F9-149 | 49 days | Starlink × 53 (Group 4-14) | Success (SLC‑40) | Success (JRTI) | ||||
| June 17, 2022 | F9-158 | 57 days | Starlink × 53 (Group 4-19)[165] | Success (LC‑39A) | Success (ASOG) | ||||
| October 8, 2022 | F9-180 | 113 days | Galaxy 33 & 34[166] | Success (SLC‑40) | Success (ASOG) | ||||
| January 3, 2023 | F9-195 | 87 days | Transporter-6 (144 Sats) | Success (SLC‑40) | Success (LZ‑1) | ||||
| July 16, 2023 | F9-239 | 194 days | Starlink × 54 (Group 5-15) | Success (SLC‑40) | Success (ASOG) | ||||
| September 24, 2023 | F9-258 | 70 days | Starlink v2 × 22 (Group 6-18) | Success (SLC‑40) | Success (JRTI) | ||||
| February 15, 2024 | F9-299 | 144 days | IM-1 (Nova-C)Odysseus lander | Success (LC‑39A) | Success (LZ‑1) | ||||
| March 24, 2024 | F9-313 | 38 days | Starlink v2 × 23 (Group 6-42) | Success (LC‑39A) | Success (JRTI) | ||||
| April 28, 2024 | F9-327 | 35 days | GalileoFOC FM25 &FOC FM27[167] | Success (LC‑39A) | No attempt | ||||
| B1061 | F9 B5 | 23 | November 15, 2020[145] | F9-098 | — | Crew-1 (Dragon C207‑1Resilience) | Success (LC‑39A) | Success (JRTI) | Expended |
| April 23, 2021 | F9-114 | 159 days | Crew-2 (Dragon C206‑2Endeavour) | Success (LC‑39A) | Success (OCISLY) | ||||
| June 6, 2021 | F9-121 | 44 days | SXM-8[168] | Success (SLC‑40) | Success (JRTI) | ||||
| August 29, 2021 | F9-124 | 84 days | CRS-23 (Dragon C208‑2) | Success (LC‑39A) | Success (ASOG) | ||||
| December 9, 2021 | F9-131 | 102 days | IXPE | Success (LC‑39A) | Success (JRTI) | ||||
| February 3, 2022 | F9-140 | 56 days | Starlink × 49 (Group 4-7)[169] | Success (LC‑39A) | Success (ASOG) | ||||
| April 1, 2022 | F9-146 | 57 days | Transporter-4 (40 Sats) | Success (SLC‑40) | Success (JRTI) | ||||
| May 25, 2022 | F9-156 | 54 days | Transporter-5 (59 Sats)[170] | Success (SLC‑40) | Success (LZ‑1) | ||||
| June 19, 2022 | F9-160 | 25 days | Globalstar FM15+ Rideshare[171] | Success (SLC‑40) | Success (JRTI) | ||||
| August 12, 2022 | F9-170 | 54 days | Starlink × 46 (Group 3-3)[172] | Success (SLC‑4E) | Success (OCISLY) | ||||
| December 30, 2022 | F9-194 | 140 days | EROS-C3[173] | Success (SLC‑4E) | Success (LZ‑4) | ||||
| March 3, 2023 | F9-208 | 63 days | Starlink × 51 (Group 2-7)[174] | Success (SLC‑4E) | Success (OCISLY) | ||||
| April 27, 2023 | F9-219 | 55 days | Starlink × 46 (Group 3-5) | Success (SLC‑4E) | Success (OCISLY) | ||||
| May 31, 2023 | F9-228 | 34 days | Starlink × 52 (Group 2-10) | Success (SLC‑4E) | Success (OCISLY) | ||||
| August 22, 2023 | F9-248 | 83 days | Starlink v2 × 21 (Group 7-1) | Success (SLC‑4E) | Success (OCISLY) | ||||
| October 21, 2023 | F9-265 | 60 days | Starlink v2 × 21 (Group 7-5) | Success (SLC‑4E) | Success (OCISLY) | ||||
| December 1, 2023 | F9-278 | 41 days | 425 Project Flight 1 | Success (SLC‑4E) | Success (LZ‑4) | ||||
| January 14, 2024 | F9-289 | 44 days | Starlink v2 × 22 (Group 7-10) | Success (SLC‑4E) | Success (OCISLY) | ||||
| February 23, 2024 | F9-302 | 40 days | Starlink v2 × 22 (Group 7-15) | Success (SLC‑4E) | Success (OCISLY) | ||||
| May 2, 2024 | F9-329 | 69 days | WorldView Legion 1 & 2 | Success (SLC‑4E) | Success (LZ‑4) | ||||
| June 8, 2024 | F9-345 | 37 days | Starlink v2 × 20 (Group 8-8) | Success (SLC‑4E) | Success (OCISLY) | ||||
| August 12, 2024 | F9-362 | 65 days | ASBM × 2 | Success (SLC‑4E) | Success (OCISLY) | ||||
| October 7, 2024 | F9-379 | 56 days | Hera | Success (SLC‑40) | No attempt | ||||
| B1062 | F9 B5 | 23 | November 5, 2020[145] | F9-097 | — | GPS III SV04 | Success (SLC‑40) | Success (OCISLY) | Destroyed in landing failure |
| June 17, 2021[175] | F9-122 | 224 days | GPS III SV05 | Success (SLC‑40) | Success (JRTI) | ||||
| September 16, 2021[176] | F9-126 | 91 days | Inspiration4 (Dragon C207‑2Resilience) | Success (LC‑39A) | Success (JRTI) | ||||
| January 6, 2022 | F9-135 | 112 days | Starlink × 49 (Group 4-5)[177] | Success (LC‑39A) | Success (ASOG) | ||||
| April 8, 2022 | F9-147 | 92 days | Ax-1 (Dragon C206‑2Endeavour) | Success (LC‑39A) | Success (ASOG) | ||||
| April 29, 2022 | F9-151 | 21 days | Starlink × 53 (Group 4-16) | Success (SLC‑40) | Success (JRTI) | ||||
| June 8, 2022 | F9-157 | 40 days | Nilesat-301[178] | Success (SLC‑40) | Success (JRTI) | ||||
| July 24, 2022 | F9-167 | 46 days | Starlink × 53 (Group 4-25) | Success (LC‑39A) | Success (ASOG) | ||||
| August 19, 2022 | F9-171 | 26 days | Starlink × 53 (Group 4-27)[179] | Success (SLC‑40) | Success (ASOG) | ||||
| October 20, 2022 | F9-182 | 62 days | Starlink × 54 (Group 4-36)[180] | Success (SLC‑40) | Success (ASOG) | ||||
| December 28, 2022 | F9-193 | 69 days | Starlink × 54 (Group 5-1)[181] | Success (SLC‑40) | Success (ASOG) | ||||
| February 12, 2023 | F9-203 | 46 days | Starlink × 55 (Group 5-4)[182] | Success (SLC‑40) | Success (ASOG) | ||||
| March 9, 2023 | F9-209 | 25 days | OneWeb #17[183] | Success (SLC‑40) | Success (LZ‑1) | ||||
| May 27, 2023 | F9-227 | 79 days | ArabSat 7B (Badr-8) | Success (SLC‑40) | Success (JRTI) | ||||
| July 28, 2023 | F9-242 | 62 days | Starlink v2 × 22 (Group 6-7)[184] | Success (SLC‑40) | Success (ASOG) | ||||
| October 18, 2023 | F9-264 | 82 days | Starlink v2 × 22 (Group 6-23) | Success (SLC‑40) | Success (JRTI) | ||||
| November 28, 2023 | F9-277 | 41 days | Starlink v2 × 23 (Group 6-30) | Success (SLC‑40) | Success (JRTI) | ||||
| January 29, 2024 | F9-293 | 62 days | Starlink v2 × 23 (Group 6-38) | Success (LC‑39A) | Success (ASOG) | ||||
| March 16, 2024 | F9-310 | 47 days | Starlink v2 × 23 (Group 6-44) | Success (LC‑39A) | Success (ASOG) | ||||
| April 13, 2024 | F9-323 | 28 days | Starlink v2 × 23 (Group 6-49) | Success (SLC‑40) | Success (ASOG) | ||||
| May 18, 2024 | F9-336 | 35 days | Starlink v2 × 23 (Group 6-59) | Success (SLC‑40) | Success (ASOG) | ||||
| June 27, 2024 | F9-350 | 40 days | Starlink v2 × 23 (Group 10-3) | Success (SLC‑40) | Success (JRTI) | ||||
| August 28, 2024 | F9-367 | 62 days | Starlink v2 × 21 (Group 8-6) | Success (SLC‑40) | Failure (ASOG) | ||||
| B1064 | FH side | 6 | November 1, 2022 | FH-004 | — | USSF-44 | Success (LC‑39A) | Success (LZ‑1)[185] | Expended |
| January 15, 2023[186] | FH-005 | 75 days | USSF-67[187] | Success (LC‑39A) | Success (LZ‑2)[188] | ||||
| July 29, 2023 | FH-007 | 195 days | Jupiter-3 (EchoStar-24)[189] | Success (LC‑39A) | Success (LZ‑1) | ||||
| October 13, 2023 | FH-008 | 76 days | Psyche[190] | Success (LC‑39A) | Success (LZ‑1) | ||||
| December 29, 2023 | FH-009 | 77 days | USSF-52 (Boeing X-37BOTV-7)[191] | Success (LC‑39A) | Success (LZ‑1) | ||||
| October 14, 2024 | FH-011 | 290 days | Europa Clipper[192] | Success (LC‑39A) | No attempt | ||||
| B1065 | FH side | 6 | November 1, 2022 | FH-004 | — | USSF-44 | Success (LC‑39A) | Success (LZ‑2)[185] | Expended |
| January 15, 2023[186] | FH-005 | 75 days | USSF-67[187] | Success (LC‑39A) | Success (LZ‑1)[188] | ||||
| July 29, 2023 | FH-007 | 195 days | Jupiter-3 (EchoStar-24)[189] | Success (LC‑39A) | Success (LZ‑2) | ||||
| October 13, 2023 | FH-008 | 76 days | Psyche[190] | Success (LC‑39A) | Success (LZ‑2) | ||||
| December 29, 2023 | FH-009 | 77 days | USSF-52 (Boeing X-37BOTV-7)[191] | Success (LC‑39A) | Success (LZ‑2) | ||||
| October 14, 2024 | FH-011 | 290 days | Europa Clipper[192] | Success (LC‑39A) | No attempt | ||||
| B1066 | FH core | 1 | November 1, 2022 | FH-004 | — | USSF-44 | Success (LC‑39A) | No attempt | Expended |
| B1068 | FH core[133] | 1 | May 1, 2023[131] | FH-006 | — | ViaSat-3 Americas[131] | Success (LC‑39A) | No attempt | Expended[132] |
| B1070 | FH core | 1 | January 15, 2023[193] | FH-005 | — | USSF-67 | Success (LC‑39A) | No attempt | Expended |
| B1073 | F9 B5 | 21 | May 14, 2022[194] | F9-154 | — | Starlink × 53 (Group 4-15)[194] | Success (SLC‑40) | Success (JRTI) | Expended |
| June 29, 2022 | F9-161 | 46 days | SES-22[195] | Success (SLC‑40) | Success (ASOG) | ||||
| August 10, 2022 | F9-169 | 42 days | Starlink × 52 (Group 4-26)[196] | Success (LC‑39A) | Success (ASOG) | ||||
| September 24, 2022 | F9-177 | 45 days | Starlink × 52 (Group 4-35)[197] | Success (SLC‑40) | Success (ASOG) | ||||
| December 11, 2022 | F9-189 | 78 days | HAKUTO-R Mission 1[198] | Success (SLC‑40) | Success (LZ‑2) | ||||
| February 7, 2023 | F9-202 | 58 days | Amazonas Nexus | Success (SLC‑40) | Success (JRTI) | ||||
| March 15, 2023 | F9-210 | 36 days | CRS-27 (Dragon C209‑3) | Success (LC‑39A) | Success (ASOG) | ||||
| April 19, 2023 | F9-218 | 35 days | Starlink v2 × 21 (Group 6-2) | Success (SLC‑40) | Success (ASOG) | ||||
| June 12, 2023 | F9-231 | 54 days | Starlink × 52 (Group 5-11) | Success (SLC‑40) | Success (JRTI) | ||||
| September 4, 2023 | F9-253 | 84 days | Starlink v2 × 21 (Group 6-12) | Success (LC‑39A) | Success (JRTI) | ||||
| November 8, 2023 | F9-270 | 65 days | Starlink v2 × 23 (Group 6-27) | Success (SLC‑40) | Success (JRTI) | ||||
| January 15, 2024 | F9-290 | 68 days | Starlink v2 × 23 (Group 6-37) | Success (SLC‑40) | Success (ASOG) | ||||
| March 4, 2024 | F9-307 | 49 days | Starlink v2 × 23 (Group 6-41) | Success (SLC‑40) | Success (ASOG) | ||||
| April 7, 2024 | F9-320 | 34 days | Bandwagon-1 (11 Sats) | Success (LC‑39A) | Success (LZ‑1) | ||||
| May 13, 2024 | F9-334 | 36 days | Starlink v2 × 23 (Group 6-58) | Success (SLC‑40) | Success (ASOG) | ||||
| July 3, 2024 | F9-352 | 51 days | Starlink v2 × 20 (Group 8-9) | Success (SLC‑40) | Success (ASOG) | ||||
| August 12, 2024 | F9-363 | 40 days | Starlink v2 × 23 (Group 10-7) | Success (LC‑39A) | Success (ASOG) | ||||
| October 23, 2024 | F9-384 | 72 days | Starlink v2 × 23 (Group 6-61) | Success (SLC‑40) | Success (ASOG) | ||||
| November 18, 2024 | F9-398 | 26 days | GSAT-20 (GSAT-N2) | Success (SLC‑40) | Success (JRTI) | ||||
| January 4, 2025 | F9-418 | 47 days | Thuraya 4-NGS | Success (SLC‑40) | Success (ASOG) | ||||
| January 30, 2025 | F9-430 | 26 days | Spainsat-NG I | Success (LC‑39A) | No attempt | ||||
| B1074 | FH core | 1 | July 29, 2023 | FH-007 | — | Jupiter-3 (EchoStar-24) | Success (LC‑39A) | No attempt | Expended |
| B1076 | F9 B5 | 22 | November 26, 2022 | F9-187 | — | CRS-26 (Dragon C211‑1) | Success (LC‑39A) | Success (JRTI) | Expended |
| January 10, 2023 | F9-196 | 45 days | OneWeb Flight 16 | Success (SLC‑40) | Success (LZ‑1) | ||||
| February 27, 2023 | F9-206 | 48 days | Starlink v2 × 21 (Group 6-1)[199] | Success (SLC‑40) | Success (ASOG) | ||||
| April 7, 2023 | F9-216 | 39 days | Intelsat 40e/Tempo | Success (SLC‑40) | Success (ASOG) | ||||
| May 19, 2023 | F9-224 | 42 days | Starlink v2 × 22 (Group 6-3) | Success (SLC‑40) | Success (ASOG) | ||||
| July 24, 2023 | F9-241 | 66 days | Starlink v2 × 22 (Group 6-6) | Success (SLC‑40) | Success (JRTI) | ||||
| September 9, 2023 | F9-254 | 47 days | Starlink v2 × 22 (Group 6-14) | Success (SLC‑40) | Success (ASOG) | ||||
| October 5, 2023 | F9-261 | 26 days | Starlink v2 × 22 (Group 6-21) | Success (SLC‑40) | Success (JRTI) | ||||
| November 12, 2023 | F9-273 | 38 days | O3b mPOWER 5 & 6 | Success (SLC‑40) | Success (ASOG) | ||||
| January 3, 2024 | F9-287 | 52 days | Ovzon-3 | Success (SLC‑40) | Success (LZ‑1) | ||||
| February 29, 2024 | F9-304 | 57 days | Starlink v2 × 23 (Group 6-40) | Success (SLC‑40) | Success (JRTI) | ||||
| March 30, 2024 | F9-315 | 30 days | Eutelsat 36D | Success (LC‑39A) | Success (JRTI) | ||||
| April 28, 2024 | F9-328 | 29 days | Starlink v2 × 23 (Group 6-54) | Success (SLC‑40) | Success (JRTI) | ||||
| June 1, 2024 | F9-342 | 34 days | Starlink v2 × 23 (Group 6-64) | Success (SLC‑40) | Success (ASOG) | ||||
| July 8, 2024 | F9-353 | 37 days | Türksat 6A | Success (SLC‑40) | Success (JRTI) | ||||
| August 15, 2024 | F9-364 | 38 days | WorldView Legion 3 & 4 | Success (SLC‑40) | Success (LZ‑1) | ||||
| October 18, 2024 | F9-382 | 64 days | Starlink v2 × 20 (Group 8-19) | Success (SLC‑40) | Success (JRTI) | ||||
| November 14, 2024 | F9-395 | 27 days | Starlink v2 × 24 (Group 6-68) | Success (SLC‑40) | Success (JRTI) | ||||
| December 5, 2024 | F9-407 | 21 days | SXM-9 | Success (LC‑39A) | Success (JRTI) | ||||
| January 27, 2025 | F9-429 | 53 days | Starlink v2 × 21 (Group 12-7) | Success (SLC‑40) | Success (ASOG) | ||||
| February 21, 2025 | F9-439 | 25 days | Starlink v2 × 21 (Group 12-14) | Success (SLC‑40) | Success (ASOG) | ||||
| October 24, 2025 | F9-551 | 245 days | Spainsat-NG II | Success (SLC‑40) | No attempt | ||||
| B1079 | FH core | 1 | October 13, 2023 | FH-008 | — | Psyche[190] | Success (LC‑39A) | No attempt | Expended |
| B1084 | FH core | 1 | December 29, 2023 | FH-009 | — | USSF-52 (Boeing X-37BOTV-7) | Success (LC‑39A) | No attempt | Expended |
| B1086 | FH side | 5 | June 25, 2024 | FH-010 | — | GOES-19 | Success (LC‑39A) | Success (LZ‑1) | Destroyed in landing failure[j] |
| F9 B5 | December 8, 2024 | F9-408 | 166 days | Starlink v2 × 23 (Group 12-5) | Success (SLC‑40) | Success (ASOG) | |||
| January 8, 2025 | F9-420 | 31 days | Starlink v2 × 21 (Group 12-11) | Success (LC‑39A) | Success (ASOG) | ||||
| February 4, 2025 | F9-433 | 27 days | WorldView Legion 5 & 6 (2 satellites) | Success (LC‑39A) | Success (LZ‑1) | ||||
| March 3, 2025 | F9-443 | 27 days | Starlink v2 × 21 (Group 12-20) | Success (SLC‑40) | Failure[j] (JRTI) | ||||
| B1087 | FH core | 1 | June 25, 2024 | FH-010 | — | GOES-19 | Success (LC‑39A) | No attempt | Expended |
| B1089 | FH core | 1 | October 14, 2024 | FH-011 | — | Europa Clipper[192] | Success (LC‑39A) | No attempt | Expended |
| |||||||||
| S/N | Type | Launches | Launch date (UTC)[6] | Flight No.[a] | Turnaround time | Payload[b] | Launch (pad) | Landing (location) | Status |
|---|---|---|---|---|---|---|---|---|---|
| B1063 | F9 B5 | 28 | November 21, 2020 | F9-099 | — | Sentinel-6A | Success (SLC‑4E) | Success (LZ‑4) | Awaiting Launch |
| May 26, 2021[200] | F9-119 | 186 days | Starlink × 60 (v1.0 L28) | Success (SLC‑40) | Success (JRTI) | ||||
| November 24, 2021[201] | F9-129 | 182 days | DART | Success (SLC‑4E) | Success (OCISLY) | ||||
| February 25, 2022 | F9-142 | 93 days | Starlink × 50 (Group 4-11) | Success (SLC‑4E) | Success (OCISLY) | ||||
| May 14, 2022 | F9-153 | 78 days | Starlink × 53 (Group 4-13)[202] | Success (SLC‑4E) | Success (OCISLY) | ||||
| July 11, 2022 | F9-163 | 58 days | Starlink × 46 (Group 3-1) | Success (SLC‑4E) | Success (OCISLY) | ||||
| August 31, 2022 | F9-173 | 51 days | Starlink × 46 (Group 3-4)[203] | Success (SLC‑4E) | Success (OCISLY) | ||||
| October 28, 2022 | F9-183 | 58 days | Starlink × 53 (Group 4-31)[204] | Success (SLC‑4E) | Success (OCISLY) | ||||
| February 17, 2023 | F9-204 | 112 days | Starlink × 51 (Group 2-5) | Success (SLC‑4E) | Success (OCISLY) | ||||
| April 15, 2023 | F9-217 | 57 days | Transporter-7 (51 Sats) | Success (SLC‑4E) | Success (LZ‑4) | ||||
| May 20, 2023 | F9-225 | 35 days | Iridium NEXT × 5 (NEXT-9)OneWeb #19[205] | Success (SLC‑4E) | Success (OCISLY) | ||||
| July 7, 2023 | F9-237 | 48 days | Starlink × 48 (Group 5-13) | Success (SLC‑4E) | Success (OCISLY) | ||||
| September 2, 2023 | F9-252 | 57 days | SDA Tranche 0, Flight 2 | Success (SLC‑4E) | Success (LZ‑4) | ||||
| October 9, 2023 | F9-262 | 37 days | Starlink v2 × 21 (Group 7-4) | Success (SLC‑4E) | Success (OCISLY) | ||||
| November 20, 2023 | F9-275 | 42 days | Starlink v2 × 22 (Group 7-7) | Success (SLC‑4E) | Success (OCISLY) | ||||
| January 24, 2024 | F9-292 | 65 days | Starlink v2 × 22 (Group 7-11) | Success (SLC‑4E) | Success (OCISLY) | ||||
| March 11, 2024 | F9-309 | 47 days | Starlink v2 × 23 (Group 7-17) | Success (SLC‑4E) | Success (OCISLY) | ||||
| May 14, 2024 | F9-335 | 64 days | Starlink v2 × 20 (Group 8-7) | Success (SLC‑4E) | Success (OCISLY) | ||||
| July 12, 2024 | F9-354 | 59 days | Starlink v2 × 20 (Group 9-3) | Failure[c] (SLC‑4E) | Success (OCISLY) | ||||
| September 6, 2024 | F9-371 | 56 days | NROL-113 (Starshield satellites) | Success (SLC‑4E) | Success (OCISLY) | ||||
| October 24, 2024 | F9-385 | 48 days | NROL-167 (Starshield satellites) | Success (SLC‑4E) | Success (OCISLY) | ||||
| December 17, 2024 | F9-411 | 54 days | NROL-149 (Starshield satellites) | Success (SLC‑4E) | Success (OCISLY) | ||||
| January 24, 2025 | F9-428 | 38 days | Starlink v2 × 23 (Group 11-6) | Success (SLC‑4E) | Success (OCISLY) | ||||
| March 26, 2025 | F9-452 | 61 days | Starlink v2 × 27 (Group 11-7) | Success (SLC‑4E) | Success (OCISLY) | ||||
| April 28, 2025 | F9-466 | 33 days | Starlink v2 × 27 (Group 11-9) | Success (SLC‑4E) | Success (OCISLY) | ||||
| June 4, 2025 | F9-485 | 37 days | Starlink v2 × 27 (Group 11-22) | Success (SLC‑4E) | Success (OCISLY) | ||||
| August 26, 2025 | F9-521 | 83 days | NAOS + 7 rideshares | Success (SLC‑4E) | Success (LZ‑4) | ||||
| September 29, 2025 | F9-541 | 34 days | Starlink x 28 (Group 11-20) | Success (SLC‑4E) | Success (OCISLY) | ||||
| Planned | October 30, 2025 | F9-xxx | 31 days | Starlink x 28 (Group 11-23) | Planned (SLC‑4E) | Planned (OCISLY) | |||
| B1067 | F9 B5 | 31 | June 3, 2021[206] | F9-120 | — | CRS-22 (Dragon C209‑1) | Success (LC‑39A) | Success (OCISLY) | Awaiting assignment |
| November 11, 2021 | F9-127 | 161 days | Crew-3 (Dragon C210‑1Endurance)[207] | Success (LC‑39A) | Success (ASOG)[208] | ||||
| December 19, 2021 | F9-133 | 38 days | Türksat 5B | Success (SLC‑40) | Success (ASOG) | ||||
| April 27, 2022 | F9-150 | 129 days | Crew-4 (Dragon C212‑1Freedom)[209] | Success (LC‑39A) | Success (ASOG) | ||||
| July 14, 2022 | F9-164 | 78 days | CRS-25 (Dragon C208-3)[210] | Success (LC‑39A) | Success (ASOG) | ||||
| September 19, 2022 | F9-176 | 67 days | Starlink × 54 (Group 4-34)[211] | Success (SLC‑40) | Success (JRTI) | ||||
| November 3, 2022 | F9-184 | 45 days | Hotbird 13G[212] | Success (SLC‑40) | Success (JRTI) | ||||
| December 16, 2022 | F9-191 | 43 days | O3b mPOWER 1 & 2[213] | Success (SLC‑40) | Success (ASOG) | ||||
| January 26, 2023 | F9-199 | 41 days | Starlink × 56 (Group 5-2) | Success (SLC‑40) | Success (JRTI) | ||||
| March 24, 2023 | F9-213 | 57 days | Starlink × 56 (Group 5-5) | Success (SLC‑40) | Success (ASOG) | ||||
| May 14, 2023 | F9-223 | 51 days | Starlink × 56 (Group 5-9)[214] | Success (SLC‑40) | Success (JRTI) | ||||
| June 18, 2023 | F9-233 | 35 days | Satria[215] | Success (SLC‑40) | Success (ASOG) | ||||
| August 17, 2023 | F9-247 | 60 days | Starlink v2 × 22 (Group 6-10) | Success (SLC‑40) | Success (ASOG) | ||||
| October 13, 2023 | F9-263 | 57 days | Starlink v2 × 22 (Group 6-22) | Success (SLC‑40) | Success (ASOG) | ||||
| November 22, 2023 | F9-276 | 40 days | Starlink v2 × 23 (Group 6-29) | Success (SLC‑40) | Success (ASOG) | ||||
| January 7, 2024 | F9-288 | 46 days | Starlink v2 × 23 (Group 6-35) | Success (SLC‑40) | Success (ASOG) | ||||
| February 20, 2024 | F9-301 | 44 days | Telkomsat Merah Putih 2 (HTS 113BT) | Success (SLC‑40) | Success (JRTI) | ||||
| March 31, 2024 | F9-316 | 40 days | Starlink v2 × 23 (Group 6-45) | Success (SLC‑40) | Success (ASOG) | ||||
| May 3, 2024 | F9-330 | 33 days | Starlink v2 × 23 (Group 6-55) | Success (SLC‑40) | Success (ASOG) | ||||
| June 5, 2024 | F9-343 | 33 days | Starlink v2 × 20 (Group 8-5) | Success (SLC‑40) | Success (JRTI) | ||||
| August 10, 2024 | F9-361 | 66 days | Starlink v2 × 21 (Group 8-3) | Success (SLC‑40) | Success (JRTI) | ||||
| September 18, 2024 | F9-375 | 39 days | GalileoFOC FM26 &FOC FM32[216] | Success (SLC‑40) | Success (JRTI) | ||||
| November 11, 2024 | F9-392 | 54 days | Koreasat 6A | Success (LC‑39A) | Success (LZ‑1) | ||||
| December 4, 2024 | F9-405 | 23 days | Starlink v2 × 24 (Group 6-70) | Success (SLC‑40) | Success (ASOG) | ||||
| January 10, 2025 | F9-422 | 37 days | Starlink v2 × 21 (Group 12-12) | Success (SLC‑40) | Success (JRTI) | ||||
| February 15, 2025 | F9-437 | 36 days | Starlink v2 × 21 (Group 12-8) | Success (SLC‑40) | Success (ASOG) | ||||
| April 14, 2025 | F9-460 | 58 days | Starlink v2 × 27 (Group 6-73) | Success (SLC‑40) | Success (JRTI) | ||||
| May 13, 2025 | F9-474 | 29 days | Starlink v2 × 28 (Group 6-83) | Success (LC‑39A) | Success (JRTI) | ||||
| July 2, 2025 | F9-500 | 50 days | Starlink x 27 (Group 10-25) | Success (SLC‑40) | Success (ASOG) | ||||
| August 28, 2025 | F9-523 | 57 days | Starlink x 28 (Group 10-11) | Success (LC‑39A) | Success (ASOG) | ||||
| October 19, 2025 | F9-548 | 52 days | Starlink x 28 (Group 10-17) | Success (SLC‑40) | Success (ASOG) | ||||
| B1069 | F9 B5 | 27 | December 21, 2021 | F9-134 | — | CRS-24 (Dragon C209‑2) | Success (LC‑39A) | Success (JRTI) | Awaiting assignment |
| August 28, 2022 | F9-172 | 250 days | Starlink × 54 (Group 4-23)[217] | Success (SLC‑40) | Success (ASOG) | ||||
| October 15, 2022 | F9-181 | 48 days | Hotbird 13F[218] | Success (SLC‑40) | Success (JRTI) | ||||
| December 8, 2022 | F9-188 | 54 days | OneWeb #15[219] | Success (LC‑39A) | Success (LZ‑1) | ||||
| February 2, 2023 | F9-201 | 56 days | Starlink × 53 (Group 5-3)[220] | Success (LC‑39A) | Success (ASOG) | ||||
| March 17, 2023 | F9-212 | 43 days | SES-18 & 19 | Success (SLC‑40) | Success (JRTI) | ||||
| May 4, 2023 | F9-221 | 48 days | Starlink × 56 (Group 5-6)[221] | Success (SLC‑40) | Success (ASOG) | ||||
| June 23, 2023 | F9-235 | 50 days | Starlink × 56 (Group 5-12) | Success (SLC‑40) | Success (JRTI) | ||||
| August 11, 2023 | F9-246 | 49 days | Starlink v2 × 22 (Group 6-9) | Success (SLC‑40) | Success (JRTI) | ||||
| September 30, 2023 | F9-260 | 50 days | Starlink v2 × 22 (Group 6-19) | Success (SLC‑40) | Success (ASOG) | ||||
| November 18, 2023 | F9-274 | 49 days | Starlink v2 × 23 (Group 6-28) | Success (SLC‑40) | Success (JRTI) | ||||
| December 29, 2023 | F9-285 | 41 days | Starlink v2 × 23 (Group 6-36) | Success (SLC‑40) | Success (ASOG) | ||||
| February 25, 2024 | F9-303 | 58 days | Starlink v2 × 24 (Group 6-39) | Success (SLC‑40) | Success (ASOG) | ||||
| April 5, 2024 | F9-318 | 40 days | Starlink v2 × 23 (Group 6-47) | Success (SLC‑40) | Success (ASOG) | ||||
| May 6, 2024 | F9-331 | 31 days | Starlink v2 × 23 (Group 6-57) | Success (SLC‑40) | Success (JRTI) | ||||
| June 8, 2024 | F9-344 | 33 days | Starlink v2 × 22 (Group 10-1) | Success (SLC‑40) | Success (ASOG) | ||||
| July 27, 2024 | F9-355 | 49 days | Starlink v2 × 23 (Group 10-9) | Success (LC‑39A) | Success (JRTI) | ||||
| August 31, 2024 | F9-368 | 35 days | Starlink v2 × 21 (Group 8-10) | Success (SLC‑40) | Success (JRTI) | ||||
| October 26, 2024 | F9-386 | 56 days | Starlink v2 × 22 (Group 10-8) | Success (SLC‑40) | Success (JRTI) | ||||
| November 21, 2024 | F9-399 | 26 days | Starlink v2 × 24 (Group 6-66) | Success (SLC‑40) | Success (ASOG) | ||||
| February 4, 2025 | F9-432 | 75 days | Starlink v2 × 21 (Group 12-3) | Success (SLC‑40) | Success (JRTI) | ||||
| March 13, 2025 | F9-445 | 37 days | Starlink v2 × 21 (Group 12-21) | Success (SLC‑40) | Success (ASOG) | ||||
| April 25, 2025 | F9-464 | 43 days | Starlink v2 × 28 (Group 6-74) | Success (SLC‑40) | Success (ASOG) | ||||
| May 24, 2025 | F9-479 | 29 days | Starlink v2 × 23 (Group 12-22) | Success (SLC‑40) | Success (ASOG) | ||||
| June 23, 2025 | F9-493 | 30 days | Starlink v2 × 27 (Group 10-23) | Success (SLC‑40) | Success (ASOG) | ||||
| July 30, 2025 | F9-510 | 37 days | Starlink x 28 (Group 10-29) | Success (SLC‑40) | Success (JRTI) | ||||
| September 5, 2025 | F9-528 | 37 days | Starlink x 28 (Group 10-57) | Success (LC‑39A) | Success (JRTI) | ||||
| B1071 | F9 B5 | 29 | February 2, 2022 | F9-139 | — | NROL-87 | Success (SLC‑4E) | Success (LZ‑4) | Awaiting assignment |
| April 17, 2022 | F9-148 | 74 days | NROL-85 | Success (SLC‑4E) | Success (LZ‑4) | ||||
| June 18, 2022 | F9-159 | 62 days | SARah-1 | Success (SLC‑4E) | Success (LZ‑4) | ||||
| July 22, 2022 | F9-166 | 34 days | Starlink × 46 (Group 3-2) | Success (SLC‑4E) | Success (OCISLY) | ||||
| October 5, 2022 | F9-179 | 75 days | Starlink × 52 (Group 4-29)[222] | Success (SLC‑4E) | Success (OCISLY) | ||||
| December 16, 2022 | F9-190 | 72 days | SWOT[223] | Success (SLC‑4E) | Success (LZ‑4) | ||||
| January 31, 2023 | F9-200 | 46 days | Starlink × 49 (Group 2-6) &D-Orbit Starfield ION SCV009[224] | Success (SLC‑4E) | Success (OCISLY) | ||||
| March 17, 2023 | F9-211 | 45 days | Starlink × 52 (Group 2-8) | Success (SLC‑4E) | Success (OCISLY) | ||||
| June 12, 2023 | F9-232 | 87 days | Transporter-8 (72 Sats) | Success (SLC‑4E) | Success (LZ‑4) | ||||
| July 20, 2023 | F9-240 | 38 days | Starlink v2 × 15 (Group 6-15) | Success (SLC‑4E) | Success (OCISLY) | ||||
| September 12, 2023 | F9-255 | 54 days | Starlink v2 × 21 (Group 7-2) | Success (SLC‑4E) | Success (OCISLY) | ||||
| November 11, 2023 | F9-272 | 60 days | Transporter-9 (113 Sats) | Success (SLC‑4E) | Success (LZ‑4) | ||||
| December 8, 2023 | F9-281 | 27 days | Starlink v2 × 22 (Group 7-8) | Success (SLC‑4E) | Success (OCISLY) | ||||
| February 10, 2024 | F9-297 | 64 days | Starlink v2 × 22 (Group 7-13) | Success (SLC‑4E) | Success (OCISLY) | ||||
| April 2, 2024 | F9-317 | 52 days | Starlink v2 × 22 (Group 7-18) | Success (SLC‑4E) | Success (OCISLY) | ||||
| May 22, 2024 | F9-337 | 50 days | NROL-146 (Starshield satellites)[225] | Success (SLC‑4E) | Success (OCISLY) | ||||
| July 28, 2024 | F9-357 | 67 days | Starlink v2 × 21 (Group 9-4) | Success (SLC‑4E) | Success (OCISLY) | ||||
| September 13, 2024 | F9-374 | 47 days | Starlink v2 × 21 (Group 9-6) | Success (SLC‑4E) | Success (OCISLY) | ||||
| October 15, 2024 | F9-381 | 32 days | Starlink v2 × 20 (Group 9-7) | Success (SLC‑4E) | Success (OCISLY) | ||||
| November 18, 2024 | F9-397 | 34 days | Starlink v2 × 20 (Group 9-12) | Success (SLC‑4E) | Success (OCISLY) | ||||
| December 21, 2024 | F9-413 | 33 days | Bandwagon-2 (30 sats) | Success (SLC‑4E) | Success (LZ‑4) | ||||
| January 10, 2025 | F9-421 | 20 days | NROL-153 (Starshield satellites) | Success (SLC‑4E) | Success (OCISLY) | ||||
| February 11, 2025 | F9-435 | 32 days | Starlink v2 × 23 (Group 11-10) | Success (SLC‑4E) | Success (OCISLY) | ||||
| April 12, 2025 | F9-458 | 60 days | NROL-192 (Starshield satellites) | Success (SLC‑4E) | Success (OCISLY) | ||||
| May 31, 2025 | F9-483 | 49 days | Starlink v2 × 27 (Group 11-18) | Success (SLC‑4E) | Success (OCISLY) | ||||
| June 23, 2025 | F9-494 | 23 days | Transporter-14 (70 Sats) | Success (SLC‑4E) | Success (OCISLY) | ||||
| July 31, 2025 | F9-511 | 38 days | Starlink x 19 (Group 13-4) | Success (SLC‑4E) | Success (OCISLY) | ||||
| September 13, 2025 | F9-532 | 44 days | Starlink x 24 (Group 17-10) | Success (SLC‑4E) | Success (OCISLY) | ||||
| October 8, 2025 | F9-544 | 25 days | Starlink x 28 (Group 11-17) | Success (SLC‑4E) | Success (OCISLY) | ||||
| B1072 | FH side | 1 | June 25, 2024 | FH-010 | — | GOES-19 | Success (LC‑39A) | Success (LZ‑2) | Awaiting Assignment |
| B1075 | F9 B5 | 21 | January 19, 2023 | F9-198 | — | Starlink × 51 (Group 2-4) | Success (SLC‑4E) | Success (OCISLY) | At Port of Long Beach |
| April 2, 2023 | F9-215 | 73 days | SDA Tranche 0, Flight 1 | Success (SLC‑4E) | Success (LZ‑4) | ||||
| May 10, 2023 | F9-222 | 38 days | Starlink × 51 (Group 2-9) | Success (SLC‑4E) | Success (OCISLY) | ||||
| June 22, 2023 | F9-234 | 43 days | Starlink × 47 (Group 5-7) | Success (SLC‑4E) | Success (OCISLY) | ||||
| August 8, 2023 | F9-245 | 47 days | Starlink v2 × 15 (Group 6-20) | Success (SLC‑4E) | Success (OCISLY) | ||||
| September 25, 2023 | F9-259 | 48 days | Starlink v2 × 21 (Group 7-3) | Success (SLC‑4E) | Success (OCISLY) | ||||
| October 29, 2023 | F9-267 | 34 days | Starlink v2 × 22 (Group 7-6) | Success (SLC‑4E) | Success (OCISLY) | ||||
| December 24, 2023 | F9-284 | 56 days | SARah 2 & 3 | Success (SLC‑4E) | Success (LZ‑4) | ||||
| January 29, 2024 | F9-294 | 36 days | Starlink v2 × 22 (Group 7-12) | Success (SLC‑4E) | Success (OCISLY) | ||||
| March 19, 2024 | F9-311 | 50 days | Starlink v2 × 22 (Group 7-16) + Rideshare | Success (SLC‑4E) | Success (OCISLY) | ||||
| June 24, 2024 | F9-349 | 97 days | Starlink v2 × 20 (Group 9-2) | Success (SLC‑4E) | Success (OCISLY) | ||||
| August 16, 2024 | F9-365 | 53 days | Transporter-11 (116 Sats) | Success (SLC‑4E) | Success (LZ‑4) | ||||
| September 20, 2024 | F9-376 | 35 days | Starlink v2 × 20 (Group 9-17) | Success (SLC‑4E) | Success (OCISLY) | ||||
| October 30, 2024 | F9-387 | 40 days | Starlink v2 × 20 (Group 9-9) | Success (SLC‑4E) | Success (OCISLY) | ||||
| November 24, 2024 | F9-400 | 25 days | Starlink v2 × 20 (Group 9-13) | Success (SLC‑4E) | Success (OCISLY) | ||||
| December 29, 2024 | F9-415 | 35 days | Starlink v2 × 22 (Group 11-3) | Success (SLC‑4E) | Success (OCISLY) | ||||
| February 1, 2025 | F9-431 | 34 days | Starlink v2 × 22 (Group 11-4) | Success (SLC‑4E) | Success (OCISLY) | ||||
| May 23, 2025 | F9-478 | 111 days | Starlink v2 × 27 (Group 11-16) | Success (SLC‑4E) | Success (OCISLY) | ||||
| July 27, 2025 | F9-509 | 65 days | Starlink x 24 (Group 17-2) | Success (SLC‑4E) | Success (OCISLY) | ||||
| September 6, 2025 | F9-529 | 41 days | Starlink x 24 (Group 17-9) | Success (SLC‑4E) | Success (OCISLY) | ||||
| October 22, 2025 | F9-550 | 46 days | Starlink x 28 (Group 11-5) | Success (SLC‑4E) | Success (OCISLY) | ||||
| B1077 | F9 B5 | 24 | October 5, 2022 | F9-178 | — | Crew-5 (Dragon C210‑2Endurance) | Success (LC‑39A) | Success (JRTI) | Landed on ASOG |
| January 18, 2023 | F9-197 | 105 days | GPS III SV06[226] | Success (SLC‑40) | Success (ASOG) | ||||
| February 18, 2023 | F9-205 | 31 days | Inmarsat 6-F2[227] | Success (SLC‑40) | Success (JRTI) | ||||
| March 29, 2023 | F9-214 | 39 days | Starlink × 56 (Group 5-10) | Success (SLC‑40) | Success (JRTI) | ||||
| June 5, 2023 | F9-230 | 68 days | CRS-28 (Dragon C208‑4) | Success (LC‑39A) | Success (ASOG) | ||||
| August 3, 2023 | F9-243 | 59 days | Galaxy 37[228] | Success (SLC‑40) | Success (JRTI) | ||||
| September 1, 2023 | F9-251 | 29 days | Starlink v2 × 22 (Group 6-13) | Success (SLC‑40) | Success (ASOG) | ||||
| October 30, 2023 | F9-268 | 59 days | Starlink v2 × 23 (Group 6-25) | Success (SLC‑40) | Success (JRTI) | ||||
| December 7, 2023 | F9-280 | 38 days | Starlink v2 × 23 (Group 6-33) | Success (SLC‑40) | Success (JRTI) | ||||
| January 30, 2024 | F9-295 | 54 days | CRS NG-20[229] | Success (SLC‑40) | Success (LZ‑1) | ||||
| March 10, 2024 | F9-308 | 40 days | Starlink v2 × 23 (Group 6-43) | Success (SLC‑40) | Success (JRTI) | ||||
| April 17, 2024 | F9-324 | 38 days | Starlink v2 × 23 (Group 6-51) | Success (LC‑39A) | Success (JRTI) | ||||
| May 24, 2024 | F9-339 | 37 days | Starlink v2 × 23 (Group 6-63) | Success (LC‑39A) | Success (JRTI) | ||||
| July 28, 2024 | F9-356 | 65 days | Starlink v2 × 23 (Group 10-4) | Success (SLC‑40) | Success (ASOG) | ||||
| September 5, 2024 | F9-370 | 39 days | Starlink v2 × 21 (Group 8-11) | Success (SLC‑40) | Success (JRTI) | ||||
| November 17, 2024 | F9-396 | 73 days | Optus-X/TD7 | Success (LC‑39A) | Success (ASOG) | ||||
| January 6, 2025 | F9-419 | 50 days | Starlink v2 × 24 (Group 6-71) | Success (SLC‑40) | Success (JRTI) | ||||
| February 11, 2025 | F9-436 | 36 days | Starlink v2 × 21 (Group 12-18) | Success (SLC‑40) | Success (JRTI) | ||||
| March 18, 2025 | F9-449 | 35 days | Starlink v2 × 23 (Group 12-25) | Success (SLC‑40) | Success (ASOG) | ||||
| April 28, 2025 | F9-465 | 41 days | Starlink v2 × 23 (Group 12-23) | Success (SLC‑40) | Success (JRTI) | ||||
| June 3, 2025 | F9-484 | 36 days | Starlink v2 × 23 (Group 12-19) | Success (SLC‑40) | Success (JRTI) | ||||
| July 8, 2025 | F9-501 | 35 days | Starlink x 28 (Group 10-28) | Success (SLC‑40) | Success (ASOG) | ||||
| August 31, 2025 | F9-525 | 54 days | Starlink x 28 (Group 10-14) | Success (SLC‑40) | Success (JRTI) | ||||
| October 26, 2025 | F9-553 | 56 days | Starlink x 28 (Group 10-21) | Success (SLC‑40) | Success (ASOG) | ||||
| B1078 | F9 B5 | 23 | March 2, 2023 | F9-207 | — | Crew-6 (Dragon C206‑4Endeavour) | Success (LC‑39A) | Success (JRTI) | Awaiting assignment |
| April 28, 2023 | F9-220 | 57 days | O3b mPOWER 3 & 4 | Success (SLC‑40) | Success (JRTI) | ||||
| June 4, 2023 | F9-229 | 37 days | Starlink v2 × 22 (Group 6-4) | Success (SLC‑40) | Success (JRTI) | ||||
| August 7, 2023 | F9-244 | 64 days | Starlink v2 × 22 (Group 6-8) | Success (SLC‑40) | Success (ASOG) | ||||
| September 16, 2023 | F9-256 | 40 days | Starlink v2 × 22 (Group 6-16) | Success (SLC‑40) | Success (JRTI) | ||||
| December 3, 2023 | F9-279 | 78 days | Starlink v2 × 23 (Group 6-31) | Success (SLC‑40) | Success (ASOG) | ||||
| February 14, 2024 | F9-298 | 73 days | USSF-124 (HBTSS & Tranche O) | Success (SLC‑40) | Success (LZ‑2) | ||||
| March 25, 2024 | F9-314 | 40 days | Starlink v2 × 23 (Group 6-46) | Success (SLC‑40) | Success (ASOG) | ||||
| April 23, 2024 | F9-326 | 29 days | Starlink v2 × 23 (Group 6-53) | Success (SLC‑40) | Success (JRTI) | ||||
| May 28, 2024 | F9-340 | 35 days | Starlink v2 × 23 (Group 6-60) | Success (SLC‑40) | Success (ASOG) | ||||
| June 23, 2024 | F9-348 | 26 days | Starlink v2 × 22 (Group 10-2) | Success (SLC‑40) | Success (ASOG) | ||||
| August 2, 2024 | F9-358 | 40 days | Starlink v2 × 23 (Group 10-6) | Success (LC‑39A) | Success (ASOG) | ||||
| September 12, 2024 | F9-373 | 41 days | BlueBird Block 1 #1-5 | Success (SLC‑40) | Success (LZ‑1) | ||||
| October 30, 2024 | F9-388 | 48 days | Starlink v2 × 23 (Group 10-13) | Success (SLC‑40) | Success (ASOG) | ||||
| November 27, 2024 | F9-402 | 28 days | Starlink v2 × 24 (Group 6-76) | Success (LC‑39A) | Success (ASOG) | ||||
| December 31, 2024 | F9-417 | 34 days | Starlink v2 × 21 (Group 12-6) | Success (LC‑39A) | Success (JRTI) | ||||
| February 8, 2025 | F9-434 | 39 days | Starlink v2 × 21 (Group 12-9) | Success (SLC‑40) | Success (ASOG) | ||||
| March 15, 2025 | F9-448 | 35 days | Starlink v2 × 23 (Group 12-16) | Success (SLC‑40) | Success (JRTI) | ||||
| April 6, 2025 | F9-456 | 22 days | Starlink v2 × 28 (Group 6-72) | Success (SLC‑40) | Success (JRTI) | ||||
| May 4, 2025 | F9-469 | 28 days | Starlink v2 × 29 (Group 6-84) | Success (LC‑39A) | Success (ASOG) | ||||
| June 13, 2025 | F9-490 | 40 days | Starlink v2 × 23 (Group 12-26) | Success (SLC‑40) | Success (ASOG) | ||||
| July 26, 2025 | F9-508 | 43 days | Starlink x 28 (Group 10-26) | Success (SLC‑40) | Success (ASOG) | ||||
| September 12, 2025 | F9-531 | 48 days | Nusantara Lima | Success (SLC‑40) | Success (ASOG) | ||||
| B1080 | F9 B5 | 22 | May 21, 2023 | F9-226 | — | Ax-2 (Dragon C212‑2Freedom) | Success (LC‑39A) | Success (LZ‑1) | Awaiting assignment |
| July 1, 2023 | F9-236 | 41 days | Euclid | Success (SLC‑40) | Success (ASOG) | ||||
| August 27, 2023 | F9-250 | 57 days | Starlink v2 × 22 (Group 6-11) | Success (SLC‑40) | Success (JRTI) | ||||
| October 22, 2023 | F9-266 | 56 days | Starlink v2 × 23 (Group 6-24) | Success (SLC‑40) | Success (ASOG) | ||||
| January 18, 2024 | F9-291 | 88 days | Ax-3 (Dragon C212‑3Freedom) | Success (LC‑39A) | Success (LZ‑1) | ||||
| March 21, 2024 | F9-312 | 63 days | CRS-30 (Dragon C209‑4) | Success (SLC‑40) | Success (LZ‑1) | ||||
| April 18, 2024 | F9-325 | 28 days | Starlink v2 × 23 (Group 6-52) | Success (SLC‑40) | Success (ASOG) | ||||
| May 23, 2024 | F9-338 | 35 days | Starlink v2 × 23 (Group 6-62) | Success (SLC‑40) | Success (ASOG) | ||||
| June 20, 2024 | F9-347 | 28 days | Astra 1P/SES-24[230] | Success (SLC‑40) | Success (JRTI) | ||||
| August 4, 2024 | F9-360 | 45 days | CRS NG-21 | Success (SLC‑40) | Success (LZ‑1) | ||||
| October 15, 2024 | F9-380 | 72 days | Starlink v2 × 23 (Group 10-10) | Success (SLC‑40) | Success (ASOG) | ||||
| November 11, 2024 | F9-393 | 27 days | Starlink v2 × 24 (Group 6-69) | Success (SLC‑40) | Success (ASOG) | ||||
| November 25, 2024 | F9-401 | 14 days | Starlink v2 × 23 (Group 12-1) | Success (SLC‑40) | Success (JRTI) | ||||
| December 23, 2024 | F9-414 | 28 days | Starlink v2 × 21 (Group 12-2) | Success (LC‑39A) | Success (JRTI) | ||||
| January 13, 2025 | F9-423 | 21 days | Starlink v2 × 21 (Group 12-4) | Success (SLC‑40) | Success (ASOG) | ||||
| February 18, 2025 | F9-438 | 36 days | Starlink v2 × 21 (Group 10-12) | Success (SLC‑40) | Success (JRTI) | ||||
| March 31, 2025 | F9-453 | 41 days | Starlink v2 × 28 (Group 6-80) | Success (SLC‑40) | Success (JRTI) | ||||
| May 2, 2025 | F9-468 | 32 days | Starlink v2 × 28 (Group 6-75) | Success (SLC‑40) | Success (JRTI) | ||||
| May 28, 2025 | F9-481 | 26 days | Starlink v2 × 27 (Group 10-32) | Success (LC‑39A) | Success (JRTI) | ||||
| June 25, 2025 | F9-496 | 28 days | Starlink v2 × 27 (Group 10-16) | Success (SLC‑40) | Success (JRTI) | ||||
| August 4, 2025 | F9-513 | 40 days | Starlink x 28 (Group 10-30) | Success (SLC‑40) | Success (JRTI) | ||||
| September 25, 2025 | F9-539 | 52 days | Starlink x 28 (Group 10-15) | Success (SLC‑40) | Success (ASOG) | ||||
| B1081 | F9 B5 | 19 | August 26, 2023 | F9-249 | — | Crew-7 (Dragon C210‑3Endurance) | Success (LC‑39A) | Success (LZ‑1) | At Port of Long Beach |
| November 10, 2023 | F9-271 | 76 days | CRS-29 (Dragon C211‑2) | Success (LC‑39A) | Success (LZ‑1) | ||||
| December 19, 2023 | F9-282 | 39 days | Starlink v2 × 23 (Group 6-34) | Success (SLC‑40) | Success (ASOG) | ||||
| February 8, 2024 | F9-296 | 51 days | PACE | Success (SLC‑40) | Success (LZ‑1) | ||||
| March 4, 2024 | F9-306 | 25 days | Transporter-10 (53 Sats) | Success (SLC‑4E) | Success (LZ‑4) | ||||
| April 7, 2024 | F9-319 | 34 days | Starlink v2 × 21 (Group 8-1) | Success (SLC‑4E) | Success (OCISLY) | ||||
| May 28, 2024 | F9-341 | 51 days | EarthCARE | Success (SLC‑4E) | Success (LZ‑4) | ||||
| June 29, 2024 | F9-351 | 32 days | NROL-186 (Starshield satellites) | Success (SLC‑4E) | Success (OCISLY) | ||||
| August 31, 2024 | F9-369 | 63 days | Starlink v2 × 21 (Group 9-5) | Success (SLC‑4E) | Success (OCISLY) | ||||
| September 25, 2024 | F9-377 | 25 days | Starlink v2 × 20 (Group 9-8) | Success (SLC‑4E) | Success (OCISLY) | ||||
| November 9, 2024 | F9-391 | 45 days | Starlink v2 × 20 (Group 9-10) | Success (SLC‑4E) | Success (OCISLY) | ||||
| December 5, 2024 | F9-406 | 26 days | Starlink v2 × 20 (Group 9-14) | Success (SLC‑4E) | Success (OCISLY) | ||||
| March 15, 2025 | F9-447 | 100 days | Transporter-13 (74 Sats) | Success (SLC‑4E) | Success (LZ‑4) | ||||
| May 10, 2025 | F9-471 | 56 days | Starlink v2 × 26 (Group 15-3) | Success (SLC‑4E) | Success (OCISLY) | ||||
| June 13, 2025 | F9-489 | 34 days | Starlink v2 × 26 (Group 15-6) | Success (SLC‑4E) | Success (OCISLY) | ||||
| July 23, 2025 | F9-507 | 40 days | TRACERS (2 satellites) + 5 rideshares | Success (SLC‑4E) | Success (LZ‑4) | ||||
| August 22, 2025 | F9-519 | 30 days | Starlink x 24 (Group 17-6) | Success (SLC‑4E) | Success (OCISLY) | ||||
| September 22, 2025 | F9-537 | 31 days | NROL-48 (Starshield satellites) | Success (SLC‑4E) | Success (LZ‑4) | ||||
| October 25, 2025 | F9-552 | 33 days | Starlink x 28 (Group 11-12) | Success (SLC‑4E) | Success (OCISLY) | ||||
| B1082 | F9 B5 | 16 | January 3, 2024 | F9-286 | — | Starlink v2 × 21 (Group 7-9) | Success (SLC‑4E) | Success (OCISLY) | Awaiting Launch |
| February 15, 2024 | F9-300 | 43 days | Starlink v2 × 22 (Group 7-14) | Success (SLC‑4E) | Success (OCISLY) | ||||
| April 11, 2024 | F9-322 | 56 days | USSF-62 (WSF-M 1) | Success (SLC‑4E) | Success (LZ‑4) | ||||
| May 10, 2024 | F9-333 | 29 days | Starlink v2 × 20 (Group 8-2) | Success (SLC‑4E) | Success (OCISLY) | ||||
| June 19, 2024 | F9-346 | 40 days | Starlink v2 × 20 (Group 9-1)[231] | Success (SLC‑4E) | Success (OCISLY) | ||||
| August 4, 2024 | F9-359 | 46 days | Starlink v2 × 23 (Group 11-1) | Success (SLC‑4E) | Success (OCISLY) | ||||
| October 20, 2024 | F9-383 | 77 days | OneWeb #20 (20 satellites) | Success (SLC‑4E) | Success (LZ‑4) | ||||
| November 14, 2024 | F9-394 | 25 days | Starlink v2 × 20 (Group 9-11) | Success (SLC‑4E) | Success (OCISLY) | ||||
| December 13, 2024 | F9-409 | 29 days | Starlink v2 × 22 (Group 11-2) | Success (SLC‑4E) | Success (OCISLY) | ||||
| January 21, 2025 | F9-427 | 39 days | Starlink v2 × 27 (Group 11-8) | Success (SLC‑4E) | Success (OCISLY) | ||||
| February 23, 2025 | F9-440 | 33 days | Starlink v2 × 22 (Group 15-1) | Success (SLC‑4E) | Success (OCISLY) | ||||
| April 20, 2025 | F9-461 | 56 days | NROL-145 (Starshield satellites) | Success (SLC‑4E) | Success (OCISLY) | ||||
| May 27, 2025 | F9-480 | 37 days | Starlink v2 × 24 (Group 17-1) | Success (SLC‑4E) | Success (OCISLY) | ||||
| July 19, 2025 | F9-505 | 53 days | Starlink v2 × 24 (Group 17-3) | Success (SLC‑4E) | Success (OCISLY) | ||||
| August 30, 2025 | F9-524 | 42 days | Starlink x 24 (Group 17-7) | Success (SLC‑4E) | Success (OCISLY) | ||||
| September 26, 2025 | F9-540 | 27 days | Starlink x 24 (Group 17-11) | Success (SLC‑4E) | Success (OCISLY) | ||||
| Planned | October 27, 2025 | F9-xxx | 31 days | Starlink x 28 (Group 11-21) | Planned (SLC‑4E) | Planned (OCISLY) | |||
| B1083 | F9 B5 | 14 | March 4, 2024 | F9-305 | — | Crew-8 (Dragon C206‑5Endeavour) | Success (LC‑39A) | Success (LZ‑1) | Awaiting Launch |
| April 10, 2024 | F9-321 | 37 days | Starlink v2 × 23 (Group 6-48) | Success (SLC‑40) | Success (JRTI) | ||||
| May 8, 2024 | F9-332 | 28 days | Starlink v2 × 23 (Group 6-56) | Success (LC‑39A) | Success (ASOG) | ||||
| September 10, 2024 | F9-372 | 125 days | Polaris Dawn (Dragon C207‑3Resilience) | Success (LC‑39A) | Success (JRTI) | ||||
| November 5, 2024 | F9-389 | 56 days | CRS-31 (Dragon C208‑5) | Success (LC‑39A) | Success (LZ‑1) | ||||
| November 30, 2024 | F9-403 | 25 days | Starlink v2 × 24 (Group 6-65) | Success (SLC‑40) | Success (JRTI) | ||||
| December 29, 2024 | F9-416 | 29 days | Astranis: From One to Many | Success (SLC‑40) | Success (ASOG) | ||||
| January 21, 2025 | F9-426 | 23 days | Starlink v2 × 21 (Group 13-1) + Rideshare | Success (LC‑39A) | Success (ASOG) | ||||
| February 27, 2025 | F9-441 | 37 days | IM-2Athena | Success (LC‑39A) | Success (ASOG) | ||||
| April 13, 2025 | F9-459 | 45 days | Starlink v2 × 21 (Group 12-17) | Success (LC‑39A) | Success (ASOG) | ||||
| May 10, 2025 | F9-472 | 27 days | Starlink v2 × 28 (Group 6-91) | Success (SLC‑40) | Success (ASOG) | ||||
| June 10, 2025 | F9-488 | 31 days | Starlink v2 × 23 (Group 12-24) | Success (SLC‑40) | Success (JRTI) | ||||
| July 13, 2025 | F9-502 | 33 days | Dror 1 | Success (SLC‑40) | Success (JRTI) | ||||
| September 3, 2025 | F9-527 | 52 days | Starlink x 28 (Group 10-22) | Success (SLC‑40) | Success (ASOG) | ||||
| Planned | October 28, 2025 | F9-xxx | 55 days | Starlink x 29 (Group 10-37) | Planned (SLC‑40) | Planned (JRTI) | |||
| B1085 | F9 B5 | 11 | August 20, 2024 | F9-366 | — | Starlink v2 × 22 (Group 10-5) | Success (SLC‑40) | Success (ASOG) | Awaiting assignment |
| September 28, 2024 | F9-378 | 39 days | Crew-9 (Dragon C212‑4Freedom) | Success (SLC‑40) | Success (LZ‑1) | ||||
| November 7, 2024 | F9-390 | 40 days | Starlink v2 × 23 (Group 6-77) | Success (SLC‑40) | Success (JRTI) | ||||
| December 17, 2024 | F9-410 | 40 days | GPS III-7 (RRT-1)[232] | Success (SLC‑40) | Success (ASOG) | ||||
| January 15, 2025 | F9-425 | 29 days | Blue Ghost Mission 1 &Hakuto-R Mission 2 | Success (LC‑39A) | Success (JRTI) | ||||
| April 1, 2025 | F9-454 | 76 days | Fram2 (Dragon C207‑4Resilience) | Success (LC‑39A) | Success (ASOG) | ||||
| May 7, 2025 | F9-470 | 36 days | Starlink v2 × 28 (Group 6-93) | Success (SLC‑40) | Success (JRTI) | ||||
| June 7, 2025 | F9-486 | 31 days | SXM-10 | Success (SLC‑40) | Success (ASOG) | ||||
| July 1, 2025 | F9-499 | 24 days | MTG-S1 /Sentinel-4A | Success (LC‑39A) | Success (JRTI) | ||||
| August 14, 2025 | F9-516 | 44 days | Starlink x 28 (Group 10-20) | Success (SLC‑40) | Success (JRTI) | ||||
| September 21, 2025 | F9-536 | 38 days | Starlink x 28 (Group 10-27) | Success (SLC‑40) | Success (ASOG) | ||||
| B1088 | F9 B5 | 11 | November 30, 2024 | F9-404 | — | NROL-126 (Starshield) andStarlink v2 × 20 | Success (SLC‑4E) | Success (OCISLY) | Awaiting assignment |
| January 14, 2025 | F9-424 | 45 days | Transporter-12 (131 Sats) | Success (SLC‑4E) | Success (LZ‑4) | ||||
| March 12, 2025 | F9-444 | 57 days | SPHEREx &PUNCH (4 satellites) | Success (SLC‑4E) | Success (LZ‑4) | ||||
| March 21, 2025 | F9-450 | 9 days | NROL-57 | Success (SLC‑4E) | Success (LZ‑4) | ||||
| April 4, 2025 | F9-455 | 14 days | Starlink × 27 (Group 11-13) | Success (SLC‑4E) | Success (OCISLY) | ||||
| May 13, 2025 | F9-473 | 39 days | Starlink v2 × 26 (Group 15-4) | Success (SLC‑4E) | Success (OCISLY) | ||||
| June 8, 2025 | F9-487 | 26 days | Starlink v2 × 26 (Group 15-8) | Success (SLC‑4E) | Success (OCISLY) | ||||
| June 28, 2025 | F9-498 | 20 days | Starlink v2 × 26 (Group 15-7) | Success (SLC‑4E) | Success (OCISLY) | ||||
| August 18, 2025 | F9-517 | 51 days | Starlink x 24 (Group 17-5) | Success (SLC‑4E) | Success (OCISLY) | ||||
| September 19, 2025 | F9-535 | 32 days | Starlink x 24 (Group 17-12) | Success (SLC‑4E) | Success (OCISLY) | ||||
| October 19, 2025 | F9-549 | 30 days | Starlink x 28 (Group 11-19) | Success (SLC‑4E) | Success (OCISLY) | ||||
| B1090 | F9 B5 | 8 | December 17, 2024 | F9-412 | — | O3b mPOWER 7 & 8 | Success (LC‑39A) | Success (JRTI) | Awaiting assignment |
| March 14, 2025 | F9-446 | 87 days | Crew-10 (Dragon C210‑4Endurance) | Success (LC‑39A) | Success (LZ‑1) | ||||
| April 22, 2025 | F9-463 | 39 days | Bandwagon-3 | Success (SLC‑40) | Success (LZ‑2) | ||||
| May 14, 2025 | F9-475 | 22 days | Starlink v2 × 28 (Group 6-67) | Success (SLC‑40) | Success (ASOG) | ||||
| June 18, 2025 | F9-492 | 35 days | Starlink v2 × 28 (Group 10-18) | Success (SLC‑40) | Success (JRTI) | ||||
| July 22, 2025 | F9-506 | 34 days | O3b mPOWER 9 & 10 | Success (SLC‑40) | Success (JRTI) | ||||
| August 24, 2025 | F9-520 | 33 days | CRS-33 (Dragon C211‑3) | Success (SLC‑40) | Success (ASOG) | ||||
| October 7, 2025 | F9-543 | 44 days | Starlink x 28 (Group 10-59) | Success (SLC‑40) | Success (ASOG) | ||||
| B1091[233] | F9 B5[d] | 2 | August 11, 2025 | F9-514 | — | KuiperSat × 24 (KF-02) | Success (SLC‑40) | Success (ASOG) | Awaiting Assignment |
| October 14, 2025 | F9-545 | 64 days | KuiperSat × 24 (KF-03) | Success (SLC‑40) | Success (ASOG) | ||||
| FH core | Planned | ? | - | — | ? | Planned (LC‑39A) | ? | ||
| B1092 | F9 B5 | 7 | February 27, 2025 | F9-442 | — | Starlink × 21 (Group 12-13)[234] | Success (SLC‑40) | Success (JRTI) | Awaiting assignment |
| March 24, 2025 | F9-451 | 25 days | NROL-69 | Success (SLC‑40) | Success (LZ‑1) | ||||
| April 21, 2025 | F9-462 | 28 days | CRS-32 (Dragon C209‑5) | Success (LC‑39A) | Success (LZ‑1) | ||||
| May 30, 2025 | F9-482 | 39 days | GPS III SV08 | Success (SLC‑40) | Success (ASOG) | ||||
| June 28, 2025 | F9-497 | 29 days | Starlink x 27 (Group 10-34) | Success (SLC‑40) | Success (ASOG) | ||||
| August 22, 2025 | F9-518 | 55 days | USSF-36 (Boeing X-37BOTV-8) | Success (LC‑39A) | Success (LZ‑2) | ||||
| September 18, 2025 | F9-534 | 27 days | Starlink x 28 (Group 10-61) | Success (SLC‑40) | Success (JRTI) | ||||
| B1093 | F9 B5 | 7 | April 7, 2025 | F9-457 | — | Starlink × 27 (Group 11-11) | Success (SLC‑4E) | Success (OCISLY) | Awaiting assignment |
| May 16, 2025 | F9-476 | 39 days | Starlink v2 × 26 (Group 15-5) | Success (SLC‑4E) | Success (OCISLY) | ||||
| June 17, 2025 | F9-491 | 32 days | Starlink v2 × 26 (Group 15-9) | Success (SLC‑4E) | Success (OCISLY) | ||||
| July 16, 2025 | F9-503 | 29 days | Starlink v2 × 26 (Group 15-2) | Success (SLC‑4E) | Success (OCISLY) | ||||
| August 14, 2025 | F9-515 | 29 days | Starlink x 24 (Group 17-4) | Success (SLC‑4E) | Success (OCISLY) | ||||
| September 10, 2025 | F9-530 | 27 days | SDA Tranche 1 Transport Layer B | Success (SLC‑4E) | Success (OCISLY) | ||||
| October 15, 2025 | F9-546 | 35 days | SDA Tranche 1 Transport Layer C | Success (SLC‑4E) | Success (OCISLY) | ||||
| B1094 | F9 B5 | 4 | April 29, 2025 | F9-467 | — | Starlink × 23 (Group 12-10) | Success (LC‑39A) | Success (ASOG) | Awaiting assignment |
| June 25, 2025 | F9-495 | 57 days | Ax-4 (Dragon C213‑1Grace) | Success (LC‑39A) | Success (LZ‑1) | ||||
| August 1, 2025 | F9-512 | 37 days | Crew-11 (Dragon C206‑6Endeavour)[235] | Success (LC‑39A) | Success (LZ‑1) | ||||
| September 14, 2025 | F9-533 | 44 days | CRS NG-23 | Success (SLC‑40) | Success (LZ‑2) | ||||
| B1095 | F9 B5 | 3 | May 21, 2025 | F9-477 | — | Starlink x 23 (Group 12-15) | Success (SLC‑40) | Success (JRTI) | Awaiting assignment |
| August 27, 2025 | F9-522 | 98 days | Starlink x 28 (Group 10-56) | Success (SLC‑40) | Success (JRTI) | ||||
| October 16, 2025 | F9-547 | 50 days | Starlink x 28 (Group 10-52) | Success (SLC‑40) | Success (JRTI) | ||||
| B1096 | F9 B5 | 2 | July 16, 2025 | F9-504 | — | KuiperSat × 24 (KF-01) | Success (SLC‑40) | Success (ASOG) | Awaiting assignment |
| September 24, 2025 | F9-538 | 70 days | IMAP + 2 Rideshares | Success (LC‑39A) | Success (JRTI) | ||||
| B1097 | F9 B5 | 2 | September 3, 2025 | F9-526 | — | Starlink x 24 (Group 17-8) | Success (SLC‑4E) | Success (OCISLY) | Awaiting assignment |
| October 3, 2025 | F9-542 | 30 days | Starlink x 28 (Group 11-39) | Success (SLC‑4E) | Success (OCISLY) | ||||
| B1098 | FH core | Planned | ? | - | — | ? | Planned (LC‑39A) | No attempt | Awaiting Assignment |
| B1100 | F9 B5 | Planned | ? | - | — | ? | Planned (TBA) | Planned (TBA) | Awaiting Assignment |
Rockets from the Falcon 9 family have a success rate of99.47% and have been launched 564 times over 15 years, resulting in 561 full successes, two in-flight failures (SpaceX CRS-7 andStarlink Group 9–3), one pre-flight failure (AMOS-6 while being prepared for an on-padstatic fire test), and one partial failure (SpaceX CRS-1, which delivered its cargo to theInternational Space Station (ISS), but asecondary payload was stranded in a lower-than-planned orbit). The active version of the rocket, theFalcon 9 Block 5, has flown 496 times successfully and failed once (Starlink Group 9–3), resulting in the99.8% success rate.
In 2022, the Falcon 9 set a new record with 60 successful launches by the same launch vehicle type in a calendar year. This surpassed the previous record held bySoyuz-U, which had 47 launches (45 successful) in 1979.[236] In 2023, the Falcon family of rockets (including the Falcon Heavy) had 96 successful launches, surpassing the63 launches (61 successful) of theR-7 rocket family in 1980.[a][237] In 2024, SpaceX broke their own record with 134 total Falcon flights (133 successful) accounting for over half of allorbital launches that year.
The Falcon 9 has evolved through several versions:v1.0 was launched five times from 2010 to 2013,v1.1 launched 15 times from 2013 to 2016,Full Thrust launched 36 times from 2015 to 2015. The most recent version, Block 5, was introduced in May 2018.[238] With each iteration, the Falcon 9 boosters has become more powerful and capable of vertical landing, while fairings simultaneously performing water landing, before being scouped out of water. As vertical landings and fairing recovery operations became more commonplace, SpaceX focused on streamlining the refurbishment process for boosters and fairings, making it faster and more cost-effective.[4]
TheFalcon Heavy derivative is a heavy-lift launch vehicle composed of three Falcon 9 first-stage boosters. The central core is reinforced, while the side boosters feature aerodynamicnosecone instead of the usualinterstage.[239]
Falcon 9 first-stage boosters landed successfully in 523 of 536 attempts (97.6%), with 498 out of 504 (98.8%) for the Falcon 9 Block 5 version. A total of 493re-flights of first stage boosters have all successfully launched their second stages and, all but one, their payloads.
This chart displays the turnaround time, in months, between two flights of each booster. As of October 26, 2025, the shortest turnaround time was 9 days, 3 hours, 39 minutes and 28 seconds, for the fourth flight of B1088. Boosters that are still likely to be re-used (active fleet) are highlighted in bold.
This chart lists how often boosters were flown. It is limited to the Full Thrust versions as previous versions were never recovered intact. The entries for Block 5 include active boosters that can make additional flights in the future. Blocks 1–3 made 27 flights with 18 boosters (1.5 flights per booster), Block 4 made 12 flights with 7 boosters (1.7 flights per booster). As of October 26, 2025, Block 5 made 497 flights with 36 boosters (13.8 flights per booster) with Falcon 9.
This chart shows how many Block 5 boosters have had N flights, and their status: whether they are still active, expended (i.e. no attempt was made to recover) or destroyed (i.e. recovery of the booster failed).
The F9 boosterexpended after 1 use was B1054, (GPS III SV01 to MEO, Dec 2018).
The three boostersdestroyed on their first flight include two FH cores : B1055 (fell off ship, Apr 2019) and B1057 (ADS landing fail, June 2019).
This timeline displays all launches of Falcon 9 boosters starting with the first launch of Full Thrust. Active boosters that are expected to make additional flights in the future are marked with an asterisk. Single flights are marked with vertical lines. A short white gap indicates conversion between Falcon 9 and Falcon Heavy side formats. For boosters having performed several launches, colored bars indicate the turnaround time for each flight.

MostFalcon Heavy flights include landing of two side boosters onshore at the same time:

Grasshopper consisted of "a Falcon 9 first-stage tank, a single Merlin-1D engine" with a height of 32 m (105 ft).[240] The booster used forGrasshopper had the serial number 0002.
Grasshopper began flight testing in September 2012 with a brief, three-second hop, followed by a second hop in November 2012 with an 8-second flight that took the testbed approximately 5.4 m (18 ft) off the ground, and a third flight in December 2012 of 29 seconds duration, with extended hover under rocket engine power, in which it ascended to an altitude of 40 m (130 ft) before descending under rocket power to come to a successful vertical landing.[241]Grasshopper made its eighth, and final, test flight on October 7, 2013, flying to an altitude of 744 m (2,441 ft) before making its eighth successfulvertical landing.[242]Grasshopper is retired.[11]

Falcon 9 B1019 was the first Full Thrust booster, and was first launched on December 22, 2015, forFalcon 9 flight 20 and landed on theLanding Zone 1 (LZ‑1) at Cape Canaveral. It became the first orbital-class rocket booster to perform a successful return to launch site andvertical landing.[243][244][245]
SpaceX decided not to fly the booster again.[246] Rather, the rocket was moved a few miles north, refurbished by SpaceX at the adjacentKennedy Space Center, to conduct a static fire test. This test aimed to assess the health of the recovered booster and the capability of this rocket design to fly repeatedly in the future.[247][243] The historic booster is on display outside SpaceX headquarters inHawthorne, California.

Falcon 9 B1021 was the first booster to be re-flown and the first to land on a droneship. It was first launched on April 8, 2016, carrying aDragon spacecraft andBigelow Expandable Activity Module (BEAM) on theSpaceX CRS-8 mission and landed on anautonomous spaceport drone ship (ASDS). After recovery, inspections and refurbishing, it was launched again on March 30, 2017, for theSES-10 mission and recovered successfully a second time. This event marks a milestone inSpaceX's drive to develop reusable rockets and reduce launch costs.[28][248][249][250][251] Following the second flight, SpaceX stated that they plan to retire this booster and donate it toCape Canaveral for public display.[252][253] It was later put on public display outsideDish Network's headquarters inLittleton, Colorado in October 2023.[30]

B1023 became the third orbital-class rocket to land on a droneship after launchingThaicom 8 into a geostationary transfer orbit on May 27, 2016. It was an unusually hard landing that crushed the energy absorbers on at least one of the landing legs, causing the booster to "walk" across the droneship and lean over,[254][255] but the rocket arrived safely at Port Canaveral.[256] B1025[257] successfully launched theCRS-9 resupply mission on its maiden flight on July 18, 2016, and landed on LZ-1, being the first after B1019 to do so.[258] The mission carried a new docking adapter specifically designed for autonomous spacecraft to the ISS in preparation forDragon 2 resupply andCommercial Crew missions.[259]
B1023 and B1025 were assigned the role of side boosters for theFalcon Heavy test flight in 2017, after which they underwent separate static fire tests. The boosters were mated to a newly built Falcon Heavy core, B1033, for the flight.[260] The maiden flight of Falcon Heavy on February 6, 2018, launched SpaceX CEO Elon Musk'sTesla Roadster and a dummy astronaut into a Mars-crossing heliocentric orbit. The boosters successfully separated from the core and performed synchronized landings on LZ-1 and LZ-2.[261] B1033 failed to land on the droneship due to running out of ignition fluid which resulted in two of three engines failing to ignite for its landing burn. The droneship suffered minor damage.
B1023 is on display at theKennedy Space Center Visitor Complex in its Falcon Heavy side booster configuration.[37]

B1046 was the first Block 5, the final version of the SpaceX Falcon 9. It was first launched on May 11, 2018, carryingBangabandhu-1, Bangladesh's first geostationary communications satellite. This marked the 54th flight of the Falcon 9 and the first flight of theFalcon 9 Block 5.[262] After completing a successful ascent, B1046 landed on thedrone shipOf Course I Still Love You. After inspection and refurbishment, B1046 was launched a second time on August 7, 2018, carrying theTelkom-4 (Merah Putih) satellite. The Telkom-4 mission marked the first time an orbital-class rocket booster launched two GTO missions. This was also the first re-flight of a Block 5 booster.[263] Four months after the Telkom-4 mission, B1046 arrived atVandenberg Air Force Base to support theSSO-A mission. Following delays for additional satellite checks,[264] liftoff occurred fromSLC-4E on December 3, 2018. This marked the first time that the same orbital-class booster flew three times.[265] Its fourth and last mission launched aCrew Dragon capsule up to the point ofmaximum dynamic pressure, where it separated from the rocket totest its abort system in flight to validate the system's safety for crews. After separation of Falcon and Dragon, B1046 was destroyed by aerodynamic forces.
B1048 was the third Falcon 9 Block 5 to fly and the second Block 5 booster to re-fly, and the first booster ever to be launched four, then five times. During the last launch, an engine shut down seconds before the planned shutdown, becoming only the second time aMerlin engine failed since the failure during theSpaceX CRS-1 in October 2012. The primary mission was unaffected and theStarlink payload deployed successfully,[266] further confirming the reliability of the rocket due to redundancy of the engines. With reduced thrust, B1048 was unable to sufficiently slow down its descent, and thus was unable to land.[267]
B1049 was the oldest Falcon 9 booster on active duty until its last flight on November 22, 2022, after which this title went to B1052. It was the first to successfully launch and land six, then seven times, and the second to launch and land eight, nine, and then ten times respectively. It launched two commercial payloads,Telstar 18V and the eighthIridium NEXT batch, and eight internalStarlink batches.[268] B1049 was seen with its landing legs and grid fins removed indicating that it would be expended on its next flight. The final flight of B1049 was originally thought to be O3b mPower 4-6 but a regrouping of the launches meant that an expendable booster was no longer required. It was then planned that B1049's last flight would be the launch of Nilesat-301 however, those plans changed and the mission was flown with a recoverable booster (B1062.7). B1049 flew the Eutelsat-10B communications satellite with a Test/SpareBlock 4 interstage on November 22, 2022. This mission was its last flight.[82][102][269]
B1050 launched for the first time on December 5, 2018.[270][271] A grid fin malfunction occurred shortly after the entry burn, resulting in the booster performing a controlled landing in the ocean instead of the planned ground pad landing.[272]
No future flights for B1050 were planned, and it was scrapped due to its damage,[273] with some parts being recycled into theStarhopper test vehicle.
B1051 was the sixth Falcon 9 Block 5 booster built. On its maiden flight on March 2, 2019, it carried a Crew Dragon into orbit on theDemo-1 mission. It then flew its second mission out of Vandenberg AFB launching the Radarsat constellation. It then flew 4 Starlink missions and launched SXM-7, totaling 5 flights in 2020 alone, and becoming the first Falcon 9 to launch a commercial payload on its seventh flight. On December 18, 2021, it flew for a record 11th time.[274] It was the first booster to be used eight, nine, ten, eleven, and twelve times respectively. It flew for the final time on November 12, 2022, for the Intelsat G-31/G-32 mission, and was expended.
B1056 first launched on May 4, 2019, carrying a Cargo Dragon to the ISS. Because of the failure of the static test fire ofCrew Dragon C204's Super-Draco abort engines on LZ-1, it landed on a drone ship instead.[275] It flew three more times. On February 17, 2020, B1056 was planned to perform the 50th orbital-class rocket landing, just 27 days after its previous launch.[276] The booster soft-landed in the Atlantic Ocean and was severely damaged after launching Starlink satellites into orbit, becoming the first flight-proven Block 5 booster to fail landing.[137]

Falcon 9 B1058 was first launched on May 30, 2020, fromKennedy Space Center Launch Complex 39A (Apollo 11 launch site). It carriedNASA astronautsDoug Hurley andBob Behnken to theInternational Space Station. It was the first crewed orbital spaceflight launched from the United States since the finalSpace Shuttle mission, and the first crewed flight test ofDragon 2. It was the first crewed orbital spaceflight by a private company. The booster was the first and only Falcon 9 booster to featureNASA's worm logo and meatball insignia, which was reintroduced after last being used in 1992.[277]
On September 11, 2022, it flew for the 14th time and became the first booster to be recovered 14 times.[278] On December 17, 2022, it was also the first booster to fly and land for the 15th time.[279] On July 10, 2023, it broke the reusability record of flying and landing an orbital-class rocket booster for the 16th time and later went on to be the first to complete 17, 18, and 19 launches in the same year.[280]
Despite the successful landing in its nineteenth flight, the booster tipped over during transit due to rough seas and high winds. SpaceX has already equipped newer Falcon boosters with upgraded landing legs that have the capability to self-level and mitigate this type of issue.[281]
B1060 first flew on June 30, 2020, a month after Demo-2. Further missions it supported include launches of Starlink v1, v1.5 and v2 Mini, two Transporter ridesharing missions, and three large commercial satellites. After becoming the senior active rocket for SpaceX on December 25, 2023, it was assigned to what would become the first successful commercial Lunar landing: the booster launchedIM-1 on February 15, 2024. This was its eighteenth mission.[282]
Falcon 9 B1061 first launchedCrew-1 to the ISS on November 16, 2020, the first operational flight of Crew Dragon, and landed on a drone ship.[283] It became the first booster to fly crew twice as well as the first reused booster to fly crew as a part of theCrew-2 mission.[284] This first stage went on to complete additional missions.[168] B1061 is the only booster to land on all of SpaceX's different landing zones and drone ships (not including LZ-2). It was expended on theESAHera launch on October 7, 2024. Booster 1061 flew a total of 23 flights, making it tied with B1062 for the oldest Falcon 9 booster.
Falcon 9 B1062 launchedInspiration4 in 2021, operated bySpaceX on behalf ofShift4 Payments CEOJared Isaacman.[285] The mission launched theCrew DragonResilience on September 16, 2021, at 00:02:56UTC[a] from the FloridaKennedy Space Center'sLaunch Complex 39A atop aFalcon 9launch vehicle, placed the Dragoncapsule intolow Earth orbit,[262] and ended successfully on September 18, 2021, at 23:06:49 UTC,[286] when theResilience splashed down in the Atlantic Ocean. B1062 held the record for the fastest booster turnaround time at 21 days and 4 hours between April 8, 2022 (Axiom-1) and April 29, 2022 (Starlink Group 4–16) beating the previous record of 27 days and 6 hours held by B1060. This was the first time a booster had flown twice in the same calendar month. According to the SpaceX webcast of the Starlink Group 4-16 mission, the booster spent just nine days in refurbishment. This record withstood until B1080 broke it by launching within 14 days between November 11-24, 2024. This booster was the first booster to achieve 20 launches and landings. This booster completed 22 successful launch and landings, before tipping over on its 23rd landing on the droneshipA Shortfall of Gravitas during the Starlink 8-6 mission.[287]
Falcon 9 B1069 launchedSpaceX CRS-24 toISS in December 2021 forNASA. SpaceX achieved the feat of 100 successful orbital rocket booster landings in this mission, coinciding with the sixth anniversary of its first booster landing. The rough seas led to the Octagrabber robot not being able to secure the booster to the deck, leading to both the booster,droneship and the Octagrabber robot being heavily damaged in transit.[288] It took months for SpaceX to refurbish B1069, returning into service only onGroup 4-23 mission in August 2022.
On its next flight forEutelsatHotbird 13F, B1069 included a hosted promotional payload byFIFA, that was a box powered byStarlink containing twoAdidas Al Rihla (the Journey) balls, that were to be used in2022 FIFA World Cup inQatar.[289] These match balls were launched and brought back by landing on the drone-ship surviving the stresses of re-entry. Later, they were taken out and shipped back to Qatar for the World Cup. This was the first payload on a Falcon 9 booster itself and demonstrated the reusability.[290] The balls' flight by SpaceX was, in part, a promotion for the company's Starlink satellite internet service. An associated website invited World Cup attendees to visit the Starlink office in Doha.[291]
Dates of Grasshopper launches
the first time SpaceX had successfully landed the rocket's first stage.
SES officials confirmed this week that satellite and rocket preps are on track for January 30. A recycled Falcon 9 booster stage that first flew 1 May with the U.S. government's classified NROL-76 payload will hoist the GovSat 1 spacecraft toward orbit, and a factory-fresh second stage will finish the job.
it has the dubious honor of being the first reused Block 5 booster to be unintentionally destroyed.
The next military mission to fly on a Falcon Heavy rocket, named USSF-67, will launch the LDPE 3 spacecraft and a Space Force communications satellite in tandem. That launch is scheduled for January, and will use the same Falcon Heavy side boosters flown on the USSF-44 mission, assuming a successful recovery on the landing zones at Cape Canaveral Space Force Station, the Space Force said.
This booster will be used on the Crew-3 mission
WATCH: Grasshopper flies to its highest height to date - 744 m (2441 ft) into the Texas sky. http://youtu.be/9ZDkItO-0a4 This was the last scheduled test for the Grasshopper rig; next up will be low altitude tests of the Falcon 9 Reusable (F9R) development vehicle in Texas followed by high altitude testing in New Mexico.