Database Coding and Publication

Transcription

1 MIXED MODE Database Coding and Publication Sorin-Dan Onitiu Jeppesen 17 October 2012 An inter-disciplinary overview of PBN design, coding and charting 1

2 Issue: Chart, Database, and Avionics Harmonization Generally, basic procedure design has been created for the analog world ; The art of procedure coding is one that balances the intent of design and the FMS requirements Virtually all the aeronautical databases are loaded according to ARINC 424 standard which specs cover a large percentage of aeronautical requirements, but not all combinations No common standard implemented to have same information charts vs. database 17

3 Challenge: Role of database & evolution of PD criteria Ground-Navaid, Complicated, Rigid paths, Nonstandard, Manually flow: Analog World 3 Satellite, Simple, Flexible paths, Standard shape, database-driven: Digital World

4 Results: Charts & Procedure coding 4

5 Approach Coding & Design Route Type concept includes a primary route type and up to two route type qualifiers Q1& Q2; Description: a) Approach Transition (Route Type A ); b) Final Approach Transition (Route Type R = APV, H = RNP PBN or J = GLS) c) Missed Approach Transition (Route Type Z ); 5

6 Approach Coding Structure Fixes associated with approach coding ARINC 424 PANS-OPS Approach Transition IAF FACF* Initial Segment IAF - IF Final Transition FACF* MAP Intermediate and Final Segments * FACF (ARINC) = IF (PANS-OPS) IF FAF - MAPt Missed Approach Transition MAP MAHP or end of MA Initial/Intermediate/ Final MA Segments MAPt end of MA phase Final Approach Transition: As a minimum, the coding of final segment must include a fix for the FAF and MAP. A third fix called FACF has to be always included when design IF is published. 21

7 PBN design/charting & coding considerations Mixed mode (RNAV/Conventional) coding Primary/Secondary Missed Approach MIXED MODE 7

8 MIXED MODE PBN design/charting & coding considerations Conventional Initial Departure of RNAV 1 SID 8

9 Coding PBN design/charting & coding considerations Vertical Angle for NPA is always included in all straight-in NPA coding solution; An FMS usually builds a profile backwards from a point 50ft above the threshold to the initial (FAF and/or SDF); Altitude at MAP fix is NOT any of procedure MDA, but it s a computed mandatory value; MDA and DA are NOT part of the approach coding solution! 9

10 PBN design/charting & coding considerations Coding of speed restrictions Speed/Altitude restrictions applied at the waypoint: general situation like Below FL100/IAS 250KT has no procedure coding solution; Speed limitation depicted somewhere during a turn shall be associated with a waypoint. For approaches, speed limit in FMS will be applied forward throughout the procedure until superseded by another speed limit. 10

11 PBN design/charting & coding considerations Coding of altitude constraints Altitude constraints have to be clearly associated to a fix; No appropriate coding solution for minimum segment altitude or MEA s. Expect altitude, Recommended, Tactical procedure altitude cannot be translated appropriately in FMS box language; 11

12 PBN design/charting & coding considerations Charted Information not provided in NavData database 12

13 Lessons Learned/Summary ARINC 424 is the encoding standard for navigational database consumed by FMS; For the data houses, ARINC 424 provides the measure of standardization they can apply; However: All things are not equal in the world of FMS & how they execute a procedure defined with Path & Terminator legs; Most of limitations are coming from the FMS execution logic and not procedure design constraints; ARINC 424 is not a charting standard file structure (it maybe addressed by the NDB industry group; Challenges DB/Publication, specifically for Mixed Mode operations (cannot properly be reflected in the FMS); Collaboration of all team players is highly recommended! Database Coding & Publication 13