28 JUN 12

AERONAUTICAL INFORMATION CIRCULAR 25/12

IMPLEMENTATION PLANNING OF CONTROLLER PILOT DATA LINK COMMUNICATIONS SERVICES IN CANADIAN DOMESTIC AIRSPACE

Introduction

On 16 December 2011, NAV CANADA commenced use of controller pilot data link communications (CPDLC) within the Canadian Domestic Airspace (CDA), with services offered in the Montreal flight information region (FIR). This was followed on 30 January 2012 by implementation in the northern portion of the Edmonton FIR. It is the intent of NAV CANADA to incrementally expand CPDLC service into the Moncton, Gander, Winnipeg, Vancouver and Toronto FIRs during the remainder of 2012 and early 2013.

As with the services offered in Montreal and Edmonton FIRs, implementation of CPDLC in the remaining regions will be via a phased approach, as detailed below.

Purpose of Circular

This circular advises operators of the service area coordinates and expected implementation timelines for each of the remaining FIRs within CDA. Specific start dates for each FIR and implementation phase will be announced via Notice to Airmen (NOTAM). A description of the implementation phases, flight crew procedures, and supported CPDLC messages are also detailed below.

Note: Cette information est aussi disponible dans l’autre langue officielle. Page 1 of 9 28 JUN 12

Page 2 of 9 AERONAUTICAL INFORMATION CIRCULAR 25/12 28 JUN 12

Moncton Area Control Center

On or after 28 June 2012, the Moncton area control centre (ACC) will begin application of CPDLC in the Moncton FIR/control area (CTA).

The Moncton CPDLC service area is flight level (FL) 290 and above, in the portion of the Moncton FIR/CTA bounded by:

41° 52’ 00” N 67° 00’ 00” W to 44° 30’ 00” N 67° 00’ 00” W 44° 30’ 00” N 67° 00’ 00” W to 44° 56’ 00” N 67° 00’ 00” W 44° 56’ 00” N 67° 00’ 00” W to 45° 37’ 30” N 67° 46’ 30” W 45° 37’ 30” N 67° 46 30 W to 45° 47’ 00” N 67° 48’ 17” W 45° 47’ 00” N 67° 48’ 17” W to 45° 49’ 30” N 67° 35’ 00” W 45° 49’ 30” N 67° 35’ 00” W to 46° 08’ 35” N 67° 13’ 00” W 46° 08’ 35” N 67° 13’ 00” W to 46° 12’ 00” N 67° 13’ 00” W 46° 12’ 00” N 67° 13’ 00” W to 46° 32’ 08” N 67° 17’ 59” W ARC Start to 35 Mile ARC Centered on 46° 32’ 08” N 67° 17’ 59” W 46° 57’ 00” N 67° 53’ 12” W Arc End to 47° 23’ 35” N 69° 00’ 00” W 47° 17’ 20” N 68° 34’ 24” W 47° 23’ 35” N 69° 00’ 00” W to 48° 00’ 00” N 69° 00’ 00” W 48° 00’ 00” N 69° 00’ 00” W to 48° 09’ 40” N 69° 19’ 45” W 48° 09’ 40” N 69° 19’ 45” W to 48° 53’ 20” N 69° 30’ 00” W 48° 53’ 20” N 69° 30’ 00” W to 49° 11’ 15” N 68° 40’ 00” W 49° 11’ 15” N 68° 40’ 00” W to 51° 00’ 00” N 68° 40’ 00” W 51° 00’ 00” N 68° 40’ 00” W to 51° 30’ 00” N 67° 00’ 00” W 51° 30’ 00” N 67° 00’ 00” W to 51° 53’ 00” N 65° 43’ 04” W 51° 53’ 00” N 65° 43’ 04” W to 51° 58’ 32” N 65° 22’ 15” W 51° 58’ 32” N 65° 22’ 15” W to 52° 07’ 27” N 64° 47’ 59” W 52° 07’ 27” N 64° 47’ 59” W to 52° 32’ 21” N 63° 07’ 24” W 52° 32’ 21” N 63° 07’ 24” W to 52° 49’ 10” N 61° 54’ 48” W 52° 49’ 10” N 61° 54’ 48” W to 51° 30’ 00” N 59° 45’ 00” W 51° 30’ 00” N 59° 45’ 00” W to 48° 50’ 00” N 57° 45’ 00” W 48° 50’ 00” N 57° 45’ 00” W to 44° 26’ 48” N 56° 03’ 06” W 44° 26’ 48” N 56° 03’ 06” W to 43° 35’ 00” N 55° 45’ 00” W 43° 35’ 00” N 55° 45’ 00” W to 42° 30’ 00” N 60° 00’ 00” W 42° 30’ 00” N 60° 00’ 00” W to 42° 20’ 12” N 61° 36’ 36” W 42° 20’ 12” N 61° 36’ 36” W to 41° 37’ 00” N 67° 00’ 00” W 41° 37’ 00” N 67° 00’ 00” W to 41° 52’ 00” N 67° 00’ 00” W

