Aeronautical Information Exchange Model (AIXM) – SID/STAR/IAP.

Aeronautical Information Exchange Model(AIXM) – SID/STAR/IAP

Content

• Context & History• Overview of the Procedure Model• Procedure Transition, SegmentLeg and SegmentPoint• Approach Conditions (minima…)• Circling Area• MSA• TAA• Miscellaneous• Some open issues

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

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

Procedure

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

StandardInstrumentDeparture

designator : TextSIDSTARDesignatorTypecontingencyRoute : CodeYesNoType

(from Departure Procedure)

<<feature>>

StandardInstrumentArrival

designator : TextSIDSTARDesignatorType

(from Arrival Procedure)

<<feature>>

InstrumentApproachProcedure

approachPrefix : CodeApproachPrefixTypeapproachType : CodeApproachTypemultipleIdentification : CodeUpperAlphaTypecopterTrack : ValBearingTypecirclingIdentification : CodeUpperAlphaTypecourseReversalInstruction : TextInstructionTypeadditionalEquipment : CodeApproachEquipmentAdditionalTypechannelGNSS : ValChannelNumberTypeWAASReliable : CodeYesNoType

(from 1 - Approach)

<<feature>>

Procedure

communicationFailureInstruction : TextInstructionTypeinstruction : TextInstructionTypedesignCriteria : CodeDesignStandardTypecodingStandard : CodeProcedureCodingStandardTypeflightChecked : CodeYesNoTypename : TextNameTypeRNAV : CodeYesNoType

(from Procedure Overview)

<<feature>>

AirportHeliport(from Airport/Hel iport)

<<feature>>

0..* 0..*0..*

+airportHeliport

0..*

services

CodeApproachPrefixBaseType

HI : stringCOPTER : stringCONVERGING : stringOTHER : string

(from AIXM Data Types)

<<codelist>>

AIXM 5.1 Procedure Model - OverviewDesignator

approachPrefix = Blank

approachType = VOR

multipleIdentification = X

copterTrack = Blank

circlingIdentification = Blank

courseReversalInstruction = Blank

SID & STAR: designator (+ name?)

Approach: name + 6 first attributes of class InstrumentApproachProcedure





<<feature>>




<<feature>>



(from 1 - Approach)

<<feature>>

Procedure

communicationFailureInstruction : TextInstructionTypeinstruction : TextInstructionTypedesignCriteria : CodeDesignStandardTypecodingStandard : CodeProcedureCodingStandardTypeflightChecked : CodeYesNoTypename : TextNameTypeRNAV : CodeYesNoType


<<feature>>

AirportHeliport(from Airport/Hel iport)

<<feature>>

0..* 0..*0..*

+airportHeliport

0..*

services

CodeApproachPrefixBaseType

HI : stringCOPTER : stringCONVERGING : stringOTHER : string


<<codelist>>

CodeProcedureCodingStandardBaseType

PANS_OPS : stringARINC_424_15 : stringARINC_424_18 : stringARINC_424_19 : stringOTHER : string


<<codelist>>

RunwayDirection(from Runway)

<<feature>>LandingTakeoffAreaCollection


<<object>> 0..1

+landing

0..1

0..1+takeoff

0..1 0..1+arrival

0..1

0..* 0..*0..*

+runway

0..*

isLocatedAt

isForLandingAtisArrivalFor

isForTakeoffAt




<<feature>>




<<feature>>



(from 1 - Approach)

<<feature>>

Connection SID/STAR/Appr -> RunwayDirection is realised through class LandingTakeOffAreaCollection

- Attribute RNAV is used to identify an RNAV procedure

- For an approach, attribute approachType can also carry the value “RNAV”


GuidanceService(from Guidance Service)

<<choice>>

AircraftCharacteristic(from Aircraft and Flight)

<<object>>

InformationService(from Service)

<<feature>>

Procedure(from Procedure Overview)

<<feature>>

0..*+guidanceFacility

0..*

isBasedOn

0..*+aircraftCharacteristic

0..*

isLimitedTo0..*

0..*

0..*

+clientProcedure

0..*

concerns

AirTrafficControlService(from Service)

<<feature>>

0..*

0..*

0..*+clientProcedure

0..* controls isActiveBy 0..*

+availability

0..*Procedure


<<feature>> ProcedureAvailability

