List of Falcon 9 and Falcon Heavy launches

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Falcon 9 Flight 16 night launch from Cape Canaveral on March 2, 2015

This is a list of missions, historic and planned, for the SpaceX Falcon 9 family of launch vehicles. The five versions of the rocket are the Falcon 9 v1.0, Falcon 9 v1.1 (both retired), the currently-operational Falcon 9 Full Thrust, and the in-development Falcon Heavy and Falcon 9 Block 5.

Notable missions

Maiden launch

Launch of Falcon 9 Flight 1 with a boilerplate Dragon

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The Falcon 9 maiden launch occurred on June 4, 2010 and was deemed a success, placing the test payload within 1 percent of the intended orbit. The second stage engine performed a short second burn to demonstrate its multiple firing capability.[1]

The rocket experienced "a little bit of roll at liftoff" as Ken Bowersox from SpaceX put it.[2] This roll had stopped prior to the craft reaching the top of the tower. The second stage began to slowly roll near the end of its burn, which was not expected.[1]

The halo from the venting of propellant from the Falcon 9 second stage as it rolled in space could be seen from all of Eastern Australia where some believed it to be a UFO.[3][4]

COTS demo missions

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The second launch of Falcon 9 was called COTS Demo Flight 1, aiming to test an operational Dragon capsule. The launch took place on December 8, 2010.[5] The booster placed the Dragon spacecraft in a roughly 300-kilometer (190 mi) orbit. After two orbits, the capsule re-entered the atmosphere to be recovered off the coast of Mexico.[6] This flight tested the pressure vessel integrity, attitude control using the Draco thrusters, telemetry, guidance, navigation, control systems, the PICA-X heat shield, and parachutes at speed. The "secret" test payload on this mission was a wheel of cheese.

The NASA COTS qualification program included two more test flights Demo 2 and Demo 3 whose objectives were combined into a single Dragon C2+ mission, on condition that all Demo 2 milestones would be validated in space before proceeding with the ultimate demonstration goal: berthing Dragon to the International Space Station and delivering its cargo. After clearing a few readiness delays and a launch abort, the Dragon capsule was propelled to orbit on May 22, 2012 and tested its positioning system, solar panels, grapple fixture and proximity navigation sensors. Over the next two days, the spacecraft performed a series of maneuvers to catch up to the ISS orbit and prove its rendezvous capabilities at safe distances. On May 24, all the Demo 2 milestones had been successfully cleared and NASA approved the extended mission. On May 25, Dragon performed a series of close approach maneuvers until reaching its final hold position a mere 9 meters away from the Harmony nadir docking port.[7] Astronaut Don Pettit subsequently grabbed the spacecraft with the station's robotic arm. On the next day, May 26 at 09:53 UTC, Pettit opened the hatch and remarked that Dragon "smells like a brand new car."[8] Over the next few days, ISS crew unloaded the incoming cargo and filled Dragon with Earth-bound items such as experiment samples and unneeded hardware. The spacecraft was released on May 31 at 09:49 UTC and successfully completed all the return procedures: unberthing, maneuvering away from the ISS, deorbit burn, trunk jettison, atmospheric reentry, parachute deployment and ocean splashdown.[9]

With successful completion of these demo missions, Falcon 9 became the first fully commercially developed launcher to deliver a payload to the International Space Station, paving the way for SpaceX and NASA to sign the first Commercial Resupply Services agreement[10] for 12 cargo deliveries starting in October 2012. The historic Dragon C2+ capsule is now on display hanging from the ceiling at SpaceX headquarters.

CRS-1

Dragon CRS-1 berthed to the ISS on October 14, 2012, photographed from the Cupola

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The first operational cargo resupply mission to ISS was launched on October 7, 2012 at 8:35 PM EST. At 76 seconds after liftoff, engine 1 of the first stage suffered a loss of pressure which caused an automatic shutdown of that engine. The remaining eight first-stage engines continued to burn and the Dragon capsule reached orbit successfully. This was the first demonstration of SpaceX Falcon 9 "engine out" capability in flight.[11][12]

Due to safety regulations required by NASA, the secondary Orbcomm-2 satellite payload was released into a lower-than-intended orbit, and subsequently declared a total loss.[13] NASA requires a greater-than-99% estimated probability that the stage of any secondary payload on a similar orbital inclination to the Station will reach its orbital goal above the station. Due to the original engine failure, the Falcon 9 used more fuel than intended, bringing this estimate down to around 95%. Because of this, the second stage did not attempt another burn, and Orbcomm-G2 was deployed into a rapidly decaying orbit[13] and burned up in Earth's atmosphere within 4 days after the launch.[13][14] The mission continued to rendezvous and berth the Dragon capsule with the ISS where the ISS crew unloaded its payload and reloaded it with cargo for return to Earth.

Maiden flight of Falcon 9 v1.1

SpaceX Falcon 9 v1.1 launch from Vandenberg with CASSIOPE

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

SpaceX launched the maiden flight of the Falcon 9 v1.1—an essentially new launch vehicle, much larger and with greater thrust than Falcon 9 v1.0—on September 29, 2013, a demonstration launch.[15] Although the rocket carried CASSIOPE as a primary payload, CASSIOPE had a payload mass that is very small relative to the rocket's capability, and it did so at a discounted rate—approximately 20% of the normal published price for SpaceX Falcon 9 LEO missions—because the flight was a technology demonstration mission for SpaceX.[16][17][18]

After the second stage separated from the booster stage, SpaceX conducted a novel high-altitude, high-velocity flight test, wherein the booster attempted to reenter the lower atmosphere in a controlled manner and decelerate to a simulated over-water landing. The test was successful, but the booster stage was not recovered.

Loss of CRS-7 mission

SpaceX CRS-7 disintegrating two minutes after liftoff, as seen from a NASA tracking camera

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

On June 28, 2015, Falcon 9 Flight 19 carried a Dragon capsule on the seventh Commercial Resupply Services mission to the International Space Station. The second stage disintegrated due to an internal helium tank failure while the first stage was still burning normally. This was the first primary mission loss for any Falcon 9 rocket.[19] In addition to ISS consumables and experiments, this mission carried the first International Docking Adapter (IDA-1), whose loss delayed preparedness of the stations's US Orbital Segment for future crewed missions.

Performance was nominal until T+140 seconds into launch when a cloud of white vapor appeared, followed by rapid loss of second-stage LOX tank pressure. The booster continued on its trajectory until complete vehicle breakup at T+150 seconds. The Dragon capsule was ejected from the disintegrating rocket and continued transmitting data until impact with the ocean. SpaceX officials stated that the capsule could have been recovered if the parachutes had deployed; however, the Dragon software did not include any provisions for parachute deployment in this situation. Subsequent investigation traced cause of the accident to the failure of a strut which secured a helium bottle inside the second-stage LOX tank. With the helium pressurization system integrity breached, excess helium quickly flooded the tank, eventually causing it to burst from overpressure.[20][21]

Full-thrust version and first booster landing

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

