VDL — How Very High Frequency Data Link Works in Aircraft Communications

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

Sergey St.

Published on Jun 12th 26

Share:

• 
• 
• 

What Is VDL?

Very High Frequency Data Link, commonly abbreviated as VDL, is a family of digital data communication protocols used by aircraft to exchange messages with ground stations over the VHF radio band. It is one of the foundational data link subnetworks in the ACARS (Aircraft Communications Addressing and Reporting System) ecosystem and is the dominant data link for aircraft operating in continental airspace worldwide.

VDL operates in the aeronautical VHF band, specifically between 118 and 137 MHz — the same band used for traditional voice radio communications between pilots and controllers. Unlike its long-range counterpart HFDL, which uses ionospheric propagation to cover oceanic distances, VDL relies on line-of-sight radio propagation. A VDL ground station typically provides coverage to aircraft within about 200 miles, depending on altitude. This makes VDL ideal for the densely covered continental regions where ground stations can be deployed in close proximity.

For developers, software-defined radio (SDR) operators, aviation researchers and engineers who decode or process VDL traffic, the messages broadcast by aircraft contain identifiable data — the ICAO 24-bit hex code, the flight number, the aircraft registration and various operational message types. The AirLabs platform does not operate VDL ground stations or decode raw VDL transmissions, but it provides the lookup and enrichment layer that converts identifiers extracted from VDL messages into structured aircraft, airline, route and flight information. This guide covers how VDL works, the different VDL modes, and how to work with VDL data programmatically.

"VDL is the workhorse data link of modern aviation. Over continental airspace it carries everything from flight plans to controller messages, with bandwidth and reliability that satellite and HF data links cannot match. Almost every commercial flight you have ever taken used VDL at some point in its journey."

How VDL Works

VDL is a digital protocol layered on top of VHF radio transmissions. The technical specifications are published in ARINC standards and ICAO documents, and the protocol is operated commercially as part of the global ACARS network. The transmission flow is straightforward:

• The aircraft's avionics determine that a message needs to be sent to a ground system
• The VDL radio selects an appropriate frequency and ground station
• The message is encoded according to the VDL mode in use and transmitted as a digital burst
• A ground station receives the message, acknowledges receipt, and relays it via terrestrial networks to the destination
• The destination — airline operations center, ATC system or weather service — processes the message and may send a response back via the same path

Compared to HFDL's 1800 bits per second, VDL Mode 2 operates at 31,500 bits per second — more than 17 times faster. This higher data rate enables a richer set of message types and supports applications like Controller-Pilot Data Link Communications (CPDLC), where the data link replaces voice for routine ATC instructions.

VDL Modes and Their Differences

The "VDL" designation actually covers several distinct protocols, each known as a "Mode." Understanding the differences helps clarify what kind of VDL data you might be working with:

VDL Mode 2 is by far the most widely deployed mode today. It is what most engineers, researchers and SDR enthusiasts encounter when working with VDL data. The modes share the same physical band (118–137 MHz) but use different modulation schemes, channel access methods and link-layer protocols.

VDL Mode 2 — The Modern Standard

VDL Mode 2 is the technical foundation of modern continental air-ground data communications. Key specifications:

• Frequency band — 118–137 MHz, with 136.975 MHz as the common signaling channel (CSC)
• Modulation — D8PSK (Differential 8-Phase Shift Keying) at 31.5 kbps
• Channel spacing — 25 kHz
• Link protocol — AVLC (Aviation VHF Link Control), based on HDLC
• Network layer — supports both ACARS and ATN/OSI protocols
• Media access — CSMA (Carrier Sense Multiple Access)

For a developer or researcher decoding VDL Mode 2 with SDR hardware, the typical pipeline captures the RF signal at 136.975 MHz, demodulates the D8PSK signal, decodes the AVLC frames, and extracts the ACARS or CPDLC message payload. Open-source tools like dumpvdl2 and acarsdec handle this processing and output structured messages.

VDL in the ACARS Family

VDL is one component of the broader ACARS ecosystem. Aircraft typically have access to multiple data link options and use whichever provides the best service for the current location:

Modern long-haul aircraft are equipped with VDL, HFDL and SATCOM, and the avionics automatically switch between them based on coverage. Over the continental US, Europe, or Asia, VDL is preferred for its bandwidth and reliability. Over the North Atlantic or Pacific, HFDL takes over. For higher-bandwidth applications, SATCOM is used. For comparison with the long-range alternative, see our HFDL guide.

The ACARS message format itself is portable across these data links. An operational message generated on board can be transmitted via VDL, HFDL or SATCOM depending on what is available — the message content remains the same, only the underlying transport changes. This is why VDL decoders and ACARS message databases can interpret messages from different sources using common parsing logic.

Coverage and VDL Ground Stations

VDL ground stations are deployed extensively across continental landmasses with dense aviation traffic. Major commercial VDL networks cover North America (operated by Collins Aerospace and SITA), Europe, East Asia, the Middle East, Australia, and parts of South America and Africa.

Each VDL message typically includes the originating Ground Station ID (GS ID), allowing receivers to identify which station served the transmission. The complete list of operational VDL ground stations is maintained by the network operators and updated as infrastructure changes.

The line-of-sight nature of VDL means coverage improves with altitude. An aircraft at 35,000 feet typically has line-of-sight to ground stations hundreds of miles away, while the same aircraft at low altitude near a terminal area may only reach a few stations.

What Data VDL Carries

VDL Mode 2 transports a wide variety of operational and safety messages, including:

• ACARS operational messages — fuel reports, ETA updates, gate assignments, crew duty times, maintenance status
• CPDLC messages — controller instructions delivered as data instead of voice (climb, descend, frequency change, route clearance)
• ADS-C reports — Automatic Dependent Surveillance-Contract position updates, important in non-radar airspace
• Weather data — METAR, TAF and SIGMET updates delivered to the cockpit
• Flight plan information — clearance delivery, departure clearance, route updates
• Position reports — periodic transmissions for tracking and separation
• Free-text messages — short text communication between crew and operations centers

Every VDL message includes identifying information about the source aircraft — the ICAO 24-bit address (in the AVLC frame header) and typically the aircraft registration or flight number (in the ACARS payload). This is what makes VDL data valuable for tracking and analysis.

Aircraft Identifiers in VDL Messages

VDL messages carry several aircraft identifiers that map directly to AirLabs API lookup fields:

ICAO 24-bit Hex Code

Every VDL Mode 2 transmission includes the source aircraft's ICAO 24-bit address as part of the AVLC frame header. This is the same 24-bit hex identifier broadcast by Mode S and ADS-B transponders. A VDL decoder extracting this hex code can resolve it to a complete aircraft record through the AirLabs Fleets Database:

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
}]

The hex code from a VDL transmission becomes the registration, model, airline and country of the aircraft. For a deeper explanation of how the 24-bit address system works, see our ICAO 24-bit Address guide.

Flight Number

VDL ACARS messages frequently include the flight number being operated. This is the marketing flight code such as AA100 or LH401. The Flight Info API resolves the flight number to full operational details:

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

The response includes departure and arrival airports, scheduled and estimated times, current status, terminal, gate and delay information — converting a flight number from a VDL message into the full context of the flight.

Registration Number

Some VDL message types include the aircraft tail number. The Fleets Database accepts registration numbers as a lookup parameter:

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

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

Enriching VDL Data with AirLabs

The AirLabs platform is not a VDL receiver, does not decode raw VDL signals and does not provide VDL message feeds. What it provides is the data enrichment layer that converts identifiers extracted from VDL messages into structured, queryable aviation data.

A typical VDL monitoring pipeline looks like this:

• Receiver layer — SDR hardware (RTL-SDR, Airspy or similar) tuned to a VDL Mode 2 frequency captures the RF signal
• Decoder layer — software like dumpvdl2 demodulates and decodes AVLC frames into structured VDL/ACARS messages
• Extraction layer — your application parses the messages to extract identifiers (hex code, flight number, registration) and payload data
• Enrichment layer — for each unique identifier, the application queries the AirLabs API to retrieve full aircraft details, current flight information and route data
• Application layer — enriched data is displayed on a map, stored in a research database, exported for analysis, or fed into a tracking dashboard

The enrichment step is where AirLabs fits in. The combination of the Fleets Database (for hex and registration lookups), the Flight Info API (for flight number lookups) and the Real-Time Flights API (for cross-checking position data) covers the typical enrichment needs of a VDL monitoring application.

Use Cases for VDL Monitoring

The community working with VDL data includes several groups:

SDR and Aviation Hobbyists

The largest community of VDL receivers consists of hobbyists running open-source software on inexpensive SDR hardware. They build personal dashboards showing aircraft overhead, log VDL messages for research and share data with online aggregator projects. The AirLabs API is useful here for turning hex codes from VDL messages into readable aircraft details for display.

Aviation Research and Academia

University researchers studying air traffic patterns, controller-pilot interaction efficiency, route utilization or operational anomalies use VDL data because it provides operational context that simple ADS-B positions cannot. Cross-referencing VDL identifiers with the Fleets Database and Flight Info API produces datasets combining raw operational messages with structured flight context.

Air Traffic Management and Safety Studies

Engineers studying ATC operations use CPDLC messages from VDL traffic to analyze how controllers and pilots interact via data link. Safety investigators occasionally use VDL message records as evidence in incident investigations. In both cases, aircraft identifiers from VDL messages are enriched through the AirLabs API to add airline, aircraft type and route context.

Practical Patterns for VDL Data Enrichment

If you are building a pipeline that ingests VDL data and enriches it through the AirLabs API, several patterns apply:

• Cache hex-to-aircraft mappings. The mapping from ICAO 24-bit hex to aircraft details is stable for the lifetime of a registration. Cache aggressively and avoid repeated lookups for the same hex.
• Deduplicate before enriching. A VDL receiver near a busy airport may capture hundreds of messages per minute from the same aircraft. Deduplicate by hex code before issuing API calls.
• Use field selection. For enrichment, you typically need registration, model, airline name and country — not every field. Pass _fields=reg_number,model,airline_iata,flag to keep responses small.
• Handle missing records gracefully. Some hex codes from VDL traffic may not appear in the database (general aviation, military, test flights). Treat missing records as a normal case.
• Cross-check with live flights. When VDL position reports come in, cross-reference with the Real-Time Flights API for the same aircraft to validate the position and merge data sources.
• Combine with route data. A flight number from VDL can be queried against the Routes Database to find the full route the aircraft operates, even if the current message only mentions the flight number.

VDL Data for Developers

If you are building a VDL monitoring application, a research tool that processes ACARS messages, or any system that extracts aircraft identifiers from VHF radio data, the AirLabs API provides the structured aviation data layer that turns raw identifiers into useful aircraft, flight and route information.

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 VDL position reports with live flight data.
• Flight Information API for resolving flight numbers extracted from VDL 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 networks operated by tracked aircraft.
• Name Suggestion API for autocomplete of airport and airline names.
• Field selection via _fields for efficient API consumption in high-volume pipelines.
• JSON, XML and CSV response formats.

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.