Hayabusa

From Infogalactic: the planetary knowledge core
(Redirected from Minerva (spacecraft))
Jump to: navigation, search

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

Hayabusa
Hayabusa hover.jpg
A computer rendering of Hayabusa above Itokawa's surface
Operator JAXA
Mission type Asteroid sample return
Launch date 9 May 2003
Launch vehicle M-V
Mission duration 7 years, 1 month and 4 days
Current destination Returned to Earth on 13 June 2010
COSPAR ID 2003-019A
Mass 510 kg (dry 380 kg)
Instruments
AMICA, LIDAR, NIRS, XRS

Hayabusa (はやぶさ?, literally "Peregrine Falcon") was an unmanned spacecraft developed by the Japan Aerospace Exploration Agency (JAXA) to return a sample of material from a small near-Earth asteroid named 25143 Itokawa to Earth for further analysis. Hayabusa, formerly known as MUSES-C for Mu Space Engineering Spacecraft C, was launched on 9 May 2003 and rendezvoused with Itokawa in mid-September 2005. After arriving at Itokawa, Hayabusa studied the asteroid's shape, spin, topography, colour, composition, density, and history. In November 2005, it landed on the asteroid and collected samples in the form of tiny grains of asteroidal material, which were returned to Earth aboard the spacecraft on 13 June 2010.

The spacecraft also carried a detachable minilander, MINERVA, which failed to reach the surface.

Mission firsts

File:D. Moura and J. Kawaguchi IAC 2010.jpg
Denis J. P. Moura (left) and Junichiro Kawaguchi (right) at the 2010 International Astronautical Congress (IAC)

Other spacecraft, notably Galileo and NEAR Shoemaker both sent by NASA, visited asteroids before, but the Hayabusa mission was the first attempt to return an asteroid sample to Earth for analysis.[1]

In addition, Hayabusa was the first spacecraft designed to deliberately land on an asteroid and then take off again (NEAR Shoemaker made a controlled descent to the surface of 433 Eros in 2000, but it was not designed as a lander and was eventually deactivated after it arrived). Technically, Hayabusa was not designed to "land"; it simply touches the surface with its sample capturing device and then moves away. However, it was the first craft designed from the outset to make physical contact with the surface of an asteroid. Junichiro Kawaguchi of the Institute of Space and Astronautical Science was appointed to be the leader of the mission.[2]

Despite its designer's intention of a momentary contact, Hayabusa did land and sit on the asteroid surface for about 30 minutes (see timeline below).

Mission profile

The Hayabusa spacecraft was launched on 9 May 2003 at 04:29:25 UTC on an M-V rocket from the Uchinoura Space Center (still called Kagoshima Space Center at that time). Following launch, the spacecraft's name was changed from the original MUSES-C to Hayabusa, the Japanese word for falcon. The spacecraft's xenon ion engines (four separate units), operating near-continuously for two years, slowly moved Hayabusa toward a September 2005 rendezvous with Itokawa. As it arrived, the spacecraft did not go into orbit around the asteroid, but remained in a station-keeping heliocentric orbit close by.

File:Hayabusa IAC 2010.jpg
The half-scale model of Hayabusa at the IAC in 2010

Hayabusa surveyed the asteroid surface from a distance of about 20 km, (the "gate position"). After this the spacecraft moved closer to the surface (the "home position"), and then approached the asteroid for a series of soft landings and for the collection of samples at a safe site. Autonomous optical navigation was employed extensively during this period because the long communication delay prohibits Earth-based real-time commanding. At the second Hayabusa touched down with its deployable collection horn, the spacecraft was programmed to fire tiny projectiles at the surface and then collect the resulting spray. Some tiny specks were collected by the spacecraft for analysis back on Earth.

After a few months in proximity to the asteroid, the spacecraft was scheduled to fire its engines to begin its cruise back to Earth. This maneuver was delayed due to problems with attitude control and the thrusters of the craft. Once it was on its return trajectory, the re-entry capsule was released from the main spacecraft three hours before reentry, and the capsule coasted on a ballistic trajectory, re-entering the Earth's atmosphere at 13:51, 13 June 2010 UTC. It is estimated that the capsule experienced peak deceleration of about 25 G and heating rates approximately 30 times those experienced by the Apollo spacecraft. It landed via parachute near Woomera, Australia.

