Article reader Listen + reading controls
Article reader
Preparing the reader…
Reading settings
Space traffic coordination needs an evidence market, not another data feed¶
More orbital data does not automatically produce a better collision warning.
A useful warning depends on the quality and timing of observations, the model used to estimate an object's orbit, the uncertainty attached to that estimate, the way several sources are combined, and whether a satellite operator can act on the result. Two providers can observe the same object and produce different answers without either behaving irrationally.
That is what made a small 2024 procurement by the Office of Space Commerce (OSC) more interesting than the original announcement suggested. OSC, part of the National Oceanic and Atmospheric Administration (NOAA), hired Kayhan Space and SpaceNav to evaluate the accuracy, consistency, and quality of commercial space situational awareness (SSA) products created by three other companies. The work supported a limited pathfinder for the emerging Traffic Coordination System for Space (TraCSS).
The government was not only buying data. It was buying an independent way to learn which data and services were useful, under which conditions, and according to which evidence.
Revised and substantially expanded July 17, 2026, using OSC's subsequently published pathfinder results and TraCSS development record.
A pathfinder should retire uncertainty¶
The Consolidated Pathfinder focused on low Earth orbit (LEO). OSC placed orders with COMSPOC, LeoLabs, and Slingshot Aerospace for commercial data and orbital products, then used Kayhan Space and SpaceNav as data-quality monitors. The five-company effort represented about $11.5 million in orders.
This structure separated production from evaluation. That is an important acquisition choice. When the same vendor supplies a data product, defines the metric, and explains the result, buyers can confuse a persuasive performance narrative with independent evidence.
The purpose of a pathfinder is not to prove that a favored architecture works. It is to reduce consequential uncertainty before the government commits to an operating model. For TraCSS, that included questions about commercial tracking, orbit determination, conjunction assessment, performance metrics, contractual deliverables, data rights, and integration with government sources.
OSC later published the results rather than declaring generic success. The October 2024 report found improvements for some objects but said the overall reduction in uncertainty—and therefore the improvement in the actionability of conjunction messages—was limited.
That is a valuable result. A pathfinder that exposes the boundary of commercial benefit has done more for the mission than a demonstration designed to produce an unqualified success story.
Data quality is part of the operational product¶
Space traffic coordination depends on estimates. Sensors observe an object at particular times and geometries. Orbit-determination methods use those observations to estimate state and uncertainty. Conjunction assessment projects possible close approaches. Operators then decide whether the evidence justifies maneuvering a spacecraft, accepting risk, or coordinating with another operator.
Every stage can add or reduce uncertainty.
For that reason, “data quality” cannot be a single score. It includes at least:
- timeliness and coverage of observations;
- accuracy, precision, and calibration;
- consistency across sources and time;
- completeness of metadata and provenance;
- uncertainty representation;
- performance by orbital regime, object type, and observation geometry;
- resilience when a source is unavailable or degraded; and
- usefulness of the final product for an operator's decision.
A technically accurate observation delivered too late may have little operational value. A precise estimate with poorly characterized uncertainty can create unwarranted confidence. A product that performs well for common objects may fail on the unusual cases that produce the greatest concern.
The quality monitor's job is therefore not simply to rank vendors. It is to make performance legible enough for the government and operators to decide when and how a source should be used.
Independence has to be designed¶
Using separate firms for evaluation is a good start, but independence requires more than organizational separation.
Evaluators need agreed reference data, access to relevant source metadata, documented methods, reproducible calculations, and freedom to publish unfavorable findings. Metrics should be selected before results are known and should represent the operational conditions the service will face. Providers need a fair process for explaining anomalies without gaining control over the evaluation.
The government also needs to manage evaluator incentives. A quality-monitoring firm may sell adjacent operational services or become a future data provider. Transparent methods, multiple evaluators, conflict disclosures, and government-owned test artifacts help preserve credibility.
This is not unique to space. Any public system that assembles commercial data, models, or artificial intelligence services needs an assurance layer capable of challenging supplier claims without becoming another opaque supplier.
Commercial integration is an architecture, not a purchase¶
The U.S. Government Accountability Office (GAO) previously found that the Department of Defense (DoD) lacked a regular process for identifying and evaluating commercial SSA capabilities. Its 2023 report also noted that a government data repository had not yet been integrated into the daily operational systems used by personnel monitoring space objects.
Those findings describe two different problems. One is market access: can government repeatedly discover and evaluate new providers? The other is operational integration: can useful commercial data actually reach the systems and decisions that need it?
A successful TraCSS market needs both. The architecture should support multiple providers, common interfaces, data lineage, performance monitoring, and the ability to replace or supplement a source without rebuilding the service. Procurement should make on-ramps and off-ramps normal. Government should preserve the right to combine data, inspect quality, reproduce consequential outputs, and continue the mission if a vendor exits.
OSC's later request for information on a multi-vendor contract continued in that direction. It sought flexible acquisition of observations, orbit determination, conjunction and risk assessment, space weather, analytics, and data-quality monitoring. The list recognizes that the market contains complementary layers, not one monolithic “SSA solution.”
Open data and commercial value can coexist¶
Public provision of basic space-safety information can strengthen, rather than eliminate, a commercial market.
TraCSS's data policy favors broad public access to government and owner-operator information with limited exceptions. Open foundational data gives researchers and companies material for testing, validation, and new services. Commercial providers can compete on sensor coverage, latency, analytics, decision support, and specialized products rather than on exclusive control of a public safety baseline.
The boundary must be explicit. Government needs enough rights to provide a dependable public service, evaluate performance, preserve records, and change suppliers. Vendors need a credible market for differentiated capability. Satellite operators need clear rules for how their data will be used and protected. Those interests are compatible when the data architecture and contracts are designed together.
Measure decision improvement¶
A pathfinder can produce many technical metrics without answering the operational question.
TraCSS should ultimately be evaluated by whether it improves spaceflight-safety decisions. Useful measures include:
- reduction in false or non-actionable alerts;
- change in uncertainty for cases where additional observations were requested;
- time from new observation to updated warning;
- consistency across independent orbit and conjunction products;
- operator understanding and response time;
- service continuity when a commercial source fails;
- performance across orbital regimes and difficult object classes; and
- the cost of achieving a meaningful improvement relative to government-only and alternative commercial approaches.
Not every improvement needs to produce a maneuver. Better evidence may help an operator avoid an unnecessary maneuver, coordinate earlier, or understand that uncertainty remains too high for a confident choice.
The market needs a referee¶
The 2024 orders were easy to summarize as another government partnership with commercial space firms. Their real importance was the operating model beneath them.
OSC created a limited market in which several companies produced inputs and products while other companies evaluated quality. It then published a result that included limited benefit, not only success. That is the behavior of a learning system.
As orbital activity grows, government will need more commercial capability. It will also need a stronger public capacity to define evidence, compare providers, preserve provenance, and translate technical performance into operational confidence.
The durable asset is not a particular data feed. It is a market architecture in which claims can be tested, uncertainty remains visible, and better evidence—not better marketing—earns a larger role in the mission.
Sources¶
- Office of Space Commerce, “Office of Space Commerce Places Orders for SSA Data Quality Monitoring Pathfinder” (March 5, 2024).
- Office of Space Commerce, “OSC Releases TraCSS Consolidated Pathfinder Results” (October 16, 2024).
- Office of Space Commerce, The TraCSS Consolidated Pathfinder: Leveraging Commercial Capability in LEO (2024).
- U.S. Government Accountability Office, Space Situational Awareness: DOD Should Evaluate How It Can Use Commercial Data (April 24, 2023).
- Office of Space Commerce, TraCSS Data and Information Policy and User Agreement.