status : CodeProcedureAvailabilityType

(from Usage)

<<object>>

PropertiesWithSchedule(from Schedules)

<<object>>

CodeProcedureAvailabilityBaseType

USABLE : stringUNUSABLE : stringOTHER : string


<<codelist>>

InstrumentApproachProcedure(from 1 - Approach)

<<feature>>StandardInstrumentArrival


<<feature>>StandardInstrumentDeparture


<<feature>>


<<feature>>

StandardInstrumentArrival(from Arrival Procedure)

<<feature>>

ArrivalLeg(from Procedure Overview)

<<feature>>

1..*

0..1

1..*

+arrival 0..1

isPartOf

DepartureLeg(from Procedure Overview)

<<feature>>

StandardInstrumentDeparture(from Departure Procedure)

<<feature>>

0..1

1..*

+departure 0..1

1..*

isPartOf


<<feature>>

SegmentLeg(from Procedure Overview)

<<feature>>ApproachLeg


<<feature>>

1..*

0..1

1..*

+approach 0..1


<<feature>>

11 0..*contains

+flightTransition

0..*ProcedureTransition


<<object>>

0..*0..*

0..*

isComposedOf

+transitionLeg0..*


<<feature>>


<<feature>>

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

ProcedureDesign

ProcedureEncoding

• A Procedure can be divided into a series of Procedure Transitions

• More optimised for Procedure Encoding

ProcedureTransition

transitionId : CodeDesignatedPointDesignatorTypetype : CodeProcedurePhaseTypeinstruction : TextInstructionTypevectorHeading : ValBearingType


<<object>>


<<feature>> isComposedOf0..*+transitionLeg 0..*

0..*

ProcedureTransitionLeg

seqNumberARINC : NoSequenceType


<<object>>

Procedure Transition & SegmentLeg

runway

IAF 1

IAF 2 IF MAP

3 “approach transitions” 1 final approach 1 missed approach

WP 4

FAF

leg 1

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)

ProcedureTransition



<<object>>

0..1

+trajectory

represents0..1 Curve

horizontalAccuracy : ValDistanceType

(from Geometry)

<<object>>


<<feature>>

ProcedureTransition



<<object>>

1

0..*

1

+flightTransition 0..*

contains

CodeProcedurePhaseBaseType

RWY : stringCOMMON : stringEN_ROUTE : stringAPPROACH : stringFINAL : stringMISSED : stringMISSED_P : stringMISSED_S : stringENGINE_OUT : stringOTHER : string


<<codelist>>

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

SegmentLeg

HoldingPattern

For an approach transition

IntermediateLeg

requiredNavigationPerformance : CodeRNPType...

<<feature>>

InitialLeg


<<feature>>

ArrivalFeederLeg


<<feature>>

FinalLeg

guidanceSystem : CodeFinalGuidanceTypelandingSystemCategory : CodeApproachGuidanceTypeminimumBaroVnavTemperature : ValTemperatureTypernpDMEAuthorized : CodeYesNoTypecourseOffsetAngle : ValBearingTypecourseOffsetSide : CodeSideTypecourseCentrelineDistance : ValDistanceTypecourseOffsetDistance : ValDistanceTypecourseCentrelineIntersect : CodeRelativePositionType

<<feature>>

MissedApproachLeg

type : CodeMissedApproachTypethresholdAfterMAPT : CodeYesNoTypeheightMAPT : ValDistanceVerticalTyperequiredNavigationPerformance : CodeRNPType...

<<feature>>

ApproachLeg<<feature>>

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

SegmentLeg

endConditionDesignator : CodeSegmentTerminationTypelegPath : CodeTrajectoryTypelegTypeARINC : CodeSegmentPathTypecourse : ValBearingTypecourseType : CodeCourseTypecourseDirection : CodeDirectionReferenceTypeturnDirection : CodeDirectionTurnTypespeedLimit : ValSpeedTypespeedReference : CodeSpeedReferenceTypespeedInterpretation : CodeAlti tudeUseTypebankAngle : ValAngleTypelength : ValDistanceTypeduration : ValDurationTypeprocedureTurnRequired : CodeYesNoTypeupperLimitAltitude : ValDistanceVerticalTypeupperLimitReference : CodeVerticalReferenceTypelowerLimitAlti tude : ValDistanceVerticalTypelowerLimitReference : CodeVerticalReferenceTypealtitudeInterpretation : CodeAltitudeUseTypealtitudeOverrideATC : ValDistanceVerticalTypealtitudeOverrideReference : CodeVerticalReferenceTypeverticalAngle : ValAngleType

