1 / 38

Content

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:

michaeljwilliams
Download Presentation

Content

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Procedure = SID, STAR or Approach

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

  4. AIXM 4.5 Procedure Model

  5. AIXM 4.5 Procedure Model

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

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

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

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

  10. Connection SID/STAR/Appr -> RunwayDirection is realised through class LandingTakeOffAreaCollection 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”

  11. AIXM 5.1 Procedure Model - Overview

  12. 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 ProcedureDesign ProcedureEncoding

  13. IAF 1 WPT 1 WP 4 leg 1 leg 2 IAF 2 IF FAF MAP leg 1 runway WP 3 WP 2 3 “approach transitions” 1 final approach 1 missed approach Procedure Transition & SegmentLeg • 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)

  14. SegmentLeg HoldingPattern Procedure Transition & SegmentLeg • Approach Transition GEBTI • Approach Transition VFA • Final Approach • Missed Approach

  15. For an approach transition 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 anApproach For aSTAR For aSID For a missed approach For a final approach

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

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

  18. Unspecified Position Course to an Altitude Course is flown making adjustment for wind 0 090 CA Leg

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

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

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

  22. Circling Area

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

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

  25. FinalLeg guidanceSystem = LPV Miscellaneous - FAS datablock • The FAS data block is defined for RNAV GNSS approaches with LPV minima (SBAS) 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

  26. Conclusion of AIXM seminar #1 Recommended navaid

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

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

  29. “Multi-branch” procedures

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

  31. “Multi-branch” procedures

  32. “Multi-branch” procedures

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

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

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

  36. “Multi-branch” procedures • Change proposal?

  37. Questions?

More Related