Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “DAA”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRS2018

An Exploratory Evaluation of UAS Detect and Avoid Operations in the Terminal Environment

New technical standards for Unmanned Aircraft Systems (UAS) detect and avoid (DAA) systems mark recent progress toward realizing the goal of full integration of UAS into the National Airspace System (NAS). The DAA system is intended to provide a means of compliance with operating regulations that required pilots on board manned aircraft to remain "well clear" of other aircraft which is accomplished through out-the-window visual acquisition of other aircraft and application of a subjective judgment of safe separation. The requirements for the DAA system, including the specification of a DAA well clear threshold as well as functional requirements for detecting, tracking, alerting and guidance processing, and displays, are specified in DO-365, Minimum Operational Performance Standards (MOPS) for DAA Systems developed within RTCA Special Committee 228 (SC-228). Intended as the first in a series of phased versions, these requirements are frequently referred to as the "Phase 1" DAA system. The Phase 1 DAA system is limited for use by aircraft transitioning to and from Class A or special use airspace, through Class D, E, and G airspace. In particular, the Phase 1 DAA MOPS are not intended for terminal airspace operations, a critical gap for enabling a full range of UAS operations. The application of the Phase 1 DAA system and DAA well clear threshold within the terminal area is predicted to result in a high number of unnecessary alerts when the UAS is safely separated from other traffic. The goal of the present study was to examine pilot performance and operational issues related to the operation of the Phase 1 DAA system in a terminal area. This experiment was intended as an exploratory study that would be used to inform the development of a new terminal area-specific DAA well clear definition, and associated alerting and guidance requirements. The two main objectives of this study were to: 1) characterize pilot behavior in the terminal environment with the Phase 1 DAA system, and 2) investigate the effect of modifications to the Phase 1 DAA alerting and guidance structure. In particular, the authors were interested in determining whether the removal of specific alerting and guidance levels, without changing the DAA well clear definition or alerting thresholds, would impact pilot performance while conducting terminal operations. The results indicate that the Phase 1 well clear definition and alerting and guidance resulted in frequent alerting that degraded pilots' ability to discriminate between encounters where another aircraft was safely separated versus when a maneuver was necessary. The resulting impact on pilot performance was slower response times and higher frequency and severity of losses of DAA well clear compared to those observed for experiments examining pilot performance in the en route environment. There was no significant effect of alerting and guidance display configuration on pilot performance.

Rorie, Conrad↗
NASA NTRS2017

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.

detect and avoid↗
NASA NTRS2016

Piloted Well Clear Performance Evaluation of Detect and Avoid Systems with Suggestive Guidance

Regulations to establish operational and performance requirements for unmanned aircraft systems (UAS) are being developed by a consortium of government, industry and academic institutions (RTCA, 2013). Those requirements will apply to the new detect-and-avoid (DAA) systems and other equipment necessary to integrate UAS with the United States (U.S) National Airspace System (NAS) and will be determined according to their contribution to the overall safety case. That safety case requires demonstration that DAA-equipped UAS collectively operating in the NAS meet an airspace safety threshold (AST). Several key gaps must be closed in order to link equipment requirements to an airspace safety case. Foremost among these is calculation of the systems risk ratio, the degree to which a particular system mitigates violation of an aircraft separation standard (FAA, 2013). The risk ratio of a DAA system, in combination with risk ratios of other collision mitigation mechanisms, will determine the overall safety of the airspace measured in terms of the number of collisions per flight hour. It is not known what the effectiveness is of a pilot-in-the-loop DAA system or even what parameters of the DAA system most improve the pilots ability to maintain separation. The relationship between the DAA system design and the overall effectiveness of the DAA system that includes the pilot, expressed as a risk ratio, must be determined before DAA operational and performance requirements can be finalized. Much research has been devoted to integrating UAS into non-segregated airspace (Dalamagkidis, 2009, Ostwald, 2007, Gillian, 2012, Hesselink, 2011, Santiago, 2015, Rorie 2015 and 2016). Several traffic displays intended for use as part of a DAA system have gone through human-in-the-loop simulation and flight-testing. Most of these evaluations were part of development programs to produce a deployable system, so it is unclear how to generalize particular aspects of those designs to general requirements for future traffic displays (Calhoun, 2014). Other displays have undergone testing to collect data that may generalize to new displays, but have not been evaluated in the context of the development of an overall safety case for UAS equipped with DAA systems in the NAS (Bell, 2012). Other research efforts focus on DAA surveillance performance and separation standards. Together with this work, they are expected to facilitate validation of the airspace safety case (Park, 2014 and Johnson, 2015). The contribution of the present work is to quantify the effectiveness of the pilot-automation system to remain well clear as a function of display features and surveillance sensor error. This quantification will help enable selection of a minimum set of DAA design features that meets the AST, a set that may not be unique for all UAS platforms. A second objective is to collect and analyze pilot performance parameters that will improve the modeling of overall DAA system performance in non-human-in-the-loop simulations. Simulating the DAA-equipped UAS in such batch experiments will allow investigation of a much larger number of encounters than is possible in human simulations. This capability is necessary to demonstrate that a particular set of DAA requirements meets the AST under all foreseeable operational conditions.

