AMC 20-XX presentation Airworthiness and Operational approval for RNAV (GNSS) Approach

1. AMC 20-XX presentationAirworthiness and Operational approval forRNAV (GNSS) Approach B. RABILLER OST O5-3 meeting 21st September 05

2. Contents • Introduction • AMC 20-XX Scope • System Description • Operational Criteria • Flight Crew training • Navigation Database Management. • Aerodrome competence and operator verification • Conclusion and Future work

3. Introduction (1/2) • AMC 20-XX is built on existing guidance material • EASA AMC 20-4 (TGL 2) for Basic RNAV • JAA TGL No. 10 for Precision RNAV • Contains both airworthiness and operational criteria • Completes family of RNAV guidance document (AMC or Leaflet) from departure to final approach • This AMC addresses only navigation systems based on GNSS technology. • Guidance on use of GPS for approach operations (contained within EASA AMC 20-5/JAA TGL 3) to be superseded by AMC 20-XX material

4. Introduction (2/2) • 2 AMCs are proposed to address RNAV Approaches operation: • AMC 20-XX “Airworthiness and operational approval for RNAV (GNSS) approach operation» • AMC 20-XZ “Airworthiness and operational approval for RNP approach operation»  • Apart from the RNP specifics, AMC 20-XX and AMC 20-XZ have common flight crew operating techniques.

5. AMC 20-XX Scope • Objective is to address RNAV(GNSS) approach operation : • Approach designed with straight segment (e.g. “T” or “Y” approach) • A final “straight in” segment following a P-RNAV arrival • Applicable to: • stand-alone GNSS/map equipments (e.g TSO C 129a receiver) • multisensor systems (FMS) with a GNSS sensor • Defines criteria for the lateral navigation part only (as a first step). • Use of Baro VNAV on NPA and APV (Baro and SBAS) are not addressed in this document. • Should not be used for RNP 0.3 approval.

6. System Description • A lateral navigation system based on GNSS. • Accuracy of +/- 1Nm for initial and intermediate approach segment and +/- 0.3 NM for the final segment. • AMC 20-XX describes all RNAV required function (e.g. deviation display, nav data base, Arinc 424 path terminator, integrity alert,…). • AMC 20-XX describes recommended function : • Autopilot/ FD coupling. • Enhance navigation display to support lateral situational awareness, navigation monitoring and flight plan verification. • Dual system installation is not requested for RNAV(GNSS) approach from an airworthiness point of view.

7. Operational criteria (1/2) Consistent with already approved RNAV operational criteria (e.g TGL 10 for PRNAV). • Normal procedure /Pre-Flight planning • RNAV Approach should be a GNSS one. • Approach loaded from the navigation data base has been validated by the operator. • Integrity availability prediction (e.g RAIM) to be checked. • Check if a dual equipment installation is requested to fly this approach (e.g. AIP) • Check availability of a non-GNSS based approach procedure at the alternate airport and/or at the destination airport. • Missed approach procedure should be flown in accordance with the published procedure. • Could be based on conventional means (VOR, NDB), on RNAV or on Dead Reckoning.

8. Operational criteria (2/2) • Normal procedure / Prior to commencing the procedure • Reasonableness check of the loaded procedure (track, distance,…) • For multisensor system, check GNSS sensor is active. • Normal procedure / During the procedure • Final approach trajectory should be intercepted before the FAF. • Route modification (e.g. DIR TO FAF) may be requested by the ATC. • To Check approach mode is activated before FAF (typically 2 Nm before FAF). • To conduct a missed approach if necessary • Abnormal procedure • To develop crew procedure in case of system failures/alerts

9. Flight Crew training • To conduct safely RNAV (GNSS) approach, each pilot should receive appropriate: • training • briefings, • guidance material • This should cover normal and abnormal procedures. • Standard training events such as proficiency check should include GNSS approach. • The operator should determine what constitutes a qualified crew.

10. Navigation Database Management • Navigation database Integrity is demonstrated if a LOA type 2 is issued. • covers the airborne navigation system and its navigation database • if it is not the case the operator should develop an alternate method (manual verification, use of specific tools…) and demonstrate its acceptability to the Authority • Navigation data-base precaution for airborne loading are requested. • load correct navigation database in the correct navigation system model on the correct aircraft type.

11. Aerodrome competence and Operator verification • Operator should determine the operational characteristic of the approach procedure to be flown (e.g hilly environment, missed approach trajectory with turns at low altitude, adequate knowledge for the aerodrome access, adequate aerodrome competence qualification,…). • Based on this assessment: • Appropriate information shall be given to the crew • Crew should have a validated competence if aerodrome access request it. • However in the frame of AMC 20-XX it is anticipated that no specific competence should be requested because RNAV(GNSS) approaches are “easy to fly” approach (e.g.“T” or “Y” approach).

12. Conclusion • AMC 20-XX is developed to address an operational need in Europe. • AMC 20-XX provides clear airworthiness and operational criteria for RNAV(GNSS) approach operation. • AMC 20-XX is consistent with other existing RNAV operational procedure practises (e.g PRNAV, BRNAV, RNP approach). • AMC 20-XX is more detailed than the approach part of AMC 20-5/ TGL 3 and reflect today operational environment.

13. Future Work • Future Version of AMC 20-XX should include APV criteria (Baro-VNAV and SBAS). • Discussion with JAA OPS and AWOSG is necessary for the Baro-VNAV aspect in order to be consistent with the CDFA concept of NPA-OPS 41: • Use of Baro VNAV on NPA . • MDA versus DA • ICAO Performance Based Manual consistency • Terminology • …….

14. Discussion