Results for “Automated decision support” — Page 6

NASA NTRS1982

Space applications of Automation, Robotics and Machine Intelligence Systems (ARAMIS). Volume 2: Space projects overview

Applications of automation, robotics, and machine intelligence systems (ARAMIS) to space activities, and their related ground support functions are studied so that informed decisions can be made on which aspects of ARAMIS to develop. The space project breakdowns, which are used to identify tasks ('functional elements'), are described. The study method concentrates on the production of a matrix relating space project tasks to pieces of ARAMIS.

Miller, R. H.↗

NASA NTRS1982

Space applications of Automation, Robotics and Machine Intelligence Systems (ARAMIS). Volume 4: Application of ARAMIS capabilities to space project functional elements

Applications of automation, robotics, and machine intelligence systems (ARAMIS) to space activities and their related ground support functions are studied, so that informed decisions can be made on which aspects of ARAMIS to develop. The specific tasks which will be required by future space project tasks are identified and the relative merits of these options are evaluated. The ARAMIS options defined and researched span the range from fully human to fully machine, including a number of intermediate options (e.g., humans assisted by computers, and various levels of teleoperation). By including this spectrum, the study searches for the optimum mix of humans and machines for space project tasks.

Miller, R. H.↗

NASA NTRS2001

En route Descent Advisor Concept for Efficient Arrival Metering Conformance

The En-route Descent Advisor (EDA) is a suite of decision support tool (DST) capabilities for en route sector subject to metering restrictions such as those generated by the Center TRACON Automation System (CTAS) Traffic Management Advisor. EDA assists controllers with high-density arrival metering by providing fuel-efficient metering-conformance advisories, integrated with conflict detection and resolution (CD&R) capabilities, to minimize deviations from the user s preferred trajectory. These DST capabilities will enable controllers to change their procedures from ones that are oriented towards sector management to procedures oriented towards trajectory management. Although adaptable to current procedures and airspace structure, EDA is intended as a tool for transitioning traffic from a Free Flight environment to an efficiently organized flow into terminal airspace. This paper describes the transition airspace problem and EDA concept, defines the key benefit mechanisms that will be enabled by EDA capabilities, and presents a traffic scenario to illustrate the use of the tool.

Green, Steven↗

NASA NTRS2022

UAM Research – X4: Introduction to Community Based Rules (CBRs)

Recent advances in technology have enabled industry development of new and innovative vehicle types, offering lower operating costs and highly automated functionality that facilitates the introduction of new types of operations. These include low-altitude airspace operations with small Unmanned Aircraft Systems (UASs), short distance urban and intercity operations, and high- altitude Upper Class E operations. These and other new operations are expected to result in a much higher operational tempo than is currently experienced across the National Airspace System (NAS). The projected increase in operations, as well as the introduction of new aircraft form factors and supporting technologies—including increasing autonomy—will present challenges to the existing Air Traffic Management (ATM) system, which is currently unable to cost-effectively scale and deliver needed services. In response to these challenges and opportunities, a highly automated, cooperative environment incorporating a federated network has been envisioned and described through multiple operational concepts, depicting the future operating environment as part of the NAS. Foundational to the success of this future operating environment is the establishment of common business rules and understandings across relevant stakeholders, referred to as Community Based Rules (CBRs). Development, adoption, and implementation of CBRs will require collaboration across multiple stakeholders, including operators, support services (industry), and the Federal Aviation Administration (FAA), to identify and resolve a broad range of questions and challenges. Examples of these questions include “what rules are needed?”, “how are they expressed?”, and “how will they be managed?” This document identifies and describes an initial set of questions and considerations to be examined as efforts begin to create the innovative, automated, cooperative operating environment of the future. The goal is to establish a common frame of reference to support discussions and decisions regarding the future implementation of CBRs as part of the NAS.

Community Based Rules↗

NASA NTRS1984

Remote sensing advances in agricultural inventories

As the complexity of the world's agricultural industry increases, more timely and more accurate world-wide agricultural information is required to support production and marketing decisions, policy formulation, and technology development. The Inventory Technology Development Project of the AgRISTARS Program has developed new automated technology that uses data sets acquired by spaceborne remote sensors. Research has emphasized the development of multistage, multisensor sampling and estimation techniques for use in global environments where reliable ground observations are not available. This paper presents research results obtained from data sets acquired by four different sensors: Landsat MSS, Landsat TM, Shuttle-Imaging Radar and environmental satellite (AVHRR).

