Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Coding

Definition

The temporary closure 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 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 equally to all. Otherwise, separate 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.

....


EBNF Code 

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

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

flight

The description of one or more type of flight categories (such as "emergency") that are exceptionally permitted at the aircraft stand during its closure.

AircraftStand/ApronAreaAvailability/..Usage/../FlightCharacteristics

aircraft

The description of one or more aircraft (such as "acft with wingspan less than") types that are exceptionally permitted at the aircraft stand during its closure.

AircraftStand/ApronAreaAvailability/..Usage/../AircraftCharacteristicsNote that only certain properties can be used in this scenario. See data validation rules for details.

other combination

Another combination of aircraft/flight characteristics that are excepted from the closure.

AircraftStand/ApronAreaAvailability/..Usage/ConditionCombination.logicalOperatorwith its value set to "OR".

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.

AircraftStand/ApronAreaAvailability/..Usage.annotation with propertyName="priorPermission" and purpose="REMARK"

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/timePosition and Event/EventTimeSlice.featureLifetime/beginPosition

end time

The end date & time when the aircraft stand closure ends.

AircraftStand/AircraftStandTimeSlice/TimePeriod.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 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:

  • AirportHeliport BASELINE as specified in the Basic Data for Airport/Heliport,
  • the information about the aircraft stand already exists in the form of a AircraftStand BASELINE TimeSlice, which contains as a minimum a designator and an associations with the AirportHeliport;
  • It is assumed that the following principles 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.

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=TWY.CLS, 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

One ApronAreaAvailability element having operationalStatus=CLOSED shall be included in each Taxiway/Taxiway Element TEMPDELTA. 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.

ER-03

If a unique flight or aircraft are specified as being excepted, they shall be encoded as one ConditionCombination with logicalOperator="NONE".

ER-04

Each pair of flight and aircraft conditions specified as being excepted shall be encoded as one ConditionCombination with logicalOperator="AND".

ER-05

If the "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).

ER-06

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.

ER-08

In accordance with the AIXM Temporality Concept, the ManoeuvringAreaAvailability elements included in the TEMPDELTA completely replace all the BASELINE ManoeuvringAreaAvailability information, during the TEMPDELTA time of applicability. Therefore, if the closure only concerns certain times, then the other times, when the runway eventually remains subject to the availability conditions of the Baseline data, shall be explicitly included in the TEMPDELTA. The calculation of the necessary additional ManoeuvringAreaAvailability elements to be included in the TEMPDELTA shall be automatically done by the applications implementing this specification.

All ManoeuvringAreaAvailability 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:  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.

ER-09

If there exists a single Taxiway leading to an Apron and if the Taxiway closure makes the Apron completely unavailable, then a consequence APN.CLS scenario shall also be encoded for the relevant Apron feature and shall include a reference to the current event with role 'causeEvent'. (APN.CLS under development)

ER-10

If there exists a Taxiway portion closure and if one or more Taxiway remain partially available, a consequence TWY.LIM scenario shall be encoded for the relevant Taxiway features and shall include a reference to the current event with role 'causeEvent' (TWY.LIM under development)


...





Decoding

Text NOTAM production rules

This section provides rules for the automated production of the text NOTAM message items, based on the AIXM 5.1 data encoding of the Event. Therefore, AIXM specific terms are used, such as names of features and properties, types of TimeSlices, etc:

  • the abbreviation TWY.BL. indicates that the corresponding data item must be taken from the Taxiway BASELINE;
  • the abbreviation APN.BL. indicates that the corresponding data item must be taken from the Apron BASELINE;
  • the abbreviation AST.BL. indicates that the corresponding data item must be taken from the AircraftStand BASELINE;
  • the abbreviation AHP.BL. indicates that the corresponding data item must be taken from the AirportHeliport BASELINE associated with the Taxiway that is associated with the TaxiwayElement concerned;
  • the abbreviation TWE.TD. indicates that the corresponding data item must be taken from the Taxiway Element TEMPDELTA that was created for the Event;
  • the abbreviation TWY.TD. indicates that the corresponding data item must be taken from the Taxiway TEMPDELTA that was created for the Event.


In general, the ICAO DOC 8126 and the OPADD rules shall be followed. These have not been copied in this document in order to avoid duplication with those documents. Only instructions that are specific to the AIXM encoding of this event are stated here.

Item A

The item A shall contain the AHP.BL.designator if AHP.BL.locationIndicatorICAO='YES'. Otherwise, the nationality letter(s) as defined in ICAO Doc 7910 followed by “XX” or “XXX”.

Q code

