Falcon 9 first-stage landing tests

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
The first stage of Falcon 9 Flight 20 successfully landed for the first time on a ground pad at Landing Zone 1, Cape Canaveral Air Force Station, after propelling 11 Orbcomm OG2 satellites to orbit.

The Falcon 9 first-stage landing tests are a series of controlled-descent flight tests that have been conducted by SpaceX since 2013. The program's objective is to execute a controlled re-entry, descent and landing (EDL) of the Falcon 9 first stage into Earth's atmosphere after it completes the boost phase of an orbital spaceflight. The first tests aimed to touch down vertically in the ocean at zero velocity. Later tests attempted to land the rocket precisely on an autonomous spaceport drone ship (a barge commissioned by SpaceX to provide a stable landing surface at sea) or on terra firma on a ground pad at Cape Canaveral.

The first test occurred in September 2013 on the sixth flight of a Falcon 9 and maiden launch of the v1.1 rocket version. As of May 2016, twelve test flights have been conducted, four of which achieved a soft landing and recovery of the booster: flight 20 safely touching down on the ground pad upon first attempt in December 2015, flight 23 finally achieving a vertical landing at sea in April 2016 after four previous attempts, and flight 24 and flight 25 returning at higher speed from GTO missions in May 2016.

The first-stage descent tests are a part of the larger SpaceX reusable launch system development program, which has also included a number of technology development activities and low-altitude test flights at the SpaceX facility in McGregor, Texas. The program's goal is to privately develop reusable rockets using vertical-landing technology.

Traditionally, the first stages of orbital carrier rockets have been discarded in the ocean once the ascent was complete. Achieving routine recovery and reuse of the launch vehicles could dramatically reduce the cost of access to space.[1][2][3][4]

History

SpaceX first announced in March 2013 that it would instrument and equip subsequent Falcon 9 first stages as controlled-descent test vehicles, able to propulsively decelerate towards a soft touchdown over the water surface. The company expected to begin these flight tests in 2013, with an attempt to return the vehicle to the launch site for a powered landing no earlier than mid-2014.[5]

In the event, SpaceX did perform their first controlled-descent test flight in 2013 but continued the over-water testing well into 2015. Following analysis of telemetry data from the first controlled descent in September 2013, SpaceX announced that a large amount of new technology passed their real-life test objectives, and that coupled with the technology advancements made on the Grasshopper low-altitude landing demonstrator, they were now ready to test the full EDL process to recover the first stage. The rocket was "able to successfully transition from vacuum through hypersonic, through supersonic, through transonic, and light the engines all the way and control the stage all the way through [the atmosphere]".[6]

This second EDL test took place during the third cargo resupply mission for NASA in April 2014. SpaceX attached landing legs to the first stage, decelerated the stage through atmospheric re-entry and attempted a simulated landing over water, following the separation of the second stage carrying the Dragon capsule to the ISS. The first stage was slowed down sufficiently to perform a soft touchdown over the Atlantic Ocean.[7][8] SpaceX announced in February 2014 that they intended to continue over-water tests of the first stage until mastering precision control of the vehicle from hypersonic speed all the way through subsonic regimes.[8]

Subsequent tests, starting with the CRS-5 mission in January 2015, attempted to land the first stage on an autonomous spaceport drone ship stationed off the Florida coastline or in the Pacific Ocean depending on launch site.[9] The ships were used for six landing attempts, two of which succeeded in April and May 2016. Meanwhile, the first attempt to land on solid ground at Cape Canaveral occurred on December 21, 2015, and succeeded flawlessly.

Post-mission test plan

Falcon 9 v.1.1 thermal imaging of the controlled-descent test of the first stage from stage separation onward, on Falcon 9 Flight 13, September 21, 2014. Includes footage as the first stage maneuvers out of the second stage plume; coasting near peak altitude of approximately 140 km (87 mi); boost-back burn to limit downrange translation; preparing for the reentry burn; and the reentry burn from approximately 70 km (43 mi) to 40 km (25 mi) altitude. Does not include the landing burn as clouds obscured the infrared imaging at low altitude.

