USA-193 intercept, Operation Burnt Frost (2008)
What happened
USA-193 was a US National Reconnaissance Office satellite that lost contact with the ground within hours of reaching orbit in December 2006 and was never controlled. On 20 February 2008 at approximately 22:26:47 EST, which is 03:26:47 UTC on 21 February, the cruiser USS Lake Erie launched a single Standard Missile-3 that intercepted the satellite at an altitude above 240 km and a closing speed above 35,000 km per hour. The stated rationale was the hazard of an uncontrolled reentry carrying roughly 450 kg of hydrazine in a tank designed to survive it. Reaching the target required capability the system did not have: three SM-3 missiles had their seekers modified to acquire an infrared signature lower than that of a ballistic missile, and the Aegis weapon system itself was modified for the engagement. Three Aegis warships participated, with Lake Erie as the firing ship. Orbital data for 173 debris objects were subsequently released via Space-Track; at least 152 had decayed by May 2009, and modelling of 10 to 20 cm objects put complete decay at 81 to 99 days after the intercept. The Department of Defense stated that no parts larger than a football survived.
Carried in a cyber corpus for one reason: a ballistic-missile-defence system acquired a counterspace mission in about six weeks by modifying its seeker discrimination and its fire-control software, not by building anything. That is the clearest public illustration that in a software-defined weapon system the line between missile defence and anti-satellite weapon is a configuration decision, and every argument about dual-use capability, export control and the verifiability of counterspace restraint runs through it. The corollary for defenders is that the capability was latent beforehand and nothing observable about the fleet changed. The debris outcome is the low-altitude case, 173 catalogued objects with near-total decay inside three months, and is the same design choice India made in 2019. One thing this record deliberately does not assert: the intercept also destroyed a classified reconnaissance payload that would otherwise have reached the ground substantially intact, and the episode is often discussed in those terms, but no source used here establishes that as a motive. Overall confidence is moderate rather than high because the software-modification claim, which is the record's point, currently rests on its weakest source.
Attack vector
A Standard Missile-3 launched from an Aegis cruiser, with one-time modifications to the missile's infrared seeker and to the Aegis weapon system, intercepting the target above 240 km.
Operational impact
Permanent destruction of USA-193, which was already uncontrolled and non-functional. 173 catalogued debris objects, substantially all decayed within three months of the intercept.
Affected segments
space
Disclosed
2008-02-21
SPARTA techniques evidenced
Each row is a technique this record evidences, with the reasoning and the source that attests to it.
What relationship, confidence, and evidence mean on the rows below
- Relationship
What kind of link this is between the technique and the target.
Mitigates: the target actively prevents, detects, or recovers from the technique.
Addresses: the target governs the technique or is relevant to it, without interdicting it. Most governance and policy obligations sit here.
Triggers obligation: the technique occurring is what triggers the duty the target imposes.
Relates to: related to the technique, but the target neither interdicts nor governs it. Used sparingly.
- Confidence
How strongly the source supports this mapping, not how severe the technique is.
High: the source supports the mapping squarely.
Moderate: supported, with a qualification such as a cross-tactic reading that stays operationally sound.
Low: the source reaches the technique only in part.
- Evidence
How close to the source text the mapping was made.
Direct: a verbatim excerpt of the cited source was read against the technique, and the rationale argues from that excerpt.
Derived: the mapping follows from the source's scope or structure, with no on-point excerpt addressing the technique.
Inferred: reached by composition through another framework, or by domain reasoning the source does not support on its face.
A missile launched from Earth to destroy a satellite in orbit is EX-0017.01's definition, and that is what the sources describe. That the operator was destroying its own satellite does not affect the mapping: the technique describes the act, not the relationship between the parties.
The satellite was permanently eliminated by physical damage. The Department of Defense's own statement, that no parts larger than a football survived the strike, is the measure of it, and 173 debris objects were catalogued.
Kinetic capability was possessed and used against a satellite on orbit, which is RD-0005.03's subject, and the technique's text does not require a purpose-built system. What makes the edge worth recording is how the capability was obtained: by modifying an existing ballistic-missile-defence system's infrared seeker and weapon-system software over about six weeks. Confidence is moderate rather than high because that modification claim rests on the weaker of the two sources used in this record.
Considered and not mapped
These techniques were considered for this record because a source, a related record or SPARTA's own catalogue pointed at them. Each was read against what the sources say and not mapped. The reason is given in full.
Rejected as in the other two kinetic records, and most easily here: 173 catalogued objects with near-total decay inside three months is not a meaningful catalogue burden.
The attack was kinetic.
An initial-access technique: using a counterspace platform to create conditions for execution against a target. Here the kinetic effect was the objective.
The classified-payload question runs the other way: the concern was denying recovery, not effecting it. No source describes anything being taken.
Sources
The published accounts this record rests on. The tier is SafeMode Space's own assessment of the source, and the reason for it is given beside it. What the tiers mean and how they are assigned: the source tiers.
A source is listed when a mapped technique rests on it, or when it disputes the account. One the curators read but neither cited nor recorded as disputing the record is not listed, so an absence here means neither is true rather than that nobody looked.
- USA 193 Post-Shootdown AnalysisResearcher blog
Tier 2: Independent orbital analysis by the analyst who maintains CelesTrak, working from released Space-Track data. Authoritative on the debris cataloguing and decay; a self-published technical page rather than peer-reviewed.
Tier 3: Defence trade outlet, undated, not a government document. Tier 3, and the weakest source used in this batch relative to the weight the record puts on it.
Every source SafeMode Space reproduces, and on what terms: sources and attribution.