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 90 of 173
Figure 6-2 FLIGHT LOG - CURRENT 1/4
The other 3 pages of the FLT LOG show the OOOI details for the 3 prior flights.
Table 6-2 Envoy FLT Log
Parameter
Description
FLIGHT
The ICAO flight ID is autopopulated data from the Flight Management Computer (FMC).
ORIGIN
ICAO airport code for the departure location, autopopulated from the FMC.
DEST
ICAO airport code for the arrival/destination, autopopulated from the FMC.
TAIL ID
Obtained from the Envoy Personality Module.
ICAO address
Obtained from Envoy Personality Module.
FLT NUM
Derived from an aircraft FLT ID and the IATA airline code.
TYPE
OOOI state is autopopulated from discretes (see MONITOR 2/6 – OOOI, COMM, and
Message Status).
TIME
Envoy UTC time
FOB
Fuel Onboard is autopopulated from the FMC. This value can be expressed in LB or KG,
depending on aircraft configuration.
Data on the FLT LOG is read-only. OOOI data for the CURRENT can be accessed, printed, or sent
to AOC from the ACARS POST FLIGHT MENU.