UPDATED! 06192024

It's happening. The requirement for a separate Oceanic Clearance in the NAT HLA is ending. Significant technological advancements in Communication, Navigation, and Surveillance made this possible. 

As an executive summary, the operator will send the Request for Clearance (RCL) that reflects the FMS loaded filed route but will not receive an Oceanic Clearance in return. Instead, ATC will use the data provided in the RCL to gather the information needed to deconflict and sequence traffic. If a reroute is required, an FMS loadable routing will be uploaded to the aircraft or received via Voice. Review the details below:

Implementation Dates/Status (Subject to Changes - Check NOTAMS):

Reykjavik OAC - Implemented March 21, 2024

Santa Maria OAC - Implemented March 21, 2024

Gander OAC - NOT yet implemented; check NOTAM for the latest implementation date/status, projected for December 4, 2024.

Shanwick OAC - NOT yet implemented; check NOTAM for the latest implementation date/status, projected for December 4, 2024.

Bodo OAC - NOT yet implemented; check NOTAM for the latest implementation date/status, projected for December 4, 2024.

 

Be sure to familiarize yourself with the new procedure for requesting clearance, as outlined in the NAT OPS Bulletin 2023_001 Revision 01.

It must contain the following elements:

  • Oceanic Entry Point (OEP)
  • ETA for OEP
  • MACH number based on FMS cost index (ECON)
  • Requested Flight Level
  • The highest acceptable Flight Level which can be attained at the OEP (via free text)
    • Provide the highest acceptable Flight Level as MAX FL (e.g., if requesting FL 360 but max is FL 380 - enter free text MAX F380)
    • If the requested Flight Level is the highest acceptable, provide the requested FL as MAX FL (e.g., Requesting FL360 - enter free text MAX F360)

Additional details can be found in the following:

Scott IPC ICRH v5
NAT OPS Bulletin 2023_001 Revision 01
NAT Doc 007 V.2024-1 (Applicable 21 March 2024)

For any questions, contact Norbert Schuchbauer at This email address is being protected from spambots. You need JavaScript enabled to view it. or at This email address is being protected from spambots. You need JavaScript enabled to view it.