In relation to the mission profile, JAXA defined the following success criteria and corresponding scores for major milestones in the mission prior to the launch of the Hayabusa spacecraft.[3] As it shows, the Hayabusa spacecraft is a platform for testing new technology and the primary objective of the Hayabusa project is the world's first implementation of microwave discharge ion engines. Hence 'operation of ion engines for more than 1000 hours' is an achievement that gives a full score of 100 points, and the rest of the milestones are a series of world's first-time experiments built on it.

File:Replica of Hayabusa capsule at JAXA i.jpg
The replica of the re-entry capsule exhibited at JAXAi (closed on December 28, 2010)
Success criteria for HAYABUSA Points Status
Operation of ion engines 50 points Success
Operation of ion engines for more than 1000 hours 100 points Success
Earth gravity assist with ion engines 150 points Success
Rendezvous with Itokawa with autonomous navigation 200 points Success
Scientific observation of Itokawa 250 points Success
Touch-down and sample collection 275 points Success
Capsule recovered 400 points Success
Sample obtained for analysis 500 points Success

MINERVA mini-lander

Hayabusa carried a tiny mini-lander (weighing only 591 g (20.8 oz), and approximately 10 cm (3.9 in) tall by 12 cm (4.7 in) in diameter) named "MINERVA" (short for Micro/Nano Experimental Robot Vehicle for Asteroid). An error during deployment resulted in the craft's failure.

This solar-powered vehicle was designed to take advantage of Itokawa's very low gravity by using an internal flywheel assembly to hop across the surface of the asteroid, relaying images from its cameras to Hayabusa whenever the two spacecraft were in sight of one another.[4]

MINERVA was deployed on 12 November 2005. The lander release command was sent from Earth, but before the command could arrive, Hayabusa's altimeter measured its distance from Itokawa to be 44 m (144 ft) and thus started an automatic altitude keeping sequence. As a result, when the MINERVA release command arrived, MINERVA was released while the probe was ascending and at a higher altitude than intended, so that it escaped Itokawa's gravitational pull and tumbled into space.[5][6]

Had it been successful, MINERVA would have been the first space hopper to see action. Instead it joins ranks with the hopper carried on the failed Phobos 2 mission, which also never saw use.

Scientific and engineering importance of the mission

Scientists' current understanding of asteroids depends greatly on meteorite samples, but it is very difficult to match up meteorite samples with the exact asteroids from which they came. Hayabusa will help solve this problem by bringing back pristine samples from a specific, well-characterized asteroid. Hayabusa bridged the gap between ground observation data of asteroids and laboratory analysis of meteorite and cosmic dust collections.[7] Also comparing the data from the onboard instruments of the Hayabusa with the data from the NEAR Shoemaker mission will put the knowledge on a wider level.[citation needed]

The Hayabusa mission has a very deep engineering importance for JAXA, too. It allowed JAXA to further test its technologies in the fields of ion engines, autonomous and optical navigation, deep space communication, and close movement on objects with low gravity among others. Second, since it was the first-ever preplanned soft contact with the surface of an asteroid (the NEAR Shoemaker landing on 433 Eros was not preplanned) it has enormous influence on further asteroid missions.[citation needed]

Changes in mission plan

The Hayabusa mission profile was modified several times, both before and after launch.

  • The spacecraft was originally intended to launch in July 2002 to the asteroid 4660 Nereus (the asteroid (10302) 1989 ML was considered as an alternative target). However, a July 2000 failure of Japan's M-5 rocket forced a delay in the launch, putting both Nereus and 1989 ML out of reach. As a result, the target asteroid was changed to 1998 SF36, which was soon thereafter named for Japanese rocket pioneer Hideo Itokawa.[8]
  • Hayabusa was to deploy a small rover supplied by NASA and developed by JPL, called Muses-CN, onto the surface of the asteroid, but the rover was canceled by NASA in November 2000 due to budget constraints.
  • In 2002, launch was postponed from December 2002 to May 2003 to recheck the O-rings of its reaction control system since one of them had been found to be using a different material than specified.[9]
  • In 2003, while Hayabusa was en route to Itokawa, a large solar flare damaged the solar cells aboard the spacecraft. This reduction in electrical power reduced the efficiency of the ion engines, thus delaying the arrival at Itokawa from June to September 2005. Since orbital mechanics dictated that the spacecraft still had to leave the asteroid by November 2005, the amount of the time it was able to spend at Itokawa was greatly reduced and the number of landings on the asteroid was reduced from three to two.
  • In 2005, two reaction wheels that govern the attitude movement of Hayabusa failed; the X-axis wheel failed on July 31, and the Y-axis on October 2. After the latter failure, the spacecraft was still able to turn on its X and Y axes with its thrusters. JAXA claimed that since global mapping of Itokawa had been completed, this was not a major problem, but the mission plan was altered. The failed reaction wheels were manufactured by Ithaco Space Systems, Inc, New York, which was later acquired by Goodrich Company.
  • The 4 November 2005, 'rehearsal' landing on Itokawa failed, and was rescheduled.
  • The original decision to sample two different sites on the asteroid was changed when one of the sites, Woomera Desert, was found to be too rocky for a safe landing.
  • The 12 November 2005, release of the MINERVA miniprobe ended in failure.