detect and avoid↗
NASA NTRS2018

An Interoperability Concept for Detect and Avoid and Collision Avoidance Systems: Results from a Human-In-The-Loop Simulation

The integration of Unmanned Aircraft Systems (UAS) into the National Airspace System (NAS) poses a variety of technical challenges to UAS developers and aviation regulators. In response to growing demand for access to civil airspace in the United States, the Federal Aviation Administration (FAA) has produced a roadmap identifying key areas requiring further research and development. One such technical challenge is the development of a "detect and avoid" system (DAA) capable of providing a means of compliance with the "see and avoid" requirement in manned aviation. The purpose of the DAA system is to support the pilot, situated at a ground control station (GCS), in maintaining "DAA well clear" of nearby aircraft through the use of GCS displays and alerts. In addition to its primary function of aiding the pilot in maintaining DAA well clear, the DAA system must also safely interoperate with existing NAS systems and operations, such as the airspace management procedures of air traffic controllers (ATC) and Collision Avoidance (CA) systems currently in use by manned aircraft, namely the Traffic Alert and Collision Avoidance System (TCAS II). It is anticipated that many UAS architectures will integrate both a DAA system and a TCAS II. It is therefore necessary to explicitly study the integration of DAA and TCAS II alerting structures and maneuver guidance formats to ensure that pilots understand the appropriate type and urgency of their response to the various alerts. This paper presents a concept of interoperability for the two systems. The concept was developed with the goal of avoiding any negative impact on the performance level of TCAS II while retaining a DAA system that still effectively enables pilots to maintain DAA well clear. The interoperability concept described in the paper focuses primarily on facilitating the transition from a late-stage DAA encounter (where a loss of DAA well clear is imminent) to a TCAS II Corrective Resolution Advisory (RA), which requires pilot compliance within five seconds of its issuance. The interoperability concept was presented to 10 participants (6 active UAS pilots and 4 active commercial pilots) in a medium-fidelity, human-in-the-loop simulation designed to stress different aspects of the DAA and TCAS II systems. Pilots' ability to maintain separation, their rate of compliance and response times using the interoperability concept are reported. Results indicated that pilots exhibited comprehension of, and appropriate prioritization within, the DAA-TCAS II combined alert structure. Pilots demonstrated a high rate of compliance with TCAS II RAs and were also seen to respond to corrective RAs within the five second requirement established for manned aircraft. The DAA system presented under test was also shown to be effective in supporting pilots' ability to maintain DAA well clear in the overwhelming majority of cases in which pilots had sufficient time to respond.

Rorie, R. Conrad↗
NASA NTRS2016

FT4 Data Analysis Summary (SSI-ARC)

