Definition

The indication that de-icing procedures are in operation at an airport

Notes:

  • this scenario shall be used to notify that de-icing operations are in progress at an airport
  • this scenario covers temporary changes to standard de-icing procedures (standard are considered those as described in the AIP) 
  • No NOTAM - this is a scenario for which it is unlikely that a NOTAM would be ever issued. The digitally coded data only might be made available to the interested parties through a digital data service at the airport level

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"] \n 
["de-icing pad name"] ( "aircraft stand" | "apron" | "taxiway") {["de-icing pad name"]( "aircraft stand" | "apron" | "taxiway")} \n
"start time" "end time" [schedule] \n
{note}.


The following table 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

designator

The published designator of the airport/heliport concerned. This information, in combination with eventually the name is used to identify the airport/heliport.

AirportHeliport.designator

name

The published name of the airport/heliport. This information, in combination with the designator is used to identify the airport/heliport.

AirportHeliport.name

de-icing pad nameThe published name of the de-icing pad DeicingArea.annotation with purpose="DESCRIPTION"
aircraft standThe designator of the aircraft stand where the de-icing pad is located atAircraftStand.designator indicated by DeicingArea.isLocatedOn xlink:href
apronThe name of the apron where the de-icing pad is located onApron.name indicated by DeicingArea.isLocatedOn xlink:href
taxiwayThe designator of the taxiway where the de-icing pad is located onTaxiway.designator indicated by DeicingArea.isLocatedOn xlink:href

start time

The effective date & time when de-icing operation is in progress. This might be further detailed in a "schedule".

DeicingArea/.../TimePeriod.beginPosition, Event/EventTimeSlice.validTime/timePeriod.beginPosition and Event/EventTimeSlice.featureLifetime/beginPosition

end time

The end date & time when when de-icing operation is expected to stop. 

Note: The event must be be updated if the time needs to be exceeded. 

DeicingArea/.../TimePeriod.endPosition and Event/EventTimeSlice.featureLifetime/endPeriod.beginPosition 

schedule 

A schedule might be provided, in case the deicing operations are provided according to a regular timetable, within the overall period.

DeicingArea/..Availability/Timesheet/...according to the rules for {{Schedules}}

note

A free text note that provides further details concerning de-icing operations, such as the de-icing fluid which is actually used at the airport. 

DeicingArea/..Availability.annotation with purpose=”REMARK”

Assumptions for baseline data

It is assumed that information about the aerodrome already exists in the form of AirportHeliport BASELINE TimeSlice(s) covering the complete period of validity of the event, for which the baseline availability is coded as specified in the Coding Guidelines for the (ICAO) AIP Data Set.

Furthermore, it is assumed that de-icing areas already exist in the form of DeicingArea BASELINE TimeSlice(s) covering as a minimum:

  • the place where the area isLocatedOn (in case of Apron or Taxiway) or isLocatedAt (in case of AircraftStand),
  • ApronAreaAvailability.operationalStatus = NORMAL when de-icing operations are not progress,
  •  de-icing pad name encoded as an annotation with purpose="DESCRIPTION". 

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. To the maximum possible extent, the compliance with these encoding rules shall be verified with automatic data validation rules.

Identifier

Data encoding rule

ER-01

The temporary provision of de-icing operations shall be encoded as:

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

  • a TimeSlice of type TEMPDELTA for the affected DeicingArea feature, for which the "event:theEvent" property points to the Event instance created above.

ER-02

One AirportHeliportAvailability element having operationalStatus=OTHER:ACTIVE shall be included in the DeicingArea TEMPDELTA.

ER-03

If the de-icing operation is provided based on 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 DeicingArea TEMPDELTA Timeslice. See the rules for Event Schedules.

ER-04

In accordance with the AIXM Temporality Concept (see sections 3.4 and 3.5 in version 1.0), the ApronAreaAvailability elements included in the TEMPDELTA completely replace all the BASELINE ApronAreaAvailability information, during the TEMPDELTA time of applicability. Therefore, if the event only concerns certain times, then the other times, when the de-icing area eventually remains under the conditions of the Baseline data, shall be explicitly included in the TEMPDELTA (associated with an ApronAreaAvailability with status= ‘CLOSED’).

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 ApronAreaAvailabilty 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 the airport 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-05The Event BASELINE shall have event:textNOTAM with attributes xsi:nil="true" and nilReason="inapplicable". 
ER-06

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

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


Note on the approach selected:

Alternative encoding could be using the AircraftGroundService type=DEICE. However, the approach was abandoned due to lack of location indication - for AircraftGroundService the location can be indicated only using coordinates, there is no connection from Service to DeicingArea nor to Apron, Taxiway or AircraftStand.

ZRH input

  • De-icing in operation    

    -       Is it just to announce the operation in progress or also changes to it – to announce operation in progress should be considered as a must have and it would also be nice to announce changes on ops (e.g. de-icing available between 06:00 - 10:00)  

    -       Is there a specific location description required (e.g. for the de-icing pads) – yet, we as well as other airports have more than one de-icing pads that’s way it has to be specified as pad or location (e.g. de-icing pads CHARLY or de-icing pads FOXTROT at LSZH)

    -       A list with data expected to be seen in an event – including those information above will be fine for this two events,  

    -       Examples or any free text description would be useful to give us a starting point and make sure we go on the right track.- you may also include de-icing fluid which is actually used at specific airport

  • No labels