EUROPEAN ORGANISATION FOR THE SAFETY OF AIR NAVIGATION

AIR / GROUND DATA LINK PROCEDURES

FOR FLIGHTS WITHIN THE AREA OF RESPONSIBILITY OF MAASTRICHT-UAC

Data link Procedures for Flights Maastricht-UAC

Edition Edition Date : : 2.5 31. July 2008

European Organisation for the Safety of Air Navigation (Eurocontrol) 2000.

All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written permission of EUROCONTROL.

MAASTRICHT-UAC U.A.C. OPERATIONS DIVISION SYSTEMS IMPLEMENTATION SECTION

DOCUMENT IDENTIFICATION SHEET

DOCUMENT DESCRIPTION Document Title Air / Ground Data link Procedures for Flights within the Area of Responsibility of Maastricht-UAC

EDITION: EDITION DATE:

2.5 31 July 2008

Abstract This Document provides the operating procedures, and additional background information and requirements, for flights conducting CPDLC with Maastricht-UAC during CPDLC operations.

Keywords Procedures, Manual, Data link; Uplinks, Downlinks, Voice Read back Requirement.

AUTHOR :

Volker Stuhlsatz

TEL: ++ 31 43 366 1510

DIVISION: SECTION:

OPERATIONS OASYS

DOCUMENT STATUS AND TYPE STATUS Working Draft Draft Proposed Issue Released Issue CATEGORY Executive Task Specialist Task Lower Layer Task CLASSIFICATION General Public Restricted Internal Use

ELECTRONIC BACK-UP INTERNAL REFERENCE NAME : Procedures for Flights.DOC HOST SYSTEM MEDIA SOFTWARE(S) Microsoft Windows Type: Hard disk Name: MS Word Media Identification: Text processor Version: 97

DOCUMENT APPROVAL
AUTHORITY NAME AND SIGNATURE DATE

Author of the Document

Volker STUHLSATZ

28 January 2008

MANAGEMENT APPROVAL
AUTHORITY Resource and Planning Manager Head of Section Peter HENDRICKX 28 January 2008 Christopher ADAMS 28 January 2008 NAME AND SIGNATURE DATE

DOCUMENT CHANGE RECORD

The following table records the complete history of the successive editions of the present document.

EDITION 0.1 0.2 1.0 2.0 2.1 2.2

DATE 13.08.03 18.08.03 22.10.03 22.12.04 14.08.05 20.02.07

REASON FOR CHANGE Initial Draft for Procedures for Step 1 / Stage 2 Formatting changes and insertion of phraseology Incorporating comments and amendments Final version for Stage 2 Addition of comment on log-on time/CPDLC connection Revision of text concerning LACK timer and dialogue closure. Plus other minor text revisions Revision of text concerning new constraint menu including now also SPEED instructions Revision Voice Read back / WILCO prior to the execution of the profile changing DL instruction. Revision

SECTIONS OR PAGES AFFECTED all Section 5 all all Pgs 11, 26 all

2.3

28 01.2008

all

2.4

28 03.2008

Section 5.1

2.5

30 07.2008

all

REFERENCE DOCUMENTS
TITLE
DATE EDITION

Table of contents

1. 2.

Acronyms....................................................................................................................... 7 Introduction .................................................................................................................. 9

2.1 2.2
3.

Manual introduction.............................................................................................9 Context.................................................................................................................9

Physical environment ................................................................................................. 10

3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9

4.

Date of operations ..............................................................................................10 Airspace .............................................................................................................10 Use of CPDLC ...................................................................................................10 Multi-stack .........................................................................................................10 Pre-flight identification......................................................................................10 Log-on address...................................................................................................10 Log-on time........................................................................................................11 Error: ACFT already LOGGED-ON .................................................................11 Callsign ..............................................................................................................11
Datalink Services ........................................................................................................ 12

4.1 4.2 4.3 4.4 4.5

5.

Datalink Services Provided................................................................................12 DLIC Datalink Initiation Capability ...............................................................12 ACM ATC Communications Management ....................................................12 ACL ATC Clearances And Instructions .........................................................12 AMC ATC Microphone Check.......................................................................13
CPDLC PROCEDURES............................................................................................ 14

5.1 Execution of clearances .....................................................................................14 5.2 Operating Context / Strategic Use .....................................................................14 5.3 Supplemental communications ..........................................................................14 5.4 Precedence .........................................................................................................15 5.5 Uncertainty revert to voice..............................................................................15 5.6 Replies................................................................................................................15 5.7 Validity of requests ............................................................................................15 5.8 Appropriate use..................................................................................................15 5.9 Emergencies.......................................................................................................15 5.10 Uplinked Clearances, Instructions and Responses .........................................16 5.10.1 Uplinks ........................................................................................................16 5.11 Downlinked Requests and Responses ............................................................20 5.11.1 Downlinks ...................................................................................................20
6. End-to-End System..................................................................................................... 24

