The temporary closure of a portion of an area intended to accommodate aircraft for purposes of loading or unloading passengers, mail or cargo, fuelling, parking or maintenance. 


  • this scenario includes the closure of a portion of an apron. It is assumed that the apron portion does not exist in the baseline data, and has to be created for the event;
  • this scenario does not cover the temporary addition of a supplementary restriction to the apron availability, such as "closed for aircraft heavier than...".
  • this scenario does not cover the temporary change of the operational hours of an apron element;
  • this scenario does not cover the situation when the apron element 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. 

input = "airport designator" ["airport name"] "apron name" \n
"apron portion closed geometry" "location and extent description"  \n
"status=CLOSED" ["closure reason"] "start time" "end time" ["schedule"] \n

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


AIXM mapping

airport designator

The published designator of the airport where the apron is located, used in combination with other elements in order to identify the apron portion concerned.


airport name

The published name of the airport where the apron is located, used in order to identify the apron(s) and/or apron portion(s) concerned.

apron name

The published name of the apron concerned. This information is used in combination with the airport designator/name in order to identify the affected  apron(s) and/or apron portion(s)

apron portion closed geometry

The coordinates defining the apron portion to be closed.


location and extent description

Textual description of the closed portion location and extent. 

ApronElement.annotation with propertyName='extent' and purpose='DESCRIPTION'
status=CLOSEDThe operational status of the apron element.ApronElement/ApronAreaAvailability.operationalStatus

closure reason

The reason for the apron portion closure.

ApronElement/ApronAreaAvailability.annotation with propertyName='operationalStatus' and purpose='REMARK'. Note that the property "warning" of the ApronAreaAvailability class is not used here because it represents a reason for caution when allowed to operate on the apron, not a reason for a closure.

start time

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

ApronElement/ApronTimeSlice/TimePeriod.beginPosition, Event/EventTimeSlice.validTime/beginPosition and Event/EventTimeSlice.featureLifetime/beginPosition

end time

The end date & time when the apron closure ends.

ApronElement/ApronTimeSlice/TimePeriod.endPositionEvent/EventTimeSlice.validTime/endPosition and Event/EventTimeSlice.featureLifetime/endPosition also applying the rules for Events with estimated end time


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

ApronElement/ApronAreaAvailability/Timesheet/... according to the rules for Schedules


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

ApronElement.annotation with purpose='REMARK'

Assumptions for baseline data

It is assumed that AirportHeliport BASELINE Timeslice covering the entire duration of the event exist and have been coded as specified in the Coding Guidelines for the (ICAO) AIP Data Set. In addition the information about the Apron already exists in the form of a Apron BASELINE TimeSlice, which contains as a minimum:

  1. a nameand
  2. an association with the AirportHeliport;

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. The compliance with some of these encoding rules can be checked with automatic data validation rules. When this is the case, the number of the encoding rule is mentioned in the data validation rule.


Data encoding rule


The temporary closure of an apron portion shall be encoded as:

  • a new Event with a 'BASELINE' TimeSlice (scenario='APE.CLS', version='2.0'), for which a PERMDELTA TimeSlice may also be provided; and
  • a TimeSlice of type 'BASELINE' for the ad-hoc ApronElement feature, for which the “event:theEvent” property points to the Event instance created above.


ApronElement BASELINE TimeSlice shall have ApronAreaAvailability with operationalStatus='CLOSED'.

ER-03ApronElement BASELINE TimeSlice shall have associatedApron@xlink:href the Apron on which is located (as selected by the operator)
ER-04The location and extent description shall be encoded in free text as an ApronElement.annotation with propertyName='extent' and purpose='DESCRIPTION'
ER-05If the apron portion 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 ApronAreaAvailability of the affected ApronElement TEMPDELTA Timeslice(s). See the rules for Event Schedules. 
ER-06If there exists aircraft stands on the closed ApronElement and if the apron portion closure makes the aircraft stand unavailable, then a consequence STAND.CLS scenario shall also be encoded for the relevant AircraftStand feature and shall include a reference to the current event with role 'causeEvent'.

The system shall automatically identify the FIR where the AirportHeliport is located. This shall be coded as corresponding concernedAirspace property in the Event

ER-08The AirportHeliport concerned by the closure shall also be coded as concernedAirportHeliport property in the Event.


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

  • to be generated

  • No labels