Versions Compared

Version Old Version 7 New Version 8
Changes made by

Wolfgang Scheucher

Manfred Beckmann

Saved on

Key

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

...

Note
titleNote
There are several open questions/issues reagarding about the encoding of this information, in regard to 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.

...

Warning
titlePANS-AIM Issue
It is not clear what is the difference between the properties Navigation specification and Navigation performance requirements, Both seems to be used to provide  provide the same information, e.g, RNAV 10, RNP 4, etc.

...

Warning
titleAIXM 5.1.1 issue

AIXM 5.1.1 provides 2 two attributes regarding navigation specifications for a RouteSegment. Both of them seem to be insufficiant insufficient to code the designation of the PBN specification.

  • navigationType is basically used to encode if the route is 'CONV 'or 'RNAV', but actually 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 an 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.