Search NASA⌕ Search

SEARCH · Search NASA

Results for “safety reporting”

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 181 records · Page 10
All sourcesNASA NTRSDOE OSTI
NASA NTRS1989

Air-ground information transfer in the National Airspace System

This paper reviews NASA's Aviation Safety Reporting System incident data for a two-year period in order to identify the frequency of air-ground information transfer errors and the factors associated with their occurrence. Of the more than 14,000 primary reports received during the 1985 and 1986 reporting period, one out of four reports concerned problems of information transfer between aircraft and ATC. Approximately half of these errors were associated directly or indirectly with aircraft deviations from assigned heading or altitude. The majority of incidents cited some human-system problem such as workload, cockpit distractions, etc., as the primary contributing factor. Improvements in air-ground information transfer using existing and future (e.g., data link) technology are proposed centering on the development and application of user-centered information management principles.

Lee, Alfred T.↗
NASA NTRS1991

The automatic human

An overview is presented of the growth and role of automation in civil aircraft operations for both cockpit management and ground control. NASA has initiated a research program centered on furthering automation and developing a consistent and rational philosophy of human centered aircraft and air traffic control automation. Introduction of the NASA Aviation Safety Reporting System (ASRS) has proved successful in bringing together pilots and ground controllers to report incidents of operational anomalies that can then be analyzed, leading to corrective action to prevent similar reoccurrences. Attention is given to the growing trend of extensive automation in the cockpit that appears to be leading to a diminution of management control of the aircraft by the decreasing number of flight crew members. A majority of reports indicate that there is a serious mismatch between new aircraft capabilities and ATC procedures, which were designed for older aircraft. ASRS has also kept research oriented toward real problems and community needs.

Billings, Charles↗
NASA NTRS1993

A taxonomy of decision problems on the flight deck

Examining cases of real crews making decisions in full-mission simulators or through Aviation Safety Reporting System (ASRS) reports shows that there are many different types of decisions that crews must make. Features of the situation determine the type of decision that must be made. The paper identifies six types of decisions that require different types of cognitive work and are also subject to different types of error or failure. These different requirements, along with descriptions of effective crew strategies, can serve as a basis for developing training practices and for evaluating crews.

Orasanu, Judith M.↗
NASA NTRS1993

Workload management and geographic disorientation in aviation incidents: A review of the ASRS data base

NASA's Aviation Safety Reporting System (ASRS) incident reports are reviewed in two related areas: pilots' failures to appropriately manage tasks, and breakdowns in geographic orientation. Examination of 51 relevant reports on task management breakdowns revealed that altitude busts and inappropriate runway usee were the most frequently reported consequences. Task management breakdowns appeared to occur at all levels of expertise, and prominent causal factors were related to breakdowns in crew communications, over-involvement with the flight management system and, for small (general aviation) aircraft, preoccupation with weather. Analysis of the 83 cases of geographic disorientation suggested that these too occurred at all levels of pilot experience. With regard to causal factors, a majority was related to poor cockpit resource management, in which inattention led to a loss of geographic awareness. Other leading causes were related to poor weather and poor decision making. The potential of the ASRS database for contributing to research and design issues is addressed.

Williams, Henry P.↗
NASA NTRS1993

Initial exploration of the ASRS database

We applied a standard classification algorithm to a subset of NASA/FAA Aviation Safety Reporting System (ASRS) database. The subset concerned incidents of aircraft altitude deviations. We are exploring the database to address questions such as: Are there 'natural' classes into which the data will fall? How would these classes correspond to recognizable events or situations? Beyond addressing these we want the data to determine directions for further study. We conducted experiments on different data subsections and analyzed diagnostics such as 'message length reduction'; these characterize the classification in terms of its significance and information content. The classification effort was successful in revealing relationships in the data that were in consonance with other studies of the data and expert opinion.

Kraft, Richard↗
NASA NTRS1998

Rating the Relevance of QUORUM-Selected ASRS Incident Narratives to a "Controlled Flight into Terrain" Accident

