Page tree
Skip to end of metadata
Go to start of metadata

ID:

AIXM-409

target version:

AIXM 5.2

version:

1.0

last updated:

24 OCt 2019

status:

APPROVED


Description

Add new attributes and enumerations to allow for the designation of the presence of safety-related lighting and marking on a runway, such as land and hold short operations (LAHSO) and runway status lights (RWSL).

Rationale for change

See https://aixmccb.atlassian.net/browse/AIXM-354;  https://aixmccb.atlassian.net/browse/AIXM-355;  https://aixmccb.atlassian.net/browse/AIXM-380

The Land and Hold Short Operations (LAHSO) part of a runway is designated by specific marking and lighting to alert aircraft to this safety critical area.The current model does not have the ability to present the perpendicular marking and/or lighting for the LAHSO on the runway.

Runway status lights (RWSL) are systems designed to provide a visual signal to pilots and vehicle operators indicating that it is unsafe to enter/cross or to begin takeoff on runway. The RWSL system has been implemented in about 20 airports across the US with additional implementation possible in the future. In AIXM the only way to define these lights is to use the OTHER value in the RunwayDirectionLightSystem.position attribute. As an example of its conceptual use, the runwayStatusLightType attribute in ICAO-AIRM captures the types of runway status lighting.

Runway Status Light Type: 

FAROS: Final Approach Runway Occupancy Signal: Provide signal to alert pilots that the approaching runway is occupied. This is done by adapting the VASIS or PAPI systems to alter from steady lights to flashing mode whilst the identified hazard remains.

REL: Runway Entrance Lights: Provide signal to aircraft entering runway from an intersecting taxiway that there is high speed traffic on the runway or there is an aircraft on final approach within the activation area.

THL: Takeoff Hold Lights: Provide signal to aircraft in position for takeoff or rolling, that it is unsafe to takeoff because the runway is occupied or about to be occupied by another aircraft or ground vehicle.

Runway Intersection Lights: Provide signal to aircraft entering a runway intersection from an intersecting taxiway that there is high speed traffic on the runway or there is an aircraft on final approach within the activation area.

Additional systems to be captured:

Runway Guard Lights: Provide signal to prevent unintended incursion of an active runway by an aircraft, consisting of a pair of unidirectional yellow lights which flash continuously.

Taxiway Centerline Lead-On Lights: Provide visual guidance to aircraft entering the runway

Taxiway Centerline Lead-Off Lights: Provide visual guidance to aircraft exiting the runway 

While these systems are grouped together as RWSL, conceptually they are distinct and should be added as attributes to the features with which they are conceptually aligned.  Recommend adding a new type attribute to the RunwayDirectionLightSystem feature, and new coded values for Runway Entrance Lights, Runway Intersection Lights, Runway Guard Lights, and Takeoff Hold Lights  toLightHoldingPositionBaseType, and a new finalApproachRunwayOccupancySignal attribute to the VisualGlideSlopeIndicator feature.  

These light systems have been used operationally in international NOTAMs. Examples: 

!DFW 03/249 DFW RWY 18L/36R RWSL OTS 

B7253/18 NOTAMN 

Q) RJJJ/QLRAS/IV/NBO/A/000/999/2612N12739E005 

A) ROAH B) 1810311330 C) 1810311800 

E) RWY ENTRANCE LGT FOR TWY E0,E1-U/S DUE TO MAINT

Impact assessment

There is no impact on existing implementations as the current AIXM 5.1.(.1) data remains fully valid against AIXM 5.2. No values are removed from this list. 

When receiving data from AIXM 5.2 implementations, current AIXM 5.1(.1) systems will have be able to map back the new values into OTHER:... values, as described in the mapping rules further in this document.

Change Proposal details

In the UML model:

  • Add a new <codeList>CodeRunwayLightBaseType, specialisation of  <XSDSimpleType>XMLSchemaDatatypes::string and defined as “a code indicating types of runway lighting", with the following code values:
    • POSITION_LIGHT: Designates a specific position/border of the runway
    • RUNWAY_INTERSECTION_LIGHT:Provides signal to aircraft on a runway that there is high speed traffic operating on the intersecting runway
    • TAKEOFF_HOLD_LIGHT: Provide signal to aircraft in position for takeoff or rolling that it is unsafe to takeoff because the runway is occupied or about to be occupied by another aircraft or ground vehicle
    • TWY_CL_LEAD_ON_LIGHT: Provide visual guidance to aircraft entering the runway
    • TWY_CL_LEAD_OFF_LIGHT: Provide visual guidance to aircraft exiting the runway
    • OTHER: other
  • Add a new <DataType>CodeRunwayLightType, specialisation of new <CodeList>CodeRunwayLightBaseType with the following attribute
    • nilReason, type of NilReasonEnumeration , defined as “A complex data type that enables the provision of a NIL reason for any attribute using this type.”
  • Add new attribute  to <feature>RunwayDirectionLightSystem
    • Add a new attribute “type”, defined as “the type of lighting system present on the runway”, type of CodeRunwayLightType.

 

  • Add new code to <CodeList>CodeRunwaySectionBaseType
    • LAHSO: Designates the Land and Hold Short Operation on a runway
  • Add new codes to <CodeList>CodeLightHoldingPositionBaseType
    • RUNWAY_ENTRANCE_LIGHT: Provide signal to aircraft entering runway from an intersecting taxiway that there is high speed traffic on the runway or there is an aircraft on final approach within the activation area
    • RUNWAY_GUARD_LIGHT: Provide signal to prevent unintended incursion of an active runway by an aircraft, consisting of a pair of unidirectional yellow lights which flash continuously.
  • Add new attribute to <feature>VisualGlideSlopeIndicator:
    • Add a new attribute “finalApproachRunwayOccupancySignal”, defined as “an indication of the presence of a FAROS system that alerts pilots that the approaching runway is occupied”, type of CodeYesNoType.


