Agenda Item 8: RNAV routes data quality monitoring status report

Transcription

1 Agenda Item 8: RNAV routes data quality monitoring status report 2 nd 12 th nd ICAO EUR PBN TF & EUROCONTROL RAiSG 12 th - 14 th March 2014 EUROCONTROL Airspace Design Section Operations Planning Unit Network Operations Management Division Network Manager Directorate EUROCONTROL

2 RNDSG WP/A Airspace AIP Publication Issues - Progress Summary and Proposed Actions

3 Presentation Progress Airspace Design Meetings RNDSG/77 (OCT 2012) - Initial proposal for adaptation in AIP ENR part of ATS routes vertical limits. RNDSG/78 (FEB 2013) - Initial vision on airspace AIP publication issues. ICAO RDGE/18 (APR 2013) - Discrepancies found in AIP publications of lower and upper vertical limits of ATS routes and consistence and quality of airspace data published in national AIPs. RNDSG/79 (APR 2013) - Airspace AIP publication issues. Summer 2013 (MAY - AUG) Document ECAC States AIP en-route publication issues produced by EUROCONTROL based on ECAC States AIPs and identifying important en-route publication issues. Document released and send to all ECAC States (NETOPS Members with copy to AIM/SWIM members) on 30 th August RNDSG/80 (OCT 2013) - Action List Annex 1 revised following resolution of issues by States in AIPs. 10 th JOINT RNDSG/ASMSG Session (OCT 2013) - Airspace AIP publication issues. Agreed on further actions to resolve the presented issues in the period of 18 months. ICAO RDGE/19 (OCT 2013) - RDGE Action 18/01 and 18/02 NETOPS/7 (OCT 2013) - Airspace Publication issues presented as part of RNDSG Report. RNDSG Regional Meeting (OCT 2013) - Bulgaria: Confirmation on AIP adaptations. RNDSG Regional Meeting (DEC 2013) - Romania, Moldova and Ukraine: requested to further consider the AIP issues and in coordination with the AIS experts to continue resolving them to meet the required time period. 17/03/2014

4 Presentation Progress AIS / AIM Meetings AIOPS/7 (Aeronautical Information Operations Sub-Group) (NOV 2012) - Presentation of an operational and airspace design view on consistency and quality of airspace data published in State AIPs in part ENR. Document ECAC States AIP en-route publication issues AIM/SWIM TEAM-5 (SEP 2013) - Document content presented under Agenda Item 1.5: NETOPS analysis on airspace publication issues. AIOPS/9 (NOV 2013) - AIP En-route harmonization publication issues presented. The AI Operations: Noted the RNDSG activity, Noted the inventory of AIP sent to NETOPS and AIM/SWIM Team members, Noted the AIM/SWIM Team-5 task. Recognized the agreement by AIM/SWIM Team and NETOPS to provide the division on origination and publication issues, for the AI Operations to assess the latter. 17/03/2014

5 AIP adaptations Progress to-date The following 19 ECAC States gradually started to resolve the identified airspace AIP inconsistencies: France, United Kingdom, Armenia, Azerbaijan, Austria, Bosnia and Herzegovina, Czech Republic, Malta, Moldova, Slovakia, The Former Yugoslav Republic of Macedonia, Turkey, Spain, Estonia, Poland, Italy, Portugal, Romania, Lithuania. The following 7 ECAC States provided information on their future intentions: Georgia, Norway, Bulgaria, Germany, Switzerland, Serbia, Montenegro. 17/03/2014

6 AIP Improvements Collection European Route Network Improvement Plan Database developed by EUROCONTROL. Central, interactive database accessible via a standard web browser, integrating short, medium and long-term improvement projects planned for implementation or under development to improve the European ATS route network and airspace structure. Project initiatives come from the States, airspace users and EUROCONTROL in form of requirements or concrete proposals for airspace changes or adaptations. Improvements quoted under Project Category AIP. 33 improvements recorded - 16 implemented / 17 planned/proposed. 17/03/2014

