IRIDIUM 33

NORAD 24946· COSPAR 1997-051C· Debris· LEO
Launch
Launched on Sep 14, 1997 from 81/23 (81L), Kazakhstan aboard a Proton-K/17S40.
Proton-K/17S40 | Iridium 27 to 33
IRIDIUM 33
Flickr user ideonexus · CC BY-SA 2.0 · via Wikimedia Commons
Live · TLE epoch 2026-07-13 10:31 UTC
Orbit class
LEO — Low Earth Orbit (circular, < 2,000 km)
Operator
Iridium Communications
Country
United States
Manufacturer
Thales Alenia Space
Launched
Sep 14, 1997
Mass
700 kg
Apogee
783 km
Perigee
774 km
Inclination
86.39°
Period
1.67 h
Debris origin · satellite collision

Iridium 33 was an operational satellite in the Iridium voice-and-data constellation when it was struck by the defunct Russian Kosmos-2251 on 10 February 2009 at about 789 km altitude — the first accidental collision between two intact satellites. Its debris cloud accounts for roughly 600 catalogued fragments; together the two clouds produced over 2,000.

Parent object
Iridium 33
Event date
Feb 10, 2009
Altitude
~789 km
Radar size class
LARGE
2009 satellite collision (Wikipedia)

About IRIDIUM 33

Iridium 33 is an American communications satellite operated by Iridium Communications as part of its first-generation mobile telephony constellation. Carrying the NORAD catalog identifier 24946 and the international designator 1997-051C, the spacecraft was lofted into low Earth orbit in September 1997 and became one of the working nodes of what was, at the time, among the most ambitious commercial satellite ventures ever undertaken. Today, Iridium 33 is perhaps best known not for its years of quiet service relaying voice and data calls, but for its role in the most significant accidental collision in the history of spaceflight — an event that permanently changed how the international community thinks about orbital debris and spacecraft conjunction analysis.

Mission and Purpose

Iridium 33 was designed to serve as a single cell in the broader mesh of the Iridium satellite constellation, a network conceived to provide continuous, pole-to-pole mobile voice and data coverage for subscribers anywhere on Earth's surface. Unlike geostationary communications satellites, which hang over a fixed equatorial point and require large dish antennas to operate, the Iridium system relied on a dense array of low-orbiting spacecraft that could be reached by small handheld terminals. Each satellite in the constellation linked to its neighbors through inter-satellite crosslinks, effectively routing calls through the sky without necessarily touching a terrestrial gateway.

Iridium 33 was assigned to Plane 3 of the operational constellation, a specific orbital shell arranged to interleave with the other planes and ensure that at least one satellite was always visible above the horizon for a user on the ground. The ascending node for this plane was positioned at 230.9°, placing it in the geometric slot required for seamless handoffs as callers moved from one satellite's footprint to the next. Each plane in the Iridium system was populated with active satellites and, in some cases, on-orbit spares that could be maneuvered into position should a primary unit fail.

The specific mission configuration details for Iridium 33, as recorded in the satellite catalog, are not publicly disclosed beyond what is standard for commercial telephony payloads of its era. What is certain is that it formed an integral piece of a larger system intended to serve maritime users, aviation customers, remote industrial sites, and individual subscribers who routinely traveled beyond the reach of conventional cellular networks.

Orbit and Tracking

Iridium 33 was launched on 14 September 1997 at 01:36 UTC from the Baikonur Cosmodrome in Kazakhstan, lifting off from Site 81/23 aboard a Proton-K rocket equipped with a Block DM2 upper stage. The launch was arranged through International Launch Services, the commercial launch provider that marketed Proton capacity to Western customers during that period. Despite being an American-owned and American-operated asset, the satellite reached space on a Russian booster — a common arrangement during the commercial launch boom of the late 1990s.

The spacecraft settled into a low Earth orbit characterized by an apogee of 785 km and a perigee of 772 km, making the orbit nearly circular. It travels at an inclination of 86.4°, a near-polar trajectory that carries the satellite over or near both poles on every pass and gives the constellation its global coverage characteristic. One complete orbit takes approximately 100.3 minutes, meaning Iridium 33 completed roughly fourteen and a half laps around the Earth each day during its operational life.

This near-polar, near-circular orbit made Iridium 33 — and indeed all members of the constellation — relatively straightforward objects to track using ground-based radar. At an altitude just under 800 km, the satellites were bright enough to be observed visually from the ground under the right lighting conditions, and ground tracking networks maintained regular positional updates on each vehicle. The orbit's high inclination means the satellite regularly passes over populated regions at high latitudes, including Canada, northern Europe, and Russia, as well as the equatorial belt.

