Agenda Item 5: PBN en-route AIP publication issues Meetings Seminars and...Step 1 - Inventory of all inconsistencies identified in routes definition and aeronautical data publication

Agenda Item 5: PBN en-route

AIP publication issues

First Combined ICAO EUR PBN TF & EUROCONTROL RAiSG Meeting

11th - 13th September 2013

ICAO EUR/NAT Office - Paris

Mr. Tihomir Todorov Head of Section Airspace Design

Operations Planning

Network Operations Management Division

Network Manager Directorate

EUROCONTROL

12/09/2013

To present an operational and airspace design view on consistency and

quality of RNAV routes definition and aeronautical data published in

ECAC States AIPs.

To further facilitate proper decisions to be taken in view of harmonization

of PBN AIP publications.

Presentation Objectives

12/09/2013

ECAC States AIP en-route publication issues

12/09/2013

Presentation Source

Document produced by EUROCONTROL

based on ECAC States AIPs and

identifying important en-route publication

issues.

Document released and sent to all ECAC

States on 30th August 2013.

12/09/2013

ICAO Requirements Covered

Annex 15 INTRODUCTION

The object of the aeronautical information service is to ensure the flow of

information/data necessary for the safety, regularity and efficiency of

international air navigation. The role and importance of aeronautical

information/data changed significantly with the implementation of area

navigation (RNAV), performance-based navigation (PBN), airborne

computer-based navigation systems and data link systems. Corrupt or

erroneous aeronautical information/data can potentially affect the safety of

air navigation.

To satisfy the uniformity and consistency in the provision of aeronautical

information/data that is required for the operational use by computer-

based navigation systems, States shall, as far as practicable, avoid

standards and procedures other than those established for international

use.

12/09/2013

EC Requirements Covered

COMMISSION REGULATION (EU) No 677/2011 of 7 July 2011 laying down

detailed rules for the implementation of air traffic management (ATM) network

functions and amending Regulation (EU) No 691/2010, Annex I - The European

Route Network Design (ERND) Function, Part B - Planning principle 9(k) stated

that “The data regarding the changes to projects that require checking for

compatibility and that need to be made available to the Network Manager include,

but are not limited to changes affecting data published in aeronautical information

publications.”.

12/09/2013

Reason, Aim and Scope

Reason

The Operational Stakeholders express regularly concerns regarding various

issues linked to the different publication of airspace data in the State AIPs.

The Network Manager operational systems also experience daily problems with

non-harmonized airspace data publication.

Aim

The aim of this document and activity performed is to achieve:

• harmonisation of ECAC States AIP en-route publication allowing the

Operational Stakeholders to correctly interpret it and properly use available

airspace entities;

• full compliance with ICAO requirements - relevant Annexes and Documents;

• full compliance with European requirements - relevant Commission

Regulations.

Scope

The presented observations are based on actual State AIPs as published in pdf

format (ref. AIRAC 22 AUG 2013) by using EAD PAMS sub-system and cover the

ECAC area of the ICAO EUR/NAT Region.

12/09/2013

Way forward

The following are the steps agreed by NETOPS/6 on the reported airspace AIP publication issues: Step 1 - Inventory of all inconsistencies identified in routes definition and aeronautical

data publication per State.

Step 2 - Consolidation of inconsistencies per subject / issue to detect, if there are any

trends.

Step 3 - Prioritisation of all subjects / issues on the basis of their operational efficiency

impact.

Step 4 - Finalization of required information by the end of August 2013.

Step 5 - Sending via e-mail beginning of September to each individual State/ANSP

NETOPS representative the inconsistencies identified in their AIP with an indication of the priority required in addressing each of the subjects / issues. The AIM/SWIM Team

representatives to be also copied.

Step 6 - A briefing to be provided to the AIM/SWIM - 5 meeting in September 2013.

Step 7 - Feedback/comments required and expected by the NETOPS/7 meeting on 23rd - 24th October 2013.

Following further discussions, comments, suggestions and directives periodical review and

monitoring of the improvements via the NETOPS will be performed. Additional arrangements

to tackle the AIP issues presented and support to States by EUROCONTROL might be

expected.

12/09/2013

Area Navigation (RNAV) routes

12/09/2013

a. Proper publication

12/09/2013

ATS route. A specified route designed for channelling the flow of traffic as necessary for the provision of air traffic service.

Note 1.- The term “ATS route” is used to mean variously, airway, advisory route, controlled or uncontrolled route, arrival or departure route, etc.

Note 2.- An ATS route is defined by route specifications which include an ATS route designator, the track to or from significant points (waypoints),

