Search NASA⌕ Search

SEARCH · Search NASA

Results for “loss of well clear”

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 37 records · Page 2

Helicopter Pilot Assessments of the Airborne Collision Avoidance System XR With Automated Maneuvering

The Airborne Collision Avoidance System X (ACAS X) is a next-generation collision avoidance tool developed to support different aircraft types and operations. The rotorcraft variant – referred to as ACAS XR – is designed to accommodate existing helicopter platforms as well as in-development, electric vertical takeoff and landing concepts, which are critical to the emerging concept of operations referred to as Advanced Air Mobility. The fundamental role of ACAS XR is to provide Detect and Avoid (DAA) and/or Collision Avoidance (CA) protection against airborne traffic. DAA alerting and guidance in the context of ACAS XR is caution-level and “suggestive,” and is to be used by the pilot if, and when, they decide to maneuver against an identified threat to DAA “well clear.” The CA alerting, by contrast, is warning-level and “directive,” with the pilot required to comply with the associated guidance to prevent a predicted Near Midair Collision (NMAC). The CA alerts generated by ACAS XR are referred to as Resolution Advisories (RAs) consistent with previous CA systems. Unlike earlier CA systems, ACAS XR issues RAs in the horizontal and vertical dimensions as well as multi-axis RAs (referred to as “Blended” RAs). According to the Minimal Operational Performance Standards of DAA systems for Unmanned Aircraft Systems, maneuvers to comply with RAs may be automated, whereas maneuvers based on DAA alerting assume a manual response. The current study was a human-in-the-loop simulation that presented rotorcraft pilots with ACAS XR alerts and guidance in a fixed-base eVTOL simulator with varying levels of automation. Objective results showed that pilots complied with all RAs within the expected 5-second time window and responded to DAA alerts quicker than in earlier studies with ACAS XU. Pilots often made larger horizontal deviations during Manual RAs, but often favored vertical and blended maneuvers. No NMACs occurred, and losses of well clear were mainly attributed to the obligation of the pilots and system to maneuver only after the CA phase of the encounter had begun. Other losses were due to pilots’ noncompliance or disregard for ACAS XR’s alerting and guidance. Noncompliance with RAs most frequently occurred when pilots determined they were too close to the terrain to continue to follow Descend RAs, performing vertical maneuvers instead of following Horizontal RAs, or rejecting Horizontal RA updates because they felt that enough maneuvering had been performed. Subjectively, pilots found the DAA and RA alerting and guidance intuitive and useful for VFR helicopter operations. Slightly more pilots preferred the Automated RA condition to the Manual RA condition. Lastly, they also felt that ACAS led to occasional unsafe Descend RAs. Caveats and future implications are discussed.

eVTOL↗

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↗

Pilot Evaluation of a UAS Detect-and-Avoid System's Effectiveness in Remaining Well Clear

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. Regulators will establish minimum operating standards for DAA effectiveness, but different combinations of algorithms, displays and procedures could be used to meet those standards. The research presented in this paper indicates the effectiveness of the combined pilot-DAA system as a function of the DAA design requirements and provides data that may be used to model the behavior of pilots when employing such systems. Two simulations involving 21 professional unmanned aircraft system (UAS) pilots evaluated eight different DAA system designs in order to assess their ability to maintain the "well clear" separation standard, i.e., the state of maintaining a safe distance from other aircraft that would not normally cause the initiation of a collision avoidance maneuver by either aircraft. When the traffic display was integrated with the primary mission map directly in front of the pilot, there were fewer losses of well clear. Greater warning time provided to the pilot was strongly correlated with success in remaining well clear. Pilots' ability to separate from aircraft with cooperative and non-cooperative surveillance systems was nearly the same after accounting for the amount of alert time provided in each encounter, although the limited surveillance volume for the airborne-equipped aircraft meant alerts tended to occur later and therefore were more difficult to resolve.

detect-and-avoid↗

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.↗

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↗

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↗

Evaluating Alerting and Guidance Performance of a UAS Detect-And-Avoid System

