On February 10, 2009, twocommunications satellites—the active commercialIridium 33 and thederelict Russian militaryKosmos 2251—(Cosmos) accidentally collided at a speed of 11.7 km/s (26,000 mph) and an altitude of 789 kilometres (490 mi) above theTaymyr Peninsula inSiberia.[1][2][3][4][5][6] It was the first time ahypervelocitycollision occurred between two satellites; previous incidents had involved a satellite and a piece ofspace debris.[7]
Kosmos 2251 was a 950-kilogram (2,100 lb) RussianStrela militarycommunications satellite owned by theRussian Space Forces.[8] Kosmos 2251 was launched on a RussianCosmos-3M carrier rocket on June 16, 1993.[2] This satellite had been deactivated prior to the collision, and remained inorbit asspace debris.
The other spacecraft, Iridium 33, was a 560-kilogram (1,200 lb) U.S.-built commercial satellite that was part of theIridium constellation for satellite phones.[2] It was launched on September 14, 1997, atop a RussianProton rocket.
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 584 m (1,916 ft).[9]
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 discussingthese tradeoffs and the difficulty of handling all the notifications they were getting regarding close approaches, which numbered 400 per week (for approaches within 5 km (3 mi)) for the entire Iridium constellation. He estimated the risk of collision per conjunction as one in 50 million.[10]
The collision occurred at 16:56UTC 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.[11] It had no propulsion system,[12] and was no longer actively controlled.[13][14]
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 10 cm (4 in), in addition to many smaller ones.[15] By July 2011, theU.S. Space Surveillance Network had catalogued over 2000 large debris fragments from the collision.[16] NASA determined the risk to theInternational Space Station, which orbits about 430 kilometres (270 mi) below the collision course, to be low,[8][17] 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 inSun-synchronous orbits,[18] and the ISS did have to perform anavoidance maneuver due to collision debris in March 2011.[16]
By December 2011, many smaller pieces of the debris were in an observableorbital decay towards Earth, and were expectedto 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.[19] In 2024, 15 years after the collision, theU.S. Space Surveillance Catalog listed 916[20] and 212[21] pieces of 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 120 m (390 ft). 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.[22]
A number of reports of phenomena in theU.S. states ofTexas,Kentucky, andNew Mexico were attributed to debris from the collision in the days immediately following the first reports of the incident in 2009,[23] although NASA and theUnited States Strategic Command, which tracks satellites and orbital debris, did not announce any reentries of debris at the time[24] and reported that these phenomena were unrelated to the collision.[25] On February 13, 2009, witnesses in Kentucky heardsonic booms.[26] TheNational Weather Service issued an information statement alerting residents of sonic booms due to the falling satellite debris.[27] TheFederal Aviation Administration also released a notice warning to pilots of the re-entering debris.[28] Some reports include details that point to these phenomena being caused by ameteoroid shower.[24] A very brightmeteor over Texas on February 15, 2009, was mistaken for reentering debris by some witnesses.[29]
This collision and numerous near-misses have renewed calls for mandatory disposal of defunct satellites (typically bydeorbiting them, or at minimum, sending them to agraveyard orbit), but no such international law exists as of 2025. Nevertheless, some countries have adopted such a law domestically, such as France in December 2010.[30] The United StatesFederal Communications Commission (FCC) requires all geostationary satellites launched after March 18, 2002 to commit to moving to agraveyard orbit at the end of their operational life.[31]
Strela-2M satellites had lifetimes of around 3 years, and Gen. Yakushin of the Military Space Forces was quoted in Moscow Times as saying Kosmos-2251 went out of service in 1995.
Russia has not commented on claims the satellite was out of control
