Agenda Item Agenda Item 88: : RNAV routes data quality monitoring RNAV routes data quality monitoring –– status reportstatus report

22ndnd ICAO EUR PBN TF & EUROCONTROL ICAO EUR PBN TF & EUROCONTROL RAiSGRAiSG1212thth -- 1414thth March 2014March 2014EUROCONTROLEUROCONTROL

Airspace Design SectionOperations Planning UnitNetwork Operations Management Division Network Manager DirectorateEUROCONTROL

RNDSG WP/ARNDSG WP/AAirspace AIP Publication Issues Airspace AIP Publication Issues --

Progress Summary and Proposed ActionsProgress Summary and Proposed Actions

17/03/2014

� 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 enECAC States AIP en --route publication issuesroute publication issues ”” produced by EUROCONTROL based on ECAC States AIPsand identifying important en-route publication issues. Document released and send to all ECAC States (NETOPS Members with copy to AIM/SWIM members) on 3030thth August 2013August 2013 .

� RNDSG/80 (OCT 2013) - Action List Annex 1 revised following resolution of issues by States in AIPs.

� 10th 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.

Presentation ProgressPresentation ProgressAirspace Design MeetingsAirspace Design Meetings

17/03/2014

Presentation ProgressPresentation ProgressAIS / AIM MeetingsAIS / 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 enECAC States AIP en --route publication issuesroute 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

AIP adaptations Progress toAIP adaptations Progress to --date date

� The following 19 ECAC States gradually started to resolve the identified airspace AIP inconsistencies:

� France, United Kingdom, Armenia, Azerbaijan, Austria, Bosnia andHerzegovina, 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

AIP Improvements Collection 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

MediumMedium --term Actionsterm ActionsAnnex 2 Category I Annex 2 Category I -- Summer 2015Summer 2015

� 46 Actions by ECAC States.

…

17/03/2014

MediumMedium --term Actionsterm ActionsAnnex 2 Category II Annex 2 Category II -- Summer 2015+Summer 2015+

� 5 Actions by ECAC States.

17/03/2014

AIP section ENR 3AIP section ENR 3Publication of ATS routes beyond the State borderPublication of ATS routes beyond the State border

1. OTRES / DIRAB - different coordinates andstatus compulsory / on-request point

2. Different Availability (PERM versus CDR3)

17/03/2014

““ ECAC States AIP enECAC States AIP en --route publication issuesroute publication issues ””Required updateRequired update

� The Document distributed on 30th August 2013 stated that all observations were referenced to the ERNIP and to Annex 15, Amendment 36 in force from 18 NOV 2010.

� The new Annex 15, Amendment 37 was adopted by the ICAO Council at the sixth meeting of its 198th Session on 1 March 2013. In addition, the Council resolved that Amendment 37 , to the extent it becomes effective, will become applicable on 14 NOV 2013.

� 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 (R NAV or RNP) route segment (ENR 3.1 - 3.4);

� remarks, including supplementary definition of positions where required (ENR 4.4).In ENR 3.3 the detailed description of area navigat ion (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.

Area Navigation (RNAV) routes publicationArea Navigation (RNAV) routes publication

Annex 15, Appendix 1, Amendment 37 (Nov 2013)

� ENR 3.3. Area Navigation (RNAV) routesDetailed 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 tenthof a nautical mile from the reference VOR/DME, if the waypoint is not collocated with it; andc) 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; and6) the navigation accuracy requirement for each PBN (RNAV or RNP) route segment; and7) 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 notconsidered to be an integral part of the route designator.

RNAV routesRNAV routesAeronautical Data RequirementsAeronautical Data Requirements

RNAV routesRNAV routesAdapted Adapted Publication Requirement Publication Requirement -- Doc 8126, Specimen AIPDoc 8126, Specimen AIP

� 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 publ ication location (AIP placeholder) in ENR 3.3 is required. All ECAC States shall adapt the aeronau tical data for RNAV routes in accordance with Annex 15.

RNAV routesRNAV routesSummary of publication issues identifiedSummary of publication issues identified

17/03/2014

Resolved AIP issues:1. Withdrawal in publication of minimum flight alti tude reference.2. Publication of required aeronautical data to des cribe appropriate RNAV routes.3. Publication of navigation specification(s) appli cable to a RNAV specified route. It is published as RNP 5 and shall further be changed to RNAV 5.4. Publication of coordinates of some 5LNCs in degr ees, 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 “RNP 5” 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).

