ICAO framework for LPV

Transcription

1 ICAO framework for LPV Patrizio Vanni GNSS expert enav.it Torrejon,

2 Main topics PBN framework GANP & ASBU concept PBN Manual GNSS Manual Italian experience Conclusions 2

3 The challenges Air Traffic is going to growth in next decades (but less than previously estimated) Transition to GNSS-based services PBN concept Fuel consumption and CO2 emission reduction 3

4 What and why PBN? Performance-based Navigation (PBN) defines performance requirements for aircraft navigating on an ATS route, terminal procedure or in a designated airspace. Benefits: reduce aviation congestion (capacity, efficiency) conserve fuel protect the environment reduce the impact of aircraft noise great flexibility Increase of safety A37-11 urges all States to complete a national PBN implementation plan as soon as possible to achieve: PBN for en route and terminal areas, NAV application NAV specification NAVAID infrastructure PBN Concept according to established timelines and intermediate milestones; PBN approach procedures with vertical guidance (APV) for all instrument runway ends (as primary or back-up for precision approach) by

5 ICAO Performance Based Navigation Concept Airspace Concept Com Nav Surv ATM Nav Applications Nav Specifications RNAV Specifications RNAV10 (RNP 10) RNAV 5 RNAV 2 RNAV 1 Nav Infrastructure RNP Specifications RNP 4 RNP 2 RNP 1 Advanced RNP RNP 0.3 RNP APCH RNP AR APCH RNP w/ Added Requirements e.g. 3D, 4D 5

6 Relevant ICAO Annexes 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 GNSS receiver performance 6

7 Relevant ICAO publications Doc 4444 Air Traffic Management PANS ATM ATC phraseology Doc 9992 PBN Airspace design manual PBN implementation processes Doc 9849 GNSS Manual GNSS context Doc 9613 PBN Manual Doc 8168 PANS--OPS PANS Implementation guidance Obstacle clearance Specifications Procedure design Doc 9905 RNP AR APCH Doc 8071 Manual on testing of radio navigation aids GNSS testing FPL Applicability Nov 2014 (subject to ANC review) 7

8 Air Navigation Conference #12 Held from 19 till 30 November 2012 Attended by 1032 participants from 120 Contracting States and 30 Observer Delegations Endorsement of Global Air Navigation Plan as unified planning mechanism Endorsement for short term Block Upgrades (Block1) Strategic directions for medium and long term Block Upgrades (Block 2 & 3) Today s priorities are: PerfomancePerfomance-based Navigation Continuous Descent Operations Continuous Climb Operations GNSS is a key element for Air Navigation Systems 8

9 ANC#12 recommendations Rationalization of radio systems That ICAO and other stakeholders to explore strategies for the decommissioning of some navigation aids and ground stations, and the rationalization of the on-board communications, navigation and surveillance systems while maintaining safety and coordinating the need for sufficient system redundancy. PBN for terminal and approach operations implementation That States and stakeholders: urgently implement, where appropriate, PBN for terminal and approach operations in accordance with Assembly Resolution A37-11; urgently adopt efficient operations approval procedures and support the mutual recognition of other States operational approvals; share their best practices including required navigation performance authorization-required implementation initiatives as well as relevant flight operational safety assessment documentation with other States; determine operational requirements in support of their airspace concept in accordance with the processes described in the Performance-based Navigation (PBN) Manual in order to select the appropriate PBN specification; including regulators, airport authorities, air navigation service providers, commercial operators, General Aviation and the military, work together at all levels and in close coordination to ensure successful performance-based navigation implementation 9

10 ICAO General Assembly #38 Hosted in Montreal from 24th September till 4th of October Endorsement of ICAO Doc 9750 Global Air Navigation Plan Areas related to GNSS: SBAS L1/L5 signal specification Reflection of GPS L5 specifications in Annex 10 Request from Russian federation on developing instructions material to assist States on implementing GNSS Output assessment on going 10

11 ICAO Global Air Navigation Plan First draft presented at ANC#12, reviewed by States, ICAO Aviation partners and industry stakeholders Provides the potentials to increase system capacity and efficiency, decreasing impacts on environment Block Upgrade concept is a flexible approach to implementation, not all modules are necessary for States and Regions Ch.1 Global Air Navigation Policy Ch.2 Standardization: Aviation System Block Upgrades Ch.3 Continuing Strategic Planning Ch.4 Implementing Globally Interoperable ATM Ch.5. Aviation System Reporting & Performance Adjustments 11

12 Air Space Block Upgrade Concept Performance Improvement Areas AIRPORT OPERATIONS Block 0 (2013) Optimization of approaches procedures including vertical guidance Block 1 (2018) Block 2 (2023) Block 3 (2028>) Optimized airport accessibility GLOBALLY INTEROPERABLE SYSTEMS AND DATA OPTIMUM CAPACITY AND FELXIBLE FLIGHTS EFFICIENT FLIGHT PATHS Improved Operations through Optimized ATS Routing Improved Flexibility and Efficiency in Descent Profiles using Continuous Descent Operations (CDOs) Improved Flexibility and Efficiency in Descent Profiles (CDOs) using VNAV Improved Flexibility and Efficiency in Descent Profiles (CDOs) Using VNAV, Required Speed and Time at Arrival. 12

