Dragon C2+

From Infogalactic: the planetary knowledge core
(Redirected from COTS Demo Flight 2)
Jump to: navigation, search
Dragon C2+
COTS2Dragon.6.jpg
Dragon approaching ISS on 25 May.
Mission type ISS resupply
Operator SpaceX/NASA
COSPAR ID 2012-027A
SATCAT № 38348
Mission duration 9 days
Spacecraft properties
Spacecraft type Dragon
Manufacturer SpaceX
Start of mission
Launch date 22 May 2012, 07:44:38 (2012-05-22UTC07:44:38Z) UTC[1]
Rocket Falcon 9 v1.0
Launch site Cape Canaveral SLC-40
Contractor SpaceX
End of mission
Disposal Recovered
Landing date 31 May 2012, 15:42 (2012-05-31UTC15:43Z) UTC
Landing site Lua error in package.lua at line 80: module 'strict' not found.[2]
Orbital parameters
Reference system Geocentric
Regime Low Earth
Inclination 51.6 degrees
Berthing at ISS
Berthing port Harmony nadir
Berthing date 25 May 2012, 16:02 UTC
Unberthing date 31 May 2012, 09:49 UTC
Time berthed 5 days 16 hours 5 minutes[3]
File:SpaceX COTS 2 emblem.png


← SpaceX COTS Demo Flight 1 SpaceX CRS-1

Dragon C2+, also known as SpaceX COTS Demo Flight 2 (COTS 2), was the second test-flight for SpaceX's uncrewed Dragon cargo spacecraft, launched on the third flight of the company's two-stage Falcon 9 launch vehicle. The flight was performed under a funded agreement from NASA as the second Dragon demonstration mission in the Commercial Orbital Transportation Services (COTS) program. The purpose of the COTS program is to develop and demonstrate commercial sources for cargo re-supply of the International Space Station (ISS). The Dragon C2+ spacecraft was the first American vehicle to visit the ISS since the end of the Space Shuttle program. It was also the first commercial spacecraft to rendezvous and berth with another spacecraft.[4]

Initially, the objectives of the C2+ mission were to have been accomplished by two separate missions; Dragon C2 would have carried out a fly-by of the ISS, practiced rendezvous maneuvers and communications with the station, before returning to Earth. A second mission, C3, would have been the first mission to berth with the station. In July 2011, NASA gave tentative approval to combine the objectives of the two missions. In December 2011, NASA formally approved the merger of the COTS 2 and 3 missions into the Dragon C2+ flight. There were several launch delays, the last one occurring on 19 May 2012, due to a launch abort during the last second before liftoff.

Dragon C2+ successfully launched from Cape Canaveral on 22 May 2012. During the mission's first three days all of the COTS 2 objectives were successfully completed. The mission's COTS 3 phase began on 25 May when Dragon rendezvoused again with the ISS and then was successfully captured using the Canadarm2. It was berthed to the station later that day, using the robotic arm. Dragon stayed for almost six days during which the astronauts unloaded cargo, and then reloaded Dragon with Earth-bound cargo. On 31 May, Dragon unberthed from the ISS, its capsule landed in the Pacific Ocean off the California coast and was recovered. All the objectives of the mission were successfully completed, and the Falcon 9-Dragon system became certified to start regular cargo delivery missions to the ISS under the Commercial Resupply Services program.

History

COTS 2 Dragon capsule being lowered onto its trunk at LC-40 on 16 November 2011 during pre-launch processing.

