1. Digital AIM Training - AIXM
Notes:
EUROCONTROL Copyright 2011

2. 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

3. Procedure = SID, STAR or Approach

4. 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

5. AIXM 4.5 Procedure Model

6. AIXM 4.5 Procedure Model

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

8. 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…)

9. 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

10. 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

11. 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

12. AIXM 5.1 Procedure Model - Overview

13. 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

14. 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)

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

16. 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

17. 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

18. 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

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

20. 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 ( )
angleType = MAG
distance = 9 NM
Angle/Distance Indication
Designator = IIF
Navaid
designator = GEBTI
type = ICAO
DesignatedPoint
role = IAF
Waypoint = YES
TerminalSegmentPoint

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

22. 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

23. Circling Area

24. 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

25. 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

26. 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

27. Conclusion of AIXM seminar #1
Recommended navaid

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

29. Conclusion of AIXM seminar #1
Recommended navaid
Point Reference Role

30. “Multi-branch” procedures

31. “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 a); followed by
b) the validity indicator in b); followed by
c) the route indicator in c), where required.”
Example: ADOLA 5 B

32. “Multi-branch” procedures

33. “Multi-branch” procedures

34. “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

35. “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

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

37. “Multi-branch” procedures
Change proposal?

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