En Route KUSA services deploying 2018- 2019. DO > Independently review, concur, and respond to all CPDLC messages. > Select LOAD prompt to insert the route amendment into the FMS, confirm and verify the route amendment is acceptable via SOP’s, then ensure cleared route is the active flight plan in the FMS. – En Route: Manually load Arrival/Transition if instructed – DCL: Confirm SID/TRANSITION from CPDLC clearance message and verify Runway During roll-out, to receive En Route CPDLC services, > If STANDBY selected follow with a ACCEPT/REJECT or WILCO/UNABLE response. logon to KUSA: > After take-off, if CPDLC service disconnects when departing > CPDLC En Route Pilot Request: Direct To Fix, from a CPDLC airport Altitude requests, lost comm VOICE CONTACT, Emergency messages > After take-off or on the ground if adequate datalink coverage is available, if departing from a non-CPDLC airport > Per SOP, when entering US-domestic airspace from adjacent DON'T external facility
> Don't use REQUEST CLEARANCE feature via CPDLC unless
required for operational reasons. All Initial DCL's are sent to the aircraft automatically. ALWAYS CLARIFY CLEARANCE VIA > Don't use ACARS ATS to request Departure Clearance VOICE IF THERE IS CONFUSION > Don’t use free text for CPDLC messaging. – Exception – Free Text is allowed for Emergency Messages
harris.com | #harriscorp FAA NextGen Data Communications Program CPDLC DCL (Departure Clearance)
U.S Domestic En Route CPDLC Services Currently In Deployment
For additional information visit the Data Communications Implementation Team (DCIT) website at: http://dcis.harris.com/en-route-cpdlc-site-activation-map
Harris is a registered trademark of Harris Corporation.