On December 22, 2015, SpaceX launched the highly anticipated return-to-flight mission after the loss of CRS-7, inaugurating a new Falcon 9 Full Thrust version of its flagship rocket featuring increased performance, notably thanks to subcooling of the propellants. This first mission of the upgraded vehicle launched a constellation of 11 Orbcomm-OG2 second-generation satellites.[22] Performing a controlled-descent and landing test for the 8th time, SpaceX managed to return the first stage successfully to the Landing Zone 1 at Cape Canaveral, marking the first successful recovery of a rocket first stage that launched a payload to orbit.[23]

First landings on drone ship

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

On April 8, 2016, SpaceX launched its eighth commercial resupply mission to the International Space Station. After completing its part of the mission, the first-stage booster slowed itself with a boostback maneuver, re-entered the atmosphere, executed an automated controlled descent and landed vertically onto the drone ship Of Course I Still Love You, marking the first successful landing of a rocket on a ship at sea. This was the fourth attempt to land on a SpaceX drone ship, as part of the company's experimental controlled-descent and landing tests. This also marked the return-to-flight of the Dragon capsule, after the loss of CRS-7.[24]

On May 6, 2016, SpaceX launched its JCSAT-14 mission, a geostationary communications satellite operating over Asia. Eight minutes and forty seconds into the flight, the first stage re-entered Earth's atmosphere at twice the speed of their first success, and hence four times the kinetic energy to dissipate (eight times as much heating).[25] The stage successfully landed on the drone ship a few hundred miles off the coast of Florida.

Loss of Amos-6 on the launch pad

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

On September 1, 2016, the 29th Falcon 9 rocket exploded on the launchpad while propellant was being loaded for a routine pre-launch static fire test. The payload, Israeli satellite Amos-6, partly commissioned by Facebook, was destroyed with the launcher.[26]

First launch and landing of a reused first stage

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

On March 30, 2017, SpaceX launched the SES-10 mission with first-stage booster B1021, which had been previously used for CRS-8. The stage was successfully recovered a second time; it will be retired and put on display at Cape Canaveral.[27]

Launch statistics

Rockets from the Falcon 9 family have been launched 33 times over 13 years, resulting in 31 full mission successes, one partial success (with primary orbital payload delivery completed, but a secondary payload left in a lower-than-planned orbit), and one failure (with total loss of spacecraft). Additionally, one rocket and payload were destroyed before launch in preparation for an on-pad static fire test. This yields a reliability record of 94% of contracted primary missions. Ten of fifteen landing attempts (67%) have succeeded in recovering the rocket's first stage.

The first rocket version Falcon 9 v1.0 was launched five times from June 2010 to March 2013, its successor Falcon 9 v1.1 fifteen times from September 2013 to January 2016 and the latest upgrade Falcon 9 Full Thrust thirteen times from December 2015 to present.

<templatestyles src="Column/styles.css"/>

<templatestyles src = "Column/styles.css" />

Flights by rocket configuration

<templatestyles src = "Column/styles.css" />

Flights by launch site

1
2
3
4
5
6
7
8
9
2010
'11
'12
'13
'14
'15
'16
'17

<templatestyles src="Column/styles.css"/>

<templatestyles src = "Column/styles.css" />

Flights by mission outcome

1
2
3
4
5
6
7
8
9
2010
'11
'12
'13
'14
'15
'16
'17
  •   Loss during flight
  •   Loss before launch
  •   Partial failure
  •   Success
<templatestyles src = "Column/styles.css" />

Flights by landing outcome

1
2
3
4
5
6
7
8
2010
'11
'12
'13
'14
'15
'16
'17
  •   Ocean failure
  •   Drone ship failure
  •   Ground pad failure
  •   Parachutes failure
  •   Ocean success
  •   Drone ship success
  •   Ground pad success
  •   No attempt

Past launches

Flight № Date and
time (UTC)
Type
Booster[lower-alpha 1]
Launch site Payload Payload mass Orbit Customer Outcome
Mission Landing

2010 to 2013

1 June 4, 2010, 18:45 F9 v1.0[28] CCAFS LC-40 Dragon Spacecraft Qualification Unit LEO SpaceX Success Parachutes[29]
Failure[30]
First flight of Falcon 9 v1.0[1]
2 December 8, 2010, 15:43[31] F9 v1.0[28] CCAFS LC-40 Dragon demo flight C1, two cubesats,[32] barrel of Brouère cheese[33] LEO NASA (COTS), NRO Success [30] Parachutes[34]
Failure[30]
Maiden flight of Dragon capsule; 3 hours, testing of maneuvering thrusters and reentry[35]
3 May 22, 2012, 07:44[36] F9 v1.0[28] CCAFS LC-40 Dragon demo flight C2+[37] LEO NASA (COTS) Success[38] No attempt
Launch was scrubbed on first attempt,[39] second launch attempt was successful.[40]
4 October 8, 2012, 00:35[41] F9 v1.0[28] CCAFS LC-40 SpaceX CRS-1[42] 500 kg
(1,100 lb)
LEO NASA (CRS) Success No attempt
Secondary payload: Orbcomm-OG2[43] 172 kg
(379 lb)[44]
LEO Orbcomm Failure[14][45]
CRS-1 successful, but the secondary payload was inserted into abnormally low orbit and lost due to Falcon 9 boost stage engine failure, ISS visiting vehicle safety rules, and the primary payload owner's contractual right to decline a second ignition of the second stage under some conditions.[13][14]
5 March 1, 2013, 15:10[46] F9 v1.0[28] CCAFS LC-40 SpaceX CRS-2[47][48] 677 kg
(1,493 lb)
LEO NASA (CRS) Success No attempt
Last launch of the original Falcon 9 v1.0 launch vehicle.[49]
6 September 29, 2013, 16:00[18] F9 v1.1[28] VAFB SLC-4E CASSIOPE[50] 500 kg
(1,100 lb)
Polar orbit MDA Success[18] Ocean
Failure
Commercial mission and first Falcon 9 v1.1 flight, with improved 13-tonne to LEO capacity.[49] Following second-stage separation from the first stage, an attempt was made to perform an ocean touchdown test of the discarded booster vehicle. The test provided good test data on the experiment—its primary objective—but as the booster neared the ocean, aerodynamic forces caused an uncontrollable roll. The center engine, depleted of fuel by centrifugal force, shut down resulting in the impact and destruction of the vehicle.[18]
7 December 3, 2013, 22:41[51] F9 v1.1 CCAFS LC-40 SES-8[52][53] 3,170 kg
(6,990 lb)
GTO SES Success[54] No attempt[55]
First GTO launch for Falcon 9.[52]

2014

8 January 6, 2014, 22:06[56] F9 v1.1 CCAFS LC-40 Thaicom 6 3,325 kg
(7,330 lb)
GTO Thaicom Success[57] No attempt[58]
Second GTO launch for Falcon 9. The USAF evaluated launch data from this flight as part of a separate certification program for SpaceX to qualify to fly U.S. military payloads and found that the Thaicom 6 launch had "unacceptable fuel reserves at engine cutoff of the stage 2 second burnoff".[59]
9 April 18, 2014, 19:25[60] F9 v1.1 CCAFS LC-40 SpaceX CRS-3[47][48] 2,296 kg
(5,062 lb)[61]
LEO NASA (CRS) Success Ocean
Success[62]
Following second-stage separation, SpaceX conducted a second controlled-descent test of the discarded booster vehicle and achieved the first successful controlled ocean touchdown of a liquid-rocket-engine orbital booster.[63][64] Following touchdown the first stage tipped over as expected and was destroyed.

