[2.0] [RWY.CLS] Runway - closure
Definition
The temporary closure of a runway or of one of its landing and take-off directions.
Notes:
this scenario covers the closure of both the entire runway (all landing directions) or of a single landing direction;
for the temporary closure of a portion of a runway, refer to runway portion closure scenario RWE.CLS
this scenario does not cover "partial" closures (exception of particular operations, flights or aircraft categories) or supplementary restrictions. The RWY.LIM scenario shall be used in that situation;
this scenario does not cover the temporary change of the operational hours of a runway;
this scenario does not cover the situation when the runway is operating normally, but subject to a reason for caution (such as "grass cutting in progress", etc.).
Event data
The following diagram identifies the information items that are usually provided by a data originator for this kind of event.
The table below provides more details about each information item contained in the diagram. It also provides the mapping of each information item within the AIXM 5.1.1 structure. The name of the variable (first column) is recommended for use as label of the data field in human-machine interfaces (HMI).
Data item | Value | AIXM mapping |
|---|---|---|
airport designator | The published designator of the airport where the runway is located, used in combination with airport name, runway or landing direction in order to identify the runway concerned. | AirportHeliport.designator |
airport name | The published name of the airport where the runway is located, used in order to identify the runway concerned. | AirportHeliport.name |
runway | The published designator of the runway (or FATO) concerned. This information is used in combination with the airport designator/name in order to identify the runway (or FATO), for which it is assumed that both landing directions are concerned by the closure. | Runway.designator |
runway direction | The published designator of the runway direction concerned. This information is used in combination with the airport designator/name in order to identify the concerned landing direction. | RunwayDirection.designator |
runway surface composition | In cases where there are two runways with the same designator but different surfaces (for instance RWY 07/25, one concrete and the second gravel or grass), the surface composition needs to be provided. | Runway.surfaceProperties/SurfaceCaracteristics.composition |
status=CLOSED | The operational status of the runway. In this scenario, it is only possible to indicate a complete closure. | RunwayDirection/ManoeuvringAreaAvailability.operationalStatus |
closure reason | The reason for the runway closure. | RunwayDirection/ManoeuvringAreaAvailability.annotation with propertyName="operationalStatus" and purpose="REMARK". Note that the property "warning" of the ManoeuvringAreaAvailability class is not used here because it represents a reason for caution when allowed to operate on the runway, not a reason for a closure. |
start time | The effective date & time when the runway closure starts. This might be further detailed in a "schedule". | RunwayDirection/RunwayDirectionTimeSlice/TimePeriod.beginPosition, Event/EventTimeSlice.validTime/timePosition and Event/EventTimeSlice.featureLifetime/beginPosition |
end time | The end date & time when the runway closure ends. | RunwayDirection/RunwayDirectionTimeSlice/TimePeriod.endPosition and Event/EventTimeSlice.featureLifetime/endPosition also applying the rules for Events with estimated end time |
schedule | A schedule might be provided, in case the runway is effectively closed according to a regular timetable, within the overall closure period. | RunwayDirection/ManoeuvringAreaAvailability/Timesheet/...according to the rules for Schedules |
note | A free text note that provides further details concerning the runway closure. | RunwayDirection/ManoeuvringAreaAvailability.annotation with purpose=”REMARK” |
Assumptions for baseline data
It is assumed that following BASELINE TimeSlices covering the entire duration of the event exist and have been coded as specified in the Coding Guidelines for the (ICAO) AIP Data Set:
AirportHeliport BASELINE as specified in the Basic Data for Airport/Heliport,
Runway BASELINE according to the encoding rules for Basic Data for Runway;
RunwayDirection BASELINE according to the encoding rules for Basic Data Runway Direction.
Data encoding rules
The data encoding rules provided in this section shall be followed in order to ensure the harmonisation of the digital encodings provided by different sources. To the maximum possible extent, the compliance with these encoding rules shall be verified with automatic data validation rules. For this purpose, the UID of the corresponding AIXM Business Rule, where applicable, appears in the first column.
Identifier / UID | Data encoding rule |
|---|---|
RWY.CLS.01 (213BD0, 1F47D0) | The temporary closure of a runway shall be encoded as a new Event with a ‘BASELINE’ Timeslice (scenario=”RWY.CLS”, version=”2.0”) for which a PERMDELTA TimeSlice may also be provided |
RWY.CLS.02 (1F5F51, 1F4BBA) | A TimeSlice of type TEMPDELTA shall be added for each affected RunwayDirection feature, for which the "event:theEvent" property points to the Event instance created above. Note that in case a full runway is concerned by the closure, then a TEMPDELTA shall be encoded for each of its RunwayDirection features. |
RWY.CLS.03 (1F4FA2, 1F538A) | First, all the BASELINE availability.ManoeuvringAreaAvailability (with operationalStatus=NORMAL), if present, shall be copied in the TEMPDELTA (see Usage limitation and closure scenarios). Then, an additional availability.ManoeuvringAreaAvailability element having operationalStatus=CLOSED shall be coded in the RunwayDirection TEMPDELTA. |
RWY.CLS.04 (N/A) | If the runway closure is limited to a discrete schedule within the overall time period between the "start time" and the "end time", then this shall be encoded using as many as necessary timeInterval/Timesheet properties for the ManoeuvringAreaAvailability having operationalStatus=CLOSED in RunwayDirection TEMPDELTA Timeslice. See the rules for Event Schedules. |
RWY.CLS.05 (212848, 213FB8, 1F72C8, 214B70) | The system shall automatically identify the FIR where the AerodromeHeliport is located. This shall be coded as corresponding concernedAirspace property in the Event |
RWY.CLS.06 (1F7A9A) | The AirportHeliport concerned by the closure shall also be coded as concernedAirportHeliport property in the Event. |
Examples