How One Missile Test Created Thousands of Orbital Hazards

What did the missile strike actually do?#

The satellite was destroyed by a high-speed physical collision. NASA's 2007 technical account describes a kinetic kill vehicle striking Fengyun-1C. A nuclear detonation is not needed to explain the breakup.

At such speeds, the impact launches shock waves through the material. Cracking, separation and the ejection of shattered material can follow. ESA's description of hypervelocity impacts explains why even a small projectile can cause extensive damage: both its mass and its relative speed matter, along with the materials and impact angle.

Kinetic energy scales with mass and the square of speed. For the same fragment, doubling the collision speed multiplies its kinetic energy by four. The diagram uses example speeds to show that relationship; it does not reconstruct the interceptor's actual speed. The exact hardware and encounter geometry are unnecessary to understand why one impact could turn a substantial spacecraft into many separate hazards.

A different historical interception, the F-15 attack on the Solwind satellite, provides context for the idea of destroying a target in orbit. Each event still needs its own assessment of where its debris went and how long it lasted.

Sources: [1][6]

How many fragments did observers actually count?#

By the end of 2007, more than 2,500 large fragments had been identified and tracked by the US Space Surveillance Network, according to a 2008 report by J.-C. Liou and Nicholas Johnson. That is a historical tracking result, not a count of every piece produced or a total remaining today.

NASA's January 2009 update separated two categories: 2,378 fragments larger than five centimetres had been formally catalogued, while more than 400 additional pieces were being tracked without yet being catalogued. The apparently smaller catalogue number therefore does not overturn the earlier tracking count. The reports describe different dates and different stages of identifying objects.

The same 2009 update estimated more than 150,000 fragments larger than one centimetre. That estimate was not 150,000 individually maintained orbital tracks. A fragment population inferred from observations and modelling is different from a catalogue of objects whose paths can be repeatedly followed. Nor does the estimate include every smaller splinter.

Sources: [2][3]

How did fragments from one place spread around Earth?#

Breaking the satellite did not remove its orbital motion. The pieces inherited motion around Earth, with the collision adding different changes in speed and direction. They entered a range of orbital paths instead of dropping together directly to the ground.

A fragment's orbital period is the time it takes to complete one circuit. Different periods let fragments separate along their paths. The planes containing those paths also change orientation, a motion called precession. NASA's 2007 analysis describes the initially narrow group of orbital planes spreading because their precession rates differed.

Pardini and Anselmo's 2007 study modelled the cloud's evolution, including this spreading into a shell-like distribution. NASA's January 2009 update subsequently illustrated orbital paths surrounding Earth. Such a picture combines many trajectories; it is not a photograph of a continuous wall of wreckage. The plotted lines also do not mean that fragments occupy every point along them simultaneously. Danger occurs when a spacecraft and a fragment arrive at the same place at the same time.

Sources: [1][4][3]

Why did the debris stay up for so long?#

Earth's gravity continues to bend each fragment's moving path into an orbit. Removing a satellite's ability to work does not, by itself, remove the motion that keeps it orbiting.

There is atmosphere at these heights, but it is extremely thin. Drag gradually removes orbital energy. As an orbit drops into denser air, the braking becomes stronger and ultimately leads to reentry. ESA explains that above about 800 kilometres, drag is much less effective and objects generally remain for many decades.

The January 2009 NASA update reported that fewer than two per cent of the catalogued Fengyun-1C fragments had reentered since the breakup. It warned that many pieces would last decades and some more than a century. These were contemporary assessments of a long-lived cloud, not a promise that every fragment had the same expiry date.

Shape and mass matter too. A lightweight sheet presents more area to drag per unit mass than a compact chunk. Liou and Johnson found unusually high area-to-mass ratios among some Fengyun-1C fragments, consistent with thermal blankets. Solar activity also changes upper-atmosphere density. Lifetime calculations therefore depend on an object's orbit and physical properties as well as assumptions about the atmosphere; they cannot supply a single exact clearing date for the entire cloud.

Sources: [5][3][2][7]

What can another satellite do about the danger?#

Operators compare predicted fragment and spacecraft orbits. A close approach is called a conjunction; its assessed risk depends on uncertainty as well as predicted separation.

ESA describes debris specialists alerting a mission team when its risk threshold is exceeded and helping plan an avoidance manoeuvre. They check the proposed path for risk reduction and other conjunctions. A warning does not guarantee a collision, and moving a satellite does not remove the fragment.

Tracking has limits. ESA describes routine low-orbit cataloguing for objects roughly five to ten centimetres across and larger. Smaller detections need not yield dependable individual predictions. Shielding offers some protection from small impacts; larger known objects may be avoided through manoeuvres. Neither approach makes debris harmless.

A fragment can also strike another object and create more fragments. Population models assess that mechanism; they do not name the next victim or collision date. A brief destructive act can leave other spacecraft carrying the operational burden long afterward.

Sources: [7][6][2][1]