Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “checklists”

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 325 records · Page 18
All sourcesNASA NTRSDOE OSTI
NASA NTRS1996

Stress and Aeronautical Team Decision Making: Strengthening the Weak Links

A model that characterizes pilots'decision making in flight will be presented. Elements of the model that appear most vulnerable to stress will be examined in light of accidents and incidents. The model includes two major components: Situation assessment and choice of a course of action. While based on Klein's Recognition-Primed Decision Making, it is tailored to the aviation environment which includes certain features that may be common to other domains: Primarily, aviation is highly proceduralized and options are generally well known. What appears to make decisions difficult are ambiguity, time pressure, and risk. In addition, decisions must often be made while carrying out the standard procedures of flight, including checklists, review of approach plates, standard briefings, and communication with air traffic controllers or cabin crew. The effects of stressors on decision making by pilots with varying levels of expertise will be explored, along with strategies for strengthening the weak links.

Orasanu, Judith↗
NASA NTRS2002

Cost Estimation and Control for Flight Systems

Good program management practices, cost analysis, cost estimation, and cost control for aerospace flight systems are interrelated and depend upon each other. The best cost control process cannot overcome poor design or poor systems trades that lead to the wrong approach. The project needs robust Technical, Schedule, Cost, Risk, and Cost Risk practices before it can incorporate adequate Cost Control. Cost analysis both precedes and follows cost estimation -- the two are closely coupled with each other and with Risk analysis. Parametric cost estimating relationships and computerized models are most often used. NASA has learned some valuable lessons in controlling cost problems, and recommends use of a summary Project Manager's checklist as shown here.

Hammond, Walter E.↗
NASA NTRS2002

Defining the Relationship Between Human Error Classes and Technology Intervention Strategies

One of the main factors in all aviation accidents is human error. The NASA Aviation Safety Program (AvSP), therefore, has identified several human-factors safety technologies to address this issue. Some technologies directly address human error either by attempting to reduce the occurrence of errors or by mitigating the negative consequences of errors. However, new technologies and system changes may also introduce new error opportunities or even induce different types of errors. Consequently, a thorough understanding of the relationship between error classes and technology "fixes" is crucial for the evaluation of intervention strategies outlined in the AvSP, so that resources can be effectively directed to maximize the benefit to flight safety. The purpose of the present project, therefore, was to examine the repositories of human factors data to identify the possible relationship between different error class and technology intervention strategies. The first phase of the project, which is summarized here, involved the development of prototype data structures or matrices that map errors onto "fixes" (and vice versa), with the hope of facilitating the development of standards for evaluating safety products. Possible follow-on phases of this project are also discussed. These additional efforts include a thorough and detailed review of the literature to fill in the data matrix and the construction of a complete database and standards checklists.

Wiegmann, Douglas A.↗
NASA NTRS2002

Collegiate Aviation Research and Education Solutions to Critical Safety Issues

This Conference Proceedings is a collection of 6 abstracts and 3 papers presented April 19-20, 2001 in Denver, CO. The conference focus was "Best Practices and Benchmarking in Collegiate and Industry Programs". Topics covered include: satellite-based aviation navigation; weather safety training; human-behavior and aircraft maintenance issues; disaster preparedness; the collegiate aviation emergency response checklist; aviation safety research; and regulatory status of maintenance resource management.

Bowen, Brent↗
NASA NTRS1997

Pilot Performance With Predictive System Status Information

Research has shown a strong pilot preference for predictive information of aircraft system status in the flight deck. However, the benefits of predictive information have not been quantitatively demonstrated. The study described here attempted to identify and quantify these benefits if they existed. In this simulator experiment, three types of predictive information (none, whether a parameter was changing abnormally, and the time for a parameter to reach an alert range) and four initial times to an alert (1 minute, 5 minutes, 15 minutes, and ETA+ 45 minutes) were found to affect when subjects accomplished certain actions, such as accessing pertinent checklists, declaring emergencies, diverting, and calling the flight attendant and dispatch.

