Search NASA⌕ Search

SEARCH · Search NASA

Results for “ground control stations”

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 109 records · Page 6

Information Displays and Crew Configurations for UTM Operations

In this paper we discuss how team configuration may influence how infor-mation is shared among team members for low-altitude Unmanned Aircraft Systems (UAS) operations. NASA collected and analyzed observation data gathered during a series of field tests for the UAS Traffic Management (UTM) project. The field tests were part of a larger effort aimed at advancing the UTM concept, conducted at six test-sites spread across the USA. Ground control station (GCS) concepts, flight-crew composition, and crew-size var-ied within and across test-sites. Flight crews took two strategic approaches to organizing their teams. The first of the two approaches was implemented by one third of the flight crews. These crews integrated the role of UTM opera-tor into the duties of existing crew members, merging the current roles with this new one, keeping the UTM Operator collocated with the flight crew. The remaining two thirds implemented a distributed team configuration, where a single UTM operator distributed support across multiple crews. Results from our data collection efforts revealed that UTM Operator location influenced whether flight crews used verbal communication versus displays to acquire UTM information.

teams↗

NASA Phase 2 DAA HITL Schedule

This schedule discusses which HiTLs will be run and the timeframe for each event. This document also discusses system architecture and data flow. The simulation environments is also briefly addressed in the document including: the ground control station and the supported simulation software.

TCAS Interoperaability↗

Automatic Execution of Collision Avoidance and Return to Course Analysis (D.6.20) Experiment Review

This presentation details the experimental design for an upcoming engineering analysis of a mock version of the Airborne Collision Avoidance System (ACAS), specifically the 'Xu' variant, which is designed for unmanned aircraft platforms. As a component of the Unmanned Aircraft System (UAS) Integration into the National Airspace System (NAS) project, this engineering analysis intends to study aspects of ACAS Xu in two parts. In the first phase of the study, the display and alerting guidance for collision avoidance (CA) resolution advisories (RA) shown to pilots at a ground control station will be manipulated, varying in level of RA transparency and presentation of safe maneuver parameters. The second phase of the engineering analysis will examine pilots' response to increasing levels of automation in the tasks of collision avoidance and return-to-course (RTC).

Sadler, Garrett↗

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↗

TPSAS-NF1676L-14864-DND

Objective 1: Develop a research test-bed and database to provide data/proof of concept for Ground Control Station (GCS) NAS operations. Objective 2: Coordinate with standards organizations to develop human factors guidelines for GCS operation in the NAS.

Anna Trujillo↗

TPSAS-NF1676L-14989-DND

Objective 1: Develop a research test-bed and database to provide data/proof of concept for Ground Control Station (GCS) NAS operations. Objective 2: Coordinate with standards organizations to develop human factors guidelines for GCS operation in the NAS. Interest in UAS routine access: 1) Federal government – DHS, NOAA, Commerce, Interior, FBI, DOT 2) Military 3) Local governments – police, fire, port authority 4) Commercial – utilities, news agencies, private security, photographers, hobbyists

Anna Trujillo↗

Integration Test and Evaluation (IT&E) Flight Test Series 6 Live Virtual Constructive - Distributed Environment (LVC-DE) Test Report

The goals of the Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) (also UAS-NAS) Project are to reduce the barriers for UAS access and its integration into the NAS. The UAS-NAS project and industry stakeholders conducted a series of flight tests integrating technologies from the Modeling & Simulation (M&S), Human Systems Integration (HSI), and Communication and Control (C2), and Integration, Test & Evaluation (IT&E) research areas. The last of the flight test series, Flight Test Series 6 (FT6) was conducted in late 2019 and focused on evaluating the interaction of the airborne non-cooperative surveillance system and the Detect and Avoid (DAA) technology. The DAA system generated conflict alert and guidance for pilots using a Research Ground Control System (RGCS) to avoid intruder aircraft. The conflict alerting and guidance information was presented on the RGCS’s display using symbology developed by the human factors team. The objective of FT6 was to investigate the interoperability of Low Size, Weight, and Power (Low SWaP) sensors with the DAA alerting, guidance, and display requirements. To support this goal, the distributed test environments (DTE) were developed at Ames Research Center (ARC) and Armstrong Flight Research Center (AFRC) and securely linked over a Virtual Private Network (VPN). These environments took advantage of existing Live Virtual Constructive (LVC) technologies to support research observation at both Centers with the insertion of live UAS and manned intruder aircraft into a simulated NAS environment with Air Traffic Control (ATC) and constructive manned aircraft. The experiment was distributed between AFRC flight operations and research facilities and the Distributed Simulation Research Laboratory (DSRL) and Software Development Laboratory (SDL) in building N243 at ARC. The Air Traffic Controller and pseudo pilots operated from the DSRL and SDL, respectively, using the Multi-Aircraft Control System (MACS). The test subject and researchers operated from the Research Ground Control Station (RGCS) at AFRC using the Vigilant Spirit Control Station (VSCS) and associated DAA software and displays. Flight Operation for the unmanned aircraft (UA) and manned intruder traffic was conducted at AFRC. Virtual traffic was managed by ARC. Voice distribution was accomplished using a combination of disparate communication systems at ARC and AFRC. The purpose of this document is to record the development, design, and execution of activities in support of the FT6 efforts from the perspective of the ARC IT&E team. Furthermore, the Armstrong IT&E team has published a thorough FT6 Test Report, with emphasis on flight test support, facilities and vehicle development; this report complements the Armstrong report. Analysis of collected FT6 data will be conducted and reported by the M&S and HSI teams and will be published in separate reports.

