What exactly is a rendezvous and proximity operation (RPO), and why does it matter militarily?

An RPO occurs when one spacecraft deliberately manoeuvres to within a few hundred kilometres — sometimes mere metres — of another. Militarily it matters because an RPO can precede jamming, laser dazzling, physical grappling, or kinetic kill of the target satellite. Unlike a missile launch, an RPO can be disguised as routine station-keeping, giving the victim state plausible deniability problems and limiting its escalation options.

Can't we just rely on US Space Command's public conjunction data?

US Space Command's 18th Space Defense Squadron releases Conjunction Data Messages (CDMs) for collision risk, but this data is optimised for debris avoidance, not intelligence. Positional accuracy is ±1–3 km, update cadence is typically every 8 hours, and intelligence-grade behavioural analysis of manoeuvring objects is not shared publicly or with most allied nations. A sovereign capability produces independent custody, higher update rates, and unfiltered access to raw tracks — none of which a CDM subscription provides.

What sensor types are needed for a credible sovereign RPO detection capability?

A layered architecture is most effective: ground-based electro-optical telescopes for GEO belt monitoring, ground-based phased-array radar for LEO tracking down to ~10 cm RCS, and — critically — space-based optical inspector satellites for proximity custody where ground geometry is unfavourable. Radiofrequency intelligence (RFINT) from HawkEye 360-style signal-detection payloads adds behavioural context by detecting command uplinks consistent with proximity manoeuvres.

How many inspector satellites does a sovereign programme realistically need?

For LEO custody of a nation's highest-value assets, a minimum viable constellation is 6–12 microsatellites in complementary orbital planes, providing revisit of approximately 90–120 minutes per target. Comprehensive coverage across all orbital regimes — LEO, MEO, and GEO — scales to 30+ satellites, as demonstrated by the US Space Development Agency's Tranche 1 Tracking Layer programme targeting 28 operational satellites.

Is there an international legal framework governing what you can and cannot do in response to an RPO?

Not precisely. The 1967 Outer Space Treaty prohibits weapons of mass destruction in orbit and requires assistance to astronauts but contains no prohibition on proximity operations or co-orbital manoeuvring. The COPUOS Long-term Sustainability Guidelines (A/AC.105/C.1/L.366) recommend notification of manoeuvres near other objects, but compliance is voluntary. This legal vacuum means sovereign detection capability is the only reliable protection — treaties cannot substitute for the ability to see and characterise an approach.

What is the cost range for a sovereign RPO detection programme?

A ground-segment-plus-data approach (licensing commercial SSA feeds and augmenting with national telescopes) runs approximately $30–80 million per year with no owned orbital assets. A dedicated microsatellite inspector constellation of 8–12 satellites costs roughly $200–400 million to develop and launch, with $20–40 million annual operating costs — a significant but one-time sovereign investment that eliminates ongoing vendor dependency.

How does RPO detection intersect with space indications and warning?

RPO detection is an upstream input to the broader Space Indications & Warning (SI&W) function. When an RPO track crosses behavioural thresholds — closing velocity, manoeuvre frequency, angular proximity — it generates a warning cue that feeds into national-level threat assessment and, potentially, missile warning if the RPO target is an early-warning satellite. Separating the detection function from the warning function architecturally is a mistake; they must be fused in a single sovereign operations centre.

What role does RF intelligence play in RPO detection beyond optical and radar tracking?

RF intelligence contributes two things optical sensors cannot: command-link activity (a burst of uplink traffic to a proximity satellite often precedes a manoeuvre by minutes, providing predictive warning) and payload characterisation (sensor emissions can reveal whether an approaching satellite carries a jammer, laser, or robotic arm). HawkEye 360 and similar RFINT constellations have demonstrated this at commercially available resolution; a sovereign programme should integrate an RFINT payload into its inspector satellites rather than treating RF and optical as separate programmes.

7.7.2Live

Rendezvous & Proximity Detection

Military operators watching multiple screens displaying orbital tracking data in a dimly lit control room — An engineer monitors multiple screens in a control room, tracking satellite rendezvous events to keep orbital operations safe and transparent.

Detecting Satellite Rendezvous From Orbit to Analyst

1
Surveillance Constellation
Space-based sensors track orbital object positions
2
Encrypted Downlink
Telemetry relayed via secure ground station
3
Proximity Analytics
Algorithms flag close-approach anomalies automatically
4
Threat Assessment
Analysts receive proximity alert with maneuver profile

Satellite sensors detect unexpected orbital rendezvous events and deliver encrypted proximity alerts to defence analysts instantly.

Page in the build queue

This application has its place in the atlas. The full page — short and long descriptions, what-matters bullets, sovereignty rationale, and the eight-field architecture block — is being written next.

Maturity reading: Operational systems exist with paying customers. Phase 1 built §4.1 (Maritime Intelligence) end-to-end as the depth-and-format reference. Section 4 is the next section to graduate from scaffold to full content; the rest follow on the roadmap.

Related applications

7.7.1 · Previous

Adversary Satellite Tracking

All in space warfare monitoring

7.7.3 · Next

Counterspace Threat Assessment

Bring this into your sovereign programme.

All solutions Speak with engineering