Introduction
For Route Segment, PANS-AIM requires as part of the minimum data set information about the navigation specification and required navigation performance.
For the AIP data set PANS-AIM requires 2 properties related to Performance Based Navigation (PBN) of a route segment.
- "Navigation specification"
Designation of the navigation specification(s) applicable to a specified segment(s) - There are two kinds of navigation specifications:
Required navigation performance (RNP) specification. A navigation specification based on area navigation that includes the requirement for performance monitoring and alerting, designated by the prefix RNP, e.g. RNP 4, RNP APCH.
Area navigation (RNAV) specification. A navigation specification based on area navigation that does not include the requirement for performance monitoring and alerting, designated by the prefix RNAV, e.g. RNAV 5, RNAV 1.
- "PBN requirements"
Area navigation based on performance requirements for aircraft operating along an ATS route, on an instrument approach procedure or in a designated airspace requirements
This property is split into 2 sub-properties
- "Navigation performance requirements"
The navigation accuracy requirement for each PBN (RNAV or RNP) route segment
- "Sensor requirements"
Indication on the sensor requirements including any navigation specification limitations
ICAO Doc 9613 (PBN Manual) describes the following designation of Navigation Specifications:
The following table shows the Application of navigation specification by flight phase:
The diagram below shows the AIXM 5.1(.1) classes, including the relevant data types, that may be used to encode that information:
AIXM 5.1.1 issue 005_RouteSegment.navigationType
AIXM 5.1.1 provides two attributes regarding navigation specifications for a RouteSegment. Both seem to be insufficient to code the designation of the PBN specification.
- navigationType is basically used to encode if the route is 'CONV 'or 'RNAV', but is not intended to code the PBN specification. Although, 'OTHER' could be used to define PBN Navigation Specifications, e.g. 'RNAV 5' or 'RNP 4'.
- requiredNavigationPerformance is intended to code RNP values (any two-digit value with one decimal is allowed).
Status: for AIXM 5.2 see CCB AIXM-135
Workaround for AIXM5.1.1, until the open PBN issue are clarified within the AIXM CCB, the following coding is proposed:
- Use the value 'OTHER' for the attribute RouteSegment.navigationType e.g. 'OTHER:RNAV_5' or 'OTHER RNP_4', according to the values defined in ICAO Doc 9613 (PBN Manual).
- for the attribute requiredNavigationPerformance provide the actual RNP or RNAV value, according to the values defined in ICAO Doc 9613 (PBN Manual).
AIP context
In an AIP this information is published in the ENR 3 section.
Coding rules for PBN Requirements for Route Segment
See coding rules of topic Basic Data of Route Segment.
Coding Examples
Coding examples can be found in the AIP Data Set - Specimen (DONLON).
| No. | Description | XPath Expression |
|---|---|---|
| RSG-EX-01 | Route segment with navigation specification | //aixm:RouteSegmentTimeSlice[@gml:id ='RSG_UA4_BARIM_WOB'] |