AERONAUTICAL INFORMATION CIRCULAR 25/12 Page 3 of 9 28 JUN 12

Gander Area Control Center

On or after 28 June 2012 the Gander ACC will begin application of CPDLC in the domestic area of the Gander FIR/CTA.

The Gander domestic CPDLC service area is FL 290 and above, in the portion of the Gander FIR/CTA bounded by:

43° 35’ N 055° 45’ W 48° 50’ N 057° 45’ W to 51° 30’ N 059° 45’ W 52° 48’ 49” N 061° 54’ 16” W to 52° 32’ 21” N 063° 07’ 24” W 52° 07’ 27” N 064° 47’ 59” W to 51° 58’ 32” N 065° 22’ 15” W 51° 53’ N 065° 43’ W to 51° 30’ N 067° 00’ W 51° 00’ N 068° 40’ W to 53° 32’ N 068° 40’ W 57° 33’ N 064° 00’ W to 58° 50’ 40” N 063° 00’ W 65° 19’ N 063° 00’ W to 65° 23’ N 062° 38’ W 65° 30’ N 060° 00’ W to 65° 42’ 36” N 058° 23’ 56” W 65° 00’ N 057° 45’ W to 63° 30’ N 055° 40’ W 63° 30’ N 055° 00’ W to 53° 52’ N 055° 00’ W 53° 05’ N 054° 05’ W to 51° 00’ N 050° 00’ W 44° 30’ N 050° 00’ W to 43° 35’ N 055° 45’ W to point of beginning.

Winnipeg Area Control Center

On or after 28 June 2012, the Winnipeg ACC will begin application of CPDLC in the Winnipeg FIR/CTA.

The Winnipeg CPDLC service area is FL 290 and above, in the portion of the Winnipeg FIR/CTA bounded by:

49° 00’ N 110° 00’ W to 49° 50’ N 109° 00’ W 51° 11’ N 109° W to 51° 20’ N 109° 30’ W 51° 30’ N 110° W to 53° 25’ 15” N 110° 00’ W then via a 60NM arc counter-clockwise around 54° 46’ N 108° 41’ 40” W the Cold Lake TACAN (UOD) 54° 46’ N 108° 25’ W to 55° 20’ N 107° 25’ W 53° 00’ N 102° 00’ W to 52° 26’ N 101° 00’ W 52° 46’ N 99° 08’ W to 52° 20’ N 95° 00’ W 52° 08’ N 95° 53’ W to 51° 20’ N 89° 23’ W 49° 54’ N 84° 12’ W to 47° 05’ N 87° 00’ W 47° 54’ 30” N 88° 46’ 30” W Then via a 35NM arc clockwise around CYQT to 48° 06’ 30” N 90° 06’ W to 48° 34’ 15” N 91° 50’ W 48° 58’ 30” N 93° 24’ W to 49° 00’ N 97° 43’ W then along 49N latitude to the point of beginning

Page 4 of 9 AERONAUTICAL INFORMATION CIRCULAR 25/12 28 JUN 12

Vancouver Area Control Center

On or after 30 September 2012, the Vancouver ACC will begin application of CPDLC in the Vancouver FIR/CTA.

The Vancouver CPDLC service area is FL 290 and above in the portion of the Vancouver FIR/CTA bounded by:

49° 00’ 02” N 115° 29’ 59” W Then west along the Canada/US boundary to 48° 29’ 36” N 124° 43’ 38” W to 48° 30’ N 125° W to 48° 20’ N 128° W to 51° N 133° 45’ W to 54° N 136° W to 54° 13’ N 134° 57’ W to 54° 39’ 44” N 132° 41’ 03” W Then along the Canada/Anchorage (US) boundary to 57° N 132° 03’ 58” W to 56° N 123° 15’ W to 53° 24’ N 119° W to 50° 19’ 35” N 116° 05’ 05” W then west along the arc of a circle 49° 57’ 18” N 115° 47’ 32” W to 25NM radius centered on Skookum, BC NDB to 49° 57’ 45” N 115° 08’ 50” W to 49° 30’ N 115° 08’ 15” W to 49° 00’ 02” N 115° 29’ 59” W to point of beginning.

Toronto Area Control Center

On or after 15 March 2013, the Toronto ACC will begin application of CPDLC in the Toronto FIR/CTA.

The Toronto CPDLC service area is FL 290 and above in the portion of the Toronto FIR/CTA bounded by:

44° 13’ 17” N 76° 11’ 30” W Then west along Canada/Us boundary to 47° 46’ 29” N 87° W to 49° 32’ N 87° W to 50° N 86° 16’ W to 52° N 83° 08’ 30” W to 53° 28’ N 80° W to 49° N 79° W to 48° 35’ 13” N 79° W Then counter clockwise along the arc of a circle of 25NM radius centered on Rouyn, QC NDB to 47° 50’ 24” N 78° 33’ 56” W to 47° 33’ 15” N 78° 07’ 03” W to 47° 06’ 39” N 77° 32’ 45” W to 46° 56’ 48” N 77° 15’ W to 46° 08” N 77° 15’ W to 45° 57’ 40” N 76° 55’ 40” W to 45° 50’ 15” N 76° 16’ W to 44° 13’ 17” N 76° 11’ 30” W to the point of beginning

AERONAUTICAL INFORMATION CIRCULAR 25/12 Page 5 of 9 28 JUN 12

Phased Implementation

Phase 1 – Basic Request Phase This initial phase will enable an aircraft to make various speed and altitude requests using CPDLC.

The response from the ACC ground system will be a free text acknowledgement that the request had been received and that a response from air traffic control (ATC) will be provided by the appropriate ACC via voice.

Phase 2 – Advising Domestic Frequencies This phase introduces the assignment of domestic contact frequencies via CPDLC. Analysis of voice traffic indicates that such messages represent a significant proportion of existing voice traffic, and using CPDLC to carry out this function would be a useful contribution to reducing voice congestion.

Phase 3 – Support En-route Altitude Changes and Speed Changes This phase will enable aircraft to request En Route altitude changes, En Route speed changes and to report Leaving/Reaching Levels via CPDLC.

Responses to these requests from the ACC will also be via CPDLC.

Phase 4 – Full Implementation With the exception of those messages deemed unsafe by ICAO, specified downlink elements will be supported. Domestic ACCs will develop appropriate procedures to respond to all received downlink message elements.

ATC will not provide information regarding when or where a flight can expect to climb or descend, due to the potential misunderstanding that such a message constitutes a clearance.

Supported Downlink Messages (Phase 1 and Phase 2)

Only the following messages will be supported for phase 1 and phase 2. Any downlink message other than indicated below will generate ‘MESSAGE NOT SUPPORTED BY THIS FACILITY’ response from the ground system.

DM0 WILCO DM1 UNABLE DM2 STANDBY DM3 ROGER DM4 AFFIRM DM5 NEGATIVE DM6 REQUEST (Alt) DM9 REQUEST CLIMB TO (Alt) DM10 REQUEST DESCENT TO (Alt) DM18 REQUEST (Speed) DM20 REQUEST VOICE CONTACT DM21 REQUEST VOICE CONTACT (FREQ) DM55 PAN PAN PAN DM56 MAYDAY MAYDAY MAYDAY DM58 CANCEL EMERGENCY DM62 ERROR (ERROR INFORMATION) DM63 NOT CURRENT DATA AUTHORITY

Page 6 of 9 AERONAUTICAL INFORMATION CIRCULAR 25/12 28 JUN 12

DM64 (ICAO FACILITY DESIGNATION) DM65 DUE TO WEATHER DM66 DUE TO AIRCRAFT PERFORMANCE DM67 FREE TEXT DM75 AT PILOTS DISCRETION

Flight Planning

Air traffic services (ATS) systems use field 10 (Equipment) of the standard ICAO flight plan to identify an aircraft’s data link capabilities.

