Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel
titlePage Table of Content

Table of Contents

Introduction

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

...

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.

Runway 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 form 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.

...

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

Runway Dimension (length & width)

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

...

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

Info
titleInfo: FATO width accuracy

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

According to ICAO Annex 14, Volume  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 form 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.

...

titleNote

...

.

...

For the runway, PANS-AIM requires to provide the surface type and its strength defined by a Pavement Classification Number (PCN).

...

...

In AIXM 5, the the SurfaceCharacteristics.composition attribute  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 preperationpreparation, 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 Rules for Basic Data for Runway

IdentifierData Encoding RuleJustificationData Verification Rule (UID)Remarks
RWY-101The Runway.type attribute is mandatory.Data consistencyTBDIt
Note
titleNote

For runway no type property is defined by ICAO Annex 15 or PANS-AIM (as FATO and Runway are handled as separate subjects).

However, in the AIXM 5 Runway and FATO are modelled as one feature. Hence, it is necessary to identify, if the data is for a Runway or a FATO by using the corresponding type attribute.

RWY-102The Runway.designator attribute is mandatory.Minimum AIP data setAIXM-5.1_RULE-1A3387
RWY-103The Runway.nominalLength attribute is mandatory.Minimum AIP data setTBD
RWY-104The Runway.nominalWidth attribute is mandatory.Minimum AIP data setTBD
RWY-105The Runway.lengthAccuracy attribute is mandatory.Minimum AIP data setTBD
RWY-106The Runway.widthAccuracy attribute is mandatory.Minimum AIP data setTBD
RWY-108For Runway, the SurfaceCharacteristics.composition attribute is mandatory.Minimum AIP data setTBD
RWY-109For Runway, the SurfaceCharacteristics.classPCN attribute is mandatory.Minimum AIP data setTBD
RWY-110For Runway, the SurfaceCharacteristics.pavementTypePCN attribute is mandatory.Minimum AIP data setTBD
RWY-111For Runway, the SurfaceCharacteristics.pavementSubgradePCN attribute is mandatory.Minimum AIP data setTBD
RWY-112For Runway, the SurfaceCharacteristics.maxTyrePressurePCN attribute is mandatory.Minimum AIP data setTBD
RWY-113For Runway, the SurfaceCharacteristics.evaluationMethodPCN attribute is mandatory.Minimum AIP data setTBD
RWY-114The distance between the first and the last RunwayCentrelinePoint associated to the same Runway cannot exceed 10 KM.EADTBD
RWY-115A Runway of type 'RWY' cannot be associated with an AirportHeliport with type ''HP'.AIXM 4.5 Business Rules / Data consistency ruleAIXM-5.1_RULE-E8E90
RWY-116

 Each Runway shall have assigned associatedAirportHeliport value.

AIXM 4.5 / Minimal data ruleAIXM-5.1_RULE-1A33AC
RWY-117If coded, the value of the Runway.lengthAccuracy shall be 1 M or less.PANS-AIMTBD
RWY-118If coded, the value of the Runway.widthAccuracy shall be 1 M or less.PANS-AIMTBD
issue
Warninginfo
titleInfo

In PANS-AIM

For FATO width

no accuracy is

missing in the data calatogue

defined for the FATO width.

RWY-119If coded, the value of the Runway.nominalLength shall be published with at least 1m or 1ft  resolution.PANS-AIM

TBD

Note: the only thing that can be verified in this case is the use of either FT or M as unit on measurement. A value such as "3000 M" cannot be assumed to break this rule because maybe this is the exact elevation value.


RWY-120

If coded, the value of the Runway.nominalWidth shall be published with at least 1m or 1ft  resolution.

PANS-AIM

TBD

Note: the only thing that can be verified in this case is the use of either FT or M as unit on measurement. A value such as "40 M" cannot be assumed to break this rule because maybe this is the exact elevation value.


Coding Examples

See parent topic Runway [RWY].

References