Effects of Automation Error Bias on Dependence and Trust in Remotely Operated Air Vehicle Operations
Explore the source record for details and available documents.
SEARCH · Search NASA
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.
Explore the source record for details and available documents.
Urban Air Mobility (UAM) is a future mode of transportation that will require revolutionary new vehicle concepts and operations. One of the many challenges that these vehicles face is a complex flight control task in a challenging urban environment and in different flight regimes such as hover, forward flight as well as the transitions between both, with a focus on a low workload and minimum required pilot training. This paper discusses the development and evaluation of simplified vehicle operations concepts using representative aircraft models, controls, inceptors and displays. These four aspects are inseparably interconnected. This simplified vehicle operations concept will be evaluated by performing relevant operations within a realistic urban environment. Handling quality evaluations will be performed using modified Mission Task Elements, or Handling Quality Task Elements. This paper focuses on the initial development of controls, inceptors and displays.
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.
Launch vehicle operational flight trajectory for Saturn IB vehicle AS-202
There is disclosed a cloud computing control system for vehicle speed control and also for control of a vehicle in a platoon. The cloud computing control system determines a speed trajectory and neutral coasting command for a first vehicle of the platoon and a vehicle controller determines a reference speed for the first vehicle in response to the speed trajectory and the neutral coasting command, and is response to one or more vehicle specific factors associated with the first vehicle.
Some concepts towards the optimum movement of vehicles on highways are presented. It is stressed that in proper perspective, the private automobile is one element of several modes of transportation. The modal mix in the long run is determined by proper land use planning, population density, and historic growth patterns. Discussion investigates the two main interacting elements of the highway in the dynamic state: the roadway and the driver operated vehicle, noting that the inefficiencies of the system are caused by the uncoordinated and disassociated actions of the two elements. Also discussed are vehicle operations on streets, highways, and freeways, on board communication, control, and guidance, systems considerations and traffic management, and benefits of optimized vehicle operations on roadways.
The Saturn Launch Vehicle Operations Simulator (LVOS) was developed for NASA at Kennedy Space Center. LVOS simulates the Saturn launch vehicle and its ground support equipment. The simulator was intended primarily to be used as a launch crew trainer but it is also being used for test procedure and software validation. A NASA/contractor team of engineers and programmers implemented the simulator after the Apollo XI lunar landing during the low activity periods between launches.
This paper describes an intelligent propulsion control architecture that coordinates with the flight control to reduce the amount of pilot intervention required to operate the vehicle. Objectives of the architecture include the ability to: automatically recognize the aircraft operating state and flight phase; configure engine control to optimize performance with knowledge of engine condition and capability; enhance aircraft performance by coordinating propulsion control with flight control; and recognize off-nominal propulsion situations and to respond to them autonomously. The hierarchical intelligent propulsion system control can be decomposed into a propulsion system level and an individual engine level. The architecture is designed to be flexible to accommodate evolving requirements, adapt to technology improvements, and maintain safety.
This paper describes an intelligent propulsion control architecture that coordinates with the flight control to reduce the amount of pilot intervention required to operate the vehicle. Objectives of the architecture include the ability to: automatically recognize the aircraft operating state and flight phase; configure engine control to optimize performance with knowledge of engine condition and capability; enhance aircraft performance by coordinating propulsion control with flight control; and recognize off-nominal propulsion situations and to respond to them autonomously. The hierarchical intelligent propulsion system control can be decomposed into a propulsion system level and an individual engine level. The architecture is designed to be flexible to accommodate evolving requirements, adapt to technology improvements, and maintain safety.
The National Aeronautics and Space Administration is supporting research to develop a prototype remote vehicle operations center at Langley Research Center to explore current and future advanced air mobility operations using small unmanned aerial systems vehicles as surrogates for future, larger-scale passenger carrying vehicles. The prototype facility known as the Remote Operations for Autonomous Missions (ROAM) Unmanned Aerial Systems (UAS) Operations Center is being used to explore different roles and responsibilities of remote operators managing multiple autonomous vehicles, with the goal of exploring human-autonomy teaming concepts that enable m:N operations (i.e., m operators managing N vehicles). ROAM has developed into a world-class research, development, and technology (RD&T) environment that can support both the collection of human factors data and the command and control of remote vehicles in beyond visual line of sight conditions. ROAM provides a key capability to enable full end-to-end hardware- and human-in-the-loop simulation testing, connecting with simulated small-UAS and creating a seamless Live-Virtual-Constructive (LVC) environment. This report describes the development of the ROAM UAS Operations Center from concept through design, culminating in the current implementation at NASA’s Langley Research Center.
Apollo Saturn-204/LM-1 launch vehicle operational flight trajectory
AS-205/CSM-101 launch vehicle operational trajectory
In multi-vehicle aerial operation contexts, a single or several human operators (m) are responsible for managing multiple uncrewed vehicles (N). This is referred to as the m:N operational paradigm. When automation error occurs during m:N operations, especially if multiple vehicles exhibit automation error, a question is raised: What level of system globality will the error be attributed to? Globality refers to the levels within the conceptual hierarchy of a perceptual object. Significant costs could be incurred if the error is falsely attributed to a higher globality level than it should be (e.g., multiple groups of vehicles as opposed to a single vehicle), and those vehicles are subsequently subject to grounding and evaluation/maintenance. Likewise, it could be problematic if error is falsely attributed to a component (i.e., a lower globality level), resulting in ongoing, unsafe operation of vehicles that should be grounded or evaluated. Thus, to meet required safety standards and facilitate commercial viability, multi-vehicle operators must be capable of appropriately attributing the level of globality of automation error within the system they are responsible for.
The National Aeronautics and Space Administration is supporting research to develop a prototype remote vehicle operations center at Langley Research Center to explore current and future advanced air mobility operations using small unmanned aerial systems vehicles as surrogates for future, larger-scale passenger carrying vehicles. Data collected within the Remote Operations for Autonomous Missions (ROAM) Unmanned Aerial Systems (UAS) Operations Center will be used to explore different roles and responsibilities of remote operators managing multiple autonomous vehicles, with the goal of exploring human-autonomy teaming concepts that enable m:N operations (i.e., m operators managing N vehicles). ROAM has developed into a world-class research, development, and technology (RD&T) environment that can support both the collection of human factors data and the command and control of remote vehicles in beyond visual line of sight conditions. Presented in this paper is an overview of ROAM, with a focus on the design components that support human factors data collection and a review of initial usability results of the facility.
The National Aeronautics and Space Administration is supporting research to develop a prototype remote vehicle operations center at Langley Research Center to explore current and future advanced air mobility operations using small unmanned aerial systems vehicles as surrogates for future, larger-scale passenger carrying vehicles. Data collected within the Remote Operations for Autonomous Missions (ROAM) Unmanned Aerial Systems (UAS) Operations Center will be used to explore different roles and responsibilities of remote operators managing multiple autonomous vehicles, with the goal of exploring human-autonomy teaming concepts that enable m:N operations (i.e., m operators managing N vehicles). ROAM has developed into a world-class research, development, and technology (RD&T) environment that can support both the collection of human factors data and the command and control of remote vehicles in beyond visual line of sight conditions. Presented in this paper is an overview of ROAM, with a focus on the design components that support human factors data collection and a review of initial usability results of the facility.
A research and development (R&D) approach is proposed for developing and validating concepts and technologies to achieve vehicle autonomy goals of Advanced Air Mobility (AAM) through Simplified Vehicle Operations (SVO). The approach applies resilience-engineering and human-automation teaming (HAT) principles to a framework for defining vehicle-based functions for the management of missions and flight trajectories, focusing initially on the en route flight domain. To achieve the SVO goal of reducing pilot training requirements and thereby increasing the pilot pool for AAM, while at the same time promoting ever-safer operations, a framework for identifying essential functions is proposed. In this framework, functions are first categorized by high-level functional purpose (mission management, flightpath management, tactical operations, and vehicle control) and then subcategorized by attributes of resilient-performing systems (abilities to monitor, respond, learn, and anticipate). The categorization by functional purpose provides structure within which HAT designs can be holistically explored and total levels of human vs. automation responsibility can be varied. The subcategorization by resilient-system attributes provides a mechanism for capturing safety-critical functions that may not be codified in current operational procedures and training curricula, particularly those where humans proactively enhance safety in currently undocumented ways. An R&D approach consisting of seven strategies is proposed in which automation engineering and human-factors communities can collaborate in the research, development, and design of an SVO roadmap to enable the ambitious objectives of AAM.
Outline: Selected Historic Shuttle Operations Data; Shuttle Lessons Learned Recommendations for Lower Cost, Operationally Efficient Launch Vehicle Systems; Selected Expendable launch vehicle experiences; Past NASA Launch Vehicle Development Programs, Studies (1985 to present); Discussion: Suggested applications of NASA Lessons Learned to already-baselined contractor XS-1 Phase I concepts.
The current focus in the ongoing development of autonomous driving systems (ADS) for heavy duty vehicles is that of vehicle operational safety. To this end, developers and researchers alike are working towards a complete understanding of the operating environments and conditions that autonomous vehicles are subject to during their mission. This understanding is critical to the testing and validation phases of the development of autonomous vehicles and allows for the identification of both the nominal and edge case scenarios encountered by these systems. Previous work by the authors saw the development of a comprehensive scenario generation framework to identify an operating domain specification (ODS), or external and internal conditions an autonomous driving system can expect to encounter on its mission to form critical scenario groups for autonomous vehicle testing and validating using statistical patterns, clustering, and correlation. Continuing this prior work, this paper focuses on the generation of test cases based on the critical scenarios identified that can be used to prioritize either the most common nominal driving scenarios or the least common severe driving scenarios. These test cases can then be used validate, through simulation or real-world testing, the operating design domain (ODD) for a generalized driving mission and built upon to identify spatial and temporal impacts on the driving mission of an autonomous vehicle.