This was the first Falcon 9 booster to fly with extensible landing legs and the first Dragon mission with the Falcon 9 v1.1 launch vehicle.

10 July 14, 2014, 15:15 F9 v1.1 CCAFS LC-40 OG2 Mission 1
6 OG2 satellites
1,316 kg
(2,901 lb)
(6 × 172 kg[44] + 2 × 142 kg)[65]
LEO Orbcomm Success[66] Ocean
Success[67]
Second Falcon 9 booster with landing legs. Following second-stage separation, SpaceX conducted a controlled-descent test of the discarded booster vehicle. The first stage successfully decelerated from hypersonic velocity in the upper atmosphere, made reentry and landing burns, deployed its landing legs and touched down on the ocean surface. As with the previous mission, the first stage then tipped over as intended and was not recovered.[68]
11 August 5, 2014, 08:00 F9 v1.1 CCAFS LC-40 AsiaSat 8[69][70][71] 4,535 kg
(9,998 lb)
GTO AsiaSat Success[72] No attempt[73]
12 September 7, 2014, 05:00 F9 v1.1 CCAFS LC-40 AsiaSat 6[69][70][74] 4,428 kg
(9,762 lb)
GTO AsiaSat Success[75] No attempt[76]
13 September 21, 2014, 05:52[77][78] F9 v1.1 CCAFS LC-40 SpaceX CRS-4[48] 2,216 kg
(4,885 lb)[79]
LEO NASA (CRS) Success[80] Ocean[81]
Success[82]

2015

14 January 10, 2015, 09:47[83] F9 v1.1 CCAFS LC-40 SpaceX CRS-5[69] 2,395 kg
(5,280 lb)[84]
LEO NASA (CRS) Success[85] Drone ship
Failure[86]
Following second stage separation, SpaceX performed a test flight which attempted to return the first stage of the Falcon 9 through the atmosphere and land it on an approximately 90-by-50-meter (300 ft × 160 ft) floating platform—called the autonomous spaceport drone ship. Many of the test objectives were achieved, including precision control of the rocket's descent to land on the platform at a specific point in the Atlantic ocean, and a large amount of test data was obtained from the first use of grid fin control surfaces used for more precise reentry positioning. The grid fin control system ran out of hydraulic fluid a minute before landing and the landing itself resulted in a crash.[87][88]
15 February 11, 2015, 23:03[89] F9 v1.1 CCAFS LC-40 DSCOVR[90] 570 kg
(1,260 lb)
Sun-Earth L1 U.S. Air Force, NASA, NOAA Success Ocean
Success
First launch under USAF's OSP 3 launch contract.[91] First SpaceX launch to put a satellite to an orbit with an orbital altitude many times the distance to the Moon: Sun-Earth libration point L1. The first stage made a test flight descent to an over-ocean landing within 10 m (33 ft) of its intended target.[92]
16 March 2, 2015, 03:50[41][93] F9 v1.1 CCAFS LC-40 ABS-3A, Eutelsat 115 West B (ex-Satmex 7)[69] 4,159 kg
(9,169 lb)
GTO ABS,
Eutelsat (Satmex)
Success No attempt[94]
The launch was Boeing's first-ever conjoined launch of a lighter-weight dual-commsat stack that was specifically designed to take advantage of the lower-cost SpaceX Falcon 9 launch vehicle.[95][96] Per satellite, launch costs were less than $30 million.[97] The ABS satellite reached its final destination ahead of schedule and started operations on September 10.[98]
17 April 14, 2015, 20:10[41] F9 v1.1 CCAFS LC-40 SpaceX CRS-6[69] 1,898 kg
(4,184 lb)[99]
LEO NASA (CRS) Success Drone ship
Failure[100]
Following the first-stage boost, SpaceX attempted a controlled-descent test of the first stage. The first stage contacted the ship, but soon tipped over due to excess lateral velocity caused by a stuck throttle valve resulting in a later-than-intended downthrottle.[101][102]
18 April 27, 2015, 23:03[103] F9 v1.1 CCAFS LC-40 TürkmenÄlem 52°E / MonacoSAT [104] 4,707 kg
(10,377 lb)
GTO Turkmenistan National Space Agency[105] Success No attempt[106]
19 June 28, 2015, 14:21[41][107] F9 v1.1 CCAFS LC-40 SpaceX CRS-7[69] 1,952 kg
(4,303 lb)[108]
LEO NASA (CRS) Failure (In-flight)[19] Drone ship[109]
N/A
Launch performance was nominal until an overpressure incident in the second-stage LOX tank, leading to vehicle breakup at T+150 seconds. The Dragon capsule survived the explosion but was lost upon splashdown because its software did not contain provisions for parachute deployment on launch vehicle failure. (more details above)
20 December 22, 2015, 01:29[110] F9 FT
B1019
CCAFS LC-40 OG-2 Mission 2[110]
11 OG2 satellites
2,034 kg
(4,484 lb)
(11 × 172 kg[44] + 1 × 142 kg)[65]
LEO Orbcomm Success Ground pad
Success[111]
First launch of the upgraded Falcon 9 v1.1 launch vehicle (now called Falcon 9 Full Thrust), with a 30 percent power increase.[112] Orbcomm had originally agreed to be the third flight of the enhanced-thrust rocket,[113] but the change to the maiden flight position was announced in October 2015.[112] SpaceX received a permit from the FAA to land the booster on solid ground at Cape Canaveral,[114] and succeeded.[111] The booster is now on permanent display outside SpaceX's headquarters in Hawthorne, CA at the intersection of Crenshaw Blvd. and Jack Northrop Ave.[115]

2016

