· deep dive · 13 min read
The Civilian Space Traffic System America Almost Didn't Build
For nearly two decades, the U.S. Air Force and Space Force have been the world's unofficial civilian space traffic control system. The Department of Commerce's Traffic Coordination System for Space (TraCSS) is now taking over that job for commercial satellite operators - in stages, against persistent congressional pressure to kill the program, and with Department of Defense advocates pushing to make it happen before it is too late.

TraCSS as a civilian space traffic control system
The Case For TraCSS
- Releases the U.S. Space Force from civilian conjunction screening, freeing military resources for warfighting missions
- Creates a dedicated civil agency with full-time focus on commercial operator needs
- Supports international coordination with civilian counterparts in Europe, Japan, and other space-faring nations
- Enables commercial SSA industry to develop and sell improved data products to a clearly defined customer
- Separates decision-making about collision risk from the national security establishment that has historically prioritized military needs
The Case Against
- Slower rollout than originally planned due to political and funding delays
- Data quality depends on unclassified sources, which provide less accurate tracking than classified military sensors
- Commercial operators accustomed to free military-provided conjunction screening are now facing subscription-style relationships
- Some functions (high-accuracy tracking of deep-space objects) still require military cooperation
- Political vulnerability: new administrations can defund or restructure the program
As of spring 2026, the Office of Space Commerce - housed within the National Oceanic and Atmospheric Administration inside the U.S. Department of Commerce - is in the middle of taking over the job of providing conjunction assessment messages and space traffic coordination services to commercial satellite operators. The Traffic Coordination System for Space, known as TraCSS, has been in planning since 2018 and under active development since 2020. Its first conjunction data messages went out to a small set of commercial operators in September 2024 through the existing Space-Track.org interface, and the service has been growing in beta ever since. A formal production release - the milestone at which the U.S. military would stop routinely providing the same services - is anticipated later in 2026.
The transition has been deliberately slow. There has been no single handover day, no congressional hearing marking the change, no press conference. Operators are being phased onto TraCSS in waves while the U.S. Space Force’s 19th Space Defense Squadron continues to run the existing service in parallel. The messages contain the same essential information - predicted close approach events between active satellites and other tracked objects - but they are now generated, increasingly, by a civilian agency reporting to the Commerce Department rather than exclusively by a military unit reporting to the Space Force.
This is the largest change in how the United States manages the commercial space environment since the Air Force began providing routine conjunction screening in 2009. Getting it this far has taken a combination of persistent policy advocacy, military leadership willing to push for the transition, and a bipartisan core of congressional supporters to get it done against the opposition of members who wanted to kill the Office of Space Commerce entirely.
Why the Air Force Was Doing This At All
When the U.S. military began providing space surveillance data to civilian users, it was not by design. The Space Surveillance Network, developed during the Cold War to track Soviet satellites and warn of ICBM launches, maintained a catalog of orbital objects that was not classified in its raw observational sense. Public data on orbital objects had been released through various channels since the 1980s, though the fidelity was deliberately degraded to avoid revealing U.S. military tracking capabilities.
After the Iridium-Cosmos collision in February 2009, which produced more than 2,000 pieces of trackable debris in one of the most heavily populated orbital bands, the Air Force substantially expanded its conjunction screening service. What was then the 18th Space Control Squadron - the lineage that runs through today’s 18th and 19th Space Defense Squadrons - began providing routine conjunction data messages (CDMs) to all active satellite operators through Space-Track.org, not just U.S. government ones. The service was free, high-quality, and indispensable for commercial operators who had no alternative source of trajectory data.
The service also consumed significant resources. The catalog of tracked objects has grown into the tens of thousands and the daily volume of CDMs runs into the tens of thousands as well, much of it generated on behalf of commercial operators - many of them foreign. The administrative overhead of supporting that user base had become a significant distraction from the squadron’s primary military mission.
The first Trump administration’s Space Policy Directive-3, issued in June 2018, formally directed the Department of Commerce to assume this civilian role. The direction has been bipartisan in practice: the Biden administration carried the program through development, and the second Trump administration has continued operating it, though pace and funding have been contested in every budget cycle.
What TraCSS Actually Does
The services TraCSS is currently delivering to its beta users are narrower than the eventual scope, but they cover the core of what commercial operators need.
The first and most important is conjunction data message distribution. TraCSS screens active commercial satellites against the orbital catalog and pushes CDMs out to operators for predicted close approaches. During the transition the messages are being delivered through the existing Space-Track.org interface so that operators do not have to rebuild ingestion pipelines.
The second is on-demand conjunction screening, which lets an operator request an assessment for a specific satellite or planned trajectory rather than waiting on the routine batch.
The third is on-demand maneuver screening - the same idea applied to a planned maneuver, so an operator can check whether a contemplated burn would resolve one conjunction at the cost of creating another.
Beyond these baseline services, the Office of Space Commerce has been building out a Presence capability that allows operators to submit their own ephemerides and planned maneuvers as authoritative input. That improves the accuracy of conjunction predictions relative to the older model, where the military had to infer operator intent from observation alone. A more ambitious coordination layer - intended to help operators negotiate who maneuvers when two spacecraft are on a close-approach trajectory - is on the published roadmap but is not yet a production service.
TraCSS is not a replacement for the Space Surveillance Network. The underlying observation data - the radars and optical telescopes that actually track objects in space - remains a U.S. Space Force responsibility, and the authoritative space object catalog stays in military hands. TraCSS consumes that catalog as an input and produces its own operator-facing products. Commercial data from providers such as LeoLabs, Slingshot, ExoAnalytic, and Kayhan Space is being layered in over time through pathfinder efforts like the COLA Gap initiative, with the goal of improving prediction quality for objects below the catalog’s detection threshold.
The Political Fight
The Office of Space Commerce has been a target of congressional opposition almost since its creation. A recurring pattern has emerged in Senate appropriations: members of the Commerce, Science, and Transportation subcommittee push to eliminate or sharply cut the office in each budget cycle, citing concerns that its mission overlaps with existing Defense Department responsibilities or that its staffing is inadequate for the work being requested.
Several appropriations cycles have proposed zeroing the office out entirely; in each case, House action and pressure from the commercial space industry have pulled funding back up. The cumulative effect of these fights has been to slow the schedule. TraCSS originally targeted an operational capability date well before 2026; the program slipped year over year as funding was restored late in each cycle and as requirements were renegotiated. The September 2024 initial release and the still-pending production date are the visible consequences of that political churn.
The saving grace has been sustained advocacy from within DoD itself. Successive Chiefs of Space Operations - General John Raymond and his successor General Chance Saltzman - testified publicly that the Space Force wanted the Commerce Department to take over commercial conjunction services. U.S. Space Command leadership has added another layer of support, emphasizing that TraCSS lets the warfighting command focus on warfighting rather than on commercial bookkeeping.
On the civilian side, Office of Space Commerce leadership under Richard DalBello and his successor Jason Kim built coalitions with commercial operators and with industry groups like the Commercial SSA Coalition. The willingness of the commercial sector to publicly endorse TraCSS - and to make the case that the alternative was an under-resourced military service trying to support a mission it had been asking to shed - has been critical to maintaining political support across administrations.
The Technical Rollout
TraCSS has not been delivered as a single release. The Office of Space Commerce has followed a staged deployment pattern that adds capability over time while the military continues to provide the same services in parallel.
Space Policy Directive-3
First Trump administration directs the Department of Commerce to take on the civilian space traffic management role.
Initial release
TraCSS begins distributing conjunction data messages to a small set of beta users through the existing Space-Track.org interface.
First Data and Information Policy
OSC publishes the first official TraCSS Data and Information Policy and User Agreement.
SpaceX joins beta
SpaceX becomes the tenth beta user, alongside operators including Iridium, OneWeb, Maxar, Planet, Intelsat, and Amazon Kuiper.
COLA Gap Pathfinder expands
Kayhan Space added to the COLA Gap Pathfinder initiative as commercial SSA providers are layered into the data picture.
Updated technical specs
OSC publishes updated technical specification documents for the data products and interfaces.
Waitlist opens
Waitlist opens for additional satellite operators; 17 organizations are listed as pilot users.
Anticipated production release
Target for the milestone at which the U.S. military stops routinely providing the same spaceflight safety services that TraCSS offers.
The gradual rollout has allowed the Office of Space Commerce to discover and fix issues without disrupting critical safety services. Early iterations exposed compatibility issues with operator ingestion software and gaps in throughput compared to the existing military service, prompting format work with industry groups and additional investment in compute capacity. Throughout the transition the military has continued to run the old service in parallel through Space-Track.org, so operators have not lost access to timely conjunction data.
The International Piece
One of the strongest arguments for moving civilian space traffic management to Commerce has always been international. The European Union’s EU SST, along with national agencies in Japan, South Korea, Canada, and other space-faring countries, have been developing their own space surveillance capabilities. Coordinating with these systems at the civilian level is straightforward. Coordinating with them at the military level is awkward, slow, and frequently blocked by intelligence-sharing restrictions.
The most concrete partnership to date is between TraCSS and EU SST, which have run joint studies on data standards, notification thresholds, and service scope. The Office of Space Commerce has also published a “Vision for Global SSA Coordination” describing how a network of national civilian providers might interoperate. Additional bilateral arrangements with other national agencies are part of the program’s stated direction, but the public catalog of formal agreements is still small.
A civil-to-civil network of space situational awareness, analogous to the civil aviation network that governs Earth-based aircraft coordination, is becoming a more realistic possibility as more countries stand up civilian counterparts. An “Aeronautical Information Manual of the sky” is the long-term goal that program advocates point to.
What TraCSS Doesn’t Do
TraCSS is not a global authority on space traffic. It is a U.S. civilian agency that provides services to operators who choose to receive them, as the Office of Space Commerce itself emphasizes - the system is “globally available free of charge to operators,” and it is provided “as is” without warranties. TraCSS has no legal authority to compel a foreign satellite operator to maneuver or to accept its conjunction analyses. The ITU, the UN Office for Outer Space Affairs, and the Committee on the Peaceful Uses of Outer Space all maintain overlapping jurisdictions over various aspects of space traffic, but none of them has operational authority either.
The point analysts at the Secure World Foundation and elsewhere have made for years still applies: TraCSS is a coordination system, not a control system. It tells operators about risks. It does not tell them what to do about those risks.
The operational authority in space traffic management ultimately rests with individual operators and their national licensing authorities. TraCSS provides the information needed to make good decisions. It cannot enforce those decisions. And it cannot compel China, Russia, or any other non-participating nation to share data or accept TraCSS recommendations.
This limitation is why ongoing work in international space traffic coordination is focused on voluntary norms and confidence-building measures rather than on enforceable rules. The 2023 U.S. declaration against destructive direct-ascent anti-satellite testing, the UN General Assembly’s 2022 resolution on the same topic, and the evolving discussions at the UN Working Group on Reducing Space Threats are all attempts to establish norms that would make TraCSS-style cooperative behavior easier even without legal authority.
What It Costs
TraCSS’s appropriation runs in the tens of millions of dollars per year, modest by federal program standards and modest compared to what its services are worth to commercial operators. The cost of a single Iridium-Cosmos-class collision - measured in new debris, new tracking work, and lost service - would exceed TraCSS’s lifetime budget many times over.
The bigger cost is what could have happened without TraCSS. Had the Office of Space Commerce been defunded as some members of Congress have proposed, commercial operators would have faced a gap in conjunction screening services at exactly the moment when the global satellite population is growing most rapidly. Military commanders have publicly said they cannot continue providing commercial services at current volumes indefinitely. A commercial-only alternative - where operators would pay LeoLabs, Slingshot, ExoAnalytic, Kayhan Space, or other SSA vendors for conjunction data - would create economic gatekeeping for small operators and startups that cannot easily afford subscription services.
What Comes Next
The 2026 production release is a milestone on the road map, not an endpoint. The Office of Space Commerce has signaled several directions for the next phase of work:
A coordination layer that goes beyond simple alerts - helping operators negotiate who maneuvers when two spacecraft are on a close-approach trajectory - is on the published roadmap, with pilots expected to precede a full production capability. The intent is to reduce duplicate burns and unnecessary fuel use by giving operators a shared place to settle disagreements.
Integration with commercial SSA providers is set to deepen. The COLA Gap Pathfinder is the visible example today, but the longer-term direction is to ingest more sources so that conjunction predictions improve for objects below the military catalog’s detection threshold.
Integration with foreign civilian counterparts is also expected to expand. EU SST is the established partnership; additional bilateral arrangements with other national agencies are part of the program’s stated direction.
Why This Matters Long-Term
The significance of TraCSS is not primarily technical. The technical capability to provide conjunction screening has existed for years, and the military has been doing it at high quality. The significance is institutional.
By establishing a permanent civilian institution for space traffic management, the United States is signaling that the space environment is now a civilian infrastructure, not an exclusively military domain. That is a fundamental shift in how space policy is conceived. It parallels what happened with civilian aviation in the 1930s through 1950s, when the country slowly separated civilian aviation regulation from military control and eventually established the Federal Aviation Administration. The organizational history of the FAA has been far from smooth, and TraCSS is likely to have a similarly bumpy evolution. But the creation of a dedicated civilian agency is a precondition for any future regulatory, coordination, or norm-building activity.
The commercial satellite industry is now global, growing, and commercially mature. It needs a civilian regulatory and service counterpart. TraCSS is on its way to becoming that counterpart for the United States and its partners. It is imperfect, underfunded, and politically vulnerable. But it exists, it is delivering services to a growing list of operators, and the production release that finally retires the parallel military service is finally in sight.
References(6)
- Space Policy Directive-3 - National Space Traffic Management Policy, June 2018
- Office of Space Commerce - Traffic Coordination System for Space (TraCSS)
- TraCSS Frequently Asked Questions - Office of Space Commerce
- Commercial SSA Coalition
- U.S. Government Accountability Office Report GAO-24-106482 on Space Traffic Management
- Secure World Foundation - Global Space Situational Awareness Activities Report
Theodore Kruczek