You are in: PRNAV // Implementation Methodology
   
 

Implementation Methodology

One of the main objectives of P-RNAV introduction is to achieve an ECAC wide consistent design and operation of RNAV in Terminal Airspace. To this end, Terminal Airspace procedures that require P-RNAV approval will have been designed by the Air Navigation Service providers according to a common methodology. This common methodology is outlined below. It also includes the reference documentation that is applied in the various design and implementation steps.



Consider

  • Benefits of Terminal Airspace optimisation using P-RNAV e.g. ATC Workload reduction, fuel reduction, ACFT equipage cost (Cost benefit analysis)
  • Viability of phased implementation to ease transition fromoperational perspective
  • Associated ATC Procedures required to reap benefits.
    Impact of P-RNAV / Conventional Nav. Mix on ATC and Operators (e.g. Effects on operators not P-RNAV approved)
  • Nav infrastructure requirements & associated RNAV flight checking
  • PANS-OPS Procedure design: limitations & opportunities (e.g. Training of designers)
Decision & Action -
  • Time scales for all actions associated with P-RNAV implementation
  • Notification of intent by operators to implement P-RNAV

(These items may only be of relevance to States regularizing their RNAV applications by implementing P-RNAV)

Guidelines & Reference Material

     

Evaluation Phase (Qualitative Analysis)
  • Proposed P-RNAV route placement [subject to NAV infrastructure availability & coverage]
  • Consider P-RNAV procedure design (PANS-OPS)
  • Re-design of Terminal Airspace volume, if required
  • Re-design of ATC sectorisation, if required
Quantitative Analysis
  • ATM safety case to assess acceptability of proposed routeing and airspace changes; incl FTS/RTS as required.
  • If acceptable, continue with PANS-OPS procedure design for P-RNAV certified aircraft

Guidelines & Reference Material

     

APPLICATION OF AVAILABLE STANDARDS AND GUIDANCE ON
  • Minimumcomplexity
  • Way-point naming
  • Validation of procedures (e.g. flight checking & flyability for all ACFT. types)

3.a ENSURE AVAILABILITY OF REQUIRED NAVAIDS

  • Determine current P-RNAV coverage
  • Establish means of flight checking

3.b ENSURE ACCURACY AND INTEGRITY OF ASSOCIATED CO-O0RDINATE DATA

  • Verify WGS/84 compliance and associated AIS processes

3.c P-RNAV PROCEDURE PUBLICATION

  • AIP description incl. coding advice, charting, advice on when to engage RNAV/FMS (e.g. LNAV); non P-RNAV procedures
  • Application of available standards and guidance
     

Introduce P-RNAV ATC procedures as per ICAO
(e.g. use of waypoints for tactical routeings, aircraft

RNAV contingencies) supplemented by

  • Local procedures, as required
  • Local procedures for handling non-approved Aircraft
  • Publication of ATC procedures in local operations manuals and related documents

Guidelines & Reference Material

     

  • Adapt local FDPS for processing of aircraft PRNAV equipment info;
  • Implement capability for automatic and systematic display of individual aircraft RNAV equipment information to ATC; (Radar or Flight Strip)

Guidelines & Reference Material

     

Schedule and perform

  • Local ATC training, taking into account
  • Local real-time simulations

Guidelines & Reference Material

     

As required by National Authority

  • Documentation of processes and applied standards
  • Address local peculiarities & local risk mitigation where required
  • Detailed requirements dependent on requirements set by state authority taking into account material agreed through EUROCONTROL safety regulation material

Guidelines & Reference Material

     


Re : This document incorporates two EUROCONTROL documents viz.

  • EUROCONTROL: GUIDANCE MATERIAL FOR DESIGN OF TERMINAL PROCEDURES FOR DME/GME & GNSSAREANAVIGATION. [Edition 2.2, September 2001]
  • EUROCONTROL: CHARTING GUIDELINES FOR RNAV PROCEDURES. [Edition 1_1, May 2002])

Download this document in PDF format

Guidelines & Reference Material

1) Collaborative Decision Making Between Users and ATSP

  • ECIP NAV.03
  • Eurocontrol: Revised Specimenaic : Operation of Precision PRNAV (P-RNAV) Airborne Equipment in ECAC terminal Airspace [Pending]
  • Standardised specimen AIP Text (To be prepared by Eurocontrol)

2) Terminal Airspace Design & Related Material

  • D. EUROCONTROL: Terminal Airspace Design - Guidelines for an operational Methodology (Edition 2, 2005) Terminal Airspace Design Guidelines
  • E. ICAO: - Doc. 9426 ()
  • F. ICAO: Manual on Airspace Planning Methodology for the determination of Separation Minima - Doc. 9689 ()

3) PANS-OPS and related material

  • G. ICAO: Aircraft Operations - Doc. 8168 ()
  • H. Eurocontrol: Guidance Material for design of Terminal Procedures (DME/DME, BARO-VNAV & RNP- RNAV) [Edition 3, JANUARY 2003]
  • ICAO: Aeronautical Information Service, Annex 15 ()
  • J. Eurocontrol: Data Origination Standard [1st Edition, Pending ]
  • K. EUROCAE: Standards for processing Aeronautical Data, ED-76A
  • L. EUROCAE: Standards for Aeronautical Information, ED-77A
  • M. JAA: Temporary Guidance Leaflet Number 10: Airworthiness and Operational Approval for Precision RNAV Operations in Designated European Airspace [November 2000]
  • N. WGS Surveying, EUR DOC 007 (to be superceded by Ref. J) (see also http://www.ecacnav.com/content.asp?PageID=133)

4) ATC Procedures

  • O. ICAO: Air Traffic Management, Doc. 4444 ATM/501 ()
  • P. ICAO: Regional Supplementary Procedures, Doc. 7030 ()

5) ATC System Modifications

  • Q. Ref. A

6) ATC Training

  • R. Eurocontrol Training Support Material (Pending)

7) Safety Reference Material

 Next Page

Sitemap | Back to Top | Printer Friendly Version

Send comments and questions on this page to: webmaster@ecacnav.com
The information in these web pages is published by EUROCONTROL - the European Organisation for the Safety of Air Navigation. © 2002-2008 EUROCONTROL. Disclaimer