distance between significant points, reporting requirements and, as determined by the appropriate ATS authority, the lowest safe altitude.”

Area navigation route. An ATS route established for the use of aircraft capable of employing area navigation.

Area navigation (RNAV). A method of navigation which permits aircraft operation on any desired flight path within the

coverage of ground- or space-based navigation aids or within the limits of the capability of self-contained aids, or a

combination of these.

Note.- Area navigation includes performance-based navigation as well as other operations that do not meet the definition of performance-based

navigation.

B-RNAV basic-RNAV, also referred to as RNAV 5

Navigation specification. A set of aircraft and aircrew requirements needed to support Performance-based Navigation

operations within a defined airspace. There are two kinds of navigation specification:

RNAV specification. A navigation specification based on area navigation that does not include the requirement for on-board

performance monitoring and alerting, designated by the prefix RNAV, e.g. RNAV 5, RNAV 1.

RNP specification. A navigation specification based on area navigation that includes the requirement for on-board performance

monitoring and alerting, designated by the prefix RNP, e.g. RNP 4, RNP APCH.

Note: The Performance-based Navigation Manual (Doc 9613), Volume II, contains detailed guidance on navigation specifications.

Performance-based navigation (PBN). Area navigation based on performance requirements for aircraft operating along an

ATS route, on an instrument approach procedure or in a designated airspace.

Note.- Performance requirements are expressed in navigation specifications (RNAV specification - does not include the requirement for performance

monitoring and alerting, RNP specification - includes the requirement for performance monitoring and alerting) in terms of accuracy, integrity,

continuity, availability and functionality needed for the proposed operation in the context of a particular airspace concept.

RNAV 5 An RNAV specification having a lateral navigation accuracy of 5 nautical miles. RNAV 5 is also referred to as B-

RNAV in the EUR.

Waypoint. A specified geographical location used to define an area navigation route or the flight path of an aircraft

employing area navigation. Waypoints are identified as either: Fly-by waypoint or Flyover waypoint.

RNAV routes ICAO Related Definitions

12/09/2013

Doc 9613, Volume II, Part B, Chapter 2, 2.2 IMPLEMENTATION CONSIDERATIONS

2.2.1 NAVAID infrastructure

2.2.1.1 States may prescribe the carriage of RNAV 5 on specific routes or for specific areas/flight levels of their airspace.

2.2.1.2 RNAV 5 systems permit aircraft navigation along any desired flight path within the coverage of station-referenced

NAVAIDs (space or terrestrial) or within the limits of the capability of self-contained aids, or a combination of both methods.

2.2.1.3 RNAV 5 operations are based on the use of RNAV equipment which automatically determines the aircraft position in

the horizontal plane using input from one or a combination of the following types of position sensors, together with the means

to establish and follow a desired path:

a) VOR/DME;

b) DME/DME;

c) INS or IRS; and

d) GNSS.

2.2.1.4 The ANSP must assess the NAVAID infrastructure in order to ensure that it is sufficient for the proposed operations,

including reversionary modes. It is acceptable for gaps in NAVAID coverage to be present; when this occurs, route spacing and

obstacle clearance surfaces need to take account of the expected increase in lateral track-keeping errors during the “dead

reckoning” phase of flight.

_____________________________________________________________________________________________________

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.

RNAV routes ICAO RNAV 5 Requirements

12/09/2013

Annex 15, Appendix 1 - Amendment 36 / 18 NOV 2010

ENR 3.1 / 3.2 - ATS route 2):

Tracks or VOR radials to the nearest degree,

Geodesic distance to the nearest tenth of a kilometre or tenth of a nautical

mile between each successive designated significant point and, in the case of

VOR radials, changeover points.

ENR 3.3. - RNAV route 2):

In respect of waypoints defining a VOR/DME 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).

RNAV routes Aeronautical Data Requirements

12/09/2013

RNAV routes Aeronautical Data Requirements

Annex 15 - 13th Edition

Amendment 36 / 18 NOV 2010 Amendment 37 / 14 NOV 2013

ENR 3.3 Area navigation routes

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 a VOR/DME area navigation route,

additionally as applicable:

a) station identification of the reference VOR/DME;




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

6) 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.

ENR 3.3 Area navigation routes

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;




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

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.

12/09/2013

Annex 11, Appendix 1

Designators for ATS routes and navigation specifications

The purpose of a system of route designators and navigation specification(s) applicable to

specified ATS route segment(s), route(s) or area is to allow both pilots and ATS, taking into account

automation requirements:

