Page Comparison

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, (such as RNAV 5 , RNP 4 etc.).  'OTHER' could be used to define the missing value for PBN Navigation SpecificationsSpecification, i.e.g. 'RNAV 5' or 'RNP 4 'OTHER:RNP'.
• requiredNavigationPerformance is intended to code RNP values (any two-digit value with one decimal is allowed!). RNAV values are not considered.

This has been raised as an issue to the AIXM CCB to be considered for AIXM 5.2. For the status of the Change Proposal see AIXM-135

Proposed Workaround for AIXM5.1(.1):

Code for navigationType 'RNAV' or 'OTHER:RNP'

and for requiredNavigationPerformance the navigation acurracy, e.g. '5' or '4'.

The two concatenated values would result in the corresponding RNAV or RNP navigation specification, e.g. RNAV 10 or RNP 4, according to the values defined in ICAO Doc 9613 (PBN Manual).

Note: This workaround does not work for one PBN navigation specifications applied for en-route: The Advanced RNP (A-RNP). For this particular case an corresponding Note may be provided.

In an AIP this information is published in the ENR 3 section.

Image RemovedImage Added