Standards for Unmanned Aircraft System (UAS) Detect-and-Avoid (DAA) systems are currently being developed under the auspices of the RTCA Special Committee 228 (SC-228). To support the development of these standards, a series of flight tests has been conducted at NASAs Armstrong Flight Research Center (NASA-AFRC). The fourth in this series of flight test activities (Flight Test 4, or simply FT4) was conducted during the Spring and Summer of 2016. FT4 supported the objectives of numerous organizations working toward UAS DAA Minimum Operational Performance Standards (MOPS) and UAS DAA Radar MOPS. The summary provided herein is limited to the objectives, analysis and conclusions of the NASA Ames Research Center (NASA-ARC) SSI team toward the refinement of UAS DAA MOPS. This document provides a high-level overview of FT4 and the SSI-ARC objectives, a summary of the data analysis methodology and recommendations for UAS DAA MOPS refinements based on the data analysis results. A total of 72 encounters were flown to support SSI-ARC objectives. Test results were generally consistent with acceptable UAS DAA system performance and will be considered in broader SC-228 requirements validation efforts. Observed alert lead times indicated acceptable UAS DAA alerting performance. Effective interoperability between the UAS DAA system and the Traffic Alert and Collision Avoidance System (TCAS) was observed with one notable exception: TCAS Resolutions Advisories (RA) were observed in the absence of any DAA alert on two occasions, indicating the need for alert parameter refinement. Findings further indicated the need for continued work in the areas of DAA Well Clear Recovery logic and alert stability for Mode-C-only intruders. Finally, results demonstrated a high level of compliance with a set of evaluation criteria designed to provide anecdotal evidence of acceptable UAS DAA system performance.

UAS Test Flight↗
NASA NTRS2016

Flight Test 4 Preliminary Results: NASA Ames SSI

Realization of the expected proliferation of Unmanned Aircraft System (UAS) operations in the National Airspace System (NAS) depends on the development and validation of performance standards for UAS Detect and Avoid (DAA) Systems. The RTCA Special Committee 228 is charged with leading the development of draft Minimum Operational Performance Standards (MOPS) for UAS DAA Systems. NASA, as a participating member of RTCA SC-228 is committed to supporting the development and validation of draft requirements as well as the safety substantiation and end-to-end assessment of DAA system performance. The Unmanned Aircraft System (UAS) Integration into the National Airspace System (NAS) Project conducted flight test program, referred to as Flight Test 4, at Armstrong Flight Research Center from April -June 2016. Part of the test flights were dedicated to the NASA Ames-developed Detect and Avoid (DAA) System referred to as JADEM (Java Architecture for DAA Extensibility and Modeling). The encounter scenarios, which involved NASA's Ikhana UAS and a manned intruder aircraft, were designed to collect data on DAA system performance in real-world conditions and uncertainties with four different surveillance sensor systems. Flight test 4 has four objectives: (1) validate DAA requirements in stressing cases that drive MOPS requirements, including: high-speed cooperative intruder, low-speed non-cooperative intruder, high vertical closure rate encounter, and Mode CS-only intruder (i.e. without ADS-B), (2) validate TCASDAA alerting and guidance interoperability concept in the presence of realistic sensor, tracking and navigational errors and in multiple-intruder encounters against both cooperative and non-cooperative intruders, (3) validate Well Clear Recovery guidance in the presence of realistic sensor, tracking and navigational errors, and (4) validate DAA alerting and guidance requirements in the presence of realistic sensor, tracking and navigational errors. The results will be presented at RTCA Special Committee 228 in support of final verification and validation of the DAA MOPS.

Detect-And-Avoid (DAA)↗
NASA NTRS2017

Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project: Advanced Collision Avoidance System for UAS (ACAS Xu) Interoperability White Paper Presentation

The Phase 1 DAA Minimum Operational Performance Standards (MOPS) provided requirements for two classes of DAA equipment: equipment Class 1 contains the basic DAA equipment required to assist a pilot in remaining well clear, while equipment Class 2 integrates the Traffic Alert and Collision Avoidance (TCAS) II system. Thus, the Class 1 system provides RWC functionality only, while the Class 2 system is intended to provide both RWC and Collision Avoidance (CA) functionality, in compliance with the Minimum Aviation System Performance (MASPS) for the Interoperability of Airborne Collision Avoidance Systems. The FAAs TCAS Program Office is currently developing Airborne Collision Avoidance System X (ACAS X) to support the objectives of the Federal Aviation Administrations (FAA) Next Generation Air Transportation System Program (NextGen). ACAS X has a suite of variants with a common underlying design that are intended to be optimized for their intended airframes and operations. ACAS Xu being is designed for UAS and allows for new surveillance technologies and tailored logic for platforms with different performance characteristics. In addition to Collision Avoidance (CA) alerting and guidance, ACAS Xu is being tuned to provide RWC alerting and guidance in compliance with the SC 228 DAA MOPS. With a single logic performing both RWC and CA functions, ACAS Xu will provide industry with an integrated DAA solution that addresses many of the interoperability shortcomings of Phase I systems. While the MOPS for ACAS Xu will specify an integrated DAA system, it will need to show compliance with the RWC alerting thresholds and alerting requirements defined in the DAA Phase 2 MOPS. Further, some functional components of the ACAS Xu system such as the remote pilots displayed guidance might be mostly references to the corresponding requirements in the DAA MOPS. To provide a seamless, integrated, RWC-CA system to assist the pilot in remaining well clear and avoiding collisions, several issues need to be addressed within the Phase 2 SC-228 DAA efforts. Interoperability of the RWC and CA alerting and guidance, and ensuring pilot comprehension, compliance and performance, will be a primary research area.