An exploratory study was conducted to identify commercial aviation incidents that are relevant to a "controlled flight into terrain" (CFIT) accident using a NASA-developed text processing method. The QUORUM method was used to rate 67820 incident narratives, virtually all of the narratives in the Aviation Safety Reporting System (ASRS) database, according to their relevance to two official reports on the crash of American Airlines Flight 965 near Cali, Colombia in December 1995. For comparison with QUORUM's ratings, three experienced ASRS analysts read the reports of the crash and independently rated the relevance of the 100 narratives that were most highly rated by QUORUM, as well as 100 narratives randomly selected from the database. Eighty-four of 100 QUORUM-selected narratives were rated as relevant to the Cali accident by one or more of the analysts. The relevant incidents involved a variety of factors, including, over-reliance on automation, confusion and changes during descent/approach, terrain avoidance, and operations in foreign airspace. In addition, the QUORUM collection of incidents was found to be significantly more relevant than the random collection.

McGreevy, Michael W.↗
NASA NTRS2001

Searching the ASRS Database Using QUORUM Keyword Search, Phrase Search, Phrase Generation, and Phrase Discovery

To support Search Requests and Quick Responses at the Aviation Safety Reporting System (ASRS), four new QUORUM methods have been developed: keyword search, phrase search, phrase generation, and phrase discovery. These methods build upon the core QUORUM methods of text analysis, modeling, and relevance-ranking. QUORUM keyword search retrieves ASRS incident narratives that contain one or more user-specified keywords in typical or selected contexts, and ranks the narratives on their relevance to the keywords in context. QUORUM phrase search retrieves narratives that contain one or more user-specified phrases, and ranks the narratives on their relevance to the phrases. QUORUM phrase generation produces a list of phrases from the ASRS database that contain a user-specified word or phrase. QUORUM phrase discovery finds phrases that are related to topics of interest. Phrase generation and phrase discovery are particularly useful for finding query phrases for input to QUORUM phrase search. The presentation of the new QUORUM methods includes: a brief review of the underlying core QUORUM methods; an overview of the new methods; numerous, concrete examples of ASRS database searches using the new methods; discussion of related methods; and, in the appendices, detailed descriptions of the new methods.

McGreevy, Michael W.↗
NASA NTRS1995

Identifying Human Factors Issues in Aircraft Maintenance Operations

Maintenance operations incidents submitted to the Aviation Safety Reporting System (ASRS) between 1986-1992 were systematically analyzed in order to identify issues relevant to human factors and crew coordination. This exploratory analysis involved 95 ASRS reports which represented a wide range of maintenance incidents. The reports were coded and analyzed according to the type of error (e.g, wrong part, procedural error, non-procedural error), contributing factors (e.g., individual, within-team, cross-team, procedure, tools), result of the error (e.g., aircraft damage or not) as well as the operational impact (e.g., aircraft flown to destination, air return, delay at gate). The main findings indicate that procedural errors were most common (48.4%) and that individual and team actions contributed to the errors in more than 50% of the cases. As for operational results, most errors were either corrected after landing at the destination (51.6%) or required the flight crew to stop enroute (29.5%). Interactions among these variables are also discussed. This analysis is a first step toward developing a taxonomy of crew coordination problems in maintenance. By understanding what variables are important and how they are interrelated, we may develop intervention strategies that are better tailored to the human factor issues involved.

Veinott, Elizabeth S.↗
NASA NTRS1996

Translating Research Into Airline Practice: Case Studies In Collaboration

Airline training departments are avid customers for research that will help them enhance the effectiveness of training and the safety of flight operations. However, various factors often make it difficult for training department managers to draw upon the large body of human factors research, e.g.: research may not address the specific questions facing the training departments, the research literature may not be in a form that training managers can readily interpret, researchers' recommendations may be too expensive or impractical to implement, etc. This panel will discuss ways in which researchers can work with training departments to design research and translate findings into products that airlines can use readily. This collaboration is most effective when it is an integral part of the study from its inception. To illustrate the process of collaboration we will use as a case study the recently completed LOFT (Line Oriented Flight Training) Debriefing research project. We will summarize the findings from that study and discuss how we translated those findings into two training tools: a manual on how to facilitate LOFT debriefings and a video that illustrates facilitation techniques in a realistically enacted debriefing. In some cases, instead of starting a new research project, training department needs can be addressed by reviewing the existing research literature and using expert opinion to develop products that specifically address those needs. To illustrate this approach we will discuss a recent informal working group of scientists and airline personnel that met to develop training material to enhance situation awareness. This group reviewed scientific literature and ASRS (Aviation Safety Reporting System) reports, analyzed contributing factors, and produced a model for managing situation awareness.