NASA and SpaceX signed a contract for COTS cargo resupply services on 18 August 2006.[5][6] The agreement called for three test-flights, under the COTS phase 1 demonstration program.[7] The first COTS mission, COTS Demo Flight1, was completed successfully on 8 December 2010, when the Dragon capsule was successfully recovered from orbit, making it the first commercially built and operated spacecraft to ever do so.[8] Due to the mission's success, SpaceX asked NASA to combine the COTS 2 ISS flyby flight, which would have seen a Dragon spacecraft approach the station but stay about 10 km away from it, and the COTS 3 flight that would berth with the ISS.[7] At a 15 July 2011 meeting, NASA tentatively approved combining the two COTS missions to accelerate the program into the operational supply mission phase in 2012.[9] On 9 December, NASA officially approved the merger of the COTS 2 and 3 missions into the renamed Dragon C2+ flight.[10][11]

The Falcon 9 launch vehicle arrived at SpaceX's Cape Canaveral, Florida facilities at Launch Complex 40 (LC-40) in July 2011.[12] The mission's Dragon spacecraft arrived at the launch site on 23 October 2011.[13] On 1 March 2012, a fueled countdown test called a Wet Dress Rehearsal (WDR), was successfully completed for the COTS 2 mission.[14] On 16 April its Flight Readiness Review (FRR) was completed by NASA and stated that a 30 April launch was feasible.[14][15] Following the review SpaceX announced a launch delay, due to continued flight software testing issues, and the next major mission milestone was the successful Falcon 9 static-fire engine test on 30 April.[16] NASA approved Dragon's flight software on 11 May, solving an issue that had previously been responsible for several launch date postponements.[17] On 17 May, the mission passed its final launch review and the Falcon 9/Dragon were erected on the launch pad in preparation for the launch.[18] The first launch attempt, on 19 May, was aborted at T-00:00:00.5 due to a pressure issue in one of the Falcon 9's engines.[19] The launch window was nearly instantaneous, for fuel-efficiency reasons, leaving little margin for error due to fuel consumption restrictions caused by the extra manoeuvres required to certify the Dragon spaceship before attempting to berth with the ISS.[20] Dragon's launch window could have been longer, but the extra fuel required to catch the ISS would have likely surpassed safety margins, due to the pre-berthing tests.[21][22]

Original plan

Under the original Dragon testing plan, the C2 and C3 missions would have been flown instead of C2+. C2 would have rendezvoused with the ISS, however it would not have performed the capture and berthing part of the mission. The third test-flight was intended to be Dragon's first mission to berth with the ISS. Following a 15 July 2011 meeting between SpaceX and NASA officials, the COTS 3 mission objectives were tentatively combined with the proposed COTS 2 demonstration flight, due to the Falcon 9's two previously successful launches, and the Space Transportation System's shuttle fleet recently being retired.[23]

On 9 December 2011, NASA formally approved the two missions' merger, and set the initial launch date for 7 February 2012.[24] Several delays occurred between December to May 2012, mostly due to SpaceX needing to further test hardware and software.[11] The Dragon C2+ mission successfully launched on 22 May, from Cape Canaveral Launch Complex 40 (SLC-40).[25] It successfully completed all COTS 2 mission objectives, then berthed with the ISS, and completed all COTS 3 mission objectives, before successfully splashing down in the Pacific Ocean, off the California coast on 31 May.[26] Since all COTS objectives were met during the Dragon C2+ flight in May 2012, the need for COTS Demo Flight 3 was eliminated.[27]

Mission timeline

Flight day 1, launch (22 May)

The COTS 2 Falcon 9 successfully launches with the Dragon spacecraft on 22 May 2012.

Launch occurred at 03:44 EDT (07:44 UTC) on 22 May 2012.[28] This was the first time a Falcon 9 was launched at night.[29] After lift-off, main engine shut-off occurred at approximately the 180-second mark, and the first stage began to be separated. Following stage separation, the second stage ignited.[21] The Dragon's nose cone was then jettisoned.[21] And at about nine minutes into the flight, the second-stage engine shut-off occurred and separated from the Dragon spacecraft.[21] The Dragon spacecraft successfully deployed its solar arrays at about 13 minutes into the flight.[21][30]

