Planner/Executive Task Distribution
Background
CPDLC enables planners to assist executives by managing certain tasks.
Safety Issues
Miscommunication between controllers, especially during high workload periods, can lead to the executive controller making decisions based on incorrect information.
Typical Scenarios
Consider a scenario where the planner sends a clearance message to an aircraft to help resolve a conflict in heavy traffic. Meanwhile, the executive has identified the conflict and devised a different plan. If their plans do not align, corrective action may be necessary. In another situation, the planner responds to a pilot’s request and prematurely initiates a frequency change. The executive might then be unable to issue a last-minute clearance, potentially leading to a loss of separation at sector boundaries.
Defenses
Organizationally, clearly defining task distribution in the ATC Manual of Operations is essential. For controllers, planners should coordinate with executive controllers before sending messages or, if that isn’t feasible, promptly inform them afterward.
Less Communication on the Radio Frequency
Background
Using CPDLC helps free up radio frequencies and generally reduces miscommunication, especially due to similar callsigns.
Safety Issues
However, CPDLC can diminish pilots’ situational awareness since they cannot monitor data link communications between the controller and other aircraft.
Defenses
In situations involving multiple aircraft conflicts, voice communication may be preferred over CPDLC.
Long and Complex Messages
Background
CPDLC allows for the transmission of long and complex messages. This can reduce confusion since recipients don’t have to memorize requests or clearances.
Safety Issues
Nevertheless, if a clearance can only be partially fulfilled, the response will be “unable,” which raises workload. Additionally, lengthy messages are more prone to ambiguity.
Defenses
In general, it’s advisable to avoid using complex messages, even if the system permits it.
Not Clear Definition of “Time-Critical”
Background
CPDLC should only be utilized in non-time-critical situations.
Safety Issues
However, there is no strict definition of what constitutes “time-critical.” Different interpretations can lead to unexpected situations becoming urgent. For example, if a controller instructs a pilot to descend at a specific rate via CPDLC, but the pilot delays their response, the situation may turn critical, risking safety.
Defenses
Controller instructions usually include time reserves to accommodate pilot response and execution transitions. It’s crucial to extend this reserve, considering the response lag of CPDLC. If feasible, voice communication should be used instead.
Wrong Messages
Background
CPDLC makes it easier to send messages to aircraft compared to voice communication.
Safety Issues
This convenience also raises the risk of sending incorrect messages to the wrong aircraft.
Defenses
If a wrong uplink message occurs, controllers should quickly address the situation, ideally using voice communication to clarify the error.
Two Controllers
Background
CPDLC allows an aircraft to communicate with one ATS unit via voice while simultaneously being connected to another through CPDLC.
Safety Issues
Conflicting clearances from two different controllers can lead to misunderstandings, increased workloads, and even separation loss.
Defenses
Procedures may limit CPDLC use by controllers, such as requiring initial voice contact before using CPDLC.
Wrong Interpretation of Messages
Background
Pilots may sometimes misinterpret messages, resulting in unexpected actions.
Typical Scenarios
For instance, the message “WHEN CAN YOU ACCEPT FL [XXX]” is a request for the pilot to indicate their capability to climb. However, it could be misinterpreted as a clearance to ascend. Similarly, the instruction “CLEARED TO [POINT] VIA [ROUTE]” requires adherence to a specified route, yet a pilot might interpret it as permission to fly directly to the point.
Safety Issues
Misinterpretations can lead to various issues, including altitude busts and airspace infringements.
Defenses
Pilots should carefully read uplink messages and seek clarification when unsure. Controllers should monitor aircraft behavior closely and time messages to minimize adverse outcomes.
Accidents and Incidents
Several events have seen CPDLC as a contributing factor. For example, on September 14, 2022, a Boeing 787-9 inbound to Mumbai lost separation from another 787-8 on the same airway due to a descent without clearance. The situation escalated when the 787-9 descended to a level where it nearly collided with the other aircraft, highlighting the importance of effective communication and adherence to protocols.
