Chelyabinsk meteor

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
2013 Chelyabinsk meteor
(image link)
Meteor fireball seen from Kamensk-Uralsky where it was still dawn, in an oblast north of Chelyabinsk

Chelyabinsk meteor is located in Russia
Chelyabinsk meteor
Location of the meteor
Time 09:20 YEKT (UTC+06:00)
Date 15 February 2013 (2013-02-15)
Location <templatestyles src="Plainlist/styles.css"/>
Coordinates Lua error in package.lua at line 80: module 'strict' not found.[1]
Also known as Chelyabinsk meteorite[2]
Cause Meteor air burst
Non-fatal injuries 1,491[3]
Property damage Over 7,200[4] damaged buildings, collapsed factory roof, shattered windows

The Chelyabinsk meteor was a superbolide caused by a near-Earth asteroid that entered Earth's atmosphere over Russia on 15 February 2013 at about 09:20 YEKT (03:20 UTC), with a speed of 19.16 ± 0.15 kilometres per second (60,000[5]–69,000 km/h or 40,000[5]–42,900 mph).[6][7] It quickly became a brilliant superbolide meteor over the southern Ural region. The light from the meteor was brighter than the Sun, up to 100 km away. It was observed over a wide area of the region and in neighbouring republics. Some eyewitnesses also felt intense heat from the fireball.

On account of its high velocity and shallow angle of atmospheric entry, the object exploded in an air burst over Chelyabinsk Oblast, at a height of around 29.7 km (18.4 miles, 97,400 feet).[7][8] The explosion generated a bright flash, producing a hot cloud of dust and gas that penetrated to 26.2 km, and many surviving small fragmentary meteorites, as well as a large shock wave. The bulk of the object's energy was absorbed by the atmosphere, with a total kinetic energy before atmospheric impact equivalent to approximately 500 kilotons of TNT (about 1.8 PJ), 20–30 times more energy than was released from the atomic bomb detonated at Hiroshima.

The object was undetected before its atmospheric entry, in part because its radiant was close to the Sun. Its explosion created panic among local residents, and about 1,500 people were injured seriously enough to seek medical treatment. All of the injuries were due to indirect effects rather than the meteor itself, mainly from broken glass from windows that were blown in when the shock wave arrived, minutes after the superbolide's flash. Some 7,200 buildings in six cities across the region were damaged by the explosion's shock wave, and authorities scrambled to help repair the structures in sub-zero (°C) temperatures.

With an estimated initial mass of about 12,000–13,000 metric tonnes[7][8][9] (13,000–14,000 short tons, heavier than the Eiffel Tower), and measuring about 20 metres in diameter, it is the largest known natural object to have entered Earth's atmosphere since the 1908 Tunguska event, which destroyed a wide, remote, forested area of Siberia. The Chelyabinsk meteor is also the only meteor confirmed to have resulted in a large number of injuries.

The earlier-predicted close approach of another, larger asteroid that same day, the roughly 30-metre 367943 Duende (at the time still known by its provisional designation 2012 DA14) occurred about 16 hours later; the very different orbits of the two objects showed they were unrelated to each other.

Initial reports

The meteor's path in relation to the ground.

Local residents witnessed extremely bright burning objects in the sky in Chelyabinsk, Kurgan, Sverdlovsk, Tyumen, and Orenburg Oblasts, the Republic of Bashkortostan, and in neighbouring regions in Kazakhstan,[10][11][12] when the asteroid entered the Earth's atmosphere over Russia.[13][14][15][16][17] Amateur videos showed a fireball streaking across the sky and a loud boom several minutes afterwards.[18][19][20] Some eyewitnesses also felt intense heat from the fireball.[21]

