...
...
...
...
Definition
The temporary "complete" closure of aircraft stand(s).
...
- this scenario includes the closure of one or more aircraft stands (could be all aircraft stands at the airport);
- more than one aircraft stand can be included only if the closure conditions (closure exceptions) applies equally to all. Otherwise, separate NOTAM shall be issued;
- this scenario includes only a "complete" closure of an aircraft stand, a "partial" closure except for flight and/or aircraft categories or temporary addition of a supplementary restriction to the aircraft stand availability, such as "closed for aircraft heavier than..." is included in STAND.LIM scenario.
- this scenario does not cover the temporary change of the operational hours of an aircraft stand;
- this scenario does not cover the situation when the aircraft stand is operating normally, but subject to a reason for caution.
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.
...
Data item | Description | AIXM mapping |
|---|---|---|
airport designator | The published designator of the airport where the aircraft stand is located, used in combination with other elements in order to identify the aircraft stand concerned. | AirportHeliport.designator |
airport name | The published name of the airport where the aircraft stand is located, used in order to identify the aircraft stand concerned. | AirportHeliport.name |
| aircraft stand designator | The designator of the aircraft stand to be closed. | AircraftStand.designator |
| status=CLOSED | The operational status of the aircraft stand. In this scenario, it is only possible to indicate a complete closure. | AircraftStand/ApronAreaAvailability.operationalStatus |
closure reason | The reason for the aircraft stand closure. | AircraftStand/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 at the aircraft stand, not a reason for a closure. |
start time | The effective date & time when the aircraft stand closure starts. This might be further detailed in a "schedule". | AircraftStand/AircraftStandTimeSlice/TimePeriod.beginPosition, Event/EventTimeSlice.validTime/beginPosition and Event/EventTimeSlice.featureLifetime/beginPosition |
end time | The end date & time when the aircraft stand closure ends. | AircraftStand/AircraftStandTimeSlice/TimePeriod.endPosition, Event/EventTimeSlice.validTime/endPosition and Event/EventTimeSlice.featureLifetime/endPosition also applying the rules for Event update and cancellation |
schedule | A schedule might be provided, in case the aircraft stand is effectively closed according to a regular timetable, within the overall closure period. | AircraftStand/ApronAreaAvailability/Timesheet/...according to the rules for {{Schedules}} |
note | A free text note that provides further details concerning the aircraft stand closure. | AircraftStand/ApronAreaAvailability.annotation according to the rules for encoding annotations |
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:
...
Identifier | Data encoding rule |
|---|---|
ER-01 | The temporary closure of an aircraft stand shall be encoded as:
|
ER-02 | First, all the BASELINE availability.ApronAreaAvailability (with operationalStatus=NORMAL), if present, shall be copied in the TEMPDELTA. Then, an additional availability.ApronAreaAvailability element having operationalStatus=CLOSED shall be coded in the AircraftStand TEMPDELTA. Note: No mistyping - ApronAreaAvailability is the actual name of the object containing information about the operational status of an AircraftStand. |
ER-03 | If the aircraft stand 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 Air TEMPDELTA Timeslice. See the rules for Event Schedules. |
Examples
Following coding examples can be found on GitHub (links attached):
...