International Civil Aviation Organization. IFPP Integration Working Group Phoenix, AZ, USA. January 28 February 3, 2012 ARINC 424 DERIVED CHARTING

Transcription

1 International Civil Aviation Organization IWG/WP xxx January 2012 WORKING PAPER IFPP Integration Working Group Phoenix, AZ, USA January 28 February 3, 2012 ARINC 424 DERIVED CHARTING (Presented by Stephane Dubet) SUMMARY This Working Paper identifies a potential means to further develop charting and navigation data requirements to promote harmonization of charts, databases and avionics systems. It proposes to consider the generation of charts corresponding to existing procedures as from the existing ARINC 424 databases. This would require a common set of rules that would associate typical series of path terminators with elementary IAC segments. The Working Paper suggests a first review and discussion of these ARINC 424 derived charting propositions. 1. INTRODUCTION 1.1 At the IFPP IWG meeting in January 2011, it was proposed to develop ARINC 424 derived charting rules that could support initial population or update of aeronautical chart portfolios as from ARINC 424, thus improving the quality of charts and their consistency with databases. 1.2 At the IWG meeting in June 2011, the group continued to express interest in the concept of ARINC 424 derived charts, but also expressed the need to see something tangible about how this could work, including some examples. (9 pages) IFPP IWG Jan WP - ARINC424 derived charting

2 IWG EXAMPLE OF SUCCESSFUL CHART GENERATION This section shows an example of an ARINC424 derived chart (Agen La Garenn SID chart). Publication

3 - 3 - IWG/7-WP/ ARINC 424 derived chart Zoom Comments ARINC 424 enables the generation of paths that can directly be used to develop the chart. The only point to be noted is that the SID (or STAR) designation in ARINC, limited to 6 characters, does not match the designation of the charts, which uses 7 characters (e.g. SECH2E au lieu de SECHE2E).

4 IWG EXAMPLE OF CHART GENERATION LIMITATIONS This section shows some limitations to the chart generation as from ARINC 424. It provides various examples where it is deemed that rules to support ARINC 424 derived charting would be beneficial 3.1 TF segment The course values are not provided for TF segment in ARINC 424 but are portrayed on charts. The same applies to the distance between points, which is not included in ARINC 424 but may be portrayed on charts. Magnetic course and distance not coded in ARINC 424 The magnetic course is published. Depending on the chart type, the distance may also be portrayed. SEURP LFMLLFFI13L AAVN 040ZEBRALFEA0E TF SEURP LFMLLFFI13L AAVN MLLFPC0E TF

5 - 5 - IWG/7-WP/ 3.2 VF segment The use of VM segments makes difficult the charting of the corresponding paths, as illustrated below. End of NDB + DME RWY 29 at Agen La Garenne procedure coding SEURP LFBALFFQ29 Q 030MQ29 LFPC0E M CF AG LF D S SEURP LFBALFFQ29 Q 040MQ29 LFPC0E M FD AGN LF D S SEURP LFBALFFQ29 Q E VM S Published chart The part circled in red cannot be derived from the ARINC 424 coding.

6 IWG MAPT location There is a difference between the MAP used in ARINC 424 and the MAPt considered by the procedure designer. This raises a difficulty when generating the chart from the ARINC 424 code, as shown below for Marseille Provence I13LZ. In ARINC 424, the MAP is defined at the runway threshold, in this case with a 63 ft altitude. SEURP LFMLLFFI13LZ I 030RW13LLFPG0G M CF ML LF PI DS In design and charting, the MAPT is located 0.8 NM ahead of the runway threshold, with a 380 ft MDA.

7 - 7 - IWG/7-WP/ 3.4 Altitude and speed restrictions over segments In ARINC 424, all altitude and speed restrictions are applicable at points ( 5.30 et 5.72). Minimum Obstacle Clearance Altitudes over flight segments are not included although they are portrayed on charts. The following example illustrates the issue. Montpellier VOR12L coding (extract) SEURP LFMTLFFD13LZ ALEKLA 010LEKLALFPC0E CA FD FJR LF D + FL S SEURP LFMTLFFD13LZ ALEKLA 020D302RLFPC0E CF FJR LF D S SEURP LFMTLFFD13LZ ALEKLA 030D302MLFPC0E CF FJR LF D S If it was used to generate the chart, the result would be as follows (see altitude and speed restrictions). FL070 et IAS 250 sur le fix IAF LEKLA 5000 ft AMSL sur le fix situé à 18NM de FJR 4000 ft AMSL et 185 kt MAX à partir du point à 13NM

8 IWG The actual chart is as follows (see altitude and speed restrictions): IAS 250 sur le fix IAF LEKLA FL070 jusqu à 25 NM de FJR puis 5000 ft AMSL jusqu à 18NM de FJR et passage à 4000 ft AMSL 185 kt MAX avant le point 13NM FJR. 4. RECOMMENDATIONS The IWG is invited to: (1) review and discuss the ARINC 424 derived charting examples provided in this paper, both the one illustrating the successful generation of a chart and the ones showing limitations to such an automatic generation (2) determine potential ways to address the limitations illustrated in this paper (set of rules in a guidance material? propositions of amendment to ICAO or ARINC standards?) (3) have the ARINC 424 derived charting initiative presented at the next IFPP WGH for their information but also to get WGH support about work continuation within the IWG

9 - 9 - IWG/7-WP/