13 PBN Manual ICAO Doc 9613 Performance-based Navigation Manual 4th ed. was published on March 2013 Guidance to States, Air Navigation Service Providers and Airspace Users on how to implement RNAV and RNP applications. Volume I: Concept and Implementation guidance Part A The PBN Concept Part B Implementation Guidance Volume II: Implementing RNAV and RNP Operations Part A General Part B Implementing RNAV Operations Part C Implementing RNP Operations 13

14 Airspace design Project planning 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 10 Confirm Navigation Specifications Validation & Implementation planning 11 Validate airspace concept 12 Finalize procedure design Implementation 13 Instrument flight procedure + Flight Inspection 14 ATC system integration consideration 15 Awareness and training material 16 Implementation 17 Post-implementation review 14

15 PBN Manual: Navigation Service Monitoring Information on the operational status of radio navigation service If the service is essential by the State GNSS monitoring tool NOTAMs (predictive GNSS service availability) OR Pilot reports based on status information provided by the avionics ADDITIONAL Independent real-time ground based stations (GNSS status information) Differences in RAIM algorithms Satellites in view Receiver mask angle Integration with other sensors (DME/DME, baro, inertial) risk to have conflicting status information, which sensor trust (avionic or ground)? Can be used also for data recording and archiving 15

16 PBN Manual: Implementing RNP APCH LNAV/VNAV minima Elements to be considered Missed approach (can be based also upon conventional NAVAID) Risk of loss of RNP APCH capability Obstacle clearance Verification of SBAS signal and SBAS provider against national regulation Air Traffic Controllers training FAS DB creation (quality of data) SBAS availability Can be checked by NOTAM or Prediction Services (to be decided by the operating authority) Prediction tools assess the expected capability 16

17 PBN Manual requirements for pre-flight RAIM levels required for RNP APCH down to LNAV or LNAV/VNAV minima can be verified by : NOTAMs (where available) prediction services The service may be provided by: ANSP, avionics manufacturer, other entities, airborne receiver RAIM prediction capability LP or LPV service availability prediction should take into account the latest GPS constellation and SBAS system status NOTAMs and avionics model (when available). The service may be provided by: ANSP, avionics manufacturer, other entities through an airborne receiver LP or LPV service prediction capability. 17

18 GNSS Manual ICAO DOC 9849 Global Navigation Satellite System Manual 2nd ed. 18

19 GNSS Manual GNSS vulnerabilities Effective spectrum management Adequate regulatory framework (repeaters and pseudolites) created by States Compatibility of DME/TACAN infrastructure with GNSS Risk assessment on intentional interference Ionosphere and Solar activity Certification and Operational approvals Airworthiness approval Smooth IFR operations Technology mature Acceptable risks SIS performance Quality of procedure design DB integrity Training 19

20 GNSS Manual: GNSS monitoring and recording Objective Monitor and record relevant GNSS data to support accident /incident Objective: investigation and confirm periodically GNSS performances (accuracy, integrity, continuity and availability) Recording point located in representative locations in the service area Recording system independent of the GNSS service and can be delegated to other entities (for EGNOS, in Europe done by ESSP) Parameters to be considered for all GEOs: GEO C/N0 GEO raw pseudo-range code and carrier phase SBAS data messages Receiver status information Can be used as support to RFI detection 20

21 GNSS Manual: Aeronautical Information Services Provide relevant information (terms & conditions, procedures, training req, etc) Background information about SBAS technology Means: AIP, AIC or advisory circular Service status notifications can be provided via NOTAM or on alternative ways (e.g. internet) NOTAM can be used in case of: Widespread SBAS service outages Confirmed local signal interferences 21

22 ENAV background in GNSS 1997: AIC A4/97 introduction of B-RNAV based on VOR/DME infrastructure September 2010: Italian PBN TF constitution, AIC A5/2010 EGNOS SoL introduction over Italian Airspace April 2011: AIC A1/2011 Introduction of P-RNAV in the terminal airspace of Italy based on GNSS, DME/DME November 2011: First draft for National RNP Approaches 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 22

23 Italian LPV implementation plan The plan is in line with the ICAO Assembly Resolution A37/11 Short term LPV procedures for major airports as backup of ILS Radar monitoring mitigation Medium term Long term LPV for airports with site critical issues 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, if necessary 23

24 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 Airports already involved: LIRF => Main runway ends (16L/R, 34L/R); LIML RWY 36, LIMC RWY 35L, LIPZ RWY 22L; Next airports: Further 8 runway ends expected before next summer LIML (RWY 18), LIMC (RWY 35R), LIRQ (RWY 05), LIPE, LIMF (RWY 36), LIME; LIMJ Implementation, expected during next year, on two runway ends at the moment served only by circling approach (LIMJ RWY 10 LIPX RWY 22). LPV helicopter approach procedures developed and validated for Milan 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. 24

25 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. 25

26 Conclusions Some points need to be further developed under ICAO and European framework in order to have an harmonized approach: Clarifications on requirements for GNSS monitoring, Actions to take in case of SIS performance degradation GNSS vulnerabilities SBAS evolutions: DF (L1, L5) + DC (GPS, Galileo) Improvements in service flexibility, availability, level of service and safety 26

27 27