21 January 17, 2016, 18:42[41] F9 v1.1 VAFB SLC-4E Jason-3[116] 553 kg
(1,219 lb)
LEO NASA, NOAA, CNES Success Drone ship
Failure
First launch of NASA and NOAA joint science mission under the NLS II launch contract (not related to NASA CRS or USAF OSP3 contracts). Last launch of the original Falcon 9 v1.1 launch vehicle. The Jason-3 satellite was successfully deployed to target orbit.[117] SpaceX again attempted a recovery of the first stage booster by landing on an autonomous drone ship; this time located in the Pacific Ocean. The first stage did achieve a soft-landing on the ship, but a lockout on one of the landing legs failed to latch and it fell over and exploded.[118][119]
22 March 4, 2016, 23:35[41] F9 FT
B1020
CCAFS LC-40 SES-9[120][121] 5,271 kg
(11,621 lb)
GTO SES Success Drone ship
Failure
Second launch of the enhanced Falcon 9 Full Thrust launch vehicle.[112] Following the launch, SpaceX attempted an experimental landing test to a drone ship,[122] although a successful landing was not expected[123] because launch mass exceeded previously indicated limit for a GTO there was little fuel left. As predicted, booster recovery failed: the spent first stage "landed hard",[124] but the controlled-descent, atmospheric re-entry and navigation to the drone ship were successful and returned significant test data on bringing back high-energy Falcon 9s.[125]
23 April 8, 2016, 20:43[41] F9 FT
B1021.1[126]
CCAFS LC-40 SpaceX CRS-8[121] 3,136 kg
(6,914 lb)[127]
LEO NASA (CRS) Success[128] Drone ship
Success[129]
Dragon carried over 1500 kg of supplies and delivered (stowed in its trunk) the inflatable Bigelow Expandable Activity Module (BEAM) to the ISS for two years of in-orbit tests.[130] The rocket's first stage landed smoothly on SpaceX's autonomous spaceport drone ship 9 minutes after liftoff,[131] making this the first ever successful landing of a rocket booster on a ship at sea as part of an orbital launch. The first stage B1021 was later also the first orbital booster to be used again, when launching SES-10 on March 30, 2017.
24 May 6, 2016, 05:21[41] F9 FT
B1022
CCAFS LC-40 JCSAT-14[132] 4,696 kg
(10,353 lb)[133]
GTO SKY Perfect JSAT Group Success Drone ship
Success
Launched the JCSAT 14 communications satellite for Tokyo-based SKY Perfect JSAT Corp. JCSAT 14 will support data networks, television broadcasters and mobile communications users in Japan, East Asia, Russia, Oceania, Hawaii and other Pacific islands. This was the first time a booster successfully landed after a GTO mission.[134]
25 May 27, 2016, 21:39[135] F9 FT
B1023.1[136]
CCAFS LC-40 Thaicom 8[137][138] 3,100 kg
(6,800 lb)[139]
GTO Thaicom Success Drone ship
Success[140]
Manufactured by Orbital ATK, the 3,100-kilogram (6,800 lb) Thaicom 8 communications satellite will serve Thailand, India and Africa from the 78.5° East geostationary location.[141] It is equipped with 24 active Ku-band transponders.
26 June 15, 2016, 14:29[41] F9 FT
B1024
CCAFS LC-40 ABS-2A, Eutelsat 117 West B (ex-Satmex 9) 3,600 kg
(7,900 lb)[142]
GTO ABS,
Eutelsat (Satmex)
Success Drone ship
Failure
One year after pioneering this technique on flight 16, Falcon again launched two Boeing 702SP gridded ion thruster satellites in a dual-stack configuration,[98] with the two customers sharing the rocket and mission costs. First stage landing attempt on drone ship failed on landing due to low thrust on one of the three landing engines.[143]
27 July 18, 2016, 04:45[41] F9 FT
B1025.1[136]
CCAFS LC-40 SpaceX CRS-9[144] 2,257 kg
(4,976 lb)*[145]
LEO NASA (CRS) Success Ground pad
Success
Among other cargo, an International Docking Adapter (IDA-2) was carried to the ISS. This mission had a successful first-stage landing at Cape Canaveral.[146] *Including the reusable Dragon Capsule, total payload to orbit was 6457 kg
28 August 14, 2016, 05:26 F9 FT
B1026
CCAFS LC-40 JCSAT-16 4,600 kg
(10,100 lb)
GTO SKY Perfect JSAT Group Success Drone ship
Success
First attempt to touch down from a ballistic trajectory using a single-engine landing burn. All previous landings from a ballistic trajectory had fired three engines on the landing-burn, which provided more braking force, but subjected the vehicle to greater structural stresses. The single-engine landing burn takes more time and fuel, but puts less stress on the vehicle.[citation needed]
N/A September 1, 2016, 13:07 F9 FT
B1028
CCAFS LC-40 Amos-6[147] 5,500 kg
(12,100 lb)
GTO Spacecom Failure
(pre-flight)
Drone ship[148]
N/A
The rocket and Amos-6 payload were lost in a launch pad explosion on September 1, 2016 during propellant fill prior to a static fire test.[149] The pad was clear of personnel and there were no injuries.[150]

2017

29 January 14, 2017, 17:54 F9 FT
B1029
VAFB SLC-4E Iridium NEXT 1–10[151][152][153] 9,600 kg
(21,200 lb)
LEO Iridium Communications Success Drone ship
Success[154]
Return-to-flight mission after the accident in September 2016, using booster core B1029.[155] Iridium NEXT will replace the original Iridium constellation, launched in the late 1990s. Each Falcon mission will carry 10 satellites, with a goal to complete deployment of the 66 plus 9 spare[156] satellite constellation by mid 2018.[157][158] The first two Iridium qualification units were supposed to ride a Dnepr rocket in April 2016 but were delayed, so Iridium decided to qualify the first batch of 10 satellites instead.[159] Total payload mass was 9,600 kg (21,200 lb) : 10 satellites weighing 860 kg each, plus the 1,000-kg dispenser. The target orbit was 780 kilometers altitude.[160]
30 February 19, 2017, 14:39 F9 FT
B1031
KSC LC-39A SpaceX CRS-10[144] 2,490 kg
(5,490 lb)[161]
LEO NASA (CRS) Success Ground pad
Success
This rocket launched the Dragon spacecraft to low-Earth orbit to deliver critical cargo to the International Space Station for NASA. The CRS-10 mission was SpaceX’s first launch from historic LC-39A at Kennedy Space Center. Dragon was filled with about 2,500 kg (5,500 lb) of supplies and payloads, including critical materials to directly support dozens of the more than 250 science and research investigations that will occur during Expeditions 50 and 51. Following stage separation, the first stage of Falcon 9 landed at SpaceX’s Landing Zone 1 (LZ-1) at Cape Canaveral.[162]
31 March 16, 2017, 06:00 F9 FT
B1030
KSC LC-39A EchoStar 23 5,600 kg
(12,300 lb)[163]
GTO EchoStar Success No attempt
Communications satellite for EchoStar Corp. EchoStar XXIII, based on a spare platform from the cancelled CMBStar 1 satellite program, will provide direct-to-home television broadcast services over Brazil.[164] There was no attempt at a first-stage recovery so this rocket did not have landing legs or grid fins.[165]
32 March 30, 2017, 22:27 F9 FT
B1021.2[126]
KSC LC-39A SES-10[120][166][167] 5,300 kg
(11,700 lb)[168]
GTO SES Success[169] Drone ship
Success
First payload to fly on a reused first stage, B1021, previously launched with CRS-8, which also landed a second time.[170][171] In what is also a first, the payload fairing remained intact after a successful splashdown achieved with thrusters and a steerable parachute.[172][173]
33 May 1, 2017, 11:15 F9 FT
B1032.1[136]
KSC LC-39A NROL-76[174] Classified LEO[175] NRO Success Ground pad
Success
First launch under SpaceX's certification for "national security space missions," which allows SpaceX to contract launch services for payloads with classified information under U.S. national security.[176] Due to the classified nature of the payload, second-stage speed and altitude telemetry was not displayed on the official SpaceX launch webcast as has been typical of previous Falcon 9 webcasts. Instead, telemetry of the first stage's speed and altitude were displayed, and SpaceX streamed continuous footage of the first-stage from liftoff to landing for the first time.[177]

Future launches