The event began at 09:20:21 Yekaterinburg time,[7][8] several minutes after sunrise in Chelyabinsk, and minutes before sunrise in Yekaterinburg. According to eyewitnesses, the bolide appeared brighter than the sun,[11] as was later confirmed by NASA.[22] An image of the object was also taken shortly after it entered the atmosphere by the weather satellite Meteosat 9.[23] Witnesses in Chelyabinsk said that the air of the city smelled like "gunpowder",[23] "sulfur" and "burning odors" starting about 1 hour after the fireball and lasting all day.[8]

Atmospheric entry

Illustrating all "phases", from atmospheric entry to explosion.

The visible phenomenon due to the passage of an asteroid or meteoroid through the atmosphere is called a meteor.[24] If the object reaches the ground, then it is called a meteorite. During the Chelyabinsk meteoroid's traversal, there was a bright object trailing smoke, then an air burst (explosion) that caused a powerful blast wave, the cause of the damage to thousands of buildings in Chelyabinsk and its neighbouring towns. The fragments entered dark flight (without the emission of light) and created a strewn field of numerous meteorites on the snow-covered ground (officially named Chelyabinsk meteorites).

The last time a similar phenomenon was observed in the Chelyabinsk region was the Kunashak meteor shower of 1949, after which scientists recovered about 20 meteorites weighing over 200 kg in total.[25] The Chelyabinsk meteor is thought to be the biggest natural space object to enter Earth's atmosphere since the 1908 Tunguska event,[26][27][28] and the only one confirmed to have resulted in a large number of injuries,[29][Note 1] although a small number of panic-related injuries occurred during the Great Madrid Meteor Event of 10 February 1896.[30]

According to the Russian Federal Space Agency, preliminary estimates indicated the object was an asteroid moving at about 30 km/s in a "low trajectory" when it entered Earth's atmosphere. According to the Russian Academy of Sciences, the meteor then pushed through the atmosphere at a velocity of 15 km/s.[16][23][31] The radiant (the apparent position of origin of the meteor in the sky) appears from video recordings to have been above and to the left of the rising Sun.[32]

Early analysis of CCTV and dashcam video posted online indicated that the meteor approached from east by south, and exploded about 40 km south of central Chelyabinsk above Korkino at a height of 23.3 km (14.5 miles, 76,000 feet), with fragments continuing in the direction of Lake Chebarkul.[1][33][34][35] On 1 March 2013 NASA published a detailed synopsis of the event, stating that at peak brightness (at 09:20:33 local time), the meteor was 23.3 km (14.5 miles, 76,000 feet) high, located at 54.8°N, 61.1°E. At that time it was travelling at about 18.6 km/s (11.6 mi/s), (about 67,000 km/h, or about 41,750 mph) —almost 60 times the speed of sound.[1][36] In November 2013, results were published based on a more careful calibration of dash cam videos in the field weeks after the event during a Russian Academy of Sciences field study, which put the point of peak brightness at 29.7 km altitude and the final disruption of the thermal debris cloud at 27.0 km, settling to 26.2 km, all with a possible systematic uncertainty of +/- 0.7 km.[7][8]

A sample found by Ural Federal University scientists at Lake Chebarkul. The object is part of the Chelyabinsk meteorite.

The United States space agency NASA estimated the diameter of the bolide at about 17–20 m and has revised the mass several times from an initial 7,700 tonnes (7,600 long tons; 8,500 short tons),[13] until reaching a final estimate of 10,000 tonnes,[13][37][38][39][40] (11,000 short tons, greater than the total weight of the Eiffel Tower).[1][41] The air burst's blast wave, when it hit the ground, produced a seismic wave which registered on seismographs at magnitude 2.7.[42][43][44]

The Russian Geographical Society said the passing of the meteor over Chelyabinsk caused three blasts of different energy. The first explosion was the most powerful, and was preceded by a bright flash, which lasted about five seconds. Initial newspaper altitude estimates ranged from 30–70 km, with an explosive equivalent, according to NASA, of roughly 500 kilotonnes of TNT (2,100 TJ), although there is some debate on this yield.[45][46] (500 kt is exactly the same energy released by the Ivy King nuclear explosion in 1952). According to a paper in 2013 however, all these ~500 kiloton yield estimates for the meteor airburst are "uncertain by a factor of two because of a lack of calibration data at those high energies and altitudes."[7][8]