Dismukes, R. Key↗
NASA NTRS1997

Ground Taxi Navigation Problems and Training Solutions

Adverse weather conditions can put considerable strain on the National Airspace System. Even small decreases in visibility on the airport surface can create delays, hinder safe movement and lead to errors. Studies of Aviation Safety Reporting System (ASRS) surface movement incidents support the need for technologies and procedures to improve ground operations in low-visibility conditions. This study examined 139 ASRS reports of low-visibility surface movement incidents at 10 major U.S. airports. Errors were characterized in terms of incident type, contributing factors and consequences. The incidents in the present sample were comprised of runway transgressions, taxiway excursions and ground conflicts. The primary contributing factors were Airport Layout and Markings, Communication and Distraction. In half the incidents the controller issued a new clearance or the flight crew took an evasive action and in the remaining half, no recovery attempt was made because the error was detected after the fact. By gaining a better understanding the factors that affect crew navigation in low visibility and the types of errors that are likely to occur, it will be possible to develop more robust technologies to aid pilots in the ground taxi task. Implications for crew training and procedure development for low-visibility ground taxi are also discussed.

Quinn, Cheryl↗
NASA NTRS2004

Analysis of Adverse Events in Identifying GPS Human Factors Issues

The purpose of this study was to analyze GPS related adverse events such as accidents and incidents (A/I), Aviation Safety Reporting System (ASRS) reports and Pilots Deviations (PDs) to create a framework for developing a human factors risk awareness program. Although the occurrence of directly related GPS accidents is small the frequency of PDs and ASRS reports indicated there is a growing problem with situational awareness in terminal airspace related to different types of GPs operational issues. This paper addresses the findings of the preliminary research and a brief discussion of some of the literature on related GPS and automation issues.

Adams, Catherine A.↗
NASA NTRS2006

Human Factors Considerations for Area Navigation Departure and Arrival Procedures

Area navigation (RNAV) procedures are being implemented in the United States and around the world as part of a transition to a performance-based navigation system. These procedures are providing significant benefits and have also caused some human factors issues to emerge. Under sponsorship from the Federal Aviation Administration (FAA), the National Aeronautics and Space Administration (NASA) has undertaken a project to document RNAV-related human factors issues and propose areas for further consideration. The component focusing on RNAV Departure and Arrival Procedures involved discussions with expert users, a literature review, and a focused review of the NASA Aviation Safety Reporting System (ASRS) database. Issues were found to include aspects of air traffic control and airline procedures, aircraft systems, and procedure design. Major findings suggest the need for specific instrument procedure design guidelines that consider the effects of human performance. Ongoing industry and government activities to address air-ground communication terminology, design improvements, and chart-database commonality are strongly encouraged. A review of factors contributing to RNAV in-service errors would likely lead to improved system design and operational performance.

Barhydt, Richard↗
NASA NTRS2007

Analytical Approach for Estimating Preliminary Mass of ARES I Crew Launch Vehicle Upper Stage Structural Components