Dragg, J. L.↗

NASA NTRS2017

Prototype Tool and Focus Group Evaluation for an Advanced Trajectory-Based Operations Concept

Trajectory-based operations (TBO) is a key concept in the Next Generation Air Transportation System transformation of the National Airspace System (NAS) that will increase the predictability and stability of traffic flows, support a common operational picture through the use of digital data sharing, facilitate more effective collaborative decision making between airspace users and air navigation service providers, and enable increased levels of integrated automation across the NAS. NASA has been developing trajectory-based systems to improve the efficiency of the NAS during specific phases of flight and is now also exploring Advanced 4-Dimensional Trajectory (4DT) operational concepts that will integrate these technologies and incorporate new technology where needed to create both automation and procedures to support gate-to-gate TBO. A TBO Prototype simulation toolkit has been developed that demonstrates initial functionality of an Advanced 4DT TBO concept. Pilot and controller subject matter experts (SMEs) were brought to the Air Traffic Operations Laboratory at NASA Langley Research Center for discussions on an Advanced 4DT operational concept and were provided an interactive demonstration of the TBO Prototype using four example scenarios. The SMEs provided feedback on potential operational, technological, and procedural opportunities and concerns. This paper describes an Advanced 4DT operational concept, the TBO Prototype, the demonstration scenarios and methods used, and the feedback obtained from the pilot and controller SMEs in this focus group activity.

Guerreiro, Nelson M.↗

NASA NTRS2017

An Advanced Trajectory-Based Operations Prototype Tool and Focus Group Evaluation

Trajectory-based operations (TBO) is a key concept in the Next Generation Air Transportation System transformation of the National Airspace System (NAS) that will increase the predictability and stability of traffic flows, support a common operational picture through the use of digital data sharing, facilitate more effective collaborative decision making between airspace users and air navigation service providers, and enable increased levels of integrated automation across the NAS. The National Aeronautics and Space Administration (NASA) has been developing trajectory-based systems to improve the efficiency of the NAS during specific phases of flight and is now also exploring Advanced 4-Dimensional Trajectory (4DT) operational concepts that will integrate these technologies and incorporate new technology where needed to create both automation and procedures to support gate-to-gate TBO. A TBO Prototype simulation toolkit has been developed that demonstrates initial functionality that may reside in an Advanced 4DT TBO concept. Pilot and controller subject matter experts (SMEs) were brought to the Air Traffic Operations Laboratory at NASA Langley Research Center for discussions on an Advanced 4DT operational concept and were provided an interactive demonstration of the TBO Prototype using four example scenarios. The SMEs provided feedback on potential operational, technological, and procedural opportunities and concerns. After viewing the interactive demonstration scenarios, the SMEs felt the operational capabilities demonstrated would be useful for performing TBO while maintaining situation awareness and low mental workload. The TBO concept demonstrated produced defined routings around weather which resulted in a more organized, consistent flow of traffic where it was clear to both the controller and pilot what route the aircraft was to follow. In general, the controller SMEs felt that traffic flow management should be responsible for generating and negotiating the operational constraints demonstrated, in cooperation with the Air Traffic Control System Command Center, while air traffic control should be responsible for the implementation of those constraints. The SMEs also indicated that digital data communications would be very beneficial for TBO operations and would result in less workload due to reduced communications, would eliminate issues due to language barriers and frequency problems, and would make receiving, loading, accepting, and executing clearances easier, less ambiguous, and more expeditious. This paper describes an Advanced 4DT operational concept, the TBO Prototype, the demonstration scenarios and methods used, and the feedback obtained from the pilot and controller SMEs in this focus group evaluation.

Guerreiro, Nelson M.↗

NASA NTRS2001

Noise Mitigation Controller Tools

