Appendix D APPENDIX D. FLIGHT PLANNING D.1 Filing Required Communication Performance (RCP)/Required Surveillance Performance (RSP) Capabilities. When filing RCP/RSP capabilities, operators must ensure the planned use of associated communication and surveillance capabilities for the flight will be in accordance with regulations, policies, and procedures in control areas for the flight, as published by the applicable States in Aeronautical Information Publications (AIP) (or equivalent publications). Operators should ensure the proper information to denote Performance-based Communication and Surveillance (PBCS) capabilities is included in the International Civil Aviation Organization (ICAO) flight plan.
D.1.1 The following are determinations for proper filing:
1. Presence of relevant serviceable equipment on board the aircraft.
2. Equipment and capabilities commensurate with pilot qualifications.
3. When applicable, appropriate authorizations as described in FAA operations specifications (OpSpec)/management specifications (MSpec)/letters of authorization (LOA).
D.2 Regulatory Basis. Flight planning must be in accordance with the following where applicable:
1. Part 91:
• § 91.169, IFR Flight Plan: Information Required.
• § 91.173, ATC Clearance and Flight Plan Required.
2. Part 121:
• § 121.667, Flight Plan: VFR and IFR: Supplemental Operations.
• § 121.695, Disposition of Load Manifest, Dispatch Release, and Flight Plans:
Domestic and Flag Operations.
• § 121.697, Disposition of Load Manifest, Flight Release, and Flight Plans:
Supplemental Operations.
3. Part 125, § 125.405, Disposition of Load Manifest, Flight Release, and Flight Plans.
D.2.1 Flight Plan Descriptors:
• D1and G1 for Automatic Dependent Surveillance-Contract (ADS-C) (Table D-2, Item 10b Flight Plan Descriptors for Surveillance Equipment);
• J1 through J7 for Controller-Pilot Data Link Communication (CPDLC) (Table D-1, Item 10a Flight Plan COM Descriptors); and
• P1 and P2 for RCP Performance (Table D-1).
D-1
Appendix D Note 1: Refer to ICAO Doc 4444, Procedures for Air Navigation Services – Air Traffic Management, Appendix 2, for flight plan requirements. Also, refer to the FAA Flight Planning Information website.
Note 2: The inclusion of PBCS capability in the filed flight plan indicates that the relevant aircraft equipment comprising the aircraft system is approved and serviceable, the pilot is appropriately trained and qualified, and the operator holds applicable authorization to use the equipment for PBCS operations. If these conditions are not met, then PBCS capability should not be included in the flight plan.
D.3 Example. As a flight plan example, use the following:
If Actual Communications Performance (ACP) meets at least RCP 240 at 95 percent and Actual Surveillance Performance (ASP) meets at least RSP 180 at 95 percent, then the operator approved for RCP 240/RSP 180 may file the following:
• Field 10: “P2.”
• Field 18: “SUR/RSP180.”
D.3.1 If ACP does not meet RCP 240 at 95 percent, then the operator may file for RCP 400 by entering P1 and/or P3 in field 10. If ASP does not meet RSP 180 at 95 percent, then the operator may file for RSP 400 by entering “SUR/RSP400” in field 18.
D.4 Item 10a Descriptors. In Item 10a of the flight plan, operators should insert one of the descriptors, P1-P2, as appropriate, listed in Table D-1, to identify an aircraft’s RCP capability.
D-2
Appendix D Table D-1. Item 10a Flight Plan COM Descriptors Descriptors System E1 FMC WPR ACARS E2 D-FIS ACARS E3 PDC ACARS J1 CPDLC ATN VDL Mode 2 J2 CPDLC FANS 1/A HFDL J3 CPDLC FANS 1/A VDL Mode 0/A J4 CPDLC FANS 1/A VDL Mode 2 J5 CPDLC FANS 1/A SATCOM (Inmarsat) J6 CPDLC FANS 1/A SATCOM (MTSAT) J7 CPDLC FANS 1/A SATCOM (Iridium) P1 CPDLC RCP 400 P2 CPDLC RCP 240 Note: Part 91 operators filing “J” codes for U.S. domestic data link services must have a data link authorization to file J5–J7 in oceanic and remote continental airspace.
D.5 Item 10b Descriptors. In Item 10b of the flight plan, operators should insert one of the descriptors, D1 and G1, as appropriate, listed in Table D-2, to identify an aircraft’s RSP capability:
Table D-2. Item 10b Flight Plan Descriptors for Surveillance Equipment Descriptor System D1 ADS-C with FANS 1/A capabilities G1 ADS-C with ATN capabilities D.6 Item 18 RSP Specification. In Item 18 of the flight plan, the aircraft operator should file the RSP capability by inserting the indicator “SUR/” followed by the appropriate RSP specification (e.g., RSP400 or RSP180).
Note: The ATSU unit uses the flight plan information to determine when to apply particular Air Traffic System Management (ATM) operations that are dependent on the capability and to configure the system (e.g., set timer threshold values) for efficient operation when RCP and/or RSP varies.
D-3
Appendix D D.7 Field 18/DAT for CPDLC or Pre-Departure Clearance (PDC). The proposed data link communication “codes” in Field 18/DAT are an optional mechanism for the user to notify FAA automation to generate a CPDLC or PDC.
• Field 10a (Equipage) used to identify aircraft capabilities.
• Field 18 (Other Information) DAT/ codes used to identify flights getting CPDLC or PDC.
• Need to fill in Field 10a in order to get to Field 18 DAT/.
• Field 18 DAT/ codes will include a primary/secondary hierarchy.
Table D-3. PDC and Departure Clearance (DCL) Operators Using Data Link Communication Capability Field 10a Data Link Communication for Field 18 DAT/* Comments for FANS in U.S. Domestic Operations Some aircraft are non-ACARS equipped, and 10a is physical equipage. Still get PDC via other means
(e.g., gate printer).
Optional if currently getting PDC.
PDC only** Not ACARS e quipped but gets PDC via manual means.
Z 1 PDC PDC only** Equipped only for ACARS/PDC. E3 Z 1PDC Optional if currently getting PDC.
PDC only** Equipped for ACARS/PDC and FANS but wants PDC only.
E3J4Jx Z 1PDC Equipped for ACARS/PDC and FANS 1/A or 1/A(+), and possibly other capabilities (Jx).
FANS 1/A & FANS 1/A+ DCL only Equipped for FANS 1/A only for CPDLC-DCL.
E3J4Jx Z 1FANS Identifies U.S. domestic preference for FANS 1/A DCL.
Code number shows priority preference,
(e.g., DCL is primary preference; FANS 1/A DCL is secondary that will be used if primary is unavailable and if feasible).
FANS 1/A & FANS 1/A+ DCL Equipped for ACARS/PDC and FANS with primary/secondary preferences.
E3J4Jx Z 1FANS2PDC * No spaces in actual DAT/ codes.
** No ICAO flight plan change required if user currently gets PDC and does not want DCL. Current PDC designation will be the default.
D-4
Appendix D Table D-4. PDC and En Route Data Link Clearances Operators Using Data Link Communication Capability Field 10a Data Link Communication for Field 18 DAT/* Comments for FANS in U.S. Domestic Operations FANS 1/A & FANS 1/A+ No En Route Arrival Load Issues For flights authorized for en route data link with no en route arrival load issues as well as for ACARS/PDC and
CPDLC-DCL with primary/secondary preferences.
E3J4Jx Z 1FANSE2PDC This code is to be used to obtain CPDLC-DCL and en route clearances with aircraft that have no en route arrival load issues; PDC is secondary that will be used if primary is unavailable and if feasible.
FANS 1/A & FANS 1/A+ With En Route Arrival Load Issues For flights authorized for en route data link with en route arrival load issues as well as for ACARS/PDC and
CPDLC-DCL with primary/secondary preferences.
E3J4Jx Z 1FANSER2PDC This code is to be used to obtain CPDLC-DCL and en route clearances with aircraft that have en route arrival load issues; PDC is secondary that will be used if primary is unavailable and if feasible.
* No spaces in actual DAT/ codes.
D-5
Appendix D Table D-5. PDC Only and En Route Data Link Operators Using Data Link Communication Capability Field 10a Data Link Communication for Field 18 DAT/* Comments for FANS in U.S. Domestic Operations FANS 1/A & FANS 1/A+ No En Route Arrival Load Issues For flights authorized for en route data link with no en route arrival load issues and for PDC service only.
E3J4Jx Z 1PDCFANSE This code is to be used to obtain PDC and CPDLC en route clearances with aircraft that have no en route arrival load issues (No Tower DCL) (see Table D-6).
FANS 1/A & FANS 1/A+ With En Route Arrival Load Issues For flights authorized for en route data link with en route arrival load issues and for PDC service only.
E3J4Jx Z 1PDCFANSER This code is to be used to obtain PDC and CPDLC and en route clearances with aircraft that have en route arrival load issues (No Tower DCL) (see Table D-6).
* No spaces in actual DAT/ codes.
Table D-6. En Route Data Link Clearances Only Operators Using Data Link Communication Capability Field 10a Data Link Communication for Field 18 DAT/* Comments for FANS in U.S. Domestic Operations FANS 1/A & FANS 1/A+ No En Route Arrival Load Issues For flights authorized for en route data link with no en route arrival load issues.
J4
Z FANSE This code is to be used to obtain CPDLC en route clearances with aircraft that have no en route arrival load issues. (No Tower DCL or PDC.)
FANS 1/A & FANS 1/A+ With En Route Arrival Load Issues For flights authorized for en route data link with en route arrival load issues.
J4
Z FANSER This code is to be used to obtain CPDLC en route clearances with aircraft that have en route arrival load issues. (No Tower DCL or PDC.)
* No spaces in actual DAT/ codes.
D-6
Appendix E APPENDIX E. VOICE PHRASEOLOGY Table E-1. Voice Phraseology Related to Controller-Pilot Data Link Communication (CPDLC) From Pilot Condition Voice Phraseology To notify air traffic control (ATC) of a correction to a CPDLC message. (International Civil Aviation Organization.
(ICAO) Doc 4444) DISREGARD CPDLC (message type) MESSAGE, BREAK (correct information or request) To notify ATC of a single CPDLC message failure. (ICAO Doc 4444) CPDLC MESSAGE FAILURE (appropriate information or request) To notify ATC of an aircraft data link system or CPDLC connection failure.
(ICAO Doc 4444) CPDLC FAILURE (requests/notifications) Note: This voice phraseology is included only with the first transmission made for this reason.
Example: CPDLC FAILURE. CONTINUING ON VOICE.
To advise ATC the CPDLC connection is being terminated manually and logon/notification procedure is being initiated with the next Air Traffic Service Unit (ATSU).
DISCONNECTING CPDLC WITH (facility designation). LOGGING ON TO (facility designation) Note: The facility designation is the ICAO four-character facility code or facility name.
To advise ATC that a logon/notification procedure is being initiated following restoration of data link service.
LOGGING ON TO (facility designation) To advise ATC that a delayed CPDLC uplink has been received and to request clarification of the intent of the CPDLC message.
DELAYED CPDLC MESSAGE RECEIVED (requests) E-1
Appendix E Table E-2. Voice Phraseology Related to CPDLC From the ATSU Condition Voice Phraseology To advise all stations or a specific flight of a complete ground system failure and provide further instructions. (ICAO Doc 4444) (ALL STATIONS) CPDLC FAILURE (instructions).
Example:
ALL STATIONS CPDLC FAILURE.
DISCONNECT CPDLC. CONTINUE ON VOICE To instruct the pilot of a single CPDLC message failure. (ICAO Doc 4444) CPDLC MESSAGE FAILURE (appropriate clearance, instruction, information or request) To instruct the pilot of a correction to a CPDLC clearances, instructions, information or requests. (ICAO Doc 4444) DISREGARD CPDLC (message type) MESSAGE, BREAK (correct clearance, instruction, information or request) To instruct all stations or a specific flight to avoid sending CPDLC requests for a limited period of time. (ICAO Doc 4444) (ALL STATIONS) STOP SENDING CPDLC REQUESTS (UNTIL ADVISED) ((reason)) To instruct the pilot to manually initiate a logon/notification to the subsequent ATSU.
DISCONNECT CPDLC THEN LOGON TO (facility designation) Note 1: The (facility designation) is the four character ICAO code.
Note 2: Use this voice phraseology when the CPDLC transfer to an adjacent ATSU has failed.
To advise the pilot prior to the commencement of a CPDLC shutdown and instruct them to continue on voice.
CPDLC WILL BE SHUT DOWN.
DISCONNECT CPDLC. CONTINUE ON VOICE To advise all stations or a specific flight to resume normal CPDLC operations and provide the logon/notification address.
(ALL STATIONS) RESUME NORMAL CPDLC OPERATIONS. LOGON TO (facility designation) E-2
Appendix F APPENDIX F. CONTRO LLER-PILOT DATA LINK COMMUNICATION (CPDLC)
UPLINK AND DOWNLINK TABLES Table F-1. Color Key Blue Uplink Tables Green Downlink Tables Table F-2. Response Attribute of CPDLC Message Element for Uplink Messages Response Attribute Description W/U Response required. Yes Valid responses. WILCO, UNABLE, STANDBY, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY, LOGICAL ACKNOWLEDGEMENT (only if required), ERROR Note: WILCO, UNABLE, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY and ERROR will close the uplink message.
FANS 1/A: WILCO, UNABLE, STANDBY, ERROR, NOT CURRENT DATA AUTHORITY.
A/N Response required. Yes Valid responses. AFFIRM, NEGATIVE, STANDBY, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY, LOGICAL ACKNOWLEDGEMENT (only if required), ERROR Note: AFFIRM, NEGATIVE, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY and ERROR will close the uplink message.
FANS 1/A: AFFIRM, NEGATIVE, STANDBY, ERROR, NOT CURRENT DATA AUTHORITY.
R Response required. Yes Valid responses. ROGER, UNABLE, STANDBY, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY, LOGICAL ACKNOWLEDGEMENT (only if required), ERROR Note: ROGER, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY and ERROR will close the uplink message.
FANS 1/A: ROGER, STANDBY, ERROR, NOT CURRENT DATA AUTHORITY. FANS 1/A aircraft do not have the capability to send UNABLE in response to an uplink message containing message elements with an “R” response attribute. For these aircraft, the pilot may use alternative means to UNABLE the message. These alternative means will need to be taken into consideration to ensure proper technical and operational closure of the communication transaction.
F-1
Appendix F Response Attribute Description Y Response required. Yes Valid responses: Any CPDLC downlink message, LOGICAL ACKNOWLEDGEMENT (only if required) N Response required. No, unless logical acknowledgement required.
Valid Responses (only if LOGICAL ACKNOWLEDGEMENT is required). LOGICAL
ACKNOWLEDGEMENT, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT
DATA AUTHORITY, ERROR FANS 1/A: Defined “Response not required,” but not used. Under some circumstances, an ERROR message will also close an uplink message.
NE [Not defined in International Civil Aviation Organization (ICAO) Doc 4444] FANS 1/A: The WILCO, UNABLE, AFFIRM, NEGATIVE, ROGER, and STANDBY responses are not enabled (NE) for pilot selection. An uplink message with a response attribute NE is considered to be closed even though a response may be required operationally. Under some circumstances, a downlink error message may be linked to an uplink message with a NE attribute.
Table F-3. Response Attribute of CPDLC Message Element for Downlink Messages Response Attribute Description Y Response required. Yes Valid responses: Any CPDLC uplink message, LOGICAL ACKNOWLEDGEMENT (only if required).
N Response required. No, unless logical acknowledgement required.
Valid responses (only if LOGICAL ACKNOWLEDGEMENT is required). LOGICAL
ACKNOWLEDGEMENT, MESSAGE NOT SUPPORTED BY THIS ATC UNIT, ERROR FANS 1/A: Aircraft do not have the capability to receive technical responses to downlink message elements with an “N” response attribute (other than LACK or ERROR for ATN B1 aircraft).
In some cases, the response attribute is different between FANS 1/A aircraft and ICAO Doc 4444.
As an example, most emergency messages have an “N” response attribute for FANS 1/A whereas ICAO Doc 4444 defines a “Y” response attribute for them. As a consequence, for FANS 1/A aircraft, the ATC will need to use alternative means to acknowledge to the pilot that an emergency message has been received.
F-2
Appendix F Table F-4. Route Uplink Message Elements (RTEU) Operational Definition in PANS-ATM (Doc 4444) CPDLC Message Sets Message Element Identifier Message Element Intended Use Format for Message Element Display Resp. FANS 1/A ATN B1 RTEU-1 Instruction to proceed via the specified departure clearance.
(departure clearance) W/U UM169 (free text) Note: UM169 may be combined with UM158 ATIS (ATIS code) and/or UM123 SQUAWK (beacon) code) and/or UM19 MAINTAIN (altitude).
N/A RTEU-2 Instruction to proceed directly to the specified position.
PROCEED DIRECT TO ( position) W/U UM 74 PROCEED DIRECT TO (position) UM74 PROCEED
DIRECT TO (position) RTEU-2 Instruction to proceed directly to the specified position.
PROCEED DIRECT TO ( position) W/U UM 75 WHEN ABLE
PROCEED DIRECT TO (position) Note: This message element is equivalent to SUPU-5 plus RTEU-2 in ICAO Doc 4444.
N/A RTEU-3 Instruction to proceed, at the specified time, directly to the specified position.
AT TIME (time) PROCEED DIRECT TO (position) W/U UM76 AT (time)
PROCEED DIRECT TO (position) N/A RTEU-4 Instruction to proceed, at the specified position, directly to the next specified position.
AT (position) PROCEED DIRECT TO (position) W/U UM77 AT (position)
PROCEED DIRECT TO (position) N/A RTEU-5 Instruction to proceed upon reaching the specified level, directly to the specified position.
AT (level single) PROCEED DIRECT TO (position) W/U UM78 AT (altitude)
PROCEED DIRECT TO (position) N/A F-3
Appendix F Operational Definition in PANS-ATM (Doc 4444) CP DLC Message Sets Message Element Identifier Message Element Intended Use Format for Message Element Display Resp. FANS 1/A ATN B1 RTEU-6 Instruction to proceed to the specified position via the specified route.
CLEARED TO (position) VIA (departure data[O]) (en-route data) W/U UM79 CLEARED TO (position) VIA (route clearance) UM79 CLEARED TO (position) VIA (route clearance) RTEU-7 Instruction to proceed via the specified route.
CLEARED (departure data[O]) (en-route data) (arrival approach data) W/U UM80 CLEARED (route clearance) UM80 CLEARED (route clearance) RTEU-8 Instruction to proceed in accordance with the specified procedure.
CLEARED (procedure name) W /U UM81 CLEARED (procedure name) N/A RTEU-9 Instruction to proceed from the specified position via the specified route.
AT (position) CLEARED (en-route data) (arrival approach data) W/U UM83 AT (position)
CLEARED (route clearance) N/A RTEU-10 Instruction to proceed from the specified position via the specified procedure.
AT (position) CLEARED (procedure name) W/U UM84 AT (position) CLEARED (procedure name) N/A RTEU-11 Instruction to enter a holding pattern at the specified position in accordance with the specified instructions.
Note: RTEU-13 EXPECT
FURTHER CLEARANCE AT TIME (time) is appended to this message when an extended hold is anticipated.
AT (position) HOLD
INBOUND TRACK (degrees)(direction) TURNS (leg type) LEGS W/U UM91 HOLD AT (position) MAINTAIN (altitude) INBOUND TRACK (degrees) (direction) TURN LEG TIME (leg type) N/A F-4