Space Traffic Management LEO: Who Controls Low Earth Orbit and How

Ask five people in the satellite industry who is “in charge” of space traffic management LEO operations and, as of 2026, you will get five different answers — a regulator, a defense agency, a private operator, an industry consortium, or, more candidly, no one. That ambiguity is not an oversight. It reflects a genuine institutional vacuum: no single body has the legal authority, the complete tracking data, and the operational mandate to direct traffic in low Earth orbit the way an air traffic controller directs aircraft.

On this page

• The Space Traffic Management LEO Problem: No Single Authority
• Conjunction Screening: From 18th SDS to Commercial SSA
• TraCSS: The U.S. Attempt at Civilian Space Traffic Management LEO Coordination
• The Informal Inter-Operator Coordination Gap
• Autonomous Avoidance as De Facto Space Traffic Management
• Who Actually Has Authority? The Licensing Patchwork
• The Institutional Vacuum and the Path Forward
• Industry Implications
• What to Watch

The Space Traffic Management LEO Problem: No Single Authority

The core structural problem is jurisdictional fragmentation. Launch and spectrum licensing runs through national regulators — the FCC and NOAA’s Office of Commercial Remote Sensing in the U.S., equivalent bodies in the UK, EU member states, and elsewhere — while orbital tracking and conjunction assessment have historically run through a single military system, the 18th Space Defense Squadron, which was never designed as a civil traffic-control function.

Why This Matters More in 2026 Than in 2020

The gap was tolerable when LEO held a few thousand active payloads tracked by a handful of operators. [INTERNAL LINK: active LEO payload count → flagship LEO census report] shows the constellation population has grown enough that manual, case-by-case coordination between operators no longer scales. Conjunction alerts that were once rare exceptions are now routine background noise for any large fleet operator, and the institutions built for the earlier, sparser environment have not kept pace.

Conjunction Screening: From 18th SDS to Commercial SSA

Conjunction Data Messages (CDMs) — the standardized alerts warning two objects may pass dangerously close — have historically originated from the 18th Space Defense Squadron’s global sensor network, screening the U.S. government’s catalog against itself and issuing warnings to registered operators. That system was built for a catalog numbering in the tens of thousands of tracked objects, not the denser, faster-refreshing picture today’s largest constellations require.

Alert Fatigue and the Fusion Problem

Industry reporting in 2026 describes “alert fatigue” as a growing operational risk in its own right: when operators receive large volumes of low-probability conjunction warnings from multiple uncoordinated sources, the signal-to-noise ratio degrades and genuinely high-risk events can be deprioritized. The Space Data Association’s ongoing platform upgrade — a contract with Spanish technology provider GMV announced in late 2025 — is explicitly aimed at fusing multiple data sources into unified conjunction messages rather than leaving operators to reconcile competing feeds manually.

TraCSS: The U.S. Attempt at Civilian Space Traffic Management LEO Coordination

The clearest institutional response to date is TraCSS, the Traffic Coordination System for Space, built by NOAA’s Office of Space Commerce under the mandate of Space Policy Directive-3 to move basic civil SSA data and conjunction warnings out of military hands and into a dedicated civilian system. The intent is to relieve the 18th Space Defense Squadron of a workload that was never core to its national-security mission and give commercial operators a purpose-built civil interface.

Voluntary by Design — For Now

Critically, TraCSS participation remains voluntary and the system provides warning data rather than binding maneuver directives. It is a coordination utility, not a traffic-control authority. The Office of Space Commerce has also begun weighing user-fee options for the service, according to trade press coverage, which raises questions about how a fee-funded civil system scales sustainably as constellation counts grow into the tens of thousands. International onboarding began in mid-2026, but coverage of non-U.S.-licensed operators — including large state-affiliated constellations — remains a known gap.

The Informal Inter-Operator Coordination Gap