a) to make unambiguous reference to any ATS route without the need to resort to the use of

geographical coordinates or other means in order to describe it;

b) to relate an ATS route to a specific vertical structure of the airspace, as applicable;

c) to indicate a required level of navigation performance accuracy, when operating along an ATS

route or within a specified area; and

d) to indicate that a route is used primarily or exclusively by certain types of aircraft.

Selection of the letter shall be made from those listed hereunder:

a) A, B, G, R for routes which form part of the regional networks of ATS routes and are not area

navigation routes;

b) L, M, N, P for area navigation routes which form part of the regional networks of ATS routes;

c) H, J, V, W for routes which do not form part of the regional networks of ATS routes and are

not area navigation routes;

d) Q, T, Y, Z for area navigation routes which do not form part of the regional networks of ATS

routes.

RNAV routes Publication Requirements - Routes Designation

12/09/2013

RNAV routes Publication Requirements - Doc 8126, Specimen AIP

Routes Designation Required

Aeronautical Data Required

12/09/2013

The ICAO Resolution at the 36th Assembly and the publication of ICAO’s PBN Concept in 2008 effectively triggered the

launch of PBN. The ICAO Resolution was updated at the 37th Assembly and marks a significant step in that it reflects

international concordance as to high-level goals and ambitions for global uptake of PBN. The 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).

Annex 15 provides the requirement for publication and detailed description of RNAV routes. Such 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 4 States are complying 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. Template in ENR 3.3 is either same as in ENR 3.1 or ENR 3.2. 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.

There are still States referencing to the airway width or lateral limits which in PBN environment is difficult to be accepted as each RNAV route has normally its defined navigation specification. It represents a RNAV containment value not a

protected airspace around the centre line of the route to allow for possible deviations as required for ATS routes defined by

VOR.

Harmonized publication for all RNAV routes and publication location (AIP placeholder) in ENR 3.3 is required. States shall adapt the aeronautical data for RNAV routes in accordance with Annex 15.

RNAV routes Summary of publication issues identified

12/09/2013

RNAV routes AIP Examples

Doc 8126 template

AIP publication compliant with Annex 15 and Doc 8126

12/09/2013


Partial Doc 8126 template

Header of the template used compliant with Annex 15 and Doc 8126

Non-compliant aeronautical data

with Annex 15 and Doc 8126

12/09/2013


Partial Doc 8126 template + width

Header of the template used partially compliant with Annex 15 and Doc 8126

Non-compliant aeronautical data

with Annex 15 and Doc 8126

12/09/2013

Significant points Interpretation in expression

In one ECAC State AIP for 7 MAR 2013 publication contains information in brackets after some selected

name-code designators.

Following a short analyses it was concluded that this is “bearing to the nearest degree from the reference

VOR/DME as the waypoint is not collocated with it”

Such aeronautical data is required by ICAO but the place is completely wrong. See also slide 13 for RNAV

routes Aeronautical Data Requirements.

NIZ 150

192

12/09/2013

b. Navigation specification (RNP/RNAV)

12/09/2013

Doc 7030, Chapter 4 NAVIGATION, 4.1.1 Area navigation (RNAV) specifications

4.1.1.2 RNAV 5 Area of applicability

4.1.1.2.3 The requirements included in the RNAV 5 (B-RNAV) specification for en-route operations shall

apply to all such operations conducted under IFR on the entire ATS route network in the following

flight information regions (FIRs)/upper flight information regions (UIRs) as specified in the relevant State

AIPs: Amsterdam, Ankara, Athinai, Baku, Barcelona, Bodø, Bordeaux, Bratislava, Bremen, Brest,

Brindisi, Bruxelles, Bucuresti, Budapest, Canarias (AFI area of applicability), Casablanca, Chisinau,

Dnipropetrovs’k, France, Hannover, Istanbul, København, Kyiv, Langen, Lisboa, Ljubljana, London,

L’viv, Madrid, Malta, Marseille, Milano, München, Nicosia, Odessa, Oslo, Paris, Praha, Reims,

Rhein, Riga, Roma, Rovaniemi, Scottish, Shannon, Simferopol, Skopje, Sofia, Stavanger, Sweden,

Switzerland, Tallinn, Tampere, Tbilisi, Tirana, Trondheim, Tunis, Varna, Vilnius, Warszawa, Wien,

Yerevan, Zagreb.

Doc 9613, Volume I, Part A, Chapter 2, 2.3 Airspace concepts by area of operation

2.3.2 Continental en-route airspace concepts are currently supported by RNAV and RNP applications. RNAV 5 is used in the Middle East (MID), South American (SAM) and European (EUR) Regions but as