detect and avoid↗
NASA NTRS2019

A Comparison of Two Terminal Area Detect and Avoid Well Clear Definitions

Technical requirements are currently under development for a detect and avoid system (DAA) that would support the operation of Unmanned Aircraft Systems (UAS) within the National Airspace System (NAS). Such a system would aid UAS operators in maintaining sufficient separation, or "well clear", from other aircraft in their vicinity. The first set of technical standards for a UAS DAA system (referred to as "Phase 1" requirements) was limited to UAS operations transiting through Class D, E, and G airspace to, or from, Class A (or special-use) airspace. Explicitly out of scope of the Phase 1 requirements was the operation of UAS within terminal airspace in the NAS. Fern, Rorie, Roberts and Monk (2018) explored the application of a Phase 1 DAA system within Class D terminal airspace in a human-in-the-loop simulation. The results of the study demonstrated a poor fit of the Phase 1 DAA well clear (DWC) definition to these terminal operations. The original DWC definition was designed for the en-route environment and could not account for the complex, tightly-choreographed nature of traffic typically found near an airport. The interaction of the en-route DWC definition and the terminal area traffic led to excessive DAA alerting against safely-separated traffic. The frequent alerting quickly degraded pilots' ability to discriminate between encounters where a maneuver was or was not necessary. This resulted in slower response times, higher rates of losses of DAA well clear, and more severe losses of DAA well clear than had been observed in previous DAA research (e.g., Rorie et al., 2017). The current paper reports on a follow-on study to Fern et al. (2018) that tested two DWC definitions designed to accommodate standard terminal area operating procedures, such as traffic in the downwind leg of a VFR traffic pattern while the UAS is on final. The two definitions utilized identical horizontal and vertical thresholds but differed in whether or not Tau (a function that takes into account the closure rate of two aircraft) was included as a part of the DWC hazard zone. The "Tau" DWC candidate definition nominally extended the DWC hazard zone by 15 seconds in the direction of the intruder aircraft, while the "No Tau" DWC candidate definition did not extend the DWC hazard zone. The results of this follow-on study indicated that both candidate definitions improved pilot and DAA system performance relative to Fern et al (2018). Pilot response times and rates of losses of DWC returned to levels comparable to earlier research in the en-route environment. Several important differences between the two DWC candidate definitions, however, are also discussed.

Terminal Area↗
NASA NTRS2019

Detect-and-Avoid Alerting Performance for High-Speed UAS and Non-Cooperative Aircraft

This paper presents a set of experiments designed to assess the viability of using a smaller Detect and Avoid (DAA) volume for large Unmanned Aircraft Systems (UAS) when they are trying to remain well clear of non-cooperative visual flight rules (VFR) aircraft, in compliance with Federal regulations. The current DAA volume was defined for both cooperative and non-cooperative VFR traffic by the work of RTCA (Radio Technical Commission for Aeronautics) Special Committee 228 in 2017, in what is referred to in this paper as the Phase 1 standards. Subsequent work by the committee has been focused on enabling operations by smaller UAS that cannot carry the heavy radars required for the Phase 1 DAA Minimum Operational Performance Standards (MOPS). The work discussed in this paper will explore whether a Phase 1 UAS using a Phase 1 radar can use the reduced non-cooperative DAA alerting volume being studied for smaller, slower Phase 2 UAS without significantly degrading system safety. The study uses UAS models and background traffic from previous Phase 1 and Phase 2 research to run an unmitigated simulation that will examine alerting performance using different DAA well clear definitions. The primary metrics are also tied to the alerting performance of the DAA system, and include average alerting times, probabilities of missed and late alerts, and the probability of a near mid-air collision given a loss of "well clear," as defined by the DAA system. Results are expected to help RTCA make the determination whether or not the DAA well clear definition for Phase 1 UAS can be reduced for non-cooperative VFR aircraft.