6.1 6.2 6.3 6.4 6.4.1 6.4.2

7.

End-to-End.........................................................................................................24 Ground system at Maastricht-UAC ...................................................................24 Communications Network .................................................................................24 Aircraft systems .................................................................................................25 Diagram ..........................................................................................................25 More................................................................................................................25
Log-on, connection and disconnection...................................................................... 26

7.1

flight plan information .......................................................................................26

7.2 7.2.1 7.2.2 7.2.3 7.3 7.3.1 7.3.2 7.3.3 7.3.4 7.4 7.5 7.6
8.

Log-on................................................................................................................26 Log-on address ...............................................................................................26 Log-on time ....................................................................................................26 Callsign...........................................................................................................26 CPDLC enable ...................................................................................................27 CPDLC Initiation............................................................................................27 CPDLC Initiation Time ..................................................................................27 Current Data Authority...................................................................................28 CPDLC only under control of Maastricht-UAC .........................................28 Inter- sector transfer...........................................................................................29 Next Data Authority...........................................................................................29 Inter-Centre transfer...........................................................................................30
Timeouts ...................................................................................................................... 31

8.1 8.2 8.3 8.3.1 8.3.2 8.4 8.4.1 8.4.2 8.5

9.

Logical Acknowledgement LACK .................................................................31 LACK Time .......................................................................................................31 LACK Time-out.................................................................................................31 System Behaviour...........................................................................................31 Controller Behaviour ......................................................................................31 Operational time-out ..........................................................................................31 System Behaviour...........................................................................................32 Controller Behaviour ......................................................................................32 Operational Time-Out - STANDBY Response From Crew ............................32
Airborne Error Messages .......................................................................................... 32

9.1
10.

Error Messages...................................................................................................32
Reporting..................................................................................................................... 33

ANNEX A............................................................................................................................... 34

Table of figures
Figure 1 - Maastricht-UAC Ground System [simplified]........................................................... 25 Figure 2 - Log-on Request and Response .............................................................................. 27 Figure 3 - CPDLC Connection and CDA ................................................................................. 28 Figure 4 - Next Data Authority ................................................................................................. 29 Figure 5 - CONTACT and End Service ................................................................................... 30

1.

ACRONYMS
Aircraft Communications Addressing and Reporting System ATC Clearances and Instructions ATC Communications Management Air Ground Data Link ATN Lower Layer Access ATC Microphone Check Air Traffic Control Aeronautical Telecommunications Network Air Traffic Services Air Traffic Services Unit Current Data Authority Controller Pilot Communications Controller Pilot Data Link Communications Data link Initiation Capability Downlink message FANS Front End Processor Future Air Navigation System Flight Data Processing System Flight Information Region Flight Level High Frequency [3-30 MHz] Identification [Flight] Logical Acknowledgement Megahertz Next Data Authority Next Secondary Surveillance Radar [Code] Mode-A PETAL2 Gate Way Preliminary EUROCONTROL Trials of Air/ground Data link Message Received [In specific CPDLC circumstances taken as WILCO] Radio Telephony Satellite Communication System Improvement and Problem Reporting [Form] Systems Implementation Section Special Position Indicator Secondary Surveillance Radar [Code] Upper Area Control Upper [Flight] Information Region Uplink Message Voice Change Instruction Very High Frequency [30-300 MHz] Message Understood and Will Comply

ACARS ACL ACM AGDL ALLA AMC ATC ATN ATS ATSU CDA CPC CPDLC DLIC DM FAFEP FANS FDPS FIR FL HF Id LACK MHz NDA NSSR P2GW PETAL ROGER R/T SATCOM SIPR SIS SPI SSR UAC UIR UM VCI VHF WILCO

Air / Ground Datalink Procedures for Flights

Intentionally Blank

Air / Ground Datalink Procedures for Flights

2.
2.1

INTRODUCTION
MANUAL INTRODUCTION

This manual of Air / Ground Data Link Procedures for Flights within the Area of Responsibility of Maastricht-UAC covers the procedures and requirements for aircraft using data link in airspace under the responsibility of MaastrichtUAC. This airspace includes:

Amsterdam FIR above FL245 Brussels UIR above FL245 Hannover UIR above FL245

The manual also intends to provide, amongst other things, a brief, simplified description of the data link process, as employed in Maastricht-UAC. It is not intended as a full technical description. 2.2 CONTEXT Data link communications began to be used by Maastricht-UAC, under the Preliminary Eurocontrol Trials Air Ground Data Link trials. The initial PETAL trials started to be conducted in 1995. Though limited in scope, these first trials opened the doorway to the use of CPDLC in an operational environment, covering high-density traffic. Following the completion of PETAL, a second trial was put in place PETAL lI, which sought to push the boundaries of CPDLC use even further. It involved the use of CPDLC with multiple flights, operating across the sectors under Maastricht-UAC control. This second trial phase also involved the development of a multi-stack system in Maastricht-UAC, enabling controllers to communicate, via data link, with aircraft operating data link under different systems, NEAN, FANS or ATN. During the lifetime of PETAL, more than 10.000 successful CPDLC flights were recorded - flights where at least one successful CPDLC exchange took place. Particulars of the messages and services that will be used are contained in this manual. Pilot procedures, and expected behaviour, are detailed in this manual. Further details, if required, are available from Maastricht-UAC.
Intentionally Blank 9