The hypocentre of the explosion was to the south of Chelyabinsk, in Yemanzhelinsk and Yuzhnouralsk. Due to the height of the air burst, the atmosphere absorbed most of the explosion's energy.[47][48] The explosion's blast wave first reached Chelyabinsk and environs between less than 2 minutes 23 seconds[49] and 2 minutes 57 seconds later.[50] The object did not release all of its kinetic energy in the form of a blast wave as some 90 kilotons of TNT (about 3.75 x 1014 joules, or 0.375 PJ) of the total energy of the main airburst's fireball was emitted as visible light according to NASA's Jet Propulsion Laboratory,[1][51] and two main fragments survived the primary airburst disruption at 29.7 kilometres (18.5 mi); they flared around 24 kilometres (15 mi), with one falling apart at 18.5 kilometres (11.5 mi) and the other remaining luminous down to 13.6 km,[8] with part of the meteoroid continuing on its general trajectory to punch a hole in the frozen Lake Chebarkul, an impact that was fortuitously captured on camera and released in November 2013.[52][53]

This visualization shows the aftermath observations by NASA satellites and computer models projections of the plume and meteor debris trajectory around the atmosphere. The plume rose to an altitude of 35 km and once there, it was rapidly blown around the globe by the polar night jet.[54]

The infrasound waves given off by the explosions were detected by 20 monitoring stations designed to detect nuclear weapons testing run by the Comprehensive Test Ban Treaty Organization (CTBTO) Preparatory Commission, including the distant Antarctic station, some 15,000 kilometres (9,300 mi) away. The blast of the explosion was large enough to generate infrasound returns, after circling the globe, at distances up to about 85,000 kilometres (53,000 mi). Multiple arrivals involving waves that traveled twice around the globe have been clearly identified. The meteor explosion produced the largest infrasounds ever to be recorded by the CTBTO infrasound monitoring system, which began recording in 2001,[55][56][57] so great that they reverberated around the world several times, taking over a day to dissipate.[58] Additional scientific analysis of US military infrasound data was aided by an agreement reached with US authorities to allow its use by civilian scientists, implemented only about a month before the Chelyabinsk meteor event.[17][58]

A full view of the smoke trail with the bulbous section corresponding to a mushroom cloud's cap.

A preliminary estimate of the explosive energy by Astronomer Boris Shustov, director of the Russian Academy of Sciences Institute of Astronomy, was 200 kilotonnes of TNT (840 TJ),[59] another using empirical period-yield scaling relations and the infrasound records, by Peter Brown of the University of Western Ontario gave a value of 460–470 kilotonnes of TNT (1,900–2,000 TJ) and represents a best estimate for the yield of this airburst, however there remains a potential "uncertainty [in the order of] a factor of two in this yield value".[60][61] Brown and his colleagues also went on to publish a paper in November 2013 which stated that the "widely referenced technique of estimating airburst damage does not reproduce the [Chelyabinsk] observations, and that the mathematical relations found in the book The Effects of Nuclear Weapons which are based on the Effects of nuclear weapons—[which is] almost always used with this technique—overestimate blast damage[when applied to meteor airbursts].[62] A similar overestimate of the explosive yield of the Tunguska airburst also exists, as incoming celestial objects have rapid directional motion, the object causes stronger blast wave and thermal radiation pulses at the ground surface than would be predicted by a stationary object exploding, limited to the height at which the blast was initiated-where the object's "momentum is ignored".[63] Thus a meteor airburst of a given energy is "much more damaging than an equivalent [energy] nuclear explosion at the same altitude."[64][65] The seismic wave produced when the primary airburst's blast struck the ground yields a rather uncertain "best estimate" of 430 kilotons(momentum ignored).[65] Corresponding to the seismic wave which registered on seismographs at magnitude 2.7.[42][43][44]

