HFDL — How High Frequency Data Link Works in Aircraft Communications

HFDL explained. How High Frequency Data Link works as part of the ACARS system, HFDL ground stations and coverage, what data HFDL messages carry, and how to enrich HFDL identifiers with full aircraft and flight data.

Sergey St.

Published on Jun 12th 26

Share:

• 
• 
• 

What Is HFDL?

High Frequency Data Link, commonly abbreviated as HFDL, is a long-range digital communications system used by aircraft to exchange data with ground stations over the High Frequency (HF) radio band. It is one of the data link protocols that make up the broader ACARS (Aircraft Communications Addressing and Reporting System) family, alongside VHF data link, satellite communications and Mode S extended squitter.

What sets HFDL apart is its range. Unlike VHF, which is limited to roughly line-of-sight distances of around 200 miles from a ground station, HFDL exploits the ability of HF radio waves (3–30 MHz) to reflect off the ionosphere and travel thousands of kilometers around the curve of the Earth. This makes HFDL essential for aircraft operating on oceanic routes, polar routes and other remote regions where neither VHF coverage nor reliable satellite signal is available.

For developers, aviation researchers, software-defined radio (SDR) enthusiasts and engineers who monitor or process HFDL traffic, the messages broadcast by aircraft contain valuable identifiers — the ICAO 24-bit hex code, the flight number, the registration number, position reports and operational data. The AirLabs platform does not operate HFDL ground stations or decode raw radio signals, but it provides the lookup and enrichment layer that converts identifiers extracted from HFDL messages into structured aircraft, airline and route data. This guide covers how HFDL works, what data it carries and how to enrich HFDL data using the AirLabs API.

"HFDL is the protocol that keeps oceanic aircraft connected when nothing else can. Every transatlantic flight, every polar route, every remote ocean crossing relies on data links like HFDL for the operational and safety messaging that VHF simply cannot deliver."

How HFDL Works

HFDL is a digital protocol layered on top of HF radio. The technical specification is published by ARINC and implemented commercially as part of the global ACARS network operated by Collins Aerospace (formerly Rockwell Collins). At a high level, HFDL uses a small number of ground stations distributed around the world, each transmitting and receiving on assigned HF frequencies.

When an aircraft equipped with HFDL avionics needs to send a message — a position report, a weather request, a maintenance log, an operational message — it does the following:

• Selects the best available ground station based on signal propagation conditions, time of day and geographic position
• Tunes its HF transceiver to one of the station's assigned frequencies
• Transmits the message in digital format using HF data modulation (typically 8-PSK or QPSK)
• Receives an acknowledgement from the ground station
• The ground station relays the message via terrestrial networks to the destination — the airline's operations center, ATC, or another ground system

The data rate over HFDL is modest by modern standards — typically around 1800 bits per second per channel. This is far slower than VHF data link or satellite communications. But the protocol is highly efficient: messages are short and structured, and the limited bandwidth is more than enough for position reports and operational messaging that occur every few minutes during a flight.

HFDL ground stations are positioned strategically to provide global coverage. There are stations in regions including Reykjavik (Iceland), Riverhead (United States), San Francisco, Hat Yai (Thailand), Krasnoyarsk (Russia), Shannon (Ireland), Auckland (New Zealand), Johannesburg (South Africa), Santa Cruz (Bolivia) and others. The exact list and frequencies are documented in ARINC standards and the receiver software used by HFDL enthusiasts and researchers.

HFDL in the ACARS Family

HFDL is one of several data link subnetworks that aircraft use to send and receive ACARS messages. Understanding the relationship between these technologies helps clarify when HFDL is used:

An aircraft typically has multiple data link options and uses the system that provides the best service for its current location. Over the continental US or Europe, VHF data link is preferred because it is fast and reliable. Over the North Atlantic or Pacific, HFDL takes over. In polar regions where neither VHF nor geostationary satellites have good coverage, HFDL is often the only option. Modern long-haul aircraft equipped with all three (VHF, HFDL, SATCOM) automatically switch between them based on availability.

