Page tree
Skip to end of metadata
Go to start of metadata


The temporary closure of an airport or heliport. The closure can be total (any traffic is forbidden) or partial (with the exception of particular operations, flights or aircraft categories).


  • this scenario does not cover the temporary addition of a supplementary restriction to the airport availability, such as "closed for aircraft heavier than...". This will be dealt with in a separate scenario;

  • this scenario does not cover the temporary change of the operational hours of an airport/heliport. Such situations will be covered by a different scenario;

  • this scenario does not cover the situation when the airport is operating normally, but subject to a reason for caution (such as "grass cutting in progress", etc.). Such situations will be covered through a different scenario.

On this page

Event data

The following diagram identifies the information items that are usually provided by a data originator for this kind of event. Note that the "excepted operations" branch is optional, but can be used more than once. A similar situation occurs for the aircraft/flight branch, where the "other combination" can be used to return and insert additional aircraft/flight conditions.

input = designator [name] ["closure reason"]\n
{"excepted operation" ["PPR time" ["PPR details"]] [["aircraft"] ["flight"] {"other combination" ["aircraft"] ["flight"]}] } \n
"start time" "end time" [schedule] \n

The following table 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


AIXM mapping


The published designator of the airport/heliport concerned. This information, in combination with eventually the name is used to identify the airport/heliport.



The published name of the airport/heliport. This information, in combination with the designator is used to identify the airport/heliport.

closure reason

The reason for the airport/heliport closure.

AirportHeliport/AirportHeliportAvailability.annotation with propertyName="operationalStatus" and purpose="REMARK". Note that the property "warning" of the AirportHeliportAvailability class is not used here because it represents a reason for caution when allowed to operate at the airport, not a reason for a closure.

excepted operation

The description of one or more operations (such as "alternate landing") that are exceptionally permitted at the airport/heliport during its closure.

AirportHeliport/..Availability/..Usage.operation with the following list of values CodeOperationAirportHeliportType

PPR time

The value (minutes, hours, days) of the prior permission request associated with the permitted operation.

AirportHeliport/..Availability/..Usage/.priorPermission with attribute uom specified.

PPR details

Additional information concerning the prior permission requirement.

AirportHeliport/..Availability/..Usage.annotation with propertyName="priorPermission" and purpose="REMARK"


The description of one or more aircraft (such as "helicopter") types that are exceptionally permitted at the airport/heliport during it's closure.

AirportHeliport/..Availability/..Usage/..selection/..AircraftCharacteristics Note that only certain properties can be used in this scenario. See data validation rules for details.


The description of one or more type of flight categories (such as "emergency") that are exceptionally permitted at the airport/heliport during it's closure.


other combination

Another combination of aircraft/flight characteristics that are excepted from the closure.

AirportHeliport/..Availability/..Usage/ConditionCombination.logicalOperator with its value set to "OR".

start time

The effective date & time when the airport closure starts. This might be further detailed in a "schedule".

Airport/AirportTimeSlice/TimePeriod.beginPosition, Event/EventTimeSlice.validTime/timePosition and Event/EventTimeSlice.featureLifetime/beginPosition

end time

The end date & time when the airport closure ends.

Airport/AirportTimeSlice/TimePeriod.endPosition and Event/EventTimeSlice.featureLifetime/endPosition also applying the rules for {{Events with estimated end time}}


A schedule might be provided, in case the airport/heliport is effectively closed according to a regular timetable, within the overall closure period.

AirportHeliport/..Availability/Timesheet/...according to the rules for {{Schedules}}


A free text note that provides further details concerning the airport closure.

AirportHeliport/..Availability.annotation with purpose=”REMARK”

Assumptions for baseline data

It is assumed that information about the aerodrome already exists in the form of AirportHeliport BASELINE TimeSlice(s) covering the complete period of validity of the event, for which the baseline availability is coded as specified in the Coding Guidelines for the (ICAO) AIP Data Set.

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.


Data encoding rule


The temporary closure of an airport/heliport shall be encoded as:

  • a new Event with a BASELINE TimeSlice (encoding=”DIGITAL”, scenario=”AD.CLS”, version=”2.0”), for which a PERMDELTA TimeSlice may also be provided; and

  • a TimeSlice of type TEMPDELTA for the affected AirportHeliport feature, for which the "event:theEvent" property points to the Event instance created above.


One AirportHeliportAvailability element having operationalStatus=CLOSED shall be included in the AirportHeliport TEMPDELTA.


If the airport/heliport is "closed except for" specified operations, flight and/or aircraft categories, all specified excepted operations shall be encoded as AirportHeliportUsage child elements with:

  • either type=PERMIT, if there is no prior permission requirement;

  • or type=CONDITIONAL, if a prior permission requirement was specified. Note that this implies that a "closed" airport/heliport can still allow certain particular operations.


If a unique flight or aircraft are specified as being excepted, they shall be encoded as one ConditionCombination with logicalOperator="NONE".


Each pair of flight and aircraft conditions specified as being excepted shall be encoded as one ConditionCombination with logicalOperator="AND".


If the "other combination" branch is used, then a root ConditionCombinations element shall be encoded having logicalOperator="OR" and each pair of flight/aircraft included as a sub-condition (with logicalOperator="AND", see ER-05).


For every AirportHeliportUsage encoded, the aixm:operation shall be specified.

ER-08If PPR time is specified, the uom attribute shall also be specified.


If the airport 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 AirportHeliportAvailability of the AirportHeliport TEMPDELTA Timeslice. See the rules for Event Schedules.


In accordance with the AIXM Temporality Concept (see sections 3.4 and 3.5 in version 1.0), the AirportHeliportAvailability elements included in the TEMPDELTA completely replace all the BASELINE AirportHeliportAvailability information, during the TEMPDELTA time of applicability. Therefore, if the closure only concerns certain times, then the other times, when the airport/heliport eventually remains subject to the availability conditions of the Baseline data, shall be explicitly included in the TEMPDELTA (associated with an AirportHeliportAvailability with status= ‘NORMAL’).

The calculation of the necessary additional AirportHeliportAvailability elements to be included in the TEMPDELTA shall be automatically done by the applications implementing this specification. All AirportHeliportAvailabilty elements that are copied from the BASELINE data for completeness sake shall get an associated Note with purpose=REMARK and the text="Baseline data copy. Not included in the NOTAM text generation". This is based on the current NOTAM practice which consists of including in the NOTAM only the changed information and not explicitly including the static data that remains valid during the NOTAM applicability.

It is recommended that the input interface provides a "calendar" view of the airport closure, enabling the operator to graphically check the availability at different times, such as in the example below:

In the calendar view, the Baseline information that remains valid during the Event validity time shall be visibly identified from the information that is specific to the Event, for example by using a different colour fill pattern.


The type of operations that do not match a pre-defined value in the CodeOperationAirportHeliportType shall be encoded as follows:

  • emergency medical evacuation -> operation=’OTHER:MEDEVAC’

  • fire fighting flights -> operation=’OTHER:FIRE_FIGHTING’


Following coding examples can be found on GitHub (links attached):

  • No labels