FANS (Future Air Navigation System) Flight Crew Procedures

FANS (Future Air Navigation System) Flight Crew Procedures
Brad Cornell Flight Deck / Flight Crew Operations 7 February 2012

What is FANS? Future Air Navigation System
GPS - Navigation Inmarsat Comm Space Air Ground Pieces of the system 3/28/2017

ATC versus AOC ATC AOC 20 55 FANS Protocol Defined Messages
CLIMB TO AND MAINTAIN [altitude] CROSS [position] AT [speed] 95% within 60s AOC Free text Multiblock Messages 1,000 characters 777, 787, A380 generates many multiblock messages No time requirements 20 55 3/28/2017

FANS Flight Crew Procedures
Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages FANS Flight Crew Procedures Section 5 of the Global Data Link Document (GOLD) Overview Logon Uplinks Downlinks Automatic Dependant Surveillance Position Reporting 3/28/2017

Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages FANS Flight Crew Procedures Overview Data Link requires different flight procedures between the pilot flying and pilot not flying than are used for voice (very important) Internal training program for FANS and integration with LOFT Requires operational approval from state authorities Operational approval enables regulators to ensure operators have an adequate training program and that the training program follows GOLD procedures. When to use CPDLC and when to use voice communicaitons 3/28/2017

Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages FANS Flight Crew Procedures Logon Unlike ACARS to establish a CPDLC connection the flight crew must “Logon” to an ATC facility to establish a CPDLC connection Procedures cover logging on when on the ground, after departure, and when entering a FANS capable FIR Procedures also cover automatic “handoffs” between FIRs and handoff failures 3/28/2017

Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages FANS Flight Crew Procedures Uplinks Once a CPDLC connection has been established CPDLC messages can be exchanged between the aircraft and ATC Each ATC data link (CPDLC) uplink message is annunciated to the flight crew using an aural and visual indication Unlike voice communication CPDLC requires BOTH flight crew to read the uplink silently to maintain situational awareness If reports are requested by ATC they should be responded to using CPDLC preformatted report messages not FREE TEXT Crew training material should highlight and develop special procedures for use of Conditional Clearances Note: The Boeing 787 has a built in conditional clearance monitor function and the Boeing 777 has a crew reminder function that can be used to remind crew of conditional clearances 3/28/2017

Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages FANS Flight Crew Procedures Uplinks - continued Free Text has been and continues to be a problem with flight crews. Each operator’s training program should highlight and remind flight crew’s on the use of free text. Preformatted messages should be used AT ALL TIMES in stead of typing out the same message using Free Text 3/28/2017

Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages FANS Flight Crew Procedures Downlinks Once a CPDLC connection is established the flight crew can create and send a “downlink” ATC message by using the pre-formatted message pages. Preformatted messages should be used AT ALL TIMES in stead of typing out the same message using Free Text To avoid potential ambiguity, the flight crew should avoid sending multiple clearance requests in a single downlink message 3/28/2017

Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages FANS Flight Crew Procedures Uplinks Once a CPDLC connection has been established CPDLC messages can be exchanged between the aircraft and ATC Each ATC data link (CPDLC) uplink message is annunciated to the flight crew using an aural and visual indication Unlike voice communication CPDLC requires BOTH flight crew to read the uplink silently to maintain situational awareness Crew training material should highlight and develop special procedures for use of Conditional Clearances Note: The Boeing 787 has a built in conditional clearance monitor function and the Boeing 777 has a crew reminder function that can be used to remind crew of conditional clearances 3/28/2017

Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages Chapter 5. Flight crew procedures 5.1 Overview 5.1.1 Operational differences between voice communications and CPDLC 5.1.2 Operational authorization to use CPDLC and ADS-C 5.1.3 When to use voice and when to use CPDLC 5.1.4 Loss of SATCOM data communications 5.2 Logon 5.2.1 General 5.2.2 When to initiate an AFN logon 5.2.3 Automatic transfer of CPDLC and ADS-C services between FIRs 5.2.4 Transfer voice communications with the CPDLC connection transfer 5.2.5 Exiting CPDLC and ADS-C service areas 5.3 CPDLC – ATS uplinks 5.3.1 General 5.3.2 Flight crew response times for uplinked messages 5.3.3 Conditional clearances 5.3.4 “EXPECT” uplinks 5.3.5 Uplinks containing FMS-loadable data 5.4 CPDLC – ATS downlinks 5.4.1 General 5.4.2 Free text 5.4.3 Unsupported messages 5.4.4 CPDLC reports 5.5 Automatic dependant surveillance – contract (ADS-C) 5.5.1 General 5.6 Position reporting 5.6.1 General 5.6.2 Position reporting in a non-ADS-C environment 5.6.3 Position reporting in an ADS-C environment (vi) Global Operational Data Link Document (GOLD) First Edition — 14 June 2010 5.6.4 Position reporting using FMC WPR 5.7 Weather deviations and offsets 5.7.1 General 5.7.2 Weather deviation requests and offsets 5.7.3 Deviations either side of route 5.7.4 Reporting back on route 5.8 Emergency and non-routine procedures 5.8.1 Emergency procedures - general 5.8.2 CPDLC and ADS-C emergency 5.8.3 Voice communications 5.8.4 Data link system failures 5.8.5 Using CPDLC to relay messages FANS Flight Crew Procedures Logon Unlike ACARS to establish a CPDLC connection the flight crew must “Logon” to an ATC facility to establish a CPDLC connection Procedures cover logging on when on the ground, after departure, and when entering a FANS capable FIR Procedures also cover automatic “handoffs” between FIRs and handoff failures 3/28/2017

