
The U.S. Office of Space Commerce announced $10.1 million in commercial awards in June 2025 for work on tracking newly deployed satellites. The contracts show one answer to who pays to prevent collisions in orbit: a public agency purchases specialized data and analysis that support a wider traffic-coordination service. Satellite operators are another customer group, buying products that connect orbital observations to their own operating decisions.
The Commercial COLA Gap Pathfinder awards separated work among data providers, an orbit-determination provider, and data-quality monitors. LeoLabs, Slingshot Aerospace, Maxar Intelligence, Turion Space, and Silentium Defense supplied the data-provider group. GMV received the orbit-determination role, and SpaceNav and a.i. Solutions received data-quality monitoring roles. The purchasing structure reflects a market with several technical services between observing an object and deciding how to operate a satellite near it.
What the Customer Receives
Collision avoidance begins with information about where objects are expected to be. A satellite operator has a spacecraft to protect and an operating plan to carry out. Tracking systems observe other objects, including active spacecraft and debris. Analysis combines observations and predicted trajectories to identify encounters that merit attention, and operations teams determine an appropriate response.
A customer can purchase parts of that sequence or an integrated service. Tracking data improves the description of an object’s orbit. Screening searches for close approaches. Risk analysis evaluates an encounter. Planning software can calculate an alternative trajectory. Coordination tools connect the organizations operating the spacecraft involved. The products perform related tasks, but they provide different outputs.
NASA’s explanation of conjunction event prediction describes the process using a protected satellite and other known objects. Their predicted positions are compared over a future period. A conjunction data message, commonly shortened to CDM, records information about a potential close approach, including the time of closest approach and the predicted states of the two objects.
An ephemeris is a series of predicted positions and velocities over time. It allows a screening system to compare moving objects at corresponding times. The associated uncertainty also matters, because each predicted position represents an estimate. These data products make orbital safety a continuing information service: new observations and planned maneuvers change the trajectories being compared.
The next calculation concerns close-approach collision risk. NASA describes collision probability as the likelihood that the actual separation will be smaller than the objects’ combined size. The calculation uses the predicted trajectories and their uncertainty. Risk assessment also considers consequences, including spacecraft loss and possible debris production.
For the operator, this turns a large set of orbital predictions into events associated with its particular spacecraft. The commercial service can perform calculations repeatedly as the information changes and organize the results for the flight team. That is a recurring operating function rather than a single report delivered at launch. The customer purchases continuing support for decisions about an asset already providing a service.
Commercial Tracking and Analysis
LeoLabs markets a space traffic management service built around its radar observations, object catalog, and analysis platform. Its published capabilities include conjunction messages, integration of messages from external sources, and screening of customer-supplied ephemerides. Operators can receive data through software interfaces or examine it through the company’s platform.
The supplier’s infrastructure provides a commercial observation source that can feed an operator’s existing systems. The same observations can also support an integrated analysis product. These are different delivery arrangements: one customer may maintain its own analysis team and purchase data, while another uses the provider’s calculations and interface. The connection to the customer’s operations determines which portion of the service is purchased.
LeoLabs also describes launch and operations support that includes locating new payloads, tracking spacecraft, and providing collision alerts. The post-launch task connects directly to the Office of Space Commerce’s pathfinder. After deployment, observations help associate a tracked object with the newly launched satellite and establish its trajectory. That information supports the transition into routine mission operations.
Launch support and continuing flight support can serve the same spacecraft at different stages. Early operations involve identifying the deployed vehicle and establishing its orbit. Routine operations involve maintaining an updated trajectory and evaluating encounters. A commercial provider can offer both services through the same underlying observation and processing infrastructure, with different work performed for each stage.
Software Connected to a Specific Satellite
OKAPI Orbits’ Aether documentation distinguishes risk monitoring from collision-avoidance planning. Its system imports conjunction messages, groups them into events, and uses customer-defined spacecraft information in its analysis. The documented inputs include spacecraft dimensions, mass, propulsion information, and accepted risk levels.
The planning service calculates maneuver options using the satellite’s definition and the selected avoidance strategy. It also screens a proposed maneuver against other objects. This connects the warning to an action the spacecraft can perform. The commercial product is tailored through configuration: the same software serves different missions, but each mission supplies its own physical characteristics and operating settings.
That connection explains why an operator might purchase specialized software even when it already receives orbital alerts. A flight team works with a particular propulsion system, spacecraft orientation, mission schedule, and command process. A planning tool translates an encounter into candidate actions within that environment. Its output enters the operator’s decision process alongside the other work required to carry out the mission.
A maneuver changes the spacecraft’s future path. The proposed path then becomes another trajectory to evaluate, which makes screening part of planning as well as initial monitoring. The service can compare candidate actions and preserve their associated assumptions. The operational deliverable is a trajectory and supporting analysis that the mission team can examine before commanding the spacecraft.
Coordination Between Operators
Slingshot Aerospace’s Beacon platform concentrates on coordination. It ingests conjunction messages, including those from Space-Track, and combines them with operator ephemerides and information about maneuverability. Its published features include configurable alerts, messaging between operators, and software interfaces for sharing planned maneuvers.
This is a communications and workflow product as well as an analysis interface. When an encounter involves two operating satellites, the organizations have information about their own planned activities. Sharing that information helps each team understand the other spacecraft’s expected behavior. Beacon’s described functions place those exchanges beside the encounter information used by mission teams.
The buyer in this case is purchasing an organized way to handle events across a fleet and communicate with another operator. A shared event record, a planned maneuver, and a message about that maneuver are separate pieces of operational information. Combining them reduces the number of separate systems through which the flight team manages the same encounter.
The operational distinction between an active satellite and debris also affects the service. An active spacecraft may have an operator able to share plans and change its trajectory. A debris object has no corresponding flight team. Tracking and prediction remain relevant in both cases; direct coordination applies where another operating organization can participate.
Public Services and Commercial Suppliers
The United States’ Traffic Coordination System for Space, or TraCSS, is being developed to provide basic space situational awareness information and services to civil and private operators. The Office of Space Commerce reports that owner and operator registration opened in 2026. Its program combines public-service delivery with procurement of commercial capabilities.
The office’s TraCSS service explanation states that initial services operate alongside those available through Space-Track. It also describes national government accounts that provide read-only views of information about affiliated spacecraft. The public system serves both individual operators and public institutions monitoring the spacecraft associated with their jurisdictions.
Europe’s EU SST services likewise include collision-risk assessment and avoidance alerts. Registered, approved users receive services without a charge. The service portfolio also covers reentry and fragmentation analysis. Publicly funded operational support is consequently part of the existing market structure, alongside commercial data, software, and mission-support offerings.
The existence of a free service and a commercial supplier are compatible within this structure. A public agency can purchase observations or analysis from private companies and make a basic service available to operators. An operator can also buy a separate product that fits its internal systems or supplies additional observation and planning capabilities. Payment can occur upstream of the organization receiving the final alert.
The 2025 pathfinder demonstrates this separation of roles. The government was the contracting customer, commercial firms supplied defined capabilities, and the work supported a traffic-coordination program serving other organizations. The award categories also made data quality a separately purchased function. Observations, calculated orbits, and evaluation of those products appeared as distinct contributions to the service.
The Operational Value Being Bought
New Space Economy’s coverage of orbital conditions and satellite services connects traffic management with the operating resources used by spacecraft. A collision-avoidance decision can affect a mission’s trajectory, schedule, and propulsion use. Commercial services sit within that operating process, helping the team organize the information and calculations associated with an encounter.
The relevant economic unit can be a spacecraft, a fleet, an analysis activity, or a public-service procurement. A constellation operator manages repeated encounters involving multiple vehicles. A mission with one satellite still has a continuing need for tracking and assessment. A government program may acquire data covering a broader population of objects. These customers use overlapping technical capabilities for different operating purposes.
The supplier’s product architecture can reflect those differences. An application programming interface sends data directly into mission software. A dashboard supports human review. A specialist service adds analysis or operational assistance. A sensor network produces observations used by several downstream applications. The same encounter can generate commercial activity at more than one point without each supplier performing the same task.
Documented offerings now cover the full sequence from observation to coordinated response. LeoLabs supplies tracking and alert services, OKAPI connects assessment to spacecraft-specific maneuver planning, and Slingshot provides operator coordination. Public agencies also purchase commercial capabilities for shared safety services. The Office of Space Commerce’s $10.1 million pathfinder awards put that purchasing model into practice through contracts for observations, orbit determination, and data-quality monitoring.