Early releases of the 3rd edition of ICAO's GOLD docement are started to appear in 2016 The official release of this document was in late 2017 as ICAO Docuemnt #10037, 1st edition. GOLD is a good compilation of CPDLC and ADS-C information from previous ICAO documents. This document is designed to help with uniform application of ICAO Standards and Recommended Practices contained in Annex 2, Annex 10, Annex 11, PANS-ATM, Doc#4444 and Regional Supplementary Procedures Doc #7030. This GOLD document represents a baseline for global harmonization of ADS-C and CPDLC implementation.
This document is not a single source for all things FANS. This document has a little bit of everything FANS. Pilots/Operators will need to read this document in conjunction with AFM supplements, Advisory Circulars, AIP information and FIR NOTAMS to obtain a Data Link operational approval. Pilots/Operators will need to determine what is important to their operation, and extract that information for use. Going forward, FANS operational approval will involve Performance Based Communication and Surveillance Systems. This document gives only a small highlight to the significance PBCS.
Below here are the two chapters that I think make the most sense for operating pilots to review. The entries in red are a high-viz item with the feds. A double asterisk ** Indicates information especially helpful to pilots/operators. Chapter 4 has signifigance for pilots/operators throught the chapter.
Chapter 1, Overview of Data Link Operations
**Paragraph 1.1.2, Good overview of all things “Data Link”
**Figure 1-2, Good picture of how different “Data Link” functions overlap and interact.
Table 1-1, Specifically helps define just what “Data Link” we are talking about.
Table 1-2, Specifically describes the means over which the data is transmitted
Paragraph 22.214.171.124.1, Explains why Data Link is important to ATC
**Paragraph 126.96.36.199.1, ACARS description and why this is not CPDLC
**Paragraph 188.8.131.52, ATN description and why this is not CPDLC
**Paragraph 184.108.40.206.2, Behind the scene description of what is happening at “LOGON”
**Paragraph 220.127.116.11, Outline of when and what to do in the cockpit for “LOGON”
Paragraph 18.104.22.168, What to watch for in the cockpit for CDA transfer to NDA
Paragraph 22.214.171.124.2, Normally, in operation the pilot initiates LOGON not ATS
**Paragraph 126.96.36.199.3, Important difference between “Contact” vice “Monitor”
**Paragraph 188.8.131.52, Automatic transfer of CDA to NDA, vice LOGOFF
Figure 1-17,1-18,1-19 Somewhat confusing timelines CPDLC events
**Table 1-4, Simply stated; Accept, Reject or STBY are the only cockpit responses
Paragraph 184.108.40.206, Why multi-element CPDLC messages are problematic
Table 1-5 and 1-6, Why multi-element CPDLC messages are problematic
**Paragraph 220.127.116.11, ADS-C overview
**Paragraph 18.104.22.168, Good description of when ADS-C reports
**Paragraph 22.214.171.124, Good description of what ADS-C reports
**Figure 1-39 thru 1-47 Good graphics of when and what ADS-C reports
Paragraph 126.96.36.199, What ATC uses ADS-C reports for
**Paragraph 188.8.131.52.2 Why using LNAV vice HDG SEL is important
Table 1-8, Explains what Figure of Merit means to you RNP capability
Chapter 3, Controller and Radio Operator Procedures
**Paragraph 3.1.2, Good description of when to use CPDLC and when not to use it
**Paragraph 3.3.2, Good description of when to use Free Text and when not to use it
**Paragraph 3.3.4, Statistically speaking, Conditional Clearances with a Vertical Element are the most misunderstood and poorly complied with.
**Paragraph 3.3.7, Weather Deviations in a FANS environment is a hot topic with regulators.
Paragraph 3.4.3, Good explanation of why not to keep sending multiple CPDLC requests for the same issue/element.
Paragraph 3.5.1, Explains why putting “Abeam Points” in an active legs page is not a good idea.
Paragraph 3.6.2, What ATC is looking for in a Vertical ADS-C contract
Paragraph 3.6.3, What ATC is looking for in a Lateral ADS-C contract
Paragraph 3.6.3, How ATC uses ADS-C contracts in Nose-to-Tail separation
**Paragraph 3.9 and 3.10, How ATC expects to respond in a FANS abnormal condition
Chapter 4, Flight Crew Procedures
Paragraph 4.1.1, An LOA/OpsSpec is required by the FAA for Data Link operations
Paragraph 4.1.2, Human Factors associated with CPDLC operational use
Paragraph 184.108.40.206, Emergency or Abnormal situation, revert to voice communications
Paragraph 220.127.116.11, Voice, Free Text or CPDLC message, pilot should respond is the same manner as queried by ATC.
Paragraph 4.2, Outline of what to do in the cockpit for “LOGON”. Match this to Chapter 1, Paragraph 18.104.22.168.
Paragraph 22.214.171.124, Outline of what to do with the Message Latency Timer in a FANS 1/A cockpit.
Paragraph 4.2.2 Outline of when to “LOGON”. Match this to Chapter 1, Paragraph 126.96.36.199
Paragraph 188.8.131.52, Local procedures for this are usually contained in FIR NOTAMs or AIC’s from the country involved
Paragraph 4.2.4, Read this paragraph with Chapter 1, Paragraph 184.108.40.206.3,
Paragraph 220.127.116.11, STBY is just as legit a response to ATC and is not listed here.
Paragraph 18.104.22.168, Why a quick response with STBY is important
Paragraph 22.214.171.124, Why a response with STBY is important
Paragraph 126.96.36.199, Why STBY is not a final answer and closes the ATC message
Paragraph 4.3.3, What to expect and how to comply with a Conditional Clearance. Match this to Table 4.3.4 and Chapter 3, Paragraph 3.3.4.
Paragraph 4.3.5, Explains how accepting a CPDLC Conditional Clearance, arms the ADS-C reporting required in the message
Paragraph 4.4, Explains how to send clear and unambiguous messages to ATC via CPDLC.
Paragraph 4.4.2, Explains when not to use Free Text
Paragraph 4.4.3, Explains what to respond to CPDLC with Voice, UM or Free Text. Match this to Chapter 3, Paragraph 3.3.2.
Paragraph 4.4.5, Good description and important information on what ATC expects in a Weather Deviation event. Read this with Document#4444, PANS-ATM Chapter 15, Paragraph 15.2.3
Paragraph 188.8.131.52.1, CPDLC and some ATC units will not accept the AIRINC-424 format. Use of full LAT/LONG is a best practice.
Paragraph 184.108.40.206.1, CPDLC position reporting at FIR boundary crossing is usually contained in FIR NOTAMs or AIC’s from the country involved
Paragraph 220.127.116.11, Read this with Chapter 1, Paragraph 18.104.22.168.2 and Chapter 3, Paragraph 3.3.7 and 3.5.1.
Paragraph 4.6, How to use CPDLC and ADS-C to report aircraft emergency to ATC
Paragraph 4.6, CPDLC and ADS-C abnormals response, LOGOFF, LOGON, if no success, revert to voice communications