Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

For Route Segment, PANS-AIM requires as part of the minimum data set information about the navigation specification and required navigation performance.

Note

There are several open questions/issues about the encoding of this information, regarding both PANS-AIM and AIXM 5. Thus, this page has only limited coding guidelines (work around) and besides this is mainly used to highlight the issues detected.

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

PANS-AIM Issue

It is not clear what is the difference between the properties "Navigation specification" and "Navigation performance requirements". Both seem to be used for providing the same information, e.g, RNAV 10, RNP 4, etc.

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

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!). RNAV values are not considered.

As a workaround, 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 and provide the actual type of RNP or RNAV specification applicable, according to the values defined in ICAO Doc 9613 (PBN Manual).

e.g. 'OTHER:RNAV5' or 'OTHER RNP4'.

AIP context

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

Coding rules for PBN Requirements for Route Segment

IdentificationData Encoding RuleJustificationData Verification Rule (UID)Remarks
RSG-501The RouteSegment.navigationType attribute is mandatory.Minimum AIP Data setTBD
See text above for coding details.

Coding Examples

Coding examples can be found in the DONLON AIP data set file:

No.DescriptionXPath Expression
RSG-EX-01Route segment with navigation specification

//aixm:RouteSegmentTimeSlice[@gml:id ='RSG_UA4_BARIM_WOB']

References


  • No labels