User's Guide
Table Of Contents
- 1 Introduction
- 1.1 Audience
- 1.2 Overview
- 1.3 Envoy CMU Features
- 1.4 Configuration Options for Envoy
- 2 Operation of Envoy
- 3 CPDLC Operations
- 3.1 Log On
- 3.2 Logoff
- 3.3 Lost Connection
- 3.4 Typical Message Composition
- 3.5 ATC Menu
- 3.5.1 ATC Request Menu – FANS 1/A+ and ATN B1 CPDLC Common
- 3.5.2 ATC REPORT Menu
- 3.5.3 WHEN CAN WE EXPECT
- 3.5.4 POS REPORT Message – FANS 1/A+
- 3.5.5 EMERGENCY (MAYDAY) Message – FANS 1/A+
- 3.5.6 ATC MSG LOG
- 3.5.7 CLEARANCE REQUESTS – FANS 1/A+
- 3.5.8 FREE TEXT 1/2
- 3.5.9 ATC VOICE CONTACT Message – FANS 1/A+
- 3.5.10 Cancel EMERGENCY, Cancel ADS
- 3.5.11 Flight Plan Transactions and Monitoring
- 4 Automatic Dependent Surveillance (ADS)
- 5 ACARS Operations
- 6 MAINTENANCE Menu
- Appendix A Acronyms
- Appendix B AFN Messages
- Appendix C Supported CPDLC Messages
- Appendix D ADS-C Tags
- Appendix E ACARS Message Labels
- Appendix F ATSU Call Signs (ICAO, IATA)
- Appendix G Fault Management
User Guide for the Envoy Data Link
Document Number: UG-15000 Rev. A Page 73 of 173
Pushback Clearance Request
Use the PUSHBACK CLR REQ to notify ATC of request to commence departure.
Figure 5-8 PUSHBACK CLR REQ
All of the information on this page, other than free text, may be autopopulated from available flight
data or from prior ACARS or CPDLC activity for the current flight.
Table 5-6 PUSHBACK CLR REQ Fields
L1
ORIG
Read only. ICAO departure airport. Editable from Flight Init page, Section 5.4.1.1.
L2
GATE
Required. Departure gate. One to 5 characters.
L3
DATE (DD)
Required. Scheduled flight date--day of month (1 to 31).
L4
FREE TEXT
Optional field of up to 24 characters to clarify this request.
R1
DEST
Read only. ICAO destination airport. Editable from Flight Init page, Section 5.4.1.1.
R3
TIME
Scheduled flight time (required) (HHMM).
R6
SEND
The SEND action prompt appears after the required data has been entered. Press LSK to
transmit the downlink message.
LSK
LABEL
FUNCTION or DESCRIPTION