Why can't existing GEO missile-warning satellites like SBIRS track hypersonic glide vehicles?

GEO satellites sit 35,786 km above Earth and detect the intense heat of a ballistic rocket boost phase. Once a HGV releases and glides, its thermal signature drops by one to two orders of magnitude and its trajectory no longer follows a predictable arc. At GEO range, the angular resolution is too coarse to maintain a fire-control-quality track on a vehicle manoeuvring at Mach 10 at 50 km altitude. Dedicated LEO infrared sensors at 500–1,000 km altitude are 35–70 times closer and can resolve the smaller, variable signature.

How many satellites does a sovereign nation actually need to field a useful HGV tracking layer?

The US Space Development Agency's analysis, leading to its 126-satellite Tranche 1 award, suggests that roughly 72–100 satellites in a Walker Delta configuration at 1,000 km is the minimum for near-global persistent coverage with < 30-second handoff gaps. Smaller nations defending a regional area of interest (say, a 3,000 km radius) could achieve useful coverage with 18–24 satellites in a lower-inclination shell, though polar threats would remain uncovered.

What sensors go on a hypersonic tracking satellite?

The primary payload is a staring or scanning infrared sensor operating in the mid-wave infrared (MWIR, 3–5 µm) or short-wave infrared (SWIR, 1–2.5 µm) bands, which capture the aerodynamic heating signature of a gliding body. Many architectures add a long-wave infrared (LWIR) channel for discrimination and a visible/near-IR imager for geolocation cross-check. Inter-satellite link (ISL) hardware — typically laser or Ka-band — is required to relay track data without touching a ground station.

Is a sovereign HGV tracking constellation legal under the Outer Space Treaty?

Pure tracking and warning is generally considered lawful under the 1967 Outer Space Treaty, which prohibits weapons of mass destruction in orbit but does not prohibit passive surveillance or warning systems. The legal risk arises if the constellation's output is tightly integrated into an automated kinetic-intercept loop, which some legal interpretations may characterise as a space-based weapon system. Nations should seek an Article 103 UN Charter and OST compatibility opinion before deployment.

Can a nation buy HGV tracking data as a service instead of building its own constellation?

Currently, no commercial vendor offers a product that meets fire-control-quality HGV tracking standards — the data is too sensitive, the latency requirements too strict, and the sensor specifications too controlled. Intelligence-sharing arrangements (such as Five Eyes) provide partial access for allied nations, but come with caveats on how data can be actioned and do not confer sovereign decision-making. Any nation that depends on an ally's feed can have that feed cut politically or technically during a crisis.

How does a tracking constellation pass data to interceptor batteries on the ground in time?

The satellite compresses a track-state vector (position, velocity, estimated trajectory) and encrypts it under a key management framework aligned with NIST SP 800-53 or equivalent national standard. It transmits via ISL to a relay satellite with a ground station contact, or directly to a ground station, targeting sub-10-second end-to-end latency. The ground station feeds a battle-management system that cues the interceptor; the entire kill chain from detection to interceptor launch must typically complete in under three minutes for a mid-course engagement.

What is the difference between this application and Ballistic Launch Detection (§7.3.1)?

Ballistic Launch Detection focuses on the bright, high-contrast boost phase — the rocket motor plume — which any infrared sensor at GEO or LEO can detect within seconds of launch. Hypersonic Glide Tracking begins after motor burnout, tracking a dimmer, manoeuvring body that is no longer on a predictable parabolic arc. The two applications are complementary: boost detection triggers the alert; HGV tracking maintains the fire-control track needed to support an intercept attempt.

How do you verify that a sovereign constellation is providing accurate tracks and not being spoofed?

Constellation integrity relies on multiple independent sensor cross-checks (staring plus scanning channels), cryptographic authentication of downlinked track packets per CCSDS 504.0-B-2, and comparison with any allied or ground-based radar data available. Anomaly detection algorithms flag abrupt track discontinuities or physically implausible manoeuvres that may indicate a spoofed uplink or sensor malfunction. Regular red-team exercises and hardware-in-the-loop simulation testing against representative HGV signature models are essential for maintaining confidence in the system.