The following mapping shall be used:

Closure status

Corresponding Q codes

CLOSED, if Taxiway.type other than FASTEXIT and there are no associated AirportHeliportUsage.type PERMIT or CONDITIONAL

QMXLC

CLOSED, Taxiway type other than FASTEXIT but there also exist associated AirportHeliportUsage.type PERMIT or CONDITIONAL

QMXLT

CLOSED, Taxiway type=FASTEXIT and there are no associated AirportHeliportUsage.type PERMIT or CONDITIONAL

QMYLC

CLOSED, Taxiway type=FASTEXIT but there also exist associated AirportHeliportUsage.type PERMIT or CONDITIONAL

QMYLT

Scope

Insert the value ‘A’.

Lower limit / Upper limit

Use “000/999”

Geographical reference

Insert the coordinate of the ARP (AHP.BL.ARP.ElevatedPoint) of the airport, formatted as follows:

  • the set of coordinates comprises 11 characters rounded up or down to the nearest minute; i.e. Latitude (N/S) in 5 characters; Longitude (E/W) in 6 characters;
  • the radius value is “005”.

Items B, C and D

Items B and C shall be decoded following the common production rules.

If at least one TWY.TD.availability.ManouevringAreaAvailability.timeInterval exists (i.e. the Event has an associated schedule), then all such Timesheet(s) shall be represented in item D according to the common NOTAM production rules for {{Item D, E - Schedules}}. Otherwise, item D shall be left empty.

Item E

The following pattern should be used for automatically generating the E field text from the AIXM data:

Reference

Rule

(1)

If AHP.BL.locationIndicatorICAO=YES, then ignore this branch.

(2)

Insert here the type of the airport decoded as follows

AHP.BL.type

Text to be inserted in Item E

AD or AH

"AD"

HP

"Heliport"

LS or OTHER

"Landing site"

(3)

If AHP.BL.name is not NIL, then insert it here. Otherwise insert here the text "located at" followed by the AHP.BL.ARP.ElevatedPoint decoded according to the text NOTAM production rules for aixm:Point.

(4)

Insert the words “rapid exit” if TWY.BLtype = FASTEXIT. Otherwise do not insert anything.

(54)

If more than one Taxiway has a TEMPDELTA associated with the Event, then insert the designator of each additional Taxiway, designator preceded by ",". The word TWY need not be repeated.

(5)