Future launches are listed chronologically when firm planning dates are in place, and reliably sourced. The order of the later launches is much less certain, as the official SpaceX manifest does not include a schedule.[178] Tentative launch dates are picked from individual sources for each launch.[179][180][181][182] Launches are expected to take place "no earlier than" (NET) the listed date.

Financial documents analyzed by The Wall Street Journal indicate an expected 27 missions in 2017, ramping up to one flight per week in 2019.[183] Gwynne Shotwell confirmed in January 2017 that she "hopes to launch at least 20 Falcon 9 and Falcon Heavy rockets this year".[167] Repairs and modernization of the SLC-40 launch pad are underway with a return to service planned for August 2017,[184] thus doubling the company's launch capabilities from the East Coast.

Heavy payloads launched from the end of 2017 are expected to use the Falcon Heavy or the Falcon 9 Block 5 with its improved performance and ease of reusability.[185]

Date and time (UTC) Type
Booster[lower-alpha 1]
Launch site Payload Orbit Customer

2017

May 15, 2017[180]
23:20–00:10[179]
F9 FT
B1034
KSC LC-39A Inmarsat-5 F4[186] GTO Inmarsat
Due to the constraints of sending a heavy satellite (6,070 kg)[187] to GTO, the rocket will fly in its expendable configuration and the first-stage booster will not be recovered.[188]
June 1, 2017
21:55[180]
F9 FT
B1035
KSC LC-39A SpaceX CRS-11[144] LEO NASA (CRS)
This mission will deliver the Neutron Star Interior Composition Explorer (NICER)[189] to the ISS, along with the MUSES[190] Earth imaging platform and ROSA[191] solar array.[192] For the first time, this mission will launch a previously-used Dragon capsule.[193]
Mid-June 2017[179] F9 FT KSC LC-39A BulgariaSat-1[194][195] GTO Bulsatcom
Late June 2017[179] F9 FT KSC LC-39A Intelsat 35e[196] GTO Intelsat
Due to the constraints of sending a heavy satellite (~6,000 kg)[197] to GTO, the rocket will fly in its expendable configuration and the first-stage booster will not be recovered.[188]
June 29, 2017
20:02[179]
F9 FT VAFB SLC-4E Iridium NEXT 11–20[151][152] LEO Iridium Communications
June 2017[179] [needs update] F9 FT KSC LC-39A SES-11[166] / EchoStar 105 GTO SES /
EchoStar
July 2017[179] F9 FT KSC LC-39A Koreasat 5A[198][199] GTO KT Corporation
July 22, 2017[184] F9 FT VAFB SLC-4E FormoSat-5[200][201][202] SSO NSPO
Formosat-5 is an Earth observation satellite of the Taiwanese space agency. The SHERPA space tug by Spaceflight Industries was removed from this mission.[203]
August 1, 2017[179] F9 FT KSC LC-39A SpaceX CRS-12[144] LEO NASA (CRS)
Dragon is expected to carry 2,349 kg (5,179 lb) of pressurized mass and 961 kg (2,119 lb) unpressurized. The external payload manifested for this flight is the CREAM cosmic-ray detector.[192]
August 24, 2017[184] F9 FT VAFB SLC-4E Iridium NEXT 21–30[151][152] LEO Iridium Communications
Late Summer, 2017[204] Heavy
  • B1033.1 core
  • B1023.2 side
  • B1025.2 side
[136]
KSC LC-39A Falcon Heavy Demo[205] TBA SpaceX
Maiden flight of Falcon Heavy, using two recovered Falcon 9 cores as side boosters, including B1023 from the Thaicom 8 mission.[206] Rocket will fly without a commercial payload,[207] though an unknown "silly" payload has been suggested.[208] Musk also stated that SpaceX would be considering recovering the upper stage to achieve full reusability.[208]
September 30, 2017[209] [needs update] Heavy KSC LC-39A DSX, FormoSat-7 A/B/C/D/E/F, LightSail 2,[210] GPIM,[211] DSAC,[212] ISAT LEO / MEO U.S. Air Force
USAF Space Test Program Flight 2 (STP-2),[91] carrying more than 30 satellites.[213]
October 2017[179] F9 FT VAFB SLC-4E Iridium NEXT 31–40[151][152] LEO Iridium Communications
October 2017[181] F9 FT VAFB SLC-4E SAOCOM 1A[214][215]
ITASAT-1
SSO CONAE
ITA
November 1, 2017[179] F9 FT KSC LC-39A SpaceX CRS-13[144] LEO NASA (CRS)
November 2017[182][216] F9 FT KSC LC-39A SpX-DM1[217] LEO NASA (CCD)
Demonstration mission to ISS for NASA with an uncrewed Dragon 2 capsule.
Nov–Dec 2017[218] F9 FT VAFB SLC-4E Paz[218] / co-payload TBA SSO Hisdesat / TBA
Formerly called SEOSAR, this radar observation satellite will be operated in a constellation with the German SAR fleet TSX and TDX on the same orbit.[218] The rocket will be shared with further payloads to be announced, as Paz weighs only 1,200 kg.[219]
December 16, 2017[181][220] F9 FT LC-39A or SLC-40 Bangabandhu-1[220][221] GTO BTRC
December 2017[179] F9 FT VAFB SLC-4E Iridium NEXT 41–50[151][152] LEO Iridium Communications
H2, 2017[222] F9 FT LC-39A or SLC-40 SES-14[223] with GOLD[224] GTO SES
UCF / NASA
The SES-14 communications satellite will carry the GOLD Earth-observation instrument as a guest payload under contract with University of Central Florida and NASA.[225]
H2, 2017[222] F9 FT LC-39A or SLC-40 SES-16 / GovSat-1[223] GTO SES
H2, 2017[226][227] F9 FT VAFB SLC-4E SHERPA dispenser for ~90 payloads[226] SSO Spaceflight Industries
Rideshare mission "Sun Synch Express"[226] SSO-A will carry close to 90 small satellites,[228] including Eu:CROPIS[227] for DLR and ORS-6 (COWVR)[229] for the US Air Force Operationally Responsive Space Office.
2017[181] F9 FT LC-39A or SLC-40 ABS-8[230] GTO ABS
2017[181] F9 FT LC-39A or SLC-40 PSN-6[231] / co-payload TBA GTO PSN / TBA
Late 2017[232] F9 FT LC-39A or SLC-40 Hispasat 30W-6[233][234] GTO Hispasat[232]

2018

