Skip to content

Graveyard Orbit

An end-of-mission storage orbit whose selected state and long-term evolution limit interference with populated operational regions.

Core Idea

A graveyard orbit stores a retired spacecraft or stage in an orbital state chosen to limit future interference with populated operating regions. Its important parts are the retired object, the selected orbit, the operating region to avoid, and how that orbit changes over time. Merely putting a satellite “higher” does not establish safe storage. ESA defines the storage idea through contained orbital variation and non-interference under stated requirements.[^ref-b409966a300d]

Scope of Application

An unnamed Eurostar 2000 telecommunications spacecraft was retired from GEO service in 2003. Operators raised its perigee while managing eccentricity and solar-pressure effects; the report gives a final perigee-altitude excess of 243.5 km above the GEO reference and short postflight checks.[^ref-3f5e67532764]

Galileo's GSAT0104 retired into a MEO storage orbit in April 2024. Its report gives an achieved mean semimajor-axis offset of 701.4 km and models later evolution relative to navigation-constellation shells. That offset and the Eurostar perigee excess measure different things. Galileo's centuries-long propagation is a forecast, rather than centuries of observation.[^ref-b8c31b1c449d]

The orbital-storage relation can also apply to launcher stages. LEO disposal by atmospheric decay has a removal endpoint and is outside this bounded graveyard-storage identity. Passivation reduces stored-energy hazards but does not itself establish orbital clearance.[ref-b409966a300d][ref-b8c31b1c449d]

Clarity

Ask three questions: Where is the retired object now? How may its orbit evolve? What evidence supports the answer? An initial separation is not a promise of permanent clearance. A proposed target, reported achieved elements, and a modeled future are distinct claims. “Graveyard” does not mean collision-free forever.[ref-b409966a300d][ref-b8c31b1c449d]

A Parking Orbit instead provides a temporary coast before a later mission injection. A graveyard orbit is an end-of-mission storage state. Their paths are orbital, but their complete purposes differ.

Manages Complexity

Disposal decisions combine maneuver capability, propellant, eccentricity, perturbations, operational shells and risk. The storage relation keeps those details organized around a smaller decision: which reachable state maintains the required separation behavior over the declared assessment horizon? Hardware and maneuver counts vary; the retirement purpose and region-relative evolution remain.[ref-3f5e67532764][ref-b8c31b1c449d]

Abstract Reasoning

Identify the operating region, select a disposal orbital state, and evaluate its evolution under stated assumptions. For GEO, ESA's 2023 requirements offer conditional routes using a perigee margin and orbital-variation or collision-risk assessments over specified intervals. These are scoped requirements, not the definition of every graveyard orbit and not a MEO formula.[^ref-b409966a300d]

The two reports show different trade-offs. Eurostar operators stopped maneuvering when further perigee benefit was small relative to control risk. Galileo's analysis balanced projected shell clearance against expanding the disposal region. Neither case supplies one universal altitude or maneuver recipe.[ref-3f5e67532764][ref-b8c31b1c449d]

Knowledge Transfer

The GEO and MEO cases share a retired orbital bearer, a selected storage state, and a forecast or observation assessed against an operating region. Their numeric thresholds and evidence horizons do not transfer automatically. Space Trajectory is the broader parent: this is a retirement-specific orbital path with a storage objective and region-relative assessment. Similarity to storing obsolete data is only an analogy unless another abstraction is independently justified.[ref-3f5e67532764][ref-b8c31b1c449d]

Relationships to Other Abstractions

Local relationship map for Graveyard OrbitParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Graveyard OrbitDOMAINDomain-specific abstraction: Space Trajectory — is a kind ofSpace TrajectoryDOMAIN

Current abstraction Graveyard Orbit Domain-specific

Parents (1) — more general patterns this builds on

  • Graveyard Orbit is a kind of Space Trajectory Domain-specific

    A graveyard orbit is a retirement-specific orbital trajectory whose evolved state is assessed against operational-region clearance.

Hierarchy path (1) — routes to 1 parentless root

Neighborhood in Abstraction Space

Graveyard Orbit sits in a sparse region of the domain-specific corpus (91st percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Unclustered & Miscellaneous (2721 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-17

References

[^ref-b409966a300d]: European Space Agency (2023). ESA Space Debris Mitigation Requirements. ESSB-ST-U-007, Issue 1, Revision 0, 30 October 2023. §3.2.23, PDF index11/physical p12; §3.2.28, index12/p13; §§5.4.2.1–5.4.2.2, index47/p48. Original official normative standard; numerical criteria apply within its scope. [^ref-3f5e67532764]: Franck Raballand, David Mignon and Jean-Louis Gonnaud (2005). “EUROSTAR 2000 Disposal on a Graveyard Orbit: Orbit Control Strategy and Operational Implementation”. Fourth European Conference on Space Debris, ESA SP-587, August 2005. §§1.2–2.2, PDF indices0–2/physical pp1–3; §3.3, index3/p4; §§5–6, index5/p6. Original operations report, analysis and limited postflight checks. [^ref-b8c31b1c449d]: Lukas Steindorf, Ruben Castro, Riccardo Di Corato and Jose Manuel Sanchez Perez (2025). “Galileo Constellation End-of-Life Disposal: Orbit Strategy and Application to First Satellite Decommissioning”. Ninth European Conference on Space Debris, 1–4 April 2025. §2.2, PDF index3/physical p4; §3, indices4–5/pp5–6; §4.1, Table3 and Figures6–7, indices6–7/pp7–8; §4.2, index7/p8. Original flight-campaign report with numerical design and forward propagation; Δa=701.4 km is a mean semimajor-axis offset.