UAS↗
NASA NTRS2017

Unmanned Aircraft Systems Minimum Operations Performance Standards End-to-End Verification and Validation (E2-V2) Simulation

As Unmanned Aircraft Systems (UAS) make their way to mainstream aviation operations within the National Airspace System (NAS), research efforts are underway to develop a safe and effective environment for their integration into the NAS. Detect and Avoid (DAA) systems are required to account for the lack of "eyes in the sky" due to having no human on-board the aircraft. The current NAS relies on pilot's vigilance and judgement to remain Well Clear (CFR 14 91.113) of other aircraft. RTCA SC-228 has defined DAA Well Clear (DAAWC) to provide a quantified Well Clear volume to allow systems to be designed and measured against. Extended research efforts have been conducted to understand and quantify system requirements needed to support a UAS pilot's ability to remain well clear of other aircraft. The efforts have included developing and testing sensor, algorithm, alerting, and display requirements. More recently, sensor uncertainty and uncertainty mitigation strategies have been evaluated. This paper discusses results and lessons learned from an End-to-End Verification and Validation (E2-V2) simulation study of a DAA system representative of RTCA SC-228's proposed Phase I DAA Minimum Operational Performance Standards (MOPS). NASA Langley Research Center (LaRC) was called upon to develop a system that evaluates a specific set of encounters, in a variety of geometries, with end-to-end DAA functionality including the use of sensor and tracker models, a sensor uncertainty mitigation model, DAA algorithmic guidance in both vertical and horizontal maneuvering, and a pilot model which maneuvers the ownship aircraft to remain well clear from intruder aircraft, having received collective input from the previous modules of the system. LaRC developed a functioning batch simulation and added a sensor/tracker model from the Federal Aviation Administration (FAA) William J. Hughes Technical Center, an in-house developed sensor uncertainty mitigation strategy, and implemented a pilot model similar to one from the Massachusetts Institute of Technology's Lincoln Laboratory (MIT/LL). The resulting simulation provides the following key parameters, among others, to evaluate the effectiveness of the MOPS DAA system: severity of loss of well clear (SLoWC), alert scoring, and number of increasing alerts (alert jitter). The technique, results, and lessons learned from a detailed examination of DAA system performance over specific test vectors and encounter cases during the simulation experiment will be presented in this paper.

Ghatas, Rania W.↗
NASA NTRS2018

An Interoperability Concept for Detect and Avoid and Collision Avoidance Systems: Results from a Human-In-The-Loop Simulation

The integration of Unmanned Aircraft Systems (UAS) into the National Airspace System (NAS) poses a variety of technical challenges to UAS developers and aviation regulators. In response to growing demand for access to civil airspace in the United States, the Federal Aviation Administration (FAA) has produced a roadmap identifying key areas requiring further research and development. One such technical challenge is the development of a "detect and avoid" system (DAA) capable of providing a means of compliance with the "see and avoid" requirement in manned aviation. The purpose of the DAA system is to support the pilot, situated at a ground control station (GCS), in maintaining "DAA well clear" of nearby aircraft through the use of GCS displays and alerts. In addition to its primary function of aiding the pilot in maintaining well clear, the DAA system must also safely interoperate with existing NAS systems and operations, such as the airspace management procedures of air traffic controllers (ATC) and Collision Avoidance (CA) systems currently in use by manned aircraft, namely the Traffic alert and Collision Avoidance System (TCAS) II. It is anticipated that many UAS architectures will integrate both a DAA system and a TCAS II. It is therefore necessary to explicitly study the integration of DAA and TCAS II alerting structures and maneuver guidance formats to ensure that pilots understand the appropriate type and urgency of their response to the various alerts. This paper presents a concept of interoperability for the two systems. The concept was developed with the goal of avoiding any negative impact on the performance level of TCAS II while retaining a DAA system that still effectively enables pilots to maintain DAA well clear.