In January 2004, President Bush gave the National Aeronautics and Space Administration (NASA) a vision for Space Exploration by setting our sight on a bold new path to go back to the Moon, then to Mars and beyond. In response to this vision, NASA started the Constellation Program, which is a new exploration launch vehicle program. The primary mission for the Constellation Program is to carry out a series of human expeditions ranging from Low Earth Orbit to the surface of Mars and beyond for the purposes of conducting human exploration of space, as specified by the Vision for Space Exploration (VSE). The intent is that the information and technology developed by this program will provide the foundation for broader exploration activities as our operational experience grows. The ARES I Crew Launch Vehicle (CLV) has been designated as the launch vehicle that will be developed as a "first step" to facilitate the aforementioned human expeditions. The CLV Project is broken into four major elements: First Stage, Upper Stage Engine, Upper Stage (US), and the Crew Exploration Vehicle (CEV). NASA's Marshall Space Flight Center (MSFC) is responsible for the design of the CLV and has the prime responsibility to design the upper stage of the vehicle. The US is the second propulsive stage of the CLV and provides CEV insertion into low Earth orbit (LEO) after separation from the First Stage of the Crew Launch Vehicle. The fully integrated Upper Stage is a mix of modified existing heritage hardware (J-2X Engine) and new development (primary structure, subsystems, and avionics). The Upper Stage assembly is a structurally stabilized cylindrical structure, which is powered by a single J-2X engine which is developed as a separate Element of the CLV. The primary structure includes the load bearing liquid hydrogen (LH2) and liquid oxygen (LOX) propellant tanks, a Forward Skirt, the Intertank structure, the Aft Skirt and the Thrust Structure. A Systems Tunnel, which carries fluid and electrical power functions to other Elements of the CLV, is included as secondary structure. The MSFC has an overall responsibility for the integrated US element as well as structural design an thermal control of the fuel tanks, intertank, interstage, avionics, main propulsion system, Reaction Control System (RCS) for both the Upper Stage and the First Stage. MSFC's Spacecraft and Vehicle Department, Structural and Analysis Design Division is developing a set of predicted mass of these elements. This paper details the methodology, criterion and tools used for the preliminary mass predictions of the upper stage structural assembly components. In general, weight of the cylindrical barrel sections are estimated using the commercial code Hypersizer, whereas, weight of the domes are developed using classical solutions. HyperSizer is software that performs automated structural analysis and sizing optimization based on aerospace methods for strength, stability, and stiffness. Analysis methods range from closed form, traditional hand calculations repeated every day in industry to more advanced panel buckling algorithms. Margin-of-safety reporting for every potential failure provides the engineer with a powerful insight into the structural problem. Optimization capabilities include finding minimum weight panel or beam concepts, material selections, cross sectional dimensions, thicknesses, and lay-ups from a library of 40 different stiffened and sandwich designs and a database of composite, metallic, honeycomb, and foam materials. Multiple different concepts (orthogrid, isogrid, and skin stiffener) were run for multiple loading combinations of ascent design load with and with out tank pressure as well as proof pressure condition. Subsequently, selected optimized concept obtained from Hypersizer runs was translated into a computer aid design (CAD) model to account for the wall thickness tolerance, weld land etc for developing the most probable weight of the components. The flow diram summarizes the analysis steps used in developing these predicted mass.

Aggarwal, Pravin↗
NASA NTRS2008

Problem Reporting System

The Problem Reporting System (PRS) is a Web application, running on two Web servers (load-balanced) and two database servers (RAID-5), which establishes a system for submission, editing, and sharing of reports to manage risk assessment of anomalies identified in NASA's flight projects. PRS consolidates diverse anomaly-reporting systems, maintains a rich database set, and incorporates a robust engine, which allows tracking of any hardware, software, or paper process by configuring an appropriate life cycle. Global and specific project administration and setup tools allow lifecycle tailoring, along with customizable controls for user, e-mail, notifications, and more. PRS is accessible via the World Wide Web for authorized user at most any location. Upon successful log-in, the user receives a customizable window, which displays time-critical 'To Do' items (anomalies requiring the user s input before the system moves the anomaly to the next phase of the lifecycle), anomalies originated by the user, anomalies the user has addressed, and custom queries that can be saved for future use. Access controls exist depending on a user's role as system administrator, project administrator, user, or developer, and then, further by association with user, project, subsystem, company, or item with provisions for business-to-business exclusions, limitations on access according to the covert or overt nature of a given project, all with multiple layers of filtration, as needed. Reporting of metrics is built in. There is a provision for proxy access (in which the user may choose to grant one or more other users to view screens and perform actions as though they were the user, during any part of a tracking life cycle - especially useful during tight build schedules and vacations to keep things moving). The system also provides users the ability to have an anomaly link to or notify other systems, including QA Inspection Reports, Safety, GIDEP (Government-Industry Data Exchange Program) Alert, Corrective Actions, and Lessons Learned. The PRS tracking engine was designed as a very extensible and scalable system, able to support additional applications, with future development possibilities already discussed, including Incident Surprise Anomalies (for anomalies occurring during Operations phases of NASA Flight projects), GIDEP and NASA Alerts, and others.

Potter, Don↗
NASA NTRS2010

