Airport/Heliport [AHP]

Owned by Wolfgang Scheucher
Last updated: 2022 Sept 23 by georgiana.andrei04

Purpose and Scope

These pages contain the coding guidelines for the minimum and conditional data items of the Aerodrome/Heliport subject as defined in PANS-AIM.

A defined area on land or water (including any buildings, installations and equipment) intended to be used either wholly or in part for the arrival, departure and surface movement of aircraft.

AIP context

In an AIP, Aerodrome/Heliport information may be found in the following main sections:

  • AD 2. AERODROMES
  • AD 3. HELIPORTS

The information required to be provided by PANS-AIM is mainly published in AD 2.1/3.1 & AD 2.2/3.2.

AIXM Model Overview

The figure below shows the main AIXM 5 classes used for the airport/heliport concept.

The main class in this AIXM model is the AirportHeliport containing the basic data, such as the name and designator.

The designator of the airport/heliport may be the same as its ICAO location indicator (if any) or the IATA code (if any). In case the airport/heliport has none, an artificial designator will be coded.

The type attribute is used to define if the feature is an airport or a heliport, etc..

Additional attributes are used for encoding information e.g. about the elevation of the airport, its magnetic variation and certification details.

The AirportHeliport may serve one or more City.

The AirportHeliport will have one ARP (Aerodrome Reference Point) defined by a Point.

The AirportHeliport may be underResponsibilityOf an OrganisationAuthority. The AirportHeliportResponsibilityOrganisation class characterises the role of the organisation or authority which is responsible for the airport/heliport (e.g it owns the airport, or provides aeronautical information).

ContactInformation may be provided for the AirportHeliport and/or OrganisationAuthority.

The availability of the AirportHeliport, such as the type of traffic permitted, may be provided via the AirportHeliportAvailability and its related classes.

AIXM 5.2 Improvements

A change proposal (AIXM-391) for the next AIXM 5.2 version has been approved by the AIXM Change Control Board, through which the data type TextNameBaseType is modified, allowing also the use of lowercase characters.

The coding guidelines provided here are aligned with forward/backward conversion rules contained in the AIXM-391 Change Proposal.

AIXM 5.2 Improvements

A change proposal (AIXM-415) for the next AIXM 5.2 version has been approved by the AIXM Change Control Board, which adds a new attribute allowing the designation of an airport having an associated segmented circle marker.

The coding guidelines provided here are aligned with forward/backward conversion rules contained in the AIXM-415 Change Proposal.

AIXM 5.2 Improvements

A change proposal (AIXM-405) for the next AIXM 5.2 version has been approved by the AIXM Change Control Board, which changed multiplicity (0..*) on the OrganisationAuthority side in the association with AirportHeliport, to allow more than one occurence.

The coding guidelines provided here are aligned with forward/backward conversion rules contained in the AIXM-405 Change Proposal.

Coding Examples

See child pages.

Child Pages