Digital AIM Training - AIXM

Slides:



Advertisements
Similar presentations
PROCEDURE DESIGN MASTER CLASS
Advertisements

B-RNAV OPERATIONS IN EUROPEAN AIRSPACE
Navigation Applications perspective on ADQ
Identifying the Achilles Heels of Instrument Flight Procedures International Flight Inspection Symposium Oklahoma City, OK USA June 2008 Ivan Ferencz CAA.
RNAV Procedures AIXM Procedures Seminar 1-2 Sept 2010.
Instrument Approach Charts
1 PP 48 Use of GNSS distance instead of DME B. Rabiller CNS-ATM steering group meeting Gatwick February 2008.
Procedure Design Considerations
PBN CHANGES Narrator BEIJING, CHINA; 30 JUN-11 JUL 2014.
PROCEDURE DESIGN CRITERIA
Specification and Validation of Navigation Data Business Rule
1 #4295. Which frequency should you expect to use for Regional Approach Control, control tower, and ground control respectively at DFW when coming from.
September 2002-MoroccoARAB INSTRUMENT PROCEDURE DESIGN SEMINAR 1 STAND-ALONE APPROACH OPERATIONS FOR CLASS A GPS.
Digital AIM Training - AIXM
CAP / RCAP Format Improvement. Types of Charts ›Approach Charts ›Cat II and III ›Circling ›Combined IAP ›RNAV ›Helicopter Procedures ›Visual Approach.
1 Approach Procedures Barb Cordell. 2 Missed Approach textual Description Minimum Safe Altitude Textual Circling remarks Segment Legs Minimums Holding.
The European Organisation for the Safety of Air Navigation Overview of the AIXM 5.1 Procedure Model AIXM Procedure Modelling/Encoding seminar Brussels.
AIXM 5.1 implementation experience
Federal Aviation Administration The Benefits and Challenges of Implementing Performance Based Navigation (PBN) Instrument Flight Procedures By: Presented.
Instrument Ground Training Module 4 & 5
PBN Airspace Concept Workshop ReviewReview. Review of Workshop 2 ✈ 10 day PBN Airspace Design Workshop ✈ ICAO Doc 9992: PBN in Airspace Design ✈ Plan,
Mr. Hooper Harris FAA/JAA Annual Meeting Phoenix, AZ June 3 - 7, 2002
Flying DME Arcs.
Instrument Procedure Design and Operational Differences
VALIDATION & IMPLEMENTATION CONSIDERATIONS 1 BEIJING, CHINA; 30 JUN-11 JUL 2014.
Introduction to AIXM. Topics Criticality of AIS information AIM – a “data centric” approach Worldwide interoperability AIXM mission Related developments.
CHARTING Regulation and issues
AIR TRAFFIC ROUTES.
International Training: Area Navigation Fundamentals
Chapter 5 Arrival Charts
This presentation contains notes in the notes sections for use by instructors when presenting to students.
EUROCONTROL Digital NOTAM Project
Chapter 8 Differences Between Jeppesen Database & Charts
What’s New with AIXM 5. Explaining AIXM 5 Mission and Objectives Coverage of the AIXM 5 data model –Scope of aeronautical information –Emerging “partner”
The European Organisation for the Safety of Air Navigation ARINC 424A specification and SESAR WP9.31 AIXM Procedure Modelling/Encoding seminar Brussels.
The European Organisation for the Safety of Air Navigation EUROCONTROL’s Efforts with AIXM AIXM 5.1 XML Developers' Seminar #4 – Mar 2010.
AIXM 5 Terminal Procedure Model Study “Verification of the AIXM 5 Procedures Model through cockpit simulation applications“
AIXM 5 Concepts This presentation is based on the first part of the “AICM and AIXM 5 - Exchange Model goals, requirements and design” document. The purpose.
RECITE A PRAYER…(15 SECONDS). ATM TOPIC 1. INTRODUCTION TO AIR TRAFFIC MANAGEMENT,TYPE OF CONTROL AREAS & FLIGHT PLAN 2. AERODROME CONTROL 3. AREA CONTROL.
Roadmap Phase 2 EAD & AICM By: Eduard Porosnicu, AIM Expert 7-8 October 2009 ACAC – AIM Workshop.
LECTURE 4: ICAO CHART requirements
Chapter 4 Departure Charts. §4.1 Introduction §4.2 Arrangement and Information of Departure Charts §4.3 Examples of Chart.
Advanced Holding Patterns Christian Pezalla ATP, CFII.
AABI Annual Meeting Preparing Flight Education Graduates for NextGen, ADS-B, and PBN/RNP JIM MINER E190 TRAININGSTANDARDSSUPERVISOR.
INSTRUMENT INSTRUMENT FLIGHT APPROACH RULES CHART APPROACH PROCEDURE
Joining RNAV Approaches at a fix or waypoint Prepared by John D. Collins CFI/CFII.
Review Chapter 4-8. Departure and Arrival Charts DPs, STARs and visual approaches are routinely assigned by ATC DPs and STARs are issued to simplify clearance.
The European Organisation for the Safety of Air Navigation AIXM Procedure Modelling Seminar Additional topics for discussion Brussels – 01/02 Sept 2010.
Advanced Holding Patterns
Arrival Charts and Procedures
Intro text for this chapter AIXM Procedure Seminar Luciad.
AIXM 5 Concepts This presentation is based on the first part of the “AICM and AIXM 5 - Exchange Model goals, requirements and design” document. The purpose.
Holding Procedures.
Допълнение 7 на PANS-ATM (ICAO Doc 4444)
PlaneWrong AGM Thursday 13th October
Overview of Continental En-route Navigation Specifications
Overview of the AIXM 5.1 Procedure Model
RAAF AERONAUTICAL INFORMATION SERVICE
Performance Based Navigation: Navigation Specifications
AIXM Procedure Modeling
PBN Airspace Concept Workshop
Approach Procedures Barb Cordell
Approach Procedures Barb Cordell
  (1.5 hours) (2.0 hours) Monday (14/07) Registration Welcome ( M/FPP)