<<feature>>

ApproachLeg

<<feature>>

ArrivalLeg

<<feature>>DepartureLeg

<<feature>>

SegmentLeg

endConditionDesignator : CodeSegmentTerminationTypelegPath : CodeTrajectoryTypelegTypeARINC : CodeSegmentPathTypecourse : ValBearingTypecourseType : CodeCourseTypecourseDirection : CodeDirectionReferenceTypeturnDirection : CodeDirectionTurnTypespeedLimit : ValSpeedTypespeedReference : CodeSpeedReferenceTypespeedInterpretation : CodeAltitudeUseTypebankAngle : ValAngleTypelength : ValDistanceTypeduration : ValDurationTypeprocedureTurnRequired : CodeYesNoTypeupperLimitAltitude : ValDistanceVerticalTypeupperLimitReference : CodeVerticalReferenceTypelowerLimitAltitude : ValDistanceVerticalTypelowerLimitReference : CodeVerticalReferenceTypealtitudeInterpretation : CodeAltitudeUseTypealtitudeOverrideATC : ValDistanceVerticalTypealtitudeOverrideReference : CodeVerticalReferenceTypeverticalAngle : ValAngleType

<<feature>>

For a SID

For aSTAR

For an Approach

For a final approach

For a missed approach

RNAV – Path Terminator Leg Type

TerminatorPath

CA

DFI

MR

Altitude

Distance

DME distance

Next leg

Manual termination

Radial termination

FixF

Constant DME arc

Course to

Direct Track

Course from a fix to

Holding pattern

Initial

Constant radius

Track between

Heading to

CD

H

R

A

I

VT

• 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

Path Terminators 14 RNAV Types

UnspecifiedPosition

090

CA Leg

0

Course is flown making adjustment for wind

Course to an Altitude

SegmentPoint

reportingATC : CodeATCReportingTypeflyOver : CodeYesNoTypewaypoint : CodeYesNoTyperadarGuidance : CodeYesNoType

(from Point Reference)

<<object>>

isFoundUsing

0..*0..* +facilityMakeup

PointReference

role : CodeReferenceRoleTypepriorFixTolerance : ValDistanceSignedTypepostFixTolerance : ValDistanceSignedType


<<object>>

0..*

isBasedOnDistance+facilityDistance

DistanceIndication(from Point Reference)

<<feature>>AngleIndication


<<feature>>

+facilityAngle 0..*0..*

isBasedOnAngle

SegmentPoint



<<object>>

isLocatedAt

0..10..1+pointChoice

SignificantPoint(from Points)

<<choice>>

0..1+fixDesignatedPoint 0..1

DesignatedPoint

designator : CodeDesignatedPointDesignatorTypetype : CodeDesignatedPointTypename : TextNameType

(from Points)

<<feature>>

TerminalSegmentPoint

role : CodeProcedureFixRoleTypeleadRadial : ValBearingTypeleadDME : ValDistanceTypeindicatorFACF : CodeYesNoType


<<object>>

SegmentPoint



<<object>>


<<feature>>

0..10..1 0..1+endPoint

0..1

terminatesAt

0..1+arcCentre0..1

SegmentLeg & SegmentPoint

designator = GEBTI

type = ICAO

DesignatedPoint

role = IAF

Waypoint = YES


type = IF

InitialLeg 1

+ startPoint

type = CF

course = 276

courseType = MAG

InitialLeg 2

+ endPoint

Waypoint = NO

Indicator FACF = Yes

Role = IF


role = RAD_DME

PointReference

angle = 96 (276-180)

angleType = MAG

distance = 9 NM

Angle/Distance Indication

Designator = IIF

Navaid

SegmentLeg - Particular cases

endConditionDesignator = ALTITUDE

lowerLimitAltitude = 2000 ft

MissedApproachLeg

endConditionDesignator = INTERCEPT

MissedApproachLeg

distance = 18 NM

DistanceIndication

designator = TOU

Navaid

+distance


<<feature>>


<<choice>>

DistanceIndication(from Point Reference)

<<feature>>

0..1+distance 0..1

