2I/Borisov: Difference between revisions

From testwiki
Jump to navigation Jump to search
imported>KyloRen2017
 
(No difference)

Latest revision as of 15:18, 2 February 2025

Template:Short description Template:Redirect Template:Use dmy dates Template:Infobox comet

2I/Borisov, originally designated C/2019 Q4 (Borisov),Template:R is the first observed rogue comet and the second observed interstellar interloper after ʻOumuamua.Template:R It was discovered by the Crimean amateur astronomer and telescope maker Gennadiy Borisov on 29 August 2019 UTC (30 August local time).[1][2]

2I/Borisov has a heliocentric orbital eccentricity of 3.36 and is not bound to the Sun.[3] The comet passed through the ecliptic of the Solar System at the end of October 2019, and made its closest approach to the Sun at just over Template:Val on 8 December 2019.Template:R[4] The comet passed closest to Earth on 28 December 2019.[5] In November 2019, astronomers from Yale University said that the comet's tail was 14 times the size of Earth, and stated, "It's humbling to realize how small Earth is next to this visitor from another solar system."[6]

Nomenclature

The comet is formally called "2I/Borisov" by the International Astronomical Union (IAU), with "2I" or "2I/2019 Q4" being its designation and "Borisov" being its name, but is sometimes referred to as "Comet Borisov", especially in the popular press.Template:Efn As the second observed interstellar interloper after 1I/ʻOumuamua, it was given the "2I" designation, where "I" stands for interstellar.[7][8] The name Borisov follows the tradition of naming comets after their discoverers. Before final designation as 2I/Borisov, the object was referred to by other names:

  • Early orbit solutions suggested that the comet could be a near-Earth object and was thus listed on IAU's Minor Planet Center's (MPC) Near-Earth Object Confirmation Page (NEOCP) as gb00234.[9]
  • Further refinements after thirteen days of observation made clear the object was a hyperbolic comet, and it was given the designation C/2019 Q4 (Borisov) by the Minor Planet Center on 11 September 2019.[10] A number of other astronomers including Davide Farnocchia, Bill Gray, and David Tholen concluded that the comet was interstellar.[10]
  • On 24 September 2019 the IAU announced that the Working Group for Small Body Nomenclature kept the name Borisov giving the comet the interstellar designation of 2I/Borisov, formally announcing the comet was indeed interstellar.[7][8]

Characteristics

In this observation, the NASA/ESA Hubble Space Telescope revisited the comet shortly after its closest approach to the Sun in December 2019.

Template:External media Unlike ʻOumuamua, which had an asteroidal appearance, 2I/Borisov's nucleus was surrounded by a coma, a cloud of dust and gas.[11]

Comet 2I/Borisov and a distant galaxy (2MASX J10500165-0152029[12]) in November 2019.[13]

Size and shape

Early estimates of nucleus 2I/Borisov diameter have ranged from Template:Val.[14][15] 2I/Borisov has, unlike Solar System comets, noticeably shrunk during Solar System flyby, losing at least 0.4% of its mass before perihelion.[16] Also, the amplitude of non-gravitational acceleration place an upper limit of 0.4 km on nucleus size, consistent with a previous Hubble Space Telescope upper limit of 0.5 km.[17] The comet did not come much closer to Earth than 300 million km, which prevents using radar to directly determine its size and shape. This could be done using the occultation of a star by 2I/Borisov but an occultation would be difficult to predict, requiring a precise determination of its orbit, and the detection would necessitate a network of small telescopes.[18]

Rotation

A study using observations from Hubble could not find a variation in the light curve. According to this study the rotational period must be larger than 10 hours.[19] A study with CSA's NEOSSat found a period of 13.2 ± 0.2 days, which is unlikely to be the nuclear spin.[20] Monte Carlo simulations based on the available orbit determinations suggest that the equatorial obliquity of 2I/Borisov could be about 59 degrees or 90 degrees, the latter is favored for the latest orbit determination.[21]

Chemical makeup and nucleus structure

David Jewitt and Jane Luu estimate from the size of its coma the comet is producing 2 kg/s of dust and is losing 60 kg/s of water. They extrapolate that it became active in June 2019 when it was between 4 and 5 Template:Smallcaps from the Sun.[17] A search of image archives found precovery observations of 2I/Borisov as early as 13 December 2018, but not on 21 November 2018, indicating it became active between these dates.[22]

2I/Borisov's composition appears uncommon yet not unseen in Solar System comets, being relatively depleted in water and diatomic carbon (C2), but enriched in carbon monoxide and amines (R-NH2).[23] The molar ratio of carbon monoxide to water in 2I/Borisov tail is 35–105%, resembling the unusual blue-tailed comet C/2016 R2 (PANSTARRS) in contrast to the average ratio of 4% for solar system comets.[24]

