NAT-HLA Explained: The North Atlantic Airspace
- Felippe Martins
- 14 hours ago
- 8 min read
NAT-HLA is the world's busiest oceanic corridor, connecting North America and Europe. Learn how it works, what PBCS means for your flight plan, and what changed in 2026.
In 1919, John Alcock and Arthur Brown climbed into a modified Vickers Vimy bomber and pointed it west to east across the Atlantic — 16 harrowing hours through fog, ice, and near-total disorientation, with no radar, no datalink, and no one waiting to clear them into controlled airspace. Eight years later, Charles Lindbergh did it solo.
Crossing the Atlantic back in the day was a feat reserved for a handful of exceptionally brave aviation pioneers, willing to risk everything on the limits of their aircraft and their own endurance.
Today, more than 1,500 flights cross the North Atlantic every single day.
What was once one of the most dangerous journeys in aviation is now one of the world's busiest overseas airspaces — and the framework that makes it safe is called the NAT-HLA: the North Atlantic High Level Airspace. If you fly long-haul between Europe and North America, NAT-HLA isn't optional reading. It's the rulebook for the crossing.
What Is NAT-HLA?
NAT-HLA stands for North Atlantic High Level Airspace. It covers the oceanic corridor between FL285 and FL420, spanning the airspace between Europe and North America across the North Atlantic Ocean.
The airspace is divided into six Oceanic Control Areas (OCAs), each managed by a dedicated ATC facility:
Gander Oceanic (Canada)
New York Oceanic (USA)
Shanwick Oceanic (UK/Ireland)
Santa Maria Oceanic (Portugal)
Bodo Oceanic (Norway)
Reykjavik ACC (Iceland)
Flights enter NAT-HLA through one of four designated transition areas: Shannon (SOTA), Northern (NOTA), Brest (BOTA), and Gander (GOTA). These entry points are the formal gates into the oceanic environment — and your clearance, timing, and equipment must all be verified before you cross them.
NAT-HLA replaced the older MNPS (Minimum Navigation Performance Specifications) designation. MNPS is gone. HLA is the current framework, and it carries significantly updated requirements.
The Organized Track System (OTS): How to fly the North Atlantic tracks
The centerpiece of NAT-HLA operations is the Organized Track System (OTS) — a set of published airways that change twice daily to optimize for jet stream winds and fuel efficiency.
There are two daily sets of tracks:
Eastbound: published for the morning rush across the Atlantic (typically 01:00–08:00 UTC departure)
Westbound: published for the afternoon/evening departure window
Each track is identified by a letter (Alpha through Zulu) and a TMI — Track Message Identifier — a three-digit number that identifies which daily message generated the track structure. You'll reference the TMI in your flight plan and ATC communications throughout the crossing.
Tracks are not fixed routes. They're dynamic, optimized each day by the Shanwick and Gander OCAs based on NOAA wind forecasts. The track giving you the best winds on Monday may not even exist on Tuesday.
Separation on track: 15 nautical miles lateral, 1,000 feet vertical, and 5-minute longitudinal between aircraft. These standards require precise time-keeping and speed management throughout the crossing — direct controller contact is not available over most of the NAT. ADS-C and CPDLC are your primary communication links.
Mach Number Technique - Longitudinal separation on NAT tracks is maintained primarily through the Mach Number Technique: when two or more aircraft fly the same track at the same flight level with the same assigned Mach number, the time interval between them stays constant throughout the crossing. ATC assigns your Mach in the oceanic clearance — you must maintain it exactly. If you cannot hold the assigned Mach within ±0.02, you must notify ATC immediately.
The tolerance is narrow because even a small speed difference compounds over hundreds of miles. An aircraft flying M0.84 that should be flying M0.82 is closing on the aircraft ahead at roughly 15 knots — invisible to radar, undetectable without accurate position reports.
Some NAT OCAs now implement OWAFS (Operations Without an Assigned Fixed Speed), where ATC issues "RESUME NORMAL SPEED" after oceanic entry. If you receive this message, the Mach restriction is released and the FMS can optimize speed freely — but only after that explicit clearance.
Think about what that means in practice. You're at FL370 over the mid-Atlantic. The nearest radar coverage is hundreds of miles behind you. No controller can see your transponder return. The aircraft ahead of you on the same track is invisible — known only by a time stamp and a Mach number on a paper strip in Shanwick.
The entire system works because every crew on that track made the same commitment before they left the coast: correct equipment, correct clearance, correct speed. One crew that can't be reached changes everything for everyone behind them. That's the context for everything that follows.
Communication Over the Ocean: HF Radio vs. CPDLC
Cross the coastline and VHF ends — line-of-sight propagation doesn't survive the Earth's curvature at oceanic distances. From that point, NAT-HLA runs on two systems that every pilot must understand before departure.
HF Radio: bounces signals off the ionosphere to cover thousands of nautical miles — the only voice system with guaranteed long-range reach. The tradeoff is reliability: static, fading, and frequency changes are routine. Most crews use SELCAL to avoid constant manual monitoring — a coded alert sounds when the OCA needs you, rather than holding an open, noisy channel throughout the crossing.
CPDLC: replaces voice with structured data link messages via FANS 1/A. Clearances, re-routes, and position reports become text exchanges — unambiguous, recorded on both ends, and immune to ionospheric interference. Since 2020, CPDLC is mandatory between FL290 and FL410 across NAT-HLA. Before oceanic entry, crews must log on to the correct Oceanic ACC in the FMS — a missed logon is one of the most common pre-entry errors on the NAT.
ADS-C: runs silently alongside CPDLC, automatically transmitting your position, altitude, and next waypoint to the OCA at set intervals. No pilot action required — it's what gives controllers a continuous picture of your track when radar coverage ends.
In normal operations: CPDLC is primary, HF via SELCAL is backup, ADS-C runs in the background. If CPDLC fails, revert to HF voice and notify the OCA immediately.
The core rule: the OCA must always have a way to reach you.
SLOP: The One Offset That's Always Available
Even in NAT-HLA, Strategic Lateral Offset Procedures (SLOP) give you an extra safety margin. You can fly up to 2.0 NM right of centerline without a clearance. Left offset and offsets greater than 2.0 NM require ATC coordination.
SLOP was made mandatory in 2017 and is now standard practice for NAT crossings. It exists to reduce the risk of collision in the event of a gross navigation error and for wake turbulence avoidance.
2026 Updates Every Pilot Should Know Before Flying NAT-HLA
The NAT operating environment saw significant changes in early 2026. Here's what matters operationally:
Oceanic Clearance Removal (OCR) - Most NAT FIRs now operate under "No Oceanic Clearance Required" procedures. Shanwick remains the exception — clearances are still required through Shanwick OCA, with full implementation delayed until after summer 2026. Check your operator's procedures for the current status before every crossing.
ETO Replaces ETA - Route Clearance (RCL) timing now uses Estimated Time Over (ETO) the oceanic entry point instead of ETA. This is a precision improvement — but it catches pilots off guard when filling out pre-departure paperwork. Verify your OFP uses the correct timing format.
FLAS Removed - The Flight Level Allocation Scheme is gone. There is no longer a published level allocation chart for NAT-HLA. You can plan any available flight level, but expect more tactical adjustments from ATC and less predictability on preferred altitude assignments.
GNSS Jamming and Spoofing - GPS interference over the NAT is now treated as a routine operational risk, not an emergency or exceptional event. Even after position recovery following a spoofing event, timing and surveillance outputs may remain affected. Know your aircraft's GNSS degradation procedures before you depart — and know how to revert to inertial-only navigation if needed.
Greenland Alternates - BGGH (Nuuk/Godthåb) is now open to jet traffic as an alternate. BGBW (Narsarsuaq) is expected to close in 2026. Update your alternate planning accordingly.
Equipment Requirements: What You Need Before You File
To operate in NAT-HLA, your aircraft and operator must be authorized. The baseline equipment requirements are:
Navigation - RNP 4 or RNAV 10
Communication - HF Radio + CPDLC (Datalink)
Surveillance - ADS-C
Long Range Nav Systems - 2 × LRNS (INS, FMS, or GPS)
ADS-B - Mandatory in Reykjavik FIR (from 2025)
Regulatory Authorization - Required from your national authority
The datalink mandate for FL290–410 has been in effect since 2020 — CPDLC is no longer optional at altitude in NAT-HLA. If your aircraft lacks FANS 1/A capability at cruising level, you are not legal to operate in those tracks.When filing, the key item 10 and item 18 codes to include are:
J2–J7: FANS 1/A CPDLC equipped
D1: FANS 1/A ADS-C equipped
R: PBN approved (specify standard in item 18)
PBCS — The Extra Layer for FL350–390
If your track is between FL350 and FL390, you're in PBCS territory. Performance Based Communication and Surveillance (PBCS) introduced tighter separation minima — but with a higher performance bar.
What is PBCS? Check a comprehensive guide on our PBCS post.
PBCS requires:
RCP240 — Required Communication Performance: your CPDLC data link must complete a round-trip within 240 seconds (4 minutes)
RSP180 — Required Surveillance Performance: your ADS-C must report position within 180 seconds (3 minutes)
In exchange, separation on PBCS tracks is reduced to 25 NM lateral, enabling more efficient track allocation and better wind optimization for the operator.
Business aviation represents only 5% of NAT traffic, but accounts for 12% of gross navigational errors — most of them on operators who are not current on PBCS requirements or who incorrectly self-certify compliance.
If your aircraft isn't verified FANS 1/A compliant by your maintenance team, don't assume P2 applies to you.
Contingency Procedures: What to Do When Things Go Wrong
Over the NAT, you are hours from the nearest radar coverage and often minutes from the edge of CPDLC range. When something goes wrong, the procedures must be immediate and precise — there is no controller watching your blip on a screen.
Offset laterally - Turn at least 30 degrees to establish a parallel, same-direction track offset 5 NM from your cleared route. This moves you away from traffic on your track without crossing into opposite-direction flow.
Manage altitude - If maintaining your flight level, establish a 500 ft vertical offset (1,000 ft above FL410) from standard levels. If a descent is required — depressurization, engine failure — descend below FL290. You may begin the lateral divergence as soon as you pass through FL290 during the descent.
Notify - Contact the OCA via CPDLC or HF as soon as possible. Squawk 7700. Provide your position, intentions, and revised routing. Request a new clearance when able. Even beyond VHF range of any ground station, broadcast your situation on 121.5 MHz (emergency) and 123.45 MHz (air-to-air) — other aircraft in your vicinity may be close enough to receive you. Nearby traffic needs to know you are changing altitude, and diverging from your cleared track.
Keep Your NAT Qualification Current
Operating in NAT-HLA requires regulatory authorization that must be maintained by your operator. That authorization depends on your aircraft's avionics certification, your company's ops specs, and in many cases, recency requirements for pilots on long-haul international operations.
NAT-HLA is one of the most regulated and dynamically managed airspaces on the planet. The track system changes daily. Equipment requirements keep tightening. Always refer to official documentation and NOTAMs regarding NAT-HLA airspace.
Keeping track of your type ratings, training, endorsements, and currency is part of staying legal to fly transatlantic. Check the Wader's App Recency and Document Wallet tools at: logbook.waderaviation.com
References:
Comments