Navigation & flight planning by FMS-equipped aircraft

1. Navigation & flight planningby FMS-equipped aircraft ARAB INSTRUMENT PROCEDURE DESIGN SEMINAR AI/EE-A 441.0144/01

2. P.3 Navigation & flight management P.4 An overview of aircraft avionics P.5 GPS PRIMARY navigation P.8 RNP navigation P.10 Flight management P.11 Flight planning P.12 Vertical navigation P.13 Navigation database : ARINC 424 format P.14 Path terminator concept P.15 IF leg type P.16 TF leg type P.17 RF leg type (new leg type) P.18 CF leg type P.19 DF leg type P.20 FA leg type P.21 FC leg type P.22 FD leg type P.23 FM leg type P.24 CA leg type P.25 CD leg type P.26 CI leg type P.27 CR leg type P.28 AF leg type P.29 VA leg type P.30 VD leg type P.31 VI leg type P.32 VM leg type P.33 VR leg type P.34 PI leg type P.35 HA, HF, HM leg types P.36 ARINC 424 leg transitions P.37 Navigation database related issues P.38 Compatibility... P.39 Production process P.40 Some top level issues P.44 Recommendations P.45 Issues summary P.46 Short term P.52 Medium term P.54 Longer term Table of contents

3. Navigation & flight management ARAB INSTRUMENT PROCEDURE DESIGN SEMINAR

4. An overview of aircraft avionics ... • Modern avionics have considerably improved flight safety on non-precision approaches : • accurate position (RNP 0.3) • flight plan display on EFIS • reference approach path • automated lateral guidance • automated vertical guidance • ground proximity warning system (GPWS) • terrain display on EFIS (EGPWS) • terrain clearance floor warnings (EGPWS)

5. 3 degrees 700’ AGL 500’ AGL 5 NM 12 NM 15 NM An overview of aircraft avionics ...

6. GPS PRIMARY navigation • AIRBUS is promoting GPS PRIMARY navigation • All new A318/A319/A320/A321/A330/A340 production aircraft are fitted with GPS PRIMARY capable equipment • Ground navaids are only used as a backup • VOR, DME • ADF is not used for navigation • only for procedural navigation check

7. EGPWS MMR or GPSSU ADIRS FMS GPS raw data GPS position IRS position GPIRS position FMS position AIRBUS system GPS architecture • Hybrid (A320 family & A340 family)

8. EGPWS MMR FMS GPS position IRS position FMS position IRS AIRBUS system GPS architecture • Autonomous (A300-600/A310 family, retrofit solution for A320 family with older ADIRS)

9. GPS PRIMARY crew interface • In GPS PRIMARY mode, on-board system integrity has a confidence greater than99.9%, so the FMS position can be relied upon without any additional navigation cross check (using ground based navaids) • Clear status of GPS PRIMARY is therefore provided to the crew

10. GPS PRIMARY GPS PRIMARY LOST GPS PRIMARY crew interface CLB FLT4567890 CRZ OPT REC MAX FL350 FL370 FL390 <REPORT UPDATE AT *[ ] BRG /DIST ---° /----.-TO[ ] PREDICTIVE <GPS GPS PRIMARY REQUIRED ACCUR ESTIMATED 2.1NMHIGH0.16NM GPS PRIMARY CLB FLT4567890 CRZ OPT REC MAX FL350 FL370 FL390 <REPORT UPDATE AT *[ ] BRG /DIST ---° /----.-TO[ ] PREDICTIVE <GPS REQUIRED ACCUR ESTIMATED 2.1NMHIGH0.28NM GPS PRIMARY LOST + triple click during approach

11. RNP navigation • AIRBUS is promoting RNP (required navigation performance) • All A318/A319/A320/A321/A330/A340 aircraft are fitted or have been retrofitted with RNP capable equipment • RNP allows crew awareness of estimated aircraft position accuracy compared to procedure designer’s required performance assumptions

12. RNP crew interface • RNP management provides HIGH and LOW navigation accuracy system monitoring against the Required Navigation Performance • The system estimated accuracy has a 95% confidence NAV ACCUR UPGRAD

