Page Comparison

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

The designator of the aircraft stand to be closed.

AircraftStand.designator

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

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

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

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

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 that are exceptionally permitted or prohibited (depending on the aircraft stand during its usage limitationlimitation 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 exceptionally permitted or prohibited (depending on the aircraft stand during its usage limitationlimitation type) during the event duration.

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

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

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 forEvents 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'

ER-01

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

• a new Event with a 'BASELINE' TimeSlice (scenario='STAND.LIM', 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.

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

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

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

The "aircraft-flight-PPR" 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.

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. 

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