Mission timeline

Up to the launch

The asteroid exploration mission by the Institute of Space and Astronautical Science (ISAS) originated in 1986–1987 when the scientists investigated the feasibility of a sample return mission to Anteros and concluded that the technology was not yet developed.[10] Between 1987 and 1994, joint ISAS / NASA group studied several missions: an asteroid rendezvous mission later became NEAR, and a comet sample return mission later became Stardust.[11]

In 1995, ISAS selected the asteroid sampling as an engineering demonstration mission, MUSES-C, Nereus as the first choice of target, 1989 ML as the secondary choice, and MUSES-C project started in fiscal year 1996. In early development phase, Nereus was considered out of reach and 1989 ML became the primary target.[12] July 2000 failure of M-V forced a delay in the launch from July 2002 to November/December, putting both Nereus and 1989 ML out of reach. As a result, the target asteroid was changed to 1998 SF36.[13] In 2002, launch was postponed from December 2002 to May 2003 to recheck O-rings of reaction control system since one of it was found using different material than specification.[9] On May 9, 2003 04:29:25 UTC, MUSES-C was launched by M-V rocket, and the probe was named "Hayabusa".

Cruising

Ion thruster checkout started on 27 May 2003. Full power operation started on 25 June.

Asteroids are named by their discoverer. ISAS asked LINEAR, the discoverer of 1998 SF36, to offer the name after Hideo Itokawa, and on 6 August, Minor Planet Circular reported that the target asteroid 1998 SF36 was named Itokawa.[14][15]

On October 2003, ISAS and two other national aerospace agencies were merged to form JAXA.

On 31 March 2004, ion thruster operation was stopped to prepare for the Earth swing-by.[16] Last maneuver operation before swing-by on 12 May.[17] On 19 May, Hayabusa performed Earth swing-by.[18][19][20][21][22][23][24] On 27 May, ion thruster operation was started again.[25]

On February 18, 2005, Hayabusa passed aphelion at 1.7 AU.[26] On 31 July, the X-axis reaction wheel failed. On 14 August, Hayabusa's first image of Itokawa was released. The picture was taken by the star tracker and shows a point of light, believed to be the asteroid, moving across the starfield.[27] Other images were taken from 22 to 24 August.[28] On 28 August, Hayabusa was switched over from the ion engines to the bi-propellant thrusters for orbital maneuvering. From 4 September, Hayabusa's cameras were able to confirm Itokawa's elongated shape.[29] From 11 September, individual hills were discerned on the asteroid.[30] On 12 September, Hayabusa was 20 km (12 mi) from Itokawa and JAXA scientists announced that Hayabusa had officially "arrived".[31]

In proximity of Itokawa

On 15 September 2005, a 'colour' image of the asteroid was released (which is, however, grey in colouring).[32] On 4 October, JAXA announced that the spacecraft had successfully moved to its 'Home Position' 7 km from Itokawa. Closeup pictures were released. It was also announced that the spacecraft's second reaction wheel, governing the Y-axis, had failed, and that the craft was now being pointed by its rotation thrusters.[33] On November 3, Hayabusa took station 3.0 km from Itokawa. It then began its descent, planned to include delivery of a target marker, and release of the Minerva minilander. The descent went well initially, and navigation images with wide-angle cameras were obtained. However, at 01:50 UTC (10:50 am JST) on 4 November, it was announced that due to a detection of an anomalous signal at the Go/NoGo decision, the descent, including release of Minerva and the target marker had been canceled. The project manager, Junichiro Kawaguchi, explained that the optical navigation system was not tracking the asteroid very well, probably caused by the complex shape of Itokawa. A few days delay was required to evaluate the situation and reschedule.[34][35]