A picture taken of the smoke trail with the double plumes clearly visible either side of the bulbous "mushroom cloud" cap.

Brown also states that the double smoke plume formation, as seen in photographs, is believed to have coincided near the primary airburst section of the dust trail (as also pictured following the Tagish Lake fireball), and it likely indicates where rising air quickly flowed into the center of the trail, essentially in the same manner as a moving 3D version of a mushroom cloud.[66] Photographs of this smoke trail portion, prior to it splitting into two plumes, depict this cigar shaped region glowing incandescently for a few seconds.[67] This region is the area in which the maximum of material ablation occurred, with the double plume persisting for a time and then appearing to rejoin or close up.[68]

Injuries and damage

Shattered windows in the foyer of the Chelyabinsk Drama Theatre

The blast created by the meteor's air burst produced extensive ground damage over an irregular elliptical area a few tens of kilometres across,[69] with the secondary effects of the blast being the main cause of the considerable number of injuries. Russian authorities stated that 1,491 people, including 311 children, sought medical attention in Chelyabinsk Oblast within the first few days.[3] Health officials said 112 people had been hospitalised, with two in serious condition. A 52-year-old woman with a broken spine was flown to Moscow for treatment.[23] However most of the injured were hurt by the secondary blast effects, that is the shattered, falling or blown-in glass.[23][70] The intense light from the meteor, momentarily 30 times brighter than the Sun,[46] also produced injuries, leading to over 180 cases of eye pain, and 70 people subsequently reported temporary flash blindness.[71] Twenty people reported ultraviolet burns similar to sunburn, possibly intensified by the presence of snow on the ground.[71] Vladimir Petrov, when meeting with scientists to assess the damage, reported that he sustained so much sunburn from the meteor that the skin flaked only days later.[72]

A fourth-grade teacher in Chelyabinsk, Yulia Karbysheva, was hailed as a hero after saving 44 children from imploding window glass cuts. Despite not knowing the origin of the intense flash of light, Karbysheva thought it prudent to take precautionary measures by ordering her students to stay away from the room's windows and to perform a duck and cover maneuver. Karbysheva, who remained standing, was seriously lacerated when the blast arrived and window glass severed a tendon in one of her arms; none of her students, whom she ordered to hide under their desks, suffered cuts.[73]

The collapsed roof over the warehouse section of a zinc factory in Chelyabinsk

After the air blast, car alarms went off and mobile phone networks were overloaded with calls.[74] Office buildings in Chelyabinsk were evacuated. Classes for all Chelyabinsk schools were cancelled, mainly due to broken windows.[23] At least 20 children were injured when the windows of a school and kindergarten were blown in at 09:22.[75] Following the event, government officials in Chelyabinsk asked parents to take their children home from schools.[76]

Approximately 600 m2 (6,500 sq ft) of a roof at a zinc factory collapsed during the incident.[77] Residents in Chelyabinsk whose windows were smashed quickly sought to cover the openings with anything available, to protect themselves against temperatures of −15 °C (5 °F).[78] Approximately 100,000 home-owners were affected, according to Chelyabinsk Oblast Governor Mikhail Yurevich.[79] He also said that preserving the water pipes of the city's district heating was the primary goal of the authorities as they scrambled to contain further post-explosion damage.[23]

By 5 March 2013 the number of damaged buildings was tallied at over 7,200, which included some 6,040 apartment blocks, 293 medical facilities, 718 schools and universities, 100 cultural organizations, and 43 sport facilities, of which only about one and a half percent had not yet been repaired.[4] The oblast's governor estimated the damage to buildings at more than 1 billion rubles[80] (approximately US$33 million). Chelyabinsk authorities said that broken windows of apartment homes, but not the glazing of enclosed balconies, would be replaced at the state's expense.[81] One of the buildings damaged in the blast was the Traktor Sport Palace, home arena of Traktor Chelyabinsk of the Kontinental Hockey League (KHL). The arena was closed for inspection, affecting various scheduled events, and possibly the postseason of the KHL.[82]

