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 18 Next »

The ATS unit providng service for an airspace is not part of the minimum AIP data set but required in ENR 3:

an indication of the controlling unit, its operating channel and, if applicable, its logon address, SATVOICE number, and any navigation, RCP and RSP specification(s) limitations.

AIXM 5.1.1 issue

In AIXM 5.1.1, SATVOICE number, and any navigation, RCP and RSP specification(s) limitations cannot be encoded, except by using a Note.

Thus, it is considered conditional data.

AIXM does not provide a direct relationship between Unit and RouteSegment class.

The concerned Unit shall be encoded independently. According to the PANS-AIM Appendix 1 (Aeronautical Data Catalogue), at least the name shall be provided.

In addition, a Service provided by the Unit shall be encoded. The Service class has several specialised classes that have an association to a RoutePortion, i.e. as there is no direct relationship to RouteSegment corresponding RoutePortion has to be encoded. One or more of these services may be provided for the same RoutePortion.

  • AirTrafficControlService
  • InformationService
  • SearchRescueService

The type of service provided may be defined by the attribute Service.type, or it may be included in the Service.name, or it may be included in the Unit.name.

Open Question

Which of the 3 options shall be laid down as coding rule?

The operation channel is encoded using the RadioCommunicationChannel class. The attribute frequencyTransmission and if applicable frequencyReception will carry the corresponding value and uom (see also Radio Communication Channel).

The RadioCommunicationChannel has to be referenced by the adequate Service.

According to the PANS-AIM Appendix 1 (Aeronautical Data Catalogue) a specified code used for data link logon to the controlling ATS unit shall be provided if applicable.

AIXM 5.1.1 issue

Depending on the specialised Service class, different ways of encoding this information are provided by AIXM. A consolidation may be needed!
  • The AirTrafficControlService class contains two relevant attributes: dataLinkEnabled and dataLinkChannel.
  • The InformationService class contains one relevant attribute: dataLink.
  • The SearchRescueService class does not contain any relevant attribute.

However, via the ContactInformation class related to the Service class, corresponding attributes of the OnlineContact class may be used to encode that information. The code list for the network attribute contains a value 'ACARS'; which is defined as

Aircraft Communications Addressing and Reporting System. A datalink system that enables ground stations (airports, aircraft maintenance bases, etc.) and commercial aircraft to communicate without voice using a datalink system.

The linkage and protocol attribute may then be used to define the details about the logon address.

The figure below shows how the information about the controlling unit is published in an AIP:

Coding Rules for Controlling Unit

IdentifierData Encoding RuleJustificationData Verification Rule (UID)Remarks
RTE-401All RouteSegments of a Route should have a related a Service provided by a Unit with the name attribute encoded.Conditional dataTBDRoutePortions have to be defined that cover all RouteSegments of a Route
RTE-402All RouteSegments of a Route should have a related Service that uses a RadioCommunicationChannel with the frequencyTransmission and frequencyRecption attribute encoded.Conditional dataTBD

All RouteSegments of a Route should have a related Service that uses a RadioCommunicationChannel with the frequencyRecption attribute encoded.Conditional data

RTE-404Data link logon address should be encoded if available.Conditional dataTBD
RTE-405If any, SATVOICE number, and any navigation, RCP and RSP specification(s) limitations should be encoded using Note.Conditional dataTBD
  • No labels