14.1.4 — Space Traffic Management — maturity: live

STM Standards & Interoperability

Developing and enforcing national technical standards that allow a sovereign STM system to exchange data and coordinate actions with international counterparts without ceding operational control.

Without agreed data formats, message protocols, and liability rules, every nation's tracking system is an island — and a single miscommunication can trigger a catastrophic collision.

No nation operates in an empty orbit. Every conjunction assessment, manoeuvre coordination message and catalogue update crosses borders — which means a sovereign STM authority is only as effective as the protocols it uses to speak to its neighbours. Today, the de-facto standard is whatever the US 18th Space Control Squadron publishes via Space-Track.org, supplemented by ad-hoc bilateral agreements and a patchwork of ITU Radio Regulations. A nation that has not codified its own interoperability posture simply inherits the US one, including its access conditions, classification gates and political dependencies.

The satellite stack underpinning this application is less about raw sensing and more about the data fabric connecting sensors to decisions. A sovereign tracking constellation — LEO SSA nanosats carrying RF and optical payloads — must output observation data in formats that other nations' systems can ingest (CCSDS CFDP, XTCE, CCSDS-TM), while simultaneously accepting external catalogue feeds without becoming dependent on any single provider. The standards layer governs message schemas, latency contracts, authentication, access tiers and the legal liability regime when a manoeuvre recommendation derived from foreign data causes a collision. Getting this right requires a national body with treaty-making authority, not just a technical team.

The operational outcome is that the nation can participate as an equal in multilateral STM forums — UN COPUOS, the Inter-Agency Space Debris Coordination Committee (IADC), bilateral data-sharing treaties — while retaining the unilateral ability to classify, withhold or act on its own data without external permission. It can also set the terms on which commercial operators in its licensing jurisdiction must report, respond and manoeuvre, creating a domestic regulatory lever that has real economic and strategic value as the congestion problem worsens.

What matters

ITU Radio Regulations govern frequency coordination but contain no binding orbital safety protocol; the standards gap is filled by whoever shows up first with a working system.
US Space-Track.org access agreements require accepting US government terms and can be revoked or throttled — nations without sovereign data feeds are exposed.
IADC membership requires demonstrable national capability and a named authority; standards compliance is the admission ticket to the rooms where norms are being written.
Domestic launch licensing increasingly demands SSA compliance from operators; a national standard gives the regulator teeth and generates a revenue-bearing data market.

Quick facts

Active satellites in orbit (early 2025): ~9,900 objects (2025) — ESA Space Environment Report 2025
Conjunction warnings issued per week by 18th Space Control Squadron: ~1,700 warnings/week (2024) — 18th Space Control Squadron Public Conjunction Data Message Statistics
Tracked resident space objects in public US SSN catalogue: ~27,000 objects (2025) — Space-Track.org Satellite Catalog
Estimated annual cost of collision-avoidance manoeuvres to commercial operators: $500M+ (2023) — OECD Space Economy in Figures 2023
Countries with national STM regulations or draft frameworks: 34 nations (2024) — UN-OOSA National Space Law and Policy Database

Sovereignty score: 8/10 — A nation without its own STM standards framework cedes rule-making authority to foreign governments and commercial incumbents at the precise moment orbital congestion is making those rules economically and strategically consequential.

Geopolitical leverage: the nation that defines the data schema and liability regime for its orbital neighbourhood sets the terms of market access for every foreign operator seeking a local launch licence or spectrum slot.
Access-continuity risk: dependence on a single foreign catalogue (Space-Track) creates a single point of political failure; a revoked or throttled feed during a crisis leaves the national STM authority operationally blind.
Regulatory authority: domestic satellite operators must be regulated against a national standard — without one, the regulator cannot enforce manoeuvre compliance or assign liability after a collision involving nationally licensed assets.
Treaty standing: IADC membership, COPUOS LTS implementation and bilateral data-sharing agreements all require a named national authority operating to documented standards; nations without this cannot participate as rule-setters.

Reference architecture