Causal Factors and Adverse Conditions of Aviation Accidents and Incidents Related to Integrated Resilient Aircraft Control

The causal factors of accidents from the National Transportation Safety Board (NTSB) database and incidents from the Federal Aviation Administration (FAA) database associated with loss of control (LOC) were examined for four types of operations (i.e., Federal Aviation Regulation Part 121, Part 135 Scheduled, Part 135 Nonscheduled, and Part 91) for the years 1988 to 2004. In-flight LOC is a serious aviation problem. Well over half of the LOC accidents included at least one fatality (80 percent in Part 121), and roughly half of all aviation fatalities in the studied time period occurred in conjunction with LOC. An adverse events table was updated to provide focus to the technology validation strategy of the Integrated Resilient Aircraft Control (IRAC) Project. The table contains three types of adverse conditions: failure, damage, and upset. Thirteen different adverse condition subtypes were gleaned from the Aviation Safety Reporting System (ASRS), the FAA Accident and Incident database, and the NTSB database. The severity and frequency of the damage conditions, initial test conditions, and milestones references are also provided.

Reveley, Mary S.↗
NASA NTRS2011

Causal Factors and Adverse Events of Aviation Accidents and Incidents Related to Integrated Vehicle Health Management

Causal factors in aviation accidents and incidents related to system/component failure/malfunction (SCFM) were examined for Federal Aviation Regulation Parts 121 and 135 operations to establish future requirements for the NASA Aviation Safety Program s Integrated Vehicle Health Management (IVHM) Project. Data analyzed includes National Transportation Safety Board (NSTB) accident data (1988 to 2003), Federal Aviation Administration (FAA) incident data (1988 to 2003), and Aviation Safety Reporting System (ASRS) incident data (1993 to 2008). Failure modes and effects analyses were examined to identify possible modes of SCFM. A table of potential adverse conditions was developed to help evaluate IVHM research technologies. Tables present details of specific SCFM for the incidents and accidents. Of the 370 NTSB accidents affected by SCFM, 48 percent involved the engine or fuel system, and 31 percent involved landing gear or hydraulic failure and malfunctions. A total of 35 percent of all SCFM accidents were caused by improper maintenance. Of the 7732 FAA database incidents affected by SCFM, 33 percent involved landing gear or hydraulics, and 33 percent involved the engine and fuel system. The most frequent SCFM found in ASRS were turbine engine, pressurization system, hydraulic main system, flight management system/flight management computer, and engine. Because the IVHM Project does not address maintenance issues, and landing gear and hydraulic systems accidents are usually not fatal, the focus of research should be those SCFMs that occur in the engine/fuel and flight control/structures systems as well as power systems.

Reveley, Mary S.↗
NASA NTRS2019

Overcoming the Challenges of Data Integration and Automation

Artificial Intelligence (AI) and machine learning (ML) are gaining increased attention as a way to leverage the world's data to solve problems. Although AI and ML offer much potential, there are often misconceptions about the application of such techniques. This panel discussion includes speakers from airlines and the research community who will present machine learning approaches they have developed on a variety of aviation data including digital flight data, safety reporting data, and traffic flow data. They will explain the purpose of the application, the data used, and the lessons learned in the development and deployment of their solutions. The panel discussion will focus on common pitfalls in developing and AI solution, the dangers of the current hype around AI, tips for gaining value from a machine learning solution, how to determine whether a machine learning approach is appropriate for a problem, and more.

Matthews, Bryan L.↗
NASA NTRS2019

Artificial Intelligence in Aviation Safety Applications - Exploring Myths and Truths of AI and ML

Artificial Intelligence (AI) and machine learning (ML) are gaining increased attention as ways to leverage the world's data to solve problems. Although AI and ML offer much potential, there are often misconceptions about the application of such techniques.Panel speakers will present machine learning approaches they have developed on a variety of aviation data, including digital flight data, safety reporting data, and voice communications data. They will discuss the purpose of the application, the data used, and the lessons learned in the development and deployment of their solutions. The panel will also discuss common pitfalls in developing an AI solution, the dangers of the current hype around AI, tips for gaining value from a ML solution, how to determine whether a ML approach is appropriate for a problem, and more.

Reeves, Scott (Capt.)↗