Definition

The temporary "complete" closure of area(s) intended to accommodate aircraft for purposes of loading or unloading passengers, mail or cargo, fueling, parking or maintenance. 

Notes:

  • this scenario includes the closure of one or more aprons (could be all the aprons at the airport);
  • more than one apron can be included only if the closure conditions (closed, exceptions, parts) applies equally to all. Otherwise, separate message shall be issued;
  • this scenario does not include closure of apron portions, defined by reference to intersection with other airport surfaces. For this refer to APE.CLS scenario.
  • this scenario does not cover the "partial" closure, nor the temporary addition of a supplementary restriction to the apron availability, such as "closed for aircraft heavier than...". This is referenced in APN.LIM 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.).

Event data

The following diagram identifies the information items that are usually provided by a data originator for this kind of event.


EBNF Code
input = "airport designator" ["airport name"] ("apron name") {("apron name")}\n
"status=CLOSED" ["closure reason"]\n
"start time" "end time" [schedule] \n
[note].


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) concerned.

AirportHeliport.designator

airport name

The published name of the airport where the apron is located, used in order to identify the apron(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.

Apron.name

status=CLOSEDThe operational status of the apron. In this scenario, it is only possible to indicate a complete closure.Apron/ApronAreaAvailability.operationalStatus

closure reason

The reason for the apron(s) closure.

Apron/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".

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

end time

The end date & time when the apron closure ends.

Apron/ApronTimeSlice/TimePeriod.endPosition, Event/EventTimeSlice.validTime/endPosition and Event/EventTimeSlice.featureLifetime/endPosition also applying the rules for Event Update

schedule

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

Apron/ApronAreaAvailability/Timesheet/...according to the rules for {{Schedules}}

note

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

Apron/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:

In addition:

  • Apron BASELINE (min. name and 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.

Identifier

Data encoding rule

ER-01

The temporary closure of an apron shall be encoded as:

  • a new Event with a BASELINE TimeSlice (scenario=APN.CLS, version=2.0), for which a PERMDELTA TimeSlice may also be provided; and
  • a TEMPDELTA TimeSlice for each affected Apron feature, for which the "event:theEvent" property points to the Event instance created above;
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 Apron TEMPDELTA.

ER-03

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 TEMPDELTA Timeslice(s). See the rules for Event Schedules. 

ER-04

If there exists aircraft stands on the closed Apron 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'. 

ER-04

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

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

Examples

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


  • No labels