Definition

The notification about the operation of low visibility procedures (LVP) at an airport.

Notes:

  • this scenario shall be used to notify the phase in which Low Visibility Procedures (LVP) are at an airport. 

  • the scenario covers an indication of the ILS Protection area that are active during the LVP duration.
  • this scenario does not include a description of procedures that will be applied as part LVP. These are usually included in the AIP, aerodrome manual and stakeholders' procedures manual. 
  • 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 = designator [name] \n
"LVP phase" "runway protection area"{"runway protection area"} \n
"start time" "end time" [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

LVP phase

The phase of LVP, as defined in ICAO EUR Doc013- European Guidance Material on All Weather Operations at Aerodromes, Fifth Edition, September 2016.

AirportHeliport.annotation with purpose=OTHER:LPV_PHASE.

runway protection area

The identification of the ILS Runway Protection areas that are active during the LVP operationsRunwayProtectionArea

start time

The effective date & time when the LVP phase starts. 

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

end time

The estimated effective date & time when the LVP phase is expected to stop. 

AirportHeliport/TimePeriod.beginPosition , Event/EventTimeSlice.validTime/timePeriod.estimatedValidity and Event/EventTimeSlice.featureLifetime/beginPosition with indeterminatePosition="unknown"

note

A free text note that provides further details concerning the LVP as far as they differ from the ones published in the official documents. 

e.g. Follow Me car assistance not available. 

AirportHeliport.annotation with purpose=OTHER:LVP_WARNING. 

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.

It is assumed that information about the runway protection areas at the aerodrome already exists in the form of RunwayProtectArea BASELINE TimeSlice covering the complete period of validity of the event, which contains as a minimum:

  1. aixm:type = ILS 
  2. aixm:status = NORMAL
  3. an association with the protectedRunwayDirection. 

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 status of low visibility procedures (LVP) at an airport shall be encoded as:

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

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

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

ER-02

The LPV phase shall be encoded in AirportHeliport TEMPDELTA using an annotation with purpose=OTHER:LPV_PHASE.

ER-03

Only following values are allowed for the aixm:note of the annotation with purpose=OTHER:LPV_PHASE:

  1. Preparation Phase

  2. Operations Phase

  3. Termination Phase

ER-04Each RunwayProtectionArea feature affected by the Event shall have a TEMPDELTA Timeslice with status=OTHER:ACTIVE

ER-05

The gml:endPosition shall have the attribute indeterminatePosition="unknown". 

Rationale: As the LVPs are weather dependent, an endPosition cannot be clearly specified but only approximated. 

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


ZHR input

  • as LVPs affect usually entire airport, for this event there is no need for location specification and it is sufficient just the announcement that LVP are in progress.

Definition

  1. According to ICAO EUR Doc013- European Guidance Material on All Weather Operations at Aerodromes, Fifth Edition, September 2016, 

    1. LVP are defined in 3 phases:

      1. Preparation Phase: This phase is commenced when deteriorating meteorological conditions reach, or are forecast to reach, specified height of cloud base or ceiling and/or visibility/RVR values.

      2. Operations Phase: This phase must be in force prior to the commencement of any of the specific operations for which LVP are required. The Operations Phase is brought into force only once all preparatory activities are complete. Flight operations requiring LVP must only commence once the LVP are in force.

      3. Termination Phase: This phase is established to facilitate a smooth transition back to normal operations.

    2. The transition phases for both the initiation and termination of LVP are in many ways the most important from an operational point of view and it is during these phases that some States have found that the most problems may occur. Any confusion or misunderstanding as to the status of LVP may have safety implications and the change in the status of the operations creates additional demands on pilots and controllers. Careful planning and clear procedures during these phases will reduce the risk of an incident occurring.
    3. To ensure that the integrity of the guidance signal radiated by the ILS is maintained during aircraft approaches, all vehicles and aircraft on the ground should remain outside the ILS critical and sensitive areas. The ILS critical areas must be clear of all vehicles, persons and aircraft at all times. (7.5.6.4.1)
  • No labels