unmanned aircraft systems↗
NASA NTRS2019

Detect-and-Avoid Alerting Performance for High-Speed UAS and Non-Cooperative Aircraft

This paper presents a set of experiments designed to assess the viability of using a smaller Detect and Avoid (DAA) volume for large Unmanned Aircraft Systems (UAS) when they are trying to remain well clear of non-cooperative visual flight rules (VFR) aircraft, in compliance with Federal regulations. The current DAA volume was defined for both cooperative and non-cooperative VFR traffic by the work of RTCA Special Committee 228 in 2017, in what is referred to in this paper as the Phase 1 standards. Subsequent work by the committee has been focused on enabling operations by smaller UAS that cannot carry the heavy radars required for the Phase 1 DAA Minimum Operational Performance Standards (MOPS). The work discussed in this paper will explore whether a Phase 1 UAS using a Phase 1 radar can use the reduced non-cooperative DAA alerting volume being studied for smaller, slower Phase 2 UAS without significantly degrading system safety. The study uses UAS models and background traffic from previous Phase 1 and Phase 2 research to run an unmitigated simulation that will examine alerting performance using different DAA well clear definitions. The primary metrics are also tied to the alerting performance of the DAA system, and include average alerting times, probabilities of missed and late alerts, and the probability of a near mid-air collision given a loss of "well clear," as defined by the DAA system. Results are expected to help RTCA make the determination whether or not the DAA well clear definition for Phase 1 UAS can be reduced for non-cooperative VFR aircraft.

Cone, Andrew C.↗
NASA NTRS2019

A Detect and Avoid System in the Context of Multiple-Unmanned Aircraft Systems Operations

NASA's Unmanned Aircraft Systems Integration into the National Airspace System (UAS in the NAS) project examines the technical barriers associated with the operation of UAS in civil airspace. For UAS, the removal of the pilot from onboard the aircraft has eliminated the ability of the ground-based pilot in command (PIC) to use out-the-window visual information to make judgements about a potential threat of a loss of well clear with another aircraft. NASA's Phase 1 research supported the development of a Detect and Avoid (DAA) system that supports the ground-based pilot's ability to detect potential traffic conflicts and determine a resolution maneuver, but existing display/alerting requirements did not account for multiple UAS control (1:N). Demands for increased scalability of UAS in the NAS operations are expected to create a need for simultaneous control of UAs, and thus, a new DAA HMI design will likely be necessary. Previous research, however, has found performance degradations as the number of vehicles under operator control has increased. The purpose of the current human-in-the-loop (HITL) simulation was to examine the viability of 1:N operations with the Phase 1 DAA alerting and guidance. Sixteen UAS pilots flew three scenarios with varying number of UAs under their control (1:1, 1:3, 1:5). In addition to their supervisory and sensor mission responsibilities, pilots were to utilize the DAA system to remain DAA well clear (DWC) during scripted conflicts of mixed severity. Measured response times, separation performance, mission task data, and subjective feedback were collected to assess how the multi-UAS control configuration impacted pilots' ability to maintain DAA well clear and perform the mission tasks. Overall, the DAA system proved surprisingly adaptive to multi-UAS control for preventing losses of DAA well clear (LoDWC). The findings suggest that, while multi-UAS operators are able to maintain safe separation (DWC) from other traffic, their ability to efficiently perform missions drastically decreases with their number of controlled vehicles. Pilot feedback indicated that, for this context, the use of automation support tools for completing and managing mission tasks would be appropriate and desired, especially for ensuring efficient use of assets. Finally, human-machine interface (HMI) design considerations for multi-UAS operations are discussed.

Monk, Kevin J.↗
NASA NTRSDate not supplied

Assessing Helicopter Pilots’ Detect and Avoid and Collision Avoidance Performance With ACAS Xr

