Learn how oceanic ATC uses tracks, CPDLC, ADS-C, HF radio and procedural separation to control Atlantic and Pacific flights.
Oceanic ATC controls aircraft beyond conventional land-based radar by combining filed routes, organised tracks or random routes, assigned flight levels and speeds, position reports and data-link surveillance. Controllers maintain procedural separation inside oceanic control areas, using CPDLC and ADS-C where equipped, with HF radio available for long-range voice communication.
In real-world aviation, crossing an ocean does not mean leaving controlled airspace. The Atlantic and Pacific are divided into flight information regions and oceanic control areas managed by specific ATC units, which coordinate each aircraft with the next unit along its route.
How does an oceanic flight move from planning to exit?
The controlling unit builds a protected traffic profile from the aircraft’s route, altitude, speed, estimated times and navigation capability.
- Plan and file the route. Dispatch selects an organised track, fixed oceanic route or user-preferred route, then checks winds, fuel, alternates, weather and entry times. Our explanation of long-haul dispatch planning in a simulator covers how these pieces fit together.
- Declare the aircraft’s capabilities. The flight plan identifies relevant navigation, surveillance and communication equipment. Oceanic approvals may depend on performance-based navigation, RVSM, CPDLC, ADS-C and the operator’s authorisation—not simply whether the cockpit has matching buttons. Modern aircraft normally combine GNSS, inertial reference systems and an FMS; we explain how those navigation systems maintain an accurate oceanic position.
- Establish contact or data-link. Before the boundary, the crew completes the required CPDLC logon, radio contact or clearance-delivery process at the lead time published for that region.
- Confirm the cleared profile. The crew checks the route, flight level and any assigned Mach number against the FMS and operational flight plan. A filed flight plan is normally a request rather than an ATC clearance, although applicable Gander and Shanwick operations use oceanic-clearance-removal procedures under which the filed profile is followed unless ATC changes it. Other oceanic areas retain different clearance procedures.
- Cross the oceanic entry point. Once inside oceanic airspace, the aircraft follows its cleared route and level, maintains an assigned speed when one is specified, and sends automatic or manual position reports.
- Transfer back to domestic control. Near the far coast, the oceanic controller coordinates the flight with the next ATC unit. The crew receives a new frequency or data-link transfer and then continues under conventional en-route and terminal control.
Is there radar coverage over the Atlantic and Pacific?
Conventional radar usually ends near the coast, but some oceanic sectors now receive surveillance from space-based ADS-B and other systems. Coverage, permitted separation and controller procedures therefore vary by region, altitude and aircraft equipment.
- ADS-B broadcasts the aircraft’s position and can be received by ground or satellite infrastructure.
- ADS-C sends position reports under a data contract agreed between the aircraft and ATC. Reports can be periodic, event-driven or requested by the controller.
- CPDLC carries text clearances and requests; it is a communication system, not a position sensor.
- HF radio provides long-range voice communication where VHF cannot reach. SELCAL can alert the crew when a ground station wants them, avoiding continuous listening to HF noise.
Where surveillance and communication performance support it, controllers may use reduced separation. Elsewhere they rely more heavily on predicted positions and procedural spacing. A cockpit display showing nearby traffic does not itself mean that oceanic ATC can apply radar separation.
How are aircraft kept separated over the ocean?
Oceanic controllers protect aircraft vertically, laterally and longitudinally, using larger procedural margins where continuous surveillance or rapid communication is unavailable.
| Type of separation | How it is maintained |
|---|---|
| Vertical | Aircraft are assigned different flight levels, subject to RVSM capability and the rules for that airspace. |
| Lateral | Routes, tracks and navigation-performance standards keep aircraft on separated paths. |
| Longitudinal | Aircraft on the same or converging route are spaced by time, distance, speed or surveillance-derived position. |
If ATC assigns a Mach number, the crew maintains it unless a change is cleared. Some regions permit operations without a fixed assigned speed, but that does not allow unrestricted speed or level changes. Climbs, descents, shortcuts and weather deviations still require clearance when communication is available.
Some oceanic airspace also authorises a strategic lateral offset procedure. This lets crews fly a small, randomly selected offset to the right of the route centreline, reducing collision risk from navigation errors and wake encounters. It may be used only where the applicable procedure permits it; crews must not invent an offset or move left of track.
Are North Atlantic and Pacific tracks mandatory?
No. Organised tracks are traffic-management tools, not compulsory routes for every oceanic flight.
| Region | Typical route structure |
|---|---|
| North Atlantic | The North Atlantic Organised Track System provides wind-optimised eastbound and westbound tracks. Flights may also use fixed routes or random routes outside, alongside or across the track system when planned and cleared appropriately. |
| Pacific | Flights may use Pacific organised tracks, fixed North Pacific routes or user-preferred routes. The structure depends heavily on the city pair, winds, airspace restrictions and controlling region. |
A published track is not a reservation. Its validity period and direction must match the crossing, and ATC can change the requested level or route to resolve traffic. Crews must also verify every latitude-and-longitude waypoint rather than trusting a track identifier copied from an old briefing.
How do pilots communicate with oceanic ATC?
CPDLC is widely used for routine oceanic messages, while HF voice remains a major long-range communication method and backup.
- CPDLC messages handle clearances, level requests, route changes, estimates and transfers without the reception problems associated with HF voice.
- ADS-C reports automatically provide position and intent data when a contract is active.
- HF voice is used where data-link is unavailable, fails or requires voice follow-up. Radio operators may relay messages between the aircraft and controller.
- VHF works near land and at certain remote stations but cannot provide continuous coverage across most oceanic routes.
- Satellite voice may be available as an approved supplementary or contingency method, depending on the aircraft and regional procedure.
On an airliner, data-link messages appear through a control and display unit or a dedicated panel. Our A320 DCDU walkthrough shows how CPDLC-style messages are presented and answered in a simulator.
If automatic reporting is unavailable, a manual position report normally includes the callsign, waypoint just passed, crossing time and level, the next waypoint with its estimated time, and the following waypoint. Exact message content and reporting requirements come from the applicable regional procedure.
What happens during a weather deviation or communication failure?
The crew requests a deviation, new level or revised route before leaving the clearance whenever communication and circumstances allow. ATC then checks the proposed path against traffic that may be invisible to the pilots.
If immediate action is required for safety, the captain may deviate under emergency authority and inform ATC as soon as possible. Lost-communication and oceanic contingency procedures prescribe routing, broadcasts, lights, transponder use and altitude changes as applicable. Those details vary by region and situation, so real crews use current charts, operator manuals and checklists rather than a memorised generic manoeuvre.
How should oceanic ATC be reproduced in a flight simulator?
Treat a simulated ocean crossing as a route, clearance and position-management exercise rather than hours of unattended cruise. Built-in ATC may continue issuing VHF-style instructions far offshore or behave as if radar coverage were uninterrupted; that is a software limitation, not a faithful model of oceanic control.
- Create a date-appropriate route. You can build and validate a long-haul SimBrief flight plan, but check that any organised track is valid for the crossing time and direction.
- Compare the route everywhere. The operational plan, simulator flight plan and aircraft FMS should contain the same entry point, oceanic coordinates and exit point.
- Check each coordinate leg. Latitude-and-longitude formats differ between avionics. A valid-looking entry can place a waypoint hundreds or thousands of miles away, so inspect leg distances and the map before departure.
- Use only supported data-link functions. A simulated DCDU may model messages without connecting to an active controller. Know whether the aircraft, add-on or ATC environment actually supports CPDLC.
- Hold the cleared profile. Do not change Mach, flight level or route merely because the simulator is quiet. Record position estimates and practise requests or reports at the appropriate points.
The mistakes we see most often are loading yesterday’s track, omitting an oceanic exit waypoint, leaving a route discontinuity in the FMS, and assuming the magenta line is an ATC clearance. Checking the validity period, waypoint sequence, leg distances and cleared profile before the coast catches all four.