UAS-NAS↗

Display and Automation Considerations for the Airborne Collision Avoidance System Xu

In this paper 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↗

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↗

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↗

Demonstration of A High-Fidelity Predictive/Preview Display Technique for Telerobotic Servicing in Space

A highly effective predictive/preview display technique for telerobotic servicing in space under several seconds communication time delay has been demonstrated on a large laboratory scale in May, 1993, involving the Jet Propulsion Laboratory as the simulated ground control station and, 2500 miles away, the Goddard Space Flight Center as the simulated satellite servicing set-up. The technique isbased on a high-fidelity calibration procedure that enables a high-fidelity overlay of 3-D graphics robot arm and object models over given 2-D TV camera images of robot arm and objects. Togenerate robot arm motions, the operator can confidently interact in real time with the graphics models of the robot arm and objects overlaid on an actual camera view of the remote work site. The technique also enables the operator to generate high-fidelity synthetic TV camera views showing motion events that are hidden in a given TV camera view or for which no TV camera views are available...

Bejczy, A. K.↗

m:N ConOps/R&R Remote Simulation

This presentation details the experimental design of an investigation of small unmanned aircraft system (sUAS) operations involving multiple vehicle management by a remote operator. The study is part of an ongoing effort to explore multiple vehicle control by multiple operators, i.e., the control of N vehicles by m operators (m:N operations). For this effort, NASA and collaborators have developed prototypes of a concept of operations (ConOps), roles and responsibilities (R&R) for operators and supervisors, and a ground control station (GCS), including software displays and interfaces. Participants in this study acted as the pilot-in-command of twelve aircraft flying pre-approved routes in a simulation of a food delivery operation utilizing sUAS in the San Diego, CA area. Each participant experienced four experimental trials. Twice within the course of each trial, participants were responsible for responding to a sudden, unanticipated, and high-priority contingency: an airspace restriction for sUAS operations known as a UAS Volume Reservation (UVR). Upon issuance of a UVR, pilots were expected to reroute affected vehicles around the airspace. The level of automation (LoA) and workload of the flight rerouting task were varied. The LoA was manipulated by providing reroute suggestions ("auto" condition) for aircraft or by requiring pilots to manually reroute ("manual" condition) affected vehicles. Workload was varied as a function of the number of vehicles affected by the UVR contingencies: 2 vehicles ("low workload" condition) versus 4 vehicles ("high workload" condition). Additionally, some vehicles required pilots to adjust for terrain conflicts while avoiding the UVR region. Due to the COVID-19 pandemic, in-person data collection for this study was not possible. Researchers adapted to this circumstance through the development of remote data collection protocol. Participants were able to view adapted GCS displays using the Microsoft Teams teleconferencing platform and responded to events by using a verbal protocol developed for the experiment. Using this protocol, participants provided instructions for actions to a researcher, referred to as the surrogate, to carry out on their behalf. This presentation describes the experiment design, including special details for remote data collection via a subject-surrogate configuration, and concludes with planned data analysis and results to be presented at a later date.

multi-UAS↗

A Cognitive Walkthrough of Multiple Drone Delivery Operations

