Category: ICAO / NAT Operations
Title: NAT Doc 007 V.2026-1 – What Will Actually Change for NAT Flights
Date of Issue: December 2025
Applicable from: March, 19^th 2026
Applicability: CAT & NCC Operators conducting NAT / NAT HLA operations

Why this matters

This update does not change the NAT concept. However, it tightens how NAT procedures are expected to be applied in practice, particularly at the Shanwick and Reykjavik interfaces, during clearance delivery, and in cockpit verification.

The points below focus on where day-to-day NAT operations will actually be affected.

RCL timing is reinforced

Revised wording around Revised Clearances (RCL) reinforces that late changes are not assumed to be acceptable, particularly in Shanwick-controlled airspace.

Operational implications:

RCL requests are time-critical and may be rejected if submitted late.
Tactical reroutes close to 30°W are less tolerated.

What to review:

Dispatcher RCL cut-off times.
Crew understanding of the last acceptable point for RCLs.

Ref: NAT Doc 007 Chapter 6

ETA to ETO – small wording, real consequences

The document aligns NAT procedures with ICAO use of Estimated Time Over (ETO).

Operational implications:

RCL validity and slot protection are time-based.
Inconsistent ETA versus ETO usage can result in clearance mismatch.

What to review:

Flight planning system conventions.
Dispatcher and crew phraseology alignment.

Ref: NAT Doc 007 Chapters 2 and 6

Reykjavik handling of mismatched clearances

Updated guidance clarifies expectations when clearances do not align with filed or expected routing.

Operational implications:

Clearances must be challenged early if routing or timing does not match expectations.
Late resolution increases operational risk.

What to review:

Crew guidance on clearance verification.
Dispatcher escalation paths.

Ref: NAT Doc 007 Chapter 6

FMS waypoint verification is explicitly reinforced

The revised text reinforces explicit FMS waypoint verification, particularly for OTS entry points, coordinate waypoints and random routes.

Operational implications:

Waypoint loading errors remain a primary NAT risk.
Verification is an operator responsibility.

What to review:

NAT cockpit procedures.
Cross-check methodology and training emphasis.

Ref: NAT Doc 007 Chapter 8

Shanwick and Reykjavik assume operator-managed error detection

The document reinforces that ATC does not validate route correctness. Incorrect waypoints, timings or degraded navigation remain the operator’s responsibility.

Operational implications:

GNSS issues prior to NAT entry require active management.
Post-event follow-up and investigation are expected.

What to review:

Dispatcher post-flight checks.
Internal event reporting and follow-up processes.

Ref: NAT Doc 007 Chapters 8 and 11

What operators should do now

Re-brief dispatchers and crews on RCL timing expectations.
Align ETA and ETO usage across dispatch, ATC and cockpit procedures.
Review FMS waypoint verification procedures.
Check OM wording for Shanwick and Reykjavik interface handling.

Official Source

ICAO NAT Doc 007 – North Atlantic Operations and Airspace Manual Edition V.2026-1, Amendment 0 Applicable from 19 March 2026

Further Information

TRS Aviation Consulting supports CAT and NCC operators with NAT procedure reviews and operations manual alignment.