Английская Википедия:2009 satellite collision

Материал из Онлайн справочника
Перейти к навигацииПерейти к поиску

Шаблон:Short description Шаблон:Use mdy dates Шаблон:Multiple image On February 10, 2009, two communications satellites — the active commercial Iridium 33 and the derelict Russian military Kosmos 2251 —accidentally collided at a speed of Шаблон:Convert and an altitude of Шаблон:Convert above the Taymyr Peninsula in Siberia.[1][2][3][4][5][6] It was the first time a hypervelocity collision occurred between two satellites; previous incidents had involved a satellite and a piece of space debris.[7]

Spacecraft

Шаблон:Main Kosmos 2251 was a Шаблон:Convert Russian Strela military communications satellite owned by the Russian Space Forces.[8] Kosmos 2251 was launched on a Russian Cosmos-3M carrier rocket on June 16, 1993.[2] Notably, this satellite had been deactivated prior to the collision, and remained in orbit as space debris.

The other spacecraft, IridiumШаблон:Nbsp33, was a Шаблон:Convert USA-built commercial satellite that was part of the Iridium constellation for satellite phones.[2] It was launched on September 14, 1997, atop a Russian Proton rocket.

Collision

Файл:Collision iridium33 kosmos2251.jpg
Collision diagram

The collision occurred at 16:56 UTC and destroyed both the Iridium 33 and Kosmos-2251. The Iridium satellite was operational at the time of the collision. Kosmos-2251 had gone out of service in 1995.[9] It had no propulsion system,[10] and was no longer actively controlled.[11][12]

Fallout

Файл:Iridium33 flashes.jpg
Flashes created by the tumbling main body of the Iridium 33 wreckage.
Файл:SpaceDebrisHistogram.png
The collision resulted in significant debris in low Earth orbit. (2011)

NASA, the U.S. space agency, initially estimated ten days after the collision that the satellite space incident had created at least 1,000 pieces of debris larger than Шаблон:Cvt, in addition to many smaller ones.[13] By July 2011, the U.S. Space Surveillance Network had catalogued over 2000 large debris fragments from the collision.[14] NASA determined the risk to the International Space Station, which orbits about Шаблон:Convert below the collision course, to be low,[8][15] as was any threat to the shuttle launch (STS-119) then planned for late February 2009.[8] However, Chinese scientists have said that the debris does pose a threat to Chinese satellites in Sun-synchronous orbits,[16] and the ISS did have to perform an avoidance maneuver due to collision debris in March 2011.[14]

By December 2011, many pieces of the debris were in an observable orbital decay towards Earth, and were expected to burn up in the atmosphere within one to two years. In 2016, Space News listed the collision as the second biggest fragmentation event in history, with Kosmos-2251 and Iridium 33 producing respectively 1,668 and 628 pieces of catalogued debris, of which 1,141 and 364 pieces of tracked debris remained in orbit as of January 2016.[17] Fourteen years after the collision the US Space Surveillance Catalog listed 1,014[18] and 290[19] debris still in orbit respectively.

A small piece of Kosmos-2251 satellite debris safely passed by the International Space Station at 2:38 a.m. EDT, Saturday, March 24, 2012, at a distance of approximately Шаблон:Cvt. As a precaution, ISS management had the six crew members on board the orbiting complex take refuge inside the two docked Soyuz rendezvous spacecraft until the debris had passed.[20]

A number of reports of phenomena in the US states of Texas, Kentucky, and New Mexico were attributed to debris from the collision in the days immediately following the first reports of the incident in 2009,[21] although NASA and the United States Strategic Command, which tracks satellites and orbital debris, did not announce any reentries of debris at the time[22] and reported that these phenomena were unrelated to the collision.[23] On February 13, 2009, witnesses in Kentucky heard sonic booms.[24] The National Weather Service issued an information statement alerting residents of sonic booms due to the falling satellite debris.[25] The Federal Aviation Administration also released a notice warning to pilots of the re-entering debris.[26] Some reports include details that point to these phenomena being caused by a meteoroid shower.[22] A very bright meteor over Texas on February 15, 2009, was mistaken for reentering debris by some witnesses.[27]

Other

Events where two satellites approach within several kilometers of each other occur numerous times each day. Sorting through the large number of potential collisions to identify those that are high risk presents a challenge. Precise, up-to-date information regarding current satellite positions is difficult to obtain. Calculations made by CelesTrak had expected these two satellites to miss by Шаблон:Convert.[28]

Planning an avoidance maneuver with due consideration of the risk, the fuel consumption required for the maneuver, and its effects on the satellite's normal functioning can also be challenging. John Campbell of Iridium spoke at a June 2007 forum discussing these tradeoffs and the difficulty of handling all the notifications they were getting regarding close approaches, which numbered 400 per week (for approaches within Шаблон:Convert) for the entire Iridium constellation. He estimated the risk of collision per conjunction as one in 50Шаблон:Nbspmillion.[29]

This collision and numerous near-misses have renewed callsШаблон:By whom for mandatory disposal of defunct satellites (typically by deorbiting them, or at minimum, sending them to a graveyard orbit), but no such international law exists as of 2023. Nevertheless, some countries have adopted such a law domestically, such as France in December 2010.[30] The United States Federal Communications Commission (FCC) requires all geostationary satellites launched after March 18, 2002 to commit to moving to a graveyard orbit at the end of their operational life.[31]

See also

References

Шаблон:Reflist

External links

Шаблон:Wikinews

Шаблон:Authority control