Definition

The temporary change of one or more declared distances for one runway direction. 

Notes:

  • this scenario does not cover other changes, such as the position or the role, of the RunwayCentrelinePoint that owns the declared distances. For that situation, see the RCP.CHG scenario. 
  • this scenario allows the coding of one or more groups of declared distances, each group being associated with one runway centreline position. 
  • this scenario may be used, for example, when the declared distances are changed due to a partial closure of the other end of the runway direction, when an obstacle appears in the proximity of the take-off area, etc.

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"] "runway direction" ["runway surface composition"] \n
["centreline point designator"] ["centreline point location note"] "declared distance type" "declared distance value" {"declared distance type" "declared distance value"} {["centreline point designator"] ["centreline point location note"] "declared distance type" "declared distance value" {"declared distance type" "declared distance value"}} \n
"start time" "end time" [schedule] [note].

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.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 runway is located, used in combination with other elements in order to identify the runway concerned.

AirportHeliport.designator

airport name

The published name of the airport where the runway is located, used in order to identify the runway concerned.

AirportHeliport.name

runway direction

The published designator of the runway direction concerned. This information is used in combination with the airport designator/name in order to identify the runway and the concerned landing direction.

RunwayDirection.designator RunwayCentrelinePoint.onRunway

runway surface composition

In cases where there are two runways with the same designator but different surfaces (for instance RWY 07/25, one concrete and the second gravel or grass), the surface composition needs to be provided.

Runway.SurfaceCaracteristics.composition

centreline point designator

The designator of the RunwayCentrelinePoint, used to identify the RunwayCentrelinePoint with which the affected declared distances are associated.

Note: The application should support the operator by displaying all baseline RunwayDeclaredDistance associated with the selected point.

RunwayCentrelinePoint.designator

centreline point location note

Textual information (such as "intersection with TWY B") enabling to identify the RunwayCentrelinePoint with which the declared distances are associated.

Note: The application should support the operator by allowing tp graphically display and select the runway centreline point concerned. Furthermore, the application should support the operator by displaying all baseline RunwayDeclaredDistance associated with the selected point.

RunwayCentrelinePoint.annotation

declared distance type

The type of declared distance.

Note: the coding guidelines for the ICAO AIP Data Set - Declared Distances different declared distance types can be associated to different centerline points. The application shall support in the HMI the operator by providing the baseline values and asking the operator to indicate which and by what have have been modified.

RunwayCentrelinePoint/RunwayDeclaredDistance.type

declared distance value

The value of the declared distance.

RunwayCentrelinePoint/RunwayDeclaredDistance/RunwayDeclaredDistanceValue.distance

start time

The effective date & time when the temporary declared distances start. This might be further detailed in a "schedule".

RunwayCentrelinePoint/ RunwayCentrelinePointTimeSlice/ TimePeriod.beginPosition, Event/EventTimeSlice.validTime/ timePosition and Event/EventTimeSlice.featureLifetime/ beginPosition

end time

The effective date & time when the temporary declared distances end.

RunwayCentrelinePoint/ RunwayCentrelinePointTimeSlice/ 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 temporary declared distances are according to a regular timetable, within the overall period.

RunwayCentrelinePoint/RunwayDeclaredDistance/ RunwayDeclaredDistanceValue/Timesheet/...

note

A  free text note that provides further details concerning the temporary change.

RunwayCentrelinePoint/RunwayDeclaredDistance.annotation according to the rules for encoding annotations

Assumptions for baseline data

It is assumed that information about the runway declared distances already exists in the form of AirportHeliport, Runway, RunwayDirection and RunwayCentrelinePoint BASELINE TimeSlice(s) covering the complete period of validity of the event, for which the baseline availability may be coded as specified in the Coding Guidelines for the (ICAO) AIP Data Set.


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 changes of declared distances shall be encoded as:

  • a new Event with a BASELINE TimeSlice (scenario=RDD.CHG, version=2.0), for which a PERMDELTA TimeSlice may also be provided; and
  • a TEMPDELTA TimeSlice for each of the affected RunwayCentrelinePoint feature(s), for which the "event:theEvent" property points to the Event instance created above.

Note: the "centreline point designator" and/or the "centreline point location note" information are used to identify the RunwayCentrelinePoint concerned. If none is provided, it is likely that a single set of declared distances is defined in the BASELINE data for that RunwayDirection. The BASELINE declared distances could still be associated with two different RunwayCentrelinePoint, as explained in the Coding Guidelines for the (ICAO) AIP Data Set. The data coding application shall support the operator in identifying the RunwayCentrelinePoint(s) concerned.

ER-02

If "centreline point location note" is provided, the operator shall have the possibility (at their own discretion) to save this information in the RunwayCentrelinePoint TEMPDELTA concerned as annotation.Note with purpose='REMARK' and propertyName='location'. 

Note: the textual information provided by the data originator that allows to identify the runway declared distances group might also be relevant for the data users who need to understand which declared distances are concerned by the temporary change.

ER-03In accordance with the AIXM Temporality Concept, the RunwayDeclaredDistance associated with the TEMPDELTA completely replaces all the BASELINE RunwayDeclaredDistance information, during the TEMPDELTA time of applicability. Therefore, if the change only concerns some declared distances for that point, then both the values that remain valid from the baseline data and the temporary values shall be encoded as associatedDeclaredDistance object(s) of the RunwayCentrelinePoint TEMPDELTA TimeSlice mentioned in ER-01. 

ER-04

If the change of declared distances 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 RunwayDeclaredDistanceValue.timeInterval/Timesheet properties for each RunwayDeclaredDistanceValue. See the  general rules for coding schedules.

In accordance with the AIXM Temporality Concept, the RunwayDeclaredDistance associated with the TEMPDELTA completely replaces all the BASELINE RunwayDeclaredDistance information, during the TEMPDELTA time of applicability. Therefore, if the change only concerns certain times, then the other times, when the declared distances eventually remains with the same status as in the Baseline data, shall be explicitly included in the TEMPDELTA, as explained in the general rules for coding schedules.

The calculation of the necessary additional RunwayDeclaredDistanceValue elements to be included in the TEMPDELTA shall be done, as much as possible, automatically by the applications implementing this specification. A graphical "calendar" view displaying the corresponding declared distance values and the applicability times should be provided in order to facilitate the correct and complete data coding.

ER-05

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

ER-06The AirportHeliport concerned by the closure shall also be coded as concernedAirportHeliport property in the Event.

Examples

TBD

  • No labels