Trujillo, Anna C.↗
NASA NTRS2004

Measures and Models for Estimating and Predicting Cognitive Fatigue

We analyzed EEG and ERPs in a fatiguing mental task and created statistical models for single subjects. Seventeen subjects (4 F, 18-38 y) viewed 4-digit problems (e.g., 3+5-2+7=15) on a computer, solved the problems, and pressed keys to respond (intertrial interval = 1 s). Subjects performed until either they felt exhausted or three hours had elapsed. Re- and post-task measures of mood (Activation Deactivation Adjective Checklist, Visual Analogue Mood Scale) confirmed that fatigue increased and energy decreased over time. We tested response times (RT); amplitudes of ERP components N1, P2, P300, readiness potentials; and amplitudes of frontal theta and parietal alpha rhythms for change as a function of time. For subjects who completed 3 h (n=9) we analyzed 12 15-min blocks. For subjects who completed at least 1.5 h (n=17), we analyzed the first-, middle-, and last 100 error-free trials. Mean RT rose from 6.7 s to 8.5 s over time. We found no changes in the amplitudes of ERP components. In both analyses, amplitudes of frontal theta and parietal alpha rose by 30% or more over time. We used 30-channel EEG frequency spectra to model the effects of time in single subjects using a kernel partial least squares classifier. We classified 3.5s EEG segments as being from the first 100 or the last 100 trials, using random sub-samples of each class. Test set accuracies ranged from 63.9% to 99.6% correct. Only 2 of 17 subjects had mean accuracies lower than 80%. The results suggest that EEG accurately classifies periods of cognitive fatigue in 90% of subjects.

Trejo, Leonard J.↗
NASA NTRS2004

Pilot Preferences for Information Provided and Its Format for Status, Alerts, and Controls

With the increased use of cathode ray tubes (CRTs) in flight decks and the computing power available, it is possible to combine status screens, alerts/procedures screens, and control screens onto a single display. This report presents the results of a survey designed to assess the perceived helpfulness and need of various pieces of information that could be included on status and control screens. The results from the survey indicate that operators want parameter ranges that change depending on the current aircraft configuration shown on bow-tie or dial displays. These displays should show the current value, normal range, alert type and range, and predictive information. Respondents wanted to see system relationships to one another for both component control and menu selection. When bringing up these various displays, this information should come up with a single button push. Finally, checklists should sense when a component has changed to the desired state.

Trujillo, Anna C.↗
NASA NTRS2005

The Challenge of Aviation Emergency and Abnormal Situations

Emergency and abnormal situations occur on flights everyday around the world. They range from minor situations readily managed to extremely serious and highly time-critical situations that deeply challenge the skills of even the most effective crews. How well crews respond to these situations is a function of several interacting sets of issues: (1) the design of non-normal procedures and checklists, (2) design of aircraft systems and automation, (3) specific aspects of the non-normal situation, such as time criticality and complexity of the situation, (4) human performance capabilities and cognitive limitations under high workload and stress, (5) design of training for non-normal situations, (6) philosophies, policies and practices within the industry, and (7) economic and regulatory constraints. Researchers and pilots working on NASA's Emergency and Abnormal Situations project are addressing these issues in a long-range study. In this paper we discuss these issues and illustrate them with examples from recent incidents and accidents.

Burian, Barbara K.↗
NASA NTRS2006

Control Room Training for the Hyper-X Program Utilizing Aircraft Simulation

The NASA Dryden Flight Research Center flew two Hyper-X Research Vehicles and achieved hypersonic speeds over the Pacific Ocean in March and November 2004. To train the flight and mission control room crew, the NASA Dryden simulation capability was utilized to generate telemetry and radar data, which was used in nominal and emergency mission scenarios. During these control room training sessions, personnel were able to evaluate and refine data displays, flight cards, mission parameter allowable limits, and emergency procedure checklists. Practice in the mission control room ensured that all primary and backup Hyper-X staff were familiar with the nominal mission and knew how to respond to anomalous conditions quickly and successfully. This paper describes the technology in the simulation environment and the mission control center, the need for and benefit of control room training, and the rationale and results of specific scenarios unique to the Hyper-X research missions.

