Versions Compared

Version Old Version 1 New Version Current
Changes made by

WOJTOWICZ Aleksander

POROSNICU Eduard

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

Definition

The temporary closure usage limitation of aircraft stand(s). The closure can be total (any traffic is forbidden) or partial (with the exception of particular flights or aircraft categories).

Notes:

  • this scenario includes the closure usage limitation of one or more aircraft stands (could be all aircraft stands at the airport);this scenario also includes closure of an aircraft stand except for flight and/or aircraft categories;
  • more than one aircraft stand can be included only if the closure conditions (closure exceptions) applies limitations conditions apply equally to all. Otherwise, separate message (NOTAM) shall be issued;this scenario does not cover the temporary addition of a supplementary restriction to the aircraft stand availability, such as "closed for aircraft heavier than...". 
  • 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.

Image RemovedImage Added

Code Block
titleEBNF Code
collapsetrue
input = "airport designator" ["airport name"] "aircraft stand designator" {"aircraft stand designator"} \n
[("closureconditional reasonfor"] | {"closed, except for" | [ "PPRprohibited timefor" [| "PPRallowed detailsfor"]])
[(["aircraft"] ["flight"]) {["other combination"aircraft"] ["flight"]} ["aircraftPPR time"] ["flightPPR 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 structure. The name of the variable (first column) is recommended for use as label of the data field in human-machine interfaces (HMI).

AircraftStand/ApronAreaAvailability/..Usage.annotation with propertyName="priorPermission" and purpose="REMARK"acft with wingspan less than that exceptionally at the aircraft stand during its closure.AircraftStand/ApronAreaAvailabilityAircraftCharacteristicsNote that only certain properties can . See data validation rules for details. exceptionally at the aircraft stand during its closure.AircraftStand/ApronAreaAvailabilityAnother combination of aircraft/flight characteristics that are excepted from the closure/ConditionCombination.logicalOperatorwith its value set to "OR" closure AircraftStandTimeSlice closure AircraftStandTimeSlice Event{{}} closed closure {{}} closure according to the rules for encoding annotations

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

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.

PPR time

The value (minutes, hours, days) of the advanced permission request associated with the permitted operation.

AircraftStand/ApronAreaAvailability/..Usage.priorPermission with uom attribute

PPR details

Additional information concerning the prior permission requirement.

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

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

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

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

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

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

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

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

AircraftStand/..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.

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

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

aircraft

The description of one or more aircraft (such as "

helicopter") types

are

permitted

or prohibited (depending on the limitation type) during the event duration.

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

permitted

or prohibited (depending on the limitation type) during the event duration.

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

Only the following FlightCharacteristics

other combination

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.AircraftStand/ApronAreaAvailability/..Usage.priorPermission with uom attribute
PPR detailsAdditional information concerning the prior permission requirement.AircraftStand/ApronAreaAvailability/..Usage.annotation with propertyName='priorPermission' and purpose='REMARK'

reason

The reason for the aircraft stand usage limitation.

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 on the apron, not a reason for a limitation.

start time

The effective date & time when the aircraft stand

limitation starts. This might be further detailed in a "schedule".

AircraftStand/

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

end time

The end date & time when the aircraft stand

limitation ends.

AircraftStand/

ApronTimeSlice/TimePeriod.endPosition,

 Event/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 aircraft stand's usage is effectively

limited according to a regular timetable, within the overall

limitation period.

AircraftStand/ApronAreaAvailability/Timesheet/...according to the rules for

Schedules

note

A free text note that provides further details concerning the aircraft stand

limitation.

AircraftStand/ApronAreaAvailability.annotation

with purpose='REMARK'

Assumptions for baseline data

It is assumed that following BASELINE TimeSlices the related ApronElement, Apron and AirportHeliport 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 the information about the aircraft stand

...

(s) concerned by the event already exist in the form of

...

a AircraftStand

...

 BASELINE TimeSlice, which contains as a minimum

...

:

  1. designator, and

...

  2. an association with the ApronElement, which is associated with an Apron, which is associated with an AirportHeliport;

It is also assumed that the following

...

principle have been followed for the encoding of BASELINE AircraftStand.availability data (if available in the BASELINE data):

    • the operationalStatus has the value
    • "
    • 'NORMAL
    • "
    • ' (meaning that the facility operates with nominal parameters) for all AircraftStand.ApronAreaAvailability that are part of the BASELINE data;
  • operations that are explicitly permitted have been encoded as ApronAreaUsage with type=PERMIT or type=CONDITIONAL (in case a PPR is necessary);
  • operations that are explicitly forbidden have been encoded as ApronAreaUsage with type=FORBID;
  • if the airport 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.

One ApronAreaAvailability element having operationalStatus=CLOSED . If the aircraft stand is "closed except for" flight and/or aircraft categories, all specified excepted operations 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" aircraft stand can still allow certain particular operations.
Note: No   a unique flight or aircraft are specified as being excepted, they one ConditionCombination with logicalOperator="NONE"Each pair of flight and aircraft conditions specified as being excepted one ConditionCombination with logicalOperator="AND"05 "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-04).If the aircraft stand closure is limited to of the Air TEMPDELTA Timeslice07

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 aircraft stand 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 taxiway element closure, enabling the operator to graphically check the availability at different times, such as in the example below:

Image Removed

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

Identifier

Data encoding rule

ER-01

The temporary closure of an aircraft stand shall be encoded as:

  • a new Event with a 'BASELINE' TimeSlice (encoding=DIGITAL, scenario='STAND.CLSLIM', version='2.0'), for which a PERMDELTA TimeSlice may also be provided; and

a TimeSlice of type TEMPDELTA for each affected AircraftStand 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 (see Usage limitation and closure scenarios).

Then, an additional availability.ApronAreaAvailability element shall be included in each 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".

Note: there is 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 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 aircraft stand 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 aircraft stand 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

ER-06

aircraft stand 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

The "aircraft-flight" branch can be used more than once. If this the case, then a parent ConditionCombination with logicalOperator='OR' shall be coded first. Otherwise, this parent element is not necessary.

Then, each flight and/or aircraft combination shall be coded as a child ConditionCombination with logicalOperator equal to:

  • 'NONE' - if either a flight condition or aircraft condition is specified (but not both);
  • 'AND' - if both a flight condition and aircraft condition are specified.

ER-08

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

ER-09

If the limitation concerns only 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

(with operationalStatus='LIMITED' or 'OTHER:EXTENDED') of all affected AircraftStand TEMPDELTA Timeslice(s). See the rules for Event Schedules. 

ER-10

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

ER-11The 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):