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 55 of 173
PROCEDURE REQUEST
Use the PROCEDURE REQUEST page to construct and send a FANS DM request for a named
departure, approach, or arrival procedure from the current data authority.
Figure 3-25 FANS PROCEDURE REQUEST
Table 3-15 PROCEDURE REQUEST Fields
LSK
Label
Description
L1
TYPE
Required. Selection list:
• Blank (default)
• Departure
• Approach
• Arrival
L3
TRANSITION
Optional. A published identifier on the current route
R1
NAME
Required. Name of the procedure
R6
VERIFY
Enabled when required inputs are complete