The ACARS message format itself is independent of the data link — the same operational message (for example, a position report) can be sent over any of these subnetworks. What changes is the physical and link layer of the protocol stack. This is why HFDL receivers can decode the same kind of structured aircraft data that VHF ACARS receivers handle, just from a different radio band.

What Data HFDL Carries

HFDL messages carry several categories of operational and safety data. The specific message types are defined by ARINC standards and the airline's AOC (Airline Operational Control) message catalog. Common HFDL message contents include:

• Position reports — periodic transmissions giving the aircraft's latitude, longitude, altitude, speed and heading. Used by airline operations centers to monitor flight progress and by ATC for surveillance over areas without radar coverage.
• Weather requests and reports — aircraft request weather updates for upcoming waypoints, and report observed conditions back to ground systems.
• AOC operational messages — fuel reports, ETA updates, gate assignments, maintenance status, crew duty time updates and other operational coordination.
• ATC messages — clearance requests, departure clearances, position reports for separation purposes in non-radar airspace.
• Free-text messages — short text messages between the flight crew and ground personnel, used for non-standard communication.

Every message includes identifying information about the aircraft — typically the ICAO 24-bit address and the flight number. This is what makes HFDL data useful for tracking and analytics: even without seeing the aircraft directly, an HFDL receiver can identify which flight is sending each message and where it currently is.

Aircraft Identifiers in HFDL Messages

Three primary identifiers appear in HFDL messages, and each maps directly to a queryable field in the AirLabs API:

ICAO 24-bit Address (Hex Code)

The most reliable identifier in HFDL traffic is the ICAO 24-bit address, broadcast as a 6-character hexadecimal value such as A9D286 or 400936. This is the same identifier used in Mode S and ADS-B transmissions — the permanent ID assigned to the aircraft's transponder. Every HFDL message includes this address, allowing receivers to correlate messages to specific airframes regardless of the flight number.

The AirLabs Fleets Database accepts the hex code as a lookup key:

GET https://airlabs.co/api/v9/fleets?hex=A9D286&api_key={KEY}

[{
  "hex": "A9D286",
  "reg_number": "N732AN",
  "flag": "US",
  "airline_iata": "AA",
  "icao": "B77W",
  "model": "Boeing 777-300ER pax",
  "engine": "jet",
  "engine_count": "2",
  "manufacturer": "BOEING",
  "built": 2015,
  "age": 11
}]

A receiver picking up the hex A9D286 from an HFDL transmission can resolve it to a specific Boeing 777-300ER operated by American Airlines. For a deeper explanation of how the hex address system works, see our ICAO 24-bit Address guide.

Flight Number

HFDL messages typically include the flight number being operated — for example, AA100 or LH401. This is the marketing flight number, which can be looked up directly through the Flight Info API:

GET https://airlabs.co/api/v9/flight?flight_iata=AA100&api_key={KEY}

The response includes departure and arrival airports, scheduled and estimated times, status, delay information, terminal and gate. This converts a flight number observed in an HFDL message into the complete operational context of the flight.

Registration Number

Some HFDL message formats include the aircraft tail number (registration). This is less common than the hex code but still appears in certain message types. The Fleets Database accepts registration numbers as a lookup field:

GET https://airlabs.co/api/v9/fleets?reg_number=N732AN&api_key={KEY}

The response is the same aircraft record as the hex lookup — just keyed by a different identifier.

Enriching HFDL Data with AirLabs

The AirLabs platform is not an HFDL receiver and does not provide raw HFDL message feeds. What it provides is the data enrichment layer that converts identifiers extracted from HFDL messages into structured aircraft, flight, airline and airport information.

A typical HFDL monitoring pipeline looks like this:

• Receiver layer — software-defined radio (SDR) or commercial HFDL receiver captures HFDL transmissions and decodes them into structured messages with identifiers
• Decoding layer — message decoder extracts the ICAO 24-bit hex, flight number, position report and other fields
• Enrichment layer — for each unique aircraft identifier, the application queries the AirLabs API to retrieve the full aircraft record, current flight information and route context
• Display or storage layer — the enriched data is displayed on a map, stored in a database for research, or piped into an analytics pipeline