Air / Ground Datalink Procedures for Flights

3.
3.1

PHYSICAL ENVIRONMENT
DATE OF OPERATIONS

Maastricht-UAC implemented operational Controller/Pilot Data Link Communications CPDLC - with effect from 18th June 2003 and is available on a 24/7 basis.

3.2

AIRSPACE

Maastricht-UAC EDYY provides data link services in the following airspaces:

EHAA - Amsterdam FIR EBBU - Brussels UIR EDVV - Hannover UIR

FL245 and above FL245 and above FL245 and above

3.3

USE OF CPDLC

The use of CPDLC in Maastricht-UAC airspace is not mandatory and conducted at the discretion of the controllers and aircrews involved. Aircrew are encouraged to use CPDLC to the maximum extend possible, as alternative communication means, also to ease the R/T frequency load.

3.4

MULTI-STACK

Maastricht-UAC operates a multi-stack system. This means that MaastrichtUAC accept CPDLC exchanges with aircraft equipped with ATN or FANS.

3.5

PRE-FLIGHT IDENTIFICATION

Maastricht-UAC requests that flights intending to conduct CPDLC exchanges with Maastricht-UAC enter tail number or 24-bit address code [as appropriate] in field 18 of their flight plans.

3.6

LOG-ON ADDRESS

The log-on [ICAO facility] address for CPDLC communications with Maastricht-UAC is EDYY. Log-on to Maastricht covers the area of responsibility of Maastricht-UAC.
Air / Ground Datalink Procedures for Flights

10

3.7

LOG-ON TIME

Entering Maastricht UAC airspace LOG-ON can be established 15 to 45 minutes prior to entry. For departing aerodromes close or below to Maastricht-UAC airspace, LOG-ON may also be conducted already on the ground. Pilots should be aware that CPDLC connection will not normally be attempted until the aircraft is within 10 minutes of the Maastricht boundary or above FL150 in case of departure flights to minimise cockpit distraction. Note: The time parameter of 15 45 minutes prior to entry is to ensure interoperability with log-on in other CPDLC regions worldwide.

3.8

ERROR: ACFT ALREADY LOGGED-ON This Error message is generated when an aircraft has established DLIC (LOGON request down linked & LOGON response up linked) and then (whilst waiting for the CPC Start Request still to be uplink) the pilot tries to LOG ON again before CPDLC is established by the onboard CMU., due to a) message latency, FANS network may be subject to message delays and b) Maastricht-UAC Flight Server at will not uplink the CPC start request until an aircraft with DLIC is close to the Maastricht or above FL150.

3.9

CALLSIGN

Aircraft should log-on using their current ICAO call sign the call sign found on their flight plan (Mode-S Flight-ID) [e.g. BER23, not AB0023]. Crews should ensure that they do not use a two-letter IATA flight identification to log-on, as this will result in a failed log-on. Crew insertion of a leading zero [0] into a call sign will also result in a failed log-on. Note: The use of the correct call sign on LOG-ON is of paramount importance to the safety of air navigation, as a LOG-ON with a wrong call sign could lead to a misdirection of CPDLC messages.

Air / Ground Datalink Procedures for Flights

11

4.
4.1

DATALINK SERVICES
DATALINK SERVICES PROVIDED

Maastricht-UAC provides the following data link services

DLIC ACM ACL AMC

4.2

DLIC DATALINK INITIATION CAPABILITY

DLIC, sometimes referred to as logging on, provides the mechanism for exchanging and forwarding information between aircraft and ground systems, in support of CPDLC, ADS, and CM communications. It also provides the necessary information to establish flight plan / address association in the ATC system, allowing the systems to ensure correct delivery of data link messages. It is a prerequisite to the operational data link services. 4.3 ACM ATC COMMUNICATIONS MANAGEMENT

From an operational point of view, the ACM service provides automated assistance to aircrew and controllers in transferring ATC communications from one sector/centre to another. It encompasses the transfer of all controller/aircrew communications, both R/T and data link. Aircrew can expect to receive data link instructions to contact their next voice frequency.

4.4

ACL ATC CLEARANCES AND INSTRUCTIONS

The ACL service enables the controller to issue en route clearances and instructions, and to reply to aircrew requests. The ACL service also enables the aircrew to make operational requests and to respond to clearances and instructions.

Air / Ground Datalink Procedures for Flights

12