The post-mission Falcon 9 test plan for the earliest flight tests called for the first stage to do a retro-propulsion burn in the upper atmosphere to slow it down and put it on a descent ballistic trajectory to its target landing location, followed by a second burn in the lower atmosphere before the first stage reached the water.[10] SpaceX announced in March 2013 that it intended to conduct such tests on Falcon 9 v1.1 launch vehicles and would "continue doing such tests until they can do a return to the launch site and a powered landing". The company said it expected several failures before it could land the vehicle successfully.[8][11]

In detailed information disclosed in the Falcon 9 Flight 6 launch license for the CASSIOPE mission, SpaceX said it would fire three of the nine Merlin 1D engines initially to slow the horizontal velocity of the rocket and begin the attempt at a controlled descent.[10] Then, shortly before hitting the ocean, one engine would be relighted in an attempt to reduce the stage's speed so that it could be recovered. As of September 10, 2013, SpaceX said the experiment had approximately a ten percent chance of success.[12]

SpaceX did not perform controlled-descent tests on all Falcon 9 v1.1 flights.[13] In September 2013, SpaceX announced that the fourth Falcon 9 v1.1 flight—which occurred in April 2014[14]—would be the second test of the first stage controlled descent test profile.[1]

Whereas the early tests restarted the engines only twice, by the fourth flight test, in September 2014, SpaceX was reigniting the engines three times to accomplish its EDL test objectives (although only three of the nine engines are used): a boost-back burn, a reentry burn, and a landing burn. The boost-back burn limits downrange translation of the used stage; the reentry burn (from approximately 70 to 40 km (43 to 25 mi) altitude) is used to control the descent and deceleration profile at atmospheric interface; and the landing burn completes the deceleration from terminal velocity to zero velocity at the landing surface.[15][16]

Test flights

Ocean touchdown attempts

Flight 6

The first EDL test occurred on September 29, 2013, on Falcon 9 Flight 6, the maiden launch of the Falcon 9 rocket, version v1.1. After the three-minute boost phase and separation of the second stage with the CASSIOPE and nanosat payloads, the rocket's first stage was reoriented backwards and three of the nine Merlin 1D engines were reignited at high altitude to initiate a deceleration and controlled descent trajectory to the surface of the ocean. The first phase of the test "worked well and the first stage re-entered safely".[17] However, the stage began to roll because of aerodynamic forces during the atmospheric descent and the roll rate exceeded the capabilities of the first stage attitude control system (ACS) to null it out. The fuel in the tanks "centrifuged" to the outside of the tank and the single engine involved in the low-altitude deceleration maneuver shut down. SpaceX was able to retrieve some first-stage debris from the ocean.[1][17] The company did not expect to recover the first stage on this flight,[18] nor on the first several powered-descent tests, as predicted in their March 2013 announcement.[5]

This first experimental descent was considered successful, achieving substantial test milestones and collecting a great deal of engineering data, despite losing the stage into the ocean.[18] SpaceX tested a large amount of new technology on this flight, and, combining those results with the advances made on the Grasshopper demonstrator, the company now believed it had "all the pieces of the puzzle".[6][18][19]

Flight 9

The second test of controlled-descent hardware and software on the first stage occurred on April 18, 2014,[7] and became the first successful controlled ocean soft touchdown of a liquid-rocket-engine orbital first stage.[20][21] The first stage included landing legs for the first time which were extended to simulate a landing upon touchdown, and the test utilized more powerful gaseous Nitrogen control thrusters to control the aerodynamic-induced rotation that had occurred on the first test flight. The first stage successfully approached the water surface with no spin and at zero vertical velocity, as designed.[8][22]

During the second test, the first stage was traveling at a velocity of Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value).[22] at an altitude of 80 kilometers (260,000 ft)[23] at the time of the high-altitude turn-around maneuver, followed by ignition of three of the nine main engines for the initial deceleration and placement onto its descent trajectory.[3] The "first stage executed a good re-entry burn and was able to stabilize itself on the way down. ... [The] landing in [the] Atlantic [ocean] was good! ... Flight computers continued transmitting [telemetry data] for 8 seconds after reaching the water" and stopped only after the first stage went horizontal.[24]

The major modifications for the second first stage controlled-descent test flight included changes to both the reentry burn and the landing burn as well as adding increased attitude control system (ACS) capabilities.[25]