The enrichment step is where AirLabs fits in. Each hex code observed in HFDL traffic resolves to a complete aircraft profile through a single API call. Flight numbers resolve to full flight details. Airport codes from position reports resolve to coordinates, timezones and connections. This converts a stream of cryptic radio messages into a useful aviation data product.

Use Cases for HFDL Monitoring and Enrichment

The community that works with HFDL data spans several distinct groups, each with different priorities:

Aviation Researchers and Academics

University researchers studying global air traffic patterns, fuel burn analysis or oceanic route operations use HFDL data because it provides position reports for aircraft over areas without radar or ADS-B coverage. Combined with aircraft details from the Fleets Database, this enables analyses that traditional ADS-B feeds cannot support.

Software-Defined Radio Enthusiasts

The SDR community runs HFDL receivers as a hobby — typically with low-cost RTL-SDR or Airspy hardware combined with open-source decoder software. Hobbyists use the AirLabs API to identify aircraft they receive: a hex code from an HFDL message is meaningless until it is resolved to "Lufthansa Airbus A340 D-AIHF, currently operating LH456 from Frankfurt to Atlanta."

Aviation Safety and Incident Investigation

In some incident investigations, HFDL position reports provide the only record of an aircraft's flight path when it operates outside radar coverage. Investigators use HFDL data alongside aircraft details to reconstruct flight trajectories and operational status leading up to events.

Ocean Traffic Analysis

Trans-Atlantic and Trans-Pacific operations rely on HFDL for routine communications. Analysts studying oceanic capacity, route utilization and altitude management use HFDL data to build a picture of operations that ADS-B feeds (limited to terrestrial receivers) cannot show.

Practical Patterns for HFDL Data Enrichment

If you are building a pipeline that ingests HFDL data and enriches it through the AirLabs API, several patterns are worth implementing from the start:

• Cache hex-to-aircraft mappings aggressively. The hex code to aircraft details mapping rarely changes during a registration's lifetime. After the first lookup, store the result locally and avoid hitting the API for the same hex repeatedly.
• Batch lookups when possible. If you have a queue of unresolved hex codes from incoming HFDL messages, process them in batches rather than individually to reduce API call frequency.
• Handle the "not found" case gracefully. Not every hex code observed on HFDL will be in the database — some are general aviation, military or special-use aircraft that may not appear in standard datasets. Treat missing records as a normal case, not an error.
• Match HFDL positions to AirLabs flights when possible. If your HFDL decoder produces position reports for a flight number that is currently live in the Real-Time Flights API, you can cross-check the position data for accuracy and merge sources.
• Use the _fields parameter to request only the fields your application needs. For an enrichment use case, you typically need registration, model, airline and country — a few fields rather than the full record.

HFDL Data for Developers

If you are building an HFDL monitoring application, a research tool that processes oceanic flight data, or any pipeline that extracts aircraft identifiers from radio traffic, the AirLabs API provides the enrichment layer that turns raw identifiers into useful aviation data.

Supported API Features

Our Developer API allows you to create a custom experience for your users and increase the value of your product:

• Aircraft Fleets Database with hex code, registration number, model, manufacturer, age and country lookup.
• Real-Time Flights API for cross-referencing HFDL position reports with live flight data.
• Flight Information API for resolving flight numbers extracted from HFDL messages.
• Airlines Database for converting IATA/ICAO airline codes into carrier names and details.
• Airports Database with IATA/ICAO codes, geolocation, timezone and connections.
• Routes Database for analyzing the route network that HFDL traffic operates on.
• Name Suggestion API for autocomplete of airport and airline names in research interfaces.
• Field selection via _fields for efficient API consumption in high-volume pipelines.
• JSON, XML and CSV response formats for integration with analytics tools.

You can try it right now without any obligation! Get a free flight API plan and see for yourself that we have exactly the data you need!

If you need more information, don't hesitate to contact us. We are always happy to chat with our customers and are sure to find a customized solution for each request.