For Route Segment, PANS-AIM requires as part of th eminimum 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 is not to be seen as coding guidelines but rather as discussion of 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.
...
| Warning | ||
|---|---|---|
| ||
| 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:
| Warning | ||
|---|---|---|
| ||
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.
Another option would be to code a FlightRestriction for a RoutePortion. A related FlightConditionElement may be encoded with a corresponding AircraftCharacteristic.navigationSpecification. The code list for this attribute CodeNaviagationSpecificationType contains all required values. However, it is not clear if the actual intention of the FlightRestriction model of AIXM is to encode that kind of information. The AIXM definition for FlightRestriction is: A rule meant to regulate the use of the route network, by identifying a set of flights which fulfil a combination of elementary flow conditions and either forbidding them on a particular routing or obliging them to follow one routing out of a set of mandatory alternatives. |
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'.
Coding rules for PBN Requirements for Route Segment
| Identification | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks |
|---|---|---|---|---|
| RSG-501 | The RouteSegment.navigationType attribute is mandatory. | Minimum AIP Data set | TBD | See text above for coding details. |
Coding Examples
Coding examples can be found in the DONLON AIP data set file:
| No. | Description | XPath Expression |
|---|---|---|
| RSG-EX-01 | Route segment with navigation specification | //aixm:RouteSegmentTimeSlice[@gml:id ='RSG_UA4_BARIM_WOB'] |