Validation of Minimum Display Requirements for a UAS Detect and Avoid System

The full integration of Unmanned Aircraft Systems (UAS) into the National Airspace System (NAS), a prerequisite for enabling a broad range of public and commercial UAS operations, presents several technical challenges to UAS developers, operators and regulators. A primary barrier is the inability for UAS pilots (situated at a ground control station, or GCS) to comply with Title 14 Code of Federal Regulations sections 91.111 and 91.113, which require pilots to see and avoid other aircraft in order to maintain well clear. UAS pilots removal from the flight deck of the aircraft necessitates the development of a UAS-specific system for detecting nearby traffic and displaying traffic information to the pilot to support their ability to maintain an objectively defined DAA well clear threshold from other aircraft. This new UAS-specific function of remaining DAA well clear is called traffic avoidance. The resulting Detect and Avoid (DAA) system, however, will be subject to a collection of requirements that manufacturers will be obligated to meet in order to certify their equipment. RTCA Special Committee 228 (SC-228), a consortium of representatives from government, industry and academia, is responsible for developing and documenting the Minimum Operational Performance Standards (MOPS) for UAS DAA systems. The present study is the final in a series of human-in-the-loop (HITL) experiments designed to explore and test the various display and alerting requirements being incorporated into the DAA MOPS. Whereas the prior DAA HITLs examined a wide variety of DAA display features and concepts, the current experiment aims to validate the latest minimum display requirements for Phase 1 of the DAA MOPS. Rather than test different display concepts, this study tests two configurations of a MOPS-compatible DAA display: a version that is integrated into the primary navigation and control display of the GCS and a version that is physically separated from the primary display. This manipulation tests the draft minimum requirement that allows the DAA traffic display to be a separate, or standalone, configuration. This type of configuration is a more achievable near-term technology solution since it does not stipulate additional certification or integration requirements on UAS manufacturers. However, a standalone display configuration has the potential to result in pilot performance issues resulting from the cognitive costs of switching between the primary DAA display and the primary navigation and control display. This configuration is also particularly susceptible to errors if the displays are in different orientations (e.g., north-up versus track-up). Both the integrated and standalone display configurations were presented to 16 active UAS pilots in a medium-fidelity simulation, which included confederate air traffic controllers and pseudo pilots operating simulated manned traffic. Pilots were tasked with navigating two different mission routes while maintaining DAA well clear with scripted conflicts. Pilot response times (i.e., measured response) and ability to remain DAA well clear are reported. Primary results indicate that both display configurations resulted in favorable response times and well clear rates. While there were clear trends of pilots objectively performing better in the integrated display condition, with several measured response metrics reaching statistical significance, the differences between the two displays were typically moderate. While the primary variable of DAA display location did not have an especially large impact on pilot performance on its own, when examined alongside the type of DAA threat the pilot was facing (a caution-level versus a warning-level alert), the response time benefits associated with the integrated display were amplified. The implications of these American Institute of Aeronautics and Astronautics 2 results on the Phase 1 DAA MOPS and the connection of this data to previous studies is also discussed