SpaceX had projected a low probability of stage recovery following the flight test due to complexity of the test sequence and the large number of steps that would need to be carried out perfectly.[8] The company was careful to label the entire flight test as "an experiment".[26] In an press conference at the National Press Club on April 25, Elon Musk said that the first stage achieved a soft touchdown on the ocean but due to rough seas, the stage was destroyed.[27][28]

Flight 10

The third test flight of a returned first stage was July 14, 2014, on Falcon 9 Flight 10. Whereas the previous test reached a target landing area some hundreds of kilometers off the Florida coast, this flight aimed for a boost-back trajectory that would attempt the ocean touchdown much nearer the coast, and closer to the original launch location at Cape Canaveral. Following the third controlled-descent test flight, SpaceX expressed confidence in their ability to successfully land in the future on a "floating launch pad or back at the launch site and refly the rocket with no required refurbishment."[29]

Following the first stage loft of the second stage and payload on its orbital trajectory, SpaceX conducted a successful flight test on the spent first stage. The first stage successfully decelerated from hypersonic speed in the upper atmosphere, made a successful reentry, landing burn, and deployment of its landing legs, and touched down on the ocean surface. The first stage was not recovered for analysis as the hull integrity was breached, either upon touchdown or on the subsequent "tip over and body slam".[30] Results of the post-landing analysis showed that the hull integrity was lost as the 46-metre (150 ft)-tall first stage fell horizontally, as planned, onto the ocean surface following the landing.[29]

Flight 13

Infrared thermal imagery of Falcon 9 SpaceX CRS-4 launch. The larger image was captured shortly after second stage separation from the first stage: the top of the first stage appears as a dim dot below the larger plume. In the inset, the restarted first stage engines power the stage.

The fourth test flight of a returned first stage, with a planned ocean touchdown, occurred on Falcon 9 Flight 13 which was launched on September 21, 2014.[31] and the first stage flew a profile approaching a zero-velocity at zero-altitude simulated landing on the sea surface.[16] SpaceX made no attempt to recover the first stage, since earlier tests had confirmed that the 14-story tall first stage would not survive the tip-over event into the sea.

One month later, detailed thermal imaging infrared sensor data and video were released of the controlled-descent test. The data was collected by NASA in a joint arrangement with SpaceX as part of research on retropropulsive deceleration technologies in order to develop new approaches to Mars atmospheric entry. A key problem with propulsive techniques is handling the fluid flow problems and attitude control of the descent vehicle during the supersonic retropropulsion phase of the entry and deceleration. All phases of the night-time flight test on the first stage were successfully imaged except for the final landing burn, as that occurred below the clouds where the IR data was not visible.[16] The research team is particularly interested in the 70–40-kilometer (43–25 mi) altitude range of the SpaceX "reentry burn" on the Falcon 9 Earth-entry tests as this is the "powered flight through the Mars-relevant retropulsion regime" that models Mars entry and descent conditions.[15]

Flight 15

Falcon 9 Flight 15 first stage re-entry with grid fins. Onboard camera view

SpaceX had planned to make the sixth controlled-descent test flight and second[32] landing attempt on their drone ship no earlier than February 11. Landing a returning rocket at sea would have been a "potentially historic rocket launch and landing", as such a feat "was unheard of" five years earlier.[32][33][34]

According to regulatory paperwork filed in 2014, SpaceX plans had called for the sixth test flight to occur on a late January 2015 launch attempt. However, after the completion of the fifth test flight, and with some damage being incurred by the drone ship in the botched landing, it was not clear whether the sixth test would still be feasible only a few weeks later.[35] This issue was resolved within days of the ship's return to Jacksonville, and by January 15, SpaceX was unambiguous about its plans to attempt a landing of the first stage following the boost phase of the Deep Space Climate Observatory mission.[34]

However, in a statement by SpaceX, the drone ship was in conditions "with waves reaching up to three stories in height crashing over the decks". Additionally, one of the four thrusters that keep the barge in a constant position had malfunctioned, making station-keeping difficult. For these reasons, the post-launch flight test did not involve the barge, but instead attempted a soft touchdown over water.[36]

The test was successful, and the first stage of the Falcon 9 landed "nicely vertical" with an accuracy of 10 meters from the target location in the ocean.[37]

