Author Description

<p>In February 2009, the commercial communications satellite Iridium 33 collided with the Russian military communications satellite Cosmos 2251. The collision, which was not the first recorded between two satellites in orbit-but the most recent and alarming-produced thousands of pieces of debris, only a small percentage of which could be tracked by sensors located around the world. In early 2007, China tested a kinetic anti-satellite weapon against one of its own satellites, which also generated substantial amounts of space debris. These collisions highlighted the importance of maintaining accurate knowledge, and the associated uncertainty, of the orbit of each object in space. These data are needed to predict close approaches of space objects and to compute the probability of collision so that owners/operators can decide whether or not to make a collision avoidance maneuver by a spacecraft with such capability. The space object catalog currently contains more than 20,000 objects, and when the planned space fence radar becomes operational this number is expected to exceed 100,000.</p> <p>A key task is to determine if objects might come closer to each other, an event known as "conjunction," and the probability that they might collide. The U.S. Air Force is the primary U.S. government organization tasked with maintaining the space object catalog and data on all space objects. This is a complicated task, involving collecting data from a multitude of different sensors-many of which were not specifically designed to track orbiting objects-and fusing the tracking data along with other data, such as data from atmospheric models, to provide predictions of where objects will be in the future.</p> <p>The Committee for the Assessment of the U.S. Air Force's Astrodynamic Standards collected data and heard from numerous people involved in developing and maintaining the current astrodynamics standards for the Air Force Space Command (AFSPC), as well as representatives of the user