AA 279B · Advanced Space Mechanics

Space Debris &
Collision Avoidance

Duncan Eddy · November 10, 2026

Stanford University

Iridium 33 and Cosmos 2251 collision, February 10, 2009

Relative speed
--km/s
Altitude
--km
Crossing angle
--°
Predicted miss distance (public element sets, SGP4)
--m
Actual miss distance
0m

Geometry reconstructed from the last public element sets before the event (Space-Track GP history, SGP4) · scripts/debris_clouds.py

Iridium 33 and Cosmos 2251 fragments still in orbit, November 2026

Fragments ever cataloged
--
Still in orbit, November 2026
--

Space-Track SATCAT and GP, propagated with SGP4 · scripts/debris_clouds.py

Starlink satellites made 207,152 collision avoidance maneuvers from December 2025 to May 2026

Starlink close approach video deck/img/starlink-near-miss.mp4

SpaceX semiannual Starlink report to the FCC, July 2026 · video: @Starlink, October 6, 2026

Rendering of a Capella Space SAR satellite

Sarah Scoles, "Two Satellites Almost Crashed. Here's How They Dodged It," WIRED, February 14, 2019

Diagram: incremental algorithmic response adoption at Project Kuiper, from satellite telemetry through orbit determination, prediction, ephemeris screening, conjunction event management, maneuver responsibility arbitration and pre-coordinated response rules

D. Eddy, "Operator CDM Response Coordination," SSA Operators Workshop, June 3, 2022, slide 12

How do you avoid a crash when you drive?

How do you avoid a crash when you drive?

On the road

AASHTO, A Policy on Geometric Design of Highways and Streets, 7th ed. (2018), Ch. 3 stopping sight distance · scripts/avoidance_budget.py

Highway speed: -- mph (closing head-on: -- mph).

You can see at least -- ft ahead: the design sight distance for this speed.

Hard braking at -- g, after a -- s reaction time.

You stop in -- ft, well inside the distance you can see.

In orbit

Orbion Aurora datasheet (2021); K2 Space · scripts/avoidance_budget.py

Median closing speed of this week's close approaches: -- mph (-- km/s).

A sensor that sees 100 km ahead gives you -- s.

Thrust the whole time: Orbion Aurora (19 mN, 100 kg sat) or K2 Space (1 N, 2,000 kg bus).

You move -- cm or -- cm.

Maneuvering one orbit early: the same thrusters and the same 8.5 s burn

550 km circular orbit: a = -- km, v = -- km/s, period -- min. Burn along the velocity one orbit before closest approach.

Orbion Aurora, 100 kg1 N, 2,000 kg K2 bus
Δv from 8.5 s of thrust\(\Delta v = (F / m)\, t\)----
Change in semi-major axis\(\Delta a = 2a\,\Delta v / v\)----
Change in orbital period\(\Delta T = 3\pi\,\Delta a / v\)----
Along-track shift one orbit later\(\Delta s \approx v\,\Delta T = 3\pi\,\Delta a\)----
Same burn in the last 8.5 s\(\Delta s = \tfrac{1}{2}(F / m)\, t^2\)----

scripts/avoidance_budget.py

Early maneuvers work by changing the orbital period, not by pushing the satellite aside. The along-track offset grows by about 3πΔa every orbit.

Avoiding a collision in space requires advance warning, which requires tracking objects in orbit and predicting close approaches before they happen.

Sensing from orbit can help, but only at enormous scale: SpaceX's Stargaze uses the star trackers on thousands of Starlink satellites.

The collision avoidance lifecycle

Measure

Where is it?

Catalog

What is it?

Screen

Who comes close?

Assess

How likely is it?

Decide

Move or wait?

Share

Where are you going?

The public catalog: tracked objects in Earth orbit

Space-Track GP catalog · scripts/catalog.py

How do we know where objects in space are?

How do we know where objects in space are?

GPS

position (and velocity)
meters, every few seconds

Radar

azimuth, elevation,
range, range-rate

Telescope

azimuth, elevation,
brightness (no range)

Two-way ranging

range from the round-trip time
of a ground-station link

Laser ranging

range to retroreflectors,
millimeters to centimeters