isLimitedBy

0..*

0..1

0..*

+pointChoice 0..1

uses

Minima

altitude : ValDistanceVerticalTypealtitudeCode : CodeMinimumAltitudeTypealtitudeReference : CodeVerticalReferenceTypeheight : ValDistanceVerticalTypemilitaryHeight : ValDistanceVerticalTyperadioHeight : ValDistanceVerticalTypeheightCode : CodeMinimumHeightTypeheightReference : CodeHeightReferenceTypevisibility : ValDistanceTypemilitaryVisibility : ValDistanceTypemandatoryRVR : CodeYesNoTyperemoteAltimeterMinima : CodeYesNoType

(from 5 - Minima)

<<object>>

EquipmentUnavailableAdjustment

type : CodeEquipmentUnavailableTypeapproachLightingInoperative : CodeYesNoType

(from 5 - Minima)

<<object>>

0..*

+adjustmentINOP

0..*isAdjustedBy

EquipmentUnavailableAdjustmentColumn

guidanceEquipment : CodeApproachTypelandingSystemLights : CodeYesNoTypeequipmentRVR : CodeYesNoTypevisibilityAdjustment : ValDistanceVerticalTypeapproachLightingInoperative : CodeYesNoType

(from 5 - Minima)

<<object>>

0..*contains+adjustmentINOPCol0..*

ApproachCondition

finalApproachPath : CodeMinimaFinalApproachPathTyperequiredNavigationPerformance : CodeRNPTypeclimbGradient : ValSlopeType

(from 1 - Approach)

<<object>>

0..1indicates

0..1

+minimumSetMinima

altitude : ValDistanceVerticalTypealtitudeCode : CodeMinimumAltitudeTypealtitudeReference : CodeVerticalReferenceTypeheight : ValDistanceVerticalTypemilitaryHeight : ValDistanceVerticalTyperadioHeight : ValDistanceVerticalTypeheightCode : CodeMinimumHeightTypeheightReference : CodeHeightReferenceTypevisibility : ValDistanceTypemilitaryVisibility : ValDistanceTypemandatoryRVR : CodeYesNoTyperemoteAltimeterMinima : CodeYesNoType

(from 5 - Minima)

<<object>>

FinalLeg(from Procedure Overview)

<<feature>>

ApproachCondition


(from 1 - Approach)

<<object>>

0..*

hasEstablished

+condition0..*

Approach Conditions

ApproachCondition


(from 1 - Approach)

<<object>>

0..*

isApprovedFor

0..* +aircraftCategory

AircraftCharacteristic(from Aircraft and Flight)

<<object>>

finalApproachPath = STRAIGHT_IN

ApproachCondition

aircraftLandingCategory = C

AircraftCharacteristics

altitude = 218 ft

altitudeCode = OCA

altitudeReference = MSL

height = 200 ft

heightCode = OCH

heightReference = HAT

Minima


<<feature>>

Surface(from Geometry)

<<object>>

PropertiesWithSchedule(from Schedules)

<<object>>

CircleSector(from Circle Sector)

<<object>>

CirclingRestriction(from 4 - Circling)

<<object>>

0..1

+restrictionArea

0..1 isDepictedBy

0..1+sectorDescription

0..1

isDescribedBy

CirclingArea(from 4 - Circling)

<<feature>>0..*0..1 0..*

+approach

0..1isUsedOn

0..1+extent 0..1

isIllustratedBy

AircraftCharacteristic(from Aircraft and Fl ight)

<<object>>

0..1+aircraftCategory

0..1

isEvaluatedFor

Minima(from 5 - Minima)

<<object>>

ApproachCondition


(from 1 - Approach)

<<object>>

0..*

+condition

0..*

has

0..*+circlingRestriction

0..*

isAppliedTo

0..*+aircraftCategory

0..*

isApprovedFor

0..1+minimumSet

0..1

indicates

Circling Area

SafeAltitudeAreaSector

bufferWidth : ValDistanceType

<<object>>

0..*isResolvedBy

+significantObstacle

0..*

Obstruction

requiredClearance : ValDistanceTypeminimumAltitude : ValDistanceVerticalTypesurfacePenetration : CodeYesNoTypeslopePenetration : ValAngleTypecontrolling : CodeYesNoTypecloseIn : CodeYesNoType

(from Surface Assessment)

