The temporary closure of movement areas established for the taxiing of aircraft or parts thereof. 


  • this scenario includes the closure of one or more full taxiways (could be all the taxiways at the airport);
  • this scenario includes closure of taxiway portions, provided the taxiway elements exist in the baseline data (see the specific assumptions for baseline data);
  • this scenario requires a graphical view of the taxiways and taxiways portions;
  • this scenario does not cover the "partial" closure, nor the temporary addition of a supplementary restriction to the taxiway availability, such as "closed for aircraft heavier than...". This is referenced in TWY.LIM scenario;
  • more than one taxiway can be included only if the closure conditions applies equally to all taxiways. Otherwise, separate NOTAM shall be issued;
  • this scenario does not cover the temporary change of the operational hours of a taxiway;
  • this scenario does not cover the situation when the taxiway 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"] ("taxiway designator" ["closed_taxiway_portion_input"]) {("taxiway designator" ["closed_taxiway_portion_input"])}\n
"status=CLOSED" ["closure reason"]\n
"start time" "end time" [schedule] \n

closed_taxiway_portion_input= "between" ("taxiway designator" | "runway designator" | "apron designator" | "stand designator") "and" ("taxiway designator" | "runway designator" | "apron designator" | "stand designator").

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 taxiway is located, used in combination with other elements in order to identify the taxiway(s) and/or taxiway portion(s) concerned.


airport name

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

taxiway designator

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


closed taxiway portion input

The portion of a published taxiway, specified using intersection elements between that taxiway and other taxiways, runways, aprons or stands.

Note on closed taxiway portion input:

  1. The application shall allow graphical display and selection of taxiway(s) and/or taxiway portion(s) to be closed;
  2. The HMI application should support the operator in identifying all relevant taxiways, taxiways portions and other elements that are affected by the closure and have an impact on operations. As a general rule, if an intersection has to be closed, the Taxiways and/or TaxiwayElements linked to this intersection shall also be closed up to the intersection.

  3. The application shall support the operator in avoiding cul-de-sac/dead-end situations and warn on situations when other Taxiways and/or TaxiwayElements are leading to nowhere. The application shall suggest to either include them in the NOTAM or generate a new NOTAM, as appropriate. 
  4. The operator shall be the one manually selecting all the portions to be closed. 

TaxiwayElement(s) identified as explained in the Data Encoding Rule ER-01. 

status=CLOSEDThe operational status of the taxiway. In this scenario, it is only possible to indicate a complete closure.Taxiway/ or TaxiwayElement/ManoeuvringAreaAvailability.operationalStatus

closure reason

The reason for the taxiway(s) and/or taxiway portion(s) closure.

Taxiway/ or TaxiwayElement/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 taxiway, not a reason for a closure.

start time

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

Taxiway/ or TaxiwayElement/TaxiwayTimeSlice/TimePeriod.beginPosition, Event/EventTimeSlice.validTime/beginPosition and Event/EventTimeSlice.featureLifetime/beginPosition

end time

The end date & time when the taxiway closure ends.

Taxiway/ or TaxiwayElement/TaxiwayTimeSlice/TimePeriod.endPosition, 
Event/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 taxiway is effectively closed according to a regular timetable, within the overall closure period.

Taxiway/ or TaxiwayElement/ManoeuvringAreaAvailability/Timesheet/...according to the rules for {{Schedules}}


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

Taxiway/ or TaxiwayElement/ManoeuvringAreaAvailability.annotation according to the rules for encoding annotations

Assumptions for baseline data

It is assumed that Airport/Heliport 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:

  1. the information about the Taxiway already exists in the form of a Taxiway BASELINE TimeSlice, which contains as a minimum:
    1. a designator,
    2. a type (ex: EXIT, FASTEXIT, etc), and

    3. an association with the AirportHeliport;

  2. If taxiway portions are concerned, it is assumed that they are encoded in BASELINE TaxiwayElements as suggested in the following diagram:
    Fig.1 - Encoding of TaxiwayElements

  3. It is assumed that each TaxiwayElements BASELINE have an annotation with purpose="OTHER:NOTAM_DESCRIPTION" and note describing their location as depicted below:

    Fig. 2 - Encoding of TaxiwayElement description 

    * a TaxiwayElement of type INTERSECTION would have a description such as “intersection TWY A and TWY B”, 
    * a TaxiwayElement of type NORMAL would have a description such as "between RWY 08L/26R and TWY J".

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 a taxiway or portion thereof shall be encoded as:

  • a new Event with a BASELINE TimeSlice (scenario=TWY.CLS, version=2.0), for which a PERMDELTA TimeSlice may also be provided; and
  • in case of complete taxiway closure:
    • a TEMPDELTA TimeSlice for each affected Taxiway feature, for which the "event:theEvent" property points to the Event instance created above;
  • in case of partial taxiway closure:
    • a TEMPDELTA TimeSlice for each affected TaxiwayElement feature, for which the "event:theEvent" property points to the Event instance created above;

Identification of the TaxiwayElements to be closed shall be done as follows:

  • The application shall support the operator in order to automatically select the TaxiwayElements that are concerned with a graphical view. 
  • With reference to Fig. 1 included in the “Assumptions for baseline data” further up in the document, if the operator specifies that the portion concerned is between intersections A/B and A/D, then the application shall automatically select the portions highlighted. By default, intersections are supposed to remain open, unless explicitly specified as closed.

First, all the BASELINE availability.ManoeuvringAreaAvailability (with operationalStatus=NORMAL), if present, shall be copied in the TEMPDELTA. 

Then, an additional availability.ManoeuvringAreaAvailability element having operationalStatus=CLOSED shall be coded in the Taxiway TEMPDELTA.

ER-03In case of complete taxiway closure, one ManoeuvringAreaAvailability element having operationalStatus=CLOSED shall be included in each Taxiway TEMPDELTA.
ER-04In case of taxiway portion closure, one ManoeuvringAreaAvailability element having operationalStatus=CLOSED shall be included in each TaxiwayElement TEMPDELTA selected to be closed.


If the 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 of all affected Taxiway or TaxiwayElement TEMPDELTA Timeslice(s). See the rules for Event Schedules. 


If there exists a single Taxiway leading to an Apron and/or ApronElement and if the Taxiway closure makes the Apron unavailable, then a consequence APN.CLS scenario shall also be encoded for the relevant Apron feature and shall include a reference to the current event with role 'causeEvent'. 


The system shall automatically identify the FIR where the AerodromeHeliport 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