Doppler

range-rate from the
carrier frequency shift

US Space Surveillance Network: radars and telescopes

Vallado, Fundamentals of Astrodynamics and Applications, 4th ed. (2013), Tables 4-2 to 4-4 · scripts/ssn_sensors.py

--, 24 hours: -- radar passes, longest unobserved gap -- h.

Simulated radar tracks of 20 satellites from one rideshare

Eglin radar (brahe SSN dataset) · scripts/rideshare_tracks.py

What do we do with all these tracks?

Associate them with objects, estimate each object's orbit, and keep those orbits up to date in a catalog.

What is a catalog?

What is a catalog?

A maintained list of tracked objects and their current orbits. Several exist, each with a different set of objects.

Space-Track.org

Run by the US Space Force's 18th Space Defense Squadron, whose mission is to maintain the satellite catalog.

When people say "the catalog", they almost always mean this one.

CelesTrak

Public and free. Redistributes the Space-Track data and adds supplemental orbits from operators' own ephemerides.

TraCSS, space-safety.com

Operator coordination platforms (Office of Space Commerce; SpaceX) with their own catalogs. Not public.

space-track.org · celestrak.org · TraCSS · space-safety.com

Multi-hypothesis tracking for track-to-object association

  1. Generate hypotheses. The new track could belong to any object it plausibly matches (gating), be a new object, or be a false alarm.
  2. Score them. How well the track fits each object's predicted orbit, given its uncertainty, plus prior rates of new objects and false alarms.
  3. Extend. When the next track arrives, branch every surviving hypothesis again.
  4. Prune and commit. Drop unlikely branches. Commit to an association only once one hypothesis clearly wins.

Tangent: Two-Line Elements

Developed for NORAD in the 1960s, when numerically integrating the whole catalog was too expensive: mean elements fitted for the semi-analytic SGP4 propagator, which includes a drag term.

Common mistakes when using TLEs

Mistake 1

click to reveal

Mean elements as osculating

TLE elements are SGP4 mean elements. Converting them straight to a position and velocity gives the wrong orbit.

Mistake 2

click to reveal

TEME used as GCRF

SGP4 outputs TEME, not a standard inertial frame. Convert it.

Mistake 3

click to reveal

A different propagator

Only valid with SGP4. Even from the correct osculating state, a similar numerical propagator drifts away.

scripts/tle_gotchas.py

Do you see an issue with this?

The catalog ran out of five-digit numbers

On July 11, 2026 the catalog passed 69,999 and jumped to 100000. Four months later, -- tracked objects have six-digit numbers.

Use GP records (CCSDS OMM, in JSON or XML) with the same SGP4.

Many people still call these TLEs.

Which of ~-- catalog objects pose a risk?

Brute-force screening of the full catalog over 7 days

All-vs-all pair count for a 33,791-object catalog: Srinivas, Kim, Eddy & Kochenderfer 2026, arXiv:2610.11645

Screening filters: apsis, path and phase

Hoots, Crawford & Roehrich 1984 · scripts/screening.py

Why is the screening volume a box that is thin radially and long along-track?

Why is the screening volume a box that is thin radially and long along-track?

It will pass -- m away at -- km/s.

How would you estimate the probability that they collide?

--

Monte Carlo probability of collision

CALIPSO vs. Cosmos 2251 debris (NASA CARA test case) · scripts/pc.py

How many samples are needed?

2D probability of collision (Foster 1992)

1. Assume motion during the encounter is a straight line

At -- km/s and --°, the encounter lasts under a second; covariances stay fixed.

2. Add the two covariances

\(C = C_1 + C_2\) is the uncertainty in the position of one object relative to the other.

3. Project onto the encounter plane

Only directions perpendicular to the relative velocity matter: -- (1σ).

4. Integrate over the hard-body disk

Relative position \(\mathbf{x}\) = primary − secondary is Gaussian around the predicted miss \(\boldsymbol{\mu}\). \(P_c\) is the chance it lands within \(R = R_1 + R_2 =\) -- m of the secondary:

