Order JO 7110.113G Procedures for Issuing Automated Clearances
This document is cancelled. It may have been replaced. Check the official source before relying on it.
a. PDC – General. › (4) PDC clearance information must be operational in nature.
U.S. DEPARTMENT OF TRANSPORTATION
FEDERAL AVIATION ADMINISTRATION
Air Traffic Organization Policy
ORDER JO 7110.113G
Effective date:
06/12/2023
SUBJ: Procedures for Issuing Automated Clearances
1. Purpose of This Order. This order prescribes procedures for issuing departure clearances using the pre-departure clearance (PDC) and the Controller Pilot Data Link Communications (CPDLC) function of the Tower Data Link System (TDLS) between airport traffic control towers (ATCT) and authorized users.
2. Audience. This change applies to all Air Traffic Organization (ATO) personnel and anyone using ATO directives.
3. Where Can I Find This Order? This order is available on the MyFAA employee website at https://employees.faa.gov/tools_resources/orders_notices/ and on the FAA website at http://www.faa.gov/regulations_policies/orders_notices/.
4. Cancellation. FAA Order JO 7110.113F, Procedures for Issuing Automated Clearances, dated October 2, 2017, is canceled.
5. Explanation of Policy Changes. The changes to this order include new requirements and procedures for transmitting clearances when in auto mode for facilities that close. Revised contact information removing the Policy Directorate, AJV-P, as the point of contact (POC) for new PDC applicants and replacing with the Tower Data Link System (TDLS) Second Level Support team. Added a requirement for the TDLS Application Specialist (TAS) to complete TAS course prior to editing the TDLS application.
6. Procedures.
a. PDC – General.
(1) Review all clearances for accuracy and route integrity.
(2) Ensure all information is complete and understandable to the recipient, and the route of flight is continuous.
(3) PDC does not permit amended or revised flight plans to be transmitted. Revised or amended flight plans require the clearance to be verbally issued to the flight crew.
NOTE– A flight plan that initially generates in the tower, with a route assigned by automation, (for example: ADR) is not considered revised or amended and may be transmitted.
(4) PDC clearance information must be operational in nature. All selectable fields will be predefined by the TAS and available from a drop down menu.
Distribution: Electronic Initiated By: AJV-P
06/12/2023 JO 7110.113G (5) The Air Traffic Manager (ATM) must determine the mode of PDC operation. Prior to use of the "AUTO" mode, facilities must establish procedures to immediately detect and promptly correct any data transmitted in error.
b. Local Directive. The ATM must establish a facility directive for… › (7) Do not imply or use terms such as "Cleared as filed" or "As filed"…
(a) Facilities must not transmit clearance information through the use of “auto” mode two hours prior to closing, in cases where the facility is part-time.
(b) Establish procedures to disable the auto sending of clearances prior to closing and include clearance void time instructions.
(6) For a minimum of 60 days following the commissioning of a TDLS system, the facility Automatic Terminal Information Service (ATIS) must broadcast that PDC is available.
(7) Technical Operations (TO) personnel must be notified when an outage or problem occurs with any element of the TDLS.
b. Local Directive. The ATM must establish a facility directive for transmitting automated clearances. The directive must contain local procedures and responsibilities for processing clearances and must include the following:
(1) Procedures to review clearances for accuracy and route integrity. Include procedures for correcting information prior to transmitting and/or to verbally correct information that has changed or been transmitted in error.
(2) Procedures for issuing Departure Procedures (DPs), Standard Instrument Departure (SIDs) procedures, climb-out procedures, altitude information, departure frequencies, and other air traffic control information in accordance with this directive.
(3) Responsible positions and procedures to ensure that all applicable clearance information, in accordance with FAA Order JO 7110.65, Air Traffic Control, is conveyed to the pilot either via Selectable Fields or verbal communication.
(4) Local procedures for use of Selectable Fields in accordance with this directive.
(5) Procedures for monitoring and reporting routes which are routinely generated by automation that differ from the filed route (indicated with plus signs on flight progress strip) to the facility POC TAS, who will report to the appropriate Air Route Traffic Control Center (ARTCC) POC as necessary.
(6) Only include information that is not contrary to that in an assigned SID and necessary for a facility specific operation. Once transmitted, if any clearance information changes or if it is contrary to that in an assigned SID, that information must be issued verbally.
(7) Do not imply or use terms such as "Cleared as filed" or "As filed" in a PDC automated clearance.
c. Controller Pilot Data Link Communications (CPDLC) - General. › (6) TO personnel must be notified when an outage or problem occurs with…
06/12/2023 JO 7110.113G (8) Only standard contractions found in FAA Order JO 7340.2 must be used in populating Selectable Fields.
(9) Procedures for operating in "AUTO" mode, when applicable.
(a) Facilities must not transmit clearance information through the use of “auto” mode two hours prior to closing, in cases where the facility is part-time.
(b) Establish procedures to disable the auto sending of clearances prior to closing and include clearance void time instructions.
(10) A Letter to Airmen (LTA) outlining the services being provided by PDC must be issued for a minimum of 2 years following commissioning of the system. The LTA must direct applicants who request to participate to contact TDLS Second Level Engineering Team, AJW 17, at [email protected].
c. Controller Pilot Data Link Communications (CPDLC) - General.
(1) All clearances must be reviewed for accuracy and route integrity. Action must be taken to ensure all information is complete and understandable to the recipient, and the route of flight is continuous.
(2) CPDLC permits amended or revised flight plans to be transmitted. Revised or amended flight plans that cannot be delivered using CPDLC must be verbally issued to the flight crew.
(3) CPDLC clearance information must be operational in nature. All selectable fields will be pre-defined by the TAS and available from a drop-down menu.
(4) The ATM must determine the mode of CPDLC operation. Prior to use of the "auto" mode, facilities must establish procedures to immediately detect and promptly correct any data transmitted in error.
(a) Facilities must not transmit clearance information through the use of “auto” mode two hours prior to closing, in cases where the facility is part-time.
(b) Establish procedures to disable the auto sending of clearances prior to closing and include clearance void time instructions.
(5) For a minimum of 60 days following the commissioning of a CPDLC capability, the facility ATIS must broadcast that CPDLC is available.
(6) TO personnel must be notified when an outage or problem occurs with any element of the TDLS.
(1) Selectable Field 1, SID Field, must contain: › (b) the SID assigned by the En Route Automation System (EAS), or
06/12/2023 JO 7110.113G d. Local Directive. The ATM must establish a facility directive for transmitting automated clearances. The directive must contain local procedures and responsibilities for processing clearances and must include the following:
(1) Procedures to review all clearances, including initial and revised clearances for accuracy and route integrity.
(2) Procedures for correcting errors via voice if unable to use CPDLC.
PHRASEOLOGY– DISREGARD CPDLC MESSAGE.
(3) Procedures for issuing DPs, SIDs, climb-out procedures, altitude information, departure frequencies, and other air traffic control information in accordance with this directive.
(4) Procedures for accomplishing coordination prior to transmitting revised clearances.
(5) Procedures for ensuring acknowledgment of WILCO, UNABLE, and STANDBY for revised clearances.
(6) Procedures for handling all flight deck responses.
(7) Procedures for handling controller alerts, errors, and timeouts.
(8) Responsible positions and procedures to ensure that all applicable clearance information in accordance with FAA Order JO 7110.65, Air Traffic Control, is conveyed to the pilot either via verbal communication or CPDLC.
(9) Procedures for operating in "AUTO" mode, when applicable.
(a) Facilities must not transmit clearance information through the use of “auto” mode two hours prior to closing, in cases where the facility is part-time.
(b) Establish procedures to disable the auto sending of clearances prior to closing and include clearance void time instructions.
e. Departure Clearance (DCL) Application (PDC/CPDLC) Selectable Fields. The DCL application provides up to nine Selectable Fields for the tower controller to enter all other clearance information. Each Selectable Field has a purpose and should only be used for that purpose. For standardization, facilities must use DCL Application Selectable Fields as follows:
(1) Selectable Field 1, SID Field, must contain:
(a) The correctly filed SID, or
(b) the SID assigned by the En Route Automation System (EAS), or
e. Departure Clearance (DCL) Application (PDC/CPDLC) Selectable Fields.… › (7) Selectable Field 7, Departure Frequency Field, is reserved for…
06/12/2023 JO 7110.113G (c) if No SID is filed or assigned by EAS, the controller must either select a SID or, if no SID is to be assigned, select the “NO SID” option.
(2) Selectable Field 2, Transition Field, is reserved for named Transitions on DPs. Selectable Field 2 must contain:
(a) The correctly filed Transition, or
(b) the Transition assigned by the EAS, or
(c) if No Transition is filed or assigned by EAS, the controller must either select a Transition or, if no Transition is to be assigned, select the “- - - -” option.
(3) Selectable Field 3, Climb Out Field, is reserved for climb related information, such as heading assignments, expected vector assignments, or defined SID climbs. Climb Out Field instructions must never contradict SID instructions and may reiterate pertinent SID information. This field is limited to 32 characters and only those entries adapted by the TAS will be available for selection.
(4) Selectable Field 4, CLIMB VIA Field, is reserved for use when a SID is assigned or selected, and will contain CLIMB VIA SID or CLIMB VIA SID EXCEPT MAINTAIN (altitude) information as follows:
(a) If the assigned SID contains vertical guidance from take-off to climb to an altitude to maintain, and it is intended that an aircraft vertically navigate in accordance with the SID assigned or entered in Selectable Field 1, then Selectable Field 4 must contain the instruction “CLIMB VIA SID”, or
(b) If the assigned SID does not have an initial altitude to maintain, but contains vertical guidance, and it is intended that an aircraft vertically navigate in accordance with the SID assigned or entered in Selectable Field 1, then Selectable Field 4 must contain the instruction “CLIMB VIA SID EXCEPT MAINTAIN (altitude)”, or
(c) If the assigned altitude is different from the published altitude in the SID, the altitude may be amended using, CLIMB VIA SID EXCEPT MAINTAIN (altitude).
(5) Selectable Field 5, Maintain Altitude Field, is reserved for initial altitude Assignment. If no SID is assigned or the assigned SID does not contain either an initial altitude or vertical guidance, then Selectable Field 5 must contain the instruction “MAINTAIN (assigned altitude)”.
(6) Selectable Field 6, Expected Altitude Field, is reserved for specifying when the Expected Altitude would be used in the event of lost communications.
(7) Selectable Field 7, Departure Frequency Field, is reserved for Departure Control Frequency Assignment. The selection of “SEE SID” may be used if the SID contains Departure Control Frequency Assignment specific to the intended departure procedure.
6. Procedures. › g. Coordination. All matters pertaining to the PDC/CPDLC/TDLS of…
06/12/2023 JO 7110.113G (8) Selectable Field 8, Contact Field, is reserved for additional contact information in accordance with facility directives. This field is limited to 32 characters.
(9) Selectable Field 9, Local Information Field, is reserved for additional information in accordance with facility directives. This field is limited to 34 characters and must not contradict information contained elsewhere in a departure clearance.
f. TAS. The ATM must designate two air traffic personnel as facility TASs. The TASs must:
(1) Complete the TDLS Application Specialist Course #50085001 prior to editing adaptations at the Maintenance TDLS Menu (MTM) Console.
(2) Configure air traffic components of TDLS, incorporate air traffic operational data, monitor data and configurations to ensure accuracy and currency, make adjustments to TDLS as required, and maintain the TDLS adaptation for currency and optimum usability.
NOTE– When configuring the TDLS MTM, the TAS should use published SID codes and transitions. For each SID in their local adaptation, enter the SID name and number, the common point, and all associated transitions, if any. If a facility deviates from this, local documentation should be established outlining the deviations. Coordination with overlying and adjacent facilities may be necessary if deviating from the above settings.
(3) Share responsibility and coordinate with the TO TDLS System Administrator(s) as necessary.
(4) Receive reports and monitor routes which are routinely generated by automation that differ from the filed route (indicated with plus signs on flight progress strip). Investigate likely causes of multiple, repeated occurrences. Report the findings to appropriate ARTCC DCL POC.
(5) Report system anomalies and enhancement requests to the TDLS Second Level Engineering Team, AJW-17, at [email protected].
g. Coordination. All matters pertaining to the PDC/CPDLC/TDLS of system-wide interest, including notification of new participants, must be coordinated through the TDLS Second Level Engineering Team, AJW-17, at [email protected].
Michael R. Beckles Director (A), Policy, AJV-P Air Traffic Organization
Appendix A. Administrative Information › 3. Authority to Change This Order.
Appendix A
Appendix A. Administrative Information
1. Distribution. This order is distributed to the following ATO service units: Terminal, En Route and Oceanic, Technical Operations, System Operations, and Mission Support; the ATO Office of Safety and Technical Training; the Air Traffic Safety Oversight Service; the William J. Hughes Technical Center; and the Mike Monroney Aeronautical Center.
2. Background. The automated PDC/TDLS is a data link between the ATCT Flight Data Input/Output System (FDIO) and specially equipped aircraft, or the User Flight Planning Computer System. The data is presented to the clearance delivery (CD) position on a terminal display in the form of a tabular list and flight plan display area. A CD specialist may append the flight plan by including approved information before relaying the clearance. The resulting departure clearance is then transmitted to the participant network computer via a data communication transfer. The PDC process virtually eliminates the need for verbal communications with participating aircraft and reduces the amount of frequency congestion, especially during peak traffic periods.
The TDLS system currently deployed at select airports throughout the NAS is being upgraded to include delivering DCL to equipped aircraft using CPDLC. Software upgrade to accommodate CPDLC has changed the display and adaptation of the legacy PDC service and is a major change for the clearance delivery controller and the TAS of the TDLS system.
The primary difference between the PDC function and the new CPDLC service is the PDC service depends on the Airlines/Flight Operations Center or other third party to deliver the predeparture clearance to the aircraft, while the CPDLC service is a direct connection from the tower automation to the flight deck avionics. The direct connection between the tower automation and the flight deck allows for revised data to be delivered to the aircraft up to the point of departure. The PDC function is still prohibited from delivering revised clearances.
The pre-departure clearance data from the EAS is presented to the CD position on a terminal display in the pick list and flight plan display area. The pick list will indicate which flights will receive a CPDLC clearance and which flights will receive a PDC clearance. The presentation of departure clearances to the controller will remain virtually the same, with a few minor changes for the CPDLC clearances. The CD specialist may append the flight plan by including approved information before sending the clearance. The resulting DCL is transmitted to the participant network computer for PDC clearances, or to the flight deck avionics for CPDLC clearances, via a data communication transfer.
Indications of revised flight data from the EAS will be presented to the controller in the pick list. CPDLC clearances will be selected and displayed in the flight plan display area. Flight data that has been revised by the EAS or by the CD specialist will be highlighted, and the CD specialist may append the flight plan by including approved information prior to up linking the revised data.
3. Authority to Change This Order. The issuance, revision, or cancellation of the material in this order is the responsibility of AJV-P.
Appendix A 4. Suggestions for Improvements. Please forward all comments on deficiencies, clarifications, or improvements regarding the contents of this order to [email protected].
Appendix A. Administrative Information › 5. Records Management.
Your suggestions are welcome. FAA Form 1320-19, Directive Feedback Information, is located in Appendix B of this order for your convenience.
5. Records Management. Refer to FAA Order 0000.1, FAA Standard Subject Classification System; FAA Order 1350.14, Records Management; or your office Records Management Officer (RMO)/Directives Management Officer (DMO) for guidance regarding retention or disposition of records.
g. Coordination. All matters pertaining to the PDC/CPDLC/TDLS of… › Appendix B. Directive Feedback Information
Appendix B
Appendix B. Directive Feedback Information
Please submit any written comments or recommendation for improving this directive, or suggest new items or subjects to be added to it. Also, if you find an error, please tell us about it.
Subject: FAA Order JO 7110.113G, Procedures for Issuing Automated Clearances
Please mark all appropriate line items:
An error (procedural or typographical) has been noted in paragraph … on page …
Recommend paragraph … on page … be changed as follows:
In a future change to this AC, please cover the following subject: (Briefly describe what you want added.)
Other comments:
I would like to discuss the above. Please contact me.
Submitted by: … Date: …
Telephone Number: … Routing Symbol: …
FAA Form 1320-19 (08/21)