Use of Free Text Messages
Description: The use of free text allows users to send messages.
Benefits: This feature provides greater flexibility and more options during non-standard situations, such as when radio communication is lost.
Issues: However, it also increases the chance of misunderstanding or ambiguity, particularly due to grammar or spelling mistakes.
Advice: If this feature is implemented, special training for staff is recommended to enhance language skills and system operation knowledge, focusing on how and when to use free text messages.
Use of Optional Messages
Description: There exists a list of standard yet optional messages, which can be included in the CPDLC system based on local implementation decisions.
Benefits: A broader set of available messages gives users more options.
Issues: However, a larger message set complicates system learning and operation, raises costs, and doesn’t guarantee that the other party will support the extended message set. A complex system is also more likely to experience stability issues.
Advice: Avoid blanket decisions like “All optional messages will be supported” or “No optional messages will be supported.” Instead, carefully consider all possible messages tailored to local needs.
Use of Complex Messages
Description: Technologically, it’s feasible to allow transmission of multi-element clearances and requests.
Benefits: This option provides more choices for controllers and pilots, allowing them to select between a multi-element message or several single-element messages.
Issues: If any part of a multi-element message cannot be fulfilled, a negative response applies to the entire message, leading to increased workload and potential for confusion. Ambiguity may arise if crews do not respond appropriately due to inadequate training.
Advice: Implement the option for complex messages only after a thorough analysis shows that benefits outweigh drawbacks. If included, ensure special staff training is conducted.
Transfer with Open Dialogues Within the Same Data Authority
Description: Open dialogues should be resolved when transferring control of an aircraft to a new data authority. For transfers between sectors within the same authority, open dialogues can be passed to the receiving sector.
Benefits: This facilitates seamless operations, eliminating the need for pilots to reissue requests or for controllers to repeat instructions, thus reducing workload, especially for controllers.
Issues: Poor coordination between sectors can lead to various undesired scenarios, such as loss of separation.
Advice: Use this option only after careful consideration, weighing the reduction in workload against the likelihood of human error. Special training is also advised if this option is implemented, as different procedures apply for inter-sector and inter-unit operations.
CPDLC Coverage
Description: CPDLC coverage determines how far from the unit boundary an aircraft can log on to the CPDLC system and is influenced by the equipment used.
Benefits: Enhanced coverage allows earlier log-on and quicker detection of equipment failures.
Issues: However, extending coverage increases costs for both initial development and ongoing maintenance.
Advice: Avoid unreasonable extensions of CPDLC coverage. Designers should focus on establishing minimum standard requirements.
Human-Machine Interface (HMI)
There are no strict guidelines for HMI, allowing for various approaches. Here are some general recommendations based on user experience:
-
Utilizing the aircraft (track) label for inputting CPDLC messages minimizes the risk of sending messages to the wrong aircraft.
-
Displaying the CPDLC status via the aircraft (track) label helps controllers monitor activities, detect failures early, and respond promptly to requests.
-
Creating a dedicated menu that includes all CPDLC features aids in familiarization with system capabilities and consolidates CPDLC-related tasks.
-
Most features should be accessible from multiple locations, such as a CPDLC menu for easy discovery and shortcuts for user convenience.
-
Implementing confirmation prompts before sending each message could help reduce errors, though it may increase workload and message exchange time.