The irregular elliptical disk shape/"spread-eagled butterfly"[83] ground blast damage area, produced by the airburst,[84] is a phenomenon first noticed upon studying the other larger airburst event-Tunguska.[85]

Reactions

The Chelyabinsk meteor struck without warning, and the spectacle from two extraterrestrial object encounters within hours of each other led one Russian politician to publicly allege that the supposed meteor was actually "the test of a new weapon by the Americans",[86] an allegation quickly dismissed by Russian sources.

Dmitry Medvedev, the Prime Minister of Russia, confirmed a meteor had struck Russia and said it proves the "entire planet" is vulnerable to meteors and a spaceguard system is needed to protect the planet from similar objects in the future.[18][87] Dmitry Rogozin, the deputy prime minister, proposed that there should be an international program that would alert countries to "objects of an extraterrestrial origin",[88] also called potentially hazardous objects.

Colonel General Nikolay Bogdanov, commander of the Central Military District, created task forces that were directed to the probable impact areas to search for fragments of the asteroid and to monitor the situation. Meteorites (fragments) measuring 1 to 5 cm (0.39 to 1.97 in) were found 1 km (0.62 mi) from Chebarkul in the Chelyabinsk region.[89]

On the day of the impact, Bloomberg News reported that the United Nations Office for Outer Space Affairs had suggested the investigation of creating an "Action Team on Near-Earth Objects", a proposed global asteroid warning network system, in face of 2012 DA14's approach.[90][91] As a result of the impact, two scientists in California proposed directed-energy weapon technology development as a possible means to protect Earth from asteroids.[92][93]

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

Frequency

It is estimated that the frequency of airbursts from objects 20 meters across is about once in every 60 years.[94] There have been three incidents in the previous century involving a comparable energy yield or higher: the 1908 Tunguska event, the 1930 Curuçá River event, and in 1963 off the coast of Prince Edward Islands in the Indian Ocean. Two of those were over unpopulated areas, but the 1490 Ch'ing-yang event with an unknown magnitude apparently caused 10000 deaths.[95] While modern researchers are skeptical about the figure, the one over Tunguska could have devastated a highly populous district.[95]

Meteorites

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

Strewnfield map of recovered meteorites (253 documented find locations, status of 18 July 2013).

In the aftermath of the air burst of the body, a large number of small meteorites fell on areas west of Chelyabinsk, generally at terminal velocity, about the speed of a piece of gravel dropped from a skyscraper.[96] Analysis of the meteor showed that all resulted from the main breakup at 34–27 km altitude.[7] Local residents and schoolchildren located and picked up some of the meteorites, many located in snowdrifts, by following a visible hole that had been left in the outer surface of the snow. Speculators were active in the informal market that emerged for meteorite fragments.[96]

In the hours following the visual meteor sighting, a 6-metre (20 ft) wide hole was discovered on Lake Chebarkul's frozen surface. It was not immediately clear whether this was the result of an impact; however, scientists from the Ural Federal University collected 53 samples from around the hole the same day it was discovered. The early specimens recovered were all under 1 centimetre (0.39 in) in size and initial laboratory analysis confirmed their meteoric origin. They are ordinary chondrite meteorites and contain 10% iron. The fall is officially designated as the Chelyabinsk meteorite.[2] The Chelyabinsk meteor was later determined to come from the LL chondrite group.[97] The meteorites were LL5 chondrites having a shock stage of S4, and had a variable appearance between light and dark types. Petrographic changes during the fall allowed estimates that the body was heated between 65 and 135 degrees during its atmospheric entry.[98]