On 7 November, Hayabusa was 7.5 km from Itokawa. On November 9, Hayabusa performed a descent to 70 m to test the landing navigation and the laser altimeter. After that, Hayabusa backed off to a higher position, then descended again to 500 m and released one of the target markers into space to test the craft's ability to track it (this was confirmed). From analysis of the closeup images, the Woomera Desert site (Point B) was found to be too rocky to be suitable for landing. The Muses Sea site (Point A) was selected as the landing site, for both first and, if possible, second landings.[36]

On 12 November, Hayabusa closed in to 55 m from the asteroid's surface. MINERVA was released but due to an error failed to reach the surface. On 19 November, Hayabusa landed on the asteroid. There was considerable confusion during and after the maneuver about precisely what had happened, because the high-gain antenna of the probe could not be used during final phase of touch-down, as well as the blackout during handover of ground station antenna from DSN to Usuda station. It was initially reported that Hayabusa had stopped at approximately 10 meters from the surface, hovering for 30 minutes for unknown reasons. Ground control sent a command to abort and ascend, and by the time the communication was regained, the probe had moved 100 km away from the asteroid. The probe had entered into a safe mode, slowly spinning to stabilize attitude control.[37][38] However, after regaining control and communication with the probe, the data from the landing attempt were downloaded and analyzed, and on 23 November, JAXA announced that the probe had indeed landed on the asteroid's surface.[39] Unfortunately, the sampling sequence was not triggered since a sensor detected an obstacle during descent; the probe tried to abort the landing, but since its altitude was not appropriate for ascent, it chose instead a safe descent mode. This mode did not permit a sample to be taken, but there is a high probability that some dust may have whirled up into the sampling horn when it touched the asteroid, so the sample canister currently attached to the sampling horn was sealed. On November 25, a second touchdown attempt was performed. It was initially thought that this time, the sampling device was activated;[40] however, later analysis decided that this was probably another failure and that no pellets were fired.[41] Due to a leak in the thruster system, the probe was put in a "safe hold mode".[42]

On 30 November, JAXA announced that control and communication with Hayabusa had been restored, but a problem remained with the craft's reaction control system, perhaps involving a frozen pipe. Mission control was working to resolve the problem before the craft's upcoming launch window for return to Earth.[43] On December 6, Hayabusa was 550 km from Itokawa. JAXA held a press conference about the situation so far.[44][45] On 27 November, the probe experienced a power outage when trying altitude correction, probably due to a fuel leakage. On 2 December, an altitude correction was attempted, but the thruster did not generate enough force. On 3 December, the probe's Z-axis was found to be 20 to 30 degrees from the Sun direction and increasing. On 4 December, as an emergency measure, xenon propellant from the ion engines was blown to correct the spin, and it was confirmed successful. Altitude control was commanded using the xenon gas. On 5 December, altitude was corrected enough to regain communication through the medium gain antenna. Telemetry was obtained and analyzed. As the result of telemetry analysis, it was found that there was a strong possibility that the sampler projectile had not penetrated when it landed on 25 November. Due to the power outage, the telemetry log data was faulty. On 8 December, a sudden altitude change was observed, and communication with Hayabusa was lost. It was thought likely that the turbulence was caused by evaporation of 8 or 10cc of leaked fuel. This forced a wait of a month or two for Hayabusa to stabilize by conversion of precession to pure rotation, after which the rotation axis needed to be directed toward the Sun and Earth within a specific angular range. The probability of achieving this was estimated at 60% by December 2006, 70% by spring 2007.[46][47]

Recovery and return to Earth

On 7 March 2006, JAXA announced[48][49] that communication with Hayabusa had been recovered in the following stages: On 23 January, the beacon signal from the probe was detected. On 26 January, the probe responded to commands from ground control by changing beacon signal. On 6 February, an ejection of xenon propellant was commanded for attitude control to improve communication. The spin axis change rate was about two degrees per day. On 25 February, telemetry data was obtained through low-gain antenna. On 4 March, telemetry data was obtained through medium-gain antenna. On 6 March, Hayabusa's position was established at about 13,000 km ahead of Itokawa in its orbit with a relative speed of 3 m per second.

