Cosmos-2251 / Iridium 33 Collision (2009) — First Accidental Satellite Collision

2,300+

Tracked Fragments

~790 km

Collision Altitude

11.7 km/s

Closing Velocity

What Happened

On 10 February 2009 at 16:56 UTC, the inactive Russian military communications satellite Cosmos 2251 (launched 1993, defunct since 1995) collided with the operational Iridium 33 communications satellite over northern Siberia at approximately 790 km altitude. The relative velocity was about 11.7 km/s — a hypervelocity impact that completely destroyed both spacecraft. This was the first confirmed accidental collision between two intact catalogued satellites.

Key Facts

Date	10 February 2009, 16:56 UTC
Location	Over northern Siberia (~790 km altitude)
Object 1	Cosmos 2251 — Russian Strela-2M military comms satellite (launched 16 June 1993, ~900 kg, defunct since 1995)
Object 2	Iridium 33 — Iridium constellation satellite (launched 14 September 1997, ~689 kg, operational)
Relative Velocity	~11.7 km/s (nearly perpendicular orbits)
Cosmos 2251 Fragments	~1,668 catalogued
Iridium 33 Fragments	~628 catalogued
Total Tracked Fragments	~2,300+
Orbit Inclinations	Cosmos: 74.0° / Iridium: 86.4°

Significance

This collision proved that the scenario at the heart of Kessler syndrome — accidental collisions between uncontrolled objects generating cascading debris — was not theoretical. It was actually happening. Both the Fengyun-1C ASAT test (2007) and this collision together more than doubled the catalogued debris population below 1,000 km in just two years.

The event also demonstrated a fundamental asymmetry: the operational Iridium 33 could have potentially manoeuvred to avoid the collision, but no conjunction warning was issued with sufficient confidence or lead time. The defunct Cosmos 2251 had no ability to manoeuvre at all — highlighting the threat posed by thousands of dead satellites drifting uncontrolled through busy orbital regimes.

Debris Persistence

At ~790 km altitude, atmospheric drag is minimal. The majority of fragments from both satellites remain in orbit as of early 2026 and will persist for decades. Some fragments were ejected to higher or lower altitudes by the energy of the collision, creating a spread across a range of orbital heights. The two debris clouds are distinguishable by their different orbital inclinations (74° vs 86.4°).

Lessons for Conjunction Assessment

The collision accelerated the development of improved conjunction assessment services. In 2010, the US established the Combined Space Operations Center (CSpOC) process for providing conjunction warnings to all satellite operators, not just US government assets. Commercial operators now receive thousands of conjunction data messages (CDMs) per week and must maintain the capability to perform avoidance manoeuvres. This event is a primary reason why conjunction assessment is now a fundamental part of satellite operations.

Potentially. Iridium 33 was operational and had manoeuvring capability. However, conjunction screening in 2009 was less mature than today, and actionable warnings were not reliably provided to commercial operators. The event demonstrated the need for systematic conjunction screening — which has since been established.

Fengyun-1C produced more fragments (~3,500 vs ~2,300) and at a higher altitude where they persist longer. However, the Cosmos-Iridium collision was arguably more significant because it was accidental — proving that the debris environment had reached a density where random collisions between intact objects were occurring without human intent.