A 112.2 gram (3.96 oz) Chelyabinsk meteorite specimen, one of many found within days of the airburst, this one between the villages of Deputatsky and Emanzhelinsk. The broken fragment displays a thick primary fusion crust with flow lines and a heavily shocked matrix with melt veins and planar fractures. Scale cube is 1 cm (0.39 in).

In June 2013, Russian scientists reported that further investigation by magnetic imaging below the location of the ice hole in Lake Chebarkul had identified a Lua error in Module:Convert at line 272: attempt to index local 'cat' (a nil value).-size meteorite buried in the mud at the bottom of the lake. Before recovery began, the chunk was estimated to weigh roughly 300 kilograms (660 lb).[99]

Following an operation lasting a number of weeks, it was raised from the bottom of the Chebarkul lake on 16 October 2013. With a total mass of 654 kg (1,442 lb) this is the largest found fragment of the Chelyabinsk meteorite. Initially, it tipped and broke the scales used to weigh it, splitting into three pieces.[100][101]

In November 2013, a video from a security camera was released showing the impact of the fragment at the Chebarkul lake.[7][102] This is the first recorded impact of a meteorite on video. From the measured time difference between the shadow generating meteor to the moment of impact, scientists calculated that this meteorite hit the ice at about 225 meters per second, 64 percent of the speed of sound.[7]

Media coverage

External video
Meteor air burst
video icon Two videos, first from a car and from street on YouTube
video icon Extensive dash cam footage from the atmospheric entry onwards on YouTube
video icon Explosion eyewitness on YouTube
video icon Bright light and sound recorded by a stationary surveillance camera on YouTube
video icon Video of meteor explosion that stirred panic in Urals region on YouTube

The Russian government put out a brief statement within an hour of the event. Heavy coverage by the international media had begun by the time the Associated Press put out a brief report with the Russian government's confirmation less than two hours afterwards.[103][104] Less than 15 hours after the meteor impact, videos of the meteor and its aftermath had been viewed millions of times.[105]

The number of injuries caused by the asteroid led the Internet-search giant Google to remove a Google Doodle from their website, created for the predicted pending arrival of another asteroid, 2012 DA14.[106] New York City planetarium director Neil deGrasse Tyson stated the Chelyabinsk meteor was unpredicted because no attempt had been made to find and catalogue every 15-metre near-Earth object.[107] In television media interviews shortly afterwards Tyson also noted the disturbing closeness of the two completely unrelated events.

On 27 March 2013 a broadcast episode of NOVA titled "Meteor Strike" documented the Chelyabinsk meteor, including the large amounts of meteoritic science revealed by the numerous videos of the airburst posted online by ordinary citizens. The NOVA program called the video documentation and the related scientific discoveries of the airburst "unprecedented". The documentary also discussed the much greater tragedy "that could have been" had the asteroid entered the Earth's atmosphere more steeply.[58][108]

Impactor orbital parameters

Preliminary orbital solutions for impacting asteroid
Source Q q a e i Ω ω
AU (°)
Popova, Jenniskens, Emel'yanenko et al.; Science[7] 2.78
±0.20
0.74
±0.02
1.76
±0.16
0.58
±0.02
4.93
±0.48°
326.442
±0.003°
108.3
±3.8°
Lyytinen via Hankey; AMS[109] 2.53 0.80 1.66 0.52 4.05° 326.43° 116.0°
Zuluaga, Ferrin; arXiv[110] 2.64 0.82 1.73 0.51 3.45° 326.70° 120.6°
Borovicka, et al.; IAU[111] 2.33 0.77 1.55 0.50 3.6° 326.41° 109.7°
Zuluaga, Ferrin, Geens; arXiv[112] 1.816 0.716 1.26
± 0.05
0.44
± 0.03
2.984° 326.5°
± 0.3°
95.5°
± 2°
Chodas, Chesley; JPL via Sky and Telescope[113] 2.78 0.75 1.73 0.57 4.2°
Insan[114] 1.5 0.5
Proud; GRL[115] 2.23 0.71 1.47 0.52 4.61° 326.53° 96.58°
de la Fuente Marcos; MNRAS: Letters[116] 2.48 0.76 1.62 0.53 3.97° 326.45° 109.71°
Q = Aphelion, q = Perihelion, a = Semi-major axis, e = Eccentricity, i = Inclination,
Ω = Ascending node longitude, ω = Argument of perihelion

