14.1.3 — Space Traffic Management — maturity: live

Manoeuvre Coordination

Coordinating collision-avoidance manoeuvres between satellite operators in real time, ensuring that one operator's evasive action does not create a new hazard for a third party.

When two active satellites must share the same patch of sky, somebody has to coordinate the dodge — and if that somebody is a foreign government or commercial vendor, your spacecraft fleet is hostage to their priorities.

Every conjunction event in low Earth orbit presents a coordination problem, not just a navigation one. When two operators independently decide to manoeuvre away from the same predicted close approach, their uncoordinated burns can transform a manageable risk into a catastrophic one — a phenomenon known as the 'manoeuvre dilema'. Without a trusted, authoritative intermediary that can see all actors simultaneously and broker agreed manoeuvre plans, the probability of collision can paradoxically increase the moment operators try to act.

A sovereign manoeuvre-coordination service closes that gap by operating a dedicated tracking and communication layer that ingests state vectors from national and allied catalogues, computes conjunction geometries at sub-kilometre accuracy, and issues coordinated manoeuvre advisories with clear responsibility assignments. The satellite component — a set of LEO relay and ranging microsatellites — provides time-stamped ranging crosslinks that sharpen orbital state knowledge to the 10–50 m level in real time, far better than ground-based radar alone. The ground segment runs the optimisation solver on a sovereign compute cluster, producing manoeuvre windows that satisfy all parties without exporting sensitive orbital data to a foreign intermediary.

Operationally, the outcome is a national STM authority that can compel or strongly advise domestic operators, coordinate bilaterally with allied agencies under data-sharing treaties, and maintain a contemporaneous record of which operator was responsible for which manoeuvre decision — legally critical when insurance claims or liability proceedings follow a close call. Nations that rely on a commercial or foreign provider for this function hand over both operational control and forensic evidence to a third party they cannot audit.

What matters

Uncoordinated independent manoeuvres by two operators responding to the same conjunction can increase collision probability by an order of magnitude compared with a jointly planned burn.
Manoeuvre responsibility attribution is a legal requirement under national space laws in the UK, France, and Germany, and is foundational to any future international liability framework.
Real-time crosslink ranging between constellation members can reduce radial orbit uncertainty to under 20 m, the threshold at which manoeuvre-or-hold decisions become operationally credible rather than precautionary.
A foreign-operated coordination service can delay, withhold, or condition advisory messages during a crisis, giving the provider's home state asymmetric leverage over another nation's space assets.

Quick facts

Conjunction warnings issued per week (US 18th Space Defense Squadron): ~1,600 screenings per object per week (2023) — 18th Space Defense Squadron Public Conjunction Data Message Service
Tracked resident space objects (RSOs) in public catalogue: ~27,000 objects (2024) — Space-Track.org RSO Catalogue Statistics
Average collision-avoidance manoeuvre delta-V cost for LEO satellite: 0.1 – 2 m/s per event (2023) — ESA Space Debris Office: Collision Avoidance Operations
Manoeuvre coordination messages exchanged via ESA-CCSDS compliant XML schema per year (ESA fleet): >4,000 messages (2024) — ESA Space Debris Office Annual Statistics Report
Estimated economic loss from a single major LEO collision (direct + debris cascade): $1.5 – 10B (2023) — OECD Space Economy Report: The Space Debris Problem
Starlink satellites executing autonomous avoidance manoeuvres in 2023: >50,000 manoeuvres (2023) — SpaceX Starlink Sustainability Report
ITU-recommended minimum time window for manoeuvre notification to affected operators: 72 hours (2023) — ITU-R Recommendation S.1003-2: Environmental Protection of the Geostationary Orbit

Sovereignty score: 9/10 — A nation that cannot coordinate its own operators' manoeuvres in real time without routing decisions through a foreign service has effectively outsourced both operational control and legal accountability for its orbital assets.