The initial COTS 2 tests began during this flight segment, when Dragon performed a test of its Absolute GPS (AGPS) system, using global positioning system satellites to determine its location.[20] Next, Dragon opened its bay door which housed its grapple fixture and relative navigation sensors, a thermal imager and the LIDAR based DragonEye.[31] After a checkout of these sensors was completed, Dragon demonstrated its ability to abort during an approach, first with a continuous firing of its Draco engines and then with a pulsed firing.[31] A free drift demonstration then began, allowing the spacecraft to float freely without using its thrusters which would normally correct its orbital path.[20][31]

Flight day 2 (23 May)

On flight day two, Dragon began a series of thruster burns, called "height adjustment" burn (HA-1), and "co-elliptical" burn (CE-1).[20][31][lower-alpha 1] The CE-1 burn changed Dragon's orbit characteristics by placing it into a circular orbit around the Earth.[20][31] The HA-1 burn raised Dragon's altitude to within a few kilometres below the ISS, in preparation for the next day's rendezvous demonstration.[33]

Flight day 3 (24 May)

Dragon spacecraft seen from the ISS during the fly-under on day three, 24 May 2012.

On flight day three, Dragon performed height adjustment burn 2 (HA-2) at 07:58 UTC, to get within about 10 km (6.2 mi) of the ISS, the "communication zone."[34][35] At 08:43 UTC co-elliptical burn 2 (CE-2) raised its orbit to nearly the same plane as the ISS, and brought it to within 2,500 m (8,200 ft) below the station.[35][36] During this "fly-under," Dragon established communications with the station using its COTS Ultra-high frequency Communication Unit (CUCU).[35] Dragon performed a test of its Relative GPS (RGPS) system, which used the relative positions of the spacecraft to the space station to determine its location.[37][38] Also, using the Crew Command Panel (CCP) on board the Cupola module, the Expedition 31 crew briefly interacted with Dragon, monitoring the fly-under and just before 11:00 UTC sending a command to Dragon to turn on its strobe light.[38] At about 11:25 UTC the Dragon made its closest approach to the ISS.[38] Once the fly-under was completed, Dragon fired its thrusters to begin a loop out in front, above and then behind the station in a racetrack oval pattern at a distance between 7 to 10 km (4.3 to 6.2 mi).[35] The Dragon performed a final burn for the day, at 11:57 UTC, that moved it away from the ISS, and set the spacecraft up for a re-rendezvous with the station the next day.[38] After Dragon cleared the station's vicinity, NASA approved the berthing to occur on day 4, meaning all the original COTS 2 mission requirements were met.[39][40]

Flight day 4 (25 May)

The Dragon spacecraft being berthed to the International Space Station on day four, 25 May 2012.

On flight day four, Dragon performed HA-3 and CE-3 thruster burns to bring it 2.5 km (1.6 mi) below the station once again.[41] NASA's Mission Control Houston team then gave SpaceX the go ahead to perform another set of burns that brought Dragon to within 1,400 m (4,600 ft) of the station.[41] Another decision was made at Mission Control Houston, and then Dragon moved to 250 m (820 ft) from the station.[42] At this point, the COTS 3 demonstration objectives began.[41] Dragon's DragonEye system demonstrated and confirmed that its position and velocity were accurate by comparing its LIDAR image to its thermal imagers.[41] A series of checkout maneuvers commenced. The SpaceX flight control team in Hawthorne, California, commanded the spacecraft to approach the station from its hold position.[41] It moved from 250 to 220 m (820 to 720 ft) below the station.[41] The crew, using the command panel, then instructed Dragon to retreat, and the spacecraft moved back down to the hold point.[41] This test ensured that Dragon's range to the ISS was accurate, and that the flight control team saw the spacecraft's acceleration and braking perform as expected.[41] It was in a holding pattern at 250 m (820 ft), and once again the Dragon flight team commanded it to approach the station.[41] At the 220 m (720 ft) position, the crew commanded the vehicle to hold.[41]