The latest variant of the Federal Aviation Administration’s Airborne Collision Avoidance System (ACAS X) is being designed for both crewed and uncrewed rotorcraft. Referred to as ACAS Xr, the system joins a suite of other ACAS X variants poised to replace the Traffic Alert and Collision Avoidance System (TCAS II). ACAS Xr is tuned to support current-day helicopter platforms as well as electric Vertical Takeoff and Landing (eVTOL) vehicles that are still under development. Given this flexibility, ACAS Xr may be used by helicopter crews currently in operation or by remotely-operated eVTOL aircraft in the emerging Advanced Air Mobility (AAM) market. To cover the range of potential uses, two distinct configurations are being proposed for ACAS Xr: Collision Avoidance System (CAS) and Detect and Avoid (DAA). Under the CAS configuration, ACAS Xr provides minimal caution-level alerting but issues directive warning-level alerting and guidance. The DAA configuration, by contrast, provides caution-level alerting and guidance, in addition to the warning-level alerting and guidance. The current study was performed as part of the National Aeronautics and Space Administration’s AAM project. Six helicopter pilots were recruited to fly a variety of scripted traffic scenarios in a full-motion, crewed eVTOL simulator. Participants flew 60 encounters over two days, reacting to pre-recorded intruder aircraft that were scripted to fly into the participant’s aircraft from different approach angles, relative altitudes, and during different phases of flight. The pilots flew half of the encounters with the CAS configuration and half with the DAA configuration. Within each block of 30 encounters, pilots experienced 10 conflicts while in cruise, 10 in hover, and 10 while on approach to a heliport. Results showed that pilot response times were consistently under 5 seconds for RAs and under 10 seconds for DAA alerts, when present, during all three phases of flight. Unsurprisingly, the DAA configuration was associated with lower rates of en-route and high-severity losses of DAA well clear compared to the CAS configuration in all phases of flight except for the terminal area. Rates of losses of DAA well clear were found to be substantially higher in the Hover scenario, compared to Cruise. Pilots failed to fully comply with RAs at a rate of 0.10-0.18 in all conditions except for the DAA configuration in the Hover scenario, which was associated with a higher non-compliance rate of 0.4 due to Descend RAs issued at low altitudes. The implications of these results with regards to the ongoing development of ACAS Xr is discussed.

air taxis↗
NASA NTRSDate not supplied

Assessing Helicopter Pilots’ Detect and Avoid and Collision Avoidance Performance with ACAS Xr

The latest variant of the Federal Aviation Administration’s Airborne Collision Avoidance System (ACAS X) is being designed for both crewed and uncrewed rotorcraft. Referred to as ACAS Xr, the system joins a suite of other ACAS X variants poised to replace the Traffic Alert and Collision Avoidance System (TCAS II). ACAS Xr is tuned to support current-day helicopter platforms as well as electric Vertical Takeoff and Landing (eVTOL) vehicles that are still under development. Given this flexibility, ACAS Xr may be used by helicopter crews currently in operation or by remotely-operated eVTOL aircraft in the emerging Advanced Air Mobility (AAM) market. To cover the range of potential uses, two distinct configurations are being proposed for ACAS Xr: Collision Avoidance System (CAS) and Detect and Avoid (DAA). Under the CAS configuration, ACAS Xr provides minimal caution-level alerting but issues directive warning-level alerting and guidance. The DAA configuration, by contrast, provides caution-level alerting and guidance, in addition to the warning-level alerting and guidance. The current study was performed as part of the National Aeronautics and Space Administration’s AAM project. Six helicopter pilots were recruited to fly a variety of scripted traffic scenarios in a full-motion, crewed eVTOL simulator. Participants flew 60 encounters over two days, reacting to pre-recorded intruder aircraft that were scripted to fly into the participant’s aircraft from different approach angles, relative altitudes, and during different phases of flight. The pilots flew half of the encounters with the CAS configuration and half with the DAA configuration. Within each block of 30 encounters, pilots experienced 10 conflicts while in cruise, 10 in hover, and 10 while on approach to a heliport. Results showed that pilot response times were consistently under 5 seconds for RAs and under 10 seconds for DAA alerts, when present, during all three phases of flight. Unsurprisingly, the DAA configuration was associated with lower rates of en-route and high-severity losses of DAA well clear compared to the CAS configuration in all phases of flight except for the terminal area. Rates of losses of DAA well clear were found to be substantially higher in the Hover scenario, compared to Cruise. Pilots failed to fully comply with RAs at a rate of 0.10-0.18 in all conditions except for the DAA configuration in the Hover scenario, which was associated with a higher non-compliance rate of 0.4 due to Descend RAs issued at low altitudes. The implications of these results with regards to the ongoing development of ACAS Xr is discussed.