13. RNP crew interface CLB FLT4567890 CRZ OPT REC MAX FL350 FL370 FL390 <REPORT UPDATE AT *[ ] BRG /DIST ---° /----.-TO[ ] PREDICTIVE <GPS REQUIRED ACCUR ESTIMATED 0.3NMHIGH0.28NM NAV ACCUR UPGRAD CLB FLT4567890 CRZ OPT REC MAX FL350 FL370 FL390 <REPORT UPDATE AT *[ ] BRG /DIST ---° /----.-TO[ ] PREDICTIVE <GPS REQUIRED ACCUR ESTIMATED 0.3NMLOW0.56NM NAV ACCUR DOWNGRAD NAV ACCUR UPGRAD NAV ACCUR DOWNGRAD

14. AIRBUS flight management details • Multi-sensor navigation & automatic navaid tuning • triple IRS, dual VOR & DME, GPS • nIRS only, nIRS/VOR/DME, nIRS/DME/DME, nIRS/GPS • LOC updating • RNP management • GPS primary navigation • RAIM or AIME on-board integrity monitoring • certified for RNP 0.3 NM use • Datalink • including F-PLN, T/O DATA and WIND uplink capability from AOC (Airline Operational Control)

15. AIRBUS flight management details • 4D flight planning & predictions • runway to runway 4D pre-computed optimized flight profile • real time optimization • decelerated approach profile, 3D non-precision approaches • full autopilot coupling capability (dual FMS, dual monitored AP) • time resolution 1 minute, guidance accuracy around 2 minutes • planned improvement to 1 second resolution, accuracy better than 30 s

16. Flight planning • Origin • Departure SID • Engine out SID • En-route • Arrival STAR • Approach • Destination • Missed approach • Alternate flight plan • Alternate destination

17. pressurization segment STEP FL CRUISE FL IDLE path SPEED LIMIT SPEED LIMIT geometric path ALTITUDE CONSTRAINTS ALTITUDE CONSTRAINTS approach path SPEED CONSTRAINTS SPEED CONSTRAINTS D APPROACH SPEEDS ACCELERATION ALT TIME CONSTRAINT THRUST REDUCTION ALT TAKE-OFF SPEEDS DESTINATION ORIGIN CRUISE DESCENT APPROACH TAKEOFF CLIMB Vertical flight management

18. Navigation database : ARINC 424 ARAB INSTRUMENT PROCEDURE DESIGN SEMINAR

19. ARINC 424 path terminator concept • The Path and Terminator concept is a means to permit coding of Terminal Area Procedures, SIDs, STARs and Approach Procedures • Charted procedure are translated into a sequence of ARINC 424 legs in the Navigation Database • Flight plans are entered into the FMS by using procedures from the navigation database and chaining them together

20. ARINC 424 path terminator concept • 23 leg types have been created to translate into computer language (FMS), procedure designed for clock & compass manual flight • It’s high time to implement RNAV, using only DO236 preferred leg types: IF, TF, RF which are fixed and without possible interpretation • The leg type is specified at the end point : “path terminator concept”

21. IF leg type • The Initial Fix or IF Leg defines a database fix as a point in space • It is only required to define the beginning of a route or procedure

22. TF leg type • Track to a Fix or TF Leg defines a great circle track over ground between two known databases fixes • Preferred method for specification of straight legs (course or heading can be mentioned on charts, but designer should ensure TF leg is used for coding)

23. RF leg type (new leg type) • Constant Radius Arc or RF Leg defines a constant radius turn between two database fixes, lines tangent to the arc and a center fix

24. CF leg type • Course to a Fix or CF Leg defines a specified course to a specific database fix • TF legs should be used instead of CF whenever possible to avoid magnetic variation issues

25. DF leg type • Direct to a Fix or DF Leg defines an unspecified track starting from an undefined position to a specified fix • Procedure designers should take into account the FMS flight path depends on initial aircraft heading as well