<<object>>

hasApplied

0..*+adjustment 0..*

AltitudeAdjustment

altitudeAdjustmentType : CodeAltitudeAdjustmentTypeprimaryAlternateMinimum : CodeYesNoTypealtitudeAdjustment : ValDistanceVerticalTypelocalRemoteCode : CodeYesNoType

(from Surface Assessment)

<<object>>

SafeAltitudeArea

safeAreaType : CodeSafeAltitudeType

<<feature>>

isDefinedBy

+sector 0..*

SafeAltitudeAreaSector

bufferWidth : ValDistanceType

<<object>>

0..1isDefinedBy0..1+sectorDefinition

CircleSector

arcDirection : CodeArcDirectionTypefromAngle : ValBearingTypetoAngle : ValBearingTypeangleType : CodeBearingTypeangleDirectionReference : CodeDirectionReferenceTypeinnerDistance : ValDistanceTypeouterDistance : ValDistanceTypeupperLimit : ValDistanceVerticalTypeupperLimitReference : CodeVerticalReferenceTypelowerLimit : ValDistanceVerticalTypelowerLimitReference : CodeVerticalReferenceType

(from Circle Sector)

<<object>>


<<object>>

0..1

+extent

isPortrayedBy0..1

0..*

SafeAltitudeArea


<<feature>>


<<feature>>

isProtectedBy

+safeAltitude 0..20..2isDefinedAt

0..* +location

AirportHeliport(from Airport/Heliport)

<<feature>>

0..*

SafeAltitudeArea


<<feature>>

0..1

isBasedOn

+centrePoint0..1


<<choice>>

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


fromAngle = 104

toAngle = 284






CircleSector 1

Designator = VFA

Navaid+centrePoint

TerminalArrivalArea

arrivalAreaType : CodeTAATypeouterBufferWidth : ValDistanceTypelateralBufferWidth : ValDistanceType

(from 2 - Terminal Arrival Area)

<<feature>> 0..1isUsedForAngle

0..1

+IAFSignificantPoint

(from Points)

<<choice>>

+IF

0..1isUsedForDistance

0..1

TerminalArrivalAreaSector

flyByCode : CodeYesNoTypeprocedureTurnRequired : CodeYesNoTypealtitudeDescription : CodeAltitudeUseType


<<object>>

0..*

isResolvedBy

0..* +significantObstacle

Obstruction(from Surface Assessment)

<<object>>

0..*

hasApplied

AltitudeAdjustment(from Surface Assessment)

<<object>>

+adjustment 0..*

TerminalArrivalArea



<<feature>>

0..*

isDefinedBy

+sector 0..*

TerminalArrivalAreaSector

flyByCode : CodeYesNoTypeprocedureTurnRequired : CodeYesNoTypealtitudeDescription : CodeAltitudeUseType


<<object>>0..1

projects


<<object>>

+extent0..1

+buffer

0..10..1shows

0..1CircleSector

(from Circle Sector)

<<object>>0..1

isDescribedBy

TAA

designator = LC406

DesignatedPoint

+IF

designator = RIMOR

DesignatedPoint

+IAF


<<feature>>

+approachRNAV0..1

isFeederFor

0..1

TerminalArrivalArea



<<feature>>


fromAngle = 83

toAngle = 173






CircleSector 1


fromAngle = 83

toAngle = 173






CircleSector 2

safeAreaType = LEFT_BASE

TerminalArrivalArea

Miscellaneous - FAS datablock

• The FAS data block is defined for RNAV GNSS approaches with LPV minima (SBAS)

FASDataBlock

horizontalAlarmLimit : ValAlarmLimitTypeverticalAlarmLimit : ValAlarmLimitTypethresholdCourseWidth : ValDistanceTypelengthOffset : ValDistanceTypeCRCRemainder : ValHexTypeoperationType : NoSequenceTypeserviceProviderSBAS : NoSequenceTypeapproachPerformanceDesignator : NoSequenceTyperouteIndicator : AlphaTypereferencePathDataSelector : NoSequenceTypereferencePathIdentifier : AlphanumericTypecodeICAO : AlphanumericType

<<object>>

+FASData 0..1

has

0..1

FinalLeg

