Listen to this article

Comet Shoemaker–Levy 9

From Infogalactic: the planetary knowledge core
(Redirected from Comet Shoemaker-Levy 9)
Jump to: navigation, search

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

"Shoemaker–Levy" redirects here. For other Shoemaker–Levy comets, see List of periodic comets.
D/1993 F2 (Shoemaker–Levy)
Hubble Space Telescope
Shoemaker–Levy 9, disrupted comet on a collision course[1]
(total of 21 fragments, taken on May 17, 1994)
Discovery
Discovered by Carolyn Shoemaker
Eugene M. Shoemaker
David Levy
Discovery date March 24, 1993
Orbital characteristics A
Inclination 94.2°

Comet Shoemaker–Levy 9 (formally designated D/1993 F2) was a comet that broke apart and collided with Jupiter in July 1994, providing the first direct observation of an extraterrestrial collision of Solar System objects.[2] This generated a large amount of coverage in the popular media, and the comet was closely observed by astronomers worldwide. The collision provided new information about Jupiter and highlighted its role in reducing space debris in the inner Solar System.

The comet was discovered by astronomers Carolyn and Eugene M. Shoemaker and David Levy.[3] Shoemaker–Levy 9, at the time captured by and orbiting Jupiter, was located on the night of March 24, 1993, in a photograph taken with the 40 cm (16 in) Schmidt telescope at the Palomar Observatory in California. It was the first comet observed to be orbiting a planet, and had probably been captured by the planet around 20 – 30 years earlier.

Calculations showed that its unusual fragmented form was due to a previous closer approach to Jupiter in July 1992. At that time, the orbit of Shoemaker–Levy 9 passed within Jupiter's Roche limit, and Jupiter's tidal forces had acted to pull apart the comet. The comet was later observed as a series of fragments ranging up to 2 km (1.2 mi) in diameter. These fragments collided with Jupiter's southern hemisphere between July 16 and July 22, 1994, at a speed of approximately 60 km/s (37 mi/s) or 216,000 km/h (134,000 mph). The prominent scars from the impacts were more easily visible than the Great Red Spot and persisted for many months.

Discovery

While conducting a program of observations designed to uncover near-Earth objects, the Shoemakers and Levy discovered Comet Shoemaker–Levy 9 on the night of March 24, 1993 in a photograph taken with the 0.4 m (1.3 ft) Schmidt telescope at the Palomar Observatory in California. The comet was thus a serendipitous discovery, but one that quickly overshadowed the results from their main observing program.[4]

Comet Shoemaker–Levy 9 was the ninth periodic comet (a comet whose orbital period is 200 years or less) discovered by the Shoemakers and Levy, hence its name. It was their eleventh comet discovery overall including their discovery of two non-periodic comets, which use a different nomenclature. The discovery was announced in IAU Circular 5725 on March 27, 1993.[3]

The discovery image gave the first hint that comet Shoemaker–Levy 9 was an unusual comet, as it appeared to show multiple nuclei in an elongated region about 50 arcseconds long and 10 arcseconds wide. Brian G. Marsden of the Central Bureau for Astronomical Telegrams noted that the comet lay only about 4 degrees from Jupiter as seen from Earth, and that while this could of course be a line of sight effect, its apparent motion in the sky suggested that it was physically close to the giant planet.[5] Because of this, he suggested that the Shoemakers and David Levy had discovered the fragments of a comet that had been disrupted by Jupiter's gravity.

Jupiter-orbiting comet

Orbital studies of the new comet soon revealed that it was orbiting Jupiter rather than the Sun, unlike all other comets known at the time. Its orbit around Jupiter was very loosely bound, with a period of about 2 years and an apojove (the point in the orbit farthest from the planet) of 0.33 astronomical units (49,000,000 km). Its orbit around the planet was highly eccentric (e = 0.9986).[6]