For non-ICAO 2012 format flight plans, operators should insert the following items into the ICAO flight plan form for FANS 1/A-equipped aircraft:

1. Field 10a (Radio communication, navigation, and approach equipment): insert the letter “J” to indicate data link equipment. 2. Field 18 (Other Information): when the letter “J” is inserted in field 10a, insert the characters “DAT/,” followed by one or more letters as appropriate to indicate the type of data link equipment carried (see table below).

Letter Following Type of Data Link DAT/ Equipment S Satellite data link H HF data link V VHF data link M SSR Mode S data link

For ICAO 2012 format flight plans, which are effective as of 15 November 2012, operators should insert the following items into the ICAO flight plan form for FANS 1/A-equipped aircraft:

1. Field 10a (Radio communication, navigation, and approach equipment): insert the indicator(s) “J1 – J7” to indicate appropriate data link equipment as per the table below.

Field 10a Indicator Type of Data Link Equipment J1 CPDLC FANS 1/A ATN VDL Mode2 J2 CPDLC FANS 1/A HFDL J3 CPDLC FANS 1/A VDL Mode A J4 CPDLC FANS 1/A VDL Mode 2 J5 CPDLC FANS 1/A SATCOM (INMARSAT) J6 CPDLC FANS 1/A SATCOM (MTSTAT) J7 CPDLC FANS 1/A SATCOM (IRIDIUM)

AERONAUTICAL INFORMATION CIRCULAR 25/12 Page 7 of 9 28 JUN 12

ATS Facilities Notification (AFN) Logon A CPDLC connection is initiated by the ground system in response to an AFN logon received from the aircraft. It is important, when initializing the flight management computer (FMC), to ensure that aircraft identification matches the identification displayed in the filed ATC flight plan message. If a flight becomes aware that incorrect flight identification data was provided in the AFN logon, the data link must immediately be terminated and a new AFN logon performed with the correct information. Flights entering any CDA CPDLC service areas from airspace where FANS 1/A ATS data link services are being received do not need to perform another AFN logon. Flights entering the CDA CPDLC service areas from airspace where no FANS 1/A ATS data link services are being received should perform an AFN logon:

a) 15 to 45 minutes prior to entering the airspace; or b) prior to departure if departing airports are adjacent to, or underlying, the airspace. The AFN logon address for flights entering CDA facilities are as follows:

Facility Name Facility Identifier for AFN Logon Montreal Area Control Center CZUL Edmonton Area Control Center CZEG Moncton Area Control Center CZQM Gander Area Control Center (Domestic) CDQX (Domestic identifier) Gander Area Control Center (Oceanic) CZQX Winnipeg Area Control Center CZWG Vancouver Area Control Center CZVR Toronto Area Control Center CZYZ

Flights exiting the CDA CPDLC service areas into adjacent airspace where data link services are offered should not need to perform another AFN logon. Under normal circumstances, the current and next ATS units automatically transfer CPDLC and Automated Dependent Surveillance–Contract (ADS-C) services. The transfer is seamless to the flight crew.

Communication of CPDLC Service Capability CPDLC will supplement existing very high frequency (VHF) voice as modes of direct controller-pilot communications (DCPC) within CDA.

Aircraft that have performed a logon should identify themselves when entering the CPDLC service area by using the term “C–P–D–L–C” after the aircraft call sign, on initial contact.

Flight crews can expect the reply from the ACC to include

1. acknowledgement that the flight is C–P–D–L–C; 2. the assigned frequency for the next station en route. The following is a sample exchange with Moncton Centre:

MONCTON CENTRE, AIRLINE FIVE FIVE ONE C–P–D–L–C, FLIGHT LEVEL 350

AIRLINE FIVE FIVE ONE C–P–D–L–C, MONCTON CENTRE, CONTACT MONCTON CENTRE AT HALIFAX ON 135.2

Page 8 of 9 AERONAUTICAL INFORMATION CIRCULAR 25/12 28 JUN 12

Contact

For further information on CPDLC service in the CDA FIR/CTAs and the expansion of this service, please contact:

Pedro A. Vicente Manager, CAATS Implementation NAV CANADA Technical Systems Centre 280 Hunt Club Road Ottawa, ON K1V 1C1

Tel.: 613-248-6965

Rudy Kellar Vice President, Operations

AERONAUTICAL INFORMATION CIRCULAR 25/12 Page 9 of 9