If more than one Taxiway Element has a TEMPDELTA associated with the Event, then the application shall identify:

  • first, all TaxiwayElements of type other than INTERSECTION and order them in a logical order; of type INTERSECTION that encompass the closed portion and generate the following text: “BETWEEN %1 AND %2” where “%1” and “%2” are the names of the Intersection elements (stored in the BASELINE data as Note of type “DESCRIPTION” (such as “Intersection TWY A and TWY B”).

(6)

If there exists a TWY.TD.availability.annotation having propertyName="operationalStatus" and purpose="REMARK", then translate it into free text according to the decoding rules for annotations.

(7)

If there exist one or more TD.availability.usage then decode them following this branch, in the following order of priorities:

  • TD.availability.usage that have operation="ALL"
  • TD.availability.usage that have type="PERMIT"
  • ... other situations ...
  • TD.availability.usage that have priorPermission which is not NIL shall be decoded last.

(8)

Decode here each FlightCharacteristics property that was specified, as detailed below. If more than one FlightCharacteristics property was used, insert blanks between consecutive properties.

FlightCharacteristics.type

Text to be inserted in Item E

OAT

"OAT"

GAT

"GAT"

ALL

"OAT/GAT"

OTHER:MY_TEXT

"my text" (replace "_" with blanks)

FlightCharacteristics.status

Text to be inserted in Item E

HEAD

"Head of State"

STATE

"State acft"

HUM

"HUM"

HOSP

"HOSP"

SAR

"SAR"

EMERGENCY

"EMERG"

ALL

"State/HUM/HOSP/SAR/EMERG"

OTHER:MY_TEXT

"my text" (replace "_" with blanks)

FlightCharacteristics.military

Text to be inserted in Item E

MIL

"MIL"

CIVIL

"civil"

ALL

"civil/MIL"

OTHER:MY_TEXT

"my text" (replace "_" with blanks)

FlightCharacteristics.origin

Text to be inserted in Item E

NTL

"domestic flights"

INTL

"international flights"

HOME_BASED

"home based acft"

ALL

"domestic/international"

OTHER:MY_TEXT

"my text" (replace "_" with blanks)

FlightCharacteristics.purpose

Text to be inserted in Item E

SCHEDULED

"scheduled flights"

NON_SCHEDULED

"unsched fights"

PRIVATE

"private flights"

AIR_TRAINING

"training flights"

AIR_WORK

"aerial work"

PARTICIPANT

"participating acft"

ALL

"scheduled/unscheduled/private/training/aerial work/participating acft"

OTHER:MY_TEXT

"my text" (replace "_" with blanks)

(9)

Decode here each AircraftCharacteristics property that was specified, as detailed below. If more than one AircraftCharacteristics property was used, insert blanks between consecutive properties.

AircraftCharacteristics.type

Text to be inserted in Item E

LANDPLANE

"landplanes"

SEAPLANE

"seaplanes"

AMPHIBIAN

"amphibians"

HELICOPTER

"helicopters"

GYROCOPTER

"gyrocopters"

TILT_WING

"tilt wing acft"

STOL

"short take-off and landing acft"

GLIDER

"gliders"

HANGGLIDER

"hang-gliders"

PARAGLIDER

"paragliders"

ULTRA_LIGHT

"ultra lights"

BALLOON

"balloons"

UAV

"UAV"

ALL

"all acfttypes"

OTHER:MY_TEXT

"my text" (replace "_" with blanks)

AircraftCharacteristics.engine

Text to be inserted in Item E

JET

"jet acft"

PISTON

"piston acft"

TURBOPROP

"turboprop"

ALL

"all engine types"

OTHER:MY_TEXT

"my text" (replace "_" with blanks)


AircraftCharacteristics.wingSpan - insert the value followed by the value of the uom attribute. Prefix with the value of AircraftCharacteristics.wingSpanInterpretation, decoded as indicated in the following table:

AircraftCharacteristics.wingSpanInterpretation

Text to be inserted in Item E

ABOVE

"acft with wingspan larger than"

AT_OR_ABOVE

"acft  with wingspan equal or larger than"

AT_OR_BELOW

"acft with wingspan equal or smaller than"

BELOW

"acft with wingspan smaller than"

OTHER:MY_TEXT

"my text" (replace "_" with blanks)



AircraftCharacteristics.weight - insert the value followed by the value of the uom attribute. Prefix with the value of AircraftCharacteristics.weightInterpretation, decoded as indicated in the following table:

AircraftCharacteristics.weightInterpretation

Text to be inserted in Item E

ABOVE

"acft mass heavier than"

AT_OR_ABOVE

"acft mass equal or heavier than"

AT_OR_BELOW

"acft mass equal or lighter than"

BELOW

"acft mass lighter than"

OTHER:MY_TEXT

"my text" (replace "_" with blanks)

(10)

If TD.usage.selection.logicalOperator=OR (there are more than one flight/aircraft combinations that are excepted), then select and decode each FlightCharacteristics/AircraftCharacteristics consecutively.

(11)

If TD.usage.priorPermission is not NIL, then insert here the decoding of the PPR information as detailed in the following diagram:

Reference

Rule

(11.1)

Insert here the value of the priotPermission attribute followed by the value of the uom attribute decoded as follows:

uom value

Text to be inserted in Item E

HR

"HR"

MIN

"min"

SEC

"sec"

OTHER:MY_TEXT

"my text" (replace "_" with blanks)

(11.2)

Decode here the annotation with propertyName="priorPermission" and purpose="REMARK", according to the decoding rules for annotations.

(12)

Annotations of TD.AirportHeliportAvailability shall be translated into free text according to the decoding rules for annotations.


Note: The objective is to full automatic generation, without human intervention. However, the implementers of the specification might consider reducing the cost of a fully automated generation by allowing the operator to fine-tune the text in order to improve its readability (with the inherent risk for human error, when re-typing is allowed).

Items F & G

Leave empty.

Event Update

The eventual update of this type of event shall be encoded following the general rules for {{Event updates or cancellation}}, which provide instructions for all NOTAM fields, except for item E and the condition part of the Q code, in the case of a NOTAMC

If a NOTAMC is produced, then the 4th and 5th letters (the "condition") of the Q code shall be "AK", except for the situation of a “new NOTAM to follow, in which case “XX”shall be used..

The following pattern should be used for automatically generating the E field text from the AIXM data

Reference

Rule

(13)

If the NOTAM will be followed by a new NOTAM concerning the same situation, then the operator shall have the possibility to specify "NEW NOTAM TO FOLLOW" and this text shall be appended at the end of item E of the NOTAM C.

Note: in this case, the 4th and 5th letters of the Q code shall also be changed into “XX”


Write a comment…

  • No labels