Tracing back the comet's orbital motion revealed that it had been orbiting Jupiter for some time. It seems most likely that it was captured from a solar orbit in the early 1970s, although the capture may have occurred as early as the mid-1960s.[7] Several other observers found images of the comet in precovery images obtained before March 24, including Kin Endate from a photograph exposed on March 15, S. Otomo on March 17, and a team led by Eleanor Helin from images on March 19.[8] No precovery images dating back to earlier than March 1993 have been found. Before the comet was captured by Jupiter, it was probably a short-period comet with an aphelion just inside Jupiter's orbit, and a perihelion interior to the asteroid belt.[9]

The volume of space within which an object can be said to orbit Jupiter is defined by Jupiter's Hill sphere (also called the Roche sphere). When the comet passed Jupiter in the late 1960s or early 1970s, it happened to be near its aphelion, and found itself slightly within Jupiter's Hill sphere. Jupiter's gravity nudged the comet towards it. Because the comet's motion with respect to Jupiter was very small, it fell almost straight toward Jupiter, which is why it ended up on a Jupiter-centric orbit of very high eccentricity – that is to say, the ellipse was nearly flattened out.[10]

The comet had apparently passed extremely close to Jupiter on July 7, 1992, just over 40,000 km (25,000 mi) above the planet's cloud tops – a smaller distance than Jupiter's radius of 70,000 km (43,000 mi), and well within the orbit of Jupiter's innermost moon Metis and the planet's Roche limit, inside which tidal forces are strong enough to disrupt a body held together only by gravity.[10] Although the comet had approached Jupiter closely before, the July 7 encounter seemed to be by far the closest, and the fragmentation of the comet is thought to have occurred at this time. Each fragment of the comet was denoted by a letter of the alphabet, from "fragment A" through to "fragment W", a practice already established from previously observed broken-up comets.[11]

More exciting for planetary astronomers was that the best orbital calculations suggested that the comet would pass within 45,000 km (28,000 mi) of the center of Jupiter, a distance smaller than the planet's radius, meaning that there was an extremely high probability that SL9 would collide with Jupiter in July 1994. Studies suggested that the train of nuclei would plow into Jupiter's atmosphere over a period of about five days.[10]

Predictions for the collision

The discovery that the comet was likely to collide with Jupiter caused great excitement within the astronomical community and beyond, as astronomers had never before seen two significant Solar System bodies collide. Intense studies of the comet were undertaken, and as its orbit became more accurately established, the possibility of a collision became a certainty. The collision would provide a unique opportunity for scientists to look inside Jupiter's atmosphere, as the collisions were expected to cause eruptions of material from the layers normally hidden beneath the clouds.[6]

Astronomers estimated that the visible fragments of SL9 ranged in size from a few hundred metres to two kilometres across, suggesting that the original comet may have had a nucleus up to 5 km (3.1 mi) across – somewhat larger than Comet Hyakutake, which became very bright when it passed close to the Earth in 1996. One of the great debates in advance of the impact was whether the effects of the impact of such small bodies would be noticeable from Earth, apart from a flash as they disintegrated like giant meteors.[12] The most optimistic prediction was that large, asymmetric ballistic fireballs would rise above the limb of Jupiter and into sunlight to be visible from Earth.[13] Other suggested effects of the impacts were seismic waves travelling across the planet, an increase in stratospheric haze on the planet due to dust from the impacts, and an increase in the mass of the Jovian ring system. However, given that observing such a collision was completely unprecedented, astronomers were cautious with their predictions of what the event might reveal.[6]

Impacts