��

�

�

�

��

RNAV routesRNAV routesPublication by Lithuania Publication by Lithuania -- 6 MAR 20146 MAR 2014

17/03/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 5.2. 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 9613. Require further confirmation for RNAV application within Wien FIR.

�

�

�

�

RNAV routesRNAV routesPublication by Austria Publication by Austria -- 3 APR 20143 APR 2014

Navigation specification (RNP/RNAV)Navigation specification (RNP/RNAV) publication

Doc 9613, Volume I, Part A, Chapter 1, 1.2 Use and scope of Navigation Specifications

Navigation SpecificationNavigation SpecificationICAO enICAO en --route requirementsroute 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) appl icable 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 IMPLEMEN TATION CONSIDERATIONS

� 2.2.5 Publication 2.2.5.1 The AIP should clearly indicate the navigation appl ication 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.

Navigation SpecificationNavigation SpecificationPublication requirementsPublication requirements

Navigation SpecificationNavigation SpecificationSummary of publication issues identifiedSummary 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 9613. 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 RNP 5 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 sp ecification and use of unique term/abbreviation - RNAV 5 (as per Doc 7030) is requ ired. The PBN introduction should also be considered as part of this harmoniza tion.

Navigation SpecificationNavigation SpecificationSummary of publication issues identifiedSummary of publication issues identified

Not publishedCZE

RNP 2ISL

RNAV 5IRL

RNP 5HUN

RNP 5GRC

Not publishedDEU

RNP 5GEO

Not publishedFRA

RNAV 5FIN

RNP 5EST

RNP 5DNK

RNP 5CYP

RNP 5HRV

RNP 5BGR

RNP 5BIH

B-RNAVBEL / LUX

RNAV 5AZE

RNAV 5AUT

RNAV 5ARM

RNP 5ALB

Navigation SpecificationState

RNP 5ITA

RNAV 5GBR

RNP 5UKR

Not publishedTUR

RNP 5MKD

Not publishedCHE

RNP 5SWE

Not publishedESP

RNP 5SVN

RNP 5SVK

RNP 5SRB / MNE

RNAV 5ROU

RNAV 5PRT

RNAV 5POL

RNAV 5NOR

B-RNAVNLD

RNP 5MDA

RNP 5MLT

RNP 5LTU

RNAV 5LVA

Navigation SpecificationState

Navigation SpecificationNavigation SpecificationAIP ExamplesAIP Examples

RNAV 5

RNP 5

NO navigation specification

B-RNAV

Publication of requirement for carriage of RNAV 5 Publication of requirement for carriage of RNAV 5 equipmentequipment

Doc 9613, Volume II, Part B, Chapter 2, 2.2 IMPLEMEN TATION CONSIDERATIONS

2.2.5 Publication

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

Carriage of RNAV 5 equipmentCarriage of RNAV 5 equipmentPublication requirementsPublication requirements

Carriage of RNAV 5 equipmentCarriage of RNAV 5 equipmentSummary of publication issues identifiedSummary 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 RNAV-defined 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 sh ould be further considered.

FL095IRL

No defined FLISL

On ATS routesHUN

On ATS routesGRC

FL095 / FL195 - Alpine areaDEU

FL195 (ENR 3.3)GEO

Above FL115

Below FL115 on RNAV-defined routesFRA

FL095FIN

FL095EST

FL095DNK

FL095CZE

FL290CYP

FL195HRV

FL095BGR

FL195BIH

FL095BEL / LUX

FL195AZE

FL195AUT

Controlled airspaceARM

FL110ALB

AIP B-RNAV (RNAV 5) LimitState

FL095ITA

En-route portion of the ATS route structureGBR

On RNAV routesUKR

No defined FLTUR

On ATS routesMKD

No defined FLCHE

No defined FLSWE

FL150 on all ATS routes under IFR and routes in

lower airspace specifically classified as RNAVESP

No defined FLSVN

FL125 on all ATS routesSVK

FL145SRB / MNE

No defined FLROU

On ATS routesPRT

Polish airspacePOL

FL095NOR

FL095NLD

FL245 on all ATS routesMDA

FL095MLT

FL095LTU

FL095LVA

AIP B-RNAV (RNAV 5) LimitState

Carriage of RNAV 5 equipmentCarriage of RNAV 5 equipmentSummary of AIP GEN 1.5Summary of AIP GEN 1.5

17/03/201417/03/2014

RecommendationsRecommendations

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.