Versions Compared

Key

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

Definition

The surface condition report event scenario describes informations information about contaminations on one or multiple runways,  taxiways and/or aprons at taxiways and/or aprons at one airport.

Notes:

  • The objective of this scenario is to support the encoding of contamination information about individual runways, taxiways or aprons, as foreseen to be contained in SNOWTAM messages as of 04 November 2021 (ICAO) or 12 August 2021 (EU);
  • Several runways, taxiways and aprons can be included in the surface condition report;
  • The content of the report is considered as described in ICAO Doc 10066 - Aeronautical Information Management, First Edition, Amendment No. 2, 2018, Appendix 4 - SNOWTAM Format and CIR (EU) 2017/373 as amended by CIR (EU) 2020/469 and CIR (EU) 2020/1177 - Appendix 3 SNOWTAM Format.
  • This scenario does not support the encoding of the information about airport, runway closure due to contamination. That information should be encoded using the dedicated AD.CLS or RWY.CLS scenarios.

...

  • AirportHeliport BASELINE as specified in the Basic Data for Airport/Heliport,

  • Runway BASELINE according to the coding rules for Basic Data for Runway;

  • Taxiway BASELINE which contains as a minimum a designator and an association with the AirportHeliport(warning)No AIP Data Set coding rules identified.

  • Apron BASELINE which contains as a minimum a designator and an association with the AirportHeliport(warning)No AIP Data Set coding rules identified.

...

Identifier

Data encoding rule

ER-01

The surface condition report shall be encoded as:

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

  • a TimeSlice of type TEMPDELTA for each affected Runway and AirportHeliport feature, for which the "event:theEvent" property points to the Event instance created above.
  • if applicable, additional TEMPDELTA TimeSlices for the affected Taxiway and/or Apron features as detailed below. Such TimeSlice shall have the "event:theEvent" property points to the Event instance created above.
ER-02

The TimeSlice.validTime of the affected Features TEMPDELTAs, the EventTimeSlice.validTime and EventTimeSlice.featureLifetime shall have TimePeriod.beginPosition equal to the latest Runway.RunwayContamination.observationTime.

Reason: When reporting on more than one runway and individual dates/times of observation/assessment are indicated by repeated Item B, the latest date/time of observation/assessment is inserted in the abbreviated heading. This is considered the start of the SNOWTAM validity.

ER-03

The TimeSlice.validTime of the affected Features TEMPDELTAs, the EventTimeSlice.validTime and EventTimeSlice.featureLifetime shall have TimePeriod.endPosition set 8h after the TimePeriod.beginPosition.

Reason: Maximum SNOWTAM validity is 8h.

ER-04

All three sections (thirds) shall always be present and each of the following values shall only be used once for the RunwaySectionContamination.section:

  • 1_THIRD
  • 2_THIRD
  • 3_THIRD


ER-05

Only the following values are allowed for Runway.RunwaySectionContamination.frictionEstimation:

  • OTHER:RWYCC_0
  • OTHER:RWYCC_1
  • OTHER:RWYCC_2
  • OTHER:RWYCC_3
  • OTHER:RWYCC_4
  • OTHER:RWYCC_5
  • OTHER:RWYCC_6


ER-06

Only the following values shall be used for RunwaySectionContamination.SurfaceContaminationLayer.type:

  • COMPACT_SNOW
  • DRY_SNOW
  • FROST
  • ICE
  • SLUSH
  • OTHER:DRY

  • OTHER:STANDING_WATER
  • OTHER:SLIPPERY_WET (Note: EASA)
  • OTHER:PREPARED_WINTER_RUNWAY (Note: EASA)
  • OTHER:WET
  • OTHER:WET_ICE
  • WET_SNOW


ER-07

Only the following values shall be used for Runway.overallContaminant.SurfaceContaminationLayer.type:

  • OTHER:DRIFTING_SNOW
  • OTHER:LOOSE_SAND
  • OTHER:CHEMICAL_TREATMENT


ER-08

In case of multiple SurfaceContaminationLayer.layerOrder, only the following combinations are allowed:

  • layerOrder='1', type='DRY_SNOW' and layerOrder='2', type='COMPACT_SNOW'
  • layerOrder='1', type='DRY_SNOW' and layerOrder='2', type='ICE'
  • layerOrder='1', type='OTHER:STANDING_WATER' and layerOrder='2',type='COMPACT_SNOW'
  • layerOrder='1', type='WET_SNOW' and layerOrder='2', type='COMPACT_SNOW'
  • layerOrder='1', type='WET_SNOW' and layerOrder='2', type='ICE'
ER-09

The maximum value of SurfaceContaminationLayer.layerOrder is 2.

ER-10Snow banks adjacent to the runway shall be encoded as Runway.overallContaminant/RunwayContamination.criticalRidge/Ridge.annotation with purpose='WARNING' and note='Snow banks present adjacent to the runway'
ER-11

When Runway.overallContaminant/RunwayContamination.criticalRidge/Ridge.distance is provided, a Ridge.annotation shall be encoded with propertyName='distance', purpose='DESCRIPTION' and note='distance measured from runway centerline'

The AIXM definition of the element is being a distance measured from the edge of the movement area and not from its centreline, therefore an interpretation rule is needed.

ER-12If the assessment is including Taxiway information, TEMPDELTA TimeSlices shall be encoded for each affected Taxiway Feature.
ER-13Snow banks present on the taxiway shall be encoded as Taxiway.contaminant/TaxiwayContamination.criticalRidge/Ridge.annotation with purpose='WARNING' and note='Snow banks present on the taxiway'.
ER-14If the assessment is including Apron information, TEMPDELTATimeSlices shall be encoded for each affected Apron Feature.
ER-15

Only the following values shall be used for Runway.RunwayContamination.frictionDevice:

  • GRT
  • MUM
  • BRD
  • RFT
  • SFH
  • SFL
  • SKH
  • SKL
  • TAP


ER-16In case items are NOT REPORTED - "NR",  xsi:nil="true" nilReason="inapplicable" shall be used.
ER-17The AirportHeliport concerned by the surface condition report shall also be coded as concernedAirportHeliport property in the Event.

Examples

under development.

...