On 1 June, Hayabusa project manager Junichiro Kawaguchi reported[50] that they confirmed two out of four ion engines work normally, which would be sufficient for the return journey. On 30 January 2007, Jaxa reported that 7 out of 11 batteries are working and the return capsule was sealed.[51] On 25 April, JAXA reported that Hayabusa started the return journey.[52][53] On 29 August, it was announced that Ion Engine C onboard Hayabusa, in addition to B and D, has been successfully re-ignited.[54] On 29 October, JAXA reported that the first phase of trajectory maneuver operation has finished and the spacecraft is now put in spin-stabilized state.[55] On 4 February 2009, JAXA reported success in reignition of ion engines and starting second phase of trajectory correction maneuver to return to the Earth.[56] On 4 November 2009, the ion engine D automatically stopped working due to the anomaly from degradation.[57]

On 19 November 2009, JAXA announced that they managed to combine the ion generator of ion engine B and the neutralizer of ion engine A.[58] It is suboptimal but expected to be sufficient to generate the necessary delta-v. Out of 2,200 m/s delta-v necessary to return to the Earth, about 2,000 m/s had been performed already, and about 200 m/s still necessary.[59] On 5 March 2010, Hayabusa was on a trajectory that would have passed within the lunar orbit. Ion engine operation was suspended to measure the precise trajectory in preparation to perform Trajectory Correction Maneuver 1 to the Earth-rim trajectory.[60][61] On 27 March, 06:17 UTC, Hayabusa was on a trajectory which would pass 20,000 km from Earth center, completing the orbit transfer operation from Itokawa to Earth.[62] By 6 April, completed first stage of Trajectory Correction Maneuver (TCM-0) which controlled coarsely to Earth rim trajectory. It was planned to be 60 days before reentry.[63][64][65][66] By 4 May, completed TCM-1 maneuver to control precisely to Earth rim trajectory.[67] On 22 May, TCM-2 started, continued for about 92.5 hours, and finished on 26 May.[68] TCM-3 from 3 through 5 June to change the trajectory from the Earth rim to Woomera, South Australia,[69][70] TCM-4 was performed on June 9 for about 2.5 hours for a precision control to Woomera Prohibited Area.[71]

The reentry capsule was released at 10:51 UTC of 13 June.

Reentry and capsule retrieval

File:Hayabusa reentry from Ames Research 2010-06-13 25seconds.png
The glowing return capsule is seen forward of and below the parent Hayabusa probe bus as the latter breaks up.

The reentry capsule and the spacecraft reentered Earth's atmosphere on 13 June 2010 at 13:51 UTC (23:21 local).[72] The heat-shielded capsule made a parachute landing in the South Australian outback while the spacecraft broke up and incinerated in a large fireball.[73]

An international team of scientists observed the 12.2 km/s entry of the capsule from 11.9 km (39,000 ft) on board NASA's DC-8 airborne laboratory, using a wide array of imaging and spectrographic cameras to measure the physical conditions during atmospheric reentry in a mission led by NASA's Ames Research Center, with Peter Jenniskens of the SETI Institute as the project scientist.[74][75]

Since the reaction control system no longer functioned, the 510 kilograms (1,120 lb) space probe re-entered the Earth's atmosphere similar to the approach of an asteroid along with the sample re-entry capsule, and, as mission scientists expected, the majority of the spacecraft disintegrated upon entry.[76]

File:Hayabusa Re-Entery.jpg
The re-entry seen from the Woomera Test Range.

The return capsule was predicted to land in a 20 km by 200 km area in the Woomera Prohibited Area, South Australia. Four ground teams surrounded this area and located the re-entry capsule by optical observation and a radio beacon. Then a team on board a helicopter was dispatched. They located the capsule and recorded its position with GPS. The capsule was successfully retrieved at 07:08 UTC (16:38 local) of 14 June 2010.[77] The two parts of the heat shield, which were jettisoned during the descent, were also found.[78]

File:Hayabusa reentry from Ames Research 2010-06-13.ogv
Hayabusa re-entry filmed by a camera onboard NASA's DC-8 Airborne Laboratory. The glowing return capsule is seen forward of and below the main Hayabusa probe bus as the latter breaks up. The heat-shielded capsule continues leaving a wake after the main bus fragments have faded. (Close-up video)