The 2I/Borisov has also produced a minor amount of neutral nickel emission attributed to an unknown volatile compound of nickel.[25] The nickel to iron abundance ratio is similar to Solar System comets.[26]

Trajectory

Trajectory across sky in cylindrical coordinates, with 30 August 2019 discovery position along with precovery positions marked back to 13 December 2018 which help narrow down the incoming trajectory
Interstellar velocity inbound (v)Template:Efn
Object Velocity
1I/2017 U1 (ʻOumuamua) Template:Cvt[27]
2I/2019 Q4 (Borisov) Template:Cvt[28]

As seen from Earth, the comet was in the northern sky from September until mid-November. It crossed the ecliptic plane on 26 October near the star Regulus,[29] and the celestial equator on 13 November 2019, entering the southern sky. On 8 December 2019, the comet reached perihelion (closest approach to the Sun)[30] and was near the inner edge of the asteroid belt. In late December, it made its closest approach to Earth,[1][4] 1.9 Template:Smallcaps, and had a solar elongation of about 80°.[31] Due to its 44° orbital inclination, 2I/Borisov did not make any notable close approaches to the planets.[30] 2I/Borisov entered the Solar System from the direction of Cassiopeia near the border with Perseus. This direction indicates that it originates from the galactic plane, rather than from the galactic halo.[28][32] It will leave the Solar System in the direction of Telescopium.[28][32] In interstellar space, 2I/Borisov takes roughly Template:Val years to travel a light-year relative to the Sun.Template:Efn

2I/Borisov's trajectory is extremely hyperbolic, having an orbital eccentricity of 3.36.[30][33] This is much higher than the 300+ known weakly hyperbolic comets, with heliocentric eccentricities just over 1, and even ʻOumuamua with an eccentricity of 1.2.[34]Template:Efn 2I/Borisov also has a hyperbolic excess velocity (v) of Template:Val, much higher than what could be explained by perturbations, which could produce velocities when approaching an infinite distance from the Sun of less than a few km/s.[35] These two parameters are important indicators of 2I/Borisov's interstellar origin.[28][36] For comparison, the Voyager 1 spacecraft, which is leaving the Solar System, is traveling at Template:Cvt.[37] 2I/Borisov has a much larger eccentricity than ʻOumuamua due to its higher excess velocity and its significantly higher perihelion distance. At this larger distance, the Sun's gravity is less able to alter its path as it passes through the Solar System.[28]

Template:Multiple image

Observation

Discovery

The comet was discovered on 30 August 2019 by amateur astronomer Gennadiy Borisov at his personal observatory MARGO in Nauchnyy, Crimea, using a 0.65 meter telescope he designed and built himself.[38] The discovery has been compared to the discovery of Pluto by Clyde Tombaugh.[39] Tombaugh was also an amateur astronomer who was building his own telescopes, although he discovered Pluto using Lowell Observatory's astrograph. At discovery, it was inbound Template:Val from the Sun, Template:Val from Earth, and had a solar elongation of 38°.[40] Borisov described his discovery thus:[41] Template:Clear

JPL Scout eccentricity ranges[42]
# of
observations
Observation
arc (hours)
Eccentricity
range
81 225 0.9–1.6
99 272 2.0–4.2
127 289 2.8–4.7
142 298 2.8–4.5
151 302 2.9–4.5

Template:Blockquote

2I/Borisov's interstellar origin required a couple of weeks to confirm. Early orbital solutions based on initial observations included the possibility that the comet could be a near-Earth object 1.4 AU from the Sun in an elliptical orbit with an orbital period of less than 1 year.[9] Later using 151 observations over 12 days, NASA Jet Propulsion Laboratory's Scout gave an eccentricity range of 2.9–4.5 .[43] But with an observation arc of only 12 days, there was still some doubt that it was interstellar because the observations were at a low solar elongation, which could introduce biases in the data such as differential refraction. Using large non-gravitational forces on the highly eccentric orbit, a solution could be generated with an eccentricity of about 1, an Earth minimum orbit intersection distance (MOID) of Template:Convert, and a perihelion at 0.90 AU around 30 December 2019.[44] However, based on available observations, the orbit could only be parabolic if non-gravitational forces (thrust due to outgassing) affected its orbit more than any previous comets.[45] Eventually with more observations the orbit converged to the hyperbolic solution that indicated an interstellar origin and non-gravitational forces could not explain the motion.[10]

Observation