26. FA leg type • Fix to an Altitude or FA Leg defines a specified track over ground from a database fix to a specified altitude at an unspecified position

27. FC leg type • Track from a Fix from a Distance or FC Leg defines a specified track over ground from a database fix for a specific distance

28. FD leg type • Track from a Fix to a DME Distance or FD Leg defines a specified track over ground from a database fix to a specific DME Distance which is from a specific database DME Navaid

29. FM leg type • From a Fix to a Manual termination or FM Leg defines a specified track over ground from a database fix until Manual termination of the leg

30. CA leg type • Course to an Altitude or CA Leg defines a specified course to a specific altitude at an unspecified position

31. CD leg type • Course to a DME Distance or CD Leg defines a specified course to a specific DME Distance which is from a specific database DME Navaid

32. CI leg type • Course to an Intercept or CI Leg defines a specified course to intercept a subsequent leg

33. CR leg type • Course to a Radial termination or CR Leg defines a course to a specified Radial from a specific database VOR Navaid

34. AF leg type • Arc to a Fix or AF Leg defines a track over ground at specified constant distance from a database DME Navaid

35. VA leg type • Heading to an Altitude termination or VA Leg defines a specified heading to a specific Altitude termination at an unspecified position

36. VD leg type • Heading to a DME Distance termination or VD Leg defines a specified heading terminating at a specified DME Distance from a specific database DME Navaid

37. VI leg type • Heading to an Intercept or VI Leg defines a specified heading to intercept the subsequent leg at an unspecified position

38. VM leg type • Heading to a Manual termination or VM Leg defines a specified heading until a Manual termination

39. VR leg type • Heading to a Radial termination or VR Leg defines a specified heading to a specified radial from a specific database VOR Navaid

40. PI leg type • Procedure Turn or PI Leg defines a course reversal starting at a specific database fix, includes Outbound Leg followed by a left or right turn and 180 degree course reversal to intercept the next leg

41. HA, HF, HM leg types • Racetrack Course Reversal or HA, HF and HM Leg Types define racetrack pattern or course reversals at a specified database fix HA = Altitude Termination HF = Single circuit terminating at the fix (base turn) HM = Manual Termination

42. ARINC 424 - allowable leg transitions * = The IF leg is coded only when the altitude constraints at each end of the “FX”, “HX” or “PI” leg are different. & = A CF/DF, DF/DF or FC/DF sequence should only be used when the termination of the first leg must be over flown, otherwise alternative coding should be used. # = The IF/RF combination is only permitted at the start of the final approach for FMS, GPS or MLS coding and only when a straight line, fixed terminated transition proceeds the start of the final.

43. Navigation database related issues ARAB INSTRUMENT PROCEDURE DESIGN SEMINAR

44. Compatibility...

45. Navigation data production process AIP Procedure design by Civil Aviation Authorities operator responsibility Data Supplier ARINC 424 “master” file FMS Database Processing Packed Data FMS

46. Some top level issues • Navigation database process is *not* certified • Transcription of procedures in “computer” language (ARINC 424) requires interpretation • Procedure designer intent is currently only published under “pilot language” format • Each FMS implementation & logic is different • May results in different flight paths and SOP • Charts and aircraft navigation displays differ • Increased risk of Human error • Training costs

47. Reminder - flight plan construction • Charted procedure are translated into a sequence of ARINC 424 legs in the Navigation Database • Flight plans are entered into the FMS by calling procedures from the navigation database • Procedure segments are chained together (or melded) to form the FMS flight plan

48. Arrival chart Airways chart Approach chart STAR-approach transition (VIA) Enroute (airways) STAR-enroute transition STAR Approach Example : F-PLN procedure melding • Procedures are chained together to form the FMS flight plan. Example :

49. Example : procedure compatibility ? • Possible procedure misconnects between en-route, arrival, and approach charts • Possible discontinuities between or inside procedures • Incompatible or conflicting altitude requirements between arrival and approach charts

50. Navigation database recommendations ARAB INSTRUMENT PROCEDURE DESIGN SEMINAR