Therefore, this test represented the fifth ocean touchdown, and the sixth overall Falcon 9 first stage controlled-descent test.

Landing attempts

Depiction of Falcon 9 landing trajectory in floating-platform recovery tests

As of May 2016, SpaceX has attempted eight landings of a first stage on a solid surface, four of which have succeeded.

In July 2014, SpaceX announced that the fifth and sixth controlled-descent test flights would attempt to land on a solid surface, merging the lessons from the high-altitude envelope expansion of the first four controlled-descent flights over water with the low-altitude lessons of the F9R Dev testing in Texas.[31] At that time, the "solid surface" was not further described, and was later revealed to be a seafaring barge dubbed an autonomous spaceport drone ship.

Many of the test objectives were achieved on the first attempt, including bringing the stage to the specific location of the floating platform and collecting a large amount of test data with the first use of grid fin control surfaces for more precise reentry positioning. However the touchdown on the corner of the barge was a hard landing and most of the rocket body fell into the ocean and sank; SpaceX published a short clip of the crash.[38] It would take four more attempts to achieve the first barge landing at sea on flight 23.[39] Meanwhile, ground landing succeeded on the first attempt with flight 20 on December 21, 2015.[40]

Flight 14

In October 2014, SpaceX clarified that the "solid surface" would be a floating platform constructed from a barge in Louisiana, and confirmed that they would attempt to land the first stage of the fourteenth Falcon 9 flight on the platform.[41] For the landing to succeed, the 18 m (60 ft)-wide span of the rocket landing legs must not only land within the 52 m (170 ft)-wide barge deck, but would need to also deal with ocean swell and GPS errors.[42] In late November, SpaceX revealed that the landing barge would be capable of autonomous operation and would not need to be anchored or moored;[9] it was hence called an autonomous spaceport drone ship. As of September 2015 three of these ships had been built, two of which were operational.[citation needed]

This fifth controlled-descent test flight was anticipated by the specialized press as a historic core return attempt.[43] It incorporated for the first time in an orbital mission the grid fin aerodynamic control surfaces that had previously been tested only during a low-altitude, low-speed test with the F9R Dev1 prototype vehicle in early 2014. The addition of grid fins, with continuation of the control authority obtained from gimbaling the engines as on previous test flights, was projected to improve the landing accuracy to 10 m (33 ft), a thousand-fold improvement over the four previous test flights which landed within 10 km (6.2 mi) of their target coordinates.[44] Prior to the flight, SpaceX projected that the likelihood of success on the first try was 50 percent or less.[42]

The first test flight for this new hardware occurred on January 10, 2015, on the CRS-5 mission for NASA. The controlled-descent flight started approximately three minutes after launch, following the second stage separation event,[43] when the first stage was approximately 80 km (50 mi) high and moving at a velocity of Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value)..[45]

The SpaceX webcast indicated that the boostback burn and reentry burns for the descending first stage occurred, and that the descending rocket then went "below the horizon," as expected, which eliminated the live telemetry signal. Shortly thereafter, SpaceX released information that the rocket did get to the drone spaceport ship as planned, but "landed hard ... Ship itself is fine. Some of the support equipment on the deck will need to be replaced."[46][47][48] Musk later elaborated that the rocket's flight-control surfaces had exhausted their supply of hydraulic fluid prior to impact.[49] Musk posted photos of the impact while talking to John Carmack on Twitter. SpaceX later released a video of the impact on Vine.[38]

Falcon 9 first stage attempts landing on ASDS after second stage with CRS-6 continued onto orbit. Landing legs are in the midst of deploying.

Flight 17

Falcon 9 Flight 17's first stage attempting a controlled landing on the Autonomous Spaceport Drone Ship following the launch of CRS-6 to the International Space Station.

A seventh test flight of the first stage controlled-descent profile occurred on April 14, 2015, on Falcon 9 Flight 17, which carried CRS-6 to the International Space Station. This was SpaceX's second attempt to land on a floating platform. The first stage was fitted with grid fins and landing legs to facilitate the post-mission test.