AIXM and AIRM Analysis Results Summary.
Approach Procedures Barb Cordell
PBN CHANGES Narrator BEIJING, CHINA; 30 JUN-11 JUL 2014.
Navaids and Points.
Navaids and Points The purpose of this presentation is to provide an overview of the Aeronautical Conceptual Model for Navaids and Points.
Presentation transcript:

Digital AIM Training - AIXM Notes: EUROCONTROL Copyright 2011

Digital AIM Training - AIXM Content Context & History Overview of the Procedure Model Procedure Transition, SegmentLeg and SegmentPoint Approach Conditions (minima…) Circling Area MSA TAA Miscellaneous Some open issues EUROCONTROL Copyright 2011

Procedure = SID, STAR or Approach

History of the AIXM Procedure Model AIXM 3.3 / AIXM 4.5: Objective: provide an encoding for procedure charts, in support of EAD SDO Based on Arinc424-14 ProcedureLeg was the key of the Procedure model Some non-Arinc legs (time-based legs PT/FT) were included

AIXM 4.5 Procedure Model

AIXM 4.5 Procedure Model

History of the Procedure Model AIXM 5.0/5.1 Better support the encoding of RNAV procedures published in AIPs Support the procedure design process Upgrade the model with recent changes in PANS-OPS and Arinc424 (FAS Datablock)

History of the Procedure Model AIXM 5.0/5.1 Procedure Model goals Intended for: support digital transfer of procedure data from procedure designer to AIS office support digital transfer of procedure data and further to the data users (data houses, charting office, etc.); this includes conversion of AIXM data into ARINC 424 Might be useful for: Procedure design (with extensions) Direct FMS encoding? (nobody tried that yet…)

AIXM 5.1 Procedure Model - Overview The terminal area procedures and related concepts (MSA, TAA...) Navaids Points Guidance Service, Point Reference, and Segment Points Holding Holding Patterns Service For Information services (ATIS) and ATC services Shared.Surface Assesment

AIXM 5.1 Procedure Model - Overview Designator SID & STAR: designator (+ name?) Approach: name + 6 first attributes of class InstrumentApproachProcedure approachPrefix = Blank approachType = VOR multipleIdentification = X copterTrack = Blank circlingIdentification = Blank courseReversalInstruction = Blank

AIXM 5.1 Procedure Model - Overview Attribute RNAV is used to identify an RNAV procedure For an approach, attribute approachType can also carry the value “RNAV” Connection SID/STAR/Appr -> RunwayDirection is realised through class LandingTakeOffAreaCollection

AIXM 5.1 Procedure Model - Overview

Procedure design vs Procedure encoding The AIXM model defines the class SegmentLeg which represents an elementary portion of a Procedure A SegmentLeg is associated to a Procedure. A procedure is designed by attaching several SegmentLeg to the procedure A Procedure can be divided into a series of Procedure Transitions More optimised for Procedure Encoding Procedure Design Procedure Encoding

Procedure Transition & SegmentLeg runway IAF 1 IAF 2 IF MAP 3 “approach transitions” 1 final approach 1 missed approach WP 4 FAF leg 1 WPT 1 WP 2 WP 3 leg 2 A Procedure can be divided in a series of Procedure Transitions A Transition can be represented as a sequence of SegmentLeg A Transition can be associated with a geographical Curve (for charting and procedure design - not intended for flight)

Procedure Transition & SegmentLeg Approach Transition GEBTI Approach Transition VFA Final Approach Missed Approach SegmentLeg HoldingPattern

SegmentLeg SegmentLeg contains a set of attributes inspired from the Arinc424 specification Note: It is not mandatory to use Arinc424 concepts => legPath SegmentLeg is an abstract class which is specialised: - 1st specialisation per type of procedure - 2nd specialisation per type of transition for approach procedures For a SID For a STAR For an Approach For a missed approach For an approach transition For a final approach

RNAV – Path Terminator Leg Type Digital AIM Training - AIXM RNAV – Path Terminator Leg Type Path Terminator F Constant DME arc Course to Direct Track Course from a fix to Holding pattern Initial Constant radius Track between Heading to C D H R A I V T C A D F I M R Altitude Distance DME distance Next leg Manual termination Radial termination Fix EUROCONTROL Copyright 2011