7.3.2Live

Hypersonic Glide Tracking

Q: What sensors go on a hypersonic tracking satellite?

The primary payload is a staring or scanning infrared sensor operating in the mid-wave infrared (MWIR, 3–5 µm) or short-wave infrared (SWIR, 1–2.5 µm) bands, which capture the aerodynamic heating signature of a gliding body. Many architectures add a long-wave infrared (LWIR) channel for discrimination and a visible/near-IR imager for geolocation cross-check. Inter-satellite link (ISL) hardware — typically laser or Ka-band — is required to relay track data without touching a ground station.

Q: Is a sovereign HGV tracking constellation legal under the Outer Space Treaty?

Pure tracking and warning is generally considered lawful under the 1967 Outer Space Treaty, which prohibits weapons of mass destruction in orbit but does not prohibit passive surveillance or warning systems. The legal risk arises if the constellation's output is tightly integrated into an automated kinetic-intercept loop, which some legal interpretations may characterise as a space-based weapon system. Nations should seek an Article 103 UN Charter and OST compatibility opinion before deployment.

Q: Can a nation buy HGV tracking data as a service instead of building its own constellation?

Currently, no commercial vendor offers a product that meets fire-control-quality HGV tracking standards — the data is too sensitive, the latency requirements too strict, and the sensor specifications too controlled. Intelligence-sharing arrangements (such as Five Eyes) provide partial access for allied nations, but come with caveats on how data can be actioned and do not confer sovereign decision-making. Any nation that depends on an ally's feed can have that feed cut politically or technically during a crisis.

Q: How does a tracking constellation pass data to interceptor batteries on the ground in time?

The satellite compresses a track-state vector (position, velocity, estimated trajectory) and encrypts it under a key management framework aligned with NIST SP 800-53 or equivalent national standard. It transmits via ISL to a relay satellite with a ground station contact, or directly to a ground station, targeting sub-10-second end-to-end latency. The ground station feeds a battle-management system that cues the interceptor; the entire kill chain from detection to interceptor launch must typically complete in under three minutes for a mid-course engagement.

Q: What is the difference between this application and Ballistic Launch Detection (§7.3.1)?

Ballistic Launch Detection focuses on the bright, high-contrast boost phase — the rocket motor plume — which any infrared sensor at GEO or LEO can detect within seconds of launch. Hypersonic Glide Tracking begins after motor burnout, tracking a dimmer, manoeuvring body that is no longer on a predictable parabolic arc. The two applications are complementary: boost detection triggers the alert; HGV tracking maintains the fire-control track needed to support an intercept attempt.

Q: How do you verify that a sovereign constellation is providing accurate tracks and not being spoofed?

Constellation integrity relies on multiple independent sensor cross-checks (staring plus scanning channels), cryptographic authentication of downlinked track packets per CCSDS 504.0-B-2, and comparison with any allied or ground-based radar data available. Anomaly detection algorithms flag abrupt track discontinuities or physically implausible manoeuvres that may indicate a spoofed uplink or sensor malfunction. Regular red-team exercises and hardware-in-the-loop simulation testing against representative HGV signature models are essential for maintaining confidence in the system.

Military analysts seated at illuminated screens in a dark command centre, monitoring radar and tracking displays — City lights below highlight the populated regions that satellite tracking of hypersonic glide vehicles works to protect from surprise attack.

Satellite Tracking of Hypersonic Glide Vehicles

1
IR Sensor Satellite
Detects hypersonic glide vehicle heat signature
2
Downlink
Encrypted telemetry to ground stations instantly
3
Trajectory Processing
Kalman-filter algorithms predict glide path
4
Command Decision
Cueed intercept alert sent to commanders

Infrared satellites detect hypersonic glide heat plumes, relay encrypted tracks, and fuse data to generate intercept-ready threat assessments.

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.3.1 · Previous

Ballistic Launch Detection

All in missile warning

7.3.3 · Next

Boost-Phase Identification

Bring this into your sovereign programme.

All solutions Speak with engineering