...
...
...
...
...
...
...
...
...
...
...
Coding
Definition
The temporary closure of area(s) intended to accommodate aircraft for purposes of loading or unloading passengers, mail or cargo, fuelling, parking or maintenance. The closure can be total (any traffic is forbidden) or partial (with the exception of particular operations, flights or aircraft categories).
Notes:
- this scenario includes the closure of one or more aprons (could be all the aprons at the airport);
- this scenario includes closure of apron portions, defined by reference to intersection with other airport surfaces;
- this scenario also includes closure of an apron except for flight and/or aircraft categories;
- more than one apron and apron element can be included only if the closure conditions (closed, exceptions, parts) applies equally to all. Otherwise, separate NOTAM shall be issued;
- this scenario does not cover the temporary addition of a supplementary restriction to the apron 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 apron or apron element;
- this scenario does not cover the situation when the apron and/or apron element is operating normally, but subject to a reason for caution (such as "grass cutting in progress", etc.). Such situations will be covered in a different scenario.
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 flight and/or aircraft categories branch is optional, but can be more than once.
| Code Block | ||||
|---|---|---|---|---|
| ||||
input = "airport designator" ["airport name"] ("apron name" ["closed_apron_portion_input"]) {("apron name" ["closed_apron_portion_input"])}\n
["closure reason"] {"except" ["PPR time" ["PPR details"]] [["aircraft"] ["flight"] {"other combination" ["aircraft"] ["flight"]}]} \n
"start time" "end time" [schedule] \n
{note}.
closed_apron_portion_input = ("between" ("taxiway designator" | "runway designator" | "apron designator" | "stand designator") "and" ("taxiway designator" | "runway designator" | "apron designator" | "stand designator") | "relative position to" ("taxiway designator" | "runway designator" | "apron designator" | "stand designator")) {"between" ("taxiway designator" | "runway designator" | "apron designator" | "stand designator") "and" ("taxiway designator" | "runway designator" | "apron designator" | "stand designator") | "relative position to" ("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
...
Description
...
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(s) and/or apron portion(s) concerned.
...
AirportHeliport.designator
...
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.
...
AirportHeliport.name
...
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.name
...
closed apron portion input
...
The portion of a published apron, specified using intersection elements between that apron and other taxiways, runways, aprons or stands.
See note on closed apron portion input below.
...
ApronElement(s) identified as explained in the Data Encoding Rule ER-01.
...
closure reason
...
The reason for the apron(s) and/or apron portion(s) closure.
...
Apron/ or ApronElement/ApronAreaAvailability.operationalStatus 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 apron, not a reason for a closure.
...
flight
...
The description of one or more type of flight categories (such as "emergency") that are exceptionally permitted on the apron(s) and/or apron portion(s) during closure.
...
Apron or ApronElement/ApronAreaAvailability/..Usage/../FlightCharacteristics
...
aircraft
...
The description of one or more aircraft (such as "helicopter") types that are exceptionally permitted on the apron(s) and/or apron portion(s) during its closure.
...
Apron/ or ApronElement/ApronAreaAvailability/..Usage/../AircraftCharacteristicsNote that only certain properties can be used in this scenario. See data validation rules for details.
...
other combination
...
Another combination of aircraft/flight characteristics that are excepted from the closure.
...
Apron/ or ApronElement/ApronAreaAvailability/..Usage/ConditionCombination.logicalOperator with its value set to "OR".
...
PPR time
...
The value (minutes, hours, days) of the advanced permission request associated with the permitted operation.
...
Apron/ or ApronElement/ApronAreaAvailability/..Usage.priorPermission with uom attribute
...
PPR details
...
Additional information concerning the prior permission requirement.
...
Apron/ or ApronElement/ApronAreaAvailability/..Usage.annotation with propertyName="priorPermission" and purpose="REMARK"
...
start time
...
The effective date & time when the apron closure starts. This might be further detailed in a "schedule".
...
Apron/ or ApronElement/ApronTimeSlice/TimePeriod.beginPosition, Event/EventTimeSlice.validTime/timePosition and Event/EventTimeSlice.featureLifetime/beginPosition
...
end time
...
The end date & time when the apron closure ends.
...
Apron/ or ApronElement/ApronTimeSlice/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 apron is effectively closed according to a regular timetable, within the overall closure period.
...
Apron/ or ApronElement/ApronAreaAvailability/Timesheet/...according to the rules for {{Schedules}}
...
note
...
A free text note that provides further details concerning the apron closure.
...
Apron/ or ApronElement/ManoeuvringAreaAvailability.annotation according to the rules for encoding annotations
Note on closed apron portion input:
- The application shall allow graphical display and selection of apron(s) and/or apron portion(s) to be closed;
The HMI application should support the operator in identifying all relevant portions that are affected by the closure and have an impact on operations. Generally, the application shall support the operator in avoiding cul-de-sac/dead-end situations and warn on situations leading to nowhere. E.q. if a taxiway leads to a closed apron, the appropriate taxiway portion leading to the closed apron shall be closed as well.
- If the operator selects a closure which extends over multiple ApronElements (e.g. t.b.a.), the application shall split the selection in individual TaxiwayElements and request operator confirmation for the selection.
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:
...
- a name, and
an association with the AirportHeliport;
...
- the operationalStatus has the value "NORMAL" (meaning that the facility operates with nominal parameters) for all Apron.availability and/or ApronElement.availability that are part of the BASELINE data;
- operations that are explicitly permitted have been encoded as availability.ApronAreaAvailability.usage.ApronAreaUsage with type=PERMIT or type=CONDITIONAL (in case a PPR is necessary);
- operations that are explicitly forbidden have been encoded as availability.ApronAreaAvailability.usage.ApronAreaUsage with type=FORBID;
- if the taxiway is exclusively reserved for certain operations, then the ApronAreaAvailability that describes this condition contains only ApronAreaUsage elements with type=RESERV;
- in case of conflicts:
- the usages of type FORBID take precedence over usages of type PERMIT or RESERVE;
- the usages of type PERMIT take precedence over the usages of type RESERVE;
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.
...
Identifier
...
Data encoding rule
...
ER-01
...
The temporary closure of an apron or portion thereof shall be encoded as:
- a new Event with a BASELINE TimeSlice (encoding=DIGITAL, scenario=APN.CLS, version=2.0), for which a PERMDELTA TimeSlice may also be provided; and
- in case of complete apron closure:
- a TEMPDELTA TimeSlice for each affected Apron feature, for which the "event:theEvent" property points to the Event instance created above;
- in case of partial apron closure:
- a TEMPDELTA TimeSlice for each affected ApronElement feature, for which the "event:theEvent" property points to the Event instance created above;
- a TEMPDELTA TimeSlice for each affected Apron feature for which the above ApronElement describesPartOf (associatedApron), for which the "event:theEvent" property points to the Event instance created above;
Identification of the ApronElements to be closed shall be done as follows:
- The application shall support the operator in order to automatically select the ApronElements that are concerned, as much as possible with a graphical view. When no graphical view is available, the application would need to analyze the closed apron portion input provided by the operator in comparison with the baseline data descriptions.
- If the operator specifies that the portion concerned is spread across multiple ApronElements, then the application shall automatically select the portions highlighted.
...
In case of apron portion closure, a TEMPDELTA TimeSlice for the affected Apron feature for which the ApronElement describesPartOf (associatedApron) shall be created and shall have Apron.availability/ApronAreaAvailability.operationalStatus=LIMITED.
...
ER-05
...
If the closure is "except for" flight and/or aircraft categories, all specified exceptions shall be encoded as ApronAreaUsage 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" apron can still allow certain particular operations.
...
ER-06
...
If a unique flight or aircraft are specified as being excepted, they shall be encoded as one ConditionCombination with logicalOperator="NONE".
...
ER-07
...
Each pair of flight and aircraft conditions specified as being excepted shall be encoded as one ConditionCombination with logicalOperator="AND".
...
ER-08
...
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-07).
...
ER-09
...
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 ApronAreaAvailability of all affected Apron and/or ApronElement TEMPDELTA Timeslice(s). See the rules for Event Schedules. (e.g. If a ApronElement is closed based on a schedule, its associatedApron TEMPDELTA shall have the same associated schedule 
)
...
ER-10
...
In accordance with the AIXM Temporality Concept, the ApronAreaAvailability elements included in the TEMPDELTA completely replace all the BASELINE ApronAreaAvailability information, during the TEMPDELTA time of applicability. Therefore, if the closure only concerns certain times, then the other times, when the Apron and/or ApronElement eventually remains subject to the availability conditions of the Baseline data, shall be explicitly included in the TEMPDELTA. The calculation of the necessary additional ApronAreaAvailability elements to be included in the TEMPDELTA shall be automatically done by the applications implementing this specification.
All ApronAreaAvailability 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 each apron element 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.
...
If there exists aircraft stands on the closed Apron and/or ApronElement and if the apron 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'. (STAND.CLS under development)
Decoding
Text NOTAM production rules
This section provides rules for the automated production of the text NOTAM message items, based on the AIXM 5.1.1 data encoding of the Event. Therefore, AIXM specific terms are used, such as names of features and properties, types of TimeSlices, etc:
the abbreviation APN.BL. indicates that the corresponding data item must be taken from the Apron BASELINE;
the abbreviation APE.BL. indicates that the corresponding data item must be taken from the ApronElement BASELINE;
the abbreviation AHP.BL. indicates that the corresponding data item must be taken from the AirportHeliport BASELINE associated with the Apron that is associated with the ApronElement concerned;
the abbreviation APN.TD. indicates that the corresponding data item must be taken from the Apron TEMPDELTA that was created for the Event.
the abbreviation APE.TD. indicates that the corresponding data item must be taken from the ApronElement TEMPDELTA that was created for the Event;
In general, the ICAO DOC 8126 and the OPADD rules shall be followed. These have not been copied in this document in order to avoid duplication with those documents. Only instructions that are specific to the AIXM encoding of this event are stated here.
Item A
The item A shall contain the AHP.BL.designator if AHP.BL.locationIndicatorICAO='YES'. Otherwise, the nationality letter(s) as defined in ICAO Doc 7910 followed by “XX” or “XXX”.
Q code
The following mapping shall be used:
Availability.usage | Corresponding Q codes |
|---|---|
none specified | QMNLC |
there exist associated ApronAreaUsage.type PERMIT or CONDITIONAL | QMNLT |
Scope
Insert the value ‘A’.
Lower limit / Upper limit
Use “000/999”
Geographical reference
Insert the coordinate of the ARP (AHP.BL.ARP.ElevatedPoint) of the airport, formatted as follows:
the set of coordinates comprises 11 characters rounded up or down to the nearest minute; i.e. Latitude (N/S) in 5 characters; Longitude (E/W) in 6 characters;
the radius value is “005”.
Items B, C and D
Items B and C shall be decoded following the common production rules.
If at least one APN.TD.availability.ApronAreaAvailability.timeInterval or APE.TD.availability.ApronAreaAvailability.timeInterval exists (i.e. the Event has an associated schedule), then all such Timesheet(s) shall be represented in item D according to the common NOTAM production rules for {{Item D, E - Schedules}}. Otherwise, item D shall be left empty.
Item E
If apron elements are used, the automatic generation of an easy human-readeable NOTAM text is practically impossible using just the AIXM encoding. Some pre-defined groups of ApronElements could be pre-defined in the application, which would then generate directly the desired text, such as "between A and C", "between A and D", etc. This is considered a limitation of this scenario - although the Digital NOTAM is accurate, the NOTAM text but cannot be automatically re-generated by the end user based on just the AIXM code.
The following pattern should be used as a base for generating the E field text from the AIXM data:
...
Reference | Rule | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
(1) | If AHP.BL.locationIndicatorICAO=YES, then ignore this branch. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(2) | Insert here the type of the airport decoded as follows
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(3) | a. If AHP.BL.name is not NIL, then insert it here. Otherwise b.insert here the text "located at" followed by the AHP.BL.ARP.ElevatedPoint decoded according to the text NOTAM production rules for aixm:Point. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(4) | Insert here the APN.annotation and/or APE.annotation note with purpose="DESCRIPTION" stored in the BASELINE data (e.g. “between Acft stand 1 and Acft stand 5”). If more than one ApronElement has a TEMPDELTA associated with the Event, then the application shall identify the connected elements and generate the text in a logical order (e.g. "between Acft stand 1 and Acft stand 10" could be generated from two ApronElements - one from Acft stand 1-5 and one from 5-10) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(5) | If more than one apron and/or apron element has a TEMPDELTA associated with the Event, then insert the designator of each additional apron and/or apron element, designator preceded by ",". Insert "and" before the last entry. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(6) | If there exists a APN.TD.availability.annotation or APE.TD.availability.annotation having propertyName="operationalStatus" and purpose="REMARK", then translate it into free text according to the decoding rules for annotations. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(7) | If there exist one or more TD.availability.usage then decode them following this branch, in the following order of priorities:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| (8) | If TD.usage.priorPermission is not NIL, then insert here the decoding of the PPR information as detailed in the following diagram:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(9) | Decode here each FlightCharacteristics property that was specified, as detailed below. If more than one FlightCharacteristics property was used, insert blanks between consecutive properties.
*Note: type is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(10) | Decode here each AircraftCharacteristics property that was specified, as detailed below. If more than one AircraftCharacteristics property was used, insert blanks between consecutive properties.
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake.
**Note: new in AIXM 5.1.1. AircraftCharacteristics.wingSpan - insert the value followed by the value of the uom attribute. Prefix with the value of AircraftCharacteristics.wingSpanInterpretation, decoded as indicated in the following table:
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake. AircraftCharacteristics.weight - insert the value followed by the value of the uom attribute. Prefix with the value of AircraftCharacteristics.weightInterpretation, decoded as indicated in the following table:
*Note: value is unlikely to be used in a NOTAM, its decoding is provided for completeness sake. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(11) | If TD.usage.selection.logicalOperator=OR (there are more than one flight/aircraft combinations that are excepted), then select and decode each FlightCharacteristics/AircraftCharacteristics consecutively. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(12) | Annotations of TD.ApronAreaAvailability shall be translated into free text according to the decoding rules for annotations. |
Items F & G
Leave empty.
Event Update
The eventual update of this type of event shall be encoded following the general rules for {{Event updates or cancellation}}, which provide instructions for all NOTAM fields, except for item E and the condition part of the Q code, in the case of a NOTAMC
If a NOTAMC is produced, then the 4th and 5th letters (the "condition") of the Q code shall be "AK", except for the situation of a “new NOTAM to follow, in which case “XX”shall be used..
The following pattern should be used for automatically generating the E field text from the AIXM data
Reference | Rule |
(13) | If the NOTAM will be followed by a new NOTAM concerning the same situation, then the operator shall have the possibility to specify "New NOTAM to follow" and this text shall be appended at the end of item E of the NOTAM C. Note: in this case, the 4th and 5th letters of the Q code shall also be changed into “XX” |