Payload: Standards compliance is primarily a ground and software problem; the space segment feeds it. Tracking nanosats carry RF survey payloads (150 MHz to 18 GHz) and wide-field optical sensors (10 cm aperture, 0.5–2 m GSD) outputting raw observations in CCSDS-TM frames.
Bus class: 6U–12U cubesat bus, 8–14 kg, 20–40 W payload power; form factor chosen to allow rapid constellation refresh as standards evolve and sensor miniaturisation improves.
Orbit: Sun-synchronous LEO at 450–550 km; 18-satellite walker constellation providing sub-90-minute global revisit adequate for catalogue contribution at IADC-compliant observation rates.
Ground segment: National STM operations centre with S-band TT&C at two geographically separated stations; a dedicated standards gateway node running CCSDS CFDP and XTCE translation middleware to interface with Space-Track, ESA SST and bilateral partners; SatNOGS backup on 435 MHz UHF.
Data pipeline: On-board L0 CCSDS framing → ground L1 demodulation → L2 orbit determination (sovereign OD software, not GPS-only) → L3 conjunction screening → XTCE-formatted observation records ingested into national catalogue → outbound feeds to IADC, ESA SST and bilateral partners via authenticated REST API with configurable access tiers.
End-user delivery: Standards portal for national licensing authority: compliance dashboard showing which domestic operators are reporting to national schema; API sandbox for operators to validate message formats before going live; classified channel to defence space operations centre for unredacted conjunction data.
Time to launch: Standards framework (legal instrument + API specification) in 12 months from political mandate; first two demonstrator nanosats contributing observations to national catalogue in 24 months; full 18-satellite constellation and bilateral data-sharing treaties operational in 48 months.
Caveats: The hardest constraint is legal, not technical: the national parliament or regulator must pass subordinate legislation mandating operator compliance before the standards layer has operational teeth. Sensor payloads are commercially available from European and Indian suppliers and are not subject to US ITAR if procured carefully; the OD software stack should be developed domestically or sourced from ESA member-state primes to avoid export-control lock-in.

Frequently asked

Why can't my nation simply use US Space-Track CDMs and skip building its own STM capability?

Space-Track is a US government service provided at US discretion. Data can be suspended, degraded, or withheld during geopolitical tensions. More practically, the public catalogue omits sensitive US government objects and carries covariance errors for objects poorly tracked by US sensors. A nation that owns its own tracking and data-processing infrastructure can cross-validate, catch errors, and remain operationally independent when the bilateral relationship is strained.

What is a Conjunction Data Message and why does the format matter?

A CDM (CCSDS 508.0-B-1) is a structured file describing the probability and geometry of two objects coming dangerously close. Standardising the format means any operator's flight-dynamics system can ingest it automatically without bespoke translation. If your national STM authority issues CDMs in a proprietary format, your operators must build custom parsers for every data source — multiplying costs and introducing translation errors at the worst possible moment.

How does ITU frequency coordination relate to physical collision risk?

Directly: a satellite filing an ITU coordination request must specify its orbital slots and operational frequencies. That filing process creates a de facto registry of where operators intend to put their spacecraft. When that registry is incomplete or out of date — as it increasingly is given the backlog — STM authorities lose visibility into planned orbital neighbourhoods. Spectrum coordination and orbital safety data are two sides of the same situational-awareness coin.

Is ISO 26900 actually used by satellite operators?

ISO 26900 defines shared vocabulary — terms like 'conjunction,' 'close approach,' and 'manoeuvre window' — rather than operational protocols. Its value is foundational: without agreed definitions, two agencies comparing risk thresholds may be talking past each other. Major space agencies including ESA and JAXA reference it in their STM policy documentation, but day-to-day operations depend more on CCSDS message standards and national procedures.

What happens when two commercial operators disagree about who should manoeuvre?

Currently, almost nothing formal happens. There is no binding arbitration mechanism under the Outer Space Treaty or Liability Convention for commercial-to-commercial disputes short of litigation in domestic courts. Most coordination happens ad hoc between flight-dynamics teams via email or through intermediary services like ESA's CAESAR or LeoLabs. A nation with a functioning STM authority and clear domestic regulations can at least mandate that its licensed operators follow a defined escalation procedure — protecting both parties and the broader orbital environment.

What is the difference between a TLE and an OEM, and why should a procurement officer care?

A Two-Line Element set (TLE) encodes orbital state in a compact but imprecise 1960s-era format; an Orbit Ephemeris Message (OEM, CCSDS 502.0-B-3) carries high-fidelity state vectors with full uncertainty. Procurement officers specifying tracking contracts should require OEM delivery: TLE-based conjunction screening produces false-positive rates high enough to trigger unnecessary and costly manoeuvres, while missing real risks for objects with poorly characterised drag.

Can a small nation realistically contribute to global STM standards rather than just receiving them?

Yes, and the window is open. COPUOS accepts all UN member states; ITU Working Party 4A and the CCSDS architecture is governed by agency votes, not budget size. Nations that invest in sovereign tracking infrastructure and show up to these forums with real operational data carry disproportionate influence. Early interoperability agreements — like data-sharing MoUs with ESA's Space Safety Programme — can give a smaller nation a seat at the table before norms harden around a handful of major powers.

What minimum technical capability does a nation need to participate meaningfully in STM data exchange?

At a minimum: at least one optical or radar sensor capable of tracking objects in the target orbital shell, a flight-dynamics software stack that can produce and consume CCSDS CDMs and OEMs, a national space object registry linked to the UN Register, and a designated STM authority with 24/7 operational staffing. Microsatellite-based radio-frequency monitoring (as demonstrated by HawkEye 360 and Spire) can supplement ground sensors for conjunction screening and frequency-interference detection at significantly lower capital cost.