File:Video-NASA-InterstellarComet-2IBorisov-HubbleST-20191016.webm The last observations were in July 2020, seven months after perihelion.[30] Observation of 2I/Borisov was aided by the fact that the comet was detected while inbound towards the Solar System. ʻOumuamua had been discovered as it was leaving the system, and thus could only be observed for 80 days before it was out of range. Because of its closest approach occurring near traditional year-end holidays, and the capability to have extended observations, some astronomers have called 2I/Borisov a "Christmas comet".[3][46] Observations using the Hubble Space Telescope began on 12 October, when the comet moved far enough from the Sun to be safely observed by the telescope.[47] Hubble is less affected by the confounding effects of the coma than ground-based telescopes, which will allow it to study the rotational light curve of 2I/Borisov's nucleus. This should facilitate an estimate of its size and shape.Template:Update inline

Comet chemistry

A preliminary (low-resolution) visible spectrum of 2I/Borisov was similar to typical Oort Cloud comets.[48][49] Its color indexes also resemble the Solar System's long period comets.[17] Emissions at Template:Val indicated the presence of cyanide (formula CN), which is typically the first detected in Solar System comets including comet Halley.[50] This was the first detection of gas emissions from an interstellar object.[51] The non-detection of diatomic carbon had also been reported in October 2019, with the ratio C2 to CN being less than either 0.095[52] or 0.3 .[53] The diatomic carbon was positively detected in November 2019, with measured C2 to CN ratio of Template:Val .[54] This resembles a carbon-chain depleted group of comets, which are either Jupiter family comets[52] or rare blue-colored carbon monoxide comets exemplified by C/2016 R2.[55] By the end of November 2019, C2 production had dramatically increased, and C2 to CN ratio reached 0.61, along with appearance of bright amine (NH2) bands.[56] Atomic oxygen has also been detected, from this observers estimated an outgassing of water at a rate similar to Solar System comets.[57][58] Initially, neither water nor OH lines were directly detected[59] in September 2019. First unambiguous detection of OH lines was done 1 November 2019, and OH production peaked in early December 2019.[60]

Suspected nucleus fragmentation

The comet did come within about 2 AU of the Sun, a distance at which many small comets have been found to disintegrate. The probability that a comet disintegrates strongly depends on the size of its nucleus; Guzik et al. estimated a probability of 10% that this would happen to 2I/Borisov.[5] Jewitt and Luu compared 2I/Borisov to C/2019 J2 (Palomar), another comet of similar size that disintegrated in May 2019 at a distance of 1.9 AU from the Sun.[61][17] In the event that the nucleus disintegrates, as is sometimes seen with small comets, Hubble can be used to study the evolution of the disintegration process.[62][17]

The severe outburst in February–March 2020, led to suspected "ongoing nucleus fragmentation" from the comet by 12 March.[63] Indeed, images from the Hubble Space Telescope taken on 30 March 2020 show a non-stellar core indicating that Comet 2I/Borisov has ejected sunward a large fragment.[64][65][66] The ejection is estimated to have begun around 7 March,[67] and may have occurred during one of the outbursts that occurred near that time.[68] The ejected fragment appeared to have vanished by 6 April 2020.[69]

A followup study, reported on 6 April 2020, observed only a single object, and noted that the fragment component had now disappeared.[69][70] Later analysis of the event showed the ejected dust and fragments have a combined mass of about 0.1% of total mass of nucleus, making the event a large outburst rather than fragmentation.[71]

Exploration

The high hyperbolic excess velocity of 2I/Borisov of Template:Val makes it hard for a spacecraft to reach the comet with existing technology: according to a team of the Initiative for Interstellar Studies, a 202 kg (445 lb) spacecraft could theoretically have been sent in July 2018 to intercept 2I/Borisov using a Falcon Heavy-class launcher, or 765 kg (1687 lb) on a Space Launch System (SLS)-class booster, but only if the object had been discovered much earlier than it was to meet the optimal launch date. Launches after the actual discovery date would eliminate the possibility to use Falcon Heavy-class rockets, requiring Oberth maneuvres near Jupiter and near the Sun and a larger launch vehicle. Even an SLS-class launcher would only have been able to deliver a Template:Convert payload (such as a CubeSat) into a trajectory that would intercept 2I/Borisov in 2045 at a relative speed of Template:Val.[72] According to congressional testimony, NASA may need at least five years of preparation to launch such an intercepting mission.[73]

See also

Notes

Template:Notelist

References

Template:Reflist

Template:Commons category