Design and Operator

Iridium 33 was manufactured by Thales Alenia Space and had a launch mass of approximately 700 kg. The first-generation Iridium satellites were designed as relatively compact, three-panel spacecraft featuring the distinctive triangular mission antennas that gave them their recognizable profile and, incidentally, produced a well-known visual phenomenon. The highly reflective main mission antenna arrays occasionally caught sunlight at precise angles and produced brilliant, brief flashes visible to the naked eye from the ground — a phenomenon that became known among amateur astronomers and satellite observers as "Iridium flares." These flares could briefly outshine everything in the night sky except the Moon, and dedicated prediction tools were developed to forecast them.

The satellite was operated by Iridium Communications, a United States-based company that held the operating license for the constellation. The Iridium program passed through a turbulent commercial history: after launching its full constellation and beginning commercial service in the late 1990s, the original operating company filed for bankruptcy in 1999 before being reorganized and relaunched under new ownership. Iridium Communications, in its reconstituted form, continued to operate the first-generation constellation for years while planning its next-generation replacement system.

Thales Alenia Space, the satellite's manufacturer, is a Franco-Italian aerospace company with extensive experience in both civil and military satellite programs. The Iridium production contract represented one of the larger commercial satellite manufacturing programs of the 1990s, requiring the construction of dozens of essentially identical spacecraft on an accelerated schedule to populate the constellation before the system could begin revenue service.

The 2009 Collision and Legacy

The story of Iridium 33 cannot be told without addressing the event that made it one of the most discussed objects in the history of space operations. On 10 February 2009, Iridium 33 collided at high velocity with Kosmos-2251, a defunct Russian military communications satellite that had been inactive for roughly a decade. The impact occurred over northern Siberia at an altitude of approximately 789 km — squarely within the Iridium constellation's operational shell.

The collision was entirely unexpected. Neither satellite was being actively maneuvered, and conjunction warnings, while technically available, were not sufficiently integrated into operational procedures at the time to prompt evasive action. The result was catastrophic for both spacecraft: each was destroyed, generating thousands of pieces of trackable debris along with a far larger number of smaller fragments too small to be cataloged but large enough to pose a hazard to other satellites.

The debris clouds from both vehicles spread into crossing orbital bands and have persisted for years, gradually decaying as atmospheric drag slowly removes individual fragments from orbit. The event prompted a significant reassessment of how satellite operators, space agencies, and national governments coordinate to prevent orbital collisions. It accelerated investment in space situational awareness capabilities, spurred debates about mandatory debris mitigation standards, and underscored the practical danger of leaving non-functional hardware in heavily used orbital regimes without any form of disposal planning.

For the Iridium constellation specifically, the loss of a revenue-generating satellite in a critical plane forced operational adjustments and reinforced the commercial case for the next-generation Iridium NEXT program, which ultimately replaced the first-generation vehicles with satellites that incorporated more capable avionics and modern conjunction assessment protocols.

Current Status

Despite its destruction in the 2009 collision, Iridium 33 — or more precisely, the debris associated with the original satellite — is formally recorded in the catalog as still in orbit. The NORAD catalog entry 24946 persists as a tracking record, with the orbital parameters reflecting elements derived from catalog maintenance rather than a functioning, cohesive spacecraft. The residual debris continues to be monitored by the United States Space Surveillance Network and equivalent tracking organizations, as individual fragments pose an ongoing collision risk to active satellites operating in the same altitude band.

The original orbital parameters — an apogee of 785 km, a perigee of 772 km, and an inclination of 86.4° — represent the pre-collision trajectory of the intact vehicle. The actual debris field has dispersed across a range of altitudes and inclinations as individual pieces respond differently to atmospheric drag and solar radiation pressure. Tracking the complete debris environment associated with the collision remains an ongoing challenge for the space surveillance community.

The catalog entry for Iridium 33 thus serves a dual function: it documents a historical satellite with a defined operational biography, and it anchors a debris management record connected to one of the most consequential events in the practical history of Earth orbit utilization. Its story has become a standard reference point in discussions of orbital sustainability, space traffic management, and the long-term stewardship of the low Earth orbit environment.

Related satellites

Sources & further reading

Embed this satellite on your site

Free for editorial use. Attribution back to LowEarth is required.

<iframe src="https://lowearth.app/embed/24946" width="640" height="400" frameborder="0" allow="fullscreen"></iframe>