Lux-Baumann, Jessica R.↗
NASA NTRS2006

Control Room Training for the Hyper-X Project Utilizing Aircraft Simulation

The NASA Dryden Flight Research Center flew two Hyper-X research vehicles and achieved hypersonic speeds over the Pacific Ocean in March and November 2004. To train the flight and mission control room crew, the NASA Dryden simulation capability was utilized to generate telemetry and radar data, which was used in nominal and emergency mission scenarios. During these control room training sessions personnel were able to evaluate and refine data displays, flight cards, mission parameter allowable limits, and emergency procedure checklists. Practice in the mission control room ensured that all primary and backup Hyper-X staff were familiar with the nominal mission and knew how to respond to anomalous conditions quickly and successfully. This report describes the technology in the simulation environment and the Mission Control Center, the need for and benefit of control room training, and the rationale and results of specific scenarios unique to the Hyper-X research missions.

Lux-Baumann, Jesica↗
NASA NTRS2007

Assurance of Complex Electronics. What Path Do We Take?

Many of the methods used to develop software bare a close resemblance to Complex Electronics (CE) development. CE are now programmed to perform tasks that were previously handled in software, such as communication protocols. For instance, Field Programmable Gate Arrays (FPGAs) can have over a million logic gates while system-on-chip (SOC) devices can combine a microprocessor, input and output channels, and sometimes an FPGA for programmability. With this increased intricacy, the possibility of "software-like" bugs such as incorrect design, logic, and unexpected interactions within the logic is great. Since CE devices are obscuring the hardware/software boundary, we propose that mature software methodologies may be utilized with slight modifications to develop these devices. By using standardized S/W Engineering methods such as checklists, missing requirements and "bugs" can be detected earlier in the development cycle, thus creating a development process for CE that will be easily maintained and configurable based on the device used.

FROM↗
NASA NTRS2007

Collocation and Pattern Recognition Effects on System Failure Remediation

Previous research found that operators prefer to have status, alerts, and controls located on the same screen. Unfortunately, that research was done with displays that were not designed specifically for collocation. In this experiment, twelve subjects evaluated two displays specifically designed for collocating system information against a baseline that consisted of dial status displays, a separate alert area, and a controls panel. These displays differed in the amount of collocation, pattern matching, and parameter movement compared to display size. During the data runs, subjects kept a randomly moving target centered on a display using a left-handed joystick and they scanned system displays to find a problem in order to correct it using the provided checklist. Results indicate that large parameter movement aided detection and then pattern recognition is needed for diagnosis but the collocated displays centralized all the information subjects needed, which reduced workload. Therefore, the collocated display with large parameter movement may be an acceptable display after familiarization because of the possible pattern recognition developed with training and its use.

Trujillo, Anna C.↗
NASA NTRS2007

Spaceflight Decompression Sickness Contingency Plan

A viewgraph presentation on the Decompression Sickness (DCS) Contingency Plan for manned spaceflight is shown. The topics include: 1) Approach; 2) DCS Contingency Plan Overview; 3) Extravehicular Activity (EVA) Cuff Classifications; 4) On-orbit Treatment Philosophy; 5) Long Form Malfunction Procedure (MAL); 6) Medical Checklist; 7) Flight Rules; 8) Crew Training; 9) Flight Surgeon / Biomedical Engineer (BME) Training; and 10) DCS Emergency Landing Site.

Dervay, Joseph P.↗
NASA NTRS2007

Software Process Assurance for Complex Electronics