Another decision was made in Houston, and Dragon was permitted to enter the Keep-Out Sphere (KOS), a virtual area 200 m (660 ft) around the station intended to prevent collision with the orbiting complex.[43] Two additional and non-planned holds occurred: one at 150 m (490 ft) to further verify LIDAR; and finally one by SpaceX at 70 m (230 ft) to re-configure the LIDARs.[44] Stray reflections from the JAXA JEM module's External Facility (EF) caused interference with the LIDAR;[42] SpaceX decided to narrow the LIDAR's field-of-view to eliminate the reflections.[44]

Dragon proceeded to a position 30 m (98 ft) from the station and automatically came to a stop for a hold.[44] Another decision was made, and then Dragon proceeded to the capture point position at 9 m (30 ft).[44] A final decision was made, and the Mission Control Houston team notified the crew they were go to capture Dragon.[44] At that point, from the Cupola module, Expedition 31 crew member Don Pettit used the station's Mobile Servicing System (Canadarm2) to reach out and grapple the Dragon spacecraft at 13:56 UTC over Western Australia.[45] Upon capture, Pettit jokingly told ISS CAPCOM Megan McArthur, "Looks like we got us a Dragon by the tail. We're thinking this sim went really well, we're ready to turn it around and do it for real."[43] Pettit, with the help of fellow crewmember André Kuipers, guided and then berthed Dragon to the Harmony module's Earth-facing Common Berthing Mechanism at 16:02 UTC.[46]

Flight day 5 and remainder of mission (26 to 31 May)

Don Pettit opening Dragon's hatch on 26 May.

On flight day five, after evaluating air quality inside Dragon, the crew opened the hatch between Dragon and the station at 05:53 EDT (09:53 UTC).[47] Pettit and Russian cosmonaut and station commander Oleg Kononenko were the first crew members to enter the Dragon.[48] They wore protective goggles and breathing masks as they performed further tests to make sure the atmosphere inside the capsule was safe, which it was, though Pettit noted that "the inside smells like a brand new car."[49]

Dragon spent approximately six days berthed to the space station, allowing astronauts time to unload its cargo.[50] They then reloaded it with Earth-bound cargo.[51] On 27 May, while being controlled by Mission Control Houston, Dextre was used to survey Dragon's trunk.[52]

Recovery of the COTS 2 Dragon on 31 May.

On its final day at the station, 31 May, the crew unberthed Dragon from Harmony using the Canadarm2 at 05:49 EDT (09:49 UTC).[3] The arm moved Dragon about 10 m (33 ft) away from the station and released it.[3] Dragon then performed a series of engine burns that placed it on a trajectory to take it away from the vicinity of the station.[53] Mission Control Houston then confirmed that Dragon was on a safe path away from the complex.[53] SpaceX instructed Dragon to close its bay door and approximately four hours after Dragon left the station, it began to conduct its nine-minute-long deorbit burn.[37] The Dragon capsule jettisoned its trunk and began to re-enter the Earth’s atmosphere.[53] Its heatshield protected it during most of the re-entry and when low enough in altitude its two drogue parachutes were deployed, followed by its three main parachutes.[54] The Dragon capsule splashed down into the Pacific Ocean about 900 km (560 mi) from the Baja Peninsula at approximately 11:42 EDT (15:42 UTC) and was recovered by a small fleet of recovery vessels from the contractor hired by SpaceX, American Marine.[55][56][57]

Capsule journey post-mission