During the past decade, the National Aeronautics and Space Administration (NASA) has been developing and evaluating a suite of decision support tools (DSTs) to aid the air traffic controller in the management of traffic. These tools are known collectively as the Center/TRACON Automation System (CTAS). The primary focus of CTAS is increased capacity. As part of a new NASA program called Quiet Aircraft Technology (QAT), the following question is being addressed: Can CTAS technology also support the noise mitigation requirements imposed by the community? Controllers currently support a variety of low noise procedures in low traffic densities but, as traffic increases, these must be abandoned due to excessive spacing requirements for vectoring or inter-arrival spacing requirements needed to handle a spectrum of low noise procedures. NASA is currently investigating how to provide controllers with noise-mitigation-based advisories which address these issues without negatively impacting capacity. These issues are of global concern which must be addressed as the demand for air travel continues to increase.

Tobias, Leonard↗

NASA NTRS2004

Data Management for Mars Exploration Rovers

Data Management for the Mars Exploration Rovers (MER) project is a comprehensive system addressing the needs of development, test, and operations phases of the mission. During development of flight software, including the science software, the data management system can be simulated using any POSIX file system. During testing, the on-board file system can be bit compared with files on the ground to verify proper behavior and end-to-end data flows. During mission operations, end-to-end accountability of data products is supported, from science observation concept to data products within the permanent ground repository. Automated and human-in-the-loop ground tools allow decisions regarding retransmitting, re-prioritizing, and deleting data products to be made using higher level information than is available to a protocol-stack approach such as the CCSDS File Delivery Protocol (CFDP).

Mars missions↗

NASA NTRS1994

Dual-Use Space Technology Transfer Conference and Exhibition, Volume 1

This document contains papers presented at the Dual-Use Space Technology Transfer Conference and Exhibition held at the Johnson Space Center February 1-3, 1994. Possible technology transfers covered during the conference were in the areas of information access; innovative microwave and optical applications; materials and structures; marketing and barriers; intelligent systems; human factors and habitation; communications and data systems; business process and technology transfer; software engineering; biotechnology and advanced bioinstrumentation; communications signal processing and analysis; new ways of doing business; medical care; applications derived from control center data systems; human performance evaluation; technology transfer methods; mathematics, modeling, and simulation; propulsion; software analysis and decision tools systems/processes in human support technology; networks, control centers, and distributed systems; power; rapid development perception and vision technologies; integrated vehicle health management; automation technologies; advanced avionics; ans robotics technologies. More than 77 papers, 20 presentations, and 20 exhibits covering various disciplines were presented b experts from NASA, universities, and industry.

Kumar Krishen↗

NASA NTRS1994

Dual-Use Space Technology Transfer Conference and Exhibition

This is the second volume of papers presented at the Dual-Use Space Technology Transfer Conference and Exhibition held at the Johnson Space Center February 1-3, 1994. Possible technology transfers covered during the conference were in the areas of information access; innovative microwave and optical applications; materials and structures; marketing and barriers; intelligent systems; human factors and habitation; communications and data systems; business process and technology transfer; software engineering; biotechnology and advanced bioinstrumentation; communications signal processing and analysis; medical care; applications derived from control center data systems; human performance evaluation; technology transfer methods; mathematics, modeling, and simulation; propulsion; software analysis and decision tools; systems/processes in human support technology; networks, control centers, and distributed systems; power; rapid development; perception and vision technologies; integrated vehicle health management; automation technologies; advanced avionics; and robotics technologies.

Krishen, Kumar↗

NASA NTRS1980

Decision making and problem solving with computer assistance

In modern guidance and control systems, the human as manager, supervisor, decision maker, problem solver and trouble shooter, often has to cope with a marginal mental workload. To improve this situation, computers should be used to reduce the operator from mental stress. This should not solely be done by increased automation, but by a reasonable sharing of tasks in a human-computer team, where the computer supports the human intelligence. Recent developments in this area are summarized. It is shown that interactive support of operator by intelligent computer is feasible during information evaluation, decision making and problem solving. The applied artificial intelligence algorithms comprehend pattern recognition and classification, adaptation and machine learning as well as dynamic and heuristic programming. Elementary examples are presented to explain basic principles.

Kraiss, F.↗

NASA NTRSDate not supplied

Gateway Autonomy for Enabling Deep Space Exploration

The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.

Molly Anderson↗

NASA NTRSDate not supplied

Gateway Autonomy for Enabling Deep Space Exploration

The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.

Molly Anderson↗

NASA NTRS1990

Human factors in spacecraft design

