AIXM 5 Terminal Procedure Model Study

“Verification of the AIXM 5 Procedures Model through cockpit simulation applications“

Objectives

• Investigation and Verification– Gap analysis procedure model – real-world data

– Examination of AIP procedure data and NOTAM

• Implementation– AIXM relational procedure DB from UML model

– Basic AIXM feeder interface

• Demonstration– Approach channel visualization in cockpit display

– Visualize (temporary) changes (received in digital NOTAMs)

(A0711/06 NOTAMNQ) EYVL/QPICH/I /NBO/A /000/999/5438N02517E010A) EYVI B) 0612210001 C) PERM E) 1. INSTRUMENT APPROACH PROCEDURE RWY 02 CHANGED AS FLW: - MNM ALT CHANGED TO 3500 FT INSTEAD OF 3000 FT, - FAP/FAF ALT(HGT) CHANGED TO 2500(1906) FT INSTEAD OF 2200(1606) FT. 2. INSTRUMENT APPROACH PROCEDURE RWY 20 CHANGED AS FLW: - MNM ALT CHANGED TO 3500 FT INSTEAD OF 3000 FT, - FAP/FAF ALT(HGT) CHANGED TO 2500(1854) FT INSTEAD OF 2200(1554) FT. REF AIP EYVI AD 2.4-37/42.)

Procedures in European AIPs

• Primary focus: non-graphical IAP information– Tabular/textual description of procedures

• Examined the (e)AIPs of– Armenia, Denmark, Estonia, France, Germany, Hungary, Italy,

Lithunia, Moldova, Netherlands, Slovenia

• Only Netherlands publishes detailed description of legs (ARINC style) of some RNAV procedures

Applying the Procedure Model

<aixm:InitialLegTimeSlice>…<aixm:legTypeARINC>TF</aixm:legTypeARINC><aixm:course>116</aixm:course><aixm:courseType>MT</aixm:courseType><aixm:courseDirection>TO</aixm:courseDirection><aixm:length uom="NM">3.5</aixm:length><aixm:lowerLimitAltitude uom="FT">2000</aixm:lowerLimitAltitude><aixm:lowerLimitReference>ALT</aixm:lowerLimitReference><aixm:altitudeInterpretation>LA</aixm:altitudeInterpretation><aixm:startingAt>

<aixm:TerminalSegmentPoint><aixm:locatedAt_DesignatedPoint xlink:href="#LISDA"/>

</aixm:TerminalSegmentPoint></aixm:startingAt><aixm:endingAt>

<aixm:TerminalSegmentPoint><aixm:locatedAt_DesignatedPoint xlink:href="#EH613"/>

</aixm:TerminalSegmentPoint></aixm:endingAt><aixm:isPartOf_InstrumentApproachProcedure xlink:href="#EHAM_LISDA"/>

</aixm:InitialLegTimeSlice>

Procedure NOTAM Analysis

• NOTAM set from EAD with NSC “P???”– Date Oct 20 2006, total number = 6731

• Most NOTAM (appr. 80%) simply change status– “…PROC NOT AVLB… EXPECT RADAR VECTOR…”

– “…PROC CHANGED. REF AIP…”

• Procedure NOTAM with “real” changes– OCA/OCH

– Segment/Leg altitudes

– Minima

– Wrong NSC!

• Very few with more complex content:

(A0711/06 NOTAMNQ) EYVL/QPICH/I /NBO/A /000/999/5438N02517E010A) EYVI B) 0612210001 C) PERM E) ILS AND NDB (GPS) APCH RWY 10 FROM ROBEL INT CHANGED AS FLW: LEAVE ROBEL AT 6000. WHEN CROSSING R274 ERF/ BRG 091DEG ERT (WP DE014) TURN RIGHT TO FINAL DESCENDING TO 5000. REST REMAINS UNCHANGED.)

Procedure Data Availability

• AIS procedure data is hard to find– Rarely any procedure data published in other form than charts

– Rarely any NOTAM with “real” changes to procedures

Why?

• No generic procedure model available• NOTAM free text form inappropriate for redefining a procedure

DUE VOR/DME SPL NOT AVBL, INSTR APCH PROC AND COM FAILURE PROC ALL RWY CHANGED: USE VOR/DME AMS INSTEAD OF VOR/DME SPL. COM FAILURE PROC RWY 09, 18R, 22 AND 36C: SUBSTITUTE FIXES ON OUTBOUND TRACKS BASED ON VOR/DME SPL BY FIXES BASED ON VOR/DME AMS WITH SAME BEARING AND DISTANCE. MISSED APCH PROC RWY 18R: AMEND DO NOT OVERSHOOT SPL 240 TO READ DO NOT OVERSHOOT AMS 240. CONTINUE MISSED APCH ON RDL AMS 280. MISSED APCH PROC RWY 36R: AMEND EH637 2.8 SPL TO READ EH637 3.8 AMS. MAINTAIN 1500FT, WHEN PASSING EH637 CLIMB TO 2000FT. MISSED APCH PROC RWY 18C: AMEND EH638 5.3 SPL TO READ EH638 5.4 AMS. MAINTAIN 1500FT, WHEN PASSING EH638 CLIMB TO 2000FT.

Scenario – Temporary Restricted Airspace affects RNAV approach

Frankfurt/Main (EDDF): RNAV (GPS) RWY 07L

AIXM Database and Display Application: Architecture

AIXM Procedure

DBMINIMUM ALTITUDE FROM LANUM ON R315 KLF TO 48.0 DME KLF TO READ

5000

Procedure data

(internal format)

AIXM XML messages

(digital NOTAM and

others)

PxP*•Pilot Procedure

Selection•Proc Data Extraction•xNOTAM

Functionality

AIXM Processor

•Process AIXM files

•Integrate into DB

AIP Procedure

Data

*Procedure xNOTAM Processor

Database Architecture and User Interaction

• Database stores baseline and delta data• Baseline DB initially loaded with procedure data (from AIP)• Decoded digital NOTAMs are written to Delta DB• Choice between primary and temporary view

Delta

Baseline

digital NOTAM

Database

Implementation of AIXM Procedure DB

• Step 1: Strip down AIXM5 CM to necessary elements (classes, attributes, associations)

• Step 2: Derive relational model from UML class model– Manual process, automatic processing with Rose Data Modeler

did not yield satisfying results

• Step 3: Implement relational model in DBMS– Choice was PostgreSQL due to its good spatial support

– Manual creation of tables, attributes, keys

Status / Next Steps

• Implementing AIXM database and software– AIXM Processor– PxP– Display application digital NOTAM extensions

• May 2007: Final Demonstration

• Outcomes– AIXM Procedure Database implementation

documentation– Procedure model investigation/verification report– Recommendations to improve AIXM support for

Procedure NOTAMs– Cockpit simulation demonstration movie

Questions?!