ENAV experience on LPV implementation Patrizio Vanni GNSS and SES expert International Strategies Office enav.it Tunisi, 23-10-2013
Main topics Company profile ENAV role in MEDUSA ENAV role in GNSS GNSS monitoring 2
Company profile Founded in 1981 Joint-Stock Company, 100% owned by Italian Ministry of Economy and Financial Planning 3
ENAV numbers Flights handled in one year: 1.6 million flights Peak of flights managed in one day: 6,064 Control Towers (TWRs): 39 Area Control Centers (ACCs): 4 Total sq km of airspace for which ENAV is responsible: 751,728 Employees (ENAV, Techno Sky, SICTA): 4,186 Hours of training delivered in 2012 (ENAV, Techno Sky, SICTA) : 195,100 4
ENAV background in GNSS 1996: first participation to international GNSS programmes 1997: First SBAS flight trials on Ciampino airport 1998: signature of bilateral agreement with ESA for the partecipation on the EGNOS programme September 2010: Italian PBN TF constitution April 2011: AIC A1/2011 Introduction of P-RNAV in the terminal airspace of Italy November 2011: First draft for National RNP APCH Safety Case May 2012: EWA signature with ESSP June 2012: National PBN Implementation Plan approved by National Regulator September 2012: National RNP Approaches Safety Case approval by NSA November 2012: AIC A17/2012 Introduction of RNP APCH in Italy December 2012: first LPV publication for Linate Airport 5
ENAV participation in international frameworks EGPC MRD CCB Sol Expert Group PB-NAV EGNOS V3 ANSP Expert Panel BoD OMM PBN TF NSP NSG 6
ENAV role in MEDUSA ENAV will be responsible of performing the flight trials on Monastir airport using a Piaggio P-180 Avanti II equipped with a Rockwell Collins GPS-4000S receiver and a LPV capable Flight Management System (FMS). ENAV is giving also technical support to MEDUSA Members on RNP APCH implementation: Sharing experience and lessons learnt on RNP APCH implementation Studying international framework (ICAO) Identifying convergence areas for Single European Sky regulations Understanding States local scenarios and constraints Defining requirements for GNSS monitoring and recording and possible solutions 7
Implementation Validation & Implementation planning Airspace design Project planning Main supporting tasks PBN implementation process ICAO Doc9613 PBN Manual ICAO EUR Doc025 EUR RNP APCH Guidance Material 1 Operational requirement 2 PBN Implementation team 3 Project objectives and scope 4 Reference scenario 5 Safety and Performance criteria 6 CNS/ATM Assumptions 7 Route design 8 Initial Procedure Design 9 Airspace Volumes Confirm Navigation Specifications 10 11 12 13 14 15 Validate airspace concept Finalize procedure design Instrument flight procedure + Flight Inspection ATC system integration consideration Awareness and training material 16 Implementation 8 17 Post-implementation review 8
Italian LPV implementation plan The plan is in line with the ICAO Assembly Resolution A37/11 Short term 2012-2014 LPV procedures for major airports Radar monitoring mitigation Medium term 2014-2016 LPV for airports with site critical issues Long term 2016-2020 Cost/benefit analysis to assess where is possible to dismiss conventional navaids Future steps 1. Consider impacts of new PBN IR 2. Perform feasibility studies of LPV implementation on small airports without radar monitoring service 3. Review National safety case in order to update some mitigations 4. Consider EGNOS evolutions 5. Update National PBN plan 9
Approach phase Consultation with operators in progress by means of periodical ENAV Customer Care meeting. RNP APCH procedures initially implemented with LNAV and LPV minima (7 procedures). Airports already involved: Fiumicino, Ciampino, Milano Linate, Venezia; Further 8 runway ends expected before next summer Milano Linate, Milano Malpensa, Firenze, Bologna, Bergamo. Implementation, expected during next year, on two runway ends at the moment served only by circling approach (Genova and Verona). LPV helicopter approach procedures developed and validated for Milano Linate and Bergamo airports in the framework of ACCEPTA Project. GNSS monitoring: Activities in progress in order to deploy a national GNSS strategy and to overcome some of the Safety Requirements needed for the implementation of RNP APCH procedures. 10
Training Plan Training modules for Procedure designers in the framework of continuous training activities Training modules on PBN familiarization and P-RNAV procedures, including operational aspects, for ATCOs operating in radar CTR Training module on GNSS approach procedure for ATCOs planned accordingly to implementation schedule Operational training modules on PBN and related procedure management for ATCOs instructors operating at ENAV Academy Training modules on PBN familiarization for all people involved in operational activities. 11
GNSS Monitoring 12
Documentation Annex 10 Aeronautical Telecommunications Annex 11 Air Traffic Services Annex 4 Aeronautical charts Annex 14 Aerodromes Annex 15 Aeronautical Information Services SARPs NOTAM SIS performance Doc 4444 Air Traffic Management Doc 9992 PBN Airspace design manual Doc 9849 GNSS Manual Doc 9613 PBN Manual Doc 8168 PANS-OPS Doc 9905 RNP AR APCH Doc 8071 Manual on testing of radio navigation aids PANS ATM PBN implementation processes GNSS context Implementation guidance Obstacle clearance GNSS testing ATC phraseology Specifications Procedure design FPL 13
The 5Ws for GNSS monitoring WHY? Annex 10 recommends that a State monitor and record relevant GNSS data to support accident/incident investigations and confirm performances. WHAT? GNSS core systems parameters SBAS WHEN? Periodically Not real time WHERE? Representative locations in the service area WHO? States Delegated State or Entity 14
Monitoring and recording process Input IGS sites EDAS EDCN Dedicated stations Recording Retention policies Recording for accidents/incidents investigation support GNSS performance confirmation Elaboration Pegasus Dedicated tools Reporting Periodicity Information 15
1. Input Analysis of sites and infrastructures available on the market: IGS network EDCN EDAS Definition of a policy for the identification of represantive sites Ionospheric errors DoP Other parameters 16
2. Recording Parameters to be recorded: Observed satellite C/N0 Observed raw pseudo-range code and carrier phase Navigation messages Receiver status For SBAS also: Observed GEO C/N0 Observed GEO raw pseudo-range code and carrier phase SBAS data messages Definition of appropriate retention policies Security rules (authentication, data integrity, etc) 17
3. Elaboration GNSS performance (total system concept SIS + airborne capability + aircraft capability to fly the trajectory) in relation to the type of approach (Annex 10) Accuracy Integrity Continuity Availability Computation by dedicated tools (e.g. Pegasus developed by Eurocontrol) Need to have adequate documentation Compliance of algorithms against MOPS specifications Discussions going on the need to monitor also GPS SPS performance 18
4. Reporting Sample of 24hrs data elaboration Trimestral reporting Share of reports For EGNOS: Public monthly reports made by ESSP Site ROMA (Roma EGNOS RIMS Channel A) Date 06/07/2013 Location Lat (deg): 41,804 Lon (deg): 12,584 Alt (m): 172,904 GPS Standalone Receiver THALES AVIONICS Software Pegasus 4.7.4 Solution: with RAIM (no SBAS) Data set Duration Start Stop Expected Total Valid Valid (%) 1 Hz 24h 00:00 23:59 86400 86399 86034 99,58% Results Operation: NPA (HAL: 556 m ; VAL: N/A) Accuracy (m) Measured Scaled Required HNSE(95%) 3,35 211,22 220,00 VNSE(95%) 3,88 - N/A Availability (%) samples 86034 Minimum required 99 % to 99,999% Availability 100% Continuity Events 0 Minimum required 1-1x10^-4 /h to 1-1x10^-8 /h Continuity 1/h (100%) Integrity Events (HPE > HAL) 0 Minimum required 1-1x10^-7 /h Integrity 1/h (100%) MI (PL > PE) Total 0 Horizontal 0 Vertical - Protection level statistics (RAIM Un-weighted PL) HPL (m) VPL (m) 99% 95% 50% mean std deviation 73,63 19,67 10,35 12,18 9,85 - - - - - Position error statistics HPE (m) VPE (m) 99% 95% 50% mean std deviation 4,22 3,35 1,30 1,58 1,04 5,10 3,88 1,56 1,70 1,21 19
Conclusions Need to develop an harmonized approach for GNSS performance assessment under ICAO framework (core constellation vs. GNSS) New constellations (Galileo, Beidou, etc), SBAS evolutions (EGNOS V3) and new services (double frequency) constitutes an attractive challenge for aviation community GNSS data recording and monitoring can be also used to support: RFI mitigation activities Real time ATC (developing dedicated interfaces) But: Differences between performance at ground level and on board aircraft 20
21