Loading AI tools
From Wikipedia, the free encyclopedia
A Falcon 9 first-stage booster is a reusable rocket booster used on the Falcon 9 and Falcon Heavy orbital launch vehicles manufactured by SpaceX. 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 a program dedicated to recovery and reuse of these boosters for a significant decrease in launch costs.[citation needed] 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 22 December 2015, on the first flight of the Full Thrust version. Since then, Falcon 9 first-stage boosters have been landed and recovered 343 times out of 355 attempts, including synchronized recoveries of the side-boosters of most Falcon Heavy flights.
In total 42 recovered boosters have been refurbished and subsequently flown at least a second time, with a record of 23 missions and landings carried 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 ten flights, each with only minor refurbishment. This milestone was first achieved by Booster B1051 on the Starlink-27 mission in 2021.[4] The limit has been extended several times, and individual boosters have flown as many as 23 flights.
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[lower-alpha 1] | Version | Launch date (UTC)[6] | Flight No. | Payload[lower-alpha 2] | 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 | 4 June 2010 | F9-001 | Dragon Spacecraft Qualification Unit | Success (SLC‑40)[12] | Failure (ocean) | Destroyed[13] |
B0004 | v1.0 | 8 December 2010 | F9-002 | COTS Demo Flight 1 (Dragon C101) | Success (SLC‑40) | Failure (ocean) | Destroyed[14] |
B0005 | v1.0 | 22 May 2012 | F9-003 | COTS Demo Flight 2 (Dragon C102) | Success (SLC‑40) | No attempt | Expended |
B0006 | v1.0 | 8 October 2012 | F9-004 | CRS-1 (Dragon C103) | Partial success (SLC‑40)[15] | No attempt | Expended |
B0007 | v1.0 | 1 March 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 | 29 September 2013 | F9-006 | CASSIOPE | Success (SLC‑4E) | Failure (ocean) | Destroyed |
B1004 | v1.1 | 3 December 2013 | F9-007 | SES-8 | Success (SLC‑40) | No attempt | Expended[20] |
B1005 | v1.1 | 6 January 2014 | F9-008 | Thaicom 6 | Success (SLC‑40) | No attempt | Expended[20] |
B1006 | v1.1 | 18 April 2014 | F9-009 | CRS-3 (Dragon C105) | Success (SLC‑40) | Controlled (ocean) | Expended |
B1007 | v1.1 | 14 July 2014 | F9-010 | Orbcomm OG2 × 6 | Success (SLC‑40) | Controlled (ocean) | Expended |
B1008 | v1.1 | 5 August 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 | 21 September 2014 | F9-013 | CRS-4 (Dragon C106) | Success (SLC‑40) | Failure (ocean) | Destroyed |
B1011 | v1.1 | 7 September 2014 | F9-012 | AsiaSat 6 / Thaicom 7 | Success (SLC‑40) | No attempt | Expended[20] |
B1012 | v1.1 | 10 January 2015 | F9-014 | CRS-5 (Dragon C107) | Success (SLC‑40) | Failure (JRTI) | Destroyed |
B1013 | v1.1 | 11 February 2015 | F9-015 | DSCOVR | Success (SLC‑40) | Controlled (ocean) | Expended |
B1014 | v1.1 | 2 March 2015 | F9-016 | ABS-3A / Eutelsat 115 West B | Success (SLC‑40) | No attempt | Expended[20] |
B1015 | v1.1 | 14 April 2015 | F9-017 | CRS-6 (Dragon C108) | Success (SLC‑40) | Failure (JRTI) | Destroyed |
B1016 | v1.1 | 27 April 2015 | F9-018 | TürkmenÄlem 52°E / MonacoSAT | Success (SLC‑40) | No attempt | Expended[20] |
B1017 | v1.1 | 17 January 2016 | F9-021 | Jason-3 | Success (SLC‑4E) | Failure (JRTI) | Destroyed |
B1018 | v1.1 | 28 June 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 and supercooled 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 like titanium grid 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 the Falcon Heavy test flight.
S/N | Version | Launch date (UTC)[6] | Flight No.[lower-alpha 1] | Turnaround | Payload[lower-alpha 2] | Launch (pad) | Landing (location) | Fate |
---|---|---|---|---|---|---|---|---|
B1019 | FT | 22 December 2015 | F9-020 | — | Orbcomm OG2 × 11 | Success (SLC‑40) | Success (LZ‑1)[24] | Retired On display at SpaceX headquarters[25][26] |
B1020 | FT | 4 March 2016 | F9-022 | — | SES-9 | Success (SLC‑40) | Failure | Destroyed[27] |
B1021 | FT | 8 April 2016 | F9-023 | — | CRS-8 (Dragon C110)[28] | Success (SLC‑40) | Success (OCISLY) | Retired[29] On display at Dish Network headquarters[30][31] |
30 March 2017 | F9-032 ♺ | 356 days | SES-10[28] | Success (LC‑39A) | Success (OCISLY)[32][33] | |||
B1022 | FT | 6 May 2016 | F9-024 | — | JCSAT-14 | Success (SLC‑40) | Success (OCISLY) | Retired |
B1023 | FT | 27 May 2016 | F9-025 | — | Thaicom 8[34] | Success (SLC‑40) | Success (OCISLY)[35] | Retired[36] On display at Kennedy Space Center Visitor Complex[37][38] |
FH side | 6 February 2018 | FH-001 ♺ | 620 days | Tesla Roadster | Success (LC‑39A) | Success (LZ‑1) | ||
B1024 | FT | 15 June 2016 | F9-026 | — | ABS-2A / Eutelsat 117 West B | Success (SLC‑40) | Failure | Destroyed[39] |
B1025 | FT | 18 July 2016 | F9-027 | — | CRS-9 (Dragon C111)[40] | Success (SLC‑40) | Success (LZ‑1) | Retired[36] |
FH side | 6 February 2018 | FH-001 ♺ | 568 days | Tesla Roadster | Success (LC‑39A) | Success (LZ‑2) | ||
B1026 | FT | 14 August 2016 | F9-028 | — | JCSAT-16 | Success (SLC‑40) | Success (OCISLY)[41] | Retired[36] |
B1027 | FH test | Manufactured in 2016[42][43] | — | — | — | — | — | — |
B1028 | FT | 3 September 2016[44] | —[lower-alpha 3] | — | AMOS-6 | Precluded[46] | Precluded | Destroyed in launch pad explosion[46] |
B1029 | FT | 14 January 2017 | F9-029 | — | Iridium NEXT × 10 (NEXT-1)[47] | Success (SLC‑4E) | Success (JRTI) | Retired[36] |
23 June 2017 | F9-036 ♺ | 160 days | BulgariaSat-1[48] | Success (LC‑39A) | Success (OCISLY)[49] | |||
B1030 | FT | 16 March 2017 | F9-031 | — | EchoStar 23[50] | Success (LC‑39A) | No attempt[51] | Expended |
B1031 | FT | 19 February 2017 | F9-030 | — | CRS-10 (Dragon C112)[52] | Success (LC‑39A) | Success (LZ‑1)[53] | Retired[36] |
11 October 2017 | F9-043 ♺ | 234 days | SES-11[53] | Success (LC‑39A) | Success (OCISLY) | |||
B1032 | FT | 1 May 2017 | F9-033 | — | USA-276 (NROL-76)[54] | Success (LC‑39A) | Success (LZ‑1) | Expended[55] |
31 January 2018 | F9-048 ♺ | 275 days | GovSat-1 / SES-16[56] | Success (SLC‑40) | Controlled (ocean)[lower-alpha 4] | |||
B1033 | FH core | 6 February 2018 | FH-001 | — | Tesla Roadster | Success (LC‑39A) | Failure | Destroyed[57] |
B1034 | FT | 15 May 2017 | F9-034 | — | Inmarsat-5 F4[58] | Success (LC‑39A) | No attempt[51] | Expended |
B1035 | FT | 3 June 2017 | F9-035 | — | CRS-11 (Dragon C106)[59] | Success (LC‑39A) | Success (LZ‑1) | Retired[36] On display at Space Center Houston[60][61] |
15 December 2017 | F9-045 ♺ | 195 days | CRS-13 (Dragon C108)[62] | Success (SLC‑40) | Success (LZ‑1)[63] | |||
B1036 | FT | 25 June 2017 | F9-037 | — | Iridium NEXT × 10 (NEXT-2)[64] | Success (SLC‑4E) | Success (JRTI) | Expended |
23 December 2017 | F9-046 ♺ | 181 days | Iridium NEXT × 10 (NEXT-4)[65] | Success (SLC‑4E) | Controlled (ocean) | |||
B1037 | FT | 5 July 2017 | F9-038 | — | Intelsat 35e[66] | Success (LC‑39A) | No attempt[51] | Expended |
B1038 | FT | 24 August 2017 | F9-040 | — | Formosat-5[67] | Success (SLC‑4E) | Success (JRTI) | Expended |
22 February 2018 | F9-049 ♺ | 182 days | Paz | Success (SLC‑4E) | No attempt[51] | |||
B1039 | FT Block 4 | 14 August 2017 | F9-039 | — | CRS-12 (Dragon C113)[68] | Success (LC‑39A) | Success (LZ‑1) | Expended |
2 April 2018 | F9-052 ♺ | 231 days | CRS-14 (Dragon C110)[69] | Success (SLC‑40) | No attempt[70] | |||
B1040 | FT Block 4 | 7 September 2017 | F9-041 | — | Boeing X-37B (OTV-5)[71] | Success (LC‑39A) | Success (LZ‑1) | Expended |
4 June 2018 | F9-056 ♺ | 270 days | SES-12[72] | Success (SLC‑40)[73] | No attempt[51] | |||
B1041 | FT Block 4 | 9 October 2017 | F9-042 | — | Iridium NEXT × 10 (NEXT-3)[74][75] | Success (SLC‑4E) | Success (JRTI) | Expended |
30 March 2018 | F9-051 ♺ | 172 days | Iridium NEXT × 10 (NEXT-5)[76][77] | Success (SLC‑4E) | No attempt[76] | |||
B1042 | FT Block 4 | 30 October 2017 | F9-044 | — | Koreasat 5A[78] | Success (LC‑39A) | Success (OCISLY) | Retired[3] |
B1043 | FT Block 4 | 8 January 2018 | F9-047 | — | Zuma[79] | Success (SLC‑40)[80] | Success (LZ‑1) | Expended |
22 May 2018 | F9-055 ♺ | 134 days | Iridium NEXT × 5 (NEXT-6) / GRACE-FO × 2 | Success (SLC‑4E) | No attempt[51] | |||
B1044 | FT Block 4 | 6 March 2018 | F9-050 | — | Hispasat 30W-6 | Success (SLC‑40) | No attempt[69] | Expended |
B1045 | FT Block 4 | 18 April 2018 | F9-053 | — | TESS[69] | Success (SLC‑40) | Success (OCISLY) | Expended |
29 June 2018 | F9-057 ♺ | 72 days | CRS-15 (Dragon C111)[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 a Falcon 9 booster or Falcon Heavy side booster.[citation needed] 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 stronger heat shield, upgraded engines, new carbon 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.
Block 5 boosters were initially certified for 10 launches[83] which was increased to 15. A "deep-dive" examination has been performed on Falcon 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 30 May 2020 (Crew Dragon Demo-2), was the only booster with NASA logos. On 11 September 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 is the current fleet leader, having achieved the first 20th, 21st, 22nd and 23rd flight of a booster while being closely matched by B1061.[87] Amongst all B5 boosters, B1058 holds the record for most spacecraft (869) launched to orbit and while the record for most spacecraft mass launched to orbit by a single booster is held by B1062 (313,000 kg (690,000 lb)). B1061 is currently the oldest surviving booster in the Falcon 9 fleet.
As of 21 August 2024[update], SpaceX has put into service a total of 42 new B5 boosters, of which 22 have been destroyed (15 have been expended, five have been lost due to failed landings, and two have been lost during recovery).[45]
S/N[lower-alpha 1] | Type | Launches | Launch date (UTC)[6] | Flight No.[lower-alpha 2] | Turnaround time | Payload[lower-alpha 3] | Launch (pad) |
Landing (location) |
Fate |
---|---|---|---|---|---|---|---|---|---|
B1046 | F9 | 4 | 11 May 2018 | F9-054 | — | Bangabandhu-1[88] | Success (LC‑39A) | Success (OCISLY) | Expended |
7 August 2018 | F9-060 ♺ | 88 days | Telkom-4 Merah Putih[89] | Success (SLC‑40) | Success (OCISLY) | ||||
3 December 2018 | F9-064 ♺ | 118 days | SHERPA (SSO-A) (65 Sats)[88][90] | Success (SLC‑4E) | Success (JRTI) | ||||
19 January 2020[91] | F9-079 ♺ | 412 days | In-Flight Abort Test (Dragon C205)[92] | Successful simulated failure (LC‑39A) |
No attempt | ||||
B1047 | F9 | 3 | 22 July 2018 | F9-058 | — | Telstar 19V[93] | Success (SLC‑40) | Success (OCISLY) | Expended[94] |
15 November 2018 | F9-063 ♺ | 116 days | Es'hail 2[95] | Success (LC‑39A) | Success (OCISLY) | ||||
6 August 2019[96] | F9-074 ♺ | 263 days | AMOS-17[97] | Success (SLC‑40) | No attempt | ||||
B1048 | F9 | 5 | 25 July 2018 | F9-059 | — | Iridium NEXT × 10 (NEXT-7)[93] | Success (SLC‑4E) | Success (JRTI) | Destroyed in landing failure[lower-alpha 4] |
8 October 2018 | F9-062 ♺ | 75 days | SAOCOM 1A[98] | Success (SLC‑4E) | Success (LZ‑4) | ||||
22 February 2019 | F9-068 ♺ | 137 days | Nusantara Satu / Beresheet[99][100] | Success (SLC‑40) | Success (OCISLY) | ||||
11 November 2019 | F9-075 ♺ | 262 days | Starlink × 60 (v1.0 L1) | Success (SLC‑40) | Success (OCISLY) | ||||
18 March 2020 | F9-083 ♺ | 128 days | Starlink × 60 (v1.0 L5)[101] | Success (LC‑39A) | Failure (OCISLY) | ||||
B1049 | F9[lower-alpha 5] | 11 | 10 September 2018 | F9-061 | — | Telstar 18V / Apstar 5C[104] | Success (SLC‑40) | Success (OCISLY) | Expended |
11 January 2019 | F9-067 ♺ | 123 days | Iridium NEXT × 10 (NEXT-8)[105] | Success (SLC‑4E) | Success (JRTI) | ||||
24 May 2019 | F9-071 ♺ | 133 days | Starlink × 60 (v0.9)[106] | Success (SLC‑40) | Success (OCISLY) | ||||
7 January 2020 | F9-078 ♺ | 228 days | Starlink × 60 (v1.0 L2)[107] | Success (SLC‑40) | Success (OCISLY) | ||||
4 June 2020 | F9-086 ♺ | 149 days | Starlink × 60 (v1.0 L7)[108] | Success (SLC‑40) | Success (JRTI) | ||||
18 August 2020 | F9-091 ♺ | 75 days | Starlink × 58 (v1.0 L10)+ Skysat 19-21[109] | Success (SLC‑40) | Success (OCISLY) | ||||
25 November 2020 | F9-100 ♺ | 99 days | Starlink × 60 (v1.0 L15)[110] | Success (SLC‑40) | Success (OCISLY) | ||||
4 March 2021 | F9-109 ♺ | 99 days | Starlink × 60 (v1.0 L17)[111] | Success (LC‑39A) | Success (OCISLY) | ||||
4 May 2021[112] | F9-116 ♺ | 61 days | Starlink × 60 (v1.0 L25) | Success (LC‑39A) | Success (OCISLY) | ||||
14 September 2021 | F9-125 ♺ | 133 days | Starlink × 51 (Group 2-1) | Success (SLC‑4E) | Success (OCISLY) | ||||
23 November 2022 | F9-186 ♺ | 435 days | Eutelsat 10B | Success (SLC‑40) | No attempt | ||||
B1050 | F9 | 1 | 5 December 2018 | F9-065 | — | CRS-16 (Dragon C112)[88] | Success (SLC‑40) | Failure (LZ‑1) | Destroyed in landing failure[lower-alpha 6] |
B1051 | F9 | 14 | 2 March 2019[113] | F9-069 | — | Demo-1 (Dragon C204) ![]() |
Success (LC‑39A) | Success (OCISLY) | Expended |
12 June 2019 | F9-072 ♺ | 102 days | RCM × 3[114] | Success (SLC‑4E) | Success (LZ‑4) | ||||
29 January 2020 | F9-080 ♺ | 231 days | Starlink × 60 (v1.0 L3) | Success (SLC‑40) | Success (OCISLY) | ||||
22 April 2020 | F9-084 ♺ | 84 days | Starlink × 60 (v1.0 L6)[115] | Success (LC‑39A) | Success (OCISLY) | ||||
7 August 2020 | F9-090 ♺ | 107 days | Starlink × 57 (v1.0 L9) | Success (LC‑39A) | Success (OCISLY) | ||||
18 October 2020 | F9-095 ♺ | 72 days | Starlink × 60 (v1.0 L13) | Success (LC‑39A) | Success (OCISLY) | ||||
13 December 2020 | F9-102 ♺ | 56 days | SXM 7[116] | Success (SLC‑40) | Success (JRTI) | ||||
20 January 2021 | F9-105 ♺ | 38 days | Starlink × 60 (v1.0 L16)[117] | Success (LC‑39A) | Success (JRTI) | ||||
14 March 2021 | F9-111 ♺ | 53 days | Starlink × 60 (v1.0 L21)[118] | Success (LC‑39A) | Success (OCISLY) | ||||
9 May 2021[119] | F9-117 ♺ | 56 days | Starlink × 60 (v1.0 L27) | Success (SLC‑40) | Success (JRTI) | ||||
18 December 2021[120][121] | F9-132 ♺ | 228 days | Starlink × 52 (Group 4-4)[122] | Success (SLC‑4E) | Success (OCISLY) | ||||
19 March 2022[120] | F9-145 ♺ | 91 days | Starlink × 53 (Group 4-12) | Success (SLC‑40) | Success (JRTI) | ||||
17 July 2022 | F9-165 ♺ | 120 days | Starlink × 53 (Group 4-22) | Success (SLC‑40) | Success (JRTI) | ||||
12 November 2022 | F9-185 ♺ | 118 days | Galaxy 31 & 32[123] | Success (SLC‑40) | No attempt | ||||
B1052 | FH side | 8 | 11 April 2019 | FH-002 | — | Arabsat-6A[114] | Success (LC‑39A) | Success (LZ‑1)[124] | Expended |
25 June 2019 | FH-003 ♺ | 75 days | COSMIC-2 (STP-2)[114] | Success (LC‑39A) | Success (LZ‑2)[124] | ||||
F9[lower-alpha 7] | 31 January 2022 | F9-138 ♺ | 951 days | CSG-2[126] | Success (SLC‑40) | Success (LZ‑1) | |||
9 March 2022 | F9-144 ♺ | 37 days | Starlink × 48 (Group 4-10)[127] | Success (SLC‑40) | Success (ASOG) | ||||
18 May 2022 | F9-155 ♺ | 70 days | Starlink × 53 (Group 4-18)[128] | Success (LC‑39A) | Success (ASOG) | ||||
4 August 2022 | F9-168 ♺ | 78 days | Danuri (KPLO)[129] | Success (SLC‑40) | Success (JRTI) | ||||
5 September 2022 | F9-174 ♺ | 32 days | Starlink × 51 (Group 4-20)+ Varuna-TDM[130] | Success (SLC‑40) | Success (JRTI) | ||||
FH side | 1 May 2023[131] | FH-006 ♺ | 238 days | ViaSat-3 Americas[131] | Success (LC‑39A) | No attempt[132] | |||
B1053 | FH side | 3 | 11 April 2019 | FH-002 | — | Arabsat-6A[114] | Success (LC‑39A) | Success (LZ‑2)[124] | Expended |
25 June 2019 | FH-003 ♺ | 75 days | COSMIC-2 (STP-2)[114] | Success (LC‑39A) | Success (LZ‑1)[124] | ||||
1 May 2023[131] | FH-006 ♺ | 1406 days | ViaSat-3 Americas[133][131] | Success (LC‑39A) | No attempt[132] | ||||
B1054 | F9 | 1 | 23 December 2018 | F9-066 | — | GPS III SV01[134] | Success (SLC‑40) | No attempt[135] | Expended |
B1055 | FH core | 1 | 11 April 2019 | FH-002 | — | Arabsat-6A | Success (LC‑39A) | Partial failure[lower-alpha 8] (OCISLY) | Destroyed during recovery[lower-alpha 8] |
B1056 | F9 | 4 | 4 May 2019 | F9-070 | — | CRS-17 (Dragon C113) | Success (SLC‑40) | Success (OCISLY) | Destroyed in landing failure[137] |
25 July 2019 | F9-073 ♺ | 82 days | CRS-18 (Dragon C108)[138] | Success (SLC‑40) | Success (LZ‑1) | ||||
17 December 2019 | F9-077 ♺ | 146 days | JCSAT-18 / Kacific-1[139] | Success (SLC‑40) | Success (OCISLY) | ||||
17 February 2020 | F9-081 ♺ | 62 days | Starlink × 60 (v1.0 L4)[140] | Success (SLC‑40) | Failure (OCISLY) | ||||
B1057 | FH core | 1 | 25 June 2019 | FH-003 | — | COSMIC-2 (STP-2)[139] | Success (LC‑39A) | Failure (OCISLY) | Destroyed in landing failure |
B1058![]() |
F9 | 19 | 30 May 2020[141] | F9-085 | — | Demo-2 (Dragon C206 Endeavour)[142] ![]() ![]() |
Success (LC‑39A) | Success (OCISLY) | Destroyed during recovery[lower-alpha 9] |
20 July 2020 | F9-089 ♺ | 51 days | ANASIS-II | Success (SLC‑40) | Success (JRTI) | ||||
6 October 2020[144] | F9-094 ♺ | 78 days | Starlink × 60 (v1.0 L12) | Success (LC‑39A) | Success (OCISLY) | ||||
6 December 2020[145] | F9-101 ♺ | 60 days | CRS-21 (Dragon C208) | Success (LC‑39A) | Success (OCISLY) | ||||
24 January 2021 | F9-106 ♺ | 49 days | Transporter-1 (143 Sats)[146] | Success (SLC‑40) | Success (OCISLY) | ||||
11 March 2021 | F9-110 ♺ | 46 days | Starlink × 60 (v1.0 L20)[147] | Success (SLC‑40) | Success (JRTI) | ||||
7 April 2021 | F9-113 ♺ | 27 days | Starlink × 60 (v1.0 L23) | Success (SLC‑40) | Success (OCISLY) | ||||
15 May 2021 | F9-118 ♺ | 38 days | Starlink × 52 (v1.0 L26)+ Rideshare | Success (LC‑39A) | Success (OCISLY) | ||||
13 November 2021[148] | F9-128 ♺ | 182 days | Starlink × 53 (Group 4-1)[149][150] | Success (SLC‑40) | Success (JRTI) | ||||
13 January 2022 | F9-136 ♺ | 61 days | Transporter-3 (105 Sats)[151] | Success (SLC‑40) | Success (LZ‑1) | ||||
21 February 2022 | F9-141 ♺ | 39 days | Starlink × 46 (Group 4-8) | Success (SLC‑40) | Success (ASOG) | ||||
6 May 2022 | F9-152 ♺ | 73 days | Starlink × 53 (Group 4-17) | Success (LC‑39A) | Success (ASOG) | ||||
7 July 2022 | F9-162 ♺ | 62 days | Starlink × 53 (Group 4-21)[152] | Success (SLC‑40) | Success (JRTI) | ||||
11 September 2022 | F9-175 ♺ | 66 days | Starlink × 34 (Group 4-2) + BlueWalker 3[153] | Success (LC‑39A) | Success (ASOG) | ||||
17 December 2022 | F9-192 ♺ | 97 days | Starlink × 54 (Group 4-37)[154] | Success (LC‑39A) | Success (JRTI) | ||||
10 July 2023 | F9-238 ♺ | 205 days | Starlink v2 × 22 (Group 6-5) | Success (SLC‑40) | Success (JRTI) | ||||
20 September 2023 | F9-257 ♺ | 72 days | Starlink v2 × 22 (Group 6-17) | Success (SLC‑40) | Success (ASOG) | ||||
4 November 2023 | F9-269 ♺ | 45 days | Starlink v2 × 23 (Group 6-26) | Success (SLC‑40) | Success (ASOG) | ||||
23 December 2023 | F9-283 ♺ | 49 days | Starlink v2 × 23 (Group 6-32) | Success (SLC‑40) | Partial failure[lower-alpha 9] (JRTI) | ||||
B1059 | F9 | 6 | 5 December 2019 | F9-076 | — | CRS-19 (Dragon C106) | Success (SLC‑40) | Success (OCISLY) | Destroyed in landing failure[lower-alpha 10] |
7 March 2020[155] | F9-082 ♺ | 93 days | CRS-20 (Dragon C112) | Success (SLC‑40) | Success (LZ‑1) | ||||
13 June 2020 | F9-087 ♺ | 98 days | Starlink × 58 (v1.0 L8)+ Skysat 16-18 | Success (SLC‑40) | Success (OCISLY) | ||||
30 August 2020 | F9-092 ♺ | 78 days | SAOCOM 1B+ Rideshare[109] | Success (SLC‑40) | Success (LZ‑1) | ||||
19 December 2020 | F9-103 ♺ | 111 days | NROL-108[156] | Success (LC‑39A) | Success (LZ‑1) | ||||
16 February 2021 | F9-108 ♺ | 59 days | Starlink × 60 (v1.0 L19)[157] | Success (SLC‑40) | Failure (OCISLY) | ||||
B1060 | F9 | 20 | 30 June 2020[158] | F9-088 | — | GPS III SV03 | Success (SLC‑40) | Success (JRTI) | Expended |
3 September 2020 | F9-093 ♺ | 65 days | Starlink × 60 (v1.0 L11)[159] | Success (LC‑39A) | Success (OCISLY) | ||||
24 October 2020 | F9-096 ♺ | 51 days | Starlink × 60 (v1.0 L14) | Success (SLC‑40) | Success (JRTI) | ||||
8 January 2021 | F9-104 ♺ | 76 days | Türksat 5A[160] | Success (SLC‑40) | Success (JRTI) | ||||
4 February 2021 | F9-107 ♺ | 27 days | Starlink × 60 (v1.0 L18)[161] | Success (SLC‑40) | Success (OCISLY) | ||||
24 March 2021 | F9-112 ♺ | 48 days | Starlink × 60 (v1.0 L22)[162] | Success (SLC‑40) | Success (OCISLY) | ||||
29 April 2021 | F9-115 ♺ | 36 days | Starlink × 60 (v1.0 L24)[163] | Success (SLC‑40) | Success (JRTI) | ||||
30 June 2021 | F9-123 ♺ | 62 days | Transporter-2 (88 Sats)[164] | Success (SLC‑40) | Success (LZ‑1) | ||||
2 December 2021 | F9-130 ♺ | 155 days | Starlink × 48 (Group 4-3)+ BlackSky Global 12-13 | Success (SLC‑40) | Success (ASOG) | ||||
19 January 2022 | F9-137 ♺ | 48 days | Starlink × 49 (Group 4-6) | Success (LC‑39A) | Success (ASOG) | ||||
3 March 2022 | F9-143 ♺ | 43 days | Starlink × 47 (Group 4-9) | Success (LC‑39A) | Success (JRTI) | ||||
21 April 2022 | F9-149 ♺ | 49 days | Starlink × 53 (Group 4-14) | Success (SLC‑40) | Success (JRTI) | ||||
17 June 2022 | F9-158 ♺ | 57 days | Starlink × 53 (Group 4-19)[165] | Success (LC‑39A) | Success (ASOG) | ||||
8 October 2022 | F9-180 ♺ | 113 days | Galaxy 33 & 34[166] | Success (SLC‑40) | Success (ASOG) | ||||
3 January 2023 | F9-195 ♺ | 87 days | Transporter-6 (144 Sats) | Success (SLC‑40) | Success (LZ‑1) | ||||
16 July 2023 | F9-239 ♺ | 194 days | Starlink × 54 (Group 5-15) | Success (SLC‑40) | Success (ASOG) | ||||
24 September 2023 | F9-258 ♺ | 70 days | Starlink v2 × 22 (Group 6-18) | Success (SLC‑40) | Success (JRTI) | ||||
15 February 2024 | F9-299 ♺ | 144 days | IM-1 (Nova-C) Odysseus lander | Success (LC‑39A) | Success (LZ‑1) | ||||
24 March 2024 | F9-313 ♺ | 38 days | Starlink v2 × 23 (Group 6-42) | Success (LC‑39A) | Success (JRTI) | ||||
28 April 2024 | F9-327 ♺ | 35 days | Galileo FOC FM25 & FOC FM27[167] | Success (LC‑39A) | No attempt
| ||||
B1062 | F9 | 23 | 5 November 2020[145] | F9-097 | — | GPS III SV04 | Success (SLC‑40) | Success (OCISLY) | Destroyed in landing failure |
17 June 2021[168] | F9-122 ♺ | 224 days | GPS III SV05 | Success (SLC‑40) | Success (JRTI) | ||||
16 September 2021[169] | F9-126 ♺ | 91 days | Inspiration4 (Dragon C207 Resilience) | Success (LC‑39A) | Success (JRTI) | ||||
6 January 2022 | F9-135 ♺ | 112 days | Starlink × 49 (Group 4-5)[170] | Success (LC‑39A) | Success (ASOG) | ||||
8 April 2022 | F9-147 ♺ | 92 days | Ax-1 (Dragon C206 Endeavour) | Success (LC‑39A) | Success (ASOG) | ||||
29 April 2022 | F9-151 ♺ | 21 days | Starlink × 53 (Group 4-16) | Success (SLC‑40) | Success (JRTI) | ||||
8 June 2022 | F9-157 ♺ | 40 days | Nilesat-301[171] | Success (SLC‑40) | Success (JRTI) | ||||
24 July 2022 | F9-167 ♺ | 46 days | Starlink × 53 (Group 4-25) | Success (LC‑39A) | Success (ASOG) | ||||
19 August 2022 | F9-171 ♺ | 26 days | Starlink × 53 (Group 4-27)[172] | Success (SLC‑40) | Success (ASOG) | ||||
20 October 2022 | F9-182 ♺ | 62 days | Starlink × 54 (Group 4-36)[173] | Success (SLC‑40) | Success (ASOG) | ||||
28 December 2022 | F9-193 ♺ | 69 days | Starlink × 54 (Group 5-1)[174] | Success (SLC‑40) | Success (ASOG) | ||||
12 February 2023 | F9-203 ♺ | 46 days | Starlink × 55 (Group 5-4)[175] | Success (SLC‑40) | Success (ASOG) | ||||
9 March 2023 | F9-209 ♺ | 25 days | OneWeb #17[176] | Success (SLC‑40) | Success (LZ‑1) | ||||
27 May 2023 | F9-227 ♺ | 79 days | ArabSat 7B (Badr-8) | Success (SLC‑40) | Success (JRTI) | ||||
28 July 2023 | F9-242 ♺ | 62 days | Starlink v2 × 22 (Group 6-7)[177] | Success (SLC‑40) | Success (ASOG) | ||||
18 October 2023 | F9-264 ♺ | 82 days | Starlink v2 × 22 (Group 6-23) | Success (SLC‑40) | Success (JRTI) | ||||
28 November 2023 | F9-277 ♺ | 41 days | Starlink v2 × 23 (Group 6-30) | Success (SLC‑40) | Success (JRTI) | ||||
29 January 2024 | F9-293 ♺ | 62 days | Starlink v2 × 23 (Group 6-38) | Success (LC‑39A) | Success (ASOG) | ||||
16 March 2024 | F9-310 ♺ | 47 days | Starlink v2 × 23 (Group 6-44) | Success (LC‑39A) | Success (ASOG) | ||||
13 April 2024 | F9-323 ♺ | 28 days | Starlink v2 × 23 (Group 6-49) | Success (SLC‑40) | Success (ASOG) | ||||
18 May 2024 | F9-336 ♺ | 35 days | Starlink v2 × 23 (Group 6-59) | Success (SLC‑40) | Success (ASOG) | ||||
27 June 2024 | F9-350 ♺ | 40 days | Starlink v2 × 23 (Group 10-3) | Success (SLC‑40) | Success (JRTI) | ||||
28 August 2024 | F9-367 ♺ | 62 days | Starlink v2 × 21 (Group 8-6) | Success (SLC‑40) | Failure (ASOG) | ||||
B1066 | FH core | 1 | 1 November 2022 | FH-004 | — | USSF-44 | Success (LC‑39A) | No attempt | Expended |
B1068 | FH core[133] | 1 | 1 May 2023[131] | FH-006 | — | ViaSat-3 Americas[131] | Success (LC‑39A) | No attempt | Expended[132] |
B1070 | FH core | 1 | 15 January 2023[178] | FH-005 | — | USSF-67 | Success (LC‑39A) | No attempt | Expended |
B1074 | FH core | 1 | 29 July 2023 | FH-007 | — | Jupiter-3 (EchoStar-24) | Success (LC‑39A) | No attempt | Expended |
B1079 | FH core | 1 | 13 October 2023 | FH-008 | — | Psyche[179] | Success (LC‑39A) | No attempt | Expended |
B1084 | FH core | 1 | 29 December 2023 | FH-009 | — | USSF-52 (Boeing X-37B OTV-7) | Success (LC‑39A) | No attempt | Expended |
B1087 | FH core | 1 | 25 June 2024 | FH-010 | — | GOES-U | Success (LC‑39A) | No attempt | Expended |
S/N | Type | Launches | Launch date (UTC)[6] | Flight No.[lower-alpha 1] | Turnaround time | Payload[lower-alpha 2] | Launch (pad) |
Landing (location) |
Status |
---|---|---|---|---|---|---|---|---|---|
B1061 | F9 | 22 | 15 November 2020[145] | F9-098 | — | Crew-1 (Dragon C207 Resilience) ![]() ![]() |
Success (LC‑39A) | Success (JRTI) | Refurbishing |
23 April 2021 | F9-114 ♺ | 159 days | Crew-2 (Dragon C206 Endeavour) ![]() ![]() |
Success (LC‑39A) | Success (OCISLY) | ||||
6 June 2021 | F9-121 ♺ | 44 days | SXM-8[180] | Success (SLC‑40) | Success (JRTI) | ||||
29 August 2021 | F9-124 ♺ | 84 days | CRS-23 (Dragon C208) | Success (LC‑39A) | Success (ASOG) | ||||
9 December 2021 | F9-131 ♺ | 102 days | IXPE | Success (LC‑39A) | Success (JRTI) | ||||
3 February 2022 | F9-140 ♺ | 56 days | Starlink × 49 (Group 4-7)[181] | Success (LC‑39A) | Success (ASOG) | ||||
1 April 2022 | F9-146 ♺ | 57 days | Transporter-4 (40 Sats) | Success (SLC‑40) | Success (JRTI) | ||||
25 May 2022 | F9-156 ♺ | 54 days | Transporter-5 (59 Sats)[182] | Success (SLC‑40) | Success (LZ‑1) | ||||
19 June 2022 | F9-160 ♺ | 25 days | Globalstar FM15+ Rideshare[183] | Success (SLC‑40) | Success (JRTI) | ||||
12 August 2022 | F9-170 ♺ | 54 days | Starlink × 46 (Group 3-3)[184] | Success (SLC‑4E) | Success (OCISLY) | ||||
30 December 2022 | F9-194 ♺ | 140 days | EROS-C3[185] | Success (SLC‑4E) | Success (LZ‑4) | ||||
3 March 2023 | F9-208 ♺ | 63 days | Starlink × 51 (Group 2-7)[186] | Success (SLC‑4E) | Success (OCISLY) | ||||
27 April 2023 | F9-219 ♺ | 55 days | Starlink × 46 (Group 3-5) | Success (SLC‑4E) | Success (OCISLY) | ||||
31 May 2023 | F9-228 ♺ | 34 days | Starlink × 52 (Group 2-10) | Success (SLC‑4E) | Success (OCISLY) | ||||
22 August 2023 | F9-248 ♺ | 83 days | Starlink v2 × 21 (Group 7-1) | Success (SLC‑4E) | Success (OCISLY) | ||||
21 October 2023 | F9-265 ♺ | 60 days | Starlink v2 × 21 (Group 7-5) | Success (SLC‑4E) | Success (OCISLY) | ||||
1 December 2023 | F9-278 ♺ | 41 days | 425 Project + Rideshare (EIRSAT-1) | Success (SLC‑4E) | Success (LZ‑4) | ||||
14 January 2024 | F9-289 ♺ | 44 days | Starlink v2 × 22 (Group 7-10) | Success (SLC‑4E) | Success (OCISLY) | ||||
23 February 2024 | F9-302 ♺ | 40 days | Starlink v2 × 22 (Group 7-15) | Success (SLC‑4E) | Success (OCISLY) | ||||
2 May 2024 | F9-329 ♺ | 69 days | WorldView Legion 1 & 2 | Success (SLC‑4E) | Success (LZ‑4) | ||||
8 June 2024 | F9-345 ♺ | 37 days | Starlink v2 × 20 (Group 8-8) | Success (SLC‑4E) | Success (OCISLY) | ||||
12 August 2024 | F9-362 ♺ | 65 days | ASBM × 2 | Success (SLC‑4E) | Success (OCISLY) | ||||
B1063 | F9 | 19 | 21 November 2020 | F9-099 | — | Sentinel-6A | Success (SLC‑4E) | Success (LZ‑4) | Awaiting Assignment |
26 May 2021[187] | F9-119 ♺ | 186 days | Starlink × 60 (v1.0 L28) | Success (SLC‑40) | Success (JRTI) | ||||
24 November 2021[188] | F9-129 ♺ | 182 days | DART | Success (SLC‑4E) | Success (OCISLY) | ||||
25 February 2022 | F9-142 ♺ | 93 days | Starlink × 50 (Group 4-11) | Success (SLC‑4E) | Success (OCISLY) | ||||
14 May 2022 | F9-153 ♺ | 78 days | Starlink × 53 (Group 4-13)[189] | Success (SLC‑4E) | Success (OCISLY) | ||||
11 July 2022 | F9-163 ♺ | 58 days | Starlink × 46 (Group 3-1) | Success (SLC‑4E) | Success (OCISLY) | ||||
31 August 2022 | F9-173 ♺ | 51 days | Starlink × 46 (Group 3-4)[190] | Success (SLC‑4E) | Success (OCISLY) | ||||
28 October 2022 | F9-183 ♺ | 58 days | Starlink × 53 (Group 4-31)[191] | Success (SLC‑4E) | Success (OCISLY) | ||||
17 February 2023 | F9-204 ♺ | 112 days | Starlink × 51 (Group 2-5) | Success (SLC‑4E) | Success (OCISLY) | ||||
15 April 2023 | F9-217 ♺ | 57 days | Transporter-7 (51 Sats) | Success (SLC‑4E) | Success (LZ‑4) | ||||
20 May 2023 | F9-225 ♺ | 35 days | Iridium NEXT × 5 (NEXT-9) OneWeb #19[192] | Success (SLC‑4E) | Success (OCISLY) | ||||
7 July 2023 | F9-237 ♺ | 48 days | Starlink × 48 (Group 5-13) | Success (SLC‑4E) | Success (OCISLY) | ||||
2 September 2023 | F9-252 ♺ | 57 days | SDA Tranche 0, Flight 2 | Success (SLC‑4E) | Success (LZ‑4) | ||||
9 October 2023 | F9-262 ♺ | 37 days | Starlink v2 × 21 (Group 7-4) | Success (SLC‑4E) | Success (OCISLY) | ||||
20 November 2023 | F9-275 ♺ | 42 days | Starlink v2 × 22 (Group 7-7) | Success (SLC‑4E) | Success (OCISLY) | ||||
24 January 2024 | F9-292 ♺ | 65 days | Starlink v2 × 22 (Group 7-11) | Success (SLC‑4E) | Success (OCISLY) | ||||
11 March 2024 | F9-309 ♺ | 47 days | Starlink v2 × 23 (Group 7-17) | Success (SLC‑4E) | Success (OCISLY) | ||||
14 May 2024 | F9-335 ♺ | 64 days | Starlink v2 × 20 (Group 8-7) | Success (SLC‑4E) | Success (OCISLY) | ||||
12 July 2024 | F9-354 ♺ | 59 days | Starlink v2 × 20 (Group 9-3) | Failure[lower-alpha 3] (SLC‑4E) | Success (OCISLY) | ||||
B1064 | FH side | 5 | 1 November 2022 | FH-004 | — | USSF-44 | Success (LC‑39A) | Success (LZ‑1)[193] | Awaiting Launch |
15 January 2023[194] | FH-005 ♺ | 75 days | USSF-67[195] | Success (LC‑39A) | Success (LZ‑2)[196] | ||||
29 July 2023 | FH-007 ♺ | 195 days | Jupiter-3 (EchoStar-24)[197] | Success (LC‑39A) | Success (LZ‑1) | ||||
13 October 2023 | FH-008 ♺ | 76 days | Psyche[179] | Success (LC‑39A) | Success (LZ‑1) | ||||
29 December 2023 | FH-009 ♺ | 77 days | USSF-52 (Boeing X-37B OTV-7)[198] | Success (LC‑39A) | Success (LZ‑1) | ||||
Planned | 10 October 2024 | FH-xxx ♺ | 286 days | Europa Clipper[199] | Planned (LC‑39A) | No attempt | |||
B1065 | FH side | 5 | 1 November 2022 | FH-004 | — | USSF-44 | Success (LC‑39A) | Success (LZ‑2)[193] | Awaiting Launch |
15 January 2023[194] | FH-005 ♺ | 75 days | USSF-67[195] | Success (LC‑39A) | Success (LZ‑1)[196] | ||||
29 July 2023 | FH-007 ♺ | 195 days | Jupiter-3 (EchoStar-24)[197] | Success (LC‑39A) | Success (LZ‑2) | ||||
13 October 2023 | FH-008 ♺ | 76 days | Psyche[179] | Success (LC‑39A) | Success (LZ‑2) | ||||
29 December 2023 | FH-009 ♺ | 77 days | USSF-52 (Boeing X-37B OTV-7)[198] | Success (LC‑39A) | Success (LZ‑2) | ||||
Planned | 10 October 2024 | FH-xxx ♺ | 286 days | Europa Clipper[199] | Planned (LC‑39A) | No attempt | |||
B1067 | F9 | 21 | 3 June 2021[200] | F9-120 | — | CRS-22 (Dragon C209) | Success (LC‑39A) | Success (OCISLY) | Refurbishing |
11 November 2021 | F9-127 ♺ | 161 days | Crew-3 (Dragon C210 Endurance)[201] ![]() ![]() |
Success (LC‑39A) | Success (ASOG)[202] | ||||
19 December 2021 | F9-133 ♺ | 38 days | Türksat 5B | Success (SLC‑40) | Success (ASOG) | ||||
27 April 2022 | F9-150 ♺ | 129 days | Crew-4 (Dragon C212 Freedom)[203]![]() ![]() |
Success (LC‑39A) | Success (ASOG) | ||||
14 July 2022 | F9-164 ♺ | 78 days | CRS-25 (Dragon C208)[204] | Success (LC‑39A) | Success (ASOG) | ||||
19 September 2022 | F9-176 ♺ | 67 days | Starlink × 54 (Group 4-34)[205] | Success (SLC‑40) | Success (JRTI) | ||||
3 November 2022 | F9-184 ♺ | 45 days | Hotbird 13G[206] | Success (SLC‑40) | Success (JRTI) | ||||
16 December 2022 | F9-191 ♺ | 43 days | O3b mPOWER 1 & 2[207] | Success (SLC‑40) | Success (ASOG) | ||||
26 January 2023 | F9-199 ♺ | 41 days | Starlink × 56 (Group 5-2) | Success (SLC‑40) | Success (JRTI) | ||||
24 March 2023 | F9-213 ♺ | 57 days | Starlink × 56 (Group 5-5) | Success (SLC‑40) | Success (ASOG) | ||||
14 May 2023 | F9-223 ♺ | 51 days | Starlink × 56 (Group 5-9)[208] | Success (SLC‑40) | Success (JRTI) | ||||
18 June 2023 | F9-233 ♺ | 35 days | Satria[209] | Success (SLC‑40) | Success (ASOG) | ||||
17 August 2023 | F9-247 ♺ | 60 days | Starlink v2 × 22 (Group 6-10) | Success (SLC‑40) | Success (ASOG) | ||||
13 October 2023 | F9-263 ♺ | 57 days | Starlink v2 × 22 (Group 6-22) | Success (SLC‑40) | Success (ASOG) | ||||
22 November 2023 | F9-276 ♺ | 40 days | Starlink v2 × 23 (Group 6-29) | Success (SLC‑40) | Success (ASOG) | ||||
7 January 2024 | F9-288 ♺ | 46 days | Starlink v2 × 23 (Group 6-35) | Success (SLC‑40) | Success (ASOG) | ||||
20 February 2024 | F9-301 ♺ | 44 days | Telkomsat Merah Putih 2 (HTS 113BT) | Success (SLC‑40) | Success (JRTI) | ||||
31 March 2024 | F9-316 ♺ | 40 days | Starlink v2 × 23 (Group 6-45) | Success (SLC‑40) | Success (ASOG) | ||||
3 May 2024 | F9-330 ♺ | 33 days | Starlink v2 × 23 (Group 6-55) | Success (SLC‑40) | Success (ASOG) | ||||
5 June 2024 | F9-343 ♺ | 33 days | Starlink v2 × 20 (Group 8-5) | Success (SLC‑40) | Success (JRTI) | ||||
10 August 2024 | F9-361 ♺ | 66 days | Starlink v2 × 21 (Group 8-3) | Success (SLC‑40) | Success (JRTI) | ||||
B1069 | F9 | 18 | 21 December 2021 | F9-134 | — | CRS-24 (Dragon C209) | Success (LC‑39A) | Success (JRTI) | Landed on JRTI |
28 August 2022 | F9-172 ♺ | 250 days | Starlink × 54 (Group 4-23)[210] | Success (SLC‑40) | Success (ASOG) | ||||
15 October 2022 | F9-181 ♺ | 48 days | Hotbird 13F[211] | Success (SLC‑40) | Success (JRTI) | ||||
8 December 2022 | F9-188 ♺ | 54 days | OneWeb #15[212] | Success (LC‑39A) | Success (LZ‑1) | ||||
2 February 2023 | F9-201 ♺ | 56 days | Starlink × 53 (Group 5-3)[213] | Success (LC‑39A) | Success (ASOG) | ||||
17 March 2023 | F9-212 ♺ | 43 days | SES-18 & 19 | Success (SLC‑40) | Success (JRTI) | ||||
4 May 2023 | F9-221 ♺ | 48 days | Starlink × 56 (Group 5-6)[214] | Success (SLC‑40) | Success (ASOG) | ||||
23 June 2023 | F9-235 ♺ | 50 days | Starlink × 56 (Group 5-12) | Success (SLC‑40) | Success (JRTI) | ||||
11 August 2023 | F9-246 ♺ | 49 days | Starlink v2 × 22 (Group 6-9) | Success (SLC‑40) | Success (JRTI) | ||||
30 September 2023 | F9-260 ♺ | 50 days | Starlink v2 × 22 (Group 6-19) | Success (SLC‑40) | Success (ASOG) | ||||
18 November 2023 | F9-274 ♺ | 49 days | Starlink v2 × 23 (Group 6-28) | Success (SLC‑40) | Success (JRTI) | ||||
29 December 2023 | F9-285 ♺ | 41 days | Starlink v2 × 23 (Group 6-36) | Success (SLC‑40) | Success (ASOG) | ||||
25 February 2024 | F9-303 ♺ | 58 days | Starlink v2 × 24 (Group 6-39) | Success (SLC‑40) | Success (ASOG) | ||||
5 April 2024 | F9-318 ♺ | 40 days | Starlink v2 × 23 (Group 6-47) | Success (SLC‑40) | Success (ASOG) | ||||
6 May 2024 | F9-331 ♺ | 31 days | Starlink v2 × 23 (Group 6-57) | Success (SLC‑40) | Success (JRTI) | ||||
8 June 2024 | F9-344 ♺ | 33 days | Starlink v2 × 22 (Group 10-1) | Success (SLC‑40) | Success (ASOG) | ||||
27 July 2024 | F9-355 ♺ | 49 days | Starlink v2 × 23 (Group 10-9) | Success (LC‑39A) | Success (JRTI) | ||||
31 August 2024 | F9-368 ♺ | 35 days | Starlink v2 × 21 (Group 8-10) | Success (SLC‑40) | Success (JRTI) | ||||
B1071 | F9 | 17 | 2 February 2022 | F9-139 | — | NROL-87 | Success (SLC‑4E) | Success (LZ‑4) | Awaiting Assignment |
17 April 2022 | F9-148 ♺ | 74 days | NROL-85 | Success (SLC‑4E) | Success (LZ‑4) | ||||
18 June 2022 | F9-159 ♺ | 62 days | SARah-1 | Success (SLC‑4E) | Success (LZ‑4) | ||||
22 July 2022 | F9-166 ♺ | 34 days | Starlink × 46 (Group 3-2) | Success (SLC‑4E) | Success (OCISLY) | ||||
5 October 2022 | F9-179 ♺ | 75 days | Starlink × 52 (Group 4-29)[215] | Success (SLC‑4E) | Success (OCISLY) | ||||
16 December 2022 | F9-190 ♺ | 72 days | SWOT[216] | Success (SLC‑4E) | Success (LZ‑4) | ||||
31 January 2023 | F9-200 ♺ | 46 days | Starlink × 49 (Group 2-6) + D-Orbit Starfield ION SCV009[217] |
Success (SLC‑4E) | Success (OCISLY) | ||||
17 March 2023 | F9-211 ♺ | 45 days | Starlink × 52 (Group 2-8) | Success (SLC‑4E) | Success (OCISLY) | ||||
12 June 2023 | F9-232 ♺ | 87 days | Transporter-8 (72 Sats) | Success (SLC‑4E) | Success (LZ‑4) | ||||
20 July 2023 | F9-240 ♺ | 38 days | Starlink v2 × 15 (Group 6-15) | Success (SLC‑4E) | Success (OCISLY) | ||||
12 September 2023 | F9-255 ♺ | 54 days | Starlink v2 × 21 (Group 7-2) | Success (SLC‑4E) | Success (OCISLY) | ||||
11 November 2023 | F9-272 ♺ | 60 days | Transporter-9 (113 Sats) | Success (SLC‑4E) | Success (LZ‑4) | ||||
8 December 2023 | F9-281 ♺ | 27 days | Starlink v2 × 22 (Group 7-8) | Success (SLC‑4E) | Success (OCISLY) | ||||
10 February 2024 | F9-297 ♺ | 64 days | Starlink v2 × 22 (Group 7-13) | Success (SLC‑4E) | Success (OCISLY) | ||||
2 April 2024 | F9-317 ♺ | 52 days | Starlink v2 × 22 (Group 7-18) | Success (SLC‑4E) | Success (OCISLY) | ||||
22 May 2024 | F9-337 ♺ | 50 days | NROL-146 (Starshield satellites)[218] | Success (SLC‑4E) | Success (OCISLY) | ||||
28 July 2024 | F9-357 ♺ | 67 days | Starlink v2 × 21 (Group 9-4) | Success (SLC‑4E) | Success (OCISLY) | ||||
B1072 | FH side | 1 | 25 June 2024 | FH-010 | — | GOES-U | Success (LC‑39A) | Success (LZ‑1) | Awaiting Assignment |
B1073 | F9 | 17 | 14 May 2022[219] | F9-154 | — | Starlink × 53 (Group 4-15)[219] | Success (SLC‑40) | Success (JRTI) | Refurbishing |
29 June 2022 | F9-161 ♺ | 46 days | SES-22[220] | Success (SLC‑40) | Success (ASOG) | ||||
10 August 2022 | F9-169 ♺ | 42 days | Starlink × 52 (Group 4-26)[221] | Success (LC‑39A) | Success (ASOG) | ||||
24 September 2022 | F9-177 ♺ | 45 days | Starlink × 52 (Group 4-35)[222] | Success (SLC‑40) | Success (ASOG) | ||||
11 December 2022 | F9-189 ♺ | 78 days | HAKUTO-R Mission 1[223] | Success (SLC‑40) | Success (LZ‑2) | ||||
7 February 2023 | F9-202 ♺ | 58 days | Amazonas Nexus | Success (SLC‑40) | Success (JRTI) | ||||
15 March 2023 | F9-210 ♺ | 36 days | CRS-27 (Dragon C209) | Success (LC‑39A) | Success (ASOG) | ||||
19 April 2023 | F9-218 ♺ | 35 days | Starlink v2 × 21 (Group 6-2) | Success (SLC‑40) | Success (ASOG) | ||||
12 June 2023 | F9-231 ♺ | 54 days | Starlink × 52 (Group 5-11) | Success (SLC‑40) | Success (JRTI) | ||||
4 September 2023 | F9-253 ♺ | 84 days | Starlink v2 × 21 (Group 6-12) | Success (LC‑39A) | Success (JRTI) | ||||
8 November 2023 | F9-270 ♺ | 65 days | Starlink v2 × 23 (Group 6-27) | Success (SLC‑40) | Success (JRTI) | ||||
15 January 2024 | F9-290 ♺ | 68 days | Starlink v2 × 23 (Group 6-37) | Success (SLC‑40) | Success (ASOG) | ||||
4 March 2024 | F9-307 ♺ | 49 days | Starlink v2 × 23 (Group 6-41) | Success (SLC‑40) | Success (ASOG) | ||||
7 April 2024 | F9-320 ♺ | 34 days | Bandwagon-1 (11 Sats) | Success (LC‑39A) | Success (LZ‑1) | ||||
13 May 2024 | F9-334 ♺ | 36 days | Starlink v2 × 23 (Group 6-58) | Success (SLC‑40) | Success (ASOG) | ||||
3 July 2024 | F9-352 ♺ | 51 days | Starlink v2 × 20 (Group 8-9) | Success (SLC‑40) | Success (ASOG) | ||||
12 August 2024 | F9-363 ♺ | 40 days | Starlink v2 × 23 (Group 10-7) | Success (LC‑39A) | Success (ASOG) | ||||
B1075 | F9 | 12 | 19 January 2023 | F9-198 | — | Starlink × 51 (Group 2-4) | Success (SLC‑4E) | Success (OCISLY) | Refurbishing |
2 April 2023 | F9-215 ♺ | 73 days | SDA Tranche 0, Flight 1 | Success (SLC‑4E) | Success (LZ‑4) | ||||
10 May 2023 | F9-222 ♺ | 38 days | Starlink × 51 (Group 2-9) | Success (SLC‑4E) | Success (OCISLY) | ||||
22 June 2023 | F9-234 ♺ | 43 days | Starlink × 47 (Group 5-7) | Success (SLC‑4E) | Success (OCISLY) | ||||
8 August 2023 | F9-245 ♺ | 47 days | Starlink v2 × 15 (Group 6-20) | Success (SLC‑4E) | Success (OCISLY) | ||||
25 September 2023 | F9-259 ♺ | 48 days | Starlink v2 × 21 (Group 7-3) | Success (SLC‑4E) | Success (OCISLY) | ||||
29 October 2023 | F9-267 ♺ | 34 days | Starlink v2 × 22 (Group 7-6) | Success (SLC‑4E) | Success (OCISLY) | ||||
24 December 2023 | F9-284 ♺ | 56 days | SARah 2 & 3 | Success (SLC‑4E) | Success (LZ‑4) | ||||
29 January 2024 | F9-294 ♺ | 36 days | Starlink v2 × 22 (Group 7-12) | Success (SLC‑4E) | Success (OCISLY) | ||||
19 March 2024 | F9-311 ♺ | 50 days | Starlink v2 × 22 (Group 7-16)+ Rideshare | Success (SLC‑4E) | Success (OCISLY) | ||||
24 June 2024 | F9-349 ♺ | 97 days | Starlink v2 × 20 (Group 9-2) | Success (SLC‑4E) | Success (OCISLY) | ||||
16 August 2024 | F9-365 ♺ | 53 days | Transporter-11 (116 Sats) | Success (SLC‑4E) | Success (LZ‑4) | ||||
B1076 | F9 | 16 | 26 November 2022 | F9-187 | — | CRS-26 (Dragon C211) | Success (LC‑39A) | Success (JRTI) | Refurbishing |
10 January 2023 | F9-196 ♺ | 45 days | OneWeb Flight 16 | Success (SLC‑40) | Success (LZ‑1) | ||||
27 February 2023 | F9-206 ♺ | 48 days | Starlink v2 × 21 (Group 6-1)[224] | Success (SLC‑40) | Success (ASOG) | ||||
7 April 2023 | F9-216 ♺ | 39 days | Intelsat 40e/Tempo | Success (SLC‑40) | Success (ASOG) | ||||
19 May 2023 | F9-224 ♺ | 42 days | Starlink v2 × 22 (Group 6-3) | Success (SLC‑40) | Success (ASOG) | ||||
24 July 2023 | F9-241 ♺ | 66 days | Starlink v2 × 22 (Group 6-6) | Success (SLC‑40) | Success (JRTI) | ||||
9 September 2023 | F9-254 ♺ | 47 days | Starlink v2 × 22 (Group 6-14) | Success (SLC‑40) | Success (ASOG) | ||||
5 October 2023 | F9-261 ♺ | 26 days | Starlink v2 × 22 (Group 6-21) | Success (SLC‑40) | Success (JRTI) | ||||
12 November 2023 | F9-273 ♺ | 38 days | O3b mPOWER 5 & 6 | Success (SLC‑40) | Success (ASOG) | ||||
3 January 2024 | F9-287 ♺ | 52 days | Ovzon-3 | Success (SLC‑40) | Success (LZ‑1) | ||||
29 February 2024 | F9-304 ♺ | 57 days | Starlink v2 × 23 (Group 6-40) | Success (SLC‑40) | Success (JRTI) | ||||
30 March 2024 | F9-315 ♺ | 30 days | Eutelsat 36D | Success (LC‑39A) | Success (JRTI) | ||||
28 April 2024 | F9-328 ♺ | 29 days | Starlink v2 × 23 (Group 6-54) | Success (SLC‑40) | Success (JRTI) | ||||
1 June 2024 | F9-342 ♺ | 34 days | Starlink v2 × 23 (Group 6-64) | Success (SLC‑40) | Success (ASOG) | ||||
8 July 2024 | F9-353 ♺ | 37 days | Türksat 6A | Success (SLC‑40) | Success (JRTI) | ||||
15 August 2024 | F9-364 ♺ | 38 days | WorldView Legion 3 & 4 | Success (SLC‑40) | Success (LZ‑1) | ||||
B1077 | F9 | 14 | 5 October 2022 | F9-178 | — | Crew-5 (Dragon C210 Endurance) ![]() ![]() |
Success (LC‑39A) | Success (JRTI) | Awaiting Assignment |
18 January 2023 | F9-197 ♺ | 105 days | GPS III SV06[225] | Success (SLC‑40) | Success (ASOG) | ||||
18 February 2023 | F9-205 ♺ | 31 days | Inmarsat 6-F2[226] | Success (SLC‑40) | Success (JRTI) | ||||
29 March 2023 | F9-214 ♺ | 39 days | Starlink × 56 (Group 5-10) | Success (SLC‑40) | Success (JRTI) | ||||
5 June 2023 | F9-230 ♺ | 68 days | CRS-28 (Dragon C208) | Success (LC‑39A) | Success (ASOG) | ||||
3 August 2023 | F9-243 ♺ | 59 days | Galaxy 37[227] | Success (SLC‑40) | Success (JRTI) | ||||
1 September 2023 | F9-251 ♺ | 29 days | Starlink v2 × 22 (Group 6-13) | Success (SLC‑40) | Success (ASOG) | ||||
30 October 2023 | F9-268 ♺ | 59 days | Starlink v2 × 23 (Group 6-25) | Success (SLC‑40) | Success (JRTI) | ||||
7 December 2023 | F9-280 ♺ | 38 days | Starlink v2 × 23 (Group 6-33) | Success (SLC‑40) | Success (JRTI) | ||||
30 January 2024 | F9-295 ♺ | 54 days | CRS NG-20[228] | Success (SLC‑40) | Success (LZ‑1) | ||||
10 March 2024 | F9-308 ♺ | 40 days | Starlink v2 × 23 (Group 6-43) | Success (SLC‑40) | Success (JRTI) | ||||
17 April 2024 | F9-324 ♺ | 38 days | Starlink v2 × 23 (Group 6-51) | Success (LC‑39A) | Success (JRTI) | ||||
24 May 2024 | F9-339 ♺ | 37 days | Starlink v2 × 23 (Group 6-63) | Success (LC‑39A) | Success (JRTI) | ||||
28 July 2024 | F9-356 ♺ | 65 days | Starlink v2 × 23 (Group 10-4) | Success (SLC‑40) | Success (ASOG) | ||||
B1078 | F9 | 12 | 2 March 2023 | F9-207 | — | Crew-6 (Dragon C206 Endeavour)![]() ![]() |
Success (LC‑39A) | Success (JRTI) | Awaiting Assignment |
28 April 2023 | F9-220 ♺ | 57 days | O3b mPOWER 3 & 4 | Success (SLC‑40) | Success (JRTI) | ||||
4 June 2023 | F9-229 ♺ | 37 days | Starlink v2 × 22 (Group 6-4) | Success (SLC‑40) | Success (JRTI) | ||||
7 August 2023 | F9-244 ♺ | 64 days | Starlink v2 × 22 (Group 6-8) | Success (SLC‑40) | Success (ASOG) | ||||
16 September 2023 | F9-256 ♺ | 40 days | Starlink v2 × 22 (Group 6-16) | Success (SLC‑40) | Success (JRTI) | ||||
3 December 2023 | F9-279 ♺ | 78 days | Starlink v2 × 23 (Group 6-31) | Success (SLC‑40) | Success (ASOG) | ||||
14 February 2024 | F9-298 ♺ | 73 days | USSF-124 | Success (SLC‑40) | Success (LZ‑2) | ||||
25 March 2024 | F9-314 ♺ | 40 days | Starlink v2 × 23 (Group 6-46) | Success (SLC‑40) | Success (ASOG) | ||||
23 April 2024 | F9-326 ♺ | 29 days | Starlink v2 × 23 (Group 6-53) | Success (SLC‑40) | Success (JRTI) | ||||
28 May 2024 | F9-340 ♺ | 35 days | Starlink v2 × 23 (Group 6-60) | Success (SLC‑40) | Success (ASOG) | ||||
23 June 2024 | F9-348 ♺ | 26 days | Starlink v2 × 22 (Group 10-2) | Success (SLC‑40) | Success (ASOG) | ||||
2 August 2024 | F9-358 ♺ | 40 days | Starlink v2 × 23 (Group 10-6) | Success (LC‑39A) | Success (ASOG) | ||||
B1080 | F9 | 10 | 21 May 2023 | F9-226 | — | Ax-2 (Dragon C212 Freedom) | Success (LC‑39A) | Success (LZ‑1) | Awaiting Assignment |
1 July 2023 | F9-236 ♺ | 41 days | Euclid | Success (SLC‑40) | Success (ASOG) | ||||
27 August 2023 | F9-250 ♺ | 57 days | Starlink v2 × 22 (Group 6-11) | Success (SLC‑40) | Success (JRTI) | ||||
22 October 2023 | F9-266 ♺ | 56 days | Starlink v2 × 23 (Group 6-24) | Success (SLC‑40) | Success (ASOG) | ||||
18 January 2024 | F9-291 ♺– | 88 days | Ax-3 (Dragon C212 Freedom) | Success (LC‑39A) | Success (LZ‑1) | ||||
21 March 2024 | F9-312 ♺ | 63 days | CRS-30 (Dragon C209) | Success (SLC‑40) | Success (LZ‑1) | ||||
18 April 2024 | F9-325 ♺ | 28 days | Starlink v2 × 23 (Group 6-52) | Success (SLC‑40) | Success (ASOG) | ||||
23 May 2024 | F9-338 ♺ | 35 days | Starlink v2 × 23 (Group 6-62) | Success (SLC‑40) | Success (ASOG) | ||||
20 June 2024 | F9-347 ♺ | 28 days | Astra 1P/SES-24[229] | Success (SLC‑40) | Success (JRTI) | ||||
4 August 2024 | F9-360 ♺ | 45 days | CRS NG-21 | Success (SLC‑40) | Success (LZ‑1) | ||||
B1081 | F9 | 9 | 26 August 2023 | F9-249 | — | Crew-7 (Dragon C210 Endurance)![]() ![]() |
Success (LC‑39A) | Success (LZ‑1) | Landed on OCISLY |
10 November 2023 | F9-271 ♺ | 76 days | CRS-29 (Dragon C211) | Success (LC‑39A) | Success (LZ‑1) | ||||
19 December 2023 | F9-282 ♺ | 39 days | Starlink v2 × 23 (Group 6-34) | Success (SLC‑40) | Success (ASOG) | ||||
8 February 2024 | F9-296 ♺ | 51 days | PACE | Success (SLC‑40) | Success (LZ‑1) | ||||
4 March 2024 | F9-306 ♺ | 25 days | Transporter-10 (53 Sats) | Success (SLC‑4E) | Success (LZ‑4) | ||||
7 April 2024 | F9-319 ♺ | 34 days | Starlink v2 × 21 (Group 8-1) | Success (SLC‑4E) | Success (OCISLY) | ||||
28 May 2024 | F9-341 ♺ | 51 days | EarthCARE | Success (SLC‑4E) | Success (LZ‑4) | ||||
29 June 2024 | F9-351 ♺ | 32 days | NROL-186 (Starshield satellites) | Success (SLC‑4E) | Success (OCISLY) | ||||
31 August 2024 | F9-369 ♺ | 63 days | Starlink v2 × 21 (Group 9-5) | Success (SLC‑4E) | Success (OCISLY) | ||||
B1082 | F9 | 6 | 3 January 2024 | F9-286 | — | Starlink v2 × 21 (Group 7-9) | Success (SLC‑4E) | Success (OCISLY) | Refurbishing |
15 February 2024 | F9-300 ♺ | 43 days | Starlink v2 × 22 (Group 7-14) | Success (SLC‑4E) | Success (OCISLY) | ||||
11 April 2024 | F9-322 ♺ | 56 days | USSF-62 (WSF-M 1) | Success (SLC‑4E) | Success (LZ‑4) | ||||
10 May 2024 | F9-333 ♺ | 29 days | Starlink v2 × 20 (Group 8-2) | Success (SLC‑4E) | Success (OCISLY) | ||||
19 June 2024 | F9-346 ♺ | 40 days | Starlink v2 × 20 (Group 9-1)[230] | Success (SLC‑4E) | Success (OCISLY) | ||||
4 August 2024 | F9-359 ♺ | 46 days | Starlink v2 × 23 (Group 11-1) | Success (SLC‑4E) | Success (OCISLY) | ||||
B1083 | F9 | 3 | 4 March 2024 | F9-305 | — | Crew-8 (Dragon C206 Endeavour) ![]() ![]() |
Success (LC‑39A) | Success (LZ‑1) | Awaiting Launch |
10 April 2024 | F9-321 ♺ | 37 days | Starlink v2 × 23 (Group 6-48) | Success (SLC‑40) | Success (JRTI) | ||||
8 May 2024 | F9-332 ♺ | 28 days | Starlink v2 × 23 (Group 6-56) | Success (LC‑39A) | Success (ASOG) | ||||
Planned | September 2024 | F9-xxx ♺ | 145 days | Polaris Dawn (Dragon C207 Resilience) | Planned (LC‑39A) | Planned (Droneship) | |||
B1085 | F9 | 1 | 20 August 2024 | F9-366 | — | Starlink v2 × 22 (Group 10-5) | Success (SLC‑40) | Success (ASOG) | Refurbishing |
Planned | 24 September 2024 | F9-xxx ♺ | 35 days | Crew-9 (Dragon C212 Freedom) ![]() ![]() |
Planned (SLC‑40) | Planned (LZ‑1) | |||
B1086 | FH side | 1 | 25 June 2024 | FH-010 | — | GOES-U | Success (LC‑39A) | Success (LZ‑2) | Awaiting Assignment |
B1088 | F9 | Planned | 2024 | F9-xxx | — | Unknown | Planned (Unknown) | Planned (Unknown) | Testing at McGregor |
B1090 | FH core | Planned | 10 October 2024 | FH-xxx | — | Europa Clipper[199] | Planned (LC‑39A) | No attempt | Awaiting Launch |
Rockets from the Falcon 9 family have been launched 379 times over 14 years, resulting in 376 full successes (99.21%), two in-flight failures (SpaceX CRS-7 and Starlink Group 9-3), and one partial success (SpaceX CRS-1, which delivered its cargo to the International Space Station (ISS), but a secondary payload was stranded in a lower-than-planned orbit). Additionally, one rocket and its payload (AMOS-6) were destroyed before launch in preparation for an on-pad static fire test. The active version of the rocket, the Falcon 9 Block 5, has flown 311 times successfully.
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 by Soyuz-U, which had 47 launches (45 successful) in 1979.[231] In 2023, the Falcon family of rockets (including the Falcon Heavy) had 96 successful launches, surpassing the 63 launches (61 successful) of the R-7 rocket family in 1980.[lower-alpha 1][232]
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.[233] With each iteration, the Falcon 9 has become more powerful and capable of vertical landing. As vertical landings became more commonplace, SpaceX focused on streamlining the refurbishment process for boosters, making it faster and more cost-effective.[4]
The Falcon 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 aerodynamic nosecone instead of the usual interstage.[234]
Falcon 9 first-stage boosters landed successfully in 343 of 355 attempts (96.6%), with 318 out of 323 (98.5%) for the Falcon 9 Block 5 version. A total of 314 re-flights of first stage boosters have all successfully launched their payloads.
This chart displays the turnaround time, in months, between two flights of each booster. As of August 2024, the shortest turnaround time was 21 days, for the sixth flight of B1062. 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 31 August 2024, Block 5 made 313 flights with 28 boosters (11.2 flights per booster) with Falcon 9.
This chart shows how many 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).
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.
Most Falcon 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).[235] The booster used for Grasshopper 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.[236] Grasshopper made its eighth, and final, test flight on 7 October 2013, flying to an altitude of 744 m (2,441 ft) before making its eighth successful vertical landing.[237] Grasshopper is retired.[11]
Falcon 9 B1019 was the first Full Thrust booster, and was first launched on 22 December 2015 for Falcon 9 flight 20 and landed on the Landing Zone 1 (LZ‑1) at Cape Canaveral. It became the first orbital-class rocket booster to perform a successful return to launch site and vertical landing.[238][239][240]
SpaceX decided not to fly the booster again.[241] Rather, the rocket was moved a few miles north, refurbished by SpaceX at the adjacent Kennedy 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.[242][238] The historic booster is on display outside SpaceX headquarters in Hawthorne, 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 8 April 2016 carrying a Dragon spacecraft and Bigelow Expandable Activity Module (BEAM) on the SpaceX CRS-8 mission and landed on an autonomous spaceport drone ship (ASDS). After recovery, inspections and refurbishing, it was launched again on 30 March 2017 for the SES-10 mission and recovered successfully a second time. This event marks a milestone in SpaceX's drive to develop reusable rockets and reduce launch costs.[28][243][244][245][246] Following the second flight, SpaceX stated that they plan to retire this booster and donate it to Cape Canaveral for public display.[247][248] It was later put on public display outside Dish Network's headquarters in Littleton, Colorado in October 2023.[30]
B1023 became the third orbital-class rocket to land on a droneship after launching Thaicom 8 into a geostationary transfer orbit on 27 May 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,[249][250] but the rocket arrived safely at Port Canaveral.[251] B1025[252] successfully launched the CRS-9 resupply mission on its maiden flight on 18 July 2016 and landed on LZ-1, being the first after B1019 to do so.[253] The mission carried a new docking adapter specifically designed for autonomous spacecraft to the ISS in preparation for Dragon 2 resupply and Commercial Crew missions.[254]
B1023 and B1025 were assigned the role of side boosters for the Falcon 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.[255] The maiden flight of Falcon Heavy on 6 February 2018 launched SpaceX CEO Elon Musk's Tesla 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.[256]
B1023 is on display at the Kennedy 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 11 May 2018, carrying Bangabandhu-1, Bangladesh's first geostationary communications satellite. This marked the 54th flight of the Falcon 9 and the first flight of the Falcon 9 Block 5.[257] After completing a successful ascent, B1046 landed on the drone ship Of Course I Still Love You. After inspection and refurbishment, B1046 was launched a second time on 7 August 2018, carrying the Telkom-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.[258] Four months after the Telkom-4 mission, B1046 arrived at Vandenberg Air Force Base to support the SSO-A mission. Following delays for additional satellite checks,[259] liftoff occurred from SLC-4E on 3 December 2018. This marked the first time that the same orbital-class booster flew three times.[260] Its fourth and last mission launched a Crew Dragon capsule up to the point of maximum dynamic pressure, where it separated from the rocket to test its abort system in flight to validate the system's safety for crews. After separation of Falcon and Dragon, B1046 was compromised 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 a Merlin engine failed since the failure during the SpaceX CRS-1 in October 2012. The primary mission was unaffected and the Starlink payload deployed successfully,[261] 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.[262]
B1049 was the oldest Falcon 9 booster on active duty until its last flight on Nov 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 eighth Iridium NEXT batch, and eight internal Starlink batches.[263] 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 on November 22, 2022. This mission was its last flight.
B1050 launched for the first time on 5 December 2018.[264][265] 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.[266]
No future flights for B1050 were planned, and it was scrapped due to its damage.[267]
B1051 was the sixth Falcon 9 Block 5 booster built. On its maiden flight on 2 March 2019, it carried a Crew Dragon into orbit on the Demo-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 18 December 2021, it flew for a record 11th time.[268] It was the first booster to be used eight, nine, ten, eleven, and twelve times respectively. It flew for the final time on 12 November 2022 for the Intelsat G-31/G-32 mission, and was expended.
B1056 first launched on 4 May 2019, carrying a Cargo Dragon to the ISS. Because of the failure of the static test fire of Crew Dragon C204's Super-Draco abort engines on LZ-1, it landed on a drone ship instead.[269] It flew three more times. On 17 February 2020, B1056 was planned to perform the 50th orbital-class rocket landing, just 27 days after its previous launch.[270] 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 30 May 2020, from Kennedy Space Center Launch Complex 39A (Apollo 11 launch site). It carried NASA astronauts Doug Hurley and Bob Behnken to the International Space Station. It was the first crewed orbital spaceflight launched from the United States since the final Space Shuttle mission, and the first crewed flight test of Dragon 2. It was the first crewed orbital spaceflight by a private company. The booster was the first and only Falcon 9 booster to feature NASA's worm logo and meatball insignia, which was reintroduced after last being used in 1992.[271]
On 11 September 2022, it flew for the 14th time and became the first booster to be recovered 14 times.[272] On 17 December 2022, it was also the first booster to fly and land for the 15th time.[273] On 10 July 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.[274]
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.[275]
B1060 first flew on 30 June 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 25 December 2023, it was assigned to what would become the first successful commercial Lunar landing: the booster launched IM-1 on 15 February 2024. This was its eighteenth mission.[276]
Falcon 9 B1061 first launched Crew-1 to the ISS in November 2020, the first operational flight of Crew Dragon, and landed on a drone ship.[277] It became the first booster to fly crew twice as well as the first reused booster to fly crew as a part of the Crew-2 mission.[278] This first stage went on to complete additional missions.[180] B1061 is the only booster to land on all of SpaceX's different landing zones and drone ships (not including LZ-2).
Falcon 9 B1062 launched Inspiration4 in 2021, operated by SpaceX on behalf of Shift4 Payments CEO Jared Isaacman.[279] The mission launched the Crew Dragon Resilience on 16 September 2021 at 00:02:56 UTC[lower-alpha 1] from the Florida Kennedy Space Center's Launch Complex 39A atop a Falcon 9 launch vehicle, placed the Dragon capsule into low Earth orbit,[257] and ended successfully on 18 September 2021 at 23:06:49 UTC,[280] when the Resilience splashed down in the Atlantic Ocean. B1062 holds the record for the fastest booster turnaround time at 21 days and 4 hours between 8 April 2022 (Axiom-1) and 29 April 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 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 droneship A Shortfall of Gravitas during the Starlink 8-6 mission.[281]
Falcon 9 B1069 launched SpaceX CRS-24 to ISS in December 2021 for NASA. 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.[282] It took months for SpaceX to refurbish B1069, returning into service only on Group 4-23 mission in August 2022.
On its next flight for Eutelsat Hotbird 13F, B1069 included a hosted promotional payload by FIFA, that was a box powered by Starlink containing two Adidas Al Rihla (the Journey) balls, that were to be used in 2022 FIFA World Cup in Qatar.[283] 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.[284] 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.[285]
Seamless Wikipedia browsing. On steroids.
Every time you click a link to Wikipedia, Wiktionary or Wikiquote in your browser's search results, it will show the modern Wikiwand interface.
Wikiwand extension is a five stars, simple, with minimum permission required to keep your browsing private, safe and transparent.