Advances of early twenty-first century aviation and transportation technologies provide opportunities for enhanced aerial projects, and the overall integration of unmanned aircraft systems (UAS) into the National Airspace System (NAS) has applications across a wide range of operations. Through these, remote operators have learned to manage several UAS at the same time in a variety of operational environments. The present work details a component piece of an ongoing body of research into multi-UAS operations. Beginning in early 2020, NASA has collaborated with Uber Technologies to design and develop concepts of operations, roles and responsibilities, and ground control station (GCS) concepts to enable food delivery operations via multiple, small UAS (sUAS). A cognitive walkthrough was chosen as the method for data collection. This allowed information to be gathered from UAS subject matter experts (SMEs) that could further mature designs for future human-in-the-loop (HITL) simulations; in addition, it allowed information to be collected remotely during the stringent restrictions of the COVID-19 pandemic. Consequently, the described cognitive walkthrough activity utilized remote data collection protocols mediated through the usage of programs designed for presentation and telecommunications. Scenarios were designed, complete with airspace, contingencies, and remedial actions, to be presented to the SMEs. Information was collected using a combination of rating scales and open-ended questions. Results received from the SMEs revealed expected hazards, workloads, and information concerns inherent in the contingency scenarios. SMEs also provided insight into the design of GCS tools and displays as well as the duties and relationships of human operators (i.e., monitors) and automation (i.e., informers and flight managers). Implications of these findings are discussed.

unmanned aircraft systems↗

A Cognitive Walkthrough of Multiple Drone Delivery Operations

Advances of early twenty-first century aviation and transportation technologies provide opportunities for enhanced aerial projects, and the overall integration of unmanned aircraft systems (UAS) into the National Airspace System (NAS) has applications across a wide range of operations. Through these, remote operators have learned to manage several UAS at the same time in a variety of operational environments. The present work details a component piece of an ongoing body of research into multi-UAS operations. Beginning in early 2020, NASA has collaborated with Uber Technologies to design and develop concepts of operations, roles and responsibilities, and ground control station (GCS) concepts to enable food delivery operations via multiple, small UAS (sUAS). A cognitive walkthrough was chosen as the method for data collection. This allowed information to be gathered from UAS subject matter experts (SMEs) that could further mature designs for future human-in-the-loop (HITL) simulations; in addition, it allowed information to be collected remotely during the stringent restrictions of the COVID-19 pandemic. Consequently, the described cognitive walkthrough activity utilized remote data collection protocols mediated through the usage of programs designed for presentation and telecommunications. Scenarios were designed, complete with airspace, contingencies, and remedial actions, to be presented to the SMEs. Information was collected using a combination of rating scales and open-ended questions. Results received from the SMEs revealed expected hazards, workloads, and information concerns inherent in the contingency scenarios. SMEs also provided insight into the design of GCS tools and displays as well as the duties and relationships of human operators (i.e., monitors) and automation (i.e., informers and flight managers). Implications of these findings are discussed.

unmanned aircraft systems↗

Functional Allocation Approach for Separation Assurance for Remotely Piloted Aircraft

A functional analysis framework is employed with the objective of exploring the separation assurance function for the remotely piloted aircraft system. The architecture of the remotely piloted aircraft system—highlighting several of the component systems and the functions resident onboard the remotely piloted aircraft and in the ground control station—is described to provide the context for understanding the complexity of the said system for a detailed functional analysis. The interactions between the agents of the separation assurance function belonging to the air traffic service provider, remotely piloted aircraft system operator and remotely piloted aircraft are described. Separation assurance by air traffic control, remain well clear by the remotely piloted aircraft system and collision avoidance onboard the remotely piloted aircraft are briefly discussed. The functional analysis framework is illustrated by relating the agents to the actions of (a) acquiring the surveillance information, (b) checking for conflicts, (c) creating the solutions for resolving conflicts and (d) implementing the conflict resolution solutions. This example is offered as a template by which a more detailed functional analysis of this and other functions could be developed. The architecture of the remotely piloted aircraft system is described to aid this process.

functional analysis↗

Functional Allocation Approach for Separation Assurance for Remotely Piloted Aircraft

A functional analysis framework is employed with the objective of exploring the separation assurance function for the remotely piloted aircraft system. The architecture of the remotely piloted aircraft system—highlighting several of the component systems and the functions resident onboard the remotely piloted aircraft and in the ground control station—is described to provide the context for understanding the complexity of the said system for a detailed functional analysis. The interactions between the agents of the separation assurance function belonging to the air traffic service provider, remotely piloted aircraft system operator and remotely piloted aircraft are described. Separation assurance by air traffic control, remain well clear by the remotely piloted aircraft system and collision avoidance onboard the remotely piloted aircraft are briefly discussed. The functional analysis framework is illustrated by relating the agents to the actions of (a) acquiring the surveillance information, (b) checking for conflicts, (c) creating the solutions for resolving conflicts and (d) implementing the conflict resolution solutions. This example is offered as a template by which a more detailed functional analysis of this and other functions could be developed. The architecture of the remotely piloted aircraft system is described to aid this process.

