PBN and Flight Planning 2nd ICAO EUR PBN TF - RAiSG meeting Aline TROADEC / Charlie ELIOT EUROCONTROL Brussels / Belgium 12-14 March 2014
Table of content Current PBN codes for FPL (FPL 2012) Latest PBN manual update and the need for more codes Preparing for the use of PBN codes in FPL (NM system changes?) 2
ICAO PANS ATM - FPL 2012 provisions (1/2) New Flight Plan (FPL) syntax (codes) introduced November 2012 Impact of Navigation: Item 10 (Equipment): P no longer available R now indicates PBN capabilities Filing R requires further information to be filed in Item 18 Item 18 (Remarks): Certified and operationally approved capabilities to be notified in PBN/ line 3
ICAO PANS ATM - FPL 2012 provisions (2/2) To ensure correct FPL filing by AOs, EUROCONTROL developed: Electronic training packages available in Training Zone: ICAO 2012 Flight Planning Modifications ICAO 2012 Flight Plan Guide Guidance material: Guidance for the provision of NAV/COM/SUR information in the New ICAO 2012 Flight Plan NSG 15 - WP 5 : 2012 Flight Plan Navigation with PBN Considerations Is there a need for more guidance? e.g. linking with EASA AMC and CS and FAA ACs? 4
Use of FPL 2012 data Analysis of FPL content has started: In collaboration with PRISME team Enables EUROCONTROL to make a fleet capability assessment (see 2nd RAISG / PBN TF IP14) Requires accurate and correct FPL filing by AOs Output data is one way of States understanding what PBN capabilities are operating within their State Increasing number of requests on FPL content for business decisions Joint EUROCONTROL teams effort required to address these demands in a consolidated way 5
Impact of updated PBN Manual PBN Manual Edition 4 released in March 2013 PANS ATM FPL provisions do not cover new Nav Specs or additional available functionality: No code for: RNP2, A-RNP, RNP0.3 RF functionality can now be associated to other terminal RNP specifications High and Low continuity requirements for RNP2 and A-RNP not considered FRT can be associated to en-route RNP specs 6
Discussing the need for more codes Joint EUROCONTROL/FAA paper proposing new PBN codes presented at ANC 12 Subsequently, PBN codes proposed for adoption in ICAO Panels (ICAO NSP, SASP, ATMRPP) ICAO will not change PANS ATM provision before FF-ICE introduction Expected 2018 2020 timeframe Therefore no global provision of new PBN codes until that date ICAO propose that regional provision be developed if specific PBN codes are not available Published in regional supplement (ICAO EUR Doc 7030) Coordination with other regions required to prepare for worldwide adoption Concern: the growing number of codes will need additional rules so that relevant codes are filled in under PBN/ designator in Item 18 limited to16 characters (instead of under NAV/ in free text) 7
Using FPL PBN content for Flow and Capacity Management (1/2) PBN data is contained in FPL but NMOC (CFMU) don t use it Using it will require changes to NM systems This is discussed in ODSG (ODSG is the «Air Traffic Flow and Capacity Management Operations and Development Sub Group», as sub group of NETOPS Team) AP 9 on the "use of advanced CNS capabilities in NM systems (includes PBN) was submitted to ODSG 28th meeting (May 2013) Based on the example of Nice airport where RNP APCH may be the only approach available to access the airport in certain weather conditions ODSG 28 endorsed the proposal to change NM systems to use these capabilities provided in flight plan messages 8
Using FPL PBN content for Flow and Capacity Management (2/2) Since ODSG 28 meeting «CNS equipment» (including PBN) has been added to ODSG work programme Implementation cannot be expected earlier than Release NM19 in 2015 and the details of a Change Request (CR) need to be defined Detailed requirements for changes have yet to be developed RAISG and PBN TF members are invited to share their views on how they expect PBN data to be used for Flow Management Proposed ACTION ON stakeholders to collect information on how PBN content in FPL is expected to be used for Flow Management (e.g. filtering by NMOC, display to ATC for operations, etc) 9
10