Aircrew requests in CPDLC operations with Maastricht-UAC are limited to the downlink of:
REQUEST DIRECT TO [position], REQUEST [level] REQUEST CLIMB TO [level] REQUEST DESCENT TO [level].

Other downlinks will be responded to by an ERROR message from ground. Important Note: Maastricht-UAC operates an environment in which profile changing CPDLC ATC clearances and instruction require in addition to a data link operational response - voice read back by the aircrew, whilst others do not require the voice read back element. These requirements for aircrew responses are detailed in Section 5.10.1 and following subsections. Note: Particular vigilance shall be exercised by AIRBUS aircrews in order not to misinterpret old CPDLC message in the LOG with actual CPDLC clearances!

4.5

AMC ATC MICROPHONE CHECK

The AMC service provides controllers with the capability to uplink an instruction to aircraft to check that they are not inadvertently blocking a given voice frequency.

Air / Ground Datalink Procedures for Flights

13

5.
5.1

CPDLC PROCEDURES
EXECUTION OF CLEARANCES

Maastricht-UAC operates an environment in which profile changing ATC clearances [direction, level] require additionally to a data link operational response - voice read back by the aircrew. If a profile changing uplink is received the crew shall execute the clearance in the following manner: Firstly give VOICE READ BACK to ATC and send a WILCO response Then comply with /execute the clearance

The above steps must be complied with in this order, in order to guarantee the correctness of the uplink clearance received prior to its execution. If a clearance or instruction is determined NOT to require voice read back then the crew shall execute the clearance in the following manner Send WILCO response and comply/execute the clearance/instruction.

In either case, voice contact with ATC is required should any situation arise that prevents execution of a clearance following a WILCO response. These requirements for aircrew responses to the different ACL messages are detailed in Section 5.10.1 and following subsections.

5.2

OPERATING CONTEXT / STRATEGIC USE

Data link CPDLC exchanges will be used in the context of routine, strategic situations only the data link timeframe does not allow for their tactical use. Strategic in this sense refers to the ATC situation prevailing at the time. Strategic situations, in this context, are situations that allow for routine, nontime critical communications to take place between controllers and pilots. Tactical in this sense refers to the ATC situation prevailing at the time. Tactical situations, in this context, are ones where speed of delivery, and receipt of an aircrew response to an instruction, are of a time-critical nature in order to ensure the immediate safety of an aircraft.

5.3

SUPPLEMENTAL COMMUNICATIONS

Data link will be used as a supplemental means of communication to voice. It is not the intention to replace voice as the primary means of communication in Maastricht-UAC airspace.

Air / Ground Datalink Procedures for Flights

14

5.4

PRECEDENCE

Voice communications and voice instructions shall have precedence over data link communications at all times. This means that a data link instruction may, if required, be over-ruled by a voice instruction. Voice remains the primary medium of communication in this airspace.

5.5

UNCERTAINTY REVERT TO VOICE

If uncertainty arises to either controllers or aircrew, about the content of a data link message, the application of a data link message, or the validity of a data link message, they must REVERT TO VOICE to clarify the situation.

5.6

REPLIES

Wherever possible, CPDLC instructions and requests should be responded to using CPDLC. This is in addition to any voice read back requirements on the clearance or instruction. If a CPDLC message requiring a closure response is subsequently negotiated by voice, a CPDLC closure response message is still necessary to ensure the proper synchronisation of ground and aircraft systems.

5.7

VALIDITY OF REQUESTS

Unless over-ruled by a subsequent voice instruction, a clearance given by data link has the same validity as one made by voice. A downlink request by data link has the same validity as one made by voice.

5.8

APPROPRIATE USE

The operational utilisation of ATS over data link shall remain at all times under the control of the air traffic controllers and aircrew involved. If either believes that its use is inappropriate in the prevailing circumstances, then it should be suspended or terminated.

5.9

EMERGENCIES

At present, CPDLC is generally not intended for use in emergency situations, where speed of delivery of messages can be a crucial element. Voice communication, if available, should be used as today, for emergency situations.
Air / Ground Datalink Procedures for Flights

15

5.10

UPLINKED CLEARANCES, INSTRUCTIONS AND RESPONSES

