Skip to main content

Conjunction Events

Each Conjunction Event in Satcat represents a predicted close approach between tracked objects, consolidating internal and external conjunction data messages (CDMs), operator-submitted ephemeris, and derived risk metrics into a single interface. These pages provide a structured view of encounter geometry, event status, and mitigation posture.

Events are updated in near real-time as new data is received and support decision-making for risk monitoring, maneuver planning, and operator-to-operator coordination.

Updating CDMs

New CDMs are automatically generated when operators upload OPERATIONAL designation ephemeris.
Learn more about Operational data

Event Dashboard​

The Conjunction Events dashboard provides a high-level view of all conjunctions involving your assets. View active and upcoming events, or review past encounters by filtering and sorting by:

  • Admin-defined Constellations
  • RSO Smart Search
  • Probability of Collision (Pc)
  • Miss Distance (total, or RIC component)
  • Time of Closest Approach (TCA)
  • Show or hide Intra-org events

Clearing the Pc filter will load any events with null Pc values. These events can then be viewed on the dashboard by switching to the MD y-axis. Each event in the Chart, Card, or Table views link to a dedicated Conjunction Event page with tools to help manage CDM history and risk trends.

tip

Default event filters help teams prioritize events based on their organization's defined risk thresholds. Admins can configure the default values in Group Management.

Event Summary​

The Event Summary provides a structured overview of the conjunction, including asset identifiers, event severity, and current event status (active, mitigated, or archived).

Critical Metrics​

  • Pc and calculation method used
  • Miss Distance (Total RSS and range)
  • Mahalanobis Distance
  • TCA countdown and exact timestamp
  • Time since event data was Last updated

CDM Timeline​

A visual CDM timeline displays all received or generated CDM reports for the event, grouped by originator and indicating primary<>secondary data sources. Ex: KAYHAN: O/O<>HAC

Satcat classifies CDMs based on operational status to distinguish operator-validated data from testing and planning data:

  • Operational — based on uploaded OPERATIONAL ephemeris
  • Theoretical — contains non-operational designation ephemeris

Alert Banner​

Alert banners are displayed when:

  • Selected CDM data contains non-operator supplied data sources
  • Selected CDM is classified as Theoretical
  • The event TCA has passed (historical view)

Maneuver Designer​

For Pro and Enterprise subscribers, operators can generate a tradespace of COLA maneuvers for the primary asset. These tradespaces help to quickly identify and test maneuvers during high-risk events.

Maneuver tradespaces can be set to auto-generate when Satcat detects a high-risk event. Learn more about COLA automation

Encounter Geometry and Risk Details​

The CDM Information section includes:

  • 3D visualization with encounter playback and object covariance
  • Pc values with computation methods and originators
  • Hard Body Radius (HBR) values for each object
  • RSS Uncertainty components (Radial, In-track, Cross-track)
  • Relative speed, approach angle, and altitude at TCA
  • CDM metadata and download links in KVN or JSON
tip

The Mitigation Plan Comparison tool is available for viewing the risk metric deltas between the selected CDM and any uploaded or generated mitigation plan.

Operator Coordination​

Each asset's organization contact information, mitigation status, and coordination metadata is listed along with additional RSO details. For Space Traffic Coordination, Satcat surfaces operator intent and maneuver responsibility:

Additional RSO details include RSO type (payload, debris, unknown), best HBR value in Satcat databases, and an RIC breakout of covariance and robustness. More details such as orbital elements at TCA, ephemeris metadata, and OD metrics are displayed if available.

Contact Center​

Each event page contains a Contact Center, with operator-to-operator chat and displaying additional operator contact info when available. Chat messaging is available for all events, unless the other party has opted-out of Satcat coordination tools.

  • All messages are timestamped and logged
  • Contact details are drawn from the Operator Contact Information within your Group Settings

Sensor Tasking​

If enabled, operators may request Kayhan's commercial sensor network to task on the primary or secondary RSOs to update the ephemeris state. This is particularly useful for poorly tracked secondary debris objects or uncooperative RSOs.

note

Sensor tasking requires an Enterprise tier and open sensor allocation.
Learn more about Sensor Tasking

Operators can visualize event trends with 2D plots and encounter geometry analytics:

  • Pc and miss distance over time
  • Radial, in-track, and cross-track dispersions
  • B-plane, encounter plane, and sensitivity to HBR or dilution

These tools support precise maneuver planning and event behavior over time.

Explore Analytics