Early 2018[216][235] F9 KSC LC-39A[236] Crew Dragon in-flight abort test[236][237] Suborbital NASA (CCD)
A Falcon 9 first stage will propel the Dragon 2 test capsule in a sub-orbital flight to conduct a separation and abort scenario in the transonic regime at Max Q, i.e. under the worst structural stress conditions of a real flight.[237] The spacecraft will then splash down in the ocean with traditional parachutes, possibly with assistance of its integrated thrusters.
February 2018[182] F9 KSC LC-39A SpaceX CRS-14[144] LEO NASA (CRS)
The IDA-3 docking adaptor will be launched on this mission[238] to replace IDA-1 lost with CRS-7 in June 2015. Other payloads include MISSE-FF[239] materials research platform, phase 3 of the RRM[240] space refueling experiment and the TSIS[241] heliophysics sensor.[192]
February 2018 (every two months)[242] F9 VAFB SLC-4E Iridium NEXT 51–60[151][152] LEO Iridium Communications
Early 2018 F9 LC-39A or SLC-40 TelStar 18V[243] GTO Telesat
Early 2018 F9 LC-39A or SLC-40 TelStar 19V[243] GTO Telesat
March 20, 2018[244] F9 KSC LC-39A Transiting Exoplanet Survey Satellite (TESS)[245] HEO NASA
April 2018 (every two months)[242] F9 VAFB SLC-4E Iridium NEXT 61–70[151][152] LEO Iridium Communications
April 2018[182] F9 KSC LC-39A SpaceX CRS-15[144] LEO NASA (CRS)
May 2018[181] F9 KSC LC-39A GPS III A-2[246] MEO USAF
SpaceX's first launch of an EELV-class payload.[246]
May 2018[182][216] F9 KSC LC-39A SpX-DM2[217] LEO NASA (CCD)
Dragon 2 will carry its first crew of NASA astronauts on a 14-day mission to the ISS. Unless Boeing's CST-100 Starliner flies first (currently planned for August 2018), they will be the first people to be launched to orbit in an American spacecraft since the last Shuttle flight in 2011, and the first people in orbit not launched by a government organization.
June 2018 (every two months)[242][247] F9 VAFB SLC-4E <templatestyles src="Plainlist/styles.css"/> LEO <templatestyles src="Plainlist/styles.css"/>
June 2018[249] F9 LC-39A or SLC-40 Telkom 4 (TBC)[250][251] GTO Telkom Indonesia
August 2018[182] F9 KSC LC-39A SpaceX CRS-16[144] LEO NASA (CRS)
October 2018[182] F9 KSC LC-39A SpaceX CRS-17[144] LEO NASA (CRS)
December 2018[182] F9 KSC LC-39A SpaceX CRS-18[144] LEO NASA (CRS)
Q4, 2018[252] F9 LC-39A or SLC-40 GiSAT-1[252] GTO Global-IP
Late 2018[253] Heavy KSC LC-39A Private circumlunar trip[254] TLI / Free return Two private citizens
Two paying individuals will launch on a Falcon Heavy to fly by the Moon and return to Earth.
2018 Heavy KSC LC-39A ArabSat 6A[255] GTO ArabSat
2018[256] F9 LC-39A or SLC-40 Es'hail 2[257] GTO Es'hailSat
2018 F9 LC-39A or SLC-40 Eutelsat-Quantum[258] GTO Eutelsat
2018 F9 VAFB SLC-4E RADARSAT Constellation[259] SSO Canadian Space Agency
2018[215] F9 VAFB SLC-4E SAOCOM 1B[214] SSO CONAE
2018 F9 VAFB SLC-4E SARah 1 (active)[260][261] SSO Bundeswehr

2019 and beyond

February 2019[262] F9 LC-39A or SLC-40 GPS III A-3[263][264] MEO USAF
May 2019[182] F9 KSC LC-39A SpaceX CRS-19[144] LEO NASA (CRS)
Q3, 2019[182] F9 KSC LC-39A SpaceX CRS-20[144] LEO NASA (CRS)
2019 F9 VAFB SLC-4E SARah 2/3 (passive)[260][265] SSO Bundeswehr
Summer 2020[266] Heavy KSC LC-39A Red Dragon[267] TMI SpaceX
2020[268] F9 LC-39A or SLC-40 Inmarsat 6-F1[186][268] GTO Inmarsat
2020[269] Heavy KSC LC-39A ViaSat-3[270] GTO ViaSat
April 2021[271] F9 VAFB SLC-4E[271] Surface Water and Ocean Topography (SWOT)[271] LEO NASA[271]
2022 Heavy KSC LC-39A Mars Cargo 1[272] TMI SpaceX
2022 Heavy KSC LC-39A Mars Cargo 2[272] TMI SpaceX

See also