5.10.1 UPLINKS The following uplink messages may be sent by controllers to aircrews conducting data link with Maastricht-UAC.
ATC Clearances CLIMB TO [level] DESCEND TO [level] MAINTAIN [level] MAINTAIN [speed] MAINTAIN PRESENT [speed] MAINTAIN [speed] OR GREATER MAINTAIN [speed] OR LESS RESUME NORMAL SPEED CONTINUE PRESENT HEADING FLY HEADING [degrees] TURN [direction] [degrees] (Relative PROCEED DIRECT TO [position] ATC Instructions CONTACT [unit name] [frequency] SQUAWK [code] SQUAWK IDENT CHECK STUCK MICROPHONE [frequency] ATC Replies to Downlink Requests STANDBY UNABLE Voice Read back Required YES YES YES YES YES YES YES YES YES YES YES YES Voice Read back Required NO NO NO NO

5.10.1.1

Uplink Level Instructions

Voice Read back Required YES YES YES

ATC Level Clearances CLIMB TO [level] DESCEND TO [level] MAINTAIN [level]

These clearances can be sent, either as clearances initiated by the controller, or as responses to requests from aircrew.

Air / Ground Datalink Procedures for Flights

16

All Flight Level clearances as listed in the above table shall be read back by the aircrew. The read back phraseology is: Call sign, confirming data link climb FL Following voice read back the aircrew shall then send a data link operational response to the message. The appropriate operational data link responses from an aircrew for these clearances are: WILCO / ACCEPT STANDBY UNABLE / REJECT If the operational response is WILCO the clearance shall be executed by the crew when the WILCO message is sent. Voice contact with ATC is required should any situation arise that prevents execution of a clearance following a WILCO response. If the operational response is UNABLE the crews inability to comply with the clearance shall be voiced on receipt of the clearance.

5.10.1.2

Uplink Route Instructions

Voice Read back Required YES YES YES YES

ATC Route Clearances CONTINUE PRESENT HEADING FLY HEADING [degrees] TURN [direction] [degrees] PROCEED DIRECT TO [position]

These clearances can be sent, either as clearances initiated by the controller, or as responses to requests from aircrew. All heading and route clearances as listed in the above table, shall be read back by the aircrew. The phraseology for read back is Call sign, confirming data link turn ... .. Following voice read back the aircrew shall then send a data link operational response to the message. The appropriate operational data link responses for these clearances are:
Air / Ground Datalink Procedures for Flights

17

WILCO STANDBY UNABLE If the operational response is WILCO the clearance shall be executed by the crew when the WILCO message is sent. Voice contact with ATC is required should any situation arise that prevents execution of a clearance following a WILCO response. If the operational response is UNABLE the crews inability to comply with the clearance shall be voiced on receipt of the clearance. Note: For FANS aircraft the implementation of the FLY HEADING [degrees] and the TURN [direction] [degrees] uplinks will present a ROGER option to the crew rather than a WILCO. After giving voice read back to ATC, aircrew selection and sending of a ROGER response in this instance is regarded as agreement from the crew that will also comply with the message in effect it is used as a WILCO in these circumstances. Since no UNABLE response is available to either of these messages for FANS aircraft, in the event of a crew being unable to comply with a FLY HEADING or TURN up linked message having informed ATC by voice they should let the message time expire.

5.10.1.3

Uplink Contact Instruction VCI

Voice Read back Required NO

ATC Instructions CONTACT [unit name] [frequency]

This instruction can be sent, either to transfer an aircraft to another Maastricht-UAC sector or to an adjacent ATC unit. The transfer instructions will detail the R/T call sign and frequency of the next unit. The crew shall execute the change of frequency when the WILCO message is sent Aircrew must always initiate a voice contact with the given frequency after a Contact message has been received. There is no requirement for the crew to read back the instruction by voice prior to execution.

Air / Ground Datalink Procedures for Flights

18

5.10.1.4

Uplink Squawk Instructions

Voice Read back Required NO

ATC Instructions SQUAWK [code]

This instruction can be sent when there is a requirement to alter the current SSR code of an aircraft. The change of squawk shall be executed by the crew when the WILCO message is sent. There is no requirement on the crew to read back the instruction by voice prior to execution.

5.10.1.5

Uplink Squawk Ident. Instructions

Voice Read back Required NO

ATC Instructions SQUAWK IDENT [code]

This instruction can be sent when there is a requirement to identify an aircraft, using the SPI feature. The SPI function shall be activated by the crew when the WILCO message is sent. There is no requirement on the crew to read back the instruction by voice prior to execution.

5.10.1.6

Uplink Check Stuck Microphone Instructions

Voice Read back Required NO

ATC Instruction CHECK STUCK MICROPHONE [frequency]

This instruction can be sent by a controller in circumstances where an aircraft may be blocking the voice frequency inadvertently. When a FANS-equipped aircraft receives this message a data link ROGER response should be sent.

Air / Ground Datalink Procedures for Flights

19

If the Check Stuck Microphone [frequency] message relates to the R/T frequency that an aircraft is currently using, then they should check that their radio equipment is not causing a permanent transmission. If the Check Stuck Microphone [frequency] message does not relate to the R/T frequency that an aircraft is using, then no action is required on the aircrews part.

5.10.1.7

ATC Replies to Downlink Requests

ATC Replies CLEARANCE STANDBY UNABLE

Controller responses to down linked Route requests will either be by data link or by voice, depending on operational circumstances prevailing at the time. If ATC can comply with a downlink request by data link they will do so in the form of issuing a clearance to the aircraft. In addition to issuing clearances, ATC can also respond to a downlink request by using STANDBY or UNABLE. In the event of a controller responding by UNABLE the dialogue will be closed by the ground system. In the event of a controller responding STANDBY to a request a further operational response will follow.

5.11

DOWNLINKED REQUESTS AND RESPONSES

5.11.1 DOWNLINKS A limited number of downlink requests are available in Maastricht-UAC airspace. Although the following downlink messages may be used, downlink requests via CPDLC should be kept to a minimum. If, following a downlink request, an error is generated aircrew should reiterate the request by voice, not by CPDLC.

Air / Ground Datalink Procedures for Flights

20

Aircrew Route Requests

REQUEST [level] REQUEST CLIMB TO [level] REQUEST DESCENT TO [level] REQUEST DIRECT TO [position]

5.11.1.1

Downlink Level Requests

Aircrew Route Requests

REQUEST [level] REQUEST CLIMB TO [level] REQUEST DESCENT TO [level]

These level messages may be transmitted by data link to request from the controller a change of level for the aircraft The controller has the ability to respond to these requests using either data link or voice. 5.11.1.2 Downlink Route Requests

Aircrew Route Requests REQUEST DIRECT TO [position] This message may be transmitted to request from the controller a direct routing to a point. The controller has the ability to respond to these requests using either data link or voice. 5.11.1.3 5.11.1.4 Aircrew Responses

Aircrew Responses
WILCO STANDBY UNABLE

Acceptable operational CPDLC responses to data link messages being used by Maastricht-UAC include: -

Air / Ground Datalink Procedures for Flights

21

WILCO STANDBY UNABLE ROGER See note.

Note: For FANS aircraft a TURN or HEADING uplink message is converted to free text format by the Maastricht-UAC ground system prior to uplink. Avionics on FANS aircraft will present a ROGER [not WILCO] data link response to this free text uplink. Following voice read back of the clearance, when a ROGER response to these uplinks is sent, aircraft compliance with the instruction is required.

Maastricht-UAC operates in a CPDLC environment in which uplinks that affect the profile of a flight [direction, level] require voice read back by the aircrew. This is in addition to a data link operational response. If responding WILCO to a profile-changing uplink message then the crew shall Firstly give voice read back of the clearance to ATC Then send a WILCO response and comply with / execute the clearance

Note: The above steps must be complied with in this order, in order to guarantee the correctness of the uplink clearance received prior to its execution. If responding WILCO to a non-profile-changing uplink message then the crew shall Send a WILCO response and comply with / execute the clearance Following a WILCO response to an uplink, should circumstances arise that prevent execution of a clearance or instruction, voice contact should be made with ATC. In the event of an aircrew responding STANDBY to a data link message, then a further operational response is required from them to close the dialogue. If the operational response to a clearance or instruction is UNABLE the crews inability to comply with the clearance or instruction shall be voiced on receipt of the clearance/instruction. If an aircrew receives an ERROR response to an operational response sent by them, or a Re-send prompt on their crew interface, they should not resend the CPDLC response, as they may only receive another Error. They should confirm their response to the clearance / message on R/T.

Air / Ground Datalink Procedures for Flights

22

5.11.1.5

Free text

On no account should FREETEXT be used by an aircrew, either to put a request, or in a response to an up linked message. If a FREETEXT message, or a message that is NOT supported by the ground environment is down linked, then the message SERVICE UNAVAILABLE will be displayed to the crew. On receipt of a SERVICE UNAVAILABLE message, aircrew should contact ATC to clarify their request. Freeform FREETEXT messages are not implemented for controller use at MAS-UAC.

Air / Ground Datalink Procedures for Flights

23

6.

END-TO-END SYSTEM

The description of the Maastricht-UAC data link system contained in this section is intended to be viewed as a simplified overview of the system. It is not intended as a detailed system specification. For a more detailed view of the system consult the PETAL End-to-End Specifications documentation.

6.1

END-TO-END

The end-to-end system for using data link messaging at Maastricht-UAC can be divided into three parts The Ground System The Communications Network The Aircraft Systems 6.2 GROUND SYSTEM AT MAASTRICHT-UAC

The data link ground system architecture at Maastricht-UAC is based on the existing Maastricht-UAC architecture, which relies on the current FDPS for most operational logic and functionality. The system supports different data link communications means ATN and FANS in a multi-stack environment. This means that Maastricht-UAC controllers can communicate with aircraft using either of these two technologies. It achieves this by providing a gateway [P2GW], external to the FDPS, which makes provision for the data channels and data exchange between the FDPS and the different communications networks. 6.3 COMMUNICATIONS NETWORK

Data link messages between aircraft and the Maastricht-UAC controllers are channelled through commercial communications service providers. The service provider networks facilitate data exchanges for both ATN and FANS messages.

Air / Ground Datalink Procedures for Flights

24

6.4

AIRCRAFT SYSTEMS

Aircraft conducting CPDLC with Maastricht-UAC do so via certified ATN or FANS equipment. The type of equipment carried varies from airline to airline, and from airframe to airframe.

6.4.1 DIAGRAM A simplified overview of the system is provided in the diagram below.

CONTROLLER

CONTROLLER

CONTROLLER

MAASTRICHT-UAC FDPS

Gateway

P2FEP ALLA
[ATN]

FAFEP
[FANS]

COMMUNICATIONS SERVICE PROVIDERS

AIRCRAFT

Figure 1 - Maastricht-UAC Ground System [simplified]

6.4.2 MORE More comprehensive explanation on the technical details is contained in PETAL End-to-End Specifications.

Air / Ground Datalink Procedures for Flights

25

7.
7.1

LOG-ON, CONNECTION AND DISCONNECTION

FLIGHT PLAN INFORMATION

Maastricht-UAC requests that flights intending to conduct CPDLC exchanges with Maastricht-UAC enter tail number or 24-bit address code [as appropriate] in field 18 of their flight plans. 7.2 LOG-ON

7.2.1 LOG-ON ADDRESS The log-on address for CPDLC communications with Maastricht-UAC is EDYY. Log-on to Maastricht-UAC covers the entire working area of the MaastrichtUAC. Aircraft do not need to log-on separately into each Maastricht-UAC sector.

7.2.2 LOG-ON TIME Ideally log-on should be initiated 15 to 45 minutes prior to entry into Maastricht-UAC airspace. For aircraft departing from airports beneath, or in close proximity to, Maastricht-UAC airspace, log-on can be initiated on the ground. Note: The time parameter of 15 45 minutes prior to entry is to ensure interoperability with log-on in other CPDLC regions worldwide. Pilots should be aware that CPDLC connection will not normally be attempted until the aircraft is within 10 minutes of the Maastricht-UAC boundary see Sections 7.3.1 and 7.3.2

7.2.3 CALLSIGN Aircraft should log-on using their ICAO call sign the call sign found on their flight plan [e.g. BER23, not AB0023].. Crews should ensure that they do not use a two-letter IATA flight identification to log-on. This will result in a failed log-on. Crew insertion of a leading zero [0] into a call sign will also result in a failed log-on.

Air / Ground Datalink Procedures for Flights

26

LOG-ON REQUEST

LOG-ON RESPONSE

E D Y Y

Figure 2 - Log-on Request and Response

7.3

CPDLC ENABLE

7.3.1 CPDLC INITIATION Following successful log-on and prior to entry into Maastricht-UAC the Maastricht-UAC ground system will initiate CPDLC connection. This is done in the form of a CPC Connect Request (CR1 for FANS) being sent to the aircraft. The aircraft response is in the form of a CPC Connect Confirm message (CC1 for FANS) to the ground system. This response is automatically generated by the avionics.

7.3.2 CPDLC INITIATION TIME Maastricht-UAC ground system will attempt CPDLC connection approximately 10 minutes prior to the entry of the aircraft into the airspace. For aircraft departing from airports beneath, or in close proximity to, Maastricht-UAC airspace, CPDLC connection will only occur above FL150. This is to ensure that crews are not distracted during busy periods of flight. If an aircraft logs-on from within Maastricht-UAC airspace CPDLC connection will occur as soon as log-on is complete

Air / Ground Datalink Procedures for Flights

27

7.3.3 CURRENT DATA AUTHORITY Following CPDLC connection confirmation the Maastricht-UAC ground system will also automatically receive a CDA notification Current Data Authority. Note: This function is emulated by the Gateway for FANS aircraft. Current Data Authority is the notification for the receiving ATSU that the aircraft is ready to conduct CPDLC with that ATSU.

LOG-ON REQUEST

LOG-ON RESPONSE

CPC CONNECT REQUEST CPC CONNECT CONFIRM

CDA

E D Y Y

Figure 3 - CPDLC Connection and CDA

7.3.4 CPDLC ONLY UNDER CONTROL OF MAASTRICHT-UAC Whilst the log-on, CPDLC connection and CDA sequence will normally be conducted outside Maastricht-UAC airspace, an aircraft must be under the control of a Maastricht-UAC sector controller, before CPDLC exchanges can occur. Air initiated CPDLC messages should only be attempted when a flight is transferred to, and under the control of, Maastricht-UAC. Aircrew receive notification of the fact that they have come under the control of Maastricht-UAC when they receive an uplink. CURRENT ATC UNIT EDYY MAASTRICHT-UAC CENTER Airborne attempts at CPDLC exchanges for flights not transferred to or under the control of Maastricht-UAC will result in errors being generated to the aircrew.

Air / Ground Datalink Procedures for Flights

28

7.4

INTER- SECTOR TRANSFER

Aircraft can be transferred via data link from one Maastricht-UAC sector to another Maastricht-UAC sector without the need for them to log-off and log-on repeatedly. Data link authority is transferred by the ground system to the appropriate sectors.

7.5

NEXT DATA AUTHORITY

Although currently, Maastricht-UAC does not have external data link partners is the system set up to take account of future partnerships. Prior to leaving Maastricht-UAC airspace, an aircraft will automatically be up linked a Next Data Authority message [NDA] by the Maastricht-UAC ground system. The purpose of this message is to alert the aircraft to its next intended data link partner.

NDA

E D Y Y

Figure 4 - Next Data Authority

Air / Ground Datalink Procedures for Flights

29

7.6

INTER-CENTRE TRANSFER

Aircraft leaving Maastricht-UAC airspace are transferred via data link with a CONTACT Instruction. After a WILCO from the aircraft, CPDLC will be terminated with the aircraft. In the normal course of events no crew interaction is required to log-off from Maastricht-UAC.

NDA

CONTACT INSTRUCTION

WILCO

CPC END REQUEST

CPC END CONFIRM

E D Y Y

Figure 5 - CONTACT and End Service

Air / Ground Datalink Procedures for Flights

30

8.

TIMEOUTS

The data link ground system in Maastricht-UAC employs several time-outs for messages. These time-outs are used to prevent data link messages becoming open-ended.

8.1

LOGICAL ACKNOWLEDGEMENT LACK

Some operational messages are sent to an aircraft that require avionics system verification of their arrival. This system verification of message receipt is referred to as a LACK, or Logical Acknowledgement. For FANS aircraft, the Message Assurance (MA) technical acknowledgement fulfils this role.

8.2 LACK TIME When an operational message that requires acknowledgement is sent, a timer is put into effect to receive a LACK from the aircraft (MA for FANS aircraft). The timer value for this technical response to be received by the MaastrichtUAC ground system is set at 30 seconds.

8.3

LACK TIME-OUT

8.3.1 SYSTEM BEHAVIOUR If the ground system does not receive a system response within 30 seconds it will alert the controller to that fact. The dialogue continues to remain open.

8.3.2 CONTROLLER BEHAVIOUR The controller will await the operational response or operational timeout..

8.4

OPERATIONAL TIME-OUT

After sending an operational message, a timer is put into effect to receive an operational response from the aircraft. (ie. WILCO, UNABLE, STANDBY) The timer value for this response to be received is set at 120 seconds.

Air / Ground Datalink Procedures for Flights

31

8.4.1 SYSTEM BEHAVIOUR If the ground system does not receive an operational response within 120 seconds it will

Close the dialogue Warn the air traffic controller

If the ground system subsequently receives an operational response after 120 seconds it will Issue an Error message to the aircrew If an aircrew receives an ERROR response to an operational response sent by them, or a Re-send prompt on their crew interface, they should not resend the CPDLC response, as they may only receive another Error. They should confirm their response to the clearance / message on R/T.

8.4.2 CONTROLLER BEHAVIOUR On receipt of an operational time-out warning the controller will revert to voice to clarify the situation with the aircrew.

8.5

OPERATIONAL TIME-OUT - STANDBY RESPONSE FROM CREW

If an aircrew responds to a data link message with a STANDBY, the timers for operational response are re-set. An operational response is then required from the crew no later than 60 seconds after a STANDBY has been sent

9.

AIRBORNE ERROR MESSAGES

9.1 ERROR MESSAGES In the event of receiving an ERROR message crews should revert to voice to clarify the operational situation with the controller. Crews should refrain from technical inquiries on the frequency with regard to possible reasons for provider aborts as controllers do normally not have any further information available.

Air / Ground Datalink Procedures for Flights

32

10.

REPORTING

CPDLC reports can be addressed to contact persons below, using the supplied form in Annex or any other agreed contact to Maastricht-UAC.

Robert LONSDALE Engineering DIV/Communication

Robert.Lonsdale@Eurocontrol.int

Horsterweg 11, 6199 AC Maastricht-Airport, Netherlands

Tel: +31 433 662 028

Volker STUHLSATZ

Volker.Stuhlsatz@Eurocontrol.int

Operations DIV/Operational and Airspace Systems Horsterweg 11, 6199 AC Maastricht-Airport, Netherlands Tel: +31 433 661 510

Air / Ground Datalink Procedures for Flights

33

ANNEX A CPDLC Report Flight Crew Data Link operations at Maastricht-UAC [EDYY] Time: Position:

Date:

C/S:

ACFT Type:

Registration: 24-Bit:

DL Provider:

Hardware CMU/FMC:

DL Mode:

Type of CPDLC event:

Airborne CPDLC LOG-ON failure

Unexpected CPDLC Provider abort (LOG-OFF)

Unexpected or Missing CPDLC message displayed

Erroneous CPDLC message received

Delayed CPDLC message receipt

Other (please specify problem in detail):

Was voice clarification need?

Which Error message was received?

Was expected CPDLC information missing?

How long was the delay of the CPDLC message?

Which abnormality was experienced?

Air / Ground Datalink Procedures for Flights

34

Air / Ground Datalink Procedures for Flights

35