guidanceSystem : CodeFinalGuidanceTypelandingSystemCategory : CodeApproachGuidanceTypeminimumBaroVnavTemperature : ValTemperatureTypernpDMEAuthorized : CodeYesNoTypecourseOffsetAngle : ValBearingTypecourseOffsetSide : CodeSideTypecourseCentrelineDistance : ValDistanceTypecourseOffsetDistance : ValDistanceTypecourseCentrelineIntersect : CodeRelativePositionType


<<feature>>CodeFinalGuidanceBaseType

LPV : stringLNAV_VNAV : stringLNAV : stringGLS : stringASR : stringARA : stringARSR : stringPAR : stringILS : stringILS_DME : stringILS_PRM : stringLDA : stringLDA_DME : stringLOC : stringLOC_BC : stringLOC_DME : stringLOC_DME_BC : stringMLS : stringMLS_DME : stringNDB : stringNDB_DME : stringSDF : stringTLS : stringVOR : stringVOR_DME : stringTACAN : stringVORTAC : stringDME : stringLP : stringOTHER : string


<<codelist>>

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

Recommended navaidAIXM Seminar

• From the IFP Design perspective, one fundamental information about a (conventional Procedure) Segment Leg is the location and type of the Navaid Equipment providing the guidance (if any). The design of the leg’s protection areas largely depend on it.

• Now, in ARINC 424 this information may be often (but not always!!) deduced from different attributes of the leg, such as the Path/Terminator, the Recommended Navaid and so on.

• Unfortunately there are cases where we are not able to infer the providing guidance Navaid from the ARINC 424 codification. Nor it seems things are going better with AIXM 5.

Providing guidance Navaid

PPG/2010/0110 All rights reserved to IDS

AIXM Seminar

• Consider the case of a “Course to a Radial” (CR) Segment Leg:

• The “Recommended Navaid” field refersto the Navaid defining the Radial (170°),not the one providing the guidancealong the CR Leg (120°)

• How can we deduce the NavEqproviding the course?

CR Segment Legs


Conclusion of AIXM seminar #1

Recommended navaid

The current AIXM 5.1 encoding solution

ArrivalLeg<<feature>>

DepartureLeg<<feature>>



role : CodeProcedureFixRoleTypeleadRadial : ValBearingTypeleadDME : ValDistanceTypeindicatorFACF : CodeYesNoType


<<object>>SegmentLeg<<feature>>0..1

+startPoint

0..1

beginsAt

0..1

+endPoint

0..1

terminatesAt

0..1

+arcCentre

0..1 has

PointReference

role : CodeReferenceRoleTypepriorFixTolerance : ValDistanceSignedTypepostFixTolerance : ValDistanceSignedType


<<object>>SegmentPoint



<<object>>

0..*

+facilityMakeup

0..*isFoundUsing


Recommended navaid

Point Reference Role


“Multi-branch” proceduresAIXM Seminar

• An IFP is not necessarily composed of a single sequence of consecutive Legs

• On the contrary, national AIPs publish into a single procedure chart a group of IFPs sharing a common portion

Multi-branch Procedures


Runway Transitions Enroute TransitionsCommonTransition

“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


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


• 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



<<feature>>

1..*

0..1

1..*

+approach

0..1

isPartOfSegmentLeg<<feature>>

Procedure<<feature>>


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

ProcedureTransitionLeg

seqNumberARINC : NoSequenceType

<<object>>

ProcedureTransition


<<object>>

0..*

0..*

0..*

+transitionLeg

isComposedOf

1

0..*

+flightTransition

0..*

0..*

contains

1Procedure

<<feature>>

SegmentLeg<<feature>>



<<feature>>

1..*

0..1

1..*

+approach

0..1

isPartOfSegmentLeg<<feature>>

Procedure<<feature>>


AIXM Seminar

• Add the <<object>> ProcedurePath to the model

First Proposal


<<feature>>

Procedure

<<object>>

ProcedurePath

<<object>>

ProcedureTransition

1

1

0..*

0..*

0..*

<<object>>

PathTransition(seqNumber)

• A Procedure would be an unordered collection of Paths.

• A Path would be an orderedsequence of Transitions

• A Transition is an orderedsequence of Legs:

• Change proposal?

Questions?Questions?

Aeronautical Information Exchange Model (AIXM) – SID/STAR/IAP.

Documents

Transcript of Aeronautical Information Exchange Model (AIXM) – SID/STAR/IAP.