National space laws (e.g. France's loi relative aux opérations spatiales, UK Space Industry Act 2018) place liability for collision damage on the authorising state — that liability cannot be discharged by a foreign intermediary who holds the decision record.
During political or military crises, a foreign coordination provider may suspend service, slow advisory issuance, or condition access on information-sharing concessions, directly threatening the continuity of critical national satellite services.
Participation in manoeuvre coordination exposes precise orbital state vectors and manoeuvre-planning logic; routing this through a commercial or allied platform transfers sensitive intelligence about national constellation architecture to a counterpart with its own strategic interests.
As mega-constellations densify LEO, coordination requests will scale to thousands per week; only sovereign infrastructure with direct operator-interface authority can enforce compliance and maintain the contemporaneous manoeuvre log that international liability proceedings will require.

Reference architecture

Payload: Dual-mode RF crosslink and optical inter-satellite ranging payload; Ka-band crosslinks at 1 Gbps for telemetry relay; laser ranging unit achieving 5 m two-way range precision at up to 2000 km baseline; secondary S-band beacon for TT&C compatibility with national ground network
Bus class: 12U cubesat bus, 24 kg wet, 40 W average payload power, cold-gas propulsion with 30 m/s delta-v for station-keeping and phasing
Orbit: Sun-synchronous LEO at 550–600 km, 18-satellite walker constellation (3 planes × 6 satellites), providing continuous crosslink geometry coverage of all populated orbital shells from 400 to 1200 km; 95-minute orbital period
Ground segment: Primary mission control at a national space operations centre with X-band uplink/downlink; two geographically separated backup stations for resilience; hardened fibre interconnect to the national STM authority operations floor; no reliance on commercial ground-station-as-a-service providers for classified command traffic
Data pipeline: On-board L0 telemetry → ground L1 state vector generation → sovereign orbital-mechanics solver (SGP4/SDP4 with laser-ranging corrections) → conjunction geometry engine → manoeuvre optimisation solver on national GPU/CPU hybrid cluster → digitally signed advisory messages issued to operators via encrypted API
End-user delivery: Operator portal with authenticated access for licensed national operators; machine-readable conjunction data messages (CDM format, CCSDS 508.0) pushed via REST and AMQP; bilateral XML data-sharing feed to allied STM authorities under treaty; post-event manoeuvre responsibility log available to the national licensing authority and insurers via audited read-only interface
Time to launch: First two-satellite ranging demonstrator in 18 months from contract award; full 18-satellite coordination constellation and operational ground segment in 42 months
Caveats: Laser ranging units require export-licence scrutiny if sourced from US suppliers — European (e.g. SpaceTech GmbH, OHB) or domestic primes are preferred; the coordination solver must be hosted on sovereign compute infrastructure to prevent a foreign cloud provider from accessing operator state vectors; GEO relay variant is not required for this application as LEO crosslinks provide sufficient timeliness

Frequently asked

What exactly is 'manoeuvre coordination' and how does it differ from conjunction assessment?

Conjunction assessment identifies a potential collision risk and quantifies its probability. Manoeuvre coordination is the subsequent step: the two operators — or their delegated STM authorities — agree on who will manoeuvre, in which direction, by how much, and when, so that the proposed solution does not create a new conjunction or interfere with a third party. It is an operational dialogue, not just a data product.

Why can't a nation just rely on the US 18th Space Defense Squadron's free CDM service?

The 18th SDS service is genuinely valuable, but it is a foreign government providing data at its discretion, subject to its own operational priorities, classification decisions, and diplomatic relationships. During a geopolitical dispute or conflict, that service could be restricted or delayed. A sovereign STM capability means you hold the tracking, the screening, and the coordination authority yourself — you are not a supplicant.

What standard format do operators use to exchange manoeuvre coordination information?

The CCSDS Conjunction Data Message (CCSDS 508.0-B-1) is the dominant interoperability standard, encoding relative position, covariance matrices, and probability of collision. ESA's Space Debris Office and many commercial providers also exchange Orbit Ephemeris Messages (OEM, CCSDS 520.1-M-1) to enable independent conjunction screening before any manoeuvre is agreed.

How much does a collision avoidance manoeuvre actually cost an operator?

Direct propellant costs are modest — a typical LEO avoidance burn costs 0.1 to 2 m/s of delta-V — but the indirect costs dominate: mission interruption, payload downtime, replanning, and the propellant budget reduction that shortens satellite lifetime. Frequent manoeuvres on a five-year LEO satellite can reduce operational life by months, representing tens of millions of dollars in lost service.

Is there a legal obligation to manoeuvre if another operator asks you to?

No. Under current international law — principally the 1967 Outer Space Treaty and the 1972 Liability Convention — there is no enforceable duty to manoeuvre on another operator's request. The IADC guidelines (IADC-2002-01 Rev.7) are voluntary. This is precisely why nations building national STM authority operations benefit from domestic legislation that sets mandatory protocols for nationally licensed operators.

How does a small nation coordinate manoeuvres when it lacks its own tracking radar?

Three practical paths exist: (1) purchase commercial SSA data from providers such as LeoLabs, ExoAnalytic, or Slingshot Aerospace and use that to run your own conjunction screening; (2) become a Space-Track registered entity and access US government CDMs for your satellites; or (3) build or procure a small optical or radar tracking station. Satellize argues for path (3) as the only route to genuine independence, with paths (1) or (2) as interim measures while sovereign capability matures.

What happens when two large mega-constellation operators have a conjunction with each other — who coordinates?

Currently, bilateral agreements between operators (such as the SpaceX–Amazon Kuiper framework letters) handle this case, with each company running its own screening. ESA has published protocols for coordinating with Starlink. There is no independent neutral arbitrator. This is a structural gap that UN-OOSA and ITU are studying but have not resolved, and it represents a strong argument for a multilateral coordination regime backed by national STM authorities.

Can a nanosatellite or microsatellite constellation realistically participate in manoeuvre coordination?

Yes, but with constraints. Many CubeSats in the 1U–6U class lack propulsion entirely, making them passive collision risks that cannot manoeuvre regardless of coordination. Larger microsatellites (50–150 kg) with electric propulsion are increasingly capable of precision manoeuvres and can participate fully in CDM exchange workflows. When designing a sovereign STM capability, Satellize recommends mandating propulsion as a minimum requirement for any nationally licensed constellation asset.

Glossary

CDM (Conjunction Data Message): A standardised data file, defined by CCSDS 508.0-B-1, that quantifies the close approach between two space objects including miss distance, relative velocity, covariance uncertainty, and probability of collision.
TCA (Time of Closest Approach): The precise predicted moment at which two objects in orbit reach their minimum separation distance, used as the reference epoch for all manoeuvre planning calculations.
Pc (Probability of Collision): A dimensionless figure, typically expressed in scientific notation (e.g. 1×10⁻⁴), representing the statistical likelihood that two catalogued objects will physically collide given their predicted trajectories and positional uncertainties.
Delta-V: The change in velocity, measured in metres per second, that a spacecraft's propulsion system must provide to alter its orbit sufficiently to avoid a predicted conjunction.
RSO (Resident Space Object): Any man-made object in Earth orbit that is tracked and catalogued by a space surveillance network, including active satellites, rocket bodies, and debris fragments.
SSA (Space Situational Awareness): The comprehensive knowledge of the space environment — including positions, velocities, status, and intentions of all RSOs — required to detect, characterise, and respond to threats to space operations.
STM (Space Traffic Management): The set of technical, regulatory, and diplomatic measures used to ensure the safe and sustainable use of orbital space, encompassing tracking, conjunction assessment, manoeuvre coordination, and deorbit planning.
Covariance Matrix: A mathematical structure within a CDM that quantifies the positional uncertainty of each tracked object in three spatial dimensions, directly determining how the probability of collision is calculated.
Kessler Syndrome: A self-sustaining cascade of collisions in which debris from one collision generates sufficient new fragments to trigger further collisions, potentially rendering certain orbital altitudes unusable; named after NASA scientist Donald Kessler.
OEM (Orbit Ephemeris Message): A CCSDS-standardised file format (CCSDS 520.1-M-1) containing a time-stamped sequence of position and velocity vectors for a spacecraft, used by receiving operators to run independent conjunction screenings.

References

ESA Space Debris Office: Collision Avoidance at ESA — ESA's Space Debris Office describes its end-to-end collision avoidance workflow, from screening against the US SSN catalogue to issuing manoeuvre recommendations to satellite operators, and reports processing over 4,000 manoeuvre coordination messages annually for its fleet.
CCSDS 508.0-B-1: Conjunction Data Message — The CCSDS Blue Book defining the Conjunction Data Message format specifies all mandatory and optional fields for encoding close-approach geometry, covariance data, and probability of collision, providing the interoperability layer that makes multi-operator manoeuvre coordination technically feasible.
OECD Handbook on Measuring the Space Economy: Space Debris and Sustainability — The OECD estimates that a single significant collision in a heavily used LEO orbital band could generate economic losses ranging from $1.5 billion to over $10 billion when accounting for debris cascade effects on subsequent satellite operations and insurance markets.
UN-OOSA: Long-term Sustainability of Outer Space Activities, Guideline A.2 — Space Object Registration and Conjunction Screening — The LTS Guidelines, adopted by UN-COPUOS in 2019, include Guideline A.2 recommending that states and international organisations share orbital data to support conjunction assessment and that operators establish manoeuvre coordination contact points, a foundational requirement for any national STM regime.
ESA Annual Space Environment Report 2024 — ESA's 2024 report documents approximately 27,000 tracked objects in Earth orbit, estimates 130 million fragments below 1 mm, and notes that the rate of conjunction warnings is increasing faster than the growth of the active satellite population due to mega-constellation proliferation.
Space-Track.org: Conjunction Data Message (CDM) Subscriber Documentation — The US 18th Space Defense Squadron's public CDM service screens every catalogued object approximately 1,600 times per week and delivers conjunction warnings to over 3,000 registered operator accounts, making it the de facto global manoeuvre coordination data source — and the principal dependency risk for non-US national operators.
ITU Radio Regulations Appendix 4: Information Required in Frequency Coordination Requests — The ITU Radio Regulations, as periodically revised by World Radiocommunication Conferences, set the framework for frequency coordination but do not address dynamic spectrum conflicts arising from close-proximity manoeuvring — a regulatory gap that national STM authorities must bridge through domestic licensing conditions.
ISO 26872:2023 — Space Systems: Disposal of Satellites in LEO — ISO 26872 sets requirements for end-of-life disposal manoeuvres including the 25-year (now widely recommended 5-year) post-mission disposal rule, directly intersecting with manoeuvre coordination protocols because disposal burns must be deconflicted from other operators' conjunction avoidance windows.
SpaceX Starlink Constellation: On-Orbit Collision Avoidance Statistics 2023 — SpaceX reported executing over 50,000 autonomous collision avoidance manoeuvres for the Starlink constellation in 2023, highlighting the scale asymmetry between mega-constellation autonomous avoidance systems and the manual CDM-based coordination workflows used by most government and smaller commercial operators.

Related applications

14.1.1 — Conjunction Assessment & Avoidance (Space Traffic Management)
14.1.5 — National STM Authority Operations (Space Traffic Management)
14.2.1 — Debris Catalogue Generation (Orbital Debris Monitoring)
14.2.2 — Active Debris Removal Targeting (Orbital Debris Monitoring)
14.2.3 — Fragmentation Event Forensics (Orbital Debris Monitoring)
14.2.4 — LEO Debris Density Forecasting (Orbital Debris Monitoring)
14.2.5 — Sub-10cm Debris Sensing (Orbital Debris Monitoring)
14.3.1 — On-Orbit Inspection (Satellite Servicing)