Template:2019 in space Template:Comets Template:Portal bar Template:Authority control

  1. 1.0 1.1 Template:Cite news
  2. Template:Cite news
  3. 3.0 3.1 Template:Cite news
  4. 4.0 4.1 Template:Cite news
  5. 5.0 5.1 Cite error: Invalid <ref> tag; no text was provided for refs named Guzik2019
  6. Template:Cite news
  7. 7.0 7.1 Cite error: Invalid <ref> tag; no text was provided for refs named Christensen2019
  8. 8.0 8.1 Cite error: Invalid <ref> tag; no text was provided for refs named MPEC2019-S72
  9. 9.0 9.1 Cite error: Invalid <ref> tag; no text was provided for refs named Gray-NEO
  10. 10.0 10.1 10.2 Cite error: Invalid <ref> tag; no text was provided for refs named MPECK19RA6
  11. Cite error: Invalid <ref> tag; no text was provided for refs named Greskno2019
  12. Template:Cite web
  13. Template:Cite web
  14. Cite error: Invalid <ref> tag; no text was provided for refs named NASA-Initial
  15. Template:Cite journal
  16. Template:Cite arXiv
  17. 17.0 17.1 17.2 17.3 17.4 Cite error: Invalid <ref> tag; no text was provided for refs named Jewitt2019b
  18. Cite error: Invalid <ref> tag; no text was provided for refs named Bamberger2019
  19. Template:Cite journal
  20. Template:Cite journal
  21. Template:Cite journal
  22. Template:Cite journal
  23. Template:Cite journal
  24. Template:Cite journal
  25. Template:Citation
  26. Optim et al. 2021, Manfroid et al 2021
  27. Cite error: Invalid <ref> tag; no text was provided for refs named ProjectPluto
  28. 28.0 28.1 28.2 28.3 28.4 Cite error: Invalid <ref> tag; no text was provided for refs named Gray-FAQ
  29. Template:Cite web
  30. 30.0 30.1 30.2 30.3 Cite error: Invalid <ref> tag; no text was provided for refs named JPL-Data
  31. Cite error: Invalid <ref> tag; no text was provided for refs named Gray234
  32. 32.0 32.1 Cite error: Invalid <ref> tag; no text was provided for refs named deLeón2020
  33. Cite error: Invalid <ref> tag; no text was provided for refs named MPC-DB
  34. Cite error: Invalid <ref> tag; no text was provided for refs named JPL-Hyperbolic
  35. Cite error: Invalid <ref> tag; no text was provided for refs named Siegel2017
  36. Cite error: Invalid <ref> tag; no text was provided for refs named Atel13100
  37. Cite error: Invalid <ref> tag; no text was provided for refs named Voyager
  38. Cite error: Invalid <ref> tag; no text was provided for refs named S&T2019
  39. Cite error: Invalid <ref> tag; no text was provided for refs named Fontanka
  40. Cite error: Invalid <ref> tag; no text was provided for refs named Gray-prec
  41. Cite error: Invalid <ref> tag; no text was provided for refs named RIA
  42. Cite error: Invalid <ref> tag; no text was provided for refs named archive-is
  43. Cite error: Invalid <ref> tag; no text was provided for refs named Scout
  44. Cite error: Invalid <ref> tag; no text was provided for refs named Gray35237
  45. Cite error: Invalid <ref> tag; no text was provided for refs named Gray234c
  46. Cite error: Invalid <ref> tag; no text was provided for refs named NYT-20191001
  47. Cite error: Invalid <ref> tag; no text was provided for refs named Hubble100719
  48. Cite error: Invalid <ref> tag; no text was provided for refs named IAC
  49. Cite error: Invalid <ref> tag; no text was provided for refs named deLeón2019
  50. Cite error: Invalid <ref> tag; no text was provided for refs named Fitzsimmons2019
  51. Cite error: Invalid <ref> tag; no text was provided for refs named CBAT4670
  52. 52.0 52.1 Cite error: Invalid <ref> tag; no text was provided for refs named Kareta2019
  53. Cite error: Invalid <ref> tag; no text was provided for refs named Opitom2019
  54. Template:Cite journal
  55. Template:Cite journal
  56. Template:Cite arXiv
  57. Template:Cite news
  58. Template:Cite journal
  59. Template:Cite arXiv
  60. Template:Cite journal
  61. Cite error: Invalid <ref> tag; no text was provided for refs named Jewitt2019a
  62. Cite error: Invalid <ref> tag; no text was provided for refs named STScI-16009
  63. Template:Cite news
  64. Template:Cite news
  65. Template:Cite news
  66. Template:Cite news
  67. Template:Cite news
  68. Template:Cite news
  69. 69.0 69.1 Template:Cite news
  70. Template:Cite news
  71. Template:Cite journal
  72. Cite error: Invalid <ref> tag; no text was provided for refs named Hibberd2019
  73. Cite error: Invalid <ref> tag; no text was provided for refs named US-Congress-20130410