7 46 Actions by ECAC States. Medium-term Actions Annex 2 Category I - Summer /03/2014

8 5 Actions by ECAC States. Medium-term Actions Annex 2 Category II - Summer /03/2014

9 AIP section ENR 3 Publication of ATS routes beyond the State border 1. OTRES / DIRAB - different coordinates and status compulsory / on-request point 2. Different Availability (PERM versus CDR3) 17/03/2014

10 ECAC States AIP en-route publication issues Required update The Document distributed on 30 th August 2013 stated that all observations were referenced to the ERNIP and to Annex 15, Amendment 36 in force from 18 NOV The new Annex 15, Amendment 37 was adopted by the ICAO Council at the sixth meeting of its 198 th Session on 1 March In addition, the Council resolved that Amendment 37, to the extent it becomes effective, will become applicable on 14 NOV The amendments in Appendix 1. Contents of Aeronautical Information Publication (AIP) related to ENR 3 and ENR 4 sub-sections are publication of: the navigation accuracy requirement for each PBN (RNAV or RNP) route segment (ENR ); remarks, including supplementary definition of positions where required (ENR 4.4). In ENR 3.3 the detailed description of area navigation (RNAV) routes point 2) requirement is now in respect of waypoints defining an area navigation route and not only VOR/DME RNAV route. The amendments above shall be properly incorporated in the Document and other new tasks, additional to those is Annex 2, and might be added to the States as identified airspace AIP inconsistencies. 17/03/2014

11 Area Navigation (RNAV) routes publication

12 ENR 3.3. Area Navigation (RNAV) routes Annex 15, Appendix 1, Amendment 37 (Nov 2013) Detailed description of area navigation (RNAV) routes, including: 1) route designator, designation of the navigation specification(s) applicable to a specified segment(s), names, coded designators or name-codes and the geographical coordinates in degrees, minutes and seconds of all significant points defining the route including compulsory or on-request reporting points; 2) in respect of waypoints defining an area navigation route, additionally as applicable: a) station identification of the reference VOR/DME; b) bearing to the nearest degree and the distance to the nearest tenth of a kilometre or tenth of a nautical mile from the reference VOR/DME, if the waypoint is not collocated with it; and c) elevation of the transmitting antenna of DME to the nearest 30 m (100 ft); 3) geodesic distance to the nearest tenth of a kilometre or tenth of a nautical mile between defined end-points and distance between each successive designated significant point; 4) upper and lower limits and airspace classification; 5) direction of cruising levels; and RNAV routes Aeronautical Data Requirements 6) the navigation accuracy requirement for each PBN (RNAV or RNP) route segment; and 7) remarks, including an indication of the controlling unit, its operating channel and, if applicable, its logon address, and any navigation specification(s) limitations. Note.- In relation to Annex 11, Appendix 1, and for flight planning purposes, defined navigation specification is not considered to be an integral part of the route designator.

13 RNAV routes Adapted Publication Requirement - Doc 8126, Specimen AIP

14 RNAV routes Summary of publication issues identified The ICAO Assembly urges all States to implement RNAV and RNP air traffic services (ATS) routes and approach procedures in accordance with the ICAO PBN concept laid down in the Performance-Based Navigation (PBN) Manual (Doc 9613). RNAV routes publication shall be done in State AIP in ENR 3.3. The main difference compare to ENR 3.1 and ENR 3.2 is the required aeronautical data for provision of area navigation on relevant route segments described in Appendix 1 Contents in AIP points 2) and 3). Currently only 5 States (one more from previous report) published RNAV routes in accordance with Annex 15 requirements. The remaining States publish the RNAV routes in either ENR 3.1 or ENR 3.2 or ENR 3.3 divided into lower and upper but using the same table formats. The aeronautical data presented is not as required by Annex 15 for definition of RNAV route. ICAO requirement is far to be a physical placement or move of aeronautical data from ENR 3.1 / 3.2 to ENR 3.3 and vice-versa. It is a requirement for publication of fundamentally different aeronautical data in order to allow RNAV operations. It is difficult to believe that the required aeronautical data in ENR 3.1 / 3.2 is sufficient to support RNAV operations with simply allowing them on these routes. Harmonized publication for all RNAV routes and publication location (AIP placeholder) in ENR 3.3 is required. All ECAC States shall adapt the aeronautical data for RNAV routes in accordance with Annex 15.