An early report from Elon Musk suggested that the first stage made a hard landing on the drone ship.[50] Musk later clarified that the bipropellant valve was stuck, and therefore the control system could not react rapidly enough for a successful landing.[51] On April 15, SpaceX released a video of the terminal phase of the descent, the landing, the tip over, and the resulting deflagration as the stage broke up on the deck of the ASDS.[52]

Falcon 9 Flight 20 after landing

Flight 20: first landing on ground pad

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

The first attempt to land the first stage of Falcon 9 on a ground pad near the launch site occurred on flight 20, the maiden flight of the Falcon 9 full thrust version, on the evening of December 21, 2015. The landing was successful and the first stage was recovered.[53][40] This was the first time in history that a rocket first stage returned to Earth after propelling an orbital launch mission and achieved a controlled vertical landing.

SpaceX applied to the Federal Aviation Administration (FAA) US regulatory authority to perform its eighth booster controlled-descent test culminating with a landing attempt at the Landing Zone 1 facility (formerly Launch Complex 13) that SpaceX had recently built at Cape Canaveral Air Force Station.[54] The FAA cleared SpaceX to attempt this landing after assessing that it would inflict minimal damage on the environment.[55][56] Additionally, NASA planned to close the NASA Causeway near the launch and landing site and significantly increase the size of exclusion zones during the launch and landing attempt.[57][58][needs update] Both options to attempt landing on the ground pad or on the drone ship at sea remained open until the day of the launch. The final decision to return the booster to Cape Canaveral was made based on a number of factors, including weather at the potential landing sites.[citation needed]

Falcon 9 Flight 20 first stage moments before touchdown on Landing Zone 1

Flight 20 took off at 20:29 EST on December 21, 2015 (01:29 UTC on December 22, 2015). About 9 minutes and 45 seconds later, the first stage landed vertically on the pad.[53][40][59]

SpaceX does not plan to fly the Falcon 9 Flight 20 first stage again.[60] Rather, the rocket was inspected and moved back to the launch pad a few miles north to perform a static fire test. After the hot fire test, the vehicle was evaluated in detail by SpaceX to assess capabilities for reflight of the launch vehicle design after future landings.

On December 31, SpaceX announced that no damage had been found on the stage and that it was ready to fire again.[61][62] On January 15, 2016, SpaceX conducted the static fire test on the recovered booster and reported a good overall outcome, except for some thrust fluctuations in one of the outer engines (engine 9). Elon Musk reported that this may have been due to debris ingestion.[63]

Flight 21

Landing approach of Falcon 9 Flight 21, which touched down at an acceptable velocity

Flight 21, the final launch of a Falcon 9 v1.1, carried the Jason 3 payload. At one point this was the first possible opportunity for an attempt to land the first stage on land,[64] but the launches were reordered following the loss of Falcon 9 Flight 19 in June 2015. Jason-3 was successfully launched on January 17, 2016, and while the first stage managed to slow down towards a soft landing, the lockout collet on one of the landing legs did not latch correctly, which caused the rocket to fall over and explode after touching down.[65][66] Elon Musk noted that ice buildup on the collet from the high-humidity launch conditions may have led to the failure of the latch.[67][68]

Flight 22

The next Falcon 9 mission had to launch the 5,271 kg (11,620 lb) heavy SES-9 communications satellite,[69][70] the rocket's largest payload yet targeting a highly-energetic geosynchronous transfer orbit (GTO). Consequently, the Falcon 9 first stage followed a ballistic trajectory after separation and re-entered the atmosphere at high velocity with very little fuel to mitigate potential aerodynamic damage.

Therefore, SpaceX could only attempt to land its Falcon 9 booster on a sea barge, the Of Course I Still Love You, positioned in the Atlantic Ocean. SpaceX founder and CEO Elon Musk confirmed in a tweet that the landing attempt had failed.[71][72]

Flight 23: first landing on drone ship

Falcon 9 Flight 23 landing on drone ship

On April 8, 2016, Falcon 9 Flight 23, the third flight of the full-thrust version, delivered the SpaceX CRS-8 cargo on its way to the International Space Station while the first stage conducted a boostback and re-entry maneuver over the Atlantic ocean. Nine minutes after liftoff, the booster landed vertically on the drone ship Of Course I Still Love You, 300 km (190 mi) from the Florida coastline, achieving a long-sought-after milestone for the SpaceX reusability development program.[39]