A key challenge to the routine, safe operation of unmanned aircraft systems (UAS) is the development of detect-and-avoid (DAA) systems to aid the UAS pilot in remaining "well clear" of nearby aircraft. The goal of this study is to investigate the effect of alerting criteria and pilot response delay on the safety and performance of UAS DAA systems in the context of routine civil UAS operations in the National Airspace System (NAS). A NAS-wide fast-time simulation study was conducted to assess UAS DAA system performance with a large number of encounters and a broad set of DAA alerting and guidance system parameters. Three attributes of the DAA system were controlled as independent variables in the study to conduct trade-off analyses: UAS trajectory prediction method (dead-reckoning vs. intent-based), alerting time threshold (related to predicted time to LoWC), and alerting distance threshold (related to predicted Horizontal Miss Distance, or HMD). A set of metrics, such as the percentage of true positive, false positive, and missed alerts, based on signal detection theory and analysis methods utilizing the Receiver Operating Characteristic (ROC) curves were proposed to evaluate the safety and performance of DAA alerting and guidance systems and aid development of DAA system performance standards. The effect of pilot response delay on the performance of DAA systems was evaluated using a DAA alerting and guidance model and a pilot model developed to support this study. A total of 18 fast-time simulations were conducted with nine different DAA alerting threshold settings and two different trajectory prediction methods, using recorded radar traffic from current Visual Flight Rules (VFR) operations, and supplemented with DAA-equipped UAS traffic based on mission profiles modeling future UAS operations. Results indicate DAA alerting distance threshold has a greater effect on DAA system performance than DAA alerting time threshold or ownship trajectory prediction method. Further analysis on the alert lead time (time in advance of predicted loss of well clear at which a DAA alert is first issued) indicated a strong positive correlation between alert lead time and DAA system performance (i.e. the ability of the UAS pilot to maneuver the unmanned aircraft to remain well clear). While bigger distance thresholds had beneficial effects on alert lead time and missed alert rate, it also generated a higher rate of false alerts. In the design and development of DAA alerting and guidance systems, therefore, the positive and negative effects of false alerts and missed alerts should be carefully considered to achieve acceptable alerting system performance by balancing false and missed alerts. The results and methodology presented in this study are expected to help stakeholders, policymakers and standards committees define the appropriate setting of DAA system parameter thresholds for UAS that ensure safety while minimizing operational impacts to the NAS and equipage requirements for its users before DAA operational performance standards can be finalized.

UAS Detect-and-Avoid (DAA) System↗

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↗

Analysis of UAS DAA Alerting in Fast-Time Simulations without DAA Mitigation

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 for DAA alerting system performance. A recent study conducted using NASA's ACES (Airspace Concept Evaluation System) simulation capability begins to address questions surrounding the development of draft MOPS for DAA alerting systems. ACES simulations were conducted to study the performance of alerting systems proposed by the SC-228 DAA Alerting sub-group. Analysis included but was not limited to: 1) correct alert (and timeliness), 2) false alert (and severity and duration), 3) missed alert, and 4) probability of an alert type at the time of loss of well clear. The performance of DAA alerting systems when using intent vs. dead-reckoning for UAS ownship trajectories was also compared. The results will be used by SC-228 to inform decisions about the surveillance standards of UAS DAA systems and future requirements development and validation efforts.

alerting↗

UAS Air Traffic Controller Acceptability Study: Evaluating Detect and Avoid Technology and Communication Delays in Simulation - 2

This study evaluated the effects of communications delays and winds on air traffic controller ratings of acceptability of horizontal miss distances (HMDs) for encounters between Unmanned Aircraft Systems (UAS) and manned aircraft in a simulation of the Dallas-Ft. Worth (DFW) airspace. Fourteen encounters per hour were staged in the presence of moderate background traffic. Seven recently retired controllers with experience at DFW served as subjects. Guidance provided to the UAS pilots for maintaining a given HMD was provided by information from Detect and Avoid (DAA) self-separation algorithms (Stratway+) displayed on the Multi-Aircraft Control System. This guidance consisted of amber "bands" on the heading scale of the UAS navigation display indicating headings that would result in a loss of well clear between the UAS and nearby traffic. Winds tested were successfully handled by the DAA algorithms and did not affect the controller acceptability ratings of the HMDs. Voice communications delays for the UAS were also tested and included one-way delay times of 0, 400, 1200, and 1800 msec. For longer communications delays, there were changes in strategy and communications flow that were observed and reported by the controllers. The aim of this work is to provide useful information for guiding future rules and regulations applicable to flying UAS in the NAS. Information from this study will also be of value to the Radio Technical Commission for Aeronautics (RTCA) Special Committee 228 - Minimum Performance Standards for UAS.

Comstock, James R., Jr.↗

Encounter-Based Simulation Architecture for Detect-And-Avoid Modeling

This paper presents an encounter-based simulation architecture developed at NASA to facilitate flexible and efficient Detect and Avoid modeling in parametric or tradespace studies on large data sets. The basic premise of this tool is that large-scale input data can be reduced to a set of `canonical encounters' and that using the reduced data in simulations does not lead to loss of fidelity. A canonical encounter is specified as ownship and intruder flight portions potentially resulting in a loss of well clear along with a set of properties that characterize the encounter. The advantages of using canonical encounters include faster simulations, reduced memory footprint, ability to select encounters based on user-specified criteria, shared encounters across multiple teams, peer-reviewed encounters, and a better understanding of the input data set, to name a few.

MOPS↗

Unmitigated ACES Simulation Supporting Draft DAA MOPS Alerting

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 for DAA alerting system performance. A recent study conducted using NASA's ACES (Airspace Concept Evaluation System) simulation capability begins to address questions surrounding the development of draft MOPS for DAA alerting systems. ACES simulations were conducted to study the performance of an alerting scheme proposed by the SC-228 DAA Alerting sub-group. Analysis included but was not limited to: 1) correct alert (and their timeliness), 2) false alert (and their severity and duration), 3) missed alert, and 4) probability of an alert type at the time of loss of well clear. The results will be used by SC-228 to inform decisions about the alerting aspect of UAS DAA systems and future requirements development and validation efforts.

alerting↗

Encounter-Based Simulation Architecture for Detect and Avoid Modeling

This paper presents an encounter-based simulation architecture developed at NASA to facilitate flexible and efficient Detect and Avoid modeling in parametric or tradespace studies on large data sets. The basic premise of this tool is that large-scale input data can be reduced to a set of `canonical encounters' and that using the reduced data in simulations does not lead to loss of fidelity. A canonical encounter is specified as ownship and intruder flight portions potentially resulting in a loss of well clear along with a set of properties that characterize the encounter. The advantages of using canonical encounters include faster simulations, reduced memory footprint, ability to select encounters based on user-specified criteria, shared encounters across multiple teams, peer-reviewed encounters, and a better understanding of the input data set, to name a few.

MOPS↗

ACES Study of DAA-Mitigated UAS Operations SC-228 Requirements Sub Group

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. A recent study conducted using NASA's ACES (Airspace Concept Evaluation System) simulation capability begins to address questions surrounding the development of draft MOPS for DAA systems by assessing DAA performance in a NAS-wide context. ACES analyses were conducted to determine the impact of varying elements of UAS pilot performance and uncertainty mitigations on DAA system performance. Simulations were conducted with recorded cooperative and non-cooperative VFR (Visual Flight Rules) traffic to accurately model UAS encounters with other NAS traffic (ATC (Air Traffic Control) being responsible for separation with other IFR (Instrument Flight Rules) aircraft) and with roughly 25, 000 simulated UAS operations The number of Loss of Well Clear (LoWC) events were recorded across the range of independent variables: pilot response time, horizontal LoWC prediction buffer and horizontal LoWC resolution buffer. The number of LoWC events was compared to the unmitigated case (without the benefit of a DAA system) to determine the resultant risk-ratio for each of 8 simulation conditions. The parameter trades presented by the resultant DAA system performance (risk ratio) will be used by SC 228 to inform decisions about future requirements development and validation efforts.

Detect-and-Avoid↗

ACAS Xr Part Task Sim, Preliminary Experiment Design

In early 2022, the Human Autonomy Teaming Lab (NASA Ames Research Center) will conduct a manned, human-in-the-loop (HITL) simulation. This part task HITL will begin the lab’s Hazard Perception and Avoidance (HPA) technical work under NASA’s Advanced Air Mobility (AAM), Automated Flight and Contingency Management (AFCM) Sub-Project. The goals will be to assess levels of automation for manned, electric vertical takeoff and landing (eVTOL) aircraft. This simulation will test manual and automated Resolution Advisory (RA) responses and return-to-course (RTC) maneuvers for the first version of the Airborne Collision Avoidance System’s (ACAS) rotary-wing (Xr) variant. This will be conducted on a fixed-based simulator designed to fly eVTOL aircraft while maneuvering for intruding traffic. Variables for this study include levels of autonomy (i.e., manual and automated) as well as the types of alerts at the onset of conflicts (i.e., Corrective and RA). The data collected will include response times, losses of well clear, and maneuver sizes and durations as well as subjective ratings like acceptability, perceived workload, and meaningful human control. Additional details and future anticipations are also discussed.

air taxis↗

Hazard Perception & Avoidance (HPA): Part Task 1 - Results Outbrief

n April 2022, the Human Autonomy Teaming Lab (NASA Ames Research Center) conducted a manned, human-in-the-loop (HITL) simulation. This part task HITL began the lab’s Hazard Perception and Avoidance (HPA) technical work under NASA’s Advanced Air Mobility (AAM), Automated Flight and Contingency Management (AFCM) Sub-Project. The goals were to assess levels of automation for manned, electric vertical takeoff and landing (eVTOL) aircraft. This simulation tested manual and automated Resolution Advisory (RA) responses and return-to-course (RTC) maneuvers for the first version of the Airborne Collision Avoidance System’s (ACAS) rotary-wing (Xr) variant. This was conducted on a fixed-based simulator designed to fly eVTOL aircraft while maneuvering for intruding traffic. Variables for this study included levels of autonomy (i.e., manual and automated) as well as the types of alerts at the onset of conflicts (i.e., Corrective and RA). The data collected included response times, losses of well clear, and maneuver sizes and durations as well as subjective ratings like acceptability, and perceived workload. Additional details and future anticipations are also discussed.

air taxis↗

Assured Vehicle Automation 1 Sim - Results Outbrief

In early 2022, the Human Autonomy Teaming Lab (NASA Ames Research Center) conducted a manned, human-in-the-loop (HITL) simulation. This part-task HITL began the lab’s Hazard Perception and Avoidance (HPA) technical work under NASA’s Advanced Air Mobility (AAM), Automated Flight and Contingency Management (AFCM) Sub-Project. The results of that sim guided the objectives of the current study, which were to examine pilots’ use of the Airborne Collision Avoidance System (ACAS) rotorcraft variant (Xr) v2 in multiple phases of flight with two separate Xr Modes, fully leverage Xr v2 features (e.g., use radar altimeter data to inform low altitude Resolution Advisory [RA] behavior, utilize the ability to designate “terminal-area intruders,” and display airspeed-based Detect and Avoid [DAA] guidance), emulate a “Traffic Advisory” (TA), and present Xr in a higher-fidelity environment. Therefore, this study was conducted in the Vertical Motion Simulator, and the variables included Phase of Flight (En-route, Hover, and Approach) as well as ACAS Xr Mode (TA/RA and DAA). The data collected included response times, losses of well clear, and maneuver sizes and durations as well as subjective ratings like acceptability and usability. Additional details and future anticipations are also discussed.

air taxis↗

Hazard Perception & Avoidance (HPA), Assured Vehicle Automation 1 Simulation (AVA-1h) Results Outbrief

In late 2022, the Human Autonomy Teaming Lab (NASA Ames Research Center) conducted a manned, human-in-the-loop (HITL) simulation. This HITL was the lab’s second Hazard Perception and Avoidance (HPA) technical work under NASA’s Advanced Air Mobility (AAM), Automated Flight and Contingency Management (AFCM) Sub-Project. The goals were to assess detect and avoid technology for manned, electric vertical takeoff and landing (eVTOL) aircraft. This simulation tested Resolution Advisory (RA) responses and return-to-course (RTC) maneuvers for the second version of the Airborne Collision Avoidance System’s (ACAS) rotary-wing (Xr) variant. This was conducted at the center's Vertical Motion Simulator (VMS), on a motion-based platform, and was configured to fly eVTOL aircraft while maneuvering for intruding traffic. Variables for this study included ACAS Xr modes (i.e., TA/RA and DAA) and phases of flight (i.e., Cruise, Hover, and Approach). The data collected included response times, losses of well clear, and pilots' noncompliances to alerts and guidance as well as subjective ratings like acceptability and perceived workload. Additional details and future anticipations are also discussed.

ACAS Xr↗