Multiple videos of the Chelyabinsk superbolide, particularly from dashboard cameras and traffic cameras, helped to establish the meteor's provenance as an Apollo asteroid.[111][117] Sophisticated analysis techniques included the subsequent superposition of nighttime starfield views over recorded daytime images, as well as the plotting of the daytime shadow vectors shown in several online videos.[58]

The radiant of the impacting asteroid was located in the constellation Pegasus in the Northern hemisphere.[110] The radiant was close to the Eastern horizon where the Sun was starting to rise.[110]

The asteroid belonged to the Apollo group of near-Earth asteroids,[110][118] and was roughly 40 days past perihelion[109] (closest approach to the Sun) and had aphelion (furthest distance from the Sun) in the asteroid belt.[109][110] Several groups independently derived similar orbits for the object, but with sufficient variance to point to different potential parent bodies of this meteoroid.[115][116][119] The Apollo asteroid 2011 EO40 is one of the candidates proposed for the role of the parent body of the Chelyabinsk superbolide.[116] Other published orbits are similar to the 2-kilometer-diameter asteroid (86039) 1999 NC43 to suggest they had once been part of the same object;[120] however, they may not be able to reproduce the timing of the impact.[116]

Coincidental asteroid approach

Comparison of the former orbit of the Chelyabinsk meteor (larger elliptical blue orbit) and asteroid 2012 DA14 (smaller circular blue orbit), showing that they are dissimilar.

Preliminary calculations rapidly showed the object was unrelated to the long-predicted close approach on 15 February of what was at the time known as asteroid 2012 DA14 (later named 367943 Duende) that flew by Earth 16 hours later at a distance of 27,700 km.[13][121][122] The Sodankylä Geophysical Observatory,[32] Russian sources,[123] the European Space Agency,[124] NASA[13] and the Royal Astronomical Society[125] all indicated the two objects could not have been related because the two asteroids had widely different trajectories.

See also

<templatestyles src="Div col/styles.css"/>

2

Notes

  1. Historical, normally accurate, Chinese records of the 1490 Ch'ing-yang event describe over 10,000 deaths, but have never been confirmed.