Glossary

CDM (Conjunction Data Message): A standardised file format (CCSDS 508.0-B-1) that packages the predicted close-approach geometry, probability of collision, and uncertainty data for two orbiting objects.
OEM (Orbit Ephemeris Message): A CCSDS-standard (502.0-B-3) high-fidelity orbital state message containing time-stamped position and velocity vectors with associated uncertainty, used in place of the older TLE format for precision conjunction assessment.
TLE (Two-Line Element set): A legacy compact encoding of a satellite's orbital parameters derived from the 1960s Spacetrack format, still widely distributed but insufficiently precise for high-confidence conjunction screening.
Conjunction: An event in which two space objects approach within a defined separation threshold, triggering formal risk assessment under a nation's or operator's STM procedures.
Covariance: The statistical uncertainty envelope around a predicted orbital state; poorly calibrated covariance inflates or deflates computed collision probability and is a leading source of erroneous manoeuvre decisions.
SSN (Space Surveillance Network): The US Department of Defense global network of radars and telescopes that generates the primary public satellite catalogue at Space-Track.org; the highest-fidelity data remains classified.
ITU Coordination: The mandatory regulatory process under ITU Radio Regulations Article 22 by which a satellite operator registers frequencies and orbital parameters and resolves interference conflicts with neighbouring networks.
COPUOS (Committee on the Peaceful Uses of Outer Space): The UN body that develops international space policy and voluntary guidelines, including the 21 Long-term Sustainability of Outer Space Activities guidelines adopted in 2019.
Probability of Collision (Pc): The dimensionless figure — typically compared against a national operator's action threshold, often 1-in-1,000 to 1-in-10,000 — that drives the manoeuvre-or-hold decision for a predicted conjunction.
Launching State: Under the 1972 Liability Convention and 1967 Outer Space Treaty, the state that launches or procures the launch of a space object, and which bears international liability for damage that object causes.

References

ESA Space Environment Report 2025 — ESA's annual assessment of the orbital environment documents the accelerating growth of the satellite population and tracked debris, providing the quantitative backdrop against which STM interoperability requirements must be set. The 2025 edition records approximately 9,900 active payloads and more than 27,000 tracked objects.
CCSDS 502.0-B-3: Orbit Data Messages — Defines the Orbit Parameter Message (OPM), Orbit Mean-Elements Message (OMM), and Orbit Ephemeris Message (OEM) formats that enable interoperable high-fidelity orbital state exchange between agencies and commercial operators. The OEM in particular is increasingly required by civil STM authorities as a condition of launch licensing.
UN COPUOS Guidelines for the Long-term Sustainability of Outer Space Activities — The 21 voluntary guidelines adopted by COPUOS in 2019 represent the closest thing to an international STM policy framework currently in force. Guideline 2.2 explicitly calls on states to share space situational awareness data and to develop interoperable data formats — providing normative backing for nations seeking to embed CCSDS standards in domestic regulation.
OECD Space Economy in Figures 2023 — Provides economic sizing of the global space sector including estimates of operational cost impacts from orbital congestion. The report estimates collision-avoidance manoeuvre costs to commercial operators now exceed $500 million annually and will rise sharply as constellation density increases without improved interoperability.
ISO 26900:2012 — Space Systems: Space Traffic Management — Concepts, Terms and Definitions — Establishes agreed terminology for STM across ISO member bodies, covering concepts such as conjunction, close approach, re-entry prediction, and manoeuvre coordination. Widely referenced in national STM regulatory frameworks as foundational vocabulary to ensure that domestic regulations are internationally interpretable.
Space Policy Directive-3: National Space Traffic Management Policy — The US SPD-3 directed the Department of Commerce to assume civil STM responsibilities from the Department of Defense and called for development of open, interoperable data standards for sharing space situational awareness. Its implementation has shaped international expectations for what a national STM authority should look like and what data it should publish.
ESA Space Safety Programme — CAESAR Conjunction Assessment Service — ESA's CAESAR service provides automated CDM generation and conjunction screening for ESA-operated and partnered satellites, serving as a practical demonstration of CCSDS-standard interoperability at operational scale. The service exchanges data with the US 18th Space Control Squadron and several national STM authorities, making it a model for regional interoperability architectures.
UN-OOSA National Space Law and Policy Database — Tracks the adoption of national space legislation across UN member states, including provisions relating to satellite licensing, STM obligations, and data-sharing requirements. As of 2024, 34 nations have enacted or are drafting STM-relevant regulatory frameworks, up from fewer than 15 a decade ago — reflecting the growing political salience of interoperability.

Related applications

14.1.1 — Conjunction Assessment & Avoidance (Space Traffic Management)
14.1.2 — Catalogue Maintenance (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)