747-400 FANS Interface 737NG, 757, and 767 are Similar FMC
Forward CDU Functions FMC Company datalink (ACARS) ATC datalink SATCOM CMC AOC AFT CDU Functions Point out Navigation display and alert section. ACMS Company datalink (ACARS) CMC SATCOM

747-400 Implementation ATC Data Link
Uplink Annunciation Loadable Clearances Armed Reports Position Reporting ATC Message Log Let’s talk specifically about the implementation of data link in the Uplinks annunciated on forward EICAS display and have a chime. Many of the clearances can be directly loaded into Flight Management system thereby reducing entry errors. ATC requested reports (REPORT PASSING) can be armed by the flight crew and the system will automatically send them down when required. There is a log available to the flight crew so they can see what things have been sent up and see a history of their responses.

ATC Data Link Airplane Requests Clearance Review Send to ATC
This is a clearance page. Can ask for altitude, new speed, an offset (to avoid weather), or a whole new route. They can enter what they want, review it, and send it to the controller.

AOC Data Link Accessible via MCDU key Route Uplinks Wind Uplinks
Position Reports Route Data Reports AOC data link is the communication between the airplane and the airline flight planning system. Receive route uplinks and new wind models. Route uplinks will generally be sent to the ATC controller as a route clearance request. They can also send position reports directly back to the airline.

777 FANS Interface Centralized alerting
Accept / Reject / Cancel Switches Automatic ATC uplink display Large format displays Common interface for both Company and ATC Common user interface with other function - ECL Read chart Crew Reminder Function can be used for conditional clearances

787 FANS Interface Centralized alerting
Accept / Reject / Cancel Switches Automatic ATC uplink display Large format displays Common interface for both Company and ATC (FANS and ATN) Common user interface with other function - ECL Read chart Conditional Clearance monitor

777 FANS 1 Implementation MFD display Cursor Control Selection
Functionally similar to

777 FANS 1 Implementation Full Display of uplink Color coded display
Action selection via CCD

777 FANS 1 Implementation Route Request via MFD Form
Most pilot selections via form

Questions? 3/28/2017

FANS (Future Air Navigation System) Flight Crew Procedures

Similar presentations

Presentation on theme: "FANS (Future Air Navigation System) Flight Crew Procedures"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

FANS (Future Air Navigation System) Flight Crew Procedures

Similar presentations

Presentation on theme: "FANS (Future Air Navigation System) Flight Crew Procedures"— Presentation transcript:

Similar presentations

About project

Feedback