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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Guidance</strong> concerning <strong>Air</strong> Navigation in and above the <strong>NAT</strong> <strong>MNPS</strong>A CHAPTER 8CHAPTER 8:<strong>MNPS</strong> FLIGHT OPERATION & NAVIGATION PROCEDURES8.1 INTRODUCTION8.1.1 The aircraft navigation systems necessary for flying in <strong>NAT</strong> <strong>MNPS</strong> <strong>Air</strong>space are capable ofhigh-performance standards. However, it is essential that stringent cross-checking procedures are employed,both to ensure that these systems perform to their full capabilities and to minimise the consequences ofequipment failures and possible human errors.8.1.2 Navigation systems are continually evolving and early editions of the <strong>NAT</strong> <strong>MNPS</strong>AOperations Manual concentrated on offering specific guidance on the use of individual approved long rangenavigation systems. The current philosophy within ICAO is to specify the navigation system performancerequired for operations within a given airspace. This concept is referred to as “Performance BasedNavigation” (PBN). Within this philosophy some navigation specifications, in addition to stating theaccuracies to be achieved, also require on-board automatic integrity monitoring and alerting functions. Suchspecifications are referred to as RNP-X, where X represents an accuracy of 95% containment in X Nms.However, specifications requiring the same accuracies but not requiring on-board monitoring are referred toas RNAV-X.8.1.3 <strong>MNPS</strong> has been in use in the <strong>NAT</strong> Region for more than thirty years. It does not require onboardautomatic monitoring and alerting functions. Instead, pilots must remain vigilant and are required toemploy rigorous routine manual monitoring procedures. In the 1990’s a navigation requirements system wasintroduced for use originally in the Pacific Region. Like the <strong>MNPS</strong>, it too does not include any requirementfor on-board automatic monitoring. Its introduction was long before the PBN concept was developed and itwas then annotated as “RNP-10”. Large numbers of aircraft worldwide are now in receipt of “RNP-10”approvals. To conform with the PBN standard terminology, as indicated above, this system should actuallybe designated as “RNAV-10”. However, it has been recognised that re-classifying such a widespreadexisting approval designation would create significant difficulties for both operators and State regulators.Consequently, it has been agreed that this designation of “RNP-10” will remain as such, even though thenavigation specifications here are, in PBN terminology, effectively “RNAV-10”.8.1.4 With current technology, on-board automatic performance monitoring can only be carriedout using GPS. Hence GPS is mandatory for true RNP airspace (e.g. RNP-4) but is not required for RNAVairspace, including that historically and still designated as “RNP-10”.8.1.5 <strong>MNPS</strong> was established primarily with the <strong>NAT</strong> OTS environment in mind. The definingwaypoints of OTS tracks are specified by whole degrees of latitude and, using an effective 60 NM lateralseparation standard, most adjacent tracks are separated by only one degree of latitude at each ten-degreemeridian. The traffic density in the OTS is higher than in any other oceanic airspace. In such a denselypopulated flexible track system (one that changes twice every day), it is essential that crews avoid (wholedegree) waypoint insertion errors. Such errors in the <strong>NAT</strong> <strong>MNPS</strong>A will inevitably result in a conflict withtraffic on an adjacent track. For this reason Minimum Navigation Performance Specifications had to includenot just the technical navigation accuracy of the Long-range Navigation Systems used on the aircraft but alsothe crew navigation procedures employed. The <strong>MNPS</strong> statement thus involves both cockpit/flight deckprocedures and crew training requirements. In the early days of the RNP concept, it was these additionalrequirements that separated <strong>MNPS</strong> from RNP. However, RNP has come a long way since its inception andthe development of the RNP-10 approvals for PAC operations brought it much closer to the original <strong>MNPS</strong>concept. The ICAO <strong>Air</strong> Navigation Plan for the North Atlantic Region states that the intention in the futureis that navigational performance is expected to be tied to a level of RNP. This will probably require the<strong>NAT</strong> <strong>Doc</strong> <strong>007</strong> 44 Edition 2010

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

Saved successfully!

Ooh no, something went wrong!