On 5 June, the Dragon capsule arrived at the Port of Los Angeles and was transported by truck to McGregor, Texas.[58] There its toxic maneuvering propellent was removed and on 13 June its cargo was transferred into NASA's possession.[59] The cargo was then transported to the Johnson Space Center in Houston for further processing.[59] On 18 July 2012, the COTS 2 Dragon was temporarily displayed to an invited audience inside a tent, in front of the Historical Society of Washington, D.C. building.[60] On 7 September 2012, Steve Jurvetson, a member on the board of directors at SpaceX, reported that the C2+ capsule was undergoing post-flight analysis back in McGregor.[61] Later in 2012 the Dragon capsule was expected to be transported back to Hawthorne, California.[59] During the post-flight press conference, the CEO and CTO of SpaceX Elon Musk stated that there are no definitive plans for the capsule but that he would like to see it taken on a tour around the United States.[62] The capsule was displayed at the 2013 Electronic Entertainment Expo in Los Angeles, California from 11 June to 13 June.[63][64] The historic Dragon C2+ capsule was ultimately placed on permanent display hanging from the ceiling at SpaceX headquarters.

On 23 August 2012, NASA announced that SpaceX and their Falcon 9-Dragon system was certified to begin their cargo delivery contract.[65] The $1.6 billion contract calls for at least 12 resupply missions.[66] The first of those flights was launched on 7 October 2012.

Payload

The interior of the Dragon spacecraft on 26 May, showing some of the delivered cargo.

The pressurized section carried 525 kg (1,157 lb) of cargo to the ISS, which included food, water, clothing, cargo bags, computer hardware, the NanoRacks Module 9 (student experiments and scientific gear) and other miscellaneous cargo.[67][68] No unpressurized cargo was delivered on this mission.[69]

An unannounced addition to the cargo manifest, made public after the launch, was a small canister, affixed to the second stage's top, containing the 1-gram ash remains of over 300 people including Project Mercury Astronaut Gordon Cooper, and James Doohan, the actor who played Scotty on the television show Star Trek in the 1960s.[70] The remains were flown semi-secretly by Celestis, a company that has flown burial canisters in the past on SpaceX's Falcon 1 launch vehicle.[71] The second stage and the burial canister remained in the initial orbit Dragon C2+ was inserted to,[72] and burned up in the Earth's atmosphere a month later.[73]

Some of the returned cargo is seen in McGregor, Texas on 13 June 2012.

On its return to Earth, Dragon brought back 665 kg (1,466 lb) worth of pressurized cargo back to Earth; the cargo included experiment samples, experiment hardware, ISS' systems hardware and Extravehicular Mobility Unit hardware.[67][74] One of the experiments returned by Dragon was the Shear History Extensional Rheology Experiment (SHERE) administered by NASA's Glenn Research Center.[75] SHERE investigated rotational stress effects on polymer fluids.[75] Items from SHERE included a toolbox, fluid modules, stowage trays, cables and a keyboard, and science data recordings.[75] Another experiment returning with Dragon was the Multi-user Droplet Combustion Apparatus (MDCA), and the Combustion Integrated Rack-Fluids and Combustion Facility (CIR).[75] The return flight was planned to carry 660 kg (1,460 lb)

Another experiment returning at the end of this mission was the Material Science Research Rack (MSRR), which investigated microgravity experiments on aluminum-alloy rods.[75] Returning from MSRR were cartridges from thermal and vacuum investigations done on metal rods in the SETA-2 and the MSL-CETSOL and MICAST studies.[75]

Originally, SpaceX also intended to launch two secondary payload satellites from the Dragon sometime in the first 72 hours after launch;[76] however, on 28 December 2011, SpaceX and Orbcomm announced a revised schedule that dropped the satellite deployment from the Dragon C2+ flight plan.[77]

Delays

COTS Demo Flight 2 was to take place as early as 2010, but was delayed by internal SpaceX issues; and then in 2011 by NASA issues.[78] As planned on the manifests, COTS 2 was to fly in June 2011.[10] It was delayed to late 2011, and then followed by further delay by the failure of the Russian Progress 44 cargo resupply vessel in August; this incident could have forced the ISS to be temporarily abandoned in mid-November.[79] Another delay was caused due to the berthing procedure which requires two ISS personnel to be trained and available for the procedure; in early December 2011 only one person was trained to berth the Dragon.[80] The launch date moved as follows: 6 June 2011, 8 October 30 November and 19 December;[81] and 7 January 2012, 30 April, and 7 May.[81]