Beneath the government-level systems sits a layer of direct, largely informal operator-to-operator coordination — bilateral emails, shared ephemeris data, and ad hoc agreements on who maneuvers when two active satellites from different fleets converge. The Space Data Association, founded by major satellite operators over a decade ago, formalizes some of this exchange, but membership is voluntary and its historic focus skewed toward GEO communications satellites rather than the high-volume, high-velocity conjunction environment that proliferated LEO constellations now generate.

Right-of-Way Ambiguity

Aviation resolved this problem with codified right-of-way rules decades ago. Orbital mechanics makes a direct analogy imperfect — relative velocities and orbital regimes vary far more than in aviation — but the absence of any agreed default (e.g., “the less-maneuverable or higher-mass-density object has priority”) means that in a genuine close approach between two commercial operators today, negotiation happens in real time, under time pressure, without a settled precedent to fall back on.

Autonomous Avoidance as De Facto Space Traffic Management

In the absence of a binding external authority, the largest constellation operators have effectively become the space traffic management system for their own fleets — and, by extension, for a meaningful share of all active LEO objects. SpaceX’s Stargaze system, unveiled in February 2026, illustrates the trend most starkly: the company says it uses star trackers across the Starlink fleet to observe roughly 30 million transits per day, generating conjunction data messages at a frequency and latency the company describes as unmatched by traditional government screening, with results delivered within minutes rather than hours.

The Competitive-Neutrality Question

This is operationally effective — fewer close approaches go unresolved when one actor holds both the densest sensor network and the largest maneuverable fleet — but it raises a structural concern that regulators and competitors have both flagged: an operator that is simultaneously a fleet owner, a de facto SSA provider, and (via CRADA arrangements) a government data partner sits in a position to shape STM norms in ways smaller or newer entrants cannot match. Whether that concentration is a temporary bridge until civil systems like TraCSS mature, or a durable feature of how LEO traffic gets managed, is one of the more consequential open questions in orbital governance heading into the back half of the decade.

A Concrete Example: Cross-Fleet Conjunctions

Consider a routine but illustrative scenario now occurring with increasing frequency as constellations from different operators share similar altitude bands: an active Starlink satellite and an active satellite from a competing broadband fleet — [INTERNAL LINK: Kuiper deployment status → Kuiper constellation profile] or a OneWeb/Eutelsat spacecraft — receive a CDM flagging elevated collision probability. Both satellites are maneuverable, both operators have their own screening systems, and neither is obligated by any binding rule to yield. In practice, operators typically resolve these through direct contact, often mediated by shared membership in the Space Data Association, with the more risk-averse or more maneuverable operator usually moving first. That “usually” is precisely the gap: it is convention, not codified obligation, and conventions can break down under time pressure or when a newer entrant unfamiliar with informal industry norms is involved.

Who Actually Has Authority? The Licensing Patchwork

Legal authority over any given satellite still runs through the licensing state under the Outer Space Treaty’s Article VI framework, meaning enforcement power is scattered across dozens of national regulators rather than concentrated anywhere with global reach. The FCC licenses U.S. operators and has increasingly attached orbital-debris and collision-avoidance conditions to license grants, but its authority stops at the U.S. border; it cannot compel a non-U.S.-licensed constellation to maneuver.

The ITU coordinates spectrum and orbital-slot filings but has no operational STM mandate — it was built for frequency interference disputes, not collision avoidance. The UN Committee on the Peaceful Uses of Outer Space (COPUOS) has produced long-term sustainability guidelines that are explicitly non-binding. The result, as multiple 2026 policy analyses have noted, is that STM authority today is best described not as a system but as a set of independently operating, jurisdictionally limited pieces that happen to interoperate reasonably well only because the largest actors have incentive to cooperate voluntarily.

