PBN Implementation inside Italian Airspace

Size: px

Start display at page:

Download "PBN Implementation inside Italian Airspace"

Roland Poole
5 years ago
Views:

1 PBN Implementation inside Italian Airspace Leonardo NICOLO Airspace and Procedures Design Department TMA, CTR & Airports Unit Responsible Brussels, March,

2 CONTENTS PBN Implementation Path PBN implementation and flight efficiency On going activities PBN contribution to the Airspace Reorganization Quick view on international acitivities in Mediterranean Area 1

National PBN Task Force in place to tackle and handle PBN deployment inside National Airspace; Consultation with Airspace Users through periodical Customer Care meeting to collect feedback and

3 National PBN Task Force in place to tackle and handle PBN deployment inside National Airspace; Consultation with Airspace Users through periodical Customer Care meeting to collect feedback and proposals; Introduction of P-RNAV inside Italian Airspace (Spring 2011); Publication of National PBN implementation plan and Regulator approval of National Safety Case for the introduction of RNP- APCH (Summer 2012); Publication of first RNP APCH procedure for Milan Malpensa and Milan Linate airports (Winter 2012). PBN Implementation Path 2

PBN Implementation Drivers Improve flight efficiency and traffic management by: Deconflicting arrival/departure flows Introduce RNP APCH as back-up for ILS approaches and when only NPAs are

4 PBN Implementation Drivers Improve flight efficiency and traffic management by: Deconflicting arrival/departure flows Introduce RNP APCH as back-up for ILS approaches and when only NPAs are available; Enable CDO/CCO operations; Support air traffic management by : - Better use of non preferential runway ends (e.g. RNP APCH instead NPAs or Circling approaches); - Manage air traffic sequences for operational scenarios characterized by unfavorable radar minima. 3

5 PBN and Flight Efficiency 2012 PBN Driven Average Gains (NM x flight) Aerodrome Procedure type Plannable Date Average gain Rationale LIRF SID YES JAN NM RNAV1 SIDs LIPX SID YES MAR NM RNAV1 SID 4

6 PBN and Flight Efficiency 2013 PBN Driven Average Gains (NM x flight) Aerodrome Procedure type Plannable Date Average gain LIEO STAR NO MAY NM LIEO SID NO MAY NM LIPZ STAR YES JUN NM Rationale RNAV1 STARS. Gains obtained on average basis. MINKA, OLBEK, BATOX exit points STAR RNAV1. Overlay of radar vector patterns 5

PBN implementation ARR/DEP phases LIEO - 2013 Implementation New RNAV1 STARs and SIDs for both runway ends, initially deployed as ATC Discretion ones.

7 PBN implementation ARR/DEP phases LIEO Implementation New RNAV1 STARs and SIDs for both runway ends, initially deployed as ATC Discretion ones. Benefits Separated Arrivals/departures Procedures enabling CDO/CCO. Achievements Average track miles reduction: 11NM for arrivals; 1NM for departures. 6

PBN implementation ARR/DEP phases LIPZ - 2013 Implementation New RNAV1 STARs for Runway 22.

8 PBN implementation ARR/DEP phases LIPZ Implementation New RNAV1 STARs for Runway 22. Benefits Optimize traffic management on coded path. STARs designed in order to support CDO operations. Achievements Average track miles reduction: 7NM 7

9 PBN and Flight Efficiency 2014 PBN Driven Average Gains (NM x flight) Aerodrome Procedure type Plannable Date Average Gain Rationale LIRQ STAR YES FEB NM STAR RNAV1 LIPE SID YES MAY NM SID RNAV1 LIPE STAR YES MAY NM STAR RNAV1 8

10 PBN implementation ARR/DEP phases LIRQ New RNAV 1 STARs in force from February 6 th, 2014 Average gain: 5NM 9

11 LIPE PBN implementation ARR/DEP phases New arrival/departure RNAV1 network planned to be in force from May 1 st, 2014 Average gain: 1NM 10

12 PBN implementation Landing phase RNP APCH procedures initially implemented with LNAV and LPV minima. First airports involved: Linate, Malpensa (12/2012), Fiumicino (01/2013), Venice (05/2013), Bergamo (04/2014) At the moment 9 instrument runway ends served by GNSS approaches. 11

13 PBN implementation Training Three PBN training modules available to tackle all the potential needs arising from the introduction of the new operational concepts: Module 1: PBN Base Target: People employed in operational activities connected to PBN concept (not necessarily ATCOs) Module 2: PBN Base, RNAV1 procedures, RNP APCH procedures: Operational implications and issues Target: ATCOs. Teached in the framework of continuous training sessions. Activities already completed for Milan & Rome ACC and for Olbia, Venice, Florence & Bologna APP; Module 3: Advanced PBN Target: Procedure designers. Splitted in different submodules to cover all the aspects connected with PBN instrument flight procedure design (design, coding, operational concepts). 12

PBN implementation planning RNAV1 planning: Further RNAV1 procedures expected during 2014 for the following airports: LIRF/FCO, LIMC/MPX, LIML/LIN, LIME/BGY, LIMF/TRN, LICJ/PMO Target: Proceed