References

  1. 1.0 1.1 Falcon 9 first-stage boosters are designated with a construction serial number and an optional flight number when reused, e.g. B1021.1 and B1021.2 represent the two flights of booster B1021.
  1. 1.0 1.1 1.2 Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. 13.0 13.1 13.2 13.3 Lua error in package.lua at line 80: module 'strict' not found.
  14. 14.0 14.1 14.2 Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. 18.0 18.1 18.2 18.3 Lua error in package.lua at line 80: module 'strict' not found.
  19. 19.0 19.1 Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. 28.0 28.1 28.2 28.3 28.4 28.5 Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. 30.0 30.1 30.2 Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. 41.0 41.1 41.2 41.3 41.4 41.5 41.6 41.7 41.8 41.9 Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. 44.0 44.1 44.2 Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. 47.0 47.1 Lua error in package.lua at line 80: module 'strict' not found.
  48. 48.0 48.1 48.2 Lua error in package.lua at line 80: module 'strict' not found.
  49. 49.0 49.1 Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. 52.0 52.1 Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. SpaceX plans to recover stages when customers allow, SpaceFlight Now, April 30, 2014
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. Lua error in package.lua at line 80: module 'strict' not found.
  61. https://www.nasa.gov/sites/default/files/files/Orbital_CRS3_mission_overview.pdf
  62. Falcon 9 First Stage Landing Video (Repaired) | CRS-3 Mission at YouTube, by SpaceX
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. Lua error in package.lua at line 80: module 'strict' not found.
  65. 65.0 65.1 Lua error in package.lua at line 80: module 'strict' not found.
  66. Lua error in package.lua at line 80: module 'strict' not found.
  67. Falcon 9 First Stage Return | ORBCOMM Mission, Published on July 22, 2014 by SpaceX on YouTube
  68. Lua error in package.lua at line 80: module 'strict' not found.
  69. 69.0 69.1 69.2 69.3 69.4 69.5 Lua error in package.lua at line 80: module 'strict' not found.
  70. 70.0 70.1 Lua error in package.lua at line 80: module 'strict' not found.
  71. Lua error in package.lua at line 80: module 'strict' not found.
  72. Lua error in package.lua at line 80: module 'strict' not found.
  73. Lua error in package.lua at line 80: module 'strict' not found.
  74. Lua error in package.lua at line 80: module 'strict' not found.
  75. Lua error in package.lua at line 80: module 'strict' not found.
  76. Lua error in package.lua at line 80: module 'strict' not found.
  77. Lua error in package.lua at line 80: module 'strict' not found.
  78. Lua error in package.lua at line 80: module 'strict' not found.
  79. http://www.nasa.gov/sites/default/files/files/SpaceX_CRS-4_Mission_Overview-1.pdf
  80. Lua error in package.lua at line 80: module 'strict' not found.
  81. Lua error in package.lua at line 80: module 'strict' not found.
  82. Lua error in package.lua at line 80: module 'strict' not found.
  83. Lua error in package.lua at line 80: module 'strict' not found.
  84. https://www.nasa.gov/sites/default/files/files/SpaceX_CRS-5_factsheet.pdf
  85. Lua error in package.lua at line 80: module 'strict' not found.
  86. Close, but no cigar. This time., published January 16, 2015 by SpaceX on Vine
  87. Lua error in package.lua at line 80: module 'strict' not found.
  88. Lua error in package.lua at line 80: module 'strict' not found.
  89. Lua error in package.lua at line 80: module 'strict' not found.
  90. Lua error in package.lua at line 80: module 'strict' not found.
  91. 91.0 91.1 Lua error in package.lua at line 80: module 'strict' not found.
  92. Lua error in package.lua at line 80: module 'strict' not found.
  93. Lua error in package.lua at line 80: module 'strict' not found.
  94. Lua error in package.lua at line 80: module 'strict' not found.
  95. Lua error in package.lua at line 80: module 'strict' not found.
  96. Lua error in package.lua at line 80: module 'strict' not found.
  97. Lua error in package.lua at line 80: module 'strict' not found.
  98. 98.0 98.1 Lua error in package.lua at line 80: module 'strict' not found.
  99. https://www.nasa.gov/sites/default/files/files/SpaceX_CRS-6_Mission_Overview%281%29.pdf
  100. April 14, 2015: CRS-6 First Stage Tracking Cam, Published on June 25, 2015 by SpaceX on YouTube
  101. Lua error in package.lua at line 80: module 'strict' not found.
  102. Lua error in package.lua at line 80: module 'strict' not found.
  103. Lua error in package.lua at line 80: module 'strict' not found.
  104. Lua error in package.lua at line 80: module 'strict' not found.
  105. Lua error in package.lua at line 80: module 'strict' not found.
  106. Lua error in package.lua at line 80: module 'strict' not found.
  107. Lua error in package.lua at line 80: module 'strict' not found.
  108. https://www.nasa.gov/sites/default/files/atoms/files/spacex_crs7_mission_overview.pdf
  109. Lua error in package.lua at line 80: module 'strict' not found.
  110. 110.0 110.1 Lua error in package.lua at line 80: module 'strict' not found.
  111. 111.0 111.1 Lua error in package.lua at line 80: module 'strict' not found.
  112. 112.0 112.1 112.2 Lua error in package.lua at line 80: module 'strict' not found.
  113. Lua error in package.lua at line 80: module 'strict' not found.
  114. Lua error in package.lua at line 80: module 'strict' not found.
  115. Lua error in package.lua at line 80: module 'strict' not found.
  116. Lua error in package.lua at line 80: module 'strict' not found.
  117. Lua error in package.lua at line 80: module 'strict' not found.
  118. Lua error in package.lua at line 80: module 'strict' not found.
  119. Lua error in package.lua at line 80: module 'strict' not found.
  120. 120.0 120.1 Lua error in package.lua at line 80: module 'strict' not found.
  121. 121.0 121.1 Lua error in package.lua at line 80: module 'strict' not found.
  122. Lua error in package.lua at line 80: module 'strict' not found.
  123. Lua error in package.lua at line 80: module 'strict' not found.
  124. Lua error in package.lua at line 80: module 'strict' not found.
  125. Lua error in package.lua at line 80: module 'strict' not found.
  126. 126.0 126.1 Lua error in package.lua at line 80: module 'strict' not found.
  127. https://www.nasa.gov/sites/default/files/atoms/files/spacex_crs-8_mission_overview.pdf
  128. Lua error in package.lua at line 80: module 'strict' not found.
  129. Lua error in package.lua at line 80: module 'strict' not found.
  130. Lua error in package.lua at line 80: module 'strict' not found.
  131. Lua error in package.lua at line 80: module 'strict' not found.
  132. Lua error in package.lua at line 80: module 'strict' not found.
  133. Lua error in package.lua at line 80: module 'strict' not found.
  134. Lua error in package.lua at line 80: module 'strict' not found.
  135. Lua error in package.lua at line 80: module 'strict' not found.
  136. 136.0 136.1 136.2 136.3 Lua error in package.lua at line 80: module 'strict' not found.
  137. Lua error in package.lua at line 80: module 'strict' not found.
  138. Lua error in package.lua at line 80: module 'strict' not found.
  139. Lua error in package.lua at line 80: module 'strict' not found.
  140. First-stage landing | Onboard camera, Published on May 27, 2016 by SpaceX on YouTube
  141. Lua error in package.lua at line 80: module 'strict' not found.
  142. [1][2]
  143. Lua error in package.lua at line 80: module 'strict' not found.
  144. 144.00 144.01 144.02 144.03 144.04 144.05 144.06 144.07 144.08 144.09 144.10 144.11 Lua error in package.lua at line 80: module 'strict' not found.
  145. http://www.nasa.gov/sites/default/files/atoms/files/spacex_crs-9_mission_overview2.pdf
  146. Lua error in package.lua at line 80: module 'strict' not found.
  147. Lua error in package.lua at line 80: module 'strict' not found.
  148. Lua error in package.lua at line 80: module 'strict' not found.
  149. Lua error in package.lua at line 80: module 'strict' not found.
  150. Lua error in package.lua at line 80: module 'strict' not found.
  151. 151.0 151.1 151.2 151.3 151.4 151.5 151.6 151.7 Lua error in package.lua at line 80: module 'strict' not found.
  152. 152.0 152.1 152.2 152.3 152.4 152.5 152.6 152.7 Lua error in package.lua at line 80: module 'strict' not found.
  153. Lua error in package.lua at line 80: module 'strict' not found.
  154. Lua error in package.lua at line 80: module 'strict' not found.
  155. Lua error in package.lua at line 80: module 'strict' not found.
  156. 156.0 156.1 Lua error in package.lua at line 80: module 'strict' not found.
  157. Lua error in package.lua at line 80: module 'strict' not found.
  158. Lua error in package.lua at line 80: module 'strict' not found.
  159. Lua error in package.lua at line 80: module 'strict' not found.
  160. Lua error in package.lua at line 80: module 'strict' not found.
  161. NASA: SpaceX CRS-10 mission overview
  162. Lua error in package.lua at line 80: module 'strict' not found.
  163. Lua error in package.lua at line 80: module 'strict' not found.
  164. Lua error in package.lua at line 80: module 'strict' not found.
  165. Falcon 9 booster minus landing legs and grid fins poised for launch March 14, 2017
  166. 166.0 166.1 Lua error in package.lua at line 80: module 'strict' not found.
  167. 167.0 167.1 Lua error in package.lua at line 80: module 'strict' not found.
  168. Lua error in package.lua at line 80: module 'strict' not found.
  169. Lua error in package.lua at line 80: module 'strict' not found.
  170. Lua error in package.lua at line 80: module 'strict' not found.
  171. SpaceX makes aerospace history with successful launch and landing of used rocket Retrieved March 31, 2017
  172. Lua error in package.lua at line 80: module 'strict' not found.
  173. Lua error in package.lua at line 80: module 'strict' not found.
  174. Lua error in package.lua at line 80: module 'strict' not found.
  175. Lua error in package.lua at line 80: module 'strict' not found.
  176. Lua error in package.lua at line 80: module 'strict' not found.
  177. Lua error in package.lua at line 80: module 'strict' not found.
  178. SpaceX launch manifest, accessed July 29, 2016.
  179. 179.00 179.01 179.02 179.03 179.04 179.05 179.06 179.07 179.08 179.09 179.10 Lua error in package.lua at line 80: module 'strict' not found.
  180. 180.0 180.1 180.2 Lua error in package.lua at line 80: module 'strict' not found.
  181. 181.0 181.1 181.2 181.3 181.4 181.5 Lua error in package.lua at line 80: module 'strict' not found.
  182. 182.0 182.1 182.2 182.3 182.4 182.5 182.6 182.7 182.8 182.9 Lua error in package.lua at line 80: module 'strict' not found.
  183. Lua error in package.lua at line 80: module 'strict' not found.
  184. 184.0 184.1 184.2 Lua error in package.lua at line 80: module 'strict' not found.
  185. Lua error in package.lua at line 80: module 'strict' not found.
  186. 186.0 186.1 Lua error in package.lua at line 80: module 'strict' not found.
  187. Lua error in package.lua at line 80: module 'strict' not found.
  188. 188.0 188.1 Lua error in package.lua at line 80: module 'strict' not found.
  189. Lua error in package.lua at line 80: module 'strict' not found.
  190. Lua error in package.lua at line 80: module 'strict' not found.
  191. Lua error in package.lua at line 80: module 'strict' not found.
  192. 192.0 192.1 192.2 Lua error in package.lua at line 80: module 'strict' not found.
  193. Lua error in package.lua at line 80: module 'strict' not found.
  194. Lua error in package.lua at line 80: module 'strict' not found.
  195. Lua error in package.lua at line 80: module 'strict' not found.
  196. Lua error in package.lua at line 80: module 'strict' not found.
  197. Lua error in package.lua at line 80: module 'strict' not found.
  198. Lua error in package.lua at line 80: module 'strict' not found.
  199. Lua error in package.lua at line 80: module 'strict' not found.
  200. Lua error in package.lua at line 80: module 'strict' not found.
  201. Lua error in package.lua at line 80: module 'strict' not found.
  202. Lua error in package.lua at line 80: module 'strict' not found.
  203. Lua error in package.lua at line 80: module 'strict' not found.
  204. Lua error in package.lua at line 80: module 'strict' not found.
  205. Lua error in package.lua at line 80: module 'strict' not found.
  206. Lua error in package.lua at line 80: module 'strict' not found.
  207. Lua error in package.lua at line 80: module 'strict' not found.
  208. 208.0 208.1 Lua error in package.lua at line 80: module 'strict' not found.
  209. Lua error in package.lua at line 80: module 'strict' not found.
  210. Lua error in package.lua at line 80: module 'strict' not found.
  211. Lua error in package.lua at line 80: module 'strict' not found.
  212. Lua error in package.lua at line 80: module 'strict' not found.
  213. Lua error in package.lua at line 80: module 'strict' not found.
  214. 214.0 214.1 Lua error in package.lua at line 80: module 'strict' not found.
  215. 215.0 215.1 Lua error in package.lua at line 80: module 'strict' not found.
  216. 216.0 216.1 216.2 Lua error in package.lua at line 80: module 'strict' not found.
  217. 217.0 217.1 Lua error in package.lua at line 80: module 'strict' not found.
  218. 218.0 218.1 218.2 Lua error in package.lua at line 80: module 'strict' not found.
  219. Lua error in package.lua at line 80: module 'strict' not found.
  220. 220.0 220.1 Lua error in package.lua at line 80: module 'strict' not found.
  221. Lua error in package.lua at line 80: module 'strict' not found.
  222. 222.0 222.1 Lua error in package.lua at line 80: module 'strict' not found.
  223. 223.0 223.1 Lua error in package.lua at line 80: module 'strict' not found.
  224. Lua error in package.lua at line 80: module 'strict' not found.
  225. Lua error in package.lua at line 80: module 'strict' not found.
  226. 226.0 226.1 226.2 Lua error in package.lua at line 80: module 'strict' not found.
  227. 227.0 227.1 Lua error in package.lua at line 80: module 'strict' not found.
  228. Lua error in package.lua at line 80: module 'strict' not found.
  229. Lua error in package.lua at line 80: module 'strict' not found.
  230. Lua error in package.lua at line 80: module 'strict' not found.
  231. Lua error in package.lua at line 80: module 'strict' not found.
  232. 232.0 232.1 Lua error in package.lua at line 80: module 'strict' not found.
  233. Lua error in package.lua at line 80: module 'strict' not found.
  234. Lua error in package.lua at line 80: module 'strict' not found.
  235. Lua error in package.lua at line 80: module 'strict' not found.
  236. 236.0 236.1 Lua error in package.lua at line 80: module 'strict' not found.
  237. 237.0 237.1 Lua error in package.lua at line 80: module 'strict' not found.
  238. Lua error in package.lua at line 80: module 'strict' not found.
  239. Lua error in package.lua at line 80: module 'strict' not found.
  240. Lua error in package.lua at line 80: module 'strict' not found.
  241. Lua error in package.lua at line 80: module 'strict' not found.
  242. 242.0 242.1 242.2 242.3 Lua error in package.lua at line 80: module 'strict' not found.
  243. 243.0 243.1 Lua error in package.lua at line 80: module 'strict' not found.
  244. Lua error in package.lua at line 80: module 'strict' not found.
  245. Lua error in package.lua at line 80: module 'strict' not found.
  246. 246.0 246.1 Lua error in package.lua at line 80: module 'strict' not found.
  247. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  248. Lua error in package.lua at line 80: module 'strict' not found.
  249. Lua error in package.lua at line 80: module 'strict' not found.
  250. Lua error in package.lua at line 80: module 'strict' not found.
  251. Lua error in package.lua at line 80: module 'strict' not found.
  252. 252.0 252.1 Lua error in package.lua at line 80: module 'strict' not found.
  253. Lua error in package.lua at line 80: module 'strict' not found.
  254. Lua error in package.lua at line 80: module 'strict' not found.
  255. Lua error in package.lua at line 80: module 'strict' not found.
  256. Lua error in package.lua at line 80: module 'strict' not found.
  257. Lua error in package.lua at line 80: module 'strict' not found.
  258. Lua error in package.lua at line 80: module 'strict' not found.
  259. Lua error in package.lua at line 80: module 'strict' not found.
  260. 260.0 260.1 Lua error in package.lua at line 80: module 'strict' not found.
  261. Lua error in package.lua at line 80: module 'strict' not found.
  262. Lua error in package.lua at line 80: module 'strict' not found.
  263. Lua error in package.lua at line 80: module 'strict' not found.
  264. Lua error in package.lua at line 80: module 'strict' not found.
  265. Lua error in package.lua at line 80: module 'strict' not found.
  266. Lua error in package.lua at line 80: module 'strict' not found.
  267. Lua error in package.lua at line 80: module 'strict' not found.
  268. 268.0 268.1 Lua error in package.lua at line 80: module 'strict' not found.
  269. Lua error in package.lua at line 80: module 'strict' not found.
  270. Lua error in package.lua at line 80: module 'strict' not found.
  271. 271.0 271.1 271.2 271.3 Lua error in package.lua at line 80: module 'strict' not found.
  272. 272.0 272.1 Lua error in package.lua at line 80: module 'strict' not found.

External links