Jupiter in ultraviolet (about 2.5 hours after R's impact). The black dot near the top is Io transiting Jupiter.[14]
Jupiter in infrared, Shoemaker–Levy 9 collision (left), Io (right)

Anticipation grew as the predicted date for the collisions approached, and astronomers trained terrestrial telescopes on Jupiter. Several space observatories did the same, including the Hubble Space Telescope, the ROSAT X-ray-observing satellite, and significantly the Galileo spacecraft, then on its way to a rendezvous with Jupiter scheduled for 1995. While the impacts took place on the side of Jupiter hidden from Earth, Galileo, then at a distance of 1.6 AU from the planet, was able to see the impacts as they occurred. Jupiter's rapid rotation brought the impact sites into view for terrestrial observers a few minutes after the collisions.[15]

Two other satellites made observations at the time of the impact: the Ulysses spacecraft, primarily designed for solar observations, was pointed towards Jupiter from its location 2.6 AU away, and the distant Voyager 2 probe, some 44 AU from Jupiter and on its way out of the Solar System following its encounter with Neptune in 1989, was programmed to look for radio emission in the 1–390 kHz range.[16]

Hubble Space Telescope images of a fireball from the first impact appearing over the limb of the planet

The first impact occurred at 20:13 UTC on July 16, 1994, when fragment A of the nucleus entered Jupiter's southern hemisphere at a speed of about 60 km/s.[2] Instruments on Galileo detected a fireball which reached a peak temperature of about 24,000 K, compared to the typical Jovian cloudtop temperature of about 130 K, before expanding and cooling rapidly to about 1500 K after 40 s. The plume from the fireball quickly reached a height of over 3,000 km.[17] A few minutes after the impact fireball was detected, Galileo measured renewed heating, probably due to ejected material falling back onto the planet. Earth-based observers detected the fireball rising over the limb of the planet shortly after the initial impact.[18]

Despite published predictions,[13] astronomers had not expected to see the fireballs from the impacts[19] and did not have any idea in advance how visible the other atmospheric effects of the impacts would be from Earth. Observers soon saw a huge dark spot after the first impact. The spot was visible even in very small telescopes, and was about 6,000 km (3,700 mi) (one Earth radius) across. This and subsequent dark spots were thought to have been caused by debris from the impacts, and were markedly asymmetric, forming crescent shapes in front of the direction of impact.[20]

Over the next 6 days, 21 distinct impacts were observed, with the largest coming on July 18 at 07:33 UTC when fragment G struck Jupiter. This impact created a giant dark spot over 12,000 km across, and was estimated to have released an energy equivalent to 6,000,000 megatons of TNT (600 times the world's nuclear arsenal).[21] Two impacts 12 hours apart on July 19 created impact marks of similar size to that caused by fragment G, and impacts continued until July 22, when fragment W struck the planet.[22]

Observations and discoveries

Chemical studies

Brown spots mark impact sites on Jupiter's southern hemisphere.

Observers hoped that the impacts would give them a first glimpse of Jupiter beneath the cloud tops, as lower material was exposed by the comet fragments punching through the upper atmosphere. Spectroscopic studies revealed absorption lines in the Jovian spectrum due to diatomic sulfur (S2) and carbon disulfide (CS2), the first detection of either in Jupiter, and only the second detection of S2 in any astronomical object. Other molecules detected included ammonia (NH3) and hydrogen sulfide (H2S). The amount of sulfur implied by the quantities of these compounds was much greater than the amount that would be expected in a small cometary nucleus, showing that material from within Jupiter was being revealed. Oxygen-bearing molecules such as sulfur dioxide were not detected, to the surprise of astronomers.[23]

As well as these molecules, emission from heavy atoms such as iron, magnesium and silicon was detected, with abundances consistent with what would be found in a cometary nucleus. While substantial water was detected spectroscopically, it was not as much as predicted beforehand, meaning that either the water layer thought to exist below the clouds was thinner than predicted, or that the cometary fragments did not penetrate deeply enough.[24] The relatively low levels of water were later confirmed by Galileo's atmospheric probe, which explored Jupiter's atmosphere directly.

Waves

As predicted beforehand, the collisions generated enormous waves which swept across the planet at speeds of 450 m/s (1,476 ft/s) and were observed for over two hours after the largest impacts. The waves were thought to be travelling within a stable layer acting as a waveguide, and some scientists believed the stable layer must lie within the hypothesised tropospheric water cloud. However, other evidence seemed to indicate that the cometary fragments had not reached the water layer, and the waves were instead propagating within the stratosphere.[25]

Other observations

A sequence of Galileo images, taken several seconds apart, showing the appearance of the fireball of fragment W on the dark side of Jupiter

Radio observations revealed a sharp increase in continuum emission at a wavelength of 21 cm after the largest impacts, which peaked at 120% of the normal emission from the planet. This was thought to be due to synchrotron radiation, caused by the injection of relativistic electrons – electrons with velocities near the speed of light – into the Jovian magnetosphere by the impacts.[26]

About an hour after fragment K entered Jupiter, observers recorded auroral emission near the impact region, as well as at the antipode of the impact site with respect to Jupiter's strong magnetic field. The cause of these emissions was difficult to establish due to a lack of knowledge of Jupiter's internal magnetic field and of the geometry of the impact sites. One possible explanation was that upwardly accelerating shock waves from the impact accelerated charged particles enough to cause auroral emission, a phenomenon more typically associated with fast-moving solar wind particles striking a planetary atmosphere near a magnetic pole.[27]

Some astronomers had suggested that the impacts might have a noticeable effect on the Io torus, a torus of high-energy particles connecting Jupiter with the highly volcanic moon Io. High resolution spectroscopic studies found that variations in the ion density, rotational velocity, and temperatures at the time of impact and afterwards were within the normal limits.[28]

Post-impact analysis

A reddish, asymmetric ejecta pattern

Several models were devised to compute the density and size of Shoemaker-Levy 9. Its average density was calculated to be about 0.5 g cm-3; the breakup of a much less dense comet would not have resembled the observed string of objects. The size of the parent comet was calculated to be about 1.8 km in diameter.[29][30] These predictions were among the few that were actually confirmed by subsequent observation.[31]

One of the surprises of the impacts was the small amount of water revealed compared to prior predictions.[32] Before the impact, models of Jupiter's atmosphere had indicated that the break-up of the largest fragments would occur at atmospheric pressures of anywhere from 30 kilopascals to a few tens of megapascals (from 0.3 to a few hundred bar),[24] with some predictions that the comet would penetrate a layer of water and create a bluish shroud over that region of Jupiter.[12]

Astronomers did not observe large amounts of water following the collisions, and later impact studies found that fragmentation and destruction of the cometary fragments in an 'airburst' probably occurred at much higher altitudes than previously expected, with even the largest fragments being destroyed when the pressure reached 250 kPa (36 psi), well above the expected depth of the water layer. The smaller fragments were probably destroyed before they even reached the cloud layer.[24]

Longer-term effects

The visible scars from the impacts could be seen on Jupiter for many months. They were extremely prominent, and observers described them as more easily visible even than the Great Red Spot. A search of historical observations revealed that the spots were probably the most prominent transient features ever seen on the planet, and that while the Great Red Spot is notable for its striking color, no spots of the size and darkness of those caused by the SL9 impacts have ever been recorded before.[33]

Spectroscopic observers found that ammonia and carbon disulfide persisted in the atmosphere for at least fourteen months after the collisions, with a considerable amount of ammonia being present in the stratosphere as opposed to its normal location in the troposphere.[34]

Counterintuitively, the atmospheric temperature dropped to normal levels much more quickly at the larger impact sites than at the smaller sites: at the larger impact sites, temperatures were elevated over a region 15,000 to 20,000 km (9,300 to 12,400 mi) wide, but dropped back to normal levels within a week of the impact. At smaller sites, temperatures 10 K higher than the surroundings persisted for almost two weeks.[35] Global stratospheric temperatures rose immediately after the impacts, then fell to below pre-impact temperatures 2–3 weeks afterwards, before rising slowly to normal temperatures.[36]

Frequency of impacts

A chain of craters on Ganymede, probably caused by a similar impact event. The picture covers an area approximately 190 km (120 mi) across.

SL9 is not unique in having orbited Jupiter for a time; five comets, (including 82P/Gehrels, 147P/Kushida–Muramatsu, and 111P/Helin–Roman–Crockett) are known to have been temporarily captured by the planet.[37][38] Cometary orbits around Jupiter are unstable, as they will be highly elliptical and likely to be strongly perturbed by the Sun's gravity at apojove (the furthest point on the orbit from the planet).

By far the most massive planet in the Solar System, Jupiter can capture objects relatively frequently, but the size of SL9 makes it a rarity: one post-impact study estimated that comets 0.3 km in diameter impact the planet once in approximately 500 years and those 1.6 km (0.99 mi) in diameter do so just once in every 6,000 years.[39]

There is very strong evidence that comets have previously been fragmented and collided with Jupiter and its satellites. During the Voyager missions to the planet, planetary scientists identified 13 crater chains on Callisto and three on Ganymede, the origin of which was initially a mystery.[40] Crater chains seen on the Moon often radiate from large craters, and are thought to be caused by secondary impacts of the original ejecta, but the chains on the Jovian moons did not lead back to a larger crater. The impact of SL9 strongly implied that the chains were due to trains of disrupted cometary fragments crashing into the satellites.[41]

Impact of July 19, 2009

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

Main article: 2009 Jupiter impact event

On July 19, 2009, a new black spot about the size of the Pacific Ocean appeared in Jupiter's southern hemisphere. Thermal infrared measurements showed the impact site was warm and spectroscopic analysis detected the production of excess hot ammonia and silica-rich dust in the upper regions of Jupiter's atmosphere. Scientists have concluded that another impact event had occurred, but this time a more compact and strong object, probably a small undiscovered asteroid, was the cause.[42]

Jupiter as a "cosmic vacuum cleaner"

The impact of SL9 highlighted Jupiter's role as a "cosmic vacuum cleaner" (or in deference to the ancients' planetary correspondences to the major organs in the human body, a "cosmic liver") for the inner Solar System. The planet's strong gravitational influence leads to many small comets and asteroids colliding with the planet, and the rate of cometary impacts on Jupiter is thought to be between two thousand and eight thousand times higher than the rate on Earth.[43] If Jupiter were not present, the probability of asteroid impacts with the Solar System's inner planets would be much greater.

The extinction of the dinosaurs at the end of the Cretaceous period is generally believed to have been caused by the Cretaceous–Paleogene impact event which created the Chicxulub crater,[44] demonstrating that impacts are a serious threat to life on Earth. Astronomers have speculated that without Jupiter to mop up potential impactors, extinction events might have been more frequent on Earth, and complex life might not have been able to develop.[45] This is part of the argument used in the Rare Earth hypothesis.

In 2009, it was shown that the presence of a smaller planet at Jupiter's position in the Solar System might increase the impact rate of comets on the Earth significantly. A planet of Jupiter's mass still seems to provide increased protection against asteroids, but the total effect on all orbital bodies within the Solar System is unclear.[46][47]

See also

References

Notes

  1. ↑ SPACE.com, Elizabeth Howell, Shoemaker–Levy 9: Comet's Impact Left Its Mark on Jupiter, 19 February 2013
  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. ↑ 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. ↑ 6.0 6.1 6.2 Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ 10.0 10.1 10.2 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. ↑ 12.0 12.1 Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ 13.0 13.1 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. ↑ 24.0 24.1 24.2 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. ↑ Mystery impact leaves Earth-sized mark on Jupiter
  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. ↑ Jupiter – friend or foe? II: the Centaurs Jupiter http://arxiv.org/pdf/0903.3305
  47. ↑ Lua error in package.lua at line 80: module 'strict' not found.

Bibliography

  • Chodas P. W., and Yeomans D. K. (1996), The Orbital Motion and Impact Circumstances of Comet Shoemaker–Levy 9, in The Collision of Comet Shoemaker–Levy 9 and Jupiter, edited by K. S. Noll, P. D. Feldman, and H. A. Weaver, Cambridge University Press, pp. 1–30
  • Chodas P. W. (2002), Communication of Orbital Elements to Selden E. Ball, Jr. Accessed February 21, 2006

External links

Retrieved from "https://infogalactic.com/w/index.php?title=Comet_Shoemaker–Levy_9&oldid=4163"