Definition

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

Notes:

  • this scenario shall be used to notify limiting and prohibiting events other than complete closures of the apron(s). For notification of apron(s) closures, refer to APN.CLS scenario
  • this scenario does not include closure of apron portions, defined by reference to intersection with other airport surfaces. For this refer to APE.CLS scenarios.
  • this scenario shall be used when the facility operates below or above its nominal parameter

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.

EBNF Code
input = "airport designator" ["airport name"] ("apron name") {("apron name")}\n
("conditional for" | "closed, except for" |  "prohibited for" | "allowed for")
(["operation"] ["aircraft"] ["flight"] ["PPR time" ["PPR details"]]) {["operation"] ["aircraft"] ["flight"] ["PPR time" ["PPR details"]]} \n 
["reason"] "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

conditional forThe description of one or more operations, which is permitted under special conditions, usually a prior permission requirement

Apron.availability.ApronAreaAvailability.operationalStatus with value 'LIMITED' and 

Apron/..Availability/..Usage.type with value 'CONDITIONAL'

closed, except forApron is closed, except for operations explicitly identified in the input data.

Apron.availability.ApronAreaAvailability.operationalStatus with value 'LIMITED' and 

Apron/..Availability/..Usage.type with value 'RESERV'

prohibited forThe description of one or more operations that are prohibited for during the event duration.

Apron.availability.ApronAreaAvailability.operationalStatus with value 'LIMITED' and 

Apron/..Availability/..Usage.type with value 'FORBID'

additionally allowed for

The description of one or more additional operations that are available for a specific purpose during the event duration.

Apron.availability.ApronAreaAvailability.operationalStatus with value 'OTHER:EXTENDED' and 

Apron/..Availability/..Usage.type with value 'PERMIT'

operationThe specific type of operation concerned by the usage limitation update.Apron/..Availability/..Usage.operation with the following list of values CodeOperationManoeuvringAreaType

aircraft

The description of one or more aircraft (such as "helicopter") types that are exceptionally permitted on the apron during it's limitation.

AirportHeliport/..Availability/..Usage/..selection/..AircraftCharacteristics 

Only the following AircraftCharacteristics properties are allowed to be used in this scenario: type, engine, wingSpan, wingSpanInterpretation, weight, weightInterpretation.

flight

The description of one or more type of flight categories (such as "emergency") that are exceptionally permitted on the apron during its limitation.

AirportHeliport/..Availability/..Usage/..selection/..FlightCharacteristics.

Only the following FlightCharacteristics properties are allowed to be used in this scenario: type, rule, status, military, origin, purpose.

PPR timeThe value (minutes, hours, days) of the prior permission request associated with a permitted operation.Apron/ApronAreaAvailability/..Usage.priorPermission with uom attribute
PPR detailsAdditional information concerning the prior permission requirement.Apron/ApronAreaAvailability/..Usage.annotation with propertyName="priorPermission" and purpose="REMARK"

reason

The reason for the apron usage limitation.

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 limitation.

start time

The effective date & time when the apron limitation 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 limitation ends.

Apron/ApronTimeSlice/TimePeriod.endPositionEvent/EventTimeSlice.validTime/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's usage is effectively limited according to a regular timetable, within the overall limitation period.

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

note

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

Apron/ApronAreaAvailability.annotation with purpose=”REMARK”


Assumptions for baseline data

For AirportHeliport for which Apron limitation is to be reported, it is assumed that AirportHeliport BASELINE Timeslice, covering the entire duration of the event exists and have been coded as specified in the Coding Guidelines for the (ICAO) AIP Data Set.

In addition:

  1. 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;

  2. It is assumed that the following principles have been followed for the encoding of BASELINE Apron.availability (as available in the BASELINE data):
    1. the operationalStatus has the value "NORMAL" (meaning that the facility operates with nominal parameters) for all Apron.availability that are part of the BASELINE data;

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 limitation of an apron shall be encoded as:

  • a new Event with a BASELINE TimeSlice (scenario=APN.LIM, 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 shall be included in the Apron TEMPDELTA having:

  • operationalStatus=LIMITED if the apron usage is "conditional for", "closed, except for", "prohibited for";
  • operationalStatus=OTHER:EXTENDED if the apron usage is "allowed for".
ER-03

If the apron usage is "conditional for" specified operations, flight and/or aircraft categories, then all specified limitations shall be encoded as ApronAreaUsage child elements with type=CONDITIONAL.

ER-04

If the apron is "closed, except for" specified operations, flight and/or aircraft categories, then all specified limitations shall be encoded as ApronAreaUsage child elements with type=RESERV.

ER-05

If the apron usage is "prohibited for" specified operations, flight and/or aircraft categories, all specified limitations shall be encoded as ApronAreaUsage child elements with type=FORBID.

ER-06If the apron usage is "allowed for" specified operations, flight and/or aircraft categories, all specified limitations shall be encoded as ApronAreaUsage child elements with type=PERMIT.
ER-07

If a unique flight or aircraft is specified as part of the condition, they shall be encoded as one ConditionCombination with logicalOperator="NONE".

Otherwise, each pair of flight and aircraft shall be encoded as one ConditionCombination with logicalOperator="AND".

ER-08

If PPR time is specified, the uom attribute shall also be specified.

ER-09

If there exists aircraft stands on the Apron affected by the limitation and if the apron limitation makes the aircraft stand unavailable, then a consequence STAND.LIM scenario shall also be encoded for the relevant AircraftStand feature and shall include a reference to the current event with role 'causeEvent'. 

ER-10

The system shall automatically identify the FIR where the AerodromeHeliport is located and where the Apron affected by the limitation isSituatedAt. This shall be coded as corresponding concernedAirspace property in the Event

ER-11The AirportHeliport, where the Apron concerned by the limitation isSituatedAt, shall also be coded as concernedAirportHeliport property in the Event.

Examples

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

  • to be developed


  • No labels