\(P_c = \displaystyle\iint_{\lVert \mathbf{x} \rVert \le R} \mathcal{N}\!\left(\mathbf{x};\ \boldsymbol{\mu},\ C_{2D}\right) dA\)

\(P_c =\) -- (1 in --)

Monte Carlo with -- samples: --. Matches NASA CARA on -- test cases (max relative error --).

Foster & Estes 1992, NASA JSC-25898; NASA CARA Pc2D_Foster · scripts/pc.py

Probability of collision methods

2D \(P_c\)

Foster 1992, Chan, Alfano

Fast encounters, straight-line motion. The workhorse.

3D \(P_c\)

Hall et al. (NASA CARA)

Curved relative motion and changing covariance. Slow or long encounters, GEO.

Monte Carlo

Sampling from TCA or from epoch

The reference. Use it to check the others when assumptions are in doubt.

NASA CARA Analysis Tools

Conjunction Data Messages (CDMs) and reporting thresholds

NASA CARA plans a mitigation when \(P_c\) ≥ 1 in 10,000 (10⁻⁴).

Space Force "emergency" events in LEO: within 3 days, miss < 1 km and \(P_c\) ≥ 1 in 10,000 (10⁻⁴).

Thresholds are set by policy and differ between organizations.

Aside: Covariance realism

scripts/covariance_banana.py

Aside: Ephemeris quality

STARLINK-4133: the operator's GPS-based ephemeris vs the public catalog element set (GP / TLE)

scripts/starlink_vs_gp.py

Ephemeris quality: error during estimation and during prediction

Error source: 35% error in the drag model

scripts/gps_od.py

Ephemeris quality: better predictions, better decisions

Effect of miss distance and uncertainty

Keep the miss direction, the covariance shape and the hard-body radius. Set the miss distance (5 m, 197 m, 2 km), scale every 1σ by the same factor, and recompute \(P_c\).

Large σ: the miss distance barely matters

At σ = 10 km, misses of 5 m, 197 m and 2 km all give \(P_c \approx 10^{-5}\).

Small σ: \(P_c\) goes to 1 or 0

At σ = 10 m, the 5 m miss (inside R = 15 m) gives 0.8. The 197 m and 2 km misses give less than \(10^{-100}\).

scripts/pc_evolution.py · Alfano 2005 (dilution)

Ephemeris quality: what you can screen against

Public catalog

GP / TLE mean elements for SGP4, on Space-Track for anyone with an account.

STARLINK-4133: about 1 km off at the start, 77 km along-track after 3 days. No covariance.

SP catalog

Special Perturbations ephemerides and state vectors from the 18 SDS High Accuracy Catalog, refit every 8 h.

Requires an SSA Sharing Agreement (Advanced CA). No covariance in the files.

Operator ephemerides

Each operator's own orbit determination, often GPS, with planned maneuvers.

Shared on Space-Track and space-safety.com, usually with covariance.

With SP ephemerides an operator can screen its own trajectories on demand. \(P_c\) still needs a covariance for the other object.

USSF Spaceflight Safety Handbook for Satellite Operators v1.7, pp. 3–8

Hands up

\(P_c = 10^{-3}\), three days before closest approach. Do you maneuver?

Now · Wait for the next update · No

\(P_c\) changes as tracking updates arrive before closest approach

scripts/pc_evolution.py

Unknowns at decision time

Updates?

Will we get more measurement updates before TCA?

How will dynamics uncertainty change \(P_c\) by then?

Data?

Will the other operator share their ephemeris?

Is it built correctly: frame, covariance, planned maneuvers?

Their action?

Can they maneuver: thrusters or differential drag?

Will they? When, and in which direction?

Net effect?

What does each of these do to the risk?

Up or down, and by how much?

Smaller: our own thruster performance, the other object's size and attitude.

Approaches to the maneuver decision

Space Force screening: what is screened against what, and when

All HAC (High Accuracy Catalog)

Every object in the SP catalog against every other: near-Earth (period ≤ 225 min) propagated 7 days, deep space 10 days.

Concern list

Re-screens the pairs that All HAC flagged, with TCA ≤ 5 days: \(P_c\) ≥ 10⁻⁷ near-Earth, miss ≤ 5 km deep space.

