ACARS aeronautical datalink monitoring from LEO
Space-based receivers can collect VHF ACARS, HFDL, and VDL Mode 2 traffic far beyond ground-station range, filling the oceanic gaps that radar and ATC simply cannot reach. This page explains the physics, the variants, the decode limits, and what the data is actually good for.
Sensors
- Spire LEMUR-2: Carries a VHF/UHF software-defined radio payload capable of receiving ACARS in the 129–137 MHz aeronautical band. The constellation of over 100 satellites provides near-global coverage with revisit intervals typically under 30 minutes at mid-latitudes, though individual pass windows over a fixed point are short (3–8 minutes), limiting per-pass message capture to whatever the aircraft transmits in that window.
- HawkEye 360 cluster satellites: Fly in formation triplets that enable time-difference-of-arrival and frequency-difference-of-arrival geolocation of VHF emitters, including aeronautical datalink signals. Geolocation accuracy is published at 1–5 km CEP depending on signal duration and geometry, which is coarse for precision tracking but sufficient to confirm oceanic route corridors.
- Aireon ADS-B (cross-validation reference): Hosted on Iridium NEXT satellites, Aireon provides global ADS-B reception with latency under 1 second and position accuracy inherited from aircraft GNSS (typically better than 30 m). It does not decode ACARS content, but its position fixes serve as ground truth against which ACARS-derived position reports can be validated.
- ICAO-standard VDL Mode 2 ground receivers (terrestrial baseline): Ground VDL Mode 2 stations operate at 136.900 MHz with 25 kHz channel spacing and GFSK modulation at 31.5 kbit/s. Their coverage radius is roughly 200–400 km depending on terrain and antenna height, leaving oceanic and polar routes entirely uncovered. Space-based reception extends this geometry globally but at lower signal-to-noise ratios.
Three protocols, one surveillance gap
ACARS is not a single standard. What the industry calls ACARS is actually a family of datalink protocols sharing a common message structure but using different physical layers depending on route and era of aircraft equipment. VHF ACARS operates between 129.125 MHz and 136.900 MHz, transmitting 2,400-baud AM-modulated bursts carrying position reports, fuel loads, engine health snapshots, clearances, and free-text operational messages. HFDL (High Frequency Data Link) uses shortwave frequencies between 2.8 and 21.9 MHz and propagates via ionospheric skip, reaching transoceanic aircraft without any satellite infrastructure. VDL Mode 2, the more modern variant, uses 136.900 MHz with GFSK modulation and a CSMA/CA access scheme, delivering roughly 13 times the throughput of legacy VHF ACARS.
All three variants share one structural property that matters for space-based monitoring: they are unencrypted. The message payload, including aircraft registration, position, altitude, speed, and free-text remarks, is transmitted in plain text. Any receiver with the right frequency, bandwidth, and demodulator can decode them. This is not a vulnerability in the security sense so much as a design assumption from an era when the receiver population was assumed to be licensed ground stations. LEO satellites changed that assumption without anyone changing the standard.
What a LEO receiver actually hears over the ocean
A LEMUR-2 satellite at roughly 550 km altitude has a radio line-of-sight footprint of approximately 2,500 km radius at VHF frequencies, ignoring atmospheric effects. An aircraft transmitting a position report burst of perhaps 0.3 seconds duration is detectable within that footprint if the signal-to-noise ratio is sufficient. The challenge is not geometry but congestion and Doppler. The aeronautical VHF band is heavily used over land; over ocean the channel is quieter, which paradoxically improves decode rates for the messages that matter most for surveillance.
Doppler shift from a LEO satellite moving at roughly 7.5 km/s relative to the ground introduces a frequency offset of up to several kilohertz at VHF, which a software-defined radio must correct before demodulation. Spire's published approach handles this in firmware. The practical result is that message decode rates over the North Atlantic Track System, where aircraft density is moderate and channel loading is lower than over continental Europe, are meaningfully higher than naive link-budget estimates would suggest. Spire does not publish a specific decode-rate figure by region, so any vendor quoting a precise percentage should be pressed for the methodology behind it.
Position reports versus radar: what ACARS adds and what it cannot replace
A standard ACARS position report (message label P1 or P2 in the ARINC 620 schema) contains latitude, longitude, altitude, groundspeed, heading, fuel remaining, and a timestamp. The position is derived from the aircraft's own GNSS or inertial reference system, not from the receiving satellite, so accuracy is determined by the aircraft avionics rather than the space segment. This is both the strength and the limitation of the method.
The strength: position accuracy can be better than 50 m when the aircraft GNSS is functioning correctly. The limitation: the report is only as honest as the avionics feeding it. An aircraft with a spoofed or failed GNSS will report a false position with full confidence. Cross-referencing ACARS position reports against Aireon ADS-B fixes, which are independently derived from a different onboard transponder chain, is the standard method for detecting this class of discrepancy. Where the two agree, confidence is high. Where they diverge by more than a few nautical miles, something requires investigation.
ACARS also carries data that ADS-B does not: engine health parameters, fuel state, crew free-text messages, and OOOI events (Out, Off, On, In gate times). For an airline operations centre this operational telemetry is the primary value. For a government monitoring oceanic traffic, the position thread is what matters.
HFDL: the variant that reaches the poles
VHF ACARS and VDL Mode 2 are line-of-sight protocols. HFDL is not. By using shortwave frequencies that refract off the ionosphere, HFDL reaches aircraft in polar regions where VHF ground stations do not exist and where even Iridium-hosted ADS-B has historically had sparser coverage. The tradeoff is throughput: HFDL operates at 300 to 1,800 baud depending on channel conditions, and ionospheric variability introduces burst errors that degrade decode rates unpredictably.
Space-based HFDL reception is technically distinct from VHF ACARS monitoring. A LEO satellite receiving HFDL must contend with the fact that the signal has already bounced off the ionosphere and may arrive at the satellite from an oblique geometry rather than directly from the aircraft. Published research has demonstrated successful space-based HFDL reception, but it remains a less mature capability than VHF ACARS collection. Buyers should treat HFDL from LEO as a supplementary layer rather than a primary surveillance feed.
Honest limits of the method
Several constraints are worth stating plainly. First, revisit. A single LEO satellite passes over a given oceanic waypoint for a few minutes every 90 minutes or so. A constellation of 100 satellites improves this dramatically but does not produce continuous coverage equivalent to a geostationary receiver. Messages transmitted between passes are simply not heard by the space segment. For a long oceanic flight, this typically means a handful of position reports captured per satellite, not a continuous track.
Second, message completeness. ACARS bursts are short. A satellite that catches the middle of a burst but misses the header cannot decode the message. Burst-level packet loss over oceanic routes from space has not been independently published in a form buyers can rely on; treat vendor claims with appropriate scepticism until validated against a known traffic sample.
Third, the unencrypted nature of ACARS is a double-edged observation. It makes collection straightforward, but it also means the data carries no authentication. A message claiming to be from a specific tail number cannot be cryptographically verified. Spoofing ACARS is not trivial but is not impossible, and the monitoring architecture should account for this.
Satellize can integrate space-based ACARS feeds with open ADS-B and Aireon data to build cross-validated oceanic position threads for government clients, following the same data-fusion logic used in its Tonga crop-estimation programme: multiple imperfect sources combined to reduce the uncertainty that any single source carries alone.
What a monitoring programme actually looks like
A practical ACARS monitoring architecture for a government with oceanic airspace responsibility has three layers. The first is message ingestion: a commercial feed from a constellation operator such as Spire, delivering decoded ACARS messages with reception metadata (satellite ID, signal strength, Doppler-corrected frequency) in near-real-time, typically with latency of 1–5 minutes from transmission to delivery.
The second layer is fusion and validation: cross-referencing ACARS position reports against ADS-B data where available, flagging aircraft that appear in one feed but not the other, and building a continuous track from sparse position samples using dead-reckoning between reports. The third layer is alerting: rules-based detection of aircraft deviating from filed flight plans, unusual fuel states, or OOOI timing anomalies that suggest an unreported diversion. None of this is exotic signal processing. It is disciplined data engineering applied to a domain where the consequences of a missed event are severe.
Typical figures
| Frequency bands covered | VHF ACARS: 129.125–136.900 MHz; VDL Mode 2: 136.900 MHz (25 kHz channels); HFDL: 2.8–21.9 MHz (selected sub-bands) |
| Modulation types | VHF ACARS: AM-MSK at 2,400 baud; VDL Mode 2: GFSK at 31.5 kbit/s; HFDL: PSK at 300–1,800 baud |
| LEO constellation revisit (mid-latitude) | Spire LEMUR-2: typically under 30 minutes aggregate constellation revisit; individual satellite pass duration 3–8 minutes per point |
| Position report accuracy (aircraft-derived) | Typically better than 50 m when aircraft GNSS is functioning; accuracy is a function of aircraft avionics, not the receiving satellite |
| Geolocation accuracy (emitter-location, HawkEye 360 TDOA/FDOA) | 1–5 km CEP depending on signal duration, satellite geometry, and signal-to-noise ratio |
| Message latency (space to ground delivery) | Typically 1–5 minutes from aircraft transmission to decoded message delivery, depending on constellation operator downlink architecture |
| Coverage | Global including oceanic and polar routes; polar HFDL coverage dependent on ionospheric conditions and is less reliable than VHF ACARS |
| Message content (ARINC 620 standard fields) | Aircraft registration, position, altitude, groundspeed, heading, fuel remaining, OOOI gate events, engine health snapshots, free-text operational messages |
| Encryption | None. Legacy VHF ACARS and HFDL are plain-text; VDL Mode 2 supports optional link-layer security but it is not universally deployed |
| Cross-validation source | Aireon ADS-B (Iridium NEXT hosted): global, sub-1-second latency, GNSS-derived position to better than 30 m; does not carry ACARS payload content |
Analytics Satellize can run
| Oceanic position thread reconstruction | Sparse-sample dead-reckoning between ACARS position reports, fused with ADS-B fixes where available, using published ARINC 620 message schema for field extraction | Per-flight position timeline GeoJSON feed, updated on each new message receipt, with confidence interval on interpolated segments |
| Flight-plan deviation alerting | Comparison of decoded ACARS position and altitude reports against filed ICAO flight plan waypoints; threshold-based flagging of lateral or vertical deviations exceeding configurable limits | Real-time alert feed (JSON or email) with tail number, deviation magnitude, last known position, and cross-reference to ADS-B status |
| ACARS versus ADS-B position discrepancy detection | Temporal alignment of ACARS position reports and Aireon ADS-B fixes for the same ICAO 24-bit address; statistical outlier detection on position delta | Daily discrepancy report flagging aircraft where the two sources disagree by more than a configurable nautical-mile threshold, with raw message logs attached |
| Oceanic traffic density mapping | Aggregation of decoded ACARS position reports into grid-cell density counts over configurable time windows; standard kernel density estimation on point data | Weekly GeoTIFF density raster and CSV summary by route corridor, suitable for airspace capacity planning |
| OOOI event timeline and diversion detection | Extraction of Out/Off/On/In gate event messages from ACARS stream; comparison of actual Off and On events against scheduled times and filed destination | Per-flight OOOI event log with automated flagging of arrivals at unscheduled aerodromes |
| Unregistered or anomalous emitter identification | Cross-referencing decoded ACARS aircraft registrations against ICAO aircraft registry and active flight plan database; flagging registrations absent from both | Alert report with message transcript, reception metadata, and HawkEye 360 geolocation estimate where signal duration permits TDOA processing |
Who does the work
We can get this done for you. Satellize runs its own analyst desk and a strong science team. You do not buy a data feed and work out what it means; our people source the imagery, run the analysis described on this page, and hand you the answer with its confidence limits stated. Discuss this requirement.