15 RNAV routes Publication by Lithuania - 6 MAR 2014 Resolved AIP issues: 1. Withdrawal in publication of minimum flight altitude reference. 2. Publication of required aeronautical data to describe appropriate RNAV routes. 3. Publication of navigation specification(s) applicable to a RNAV specified route. It is published as and shall further be changed to RNAV Publication of coordinates of some 5LNCs in degrees, minutes and seconds. Remaining AIP issues: 1. Replacement of term FL series with Direction of cruising levels (CAT I). 2. Replacement of term Dist with Geodesic DIST (CAT I). 3. Replacement of navigation specification(s) applicable to a RNAV specified route with RNAV 5 (CAT I). 4. Publication of boundary name-code designators outside of brackets and insertion there the term FIR BDRY - example LAVAR (FIR BDRY) (CAT I). 5. Publication of airspace classification at required place with lower/upper limits (CAT II). 6. Publication of all remarks placed in route designator field at appropriate column (CAT I or CAT II). ❸ ❹ ❸ ❻ ❷ ❷ ❷ ❶ ❶ ❸ ❺ ❹ 17/03/2014

16 RNAV routes Publication by Austria - 3 APR 2014 Resolved AIP issues: 1. Template for RNAV routes publication completely changed and adapted to Annex 15 requirements. Remaining AIP issues: 1. Publication of navigation specification(s) applicable to a RNAV specified route - RNAV Publication of airspace classification at required place with lower/upper limits (CAT II). 3. Publication of coordinates of some 5LNCs in degrees, minutes and seconds. 4. No aeronautical data meaning most probably VOR/DME not used as source for area navigation in accordance with Doc Require further confirmation for RNAV application within Wien FIR. ❶ ❸ ❶ ❹ ❷ 17/03/2014

17 Navigation specification (RNP/RNAV) publication

18 Navigation Specification ICAO en-route requirements Doc 9613, Volume I, Part A, Chapter 1, 1.2 Use and scope of Navigation Specifications

19 Navigation Specification Publication requirements Annex 15, Appendix 1, Amendment 37 (Nov 2013) Detailed description of lower ATS routes or upper ATS routes or area navigation (RNAV) routes, including: 1) route designator, designation of the navigation specification(s) applicable to a specified segment(s), names, coded designators or name-codes and the geographical coordinates in degrees, minutes and seconds of all significant points defining the route including compulsory or on-request reporting points; Doc 9613, Volume II, Part B, Chapter 2, 2.2 IMPLEMENTATION CONSIDERATIONS Publication The AIP should clearly indicate the navigation application is RNAV 5. The requirement for the carriage of RNAV 5 equipment in specific airspace or on identified routes should be published in the AIP. The route should rely on normal descent profiles and identify minimum segment altitude requirements. The navigation data published in the State AIP for the routes and supporting NAVAIDs must meet the requirements of Annex 15 - Aeronautical Information Services. All routes must be based upon WGS-84 coordinates.

20 Navigation Specification Summary of publication issues identified The different use of the two kinds of PBN navigation specification RNP and RNAV should be further clarified based on provisions of Doc 7030 and Doc One navigation specification (RNAV) does not include the requirement for on-board performance monitoring and alerting while the other (RNP) includes. Currently majority of States describe the navigation specification of their area navigation routes as while only 11 States as RNAV 5 (4 more from previous report). Two States published B-RNAV while for 6 States there is no description in ENR sub-section (together with route designator) and sometimes reference to GEN 1.5 is made. The table in next slide represents the AIP publication of RNAV routes Navigation Specification as expressed by each ECAC State in publication tables. Harmonized publication of RNAV routes navigation specification and use of unique term/abbreviation - RNAV 5 (as per Doc 7030) is required. The PBN introduction should also be considered as part of this harmonization.