References

  1. 1.0 1.1 1.2 1.3 1.4 Lua error in package.lua at line 80: module 'strict' not found.
    NASA's webpage in turn acknowledges credit for its data and visual diagrams to:
    Peter Brown (University of Western Ontario); William Cooke (Marshall Space Flight Center); Paul Chodas, Steve Chesley and Ron Baalke (JPL); Richard Binzel (MIT); and Dan Adamo.
  2. 2.0 2.1 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. 4.0 4.1 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. Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.8 7.9 Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.0 8.1 8.2 8.3 8.4 8.5 8.6 Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. 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. 13.0 13.1 13.2 13.3 13.4 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. 16.0 16.1 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 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. 23.0 23.1 23.2 23.3 23.4 23.5 23.6 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. 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. 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. 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 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. 46.0 46.1 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. 58.0 58.1 58.2 58.3 Lua error in package.lua at line 80: module 'strict' not found.
  59. http://atominfo.ru/newsd/k0520.htm
  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. 65.0 65.1 Lua error in package.lua at line 80: module 'strict' not found.
  66. Lua error in package.lua at line 80: module 'strict' not found.
  67. 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. 71.0 71.1 Lua error in package.lua at line 80: module 'strict' not found.
  72. http://cams.seti.org/index-chelyabinsk.html
  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. Boyarkina, A. P., Demin, D. V., Zotkin, I. T., Fast, W. G. Estimation of the blast wave of the Tunguska meteorite from the forest destruction. – Meteoritika, Vol. 24, 1964, pp. 112–128 (in Russian).
  86. Lua error in package.lua at line 80: module 'strict' not found.
  87. Lua error in package.lua at line 80: module 'strict' not found.
  88. Lua error in package.lua at line 80: module 'strict' not found.
  89. Lua error in package.lua at line 80: module 'strict' not found.
  90. Lua error in package.lua at line 80: module 'strict' not found.
  91. Lua error in package.lua at line 80: module 'strict' not found.
  92. Lua error in package.lua at line 80: module 'strict' not found.
  93. Lua error in package.lua at line 80: module 'strict' not found.
  94. Lua error in package.lua at line 80: module 'strict' not found. (solution using 2600kg/m^3, 17km/s, 45 degrees)
  95. 95.0 95.1 Yau, K., Weissman, P., & Yeomans, D. Meteorite Falls In China And Some Related Human Casualty Events, Meteoritics, Vol. 29, No. 6, pp. 864-871, ISSN 0026-1114, bibliographic code: 1994Metic..29..864Y.
  96. 96.0 96.1 Lua error in package.lua at line 80: module 'strict' not found.
  97. Lua error in package.lua at line 80: module 'strict' not found.
  98. Lua error in package.lua at line 80: module 'strict' not found.
  99. Lua error in package.lua at line 80: module 'strict' not found.
  100. Lua error in package.lua at line 80: module 'strict' not found.
  101. Lua error in package.lua at line 80: module 'strict' not found.
  102. Lua error in package.lua at line 80: module 'strict' not found.
  103. Lua error in package.lua at line 80: module 'strict' not found.
  104. Lua error in package.lua at line 80: module 'strict' not found.
  105. Lua error in package.lua at line 80: module 'strict' not found.
  106. Lua error in package.lua at line 80: module 'strict' not found.
  107. Lua error in package.lua at line 80: module 'strict' not found.
  108. Lua error in package.lua at line 80: module 'strict' not found.
  109. 109.0 109.1 109.2 Lua error in package.lua at line 80: module 'strict' not found.
  110. 110.0 110.1 110.2 110.3 110.4 Lua error in package.lua at line 80: module 'strict' not found.
  111. 111.0 111.1 Lua error in package.lua at line 80: module 'strict' not found. (registration required)
  112. Lua error in package.lua at line 80: module 'strict' not found.
  113. Lua error in package.lua at line 80: module 'strict' not found.
  114. Lua error in package.lua at line 80: module 'strict' not found.
  115. 115.0 115.1 Lua error in package.lua at line 80: module 'strict' not found.
  116. 116.0 116.1 116.2 116.3 Lua error in package.lua at line 80: module 'strict' not found.
  117. Lua error in package.lua at line 80: module 'strict' not found.
  118. Lua error in package.lua at line 80: module 'strict' not found.
  119. Lua error in package.lua at line 80: module 'strict' not found.
  120. Lua error in package.lua at line 80: module 'strict' not found.
  121. Lua error in package.lua at line 80: module 'strict' not found.
  122. Lua error in package.lua at line 80: module 'strict' not found.
  123. Lua error in package.lua at line 80: module 'strict' not found.
  124. Lua error in package.lua at line 80: module 'strict' not found.
  125. Lua error in package.lua at line 80: module 'strict' not found.
Attribution
  • This article contains portions of text translated from the corresponding article of the Russian Wikipedia. A list of contributors can be found there in its history section.

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. (website).
    Also published as Lua error in package.lua at line 80: module 'strict' not found. (print).
  • 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.
  • 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.
  • 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.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
Synopsis: "A calculation based on the number of casualty events in the Chinese meteorite records suggests that the probability of a meteorite striking a human is far greater than previous estimates."

External links

  • 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.
  • 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.
  • Animation of meteor explosion, by "Strip the Cosmos"