air taxis↗
NASA NTRS2017

Maintain and Regain Well Clear: Maneuver Guidance Designs for Pilots Performing the Detect-and-Avoid Task

In order to support the future expansion and integration of Unmanned Aircraft Systems (UAS), ongoing research efforts have sought to produce findings that inform the minimum display information elements required for acceptable UAS pilot response times and traffic avoidance. Previous simulations have revealed performance benefits associated with DAA displays containing predictive information and suggestive maneuver guidance tools in the form of banding. The present study investigated the impact of various maneuver guidance display configurations on detect-and-avoid (DAA) task performance in a simulated airspace environment. UAS pilots ability to maintain DAA well clear was compared between displays with either the presence or absence of green DAA bands, which indicated conflict-free flight regions. Additional display comparisons assessed pilots ability to regain DAA well clear with two different guidance presentations designed to aid in DAA well clear recovery during critical encounters. Performance implications and display considerations for future UAS DAA systems are discussed.

unmanned aircraft systems (UAS)↗
NASA NTRS2017

Maintain and Regain Well Clear: Maneuver Guidance Designs for Pilots Performing the Detect-and-Avoid Task

In order to support the future expansion and integration of Unmanned Aircraft Systems (UAS), ongoing research efforts have sought to produce findings that inform the minimum display information elements required for acceptable UAS pilot response times and traffic avoidance. Previous simulations have revealed performance benefits associated with DAA displays containing predictive information and suggestive maneuver guidance tools in the form of banding. The present study investigated the impact of various maneuver guidance display configurations on detect-and-avoid (DAA) task performance in a simulated airspace environment. UAS pilots ability to maintain DAA well clear was compared between displays with either the presence or absence of green DAA bands, which indicated conflict-free flight regions. Additional display comparisons assessed pilots ability to regain DAA well clear with two different guidance presentations designed to aid in DAA well clear recovery during critical encounters. Performance implications and display considerations for future UAS DAA systems are discussed.

user interface design↗
NASA NTRS2021

UAS Integration in the NAS Flight Test 6: Full Mission Results

Recent standards development efforts for the integration of Unmanned Aircraft Systems (UAS) into the National Airspace System (NAS) such as those in RTCA Inc. Special Committee 228 (SC-228) have focused on relatively large UAS transitioning to and from Class A airspace. In an effort to expand the range of vehicle classes that can access the NAS, the NASA UAS Integration in the NAS project has investigated Low Size, Weight, and Power (Low SWaP) technologies that would allow smaller UAS to detect-and-avoid (DAA) traffic. Through batch and human in the loop (HITL) simulation studies, the UAS Integration in the NAS DAA subproject have identified candidate performance standards that would contribute to enabling extended Low SWaP, UAS operations under 10,000 feet. These candidate performance standards include minimum field of regard (FOR) values for Low SWaP air surveillance sensors as well as a DAA well-clear (DWC) definition which can be applied to non-cooperative traffic to reduce the required maneuver initiation range. To test the assumptions of the project’s simulation studies and validate the candidate performance standards, a live flight research event was executed at NASA Armstrong Flight Research Center. The UAS Integration in the NAS Project Flight Test 6 Full Mission sought to characterize UAS pilot responses to traffic conflicts using a representative Low SWAP DAA system in an operational NAS environment. To achieve this, live, virtual and constructive distributed environment (LVC-DE) elements were combined to simulate a sector of Oakland center airspace and induce encounters with a live, manned aircraft. A Navmar Applied Sciences Tigershark XP was used as the UAS ownship and was integrated into the test architecture to enable it to be controlled from a Vigilant Spirit Control Station (VSCS) research ground control station. Qualified UAS pilots were recruited to act as subject pilots under test (SPUT) to control the Tigershark XP in a simulated mission while coordinating with a participating air traffic controller in simulated airspace. The intruder speed, intruder equipage and encounter geometry were varied between six scripted encounters per SPUT. Various metrics were collected including pilot reaction time from the onset of DAA alert, ATC coordination rate, probability and severity of losses of DAA well clear, and subjective ratings of system acceptability. The implications of these results on the development of standards for Low SWAP DAA systems will be discussed.

UAV↗