The UML class diagram shows the new attributes and datatypes (highlighted with red lines).


Mapping AIXM 5.1.1 to AIXM 5.2 (forward)

[MAPC-01] The forward mapping approach proposed in this case is as follows:

  • For each RunwayDirectionLightSystem.postion with value:
    • if “OTHER: LAHSO” replace with RunwayDirectionLightSystem.position with value “LAHSO” 
    • if “OTHER: POSITION_LIGHT” replace with RunwayDirectionLightSystem.type with value “POSITION_LIGHT”
    • if “OTHER: RUNWAY_INTERSECTION_LIGHT” replace with RunwayDirectionLightSystem.type with value “RUNWAY_INTERSECTION_LIGHT”
    • if “OTHER: TAKEOFF_HOLD_LIGHT” replace with RunwayDirectionLightSystem.type with value “TAKEOFF_HOLD_LIGHT”
    • if “OTHER: TWY_CL_LEAD_ON_LIGHT” replace with RunwayDirectionLightSystem.type with value “TWY_CL_LEAD_ON_LIGHT”
    • if “OTHER: TWY_CL_LEAD_OFF_LIGHT” replace with RunwayDirectionLightSystem.type with value “TWY_CL_LEAD_OFF_LIGHT”
    • Else as-is
  • For each TaxiHoldingPositionLightSystem.type with value:
    • if “OTHER: RUNWAY_GUARD_LIGHT” replace with TaxiHoldingPositionLightSystem.type with value “RUNWAY_GUARD_LIGHT”
    • if “OTHER: RUNWAY_ENTRANCE_LIGHT” replace with TaxiHoldingPositionLightSystem.type with value “RUNWAY_ ENTRANCE _LIGHT”
    • Else as-is
  • For each RunwayMarking.markingLocation with value:
    • if “OTHER: LAHSO” replace with RunwayMarking.markingLocation with value “LAHSO”
    • Else as-is

Mapping AIXM 5.2 to AIXM 5.1.1 (backward)

[MAPC-01] The backward mapping approach proposed in this case is as follows:

  • For each RunwayDirectionLightSystem.postion with value:
    • if “LAHSO” replace with RunwayDirectionLightSystem.position with value “OTHER: LAHSO”
  • For each TaxiHoldingPositionLightSystem.type with value
    • If “RUNWAY_GUARD_LIGHT” , replace TaxiHoldingPositionLightSystem.type with value “OTHER: RUNWAY_ GUARD_LIGHT”
    • If “RUNWAY_ENTRANCE” , replace TaxiHoldingPositionLightSystem.type with value “OTHER: RUNWAY_ ENTRANCE_LIGHT”
  • For each RunwayMarking.markingLocation with value:
    • if “LAHSO” replace with RunwayMarking.markingLocation with value “OTHER: LAHSO”


[MAPC-02] The following algorithm shall be applied:

  • For each RunwayDirectionLightSystem.type with value
    • Remove RunwayDirectionLightSystem.type
    • Add an annotation.Note associated with the <feature>RunwayDirectionLightSystem having
      • purpose=“OTHER:BACKWARD_MAPPING”;
      • translatedNote.LinguisticNote.note=” RunwayDirectionLightSystem.type: <value of RunwayDirectionLightSystem.type>
  • For each VisualGlideSlopeIndicator.finalApproachRunwayOccupancySignal with value
    • Remove the VisualGlideSlopeIndicator.finalApproachRunwayOccupancySignal
    • Add an annotation.Note associated with the <feature>VisualGlideSlopeIndicator having
      • purpose=“OTHER:BACKWARD_MAPPING”;
    • translatedNote.LinguisticNote.note=”finalApproachRunwayOccupancySignal:<value of VisualGlideSlopeIndicator.finalApproachRunwayOccupancySignal>

Mapping example

Mapping example to be added...


(Note: for mapping test data see: https://github.com/aixm/mapping_52_511/tree/master/AIXM-xxx

AIXM 5.2AIXM 5.1(.1)
  ...





...



  • No labels