O/O ephemeris vs HAC

Your uploaded ephemeris against the SP catalog. Operational files: results 8–12 h after the slot. Special (maneuver) files: as soon as possible, results within 4 h.

O/O vs O/O

Operational ephemerides against each other, re-screened every 8 h until less than 8 h (near-Earth) or 12 h (deep space) of the file remains.

USSF Spaceflight Safety Handbook for Satellite Operators v1.7, pp. 5–9 · schedule in EST (EDT is one hour earlier)

Planning a maneuver: screen, decide, share

You launch next year. What do you need to be able to do?

You launch next year. What do you need to be able to do?

Register

Account and SSA sharing agreement: CDMs, ephemeris screening, SP data

Also: TraCSS · space-safety.com

Automate flight dynamics

Download measurements and determine and predict orbits, automatically

Check that predictions are self-consistent

Share it

Publish predicted ephemerides (OEM) and maneuver plans

Have a conjunction response plan

Fixed rules, trade-space tools, or a solved decision policy

On call at any hour

Have the process before launch. The first warning can arrive before your thrusters are commissioned.

Resources

Doing this requires time systems, reference frames, propagation, estimation, data formats and catalog clients.

Does every new operator have to build all of this?

brahe: an open-source astrodynamics library

Time & frames

time · eop · frames · coordinates · spice · attitude

Dynamics

orbits · orbit_dynamics · propagators · integrators · relative_motion

Analysis

events · access · estimation

Data formats

ccsds (OEM · OPM · OMM · OCM) · itc · sp3

Clients

spacetrack · celestrak · starlink · igs

Tools

constants · math · plots · cli

Coming

conjunction screening · \(P_c\)

Rust core, Python API, MIT licensed, developed since 2014. Every figure today is a short uv run script built on it.

brahe: Earth orbit with a chosen force model

import brahe as bh

epoch = bh.Epoch(2026, 11, 10, 0, 0, 0.0, time_system=bh.TimeSystem.UTC)
x0 = bh.state_koe_to_eci([bh.R_EARTH + 525e3, 0.001, 97.5, 30, 0, 0],
                         bh.AngleFormat.DEGREES)

force = bh.ForceModelConfig(
    gravity=bh.GravityConfiguration.spherical_harmonic(degree=20, order=20),
    drag=bh.DragConfiguration(bh.AtmosphericModel.HARRIS_PRIESTER,
        area=bh.ParameterSource.value(1.2), cd=bh.ParameterSource.value(2.2)),
    third_body=[bh.ThirdBody.SUN, bh.ThirdBody.MOON],
    mass=bh.ParameterSource.value(100.0),
)
prop = bh.NumericalOrbitPropagator(epoch, x0,
    bh.NumericalPropagationConfig.default(), force)
prop.propagate_to(epoch + 3 * 86400.0)

brahe: Earth to Mars, with an impulsive burn

bh.load_spice_kernel("de440s")
t0 = bh.Epoch(2028, 12, 10, 0, 0, 0.0, time_system=bh.TimeSystem.TDB)
x0 = bh.spk_state(bh.NAIFId.EARTH, bh.NAIFId.SUN, t0)  # on Earth's orbit

sun = bh.CentralBody.from_naif_id(bh.NAIFId.SUN)
force = bh.ForceModelConfig.for_body(sun,
    gravity=bh.GravityConfiguration.point_mass(),
    third_body=[bh.ThirdBody.JUPITER, bh.ThirdBody.VENUS])

def tmi(epoch, x):  # trans-Mars injection: 3.2 km/s prograde
    x = x.copy()
    x[3:] += 3200.0 * x[3:] / np.linalg.norm(x[3:])
    return x, bh.EventAction.CONTINUE

cruise = bh.NumericalOrbitPropagator(t0, x0,
    bh.NumericalPropagationConfig.default(), force)
cruise.add_event_detector(
    bh.TimeEvent(t0 + 86400.0, "TMI").with_callback(tmi))
cruise.propagate_to(t0 + 204 * 86400.0)  # passes Mars

Summary

Spacecraft collision avoidance is managed through the intersection of multiple complex systems, all of which are facing strain under increased operational activity.