JCSAT-14 first stage on drone ship

Flight 24: first return from GTO mission

On May 6, 2016, Falcon 9 Flight 24 delivered the JCSAT-14 satellite on a geostationary transfer orbit (GTO) while the first stage conducted a re-entry burn under ballistic conditions without prior boostback. Following the controlled descent through the atmosphere, the booster executed a short landing burn as it approached the drone ship Of Course I Still Love You, and succeeded in landing vertically. This second landing at sea was more difficult than the previous one because the booster at separation was traveling about 8,350 km/h (5,190 mph) compared to 6,650 km/h (4,130 mph) on the CRS-8 launch to low Earth orbit.[73][74] Pursuing their experiments to test the limits of the flight envelope, SpaceX opted for a shorter landing burn with three engines instead of the single-engine burns seen in earlier attempts; this approach consumes less fuel by leaving the stage in free fall as long as possible and decelerating more sharply, thereby minimizing the amount of energy expended to counter gravity.[75] Elon Musk indicated this first stage may not be flown again instead being used as a life leader for ground tests to confirm others are good.[76]

Flight 25

On May 27, 2016, Falcon 9 Flight 25 delivered THAICOM 8 to a supersynchronous transfer orbit; despite high re-entry speed, the first stage again landed successfully on the SpaceX drone ship.[77]

Future tests

SpaceX aims to return a number of first stages in both ground and sea landings to clarify the procedures needed to re-use flown boosters. The company hopes to begin offering pre-flown Falcon 9 rocket stages commercially by the end of 2016,[78] aiming to re-launch a recovered stage as soon as June 2016.[79] In January 2016 Musk evaluated the likelihood of success to approximately 70 percent for landing attempts in 2016, hopefully rising to 90 percent in 2017; he also cautioned that the company expects "a few more RUDs" (Rapid Unscheduled Disassembly; Musk's euphemism to denote destruction of the vehicle on impact).[80]

See also

References

  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. 3.0 3.1 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. 5.0 5.1 Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.0 8.1 8.2 8.3 8.4 Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 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. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. 15.0 15.1 Lua error in package.lua at line 80: module 'strict' not found.
  16. 16.0 16.1 16.2 Lua error in package.lua at line 80: module 'strict' not found.
  17. 17.0 17.1 Lua error in package.lua at line 80: module 'strict' not found.
  18. 18.0 18.1 18.2 Lua error in package.lua at line 80: module 'strict' not found.
  19. 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. 22.0 22.1 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. Lua error in package.lua at line 80: module 'strict' not found.
  29. 29.0 29.1 Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. 31.0 31.1 Lua error in package.lua at line 80: module 'strict' not found.
  32. 32.0 32.1 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. 34.0 34.1 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. 38.0 38.1 Lua error in package.lua at line 80: module 'strict' not found.
  39. 39.0 39.1 Lua error in package.lua at line 80: module 'strict' not found.
  40. 40.0 40.1 40.2 Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. 42.0 42.1 Lua error in package.lua at line 80: module 'strict' not found.
  43. 43.0 43.1 Lua error in package.lua at line 80: module 'strict' not found.
  44. 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. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. 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. CRS-6 First Stage Landing, SpaceX, April 15, 2015.
  53. 53.0 53.1 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. Lua error in package.lua at line 80: module 'strict' not found.
  59. SpaceX Falcon9 1st Successful Launch/Landing on Target - YouTube
  60. Lua error in package.lua at line 80: module 'strict' not found.
  61. Lua error in package.lua at line 80: module 'strict' not found.
  62. Lua error in package.lua at line 80: module 'strict' not found.
  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. 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. Lua error in package.lua at line 80: module 'strict' not found.
  68. Lua error in package.lua at line 80: module 'strict' not found.
  69. Lua error in package.lua at line 80: module 'strict' not found.
  70. 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. You tube JCSat 14 hosted webcast
  74. You tube CRS8 hosted webcast
  75. Lua error in package.lua at line 80: module 'strict' not found.
  76. Florida Today Landed spacex rocket suffered max damage
  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. Lua error in package.lua at line 80: module 'strict' not found.
  80. Lua error in package.lua at line 80: module 'strict' not found.

External links