Versions Compared

Version Old Version 10 New Version Current
Changes made by

Manfred Beckmann

Wolfgang Scheucher

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Image Removed

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 the issues detected
Note
titleNote
Panel
titlePage Table of Content

Table of Contents

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.

...

Indication on the sensor requirements including any navigation specification limitations

...

...

titlePANS-AIM Issue

...

ICAO Doc 9613 (PBN Manual)

  describes the following designation of Navigation Specifications:

Th The following table shows the Application of navigation specification by flight phase:Image Removed:

Image Added

The diagram below shows the AIXM 5.1(.1) classes, including the relevant data types, that may be used to encode that information:

Image Added

Warning
titleAIXM 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, (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 . RNAV values are not considered.

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.
  • (any two-digit value with one decimal is allowed).

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.

Tip
titleAIP context

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

Image Added

Coding Examples

Coding examples can be found in the AIP Data Set - Specimen (DONLON).

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

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

References