Entity	Role	Authority Type	2026 Status
18th Space Defense Squadron (USSF)	Legacy conjunction screening, global catalog	Military; advisory to civil operators	Transitioning civil workload to TraCSS
TraCSS (NOAA / Office of Space Commerce)	Civil SSA data, conjunction warnings	Voluntary civil platform	52 pilot users, 2 national govt. accounts, ~11,125 satellites covered (June 2026)
FCC	U.S. launch/spectrum licensing, debris-mitigation conditions	Binding, U.S.-jurisdiction only	Attaching stricter avoidance conditions to new licenses
Space Data Association	Operator-to-operator conjunction data sharing	Voluntary industry consortium	Platform upgrade underway (GMV contract, late 2025)
Individual operators (e.g., SpaceX Stargaze)	Autonomous fleet-level collision avoidance	Private, self-governed	~30M transits/day screened; de facto STM for own fleet
ITU / UN COPUOS	Spectrum coordination; sustainability guidelines	International, largely non-binding	No operational STM enforcement mandate

The Institutional Vacuum and the Path Forward

Every credible near-term fix to space traffic management LEO gaps is incremental rather than structural. TraCSS is expanding its user base and beginning international onboarding, but it remains fee-uncertain and non-binding. The Space Data Association’s data-fusion upgrade should reduce alert fatigue but does not resolve right-of-way ambiguity between competing operators. Commercial SSA providers add tracking redundancy but also add another set of feeds operators must reconcile.

The most plausible medium-term outcome is not a single global STM authority — treaty-level international agreement on binding orbital traffic control remains politically distant — but a tighter federation of the pieces that already exist: TraCSS as the default civil data hub, FCC and equivalent national regulators attaching harder avoidance obligations to licenses, and industry-standard data formats (building on existing CDM conventions) making multi-source conjunction data easier to fuse automatically. [INTERNAL LINK: FCC orbital debris rule updates → regulatory tracker] and [EXTERNAL LINK: Space Policy Directive-3 text → whitehouse.gov archive] remain the two documents most likely to shape how binding this framework becomes over the next two to three years.

Until then, the honest answer to “who controls LEO” is: whoever has the densest sensor network and the largest maneuverable fleet, operating within a loose, largely voluntary set of norms that the rest of the industry has little practical ability to override.

Frequently Asked Questions

What is space traffic management in LEO and why is it different from air traffic control?

Space traffic management (STM) refers to the tracking, conjunction screening, and coordination of maneuvers needed to prevent in-orbit collisions. Unlike air traffic control, no single authority has binding power to direct spacecraft; coordination in LEO instead runs through a mix of voluntary government platforms like TraCSS, industry consortia like the Space Data Association, and individual operators’ own autonomous avoidance systems.

Who currently issues conjunction data messages (CDMs) for LEO satellites?

CDMs historically originate from the U.S. Space Force’s 18th Space Defense Squadron, which screens the government’s tracking catalog and alerts registered operators. Commercial SSA providers such as LeoLabs, and increasingly individual operators’ own systems like SpaceX’s Stargaze, now generate independent CDMs as well, adding redundancy but also requiring operators to reconcile multiple feeds.

Is TraCSS mandatory for satellite operators?

No. TraCSS, built by NOAA’s Office of Space Commerce, is a voluntary civil platform. As of June 2026 it counted 52 pilot users and 2 national government accounts (the UK and Australia) covering more than 11,125 satellites, but operators are not legally required to join or to follow its warnings.

Does any international body have authority to order a satellite to maneuver?

No. The ITU coordinates spectrum and orbital-slot filings, and UN COPUOS has issued non-binding long-term sustainability guidelines, but neither has operational authority to compel a maneuver. Enforcement power sits with national licensing regulators, such as the FCC for U.S.-licensed operators, and stops at national jurisdictional boundaries.

How does SpaceX’s Stargaze system relate to broader space traffic management?

Stargaze, unveiled in February 2026, is SpaceX’s proprietary optical tracking and conjunction-screening system, reportedly monitoring roughly 30 million transits per day across the Starlink fleet. It functions as de facto space traffic management for the largest single LEO constellation, operating largely independently of — though increasingly integrated with, via CRADA arrangements — government systems like TraCSS.