11.07.2015 Views

World Air Ops | NAT | Doc 007 MNPS Guidance

World Air Ops | NAT | Doc 007 MNPS Guidance

World Air Ops | NAT | Doc 007 MNPS Guidance

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Guidance</strong> concerning <strong>Air</strong> Navigation in and above the <strong>NAT</strong> <strong>MNPS</strong>A CHAPTER 5CHAPTER 5:OCEANIC ATC CLEARANCES5.1 GENERAL5.1.1 Oceanic Clearances are required for all flights within <strong>NAT</strong> controlled <strong>Air</strong>space (at or aboveFL55). Pilots should request Oceanic Clearances from the ATC unit responsible for the first OCA withinwhich they wish to operate, following the procedures and the time-frame laid down in appropriate AIPs.Such clearances, although in most cases obtained some time before reaching the Oceanic entry point, areapplicable only from that entry point. It is recommended that pilots should request their Oceanic Clearanceat least 40 minutes prior to the Oceanic entry point ETA except when entering the Reykjavik area from theScottish or Stavanger areas, then the clearance should be requested 20 minutes before the Oceanic entrypoint ETA.5.1.2 To assist the OAC in pre-planning optimum airspace utilisation, when requesting an oceanicclearance the pilot should notify the OAC of the maximum acceptable flight level possible at the boundary,taking into account that a climb to the assigned oceanic flight level must be achieved prior to enteringoceanic airspace and normally whilst the aircraft is within radar coverage. The pilot should also notify theOAC of any required change to the oceanic flight planned level, track or Mach Number as early aspracticable after departure. If requesting an OTS track, the clearance request should include the nextpreferred alternative track.5.1.3 Specific information on how to obtain oceanic clearance from each <strong>NAT</strong> OAC is publishedin State AIPs. Various methods of obtaining Oceanic Clearances include:a) use of published VHF clearance delivery frequencies;b) by HF communications to the OAC through the appropriate aeradio station (in accordancewith the timeframes detailed in paragraph 5.1.1 above);c) a request via domestic or other ATC agencies;d) by data link, when arrangements have been made with designated airlines to request andreceive clearances using on-board equipment (ACARS). Detailed procedures for itsoperation may vary. Gander, Shanwick, Santa Maria and Reykjavik OACs provide such afacility and the relevant operational procedures are published in national AIS and also as<strong>NAT</strong> OPS Bulletins which are available for download from the ICAO Paris website (seehttp://www.paris.icao.int/). New York OAC uses the FANS 1/A CPDLC function to uplinkoceanic clearances to all aircraft utilising CPDLC.5.1.4 At some airports situated close to oceanic boundaries or within the <strong>NAT</strong> Region, it maybe necessary to obtain the Oceanic Clearance before departure. These procedures are detailed in relevantState AIPs, which should be consulted prior to departure. On the east side of the <strong>NAT</strong>, this will apply todepartures from all Irish airfields, all UK airfields west of 2° 30'W and all French <strong>Air</strong>fields west of zerodegree longitude. Oceanic Clearances for controlled flights leaving airports within the region are issued bythe relevant ATS unit prior to departure.5.1.5 If an aircraft, which would normally be RVSM and/or <strong>MNPS</strong> approved, encounters, whilsten route to the <strong>NAT</strong> Oceanic <strong>Air</strong>space, a critical in-flight equipment failure, or at dispatch is unable to meetthe MEL requirements for RVSM or <strong>MNPS</strong> approval on the flight, then the pilot must advise ATC at initialcontact when requesting Oceanic Clearance.<strong>NAT</strong> <strong>Doc</strong> <strong>007</strong> 25 Edition 2010

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!