Functional analysis↗

Usability Evaluation of Fleet Management Interface for High Density Vertiplex Environments

To meet the rising demand for an Advanced Air Mobility (i.e. urban and rural unmanned aircraft systems) ecosystem, NASA Aeronautics Research Mission Directorate (ARMD) is hosting a series of simulations and flight tests under the High Density Vertiplex sub-project (HDV). HDV aims to develop an integrated automation architecture to support terminal area flight operations. The HDV simulations and flight tests address safety, integration, and operational challenges, while integrated systems and software demonstrate design readiness, robustness, and interoperability. During the initial HDV simulation in 2021, a prototype traffic management tool developed by NASA called Fleet Management Interface (FMI) was tested. FMI was designed to introduce an advanced level of human-automation interaction to aid both Ground Control Station Operators (GCSOs) and Fleet Managers (FMs) in remotely managing flights under their ownership. In a human-in-the-loop simulation, a usability study was conducted with FMI to identify optimal approaches for displaying information for human operators using subjective measures of usability, workload, situation awareness, risk, and trust, along with qualitative feedback. This study consisted of task analysis in which GCSO and FM subjects used an Urban Air Mobility (UAM) environment to develop and execute a plan for two different traffic scenarios of remotely controlled vehicles. In each scenario, a controlled vehicle completed a takeoff, active flight, and landing sequence while automated traffic flew in the background at a rate of 20 operations per hour. In the first scenario, the controlled vehicle flew a nominal route with takeoff and landing at the same vertiport. In the second scenario, the controlled vehicle started on the nominal route, then diverted to an unplanned location mid-flight. Results showed that self-reported performance, usability, trust, and situation awareness ratings of FMI were moderately to strongly high. There were small differences between scenarios, with Scenario 2 being perceived as more unstable, complex, variable, risky, and potentially harmful than Scenario 1. Furthermore, participants described improvements that could be made to create a better user experience. For example, users would like greater configurability of the interface based on their personal information requirements, and they would like the opportunity to review routes before assigning them. The results from this study will inform future development of the FMI with the end goal of creating a reference automation tool for airspace management procedures in AAM. The FMI could be introduced as a potential way to reduce dependency on traditional air navigation services through increased automation in high density vertiplex environments.

vertiplex↗

Usability Evaluation of Fleet Management Interface for High Density Vertiplex Environments

To meet the rising demand for an Advanced Air Mobility (AAM) (i.e. urban and rural unmanned aircraft systems) ecosystem, the NASA Aeronautics Research Mission Directorate (ARMD) is hosting a series of simulations and flight tests under the High Density Vertiplex sub-project (HDV) to prototype and study the effectiveness AAM capabilities under various operational contexts. HDV aims to develop an integrated automation architecture to support terminal area flight operations. The HDV simulations and flight tests address safety, integration, and operational challenges, while integrated systems and software demonstrate design readiness, robustness, and interoperability. During the initial HDV simulation in 2021, a prototype traffic management tool developed by NASA called the Fleet Management Interface (FMI) was tested. FMI was designed to introduce an advanced level of human-automation interaction to aid both Ground Control Station Operators (GCSOs) and Fleet Managers (FMs) in remotely managing flights under their ownership. In a human-in-the-loop simulation, a usability study was conducted with the FMI to identify optimal approaches for displaying information to human operators using subjective measures of usability, workload, situation awareness, risk, and trust, along with qualitative feedback. This study consisted of task analysis in which GCSO and FM subjects used an Urban Air Mobility (UAM) environment to develop and execute a plan for two different traffic scenarios of remotely controlled vehicles. In each scenario, a remotely controlled vehicle completed a takeoff, active flight, and landing sequence while simulated traffic flew in the background at a rate of 20 operations per hour. In the first scenario, the controlled vehicle flew a nominal route with takeoff and landing at the same vertiport. In the second scenario, the controlled vehicle started on the nominal route, then diverted to an unplanned location mid-flight. Results showed that self- reported performance, usability, trust, and situation awareness ratings of FMI were moderately to strongly high. There were small differences between scenarios, with Scenario 2 being perceived as more unstable, complex, variable, risky, and potentially harmful than Scenario 1. Furthermore, participants described improvements that could be made to create a better user experience. For example, users suggested customizable interfaces to accommodate information display preferences, and the ability to review routes before assigning them. The results from this study will inform future development of the FMI with the end goal of creating a reference automation tool for airspace management procedures in AAM. The FMI could serve to reduce dependency on traditional air navigation services through increased automation in high density vertiplex environments.

Fleet manager↗