21 Navigation Specification Summary of publication issues identified State Navigation Specification State Navigation Specification ALB ITA ARM RNAV 5 LVA RNAV 5 AUT RNAV 5 LTU AZE RNAV 5 MLT BEL / LUX B-RNAV MDA BIH NLD B-RNAV BGR NOR RNAV 5 HRV POL RNAV 5 CYP PRT RNAV 5 CZE Not published ROU RNAV 5 DNK SRB / MNE EST SVK FIN RNAV 5 SVN FRA Not published ESP Not published GEO SWE DEU Not published CHE Not published GRC MKD HUN TUR Not published ISL RNP 2 UKR IRL RNAV 5 GBR RNAV 5

22 Navigation Specification AIP Examples RNAV 5 B-RNAV NO navigation specification

23 Publication of requirement for carriage of RNAV 5 equipment

24 Carriage of RNAV 5 equipment Publication requirements Doc 9613, Volume II, Part B, Chapter 2, 2.2 IMPLEMENTATION CONSIDERATIONS Publication The AIP should clearly indicate the navigation application is RNAV 5. The requirement for the carriage of RNAV 5 equipment in specific airspace or on identified routes should be published in the AIP. The route should rely on normal descent profiles and identify minimum segment altitude requirements. The navigation data published in the State AIP for the routes and supporting NAVAIDs must meet the requirements of Annex 15 - Aeronautical Information Services. All routes must be based upon WGS-84 coordinates.

25 Carriage of RNAV 5 equipment Summary of publication issues identified The requirement for the carriage of RNAV 5 equipment in specific airspace or on identified routes published in the AIP is different from State to State AIP. In most of the States there is a defined FL above which the carriage of equipment is mandatory but this FL is different in entire ECAC airspace - FL095, FL110, FL115, FL125, FL145, FL195, FL245 etc. There are also definitions as controlled airspace, below FL115 on RNAVdefined routes, on ATS routes, on all ATS routes, State airspace, on all ATS routes under IFR and routes in lower airspace specifically classified as RNAV, on RNAV routes, en-route portion of the ATS route structure or there is no defined FL. Harmonized AIP publication of RNAV 5 application should be further considered.

26 Carriage of RNAV 5 equipment Summary of AIP GEN 1.5 State AIP B-RNAV (RNAV 5) Limit State AIP B-RNAV (RNAV 5) Limit ALB FL110 ITA FL095 ARM Controlled airspace LVA FL095 AUT FL195 LTU FL095 AZE FL195 MLT FL095 BEL / LUX FL095 MDA FL245 on all ATS routes BIH FL195 NLD FL095 BGR FL095 NOR FL095 HRV FL195 POL Polish airspace CYP FL290 PRT On ATS routes CZE FL095 ROU No defined FL DNK FL095 SRB / MNE FL145 EST FL095 SVK FL125 on all ATS routes FIN FL095 SVN No defined FL FRA Above FL115 Below FL115 on RNAV-defined routes ESP FL150 on all ATS routes under IFR and routes in lower airspace specifically classified as RNAV GEO FL195 (ENR 3.3) SWE No defined FL DEU FL095 / FL195 - Alpine area CHE No defined FL GRC On ATS routes MKD On ATS routes HUN On ATS routes TUR No defined FL ISL No defined FL UKR On RNAV routes IRL FL095 GBR En-route portion of the ATS route structure

27 Recommendations The participants at Second Combined ICAO EUR PBN TF & EUROCONTROL RAiSG Meeting are requested to: consider the content of this presentation and discuss as appropriate; further discuss all presented observations with their appropriate AIS/AIM units; consider possible further actions to resolve the presented PBN issues. 17/03/2014