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 16<strong>NAT</strong> ATS providers have established a policy to enable an aircraft that is temporarily non-RVSMcompliant to fly in <strong>NAT</strong> RVSM <strong>Air</strong>space for the purpose of positioning the aircraft at a maintenancefacility (see Chapter 1 in this Manual). This policy may vary and requires prior co-ordination withappropriate ATC centres so that 2,000 ft separation can be applied between the non-compliantaircraft and other aircraft. These requests must be co-ordinated with each individual OAC. Thedispatcher must be aware of the policy for such operations, as published in NOTAMS, AIPs andother appropriate documents. States of Registry also vary in their policies on Maintenance FerryFlights. Dispatchers should ensure that they fully understand any additional restrictions orlimitations that may be imposed by their State of Registry.Delivery and Humanitarian FlightsATS Providers allow limited operations by aircraft not approved for RVSM but which are engagedon delivery or humanitarian flights. For such flights, the dispatcher must also comply with thepolicies published in State AIPs, NOTAMS and other appropriate documents. Co-ordinate directlywith appropriate ATC facilities and the aircraft’s State of Registry.En route Equipage FailuresPrior to entering <strong>NAT</strong> RVSM <strong>Air</strong>spaceThe following equipment is required to be operational:i) two independent primary altimetry systems;ii) one automatic altitude control system; andiii) one altitude alerting deviceIf any required equipment fails prior to entering <strong>NAT</strong> RVSM <strong>Air</strong>space, the pilot-in-command willnotify ATS and obtain a new Oceanic Clearance to fly above or below <strong>NAT</strong> RVSM <strong>Air</strong>space. Thepilot should accept the new clearance contingent upon review by the dispatcher. Dispatcher actionsare based on the options, identified as OPTION 1 to OPTION 3, outlined later in this chapter.After entering <strong>NAT</strong> RVSM <strong>Air</strong>space.The appropriate State RVSM guidance material provides for pilot and controller actions if RVSMrequired aircraft equipment fails after entry into <strong>NAT</strong> RVSM <strong>Air</strong>space, or the aircraft encountersturbulence that affects the aircraft’s ability to maintain its level. Should any required RVSMequipment fail, or turbulence greater than moderate be encountered, then the pilot-in-command isexpected to notify ATS of the intended course of action.Pilot-in-command options are to:(1) continue with the original clearance if ATC can apply another form of aircraft separation(i.e. lateral, longitudinal or 2,000 ft vertical separation);(2) request ATC clearance to climb above or descend below <strong>NAT</strong> RVSM <strong>Air</strong>space if ATCcannot provide adequate separation from other traffic; or(3) execute contingency procedures to offset from track and flight level if ATC cannot provideadequate separation from other aircraft. The pilot-in-command will maintain any offsets untila revised ATC clearance can be obtained.Dispatcher ActionsOPTION 1 - if the pilot-in-command elects for Option (1) then no Dispatcher action is required.OPTION 2 - if the pilot-in-command elects to follow Option (2) then the pilot-in-command shouldcontact the dispatcher who will evaluate the clearance with due consideration for the effect on fuelconsumption, time en route, any MEL/CDL issues and/or other operational factors. The dispatcher<strong>NAT</strong> <strong>Doc</strong> <strong>007</strong> 101 Edition 2010

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

Saved successfully!

Ooh no, something went wrong!