14 PBN implementation planning RNAV1 planning: Further RNAV1 procedures expected during 2014 for the following airports: LIRF/FCO, LIMC/MPX, LIML/LIN, LIME/BGY, LIMF/TRN, LICJ/PMO Target: Proceed towards the implementation of RNAV1 PBN procedures on all areas provided with radar approach service RNP APCH planning: Further RNP APCH procedures expected during 2014 for the following airports: LIRF/FCO, LIMC/MPX, LIML/LIN LIME/BGY, LIMF/TRN, LICJ/PMO LIPE/BLN, LIRQ/FLR, LIPZ/VCE Target: Achieve about 20 eligible instrument runway ends equipped with GNSS approaches by the end of 2014 and all eligible instrument runway ends by

15 On going activities Introduction of APV BARO/VNAV minima on RNP APCH procedures (last quarter 2014); DME/DME radioelectric coverage assessment supporting PBN operations (update of a former study conducted 9 years ago). Evaluating also low altitude coverage to support RNP APCH missed approach procedures; Gradually enable CDO/CCO operations: - on RNAV1 networks already available and potentially suitable for the introduction of the concept; - on new tailored RNAV1Stars for those airports not yet supported by dedicated RNAV1 networks; Target date: Autumn Target Airports: LIML, LIMC, LIRF. 14

16 PBN support to Airspace Reorganization PBN design => Main enabler of the new airspace structure Segregate arrival and departure flows; Provide a reduction in flown track miles. PBN procedures in Airspace Reorganization Phase 3 Airports affected: 1. Fiumicino 2. Milan Linate 3. Bergamo Orio al Serio 4. Bologna 15

17 PBN support to Airspace Reorganization -LIRF- Expected gains on published flows LIRF Arrivals from N/NE => 7-8 NM LIRA arrivals from N/NE => No gain The slight increase (0.5NM) is overtaken from the great benefit to have splitted arrival flows between LIRF and LIRA. 16

18 PBN support to Airspace Reorganization -LIMC/LIME- Expected gains on published flows LIMC Arrivals from S/SE => 7-8 NM LIME Arrivals from S/SE => 1-5 NM 17

19 PBN support to Airspace Reorganization -LIML- Expected gains on published flows Arrivals from S/SE => 3-7NM Departures SB 1NM Other benefit Reduction of the interdependecy between ARRs and DEPs 18

International Activities Euromed GNSS programme funded by EC, started on 2012.

20 International Activities Euromed GNSS programme funded by EC, started on Objective: Support Euromed countries (Algeria, Morocco, Tunisia, Egypt, Lebanon, Israel, Libya, Syria, Jordan, Palestine) towards the exploitation and operational adoption of EGNOS services in civil aviation and freight transport (identified as priority applications in METIS project, MEDUSA s precursor). Sharing best practices, enabling countries to start the preparation and the implementation of steps and enablers, in view of the EGNOS service coverage; Contributing to technological transfer and capacity building for service exploitation. Establishing a long-term permanent structure named GEMCO (Galileo Euromed Cooperation Office), acting as a driver for E-GNSS initiatives in all domains and involving the Euromed countries. ENAV contribution: PBN expertise (including procedure design activity) Aircraft fleet for procedure validation 19

BLUEMED is the Mediterranean FAB (Italy, Greece, Malta and Cyprus). It is an initiative opened to the participation of other neighboring countries.

21 BLUEMED is the Mediterranean FAB (Italy, Greece, Malta and Cyprus). It is an initiative opened to the participation of other neighboring countries. Sharing experience to achieve an implementation program defined to cover also PBN aspects: Set up of a BLUE MED PBN TF (activity on going) Elaboration of a BLUE MED PBN implementation policy Elaboration of a BLUE MED FAB roadmap First phase: Approach Procedures with vertical guidance (accordingly to ICAO resolution) Updated airport list maintained at Interim Deployment Programme level Second phase: International Activities Harmonization plan (including analysis of next PBN IR) Overall FAB reporting provided to EC under the Interim Deployment Steering Group framework Elaboration of ICAO conformity guidelines 20

22 Conclusions Phased approach PBN implementation targets a) Achieve tangible results b) Answer to operational needs PBN on going 1) Improve 3D flight efficiency 2) Provide RNP APCH on all runway ends 3) Improve ATCOs air traffic management 4) Training: Provide adequate skills to personnel depending on the field of operation (non ATCOs, ATCOs, IFP designers) PBN & MED Area I. Introduction of BARO/VNAV minima; II. DME/DME radioelectric coverage assessment; III. Support to National Airspace reorganization plan I. PBN Blue Med Roadmap & Implementation II. MEDUSA I. GNSS approaches for Beirut airport II. Flight Validation activities 21

23 Thank you for your attention 22

PBN Implementation inside Italian Airspace Status update Summer 2013

PBN Implementation inside Italian Airspace Status update Summer 2013 Paris, 11-13 September 2013 enav.it Contents Tasks achieved PBN implementation schedules On going activities Further aspects Conclusions