of the publication date of this manual, it is designated as B-RNAV (Basic RNAV) in Europe and RNP 5 in the Middle East (see 1.2.5.5). In the United States, an RNAV 2 application supports an en-route

continental airspace concept. At present, continental RNAV applications support airspace concepts which

include radar surveillance and direct controller pilot communication (voice). Within the next few years, en

route Advanced RNP operations are expected in Europe whilst RNP 0.3 operations for helicopters and slow moving aircraft are expected in the United States.

Navigation Specification ICAO en-route requirements

12/09/2013

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

Navigation Specification ICAO en-route requirements

12/09/2013

Annex 15, Appendix 1

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;


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.

Navigation Specification Publication requirements

12/09/2013

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 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 described the navigation specification of their area navigation

routes as RNP 5 while only 7 States as RNAV 5. Two States published B-RNAV while for 7

States there is no description in ENR sub-section and sometimes reference to GEN 1.5 is

made.

Doc 8126 template requires use of term/abbreviation (RNP/RNAV) but currently terms RNP

Type or PBN Specification or RNP/RNAV Type are used.

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.

12/09/2013

Navigation Specification Summary of publication issues identified

State Navigation Specification

ALB RNP 5

ARM RNP 5

AUT RNP 5

AZE RNAV 5

BEL / LUX B-RNAV

BIH RNP 5

BGR RNP 5

HRV RNP 5

CYP RNP 5

CZE Not published

DNK RNP 5

EST RNP 5

FIN RNP 5

FRA Not published

GEO RNP 5

DEU Not published

GRC RNP 5

HUN RNP 5

ISL RNP 2

IRL RNAV 5

State Navigation Specification

ITA RNP 5

LVA RNAV 5

LTU RNP 5

MLT RNP 5

MDA RNP 5

NLD B-RNAV

NOR RNAV 5

POL Not published

PRT RNAV 5

ROU RNAV 5

SRB / MNE RNP 5

SVK RNP 5

SVN RNP 5

ESP Not published

SWE RNP 5

CHE Not published

MKD RNP 5

TUR Not published

UKR RNP 5

GBR RNAV 5

12/09/2013

Navigation Specification AIP Examples

RNAV 5

RNP 5

NO navigation specification

B-RNAV

12/09/2013

Other AIP publication issues

12/09/2013

AIP sub-section GEN 1.5 Carriage of RNAV 5 equipment


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.

12/09/2013

AIP sub-section GEN 1.5 Summary of publication issues identified

Other important issue not covered by this document is the definition of provision of area navigation

within the States in ECAC area published in GEN 1.5 “Aircraft instruments, equipment and flight

documents”.

With effect from 23 APR 1998, for en-route operations, aircraft, other than State aircraft, operating

on the ATS routes, above the lowest applicable flight level as published by States, shall be

equipped with RNAV meeting RNP 5 (B-RNAV or RNAV 5).

The definition of this B-RNAV (RNAV 5) airspace 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.

The table in next slide represents the AIP publication where the area navigation is applied within each ECAC State.

Harmonized AIP publication of RNAV 5 application should be further considered.

12/09/2013

State AIP B-RNAV (RNAV 5) Limit

ALB FL110

ARM Controlled airspace

AUT FL195

AZE FL195

BEL / LUX FL095

BIH FL195

BGR FL095

HRV FL195

CYP FL290

CZE FL095

DNK FL095

EST FL095

FIN FL095

FRA Above FL115

Below FL115 on RNAV-defined routes

GEO FL195 (ENR 3.3)

DEU FL095 / FL195 - Alpine area

GRC On ATS routes

HUN On ATS routes

ISL No defined FL

IRL FL095

State AIP B-RNAV (RNAV 5) Limit

ITA FL095

LVA FL095

LTU FL095

MLT FL095

MDA FL245 on all ATS routes

NLD FL095

NOR FL095

POL Polish airspace

PRT On ATS routes

ROU No defined FL

SRB / MNE FL145

SVK FL125 on all ATS routes

SVN No defined FL

ESP FL150 on all ATS routes under IFR and routes in

lower airspace specifically classified as RNAV

SWE No defined FL

CHE No defined FL

MKD On ATS routes

TUR No defined FL

UKR On RNAV routes

GBR En-route portion of the ATS route structure

AIP sub-section GEN 1.5 Summary of publication issues identified

12/09/2013

AIP sub-section GEN 1.5 AIP examples

12/09/2013

Recommendations

The participants at First 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.

12/09/2013 35

Q U E S T I O N S