With a busy launch schedule at Cape Canaveral, and with other missions to the ISS, NASA and SpaceX did not announce a new date until mid-March for a 30 April launch.[82][83] More testing was required by SpaceX for the computer code that controlled berthing, causing another delay to be announced on 23 April, delaying the launch to 7 May at 09:38 EDT (13:38 UTC).[84][85] A further delay was announced by NASA, pushing the launch to sometime in May.[84] On 4 May, the new targeted launch date was set for 19 May at 04:55 EDT/08:55 UTC. The launch proceeded nominally but was automatically aborted at T−00:00:00.5 when pressure in engine number 5 rose to unacceptable limits.[86] After making repairs, the launch date was set for 22 May at 03:44 EDT (07:44 UTC), with a secondary backup date of 23 May at 03:22 EDT (07:22 UTC) if a longer delay became necessary.[21]

Launch attempts

Attempt Planned Result Turnaround Reason Decision point Weather go (%) Notes
1 19 May 2012, 8:55:26 am Abort --- Technical 19 May 2012, 8:55 am(T−0:00:00.5) 80% Launch was automatically aborted with higher than acceptable pressure detected in engine 5.[87] This was due to a faulty check valve, which was then replaced later that day.[87]
2 22 May 2012, 7:44:38 am Success 2 days, 22 hours, 49 minutes 90% Nominal launch, inserted Dragon into preliminary orbit, nine minutes and 48 seconds after launch.[1]

Gallery

Notes

  1. A height adjustment burn is a thruster burn that changes the Dragon spacecraft's altitude, while the co-elliptical burn changes its shape. "Coelliptic orbits can be defined as two orbits that are coplanar and confocal. A property of coelliptic orbits is that the difference in magnitude between aligned radius vectors is nearly the same, regardless of where within the orbits they are positioned. For this and other reasons, coelliptic orbits are useful in rendezvous".[32]

See also

References

  1. 1.0 1.1 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 3.2 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. 7.0 7.1 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. 10.0 10.1 Lua error in package.lua at line 80: module 'strict' not found.
  11. 11.0 11.1 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. 14.0 14.1 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. 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. 20.0 20.1 20.2 20.3 20.4 Lua error in package.lua at line 80: module 'strict' not found.
  21. 21.0 21.1 21.2 21.3 21.4 21.5 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. 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. Lua error in package.lua at line 80: module 'strict' not found.
  31. 31.0 31.1 31.2 31.3 31.4 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. COTS 2 Mission Press Kit, p. 13.
  35. 35.0 35.1 35.2 35.3 Lua error in package.lua at line 80: module 'strict' not found.
  36. COTS 2 Mission Press Kit, p. 10.
  37. 37.0 37.1 Lua error in package.lua at line 80: module 'strict' not found.
  38. 38.0 38.1 38.2 38.3 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. 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. 44.0 44.1 44.2 44.3 44.4 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. Lua error in package.lua at line 80: module 'strict' not found.
  53. 53.0 53.1 53.2 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. 59.0 59.1 59.2 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. 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. 67.0 67.1 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. http://www.heavens-above.com/SatInfo.aspx?satid=38349&lat=0&lng=0&loc=Unspecified&alt=0&tz=UCT
  74. Lua error in package.lua at line 80: module 'strict' not found.
  75. 75.0 75.1 75.2 75.3 75.4 75.5 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. 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.
  81. 81.0 81.1 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. 84.0 84.1 Lua error in package.lua at line 80: module 'strict' not found.
  85. Lua error in package.lua at line 80: module 'strict' not found.
  86. Lua error in package.lua at line 80: module 'strict' not found.
  87. 87.0 87.1 Lua error in package.lua at line 80: module 'strict' not found.

Bibliography

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

External links