This paper describes some of the salient implications of evolving mission parameters for spacecraft design. Among the requirements for future spacecraft are new, higher standards of living, increased support of human productivity, and greater accommodation of physical and cultural variability. Design issues include volumetric allowances, architecture and layouts, closed life support systems, health maintenance systems, recreational facilities, automation, privacy, and decor. An understanding of behavioral responses to design elements is a precondition for critical design decisions. Human factors research results must be taken into account early in the course of the design process.

Harrison, Albert A.↗

NASA NTRS2010

Decision Engines for Software Analysis Using Satisfiability Modulo Theories Solvers

The area of software analysis, testing and verification is now undergoing a revolution thanks to the use of automated and scalable support for logical methods. A well-recognized premise is that at the core of software analysis engines is invariably a component using logical formulas for describing states and transformations between system states. The process of using this information for discovering and checking program properties (including such important properties as safety and security) amounts to automatic theorem proving. In particular, theorem provers that directly support common software constructs offer a compelling basis. Such provers are commonly called satisfiability modulo theories (SMT) solvers. Z3 is a state-of-the-art SMT solver. It is developed at Microsoft Research. It can be used to check the satisfiability of logical formulas over one or more theories such as arithmetic, bit-vectors, lists, records and arrays. The talk describes some of the technology behind modern SMT solvers, including the solver Z3. Z3 is currently mainly targeted at solving problems that arise in software analysis and verification. It has been applied to various contexts, such as systems for dynamic symbolic simulation (Pex, SAGE, Vigilante), for program verification and extended static checking (Spec#/Boggie, VCC, HAVOC), for software model checking (Yogi, SLAM), model-based design (FORMULA), security protocol code (F7), program run-time analysis and invariant generation (VS3). We will describe how it integrates support for a variety of theories that arise naturally in the context of the applications. There are several new promising avenues and the talk will touch on some of these and the challenges related to SMT solvers. Proceedings

Bjorner, Nikolaj↗

NASA NTRSDate not supplied

Flight Deck Design of a Hybrid Turbine/Electric Passenger Aircraft

NASA is exploring the development of a 180-passenger subsonic single engine aft turbine aircraft, The aft turbine provides electric power in a hybrid design to wing mounted electric engines, creating a highly efficient, high-bypass-ratio fan equivalent. The SUbsonic Single Aft eNgine (SUSAN) aircraft is being developed as a sustainable subsonic regional aircraft that seeks to reduce emission levels by 50% in the next few decades. Pilot-in-the-loop studies were conducted at the NASA Langley Research Center in Hampton, Virginia, to explore the flight deck design for the hybrid electric aircraft. Following modern trends in commercial aircraft flight decks with full time augmented controls and a quiet and dark philosophy, single throttle and simplified engine displays were developed for the SUSAN aircraft. The aircraft includes a single aft mounted turbine engine and 16 wing mounted electric fans. The final design was developed from feedback received during an earlier pilot-in-the-loop study where one, two, and three throttles were tested in standard airline operations, including various failures of the turbine and electric engines. Current flight deck designs normally provide control inceptors for each propulsion engine and an engine display for all primary aircraft engine parameters. With full time augmentation expected, a single throttle control with autothrottle always engaged, even during failures, is desired. Augmentation of flight controls using distributed thrust also requires full time control of the electric engines using automation. Additionally, electric engine thrust is augmented during climb based on battery state of charge. Thrust augmentation changes faster than human reaction time and therefore requires full-time automation. A pilot-in-the-loop study was conducted at the NASA Langley Research Center in Hampton, Virginia, to test the final design of the single throttle with simplified engine displays. Fourteen airline pilots evaluated the single throttle and engine display concept. Electric engine failures included one, four symmetric, and eight non-symmetric electric engine failures. The turbine engine was evaluated for complete and partial failure during critical phases of flight to include takeoff as well as enroute. Unexpected go-arounds increase workload and require significant throttle manipulation. Go-arounds were included to ensure the single throttle was usable for all phases of flight. Failures during takeoff required a return to the departure field and failures enroute required a diversion except for one and four electric engine failures as these failures did not affect aircraft flyability or range. There are currently no Part 25 aircraft certified with hybrid systems or electric engines with batteries as emergency propulsion. For turbine engine failures in the SUSAN aircraft design, range is limited to 30 minutes at full power. Battery state of charge and battery health displays were developed and tested for usability and to determine how well they supported pilot decisions for alternate airports during emergency diversions. Novel displays using shape and color were developed to provide immediate feedback when state of charge became critical. This paper details the pilot study including pilot feedback supporting the potential for increased automation and a single throttle control. Detailed recommendations are provided for a novel single throttle control and additional pilot controls to support selection of engines during start, shutdown, and engine troubleshooting procedures. This design deviates significantly from current practice of providing throttles for each propulsion engine. Engine display recommendations are provided based on pilot feedback during a guided post-evaluation interview. Battery state of charge and battery health display recommendations were collected from all airline crews. The simplified engine displays design was rated excellent as measured with a usability scale. Quantitative metrics include airspeed tracking, time to complete checklists, time to make diversion decisions and the quality of the diversion decision. Recommendations for future studies are documented with supporting research and current observations about upcoming flight deck certifications.

autothrottle↗

NASA NTRSDate not supplied

Flight Deck Design of a Hybrid Turbine/Electric Passenger Aircraft

NASA is exploring the development of a 180-passenger subsonic single engine aft turbine aircraft, The aft turbine provides electric power in a hybrid design to wing mounted electric engines, creating a highly efficient, high-bypass-ratio fan equivalent. The SUbsonic Single Aft eNgine (SUSAN) aircraft is being developed as a sustainable subsonic regional aircraft that seeks to reduce emission levels by 50% in the next few decades. Pilot-in-the-loop studies were conducted at the NASA Langley Research Center in Hampton, Virginia, to explore the flight deck design for the hybrid electric aircraft. Following modern trends in commercial aircraft flight decks with full time augmented controls and a quiet and dark philosophy, single throttle and simplified engine displays were developed for the SUSAN aircraft. The aircraft includes a single aft mounted turbine engine and 16 wing mounted electric fans. The final design was developed from feedback received during an earlier pilot-in-the-loop study where one, two, and three throttles were tested in standard airline operations, including various failures of the turbine and electric engines. Current flight deck designs normally provide control inceptors for each propulsion engine and an engine display for all primary aircraft engine parameters. With full time augmentation expected, a single throttle control with autothrottle always engaged, even during failures, is desired. Augmentation of flight controls using distributed thrust also requires full time control of the electric engines using automation. Additionally, electric engine thrust is augmented during climb based on battery state of charge. Thrust augmentation changes faster than human reaction time and therefore requires full-time automation. A pilot-in-the-loop study was conducted at the NASA Langley Research Center in Hampton, Virginia, to test the final design of the single throttle with simplified engine displays. Fourteen airline pilots evaluated the single throttle and engine display concept. Electric engine failures included one, four symmetric, and eight non-symmetric electric engine failures. The turbine engine was evaluated for complete and partial failure during critical phases of flight to include takeoff as well as enroute. Unexpected go-arounds increase workload and require significant throttle manipulation. Go-arounds were included to ensure the single throttle was usable for all phases of flight. Failures during takeoff required a return to the departure field and failures enroute required a diversion except for one and four electric engine failures as these failures did not affect aircraft flyability or range. There are currently no Part 25 aircraft certified with hybrid systems or electric engines with batteries as emergency propulsion. For turbine engine failures in the SUSAN aircraft design, range is limited to 30 minutes at full power. Battery state of charge and battery health displays were developed and tested for usability and to determine how well they supported pilot decisions for alternate airports during emergency diversions. Novel displays using shape and color were developed to provide immediate feedback when state of charge became critical. This paper details the pilot study including pilot feedback supporting the potential for increased automation and a single throttle control. Detailed recommendations are provided for a novel single throttle control and additional pilot controls to support selection of engines during start, shutdown, and engine troubleshooting procedures. This design deviates significantly from current practice of providing throttles for each propulsion engine. Engine display recommendations are provided based on pilot feedback during a guided post-evaluation interview. Battery state of charge and battery health display recommendations were collected from all airline crews. The simplified engine displays design was rated excellent as measured with a usability scale. Quantitative metrics include airspeed tracking, time to complete checklists, time to make diversion decisions and the quality of the diversion decision. Recommendations for future studies are documented with supporting research and current observations about upcoming flight deck certifications.

autothrottle↗