When an aircraft departs the radar environment and heads out over the open ocean or into remote continental airspace, the familiar infrastructure of ground-based radar and continuous VHF radio contact disappears. Controllers can no longer "paint" the aircraft on a scope every few seconds, and pilots can no longer simply call Center on a discrete frequency and expect a clear reply. To manage the safe flow of thousands of flights crossing the North Atlantic, Pacific, and polar tracks every day, aviation relies on a carefully layered system of satellite-based data link communications, surveillance technology, and structured voice position reports. For the Aircraft Dispatcher, understanding these procedures is essential not only for passing the ADX knowledge test but for providing accurate pre-flight release information and flight-following support to crews operating in these environments.
This article covers the three pillars of oceanic and remote airspace situational awareness: Controller–Pilot Data Link Communications (CPDLC), Automatic Dependent Surveillance–Broadcast (ADS-B Out), and formal oceanic position reporting. Each tool addresses a different limitation of the oceanic environment, and together they form the backbone of what the FAA and ICAO call the Future Air Navigation System (FANS) infrastructure.
The Oceanic Environment and Its Challenges
Beyond approximately 200–300 nautical miles from shore, conventional primary and secondary radar no longer provides reliable surveillance. Over the North Atlantic (NAT), North Pacific, and polar routes, aircraft may be separated by large lateral and vertical buffers that would seem enormous by domestic standards—historically as wide as 60 NM laterally and 2,000 feet vertically—precisely because controllers had no real-time position information. Without radar, position must be inferred from procedural separation: if each aircraft follows its cleared route and altitude, maintains its assigned Mach number, and reports position at designated waypoints, then collision risk remains acceptably low even without radar. Any deviation from the cleared clearance—an off-track excursion, an unauthorized altitude change, or a late position report—immediately degrades that safety margin. This is why procedural discipline in oceanic airspace is treated with extraordinary seriousness.
Voice communication over HF radio has traditionally filled the gap left by VHF range limits. However, HF is subject to atmospheric interference, propagation anomalies, and crowded frequencies, making it unreliable for the precise, timely exchanges that modern oceanic operations demand. CPDLC and ADS-B emerged to provide data links that are far more reliable than HF voice for routine clearances and surveillance.
CPDLC: Controller–Pilot Data Link Communications
CPDLC is a text-based messaging system that allows ATC to send clearances, instructions, and information to a flight crew via a digital data link rather than voice. The crew reads the message on a cockpit display unit (CDU or MCDU), and acknowledges or responds via the same link. In oceanic airspace, CPDLC operates over the ACARS (Aircraft Communications Addressing and Reporting System) or VHF Data Link Mode 2 (VDL Mode 2) networks on the ground, but over the ocean the underlying bearer is typically satellite—most commonly the FANS 1/A suite developed by Boeing and Airbus using Inmarsat or Iridium satellite networks.
The FANS 1/A system combines CPDLC with ADS-C (Automatic Dependent Surveillance–Contract), which is a separate but related capability that automatically transmits position reports at contracted intervals or upon demand from ATC. Dispatchers should note that FANS 1/A is distinct from the domestic ATN B1 (Aeronautical Telecommunication Network Baseline 1) CPDLC used in some CONUS and European high-altitude airspace; the two are not always interoperable.
A typical oceanic CPDLC exchange begins when the aircraft logs on to the oceanic center's ATSU (Air Traffic Service Unit) prior to entering oceanic airspace—ideally 30–40 minutes before the oceanic entry point. The crew sends a logon message; the ground system acknowledges, and a data link session is established. Once in the oceanic sector, ATC can transmit an oceanic clearance (or a revision to an existing clearance) via CPDLC. The crew reviews the clearance, and if it is acceptable, they respond WILCO (will comply); if not, they negotiate via CPDLC or, if urgency requires, via HF voice. HF voice always remains available as a backup; SELCAL (Selective Calling) is used so the crew does not have to monitor HF continuously and can be alerted when a voice call is directed to them.
From a dispatcher's perspective, the oceanic clearance the crew receives via CPDLC may differ from the flight plan filed, especially on North Atlantic Tracks (NAT) where the Organized Track System (OTS) is published twice daily. If the crew accepts a reroute via CPDLC, the dispatcher must be notified (and in Part 121 operations, must concur with significant route changes) so that fuel release, alternates, and operational control remain valid.
ADS-B Out in Oceanic Airspace
ADS-B Out transmits an aircraft's GPS-derived position, altitude, velocity, and identification automatically via a 1090 MHz Extended Squitter (1090ES) transponder to any equipped receiver within line of sight. Over land, a dense network of FAA ground stations provides near-continuous coverage for properly equipped aircraft. Over the ocean, however, ground stations are absent, so line-of-sight ADS-B Out does not reach ATC directly. The solution comes in two forms: space-based ADS-B and ADS-C.
Space-based ADS-B uses a constellation of satellites (currently operated by Aireon, hosted on Iridium NEXT satellites) to receive 1090ES transmissions from aircraft anywhere on the globe. This technology, deployed in the NAT High-Level Airspace (NAT HLA) since 2019, now provides near real-time position surveillance without requiring any additional avionics beyond a standard ADS-B Out transponder. As a result, the NAT HLA reduced its lateral separation minima from 30 NM to as little as 14 NM for FANS-equipped aircraft with space-based ADS-B surveillance, significantly increasing track capacity.
ADS-C (Automatic Dependent Surveillance–Contract) works differently from ADS-B. Instead of a continuous broadcast, ADS-C is a point-to-point system in which ATC establishes a "contract" with the aircraft's avionics specifying when automatic position reports should be sent—for example, every 10 minutes, or upon reaching each waypoint, or if a deviation from cleared altitude exceeds a threshold. ADS-C reports travel via satellite data link (FANS 1/A) directly to the controlling ATSU, providing confirmation of position that supplements or replaces voice position reporting.
Oceanic Position Reporting
Even with CPDLC and ADS-C in place, formal voice position reports via HF remain a procedural requirement for flights not equipped with, or not currently connected via, FANS. A standard oceanic position report contains the following elements in order: aircraft identification, position (the waypoint just passed), time over that waypoint (in UTC), altitude, next waypoint, and estimated time over the next waypoint (ETA), followed by the waypoint after that (the ensuing waypoint, for additional situational awareness). This structure is commonly remembered as: Identification, Position, Time, Altitude/Level, Next position and time, Ensuing position—matching the standard position report format described in the AIM and ICAO Doc 4444.
Reports must be made within a specified window—typically within 3 minutes of passing the reporting point. A late or missed position report is treated as an indication of a possible in-flight problem and triggers overdue-aircraft procedures; if the aircraft's position and status cannot be confirmed, this can escalate to an Alert Notice (ALNOT), which can ultimately lead to a full search-and-rescue response. For the dispatcher, a missed position report from a flight over the ocean is an operational emergency trigger that demands immediate action.
Why These Procedures Matter for Dispatchers
Under 14 CFR Part 121, the dispatcher shares operational control of a flight with the captain. This joint responsibility does not end at the coastline. A dispatcher who releases a flight on an oceanic route must ensure that the aircraft is equipped with appropriate CPDLC/FANS capability if required for the track system, that ADS-B Out is functioning (since space-based ADS-B surveillance now underpins reduced separation in the NAT), and that HF and SELCAL are tested and operational. Dispatch release documentation for oceanic flights must address alternate airports within range at critical oceanic waypoints (ETOPS or equivalent planning) and fuel reserves consistent with the specific oceanic route structure.
Dispatchers must also understand the NAT Minimum Navigation Performance Specifications (MNPS) and, for RVSM airspace within the NAT HLA (FL290–FL410), RVSM approval requirements. Non-RVSM aircraft cannot fly in RVSM airspace and must coordinate non-standard altitude assignments, which dramatically reduces routing flexibility and may affect fuel burn and block times.
Key Numbers and Rules
- FANS 1/A logon: Complete at least 30–40 minutes before the oceanic entry point.
- Position report window: Within 3 minutes of passing an oceanic waypoint.
- NAT HLA altitude band: FL285–FL420 (RVSM required, FL290–FL410).
- Legacy lateral separation: 60 NM without ADS-B/FANS; reduced to as low as 14 NM with space-based ADS-B surveillance and FANS.
- ADS-B Out frequency: 1090 MHz Extended Squitter (1090ES) — required for NAT HLA operations.
- HF backup: Always required; SELCAL check must be completed before oceanic entry.
- Oceanic clearance delivery: Request oceanic clearance from the oceanic center (e.g., Gander, Shanwick, Oakland) typically at or before the oceanic entry point, coordinated through CPDLC or HF.
Common Test Traps
- Confusing ADS-B Out with ADS-C. ADS-B Out is a continuous broadcast picked up by ground stations or satellites; ADS-C is a contracted, point-to-point report delivered via FANS data link. They are separate systems with separate purposes.
- Assuming domestic ATC radar procedures apply oceaniclly. In oceanic airspace, procedural separation—not radar—is the primary tool. A pilot cannot request a block altitude the same way as over land; all changes require a new clearance via CPDLC or HF.
- Forgetting the dispatcher's role in oceanic clearance changes. If the crew accepts a reroute or altitude change that materially alters the flight plan, the dispatcher must be informed and must concur; this is an operational control obligation under Part 121.
- Mixing up MNPS and RVSM. MNPS refers to the horizontal navigation accuracy required for the NAT oceanic tracks; RVSM refers to the reduced vertical separation (1,000 feet instead of 2,000 feet) approval in the FL290–FL410 band. Both are required concurrently in the NAT HLA but address different dimensions.
- Confusing SLOP with position-report escalation. SLOP (Strategic Lateral Offset Procedure) is a collision-avoidance technique that allows aircraft to fly a small offset right of centerline in oceanic airspace; it has nothing to do with missed position reports. A missed or overdue position report instead triggers overdue-aircraft procedures that can escalate to an ALNOT.
- Underestimating the position report timeline. A missed position report is not a minor administrative lapse—it can escalate to a full ALNOT and SAR activation. Dispatchers and pilots must treat position reporting as a critical safety task.