Complex Electronics (CE) now perform tasks that were previously handled in software, such as communication protocols. Many methods used to develop software bare a close resemblance to CE development. Field Programmable Gate Arrays (FPGAs) can have over a million logic gates while system-on-chip (SOC) devices can combine a microprocessor, input and output channels, and sometimes an FPGA for programmability. With this increased intricacy, the possibility of software-like bugs such as incorrect design, logic, and unexpected interactions within the logic is great. With CE devices obscuring the hardware/software boundary, we propose that mature software methodologies may be utilized with slight modifications in the development of these devices. Software Process Assurance for Complex Electronics (SPACE) is a research project that used standardized S/W Assurance/Engineering practices to provide an assurance framework for development activities. Tools such as checklists, best practices and techniques were used to detect missing requirements and bugs earlier in the development cycle creating a development process for CE that was more easily maintained, consistent and configurable based on the device used.

Plastow, Richard A.↗
NASA NTRS2007

Filling the Assurance Gap on Complex Electronics

Many of the methods used to develop software bare a close resemblance to Complex Electronics (CE) development. CE are now programmed to perform tasks that were previously handled by software, such as communication protocols. For example, the James Webb Space Telescope will use Field Programmable Gate Arrays (FPGAs), which can have over a million logic gates, to send telemetry. System-on-chip (SoC) devices, another type of complex electronics, can combine a microprocessor, input and output channels, and sometimes an FPGA for programmability. With this increased intricacy, the possibility of software-like bugs such as incorrect design, logic, and unexpected interactions within the logic is great. Since CE devices are obscuring the hardware/software boundary, mature software methodologies have been proposed, with slight modifications, to develop these devices. By using standardized S/W Engineering methods such as checklists, missing requirements and bugs can be detected earlier in the development cycle, thus creating a development process for CE that can be easily maintained and configurable based on the device used.

Plastow, Richard A.↗
NASA NTRS2007

Software Process Assurance for Complex Electronics (SPACE)

Complex Electronics (CE) are now programmed to perform tasks that were previously handled in software, such as communication protocols. Many of the methods used to develop software bare a close resemblance to CE development. For instance, Field Programmable Gate Arrays (FPGAs) can have over a million logic gates while system-on-chip (SOC) devices can combine a microprocessor, input and output channels, and sometimes an FPGA for programmability. With this increased intricacy, the possibility of software-like bugs such as incorrect design, logic, and unexpected interactions within the logic is great. Since CE devices are obscuring the hardware/software boundary, we propose that mature software methodologies may be utilized with slight modifications in the development of these devices. Software Process Assurance for Complex Electronics (SPACE) is a research project that looks at using standardized S/W Assurance/Engineering practices to provide an assurance framework for development activities. Tools such as checklists, best practices and techniques can be used to detect missing requirements and bugs earlier in the development cycle creating a development process for CE that will be more easily maintained, consistent and configurable based on the device used.

Plastow, Richard A.↗
NASA NTRS2008

Staying Motivated During Tough Times

This paper describes the problem of team motivation on a project. Our team was working with the Department of Homeland Security (DHS). The task consisted of figuring out how to safely control and land an airliner using just the thrust from the engines. This is called Throttles-Only Control (TOC). We weren't allowed to modify the airliner in any way, given the time and cost involved, and we had to use a stock airliner with line pilots. The idea was to give the pilots an emergency checklist which would provide them with the most useful information in the shortest time to learn how to fly TOC. The DHS Program office that was supporting us had its funding redirected, due to new priorities. The process of staying motivated for finishing as much of the project as possible is described.

Cole, Jennifer H.↗
NASA NTRS2008

Operator Performance Evaluation of Fault Management Interfaces for Next-Generation Spacecraft

In the cockpit of the NASA's next generation of spacecraft, most of vehicle commanding will be carried out via electronic interfaces instead of hard cockpit switches. Checklists will be also displayed and completed on electronic procedure viewers rather than from paper. Transitioning to electronic cockpit interfaces opens up opportunities for more automated assistance, including automated root-cause diagnosis capability. The paper reports an empirical study evaluating two potential concepts for fault management interfaces incorporating two different levels of automation. The operator performance benefits produced by automation were assessed. Also, some design recommendations for spacecraft fault management interfaces are discussed.

Hayashi, Miwa↗