Path Terminators 14 RNAV Types Digital AIM Training - AIXM Path Terminators 14 RNAV Types Course to an Altitude - CA Course to a Fix - CF Direct to a Fix - DF Fix to an Altitude - FA Fix to a Manual Termination - FM Racetrack Course Reversal (Alt Term) - HA Racetrack (Single Circuit - Fix Term) - HF Racetrack (Manual Termination) - HM Initial Fix - IF Track to a Fix - TF Constant Radius Arc - RF Heading to an Altitude - VA Heading to an Intercept - VI Heading to a Manual Termination - VM EUROCONTROL Copyright 2011

Digital AIM Training - AIXM Course to an Altitude Unspecified Position Course is flown making adjustment for wind 090 CA Leg EUROCONTROL Copyright 2011

SegmentLeg & SegmentPoint type = IF InitialLeg 1 + startPoint type = CF course = 276 courseType = MAG InitialLeg 2 + endPoint Waypoint = NO Indicator FACF = Yes Role = IF TerminalSegmentPoint role = RAD_DME PointReference angle = 96 (276-180) angleType = MAG distance = 9 NM Angle/Distance Indication Designator = IIF Navaid designator = GEBTI type = ICAO DesignatedPoint role = IAF Waypoint = YES TerminalSegmentPoint

SegmentLeg - Particular cases endConditionDesignator = ALTITUDE lowerLimitAltitude = 2000 ft MissedApproachLeg endConditionDesignator = INTERCEPT MissedApproachLeg distance = 18 NM DistanceIndication designator = TOU Navaid +distance

AircraftCharacteristics Approach Conditions finalApproachPath = STRAIGHT_IN ApproachCondition aircraftLandingCategory = C AircraftCharacteristics altitude = 218 ft altitudeCode = OCA altitudeReference = MSL height = 200 ft heightCode = OCH heightReference = HAT Minima

Circling Area

MSA Navaid Designator = VFA SafeAltitudeArea safeAreaType = MSA +centrePoint MSA safeAreaType = MSA SafeAltitudeArea arcDirection = CWA (clockwise Arc) fromAngle = 284 toAngle = 104 angleDirectionReference = TO innerDistance = 0 NM outerDistance = 25 NM lowerLimit = 1400 ft lowerLimitReference = MSL CircleSector 2 arcDirection = CWA (clockwise Arc) fromAngle = 104 toAngle = 284 angleDirectionReference = TO innerDistance = 0 NM outerDistance = 25 NM lowerLimit = 3000 ft lowerLimitReference = MSL CircleSector 1

TAA +IF +IAF TerminalArrivalArea safeAreaType = LEFT_BASE arcDirection = CWA (clockwise Arc) fromAngle = 83 toAngle = 173 angleDirectionReference = TO innerDistance = 15 NM outerDistance = 25 NM lowerLimit = 7100 ft lowerLimitReference = MSL CircleSector 1 safeAreaType = LEFT_BASE TerminalArrivalArea arcDirection = CWA (clockwise Arc) fromAngle = 83 toAngle = 173 angleDirectionReference = TO innerDistance = 0 NM outerDistance = 15 NM lowerLimit = 5000 ft lowerLimitReference = MSL CircleSector 2 designator = RIMOR DesignatedPoint +IAF designator = LC406 DesignatedPoint +IF

Miscellaneous - FAS datablock The FAS data block is defined for RNAV GNSS approaches with LPV minima (SBAS) guidanceSystem = LPV FinalLeg Note: The FAS DB can not be encoded as a whole (i.e. in one block) in AIXM 5.1 (E.g: AirportID) Extracted from RTCA DO229-D

Conclusion of AIXM seminar #1 Recommended navaid

Conclusion of AIXM seminar #1 Recommended navaid The current AIXM 5.1 encoding solution

Conclusion of AIXM seminar #1 Recommended navaid Point Reference Role

“Multi-branch” procedures

“Multi-branch” procedures ICAO Annex 11, Appendix 3 “The coded designator of a standard departure or arrival route instrument or visual, shall consist of: a) the coded designator or name-code of the significant point described in 2.1.1 a); followed by b) the validity indicator in 2.1.1 b); followed by c) the route indicator in 2.1.1 c), where required.” Example: ADOLA 5 B

“Multi-branch” procedures

“Multi-branch” procedures

“Multi-branch” procedures According to Annex 11, AIPs: multi-branch procedures do not exist? “common route” transitions have been introduced for FMS database size reasons AIXM 5 tries to support both views: individual procedures and multi-branch

“Multi-branch” procedures Procedure encoding workflow with AIXM Each leg belongs to one procedure No sequence number because it was assumed that start/end point data is sufficient to identify the order of the segments VEROR4A and VEROR4B are two different Procedure instances

“Multi-branch” procedures Procedure transitions can also be encoded “top-down”, using the pre-defined legs.

“Multi-branch” procedures Change proposal?

Digital AIM Training - AIXM Questions? Notes: EUROCONTROL Copyright 2011