After confirming that the explosive devices used for parachute deployment were safe the capsule was packed inside a double layer of plastic bags filled with pure nitrogen gas to reduce the risk of contamination. The soil at the landing site was also sampled for reference in case of contamination. Then the capsule was put inside a cargo container which had air suspension to keep the capsule below 1.5 G shock during transportation.[79] The capsule and its heat shield parts were transported to Japan by a chartered plane and arrived at the curation facility at the JAXA/ISAS Sagamihara campus on June 18.[80]

A Tokyo Metropolitan Government adviser and former lieutenant general, Toshiyuki Shikata, claimed that part of the rationale for the reentry and landing part of the mission was to demonstrate "that Japan's ballistic missile capability is credible."[81]

Scientific study of samples

Before the capsule was extracted from the protecting plastic bag, it was inspected using X-ray CT to determine its condition. Then the sample canister was extracted from the reentry capsule. The surface of the canister was cleaned using pure nitrogen gas and carbon dioxide; it was then placed in the canister opening device. The internal pressure of the canister was determined by a slight deformation of the canister as the pressure of the environment nitrogen gas in the clean chamber was varied. The nitrogen gas pressure was then adjusted to match the internal canister pressure to prevent the escape of any gas from the sample upon the opening of the canister.[82]

Confirmation of asteroid particles

On 16 November 2010, JAXA confirmed that most of the particles found in one of two compartments inside the Hayabusa sample return capsule came from Itokawa.[83] Analysis with a scanning electron microscope identified about 1,500 grains as rocky particles, according to the JAXA press release.[84] After further studying the analysis results and comparison of mineral compositions, most of them were judged to be of extraterrestrial origin, and definitely from the asteroid Itokawa.[85]

According to Japanese scientists, the composition of Hayabusa's samples was more similar to meteorites than known rocks from Earth. Their size is mostly less than 10 micrometers.[86] The material matches chemical maps of Itokawa from Hayabusa's remote sensing instruments. The researchers found concentrations of olivine and pyroxene in the Hayabusa samples.

Further study of the samples had to wait until 2011 because researchers were still developing special handling procedures to avoid contaminating the particles during the next phase of research.

In 2013 JAXA announced that 1500 extraterrestrial grains had been recovered, comprising the minerals olivine, pyroxene, plagioclase and iron sulphide. The grains were about 10 micrometers in size.[87] JAXA performed detailed analyses of the samples by splitting particles and examining their crystal structure at SPring-8.[88]

Results

The August 26, 2011, issue of Science devoted six articles to findings based on dust collected by Hayabusa.[89] Scientists' analysis of the dust from Itokawa suggested that it had probably originally been part of a larger asteroid. Dust collected from the asteroid surface was believed to have been exposed there for about eight million years.[89]

Dust from Itokawa was found to be "identical to material that makes up meteorites."[89] Itokawa is an S-type asteroid whose composition matches that of an LL chondrite.[90]

In popular culture

In Japan, rival film companies announced the production of three different feature length theatrical films based on the story of Hayabusa, one of which, Hayabusa: Harukanaru Kikan, starred Ken Watanabe.[91][92]

The Lego construction toy company released a model of Hayabusa through their Cuusoo website.[93]

Many references to Hayabusa appear in the Japanese series Kamen Rider Fourze, a space-themed tokusatsu series.

A music video titled "Hayabusa", named after the unmanned spacecraft was made using the Vocaloid Hatsune Miku. The music and lyrics were composed by SHO.

See also

References

  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. 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. "Japan's asteroid archaeologist", Sky and Telescope, June 2005, pp. 34–37
  8. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. Mission Accomplished For Japan's Asteroid Explorer Hayabusa
  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. 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. 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. 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. Japan launches second asteroid mission (Physicsworld.com, Dec 3, 2014)
  88. Lua error in package.lua at line 80: module 'strict' not found.
  89. 89.0 89.1 89.2 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. Lua error in package.lua at line 80: module 'strict' not found.
  92. Shoji, Kaori, "In a galaxy not so far away....", Japan Times, 23 September 2011, p. 20.
  93. Lua error in package.lua at line 80: module 'strict' not found.

Further reading

  • Lua error in package.lua at line 80: module 'strict' not found.
  • 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