Search NASA⌕ Search

SEARCH · Search NASA

Results for “DAA Alerting Performance”

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.

66 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS2015

The Impact of Integrated Maneuver Guidance Information on UAS Pilots Performing the Detect and Avoid Task

The integrated human-in-the-loop (iHITL) simulation examined the effect of four different Detect-and-Avoid (DAA) display concepts on unmanned aircraft system (UAS) pilots' ability to maintain safe separation. The displays varied in the type and amount of guidance they provided to pilots. The study's background and methodology are discussed, followed by the 'measured response' data (i.e., pilots' end-to-end response time in reacting to traffic alerts on their DAA display). Results indicate that display type had a significant impact on how long pilot's spent interacting with the interface (i.e., edit times).

detect and avoid↗
NASA NTRS2015

Characteristics of a Well Clear Definition and Alerting Criteria for Encounters Between UAS and Manned Aircraft in Class E Airspace

Unmanned aircraft systems (UAS) will be required to equip with a detect-and-avoid (DAA) system in order to satisfy the federal aviation regulations to remain well clear of other aircraft. For a DAA system to satisfy the requirement to stay well clear of other airborne traffic, a quantitative definition of well clear needs to be defined and evaluated. This study investigates the implications of UAS using proposed well clear definitions as a separation standard for conducting operations in the National Airspace System (NAS). The first analysis considers three well clear definitions and presents the relative state conditions of intruder aircraft as they encroach upon the well clear boundary. The second analysis focuses on the definition of the alerting criteria needed to inform the UAS operator of a potential loss of well clear. All analyses are conducted in a NAS-wide fast-time simulation environment using UAS aircraft models, proposed UAS missions, and historical air defense radar data to populate the background traffic operating under visual flight rules. The results presented in this study inform the safety case, requirements development, and the operational environment for DAA minimum operational performance standards.

Safety↗
NASA NTRS2018

Detect and Avoid: Efforts from NASA's UAS Integration into the NAS Project

NASA's Unmanned Aerial Systems (UAS) integration into the National Air Space (NAS) project has been working closely with the FAA and RTCA Special Committee 228 to identify and break down barriers to UAS integration. A focus of this work is on detect and avoid (DAA) technologies. A pilot has responsibility to see and avoid other aircraft and to remain "well clear," using their best judgment (Federal Aviation Regulations (FAR) Sec. 91.113). For UAS to perform this function, the see function is replaced by sensors to detect the other aircraft. Secondly, the pilot judgment of well clear has to be replaced by a mathematical expression. For Phase 1 of this effort, a well clear violation was defined if all three of these conditions are true: a) the horizontal clearance is less than 4000 ft., and b) the vertical clearance is less than 450 ft., and c) the time to loss of well clear is less than 35 seconds. This definition was developed with a great deal of community input and testing to ensure interoperability with Air Traffic Control (ATC) and pilots of manned aircraft. Appropriate guidance, alerting and displays were developed to allow UAS, with the appropriate sensors, to effectively maintain well clear. This work contributed to FAA Technical Standard Orders: TSO-C211, Detect and Avoid and TSO-C212, ATAR for Traffic Surveillance. Phase 2 of this work extends the operational environment to include the terminal area and lesser capable aircraft that might not have the payload capability to carry the RADAR defined in Phase 1. This session reports on work from Phase 1 and initial work in Phase 2.

Detect and Avoid (DAA)↗
NASA NTRS2016

Defining the Collision Avoidance Region for DAA Systems

Unmanned aircraft systems (UAS) will be required to equip with a detect-­‐and-­‐avoid (DAA) system in order to satisfy the federal aviation regulations to maintain well clear of other aircraft, some of which may be equipped with a Traffic Collision Avoidance System (TCAS) to mitigate the possibility of mid-­‐air collisions. As such, the minimum operational performance standards (MOPS) for UAS DAA systems are being designed with TCAS interoperability in mind by a group of industry, government, and academic institutions named RTCA Special Committee-228 (SC-228). This document will discuss the development of the spatial-­‐temporal volume known as the collision avoidance region in which the DAA system is not allowed to provide vertical guidance to maintain or regain DAA well clear that could conflict with resolution advisories (RAs) issued by the intruder aircraft's TCAS system. Three collision avoidance region definition candidates were developed based on the existing TCAS RA and DAA alerting definitions. They were evaluated against each other in terms of their interoperability with TCAS RAs and DAA alerts in an unmitigated factorial encounter analysis of 1.3 million simulated pairs.

collision avoidance region↗
NASA NTRSDate not supplied

Integration of Automated Systems (IAS) Flight Test Overview

The Integration of Automated Systems (IAS) Project is conducting a series of 2023 flight tests supporting NASA's Advanced Air Mobility (AAM) and National Campaign efforts. These flights include crewed, test (i.e., ownship) and traffic (i.e., intruder) aircraft that will fly with unique technologies onboard. The presentation will include overviews of the Hazard Perception and Avoidance (HPA) and Flight Path Management (FPM) technical areas but will focus primarily on HPA. HPA will test the FAA's Airborne Collision Avoidance System X (ACAS X), a next-generation collision avoidance tool developed to support different aircraft types and operations. The rotorcraft variant, ACAS Xr, is designed to accommodate existing helicopter platforms and in-development, vertical takeoff and landing (VTOL) concepts, which are critical to the emerging AAM concept of operations. Two configurations of ACAS Xr will be examined: Collision Avoidance System (CAS, similar to the Traffic Collision Avoidance System [TCAS] II) and Detect and Avoid (DAA, previously developed to provide added situational awareness for uncrewed aircraft). Additionally, this system will be explored during cruise and low-speed flight as well as flights within en-route, structured (i.e., dense/urban), and terminal airspaces. Scripted flight conflicts will be conducted, and these conflicts will be mitigated through maneuvers that are manual (i.e., performed by the pilots) or automated (i.e., achieved by the cooperation of the program middleware and onboard ownship systems). Objective data will be collected involving system and pilot performance as well as pilot decisions; subjective data will include pilot opinions of ACAS Xr's alerting and guidance as well as the automated maneuvers.

detect and avoid↗
NASA NTRS2016

Flight Test Overview for UAS Integration in the NAS Project

The National Aeronautics and Space Administration is conducting a series of flight tests intended to support the reduction of barriers that prevent unmanned aircraft from flying without the required waivers from the Federal Aviation Administration. The most recent testing supported two separate test configurations. The first investigated the timing of Detect and Avoid (DAA) alerting thresholds using a radar-equipped unmanned vehicle and multiple live intruders flown at varying encounter geometries. The second configuration included a surrogate unmanned vehicle (flown from a ground control station, with a safety pilot on board) flying a mission in a virtual air traffic control airspace sector using research pilot displays and DAA advisories to maintain separation from live and virtual aircraft. The test was conducted over a seven-week span in the summer of 2015. The data from over 100 encounter sorties will be used to inform the RTCA Phase 1 Detect and Avoid and Command and Control Minimum Operating Performance Standards (MOPS) intended to be completed by the summer of 2016. Follow-on flight-testing is planned for the spring of 2016 to capture remaining encounters and support validation of the MOPS.

UAS↗
NASA NTRS2015

Java Architecture for Detect and Avoid Extensibility and Modeling

Unmanned aircraft will equip with a detect-and-avoid (DAA) system that enables them to comply with the requirement to "see and avoid" other aircraft, an important layer in the overall set of procedural, strategic and tactical separation methods designed to prevent mid-air collisions. This paper describes a capability called Java Architecture for Detect and Avoid Extensibility and Modeling (JADEM), developed to prototype and help evaluate various DAA technological requirements by providing a flexible and extensible software platform that models all major detect-and-avoid functions. Figure 1 illustrates JADEM's architecture. The surveillance module can be actual equipment on the unmanned aircraft or simulators that model the process by which sensors on-board detect other aircraft and provide track data to the traffic display. The track evaluation function evaluates each detected aircraft and decides whether to provide an alert to the pilot and its severity. Guidance is a combination of intruder track information, alerting, and avoidance/advisory algorithms behind the tools shown on the traffic display to aid the pilot in determining a maneuver to avoid a loss of well clear. All these functions are designed with a common interface and configurable implementation, which is critical in exploring DAA requirements. To date, JADEM has been utilized in three computer simulations of the National Airspace System, three pilot-in-the-loop experiments using a total of 37 professional UAS pilots, and two flight tests using NASA's Predator-B unmanned aircraft, named Ikhana. The data collected has directly informed the quantitative separation standard for "well clear", safety case, requirements development, and the operational environment for the DAA minimum operational performance standards. This work was performed by the Separation Assurance/Sense and Avoid Interoperability team under NASA's UAS Integration in the NAS project.

unmanned aircraft systems↗
NASA NTRS2018

Unmanned Aerial Systems (UAS) Integration into the National Airspace System (NAS)

NASA's Unmanned Aerial Systems (UAS) integration into the National Air Space (NAS) project has been working closely with the FAA and RTCA Special Committee 228 to identify and break down barriers to UAS integration. A focus of this work is on detect and avoid (DAA) technologies. A pilot has responsibility to see and avoid other aircraft and to remain "well clear," using their best judgment (Federal Aviation Regulations (FAR) Sec. 91.113). For UAS to perform this function, the see function is replaced by sensors to detect the other aircraft. Secondly, the pilot judgment of well clear has to be replaced by a mathematical expression. For Phase 1 of this effort, a well clear violation was defined if all three of these conditions are true: a) the horizontal clearance is less than 4000 ft., and b) the vertical clearance is less than 450 ft., and c) the time to loss of well clear is less than 35 seconds. This definition was developed with a great deal of community input and testing to ensure interoperability with Air Traffic Control (ATC) and pilots of manned aircraft. Appropriate guidance, alerting and displays were developed to allow UAS, with the appropriate sensors, to effectively maintain well clear. This work contributed to FAA Technical Standard Orders: TSO-C211, Detect and Avoid and TSO-C212, ATAR for Traffic Surveillance. Phase 2 of this work extends the operational environment to include the terminal area and lesser capable aircraft that might not have the payload capability to carry the RADAR defined in Phase 1. This session reports on work from Phase 1 and initial work in Phase 2.

UAS↗
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↗
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 NTRS2017

An Alternative Time Metric to Modified Tau for Unmanned Aircraft System Detect And Avoid

A new horizontal time metric, Time to Protected Zone, is proposed for use in the Detect and Avoid (DAA) Systems equipped by unmanned aircraft systems (UAS). This time metric has three advantages over the currently adopted time metric, modified tau: it corresponds to a physical event, it is linear with time, and it can be directly used to prioritize intruding aircraft. The protected zone defines an area around the UAS that can be a function of each intruding aircraft's surveillance measurement errors. Even with its advantages, the Time to Protected Zone depends explicitly on encounter geometry and may be more sensitive to surveillance sensor errors than modified tau. To quantify its sensitivity, simulation of 972 encounters using realistic sensor models and a proprietary fusion tracker is performed. Two sensitivity metrics, the probability of time reversal and the average absolute time error, are computed for both the Time to Protected Zone and modified tau. Results show that the sensitivity of the Time to Protected Zone is comparable to that of modified tau if the dimensions of the protected zone are adequately defined.

alert↗
NASA NTRS2017

An Alternative Time Metric to Modified Tau for Unmanned Aircraft System Detect And Avoid

A new horizontal time metric, Time to Protected Zone, is proposed for use in the Detect and Avoid (DAA) Systems equipped by unmanned aircraft systems (UAS). This time metric has three advantages over the currently adopted time metric, modified tau: it corresponds to a physical event, it is linear with time, and it can be directly used to prioritize intruding aircraft. The protected zone defines an area around the UAS that can be a function of each intruding aircraft's surveillance measurement errors. Even with its advantages, the Time to Protected Zone depends explicitly on encounter geometry and may be more sensitive to surveillance sensor errors than modified tau. To quantify its sensitivity, simulation of 972 encounters using realistic sensor models and a proprietary fusion tracker is performed. Two sensitivity metrics, the probability of time reversal and the average absolute time error, are computed for both the Time to Protected Zone and modified tau. Results show that the sensitivity of the Time to Protected Zone is comparable to that of modified tau if the dimensions of the protected zone are adequately defined.

UAS↗