Search NASASearch

Engineering topics

Conrad Rorie

Publications and source records attributed to Conrad Rorie.

At least 19 records

Pathfinding for Airspace with Autonomous Vehicles (PAAV) Tabletop 4 Report

NASA's Pathfinding for Airspace with Autonomous Vehicles (PAAV) sub-project investigates procedures and technologies to facilitate seamless integration of future UAS operations into the NAS. The Tabletop 4 activity solicited subject matter expertise to identify solutions to the potential challenges expected when the remote pilot-to-vehicle ratio scales from 1:1 to m:N, where one or more ground-based pilots control multiple uncrewed aircraft. This report details the method and results of the PAAV Tabletop 4 activity.

multi-vehicle operations

m:N and Human Autonomy Teaming Concepts for High Density Vertiport Operations

This report focuses on the role of the Fleet Manager (FM) and, in particular, the ways in which automation could support their position as they manage multiple aircraft and operators in a highly dynamic, advanced air mobility (e.g., air taxi) environment, specifically "high-density vertiport" (HDV) regions. Similar to terminal area operations for traditional aviation, operations involving HDVs will need to be highly structured while also remaining resilient to the various contingencies that can happen in that environment. The role of the FM is consistent with an “m:N” architecture, where “m” number of operators cooperatively manage “N” number of vehicles (where “N” is always larger than “m”). In such a paradigm it is critical to provide the operator with the tools and information necessary to manage their fleet safely and navigate the known pitfalls with highly automated, complex systems (e.g., brittleness, insufficient situation awareness, skill degradation). As the field of m:N has expanded as an area of study, a set of higher-level automation concepts have emerged—namely “plays,” “working agreements,” and “human-autonomy teaming” (HAT)—that could support operators in this new role.

human autonomy teaming

UAS Integration in the NAS Project: Overview of Flight Test Series 6

The National Aeronautics and Space Administration (NASA) Unmanned Aircraft Systems Integration in the National Airspace System (UAS-NAS) Project has conducted a series of flight test campaigns intended to support the reduction of barriers that prevent unmanned aircraft from flying without the required waivers from the Federal Aviation Administration (FAA). The 2019 Flight Test Series 6 (FT6) campaign furthered this path and supported three test configurations: 1) Radar Characterization, 2) Scripted Encounters and 3) Full Mission. Radar Characterization assessed the performance of Honeywell’s low size, weight, and power (low SWaP) radar system; Scripted Encounters investigated the timing of Detect and Avoid (DAA) alerting thresholds using a Department of Defense (DoD) Group 3 unmanned aircraft system (UAS) equipped with low SWaP sensors and three different live intruder aircraft flown at varying encounter geometries; and Full Mission validated human-in-the-loop simulations by collecting pilot performance data from a ground control station while controlling a live unmanned aircraft on a mission in both virtual and live air traffic controlled airspace. The subject pilot observed a research display that presented DAA advisories to maintain separation from live and virtual aircraft. The test was conducted over a twenty-week period within the R-2508 special use airspace located near Edwards Air Force Base (EAFB), CA. Over 240 encounters were flown during the test series and FT6 proved to be invaluable for the purposes of planning, managing, and executing this type of integrated flight test in both live and virtual environments. Data collected from FT6 was provided to the RTCA Special Committee 228 (SC-228) to help inform the Phase 2 Minimum Operational Performance Standards (MOPS). FT6 was the final test series for the UAS-NAS project that began in 2012. This paper provides an overview of FT6 and its success can be directly attributed to the diligent work of the men and women who supported this effort.

UAS in the NAS

A Framework for Assessment of Autonomy Challenges in Air Traffic Management

Traditionally, air traffic management services have been provided by air traffic controllers and managers stationed in ground facilities, employed or contracted by the public sector, and supported by automation. These centralized, human-centric air traffic management services do not scale to accommodate increasing demands from conventional and new entrant operations for access to the national airspace system. One transformation that provides much needed scalability is increasing the level of autonomy of air traffic management by enabling edge agents of the system, including vehicles, operators, and third-party service suppliers, to collectively self-manage independently from the centralized service providers and enabling the automation to also take on more independent traffic management responsibility from the human agents. This paper identifies challenges to increasing the level of autonomy of air traffic management services. It describes a framework to enable a systematic identification of these challenges. The framework consists of a functional breakdown of air traffic management services and several dimensions characterizing different autonomy scales. The autonomy dimensions include the automation level between human and machine agents, the locus of control between centralized and distributed edge agents, cognitive activities for autonomous situation awareness and decision making, intelligence levels ranging from skill-based to expertise-based autonomous behavior, and uncertainty levels of the dynamics and environment in which autonomous agents operate. Several challenges are identified and categorized using the different dimensions of the autonomy framework.

automation, autonomy framework, collective autonom

Display and Automation Considerations for the Airborne Collision Avoidance System Xu

In this presentation we examine several display and automation considerations of a collision avoidance system that is currently under development: the Airborne Collision Avoidance System (ACAS) Xu. This study builds on previous work conducted as part of NASA’s Unmanned Aircraft Systems (UAS) Integration into the National Airspace System (NAS) project. ACAS Xu represents the next-generation successor to the Traffic Alert and Collision Avoidance System (TCAS II), wherein the Xu variant is intended for UAS applications. Whereas TCAS II exclusively issues RAs in the vertical dimension, a major distinction between ACAS Xu and previous collision avoidance (CA) systems is the introduction of horizontal and “blended” RAs (i.e., RAs with both horizontal and vertical components). This present work was conducted as an engineering analysis involving two parts. In Part 1, a two-by-two, within-subjects study was performed that manipulated how RAs were presented to a pilot situated at a UAS ground control station. Five participants experienced four experimental trials in which text and aural alerting characteristics were manipulated. In Part 2, another five participants experienced four trials in which the levels of automation were manipulated with regard to the CA and return-to-course (RTC) tasks. The results for Part 1 found no effect of display or alerting configuration on pilot performance. However, it was discovered that pilot response time to RAs greatly depended on the RA type. In particular, pilots were quicker to respond to vertical RAs (M = 4.52 seconds) than horizontal (M = 7.42 seconds) and blended (M = 9.68 seconds) RAs in which both dimensions were issued simultaneously. For Part 2 of the study, pilots found both auto-CA and auto-RTC functions equally useful. Most pilots were comfortable with the automation, however responses were mixed. Three of five participants indicated high levels of comfort with the auto-CA function, while two rated their comfort as low. Pilots’ comfort for the auto-RTC functionality was slightly higher: four out of five pilots gave high ratings, while one pilot gave a low rating. Overall, pilots ordinally ranked their preference for automated functions as auto-CA together with auto-RTC (when an aural alert announces a change between CA and RTC states), auto-CA, and auto-CA and RTC (without the aural state-change announcement). Recommendations for improving the display of automation are also discussed.

collision avoidance

NASA-CAL Analytics Xr v1 Integration

This report documents the development and validation of the encounter set and the simulation results using ACAS Xr.

Advanced Air Mobility

Pathfinding for Airspace with Autonomous Vehicles (PAAV) + m:N Tabletop

The Pathfinding for Airspace with Autonomous Vehicles (PAAV) project is investigating how to integrate increasingly autonomous aircraft into the current air traffic management system. The project aims to help develop airspace procedures and technologies that are scalable to future autonomous operations. The purpose of this brief is to inform a working group on past and future PAAV efforts. The working group specializes in "m:N" operations, which refers to remote operations where one or more ground-based pilots cooperatively control multiple unmanned aircraft. The PAAV team will detail an upcoming tabletop exercise that is designed to elicit feedback from subject matter experts on current barriers to m:N operations for unmanned cargo operations and potential solutions to those obstacles. The working group will be given an opportunity to provide feedback on the objectives and methodology to be used in the PAAV tabletop exercise.

autonomous

m:N Working Group

The principles and reasons for employing Human Autonomy Teaming is discussed. Application of these techniques to multi-vehicle control is described. In several operational environments from small drone delivery to air taxi to autonomous cargo, many companies will need technologies that will allow for the operation of an unmanned aircraft (UAS or eVTOL) by a small crew of individuals that are located in a remote network operations center. That is, Multiple operators supervising an increasing Number of vehicles (M:N). This will require a new control/supervisory paradigm where the supervisors team with automation to achieve their joint tasks; Human Autonomy Teaming (HAT). This task will follow the HAT philosophy and tenants (e.g., trust, bi-directional communication, pilot directed interfaces). It will also develop and employ specific HAT tools (e.g., playbook, working agreements, predictive timeline displays, transparent interfaces to build trust). This presentation discusses the background and progress of the m:N working group.

multi-vehicle control

m:N Handoff Study

Explore the source record for details and available documents.

m:N operations

Streamlining Tactical Operator Handoffs During Multi-Vehicle Operations

Increased automation has shifted the operator control paradigm from a single operator controlling a single vehicle, to multiple operators collaborating to control multiple vehicles; this paradigm is known as m:N. Many questions remain unanswered in this new operational paradigm about the division of assets as workload for individual operators varies over time. This paper explores the management of workload by enabling operators to temporarily handoff vehicles among each other. A study was conducted to explore both a manual and assisted method for performing handoffs during manipulated contingency scenarios. The assisted handoff method allowed subjects to easily choose and group nominal and/or contingency vehicles. The number of contingencies was also manipulated to determine the effect workload had on how pilots utilized the ability to handoff vehicles. Results show subjects performed handoffs more often when there were more contingencies and when the assisted handoff tool was available. In addition, the assisted tool made subjects feel more comfortable, enabling them to feel like they could take longer to resolve contingency situations. Lastly, even during contingencies, subjects were able to successfully complete secondary tasks.

m:N operations

Integration of Automation Systems Flight Test Overview

This short presentation outlines an upcoming flight test to be performed as part of the Advanced Air Mobility (AAM) project. Referred to as the Integration of Automated Systems (IAS) flight test series, the objectives are to evaluate NASA research concepts and technologies for complex operations through integrated automation and candidate operational concepts and scenarios. The primary objective is to test mature AAM technologies in a relevant environment. The two primary systems under test are the Flight Path Management (FPM) and Hazard Perception and Avoidance (HPA) technology. This presentation focuses on the HPA technology developed by the FAA known as the Airborne Collision Avoidance System X for Rotorcraft (ACAS Xr) since the audience consists of committee members currently working on developing the minimum requirements for this system. The second half of the presentation explains the primary objectives and describes the scenarios expected to be tested in flight.

automation

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

Integration of Automated Systems (IAS) Flight Test - Hazard Perception & Avoidance (HPA) Results

The Integration of Automated Systems (IAS) flight test series concluded in October 2023 in support of NASA's Advanced Air Mobility (AAM) project. These flights include crewed, test (i.e., ownship) and traffic (i.e., intruder) aircraft that flew with unique technologies onboard. The presentation includes overviews of the flight tet itself and the specific results that pertain to the Hazard Perception and Avoidance (HPA) technical areas. HPA tested 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 were 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 remote pilots). Additionally, this system was flown in cruise and low-speed flight regimes as well as within en-route and (emulated), structured (i.e., dense/urban), and terminal airspaces. Results include the types of alerts generated by ACAS Xr across the different configurations, the distances at which the alerts were generated, response times, manuever sizes, miss distances, and general comments from pilots. Key takeaways and next steps are also provided.

detect and avoid

FT-01: Autonomous Helicopter Flight Testing Over Long Island Sound Special Session - Hazard Perception and Avoidance Tech Area

This presentation is included as part of a panel reporting on the Integration of Automated Systems (IAS) flight test series. The IAS series concluded in October 2023 and was conducted under NASA’s Advanced Air Mobility project and in partnership with Sikorsky and the Defense Advanced Research Projects Agency (DARPA). The flight test effort included two crewed rotorcraft platforms. The first, a modified S-76B helicopter, served as the “ownship” for the duration of the flight test. The second vehicle, a modified S-70, served as the intruder aircraft. One Sikorsky pilot and one NASA test pilot was onboard each aircraft for every test point, with the NASA test pilot responsible for interacting with the research systems under test. This portion of the panel presentation focuses on the results of the flight test that assessed the Federal Aviation Administration’s (FAA) next-generation collision avoidance system, the Airborne Collision Avoidance System X for Rotorcraft (ACAS Xr). The two configurations available within ACAS Xr – the Collision Avoidance System (CAS) configuration and the Detect and Avoid (DAA) configuration – were flown with an onboard pilot under Visual Flight Rules in controlled airspace over the Long Island Sound (Connecticut, USA). A total of 33 flight test cards were flown with ACAS Xr active. Results showed that the ACAS Xr alerting and guidance was largely effective and rated positively by the NASA test pilots, exemplified by zero instances of the pilots overriding an ACAS Xr Resolution Advisory (RA). Key areas of improvement, however, were noted, particularly with regards to the lack of an aural alert indicating a need to accelerate when receiving an RA at low speed and the occurrence of multiple RAs that the pilots found to be unacceptable.

detect and avoid