What you will learn
- How conjunction screening works from orbital data
- What collision probability and risk assessment involve
- How manoeuvre planning and coordination fit the alert workflow
- What data sources and accuracy limits operators must understand
- How to phase a platform from screening to decision support
What an orbital debris tracking platform is
A debris tracking platform screens a satellite's orbit against catalogues of tracked objects and other satellites, looking for close approaches — conjunctions — in the coming days. For each conjunction it estimates miss distance and collision probability, ranks the risk, and presents the operator with the information needed to decide whether to manoeuvre, coordinate with the other operator, or accept the risk.
Risk presentation is the product's hardest problem. Collision probabilities are small numbers with large uncertainties, and operators must decide under time pressure. The platform should show miss distance, probability, uncertainty, and how the assessment changes with new tracking data, rather than a single red or green verdict.
Core features
Uncertainty-aware risk presentation is central.
- Conjunction screening against debris and satellite catalogues
- Miss distance and collision probability estimation
- Risk ranking and alerting with uncertainty shown
- Tracking-data freshness and accuracy indicators
- Manoeuvre planning support with fuel and mission impact
- Operator coordination messaging for shared conjunctions
How it is built
Start with screening and risk display for one satellite, then add decision support.
- Data: catalogue ingestion, screening, and freshness tracking
- Screening: conjunction detection for one satellite
- Risk: probability estimation, ranking, and alerting
- Decisions: manoeuvre options, fuel impact, and coordination
- Fleet: multi-satellite screening, operator dashboards, and reporting
Technology choices
Orbital mechanics and screening libraries should come from established sources, with the platform built around them for presentation, alerting, and workflow. Reimplementing screening from scratch invites subtle errors in a safety-relevant calculation.
Data provenance must be visible. Every conjunction assessment should show which tracking data it used and how fresh that data was, because a risk figure without provenance cannot be trusted.
Challenges to plan for
False alarms are endemic. Screening produces many low-risk conjunctions, and operators learn to ignore alerts if every one demands attention. Alert thresholds and ranking should be tuned with operators, and low-risk events should be summarised rather than alarmed.
Coordination between operators is often manual. When two active satellites approach, both operators need to know the other's plan; the platform should support coordination messaging rather than assuming one side manoeuvres.
Who it is for, and its limits
Debris tracking fits satellite operators, constellation operators, and space traffic coordination services. It fits any operator whose satellites share crowded orbits.
The platform does not decide manoeuvres. Risk assessment supports the operator's decision, and manoeuvre execution stays with mission operations under the operator's procedures.
What a first release looks like
A first release should screen one satellite against the catalogue, with conjunction alerts, miss distance and probability estimates, uncertainty shown, and data freshness labelled. Manoeuvre planning support and fleet screening come later, once operators have worked real conjunctions through the alert workflow, including at least one high-uncertainty event where the probability changed sharply with new tracking data. The release must be judged on whether operators trust its risk presentation, not on how many conjunctions it lists.
Consider a conjunction with a miss distance under a kilometre and a low but uncertain collision probability. The platform shows the probability, the uncertainty range, the freshness of the tracking data, and how the assessment changed with the last data update. The operator decides to wait for the next tracking update rather than manoeuvre, and the platform records that decision with its rationale. Two days later the updated data shows the risk falling, and the event closes without a manoeuvre. If the platform had shown only a red or green verdict, that judgement would have been harder, not easier.
A mistake worth avoiding
The mistake worth avoiding is acting on a single conjunction assessment as if it were certain. Collision probabilities rest on tracking data with real uncertainty, and early assessments for a conjunction often swing sharply as new tracking arrives. An operator who manoeuvres on the first alarming figure wastes fuel and mission time; an operator who dismisses every alert as uncertain courts the opposite failure. The discipline is assessment discipline: wait for updated tracking where the timeline allows, show uncertainty and data freshness alongside every figure, and record the decision and its rationale. The platform should make patient, evidence-based decisions easy and panicked ones hard.
Frequently asked questions
What is a conjunction?
A predicted close approach between two orbiting objects within a screening window, assessed by miss distance and collision probability.
Why show uncertainty?
Because collision probabilities rest on tracking data with limited accuracy. Showing uncertainty prevents a precise-looking number from being over-trusted.
When should an operator manoeuvre?
When the assessed risk, the data quality, and the mission impact together justify it — a judgement the platform supports with options, not one it makes alone.
How do two operators coordinate?
Through coordination messaging about planned manoeuvres, so both sides do not manoeuvre into each other.
How much does it cost to build?
Cost depends on satellite count, screening frequency, and decision-support depth. Single-satellite screening is far smaller than a fleet coordination platform, so confirm with a scoped quote.