Page Table of Content

Introduction

For Runway, PANS-AIM requires some basic properties as part of the minimum AIP data set. These are

designator, nominal length, nominal width, surface type, strength.

Note

For a FATO (see Runway.type) surface type and strength is not required as part of the minimum AIP data set.

The diagram below shows the AIXM classes, including the relevant data types, needed to encode that information:

The Runway class is used to describe the physical area of the runway.

The Runway class is basically used to give the runway a designator and to describe its dimension and surface. Additionally, information regarding the runway strip may be provided.

All other runway facets are described with respect to a RunwayDirection, for example stopways and protection areas; runway direction obstacles; approach lighting; declared distances and runway lighting.

Runway type

In AIXM, the Runway class is used to code the runway for airplanes but also to code the Final Approach and Take-off Area (FATO) for helicopters.

Hence, the Runway.type attribute can take the value 'RWY' or 'FATO'. 'OTHER' shall not be used.

AIXM 5.2 Improvements

A change proposal (AIXM-339) for the next AIXM 5.2 version has been approved by the AIXM Change Control Board, which adds a new code to the codelist CodeRunwayMarkingBasetype.

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

Runway (FATO) designator

The Runway.designator attribute is used to code the full textual designator of the runway, used to uniquely identify it at an aerodrome/heliport. E.g. '09/27', '02R/20L', 'RWY 18'.

The attribute value should reflect the local convention for physical runway naming at the Airport. In particular, it is not necessary to concatenate the runway direction designator to from the physical runway designator, but this is not prohibited.

It is also possible to add a prefix to the designator, e.g. 'RWY-18/36'.

The value for the designator is limited to 16 characters.

The designator for a FATO may also be derived from the FATO bearings or from any Helicopter landing area naming convention that is locally used.

Like for Runways also a prefix can be given, e.g.' FATO-03/21'.

Runway (FATO) Dimension (length & width)

The runway dimension attributes are used to describe the physical dimension of a runway.

The Runway.nominalLength is the declared longitudinal extent of the runway for operational (performance) calculations.

The Runway.nominalWidth is the declared transversal extent of the runway for operational (performance) calculations.

For both attributes a dedicated attribute to provide accuracy information is available, lengthAccuracy and widthAccuracy.

Info: FATO width accuracy

PANS-AIM defines an accuracy for the Runway width but not for the FATO width.

According to ICAO Annex 14, Volume I the runway Strip is:

A defined area including the runway and stopway, if provided, intended:
to reduce the risk of damage to aircraft running off a runway; and
to protect aircraft flying over it during take-off or landing operations

In AIXM 5 dedicated attributes are used to code the strip dimension (viz. lengthStrip and widthStrip). This information is not part of the minimum/conditional AIP data set, but mentioned here in order to differentiate runway dimension from strip dimension.

Surface

The surface specification of a runway is related to the complete runway as a physical element and not related to the different runway directions.

For the runway, PANS-AIM requires to provide the surface type.

In AIXM 5, the SurfaceCharacteristics.composition attribute is used to code the surface type, e.g. asphalt, concrete, grass, etc.

In addition PANS-AIM requires the strength of the runway which shall be provided as Pavement Classification Number (PCN).

For coding the PCN, in AIXM 5 a set of attributes is provided by the SurfaceCharacteristics class.

The SurfaceCharacteristics class groups together more attributes to model the characteristics of an airport surface, such as preparation, surface condition, LCN, SWIL AUW, etc.

For detailed information about the encoding of the PCN and other the surface characteristic attributes & corresponding rules, please refer to topic Surface Characteristics [SCH].

Coding Examples

See parent topic Runway [RWY].

References

Browser not supported