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.
This presentation gives an overview of the technology, methods and processes developed during the TC3 Technical Challenge of the System-Wide Safety (SWS) project. The presentation goes over the motivation for doing this research, gives an overview of the tool, methods and process developed under this program, and describes case studies and impact in industry.
Humans are frequently left to “backstop” automated systems, and Human Factors specialists have argued against this for decades with, at best, partial success. What if we took a different tack... and designed to support it? The participants were involved in a recent effort to review and document cases across multiple domains where operators acted as a “failsafe” for automation, intervening in unanticipated situations to maximize success and minimize damage. We defined a “Human As Failsafe” (HAF) incident and then investigated conditions and practices making HAF success more or less likely. Analyzing these historical incidents, we suggested remediation approaches. The project also examined the legal concept of culpability (i.e., when intervention should have happened but didn’t) and proposed a state-machine-based analytic simulation to identify when HAF interventions are plausible. The panel objective will be to briefly present these concepts, but more generally to discuss designing for inevitable HAF events. This presentation with review the concept of a HAT Assistant to support multi-vehicle control of drones in a wildland firefighting context.
The Future Aviation Safety Team (FAST) is a multidisciplinary international group of aviation professionals that was established to identify possible future aviation safety hazards. The principle was adopted that future hazards are undesirable consequences of changes, and a primary activity of FAST became identification and prioritization of possible future changes affecting aviation. Since 2004, FAST has been maintaining a catalogue of "Areas of Change" (AoC) that could potentially influence aviation safety. The horizon for such changes is between 5 to 20 years. In this context, changes must be understood as broadly as possible. An AoC is a description of the change, not an identification of the hazards that result from the change. An ex-post analysis of the AoCs identified in 2004 demonstrates that changes catalogued many years previous were directly implicated in the majority of fatal aviation accidents over the past ten years. This paper presents an overview of the current content of the AoC catalogue and a subsequent discussion of aviation safety concerns related to these possible changes. Interactions among these future changes may weaken critical functions that must be maintained to ensure safe operations. Safety assessments that do not appreciate or reflect the consequences of significant interaction complexity will not be fully informative and can lead to inappropriate trade-offs and increases in other risks. The FAST strongly encourages a system-wide approach to safety risk assessment across the global aviation system, not just within the domain for which future technologies or operational concepts are being considered. The FAST advocates the use of the "Areas of Change" concept, considering that several possible future phenomena may interact with a technology or operational concept under study producing unanticipated hazards.
This report describes the research effort to demonstrate the integration of a data sharing technology, Ring Buffered Network Bus, in development by Dryden Flight Research Center, with an engine simulation application, the Java Gas Turbine Simulator, in development at the University of Toledo under a grant from the Glenn Research Center. The objective of this task was to examine the application of the RBNB technologies as a key component in the data sharing, health monitoring and system wide modeling elements of the NASA Aviation Safety Program (AVSP) [Golding, 1997]. System-wide monitoring and modeling of aircraft and air safety systems will require access to all data sources which are relative factors when monitoring or modeling the national airspace such as radar, weather, aircraft performance, engine performance, schedule and planning, airport configuration, flight operations, etc. The data sharing portion of the overall AVSP program is responsible for providing the hardware and software architecture to access and distribute data, including real-time flight operations data, among all of the AVSP elements. The integration of an engine code capable of numerically "flying" through recorded flight paths and weather data using a software tool that allows for distributed access of data to this engine code demonstrates initial steps toward building a system capable of monitoring and modeling the National Airspace.
This research presents a methodology for generating errors from a model of nominally preferred correct operator activities, given a particular operational context, and maintaining an explicit link to the erroneous contextual information to support analyses. It uses the Crew Activity Tracking System (CATS) model as the basis for error generation. This report describes how the process works, and how it may be useful for supporting agent-based system safety analyses. The report presents results obtained by applying the error-generation process and discusses implementation issues. The research is supported by the System-Wide Accident Prevention Element of the NASA Aviation Safety Program.
NASA has conducted an extensive redesign effort for the Space Shutle in the aftermath of the STS 51-L Challenger accident, encompassing not only Shuttle vehicle and booster design but also such system-wide factors as organizational structure, management procedures, flight safety, flight operations, sustainable flight rate, and maintenance safeguards. Attention is presently given to Solid Rocket Booster redesign features, the Shuttle Main Engine's redesigned high pressure fuel and oxidizer turbopumps, the Shuttle Orbiter's braking and rollout (landing gear) system, the entry control mode of the flight control system, a 'split-S' abort maneuver for the Orbiter, and crew escape capsule proposals.
This report describes preliminary research on intelligent agents that make errors. Such agents are crucial to the development of novel agent-based techniques for assessing system safety. The agents extend an agent architecture derived from the Crew Activity Tracking System that has been used as the basis for air traffic controller agents. The report first reviews several error taxonomies. Next, it presents an overview of the air traffic controller agents, then details several mechanisms for causing the agents to err in realistic ways. The report presents a performance assessment of the error-generating agents, and identifies directions for further research. The research was supported by the System-Wide Accident Prevention element of the FAA/NASA Aviation Safety Program.
This effort was supported by the System-Wide Accident Prevention element of NASA s Aviation Safety Program. This document may serve as a first step toward the goal of integrating traffic, weather, and terrain information; it provides recommendations for a cockpit display that integrates weather information with traffic information. While some of the recommendations are general enough to be used for any type of operations, these recommendations are targeted for Federal Aviation Regulations Part 121 Operations. The document is organized in the following manner. First, weather information is discussed as an independent subject matter, and recommendations are presented for presenting weather in the cockpit. Second, traffic is discussed independently, but this discussion essentially reviews work on the display of traffic in the cockpit. Third, recommendations for the cockpit integration of weather and traffic information are discussed. Fourth, several research groups are recognized for their efforts in developing systems that are relevant to the current discussion. Finally, closing remarks provide suggestions for future efforts.
The ultimate goal of conducting an accident investigation is to prevent similar accidents from happening again and to make operations safer system-wide. Based on the findings extracted from the investigation, the "lesson learned" becomes a genuine part of the safety database making risk management available to safety analysts. The airline industry is no exception. In the US, the FAA has advocated the usage of the System Safety concept in enhancing safety since 2000. Yet, in today s usage of System Safety, the airline industry mainly focuses on risk management, which is a reactive process of the System Safety discipline. In order to extend the merit of System Safety and to prevent accidents beforehand, a specific System Safety tool needs to be applied; so a model of hazard prediction can be formed. To do so, the authors initiated this study by reviewing 189 final accident reports from the National Transportation Safety Board (NTSB) covering FAR Part 121 scheduled operations. The discovered accident causes (direct hazards) were categorized into 10 groups Flight Operations, Ground Crew, Turbulence, Maintenance, Foreign Object Damage (FOD), Flight Attendant, Air Traffic Control, Manufacturer, Passenger, and Federal Aviation Administration. These direct hazards were associated with 36 root factors prepared for an error-elimination model using Fault Tree Analysis (FTA), a leading tool for System Safety experts. An FTA block-diagram model was created, followed by a probability simulation of accidents. Five case studies and reports were provided in order to fully demonstrate the usefulness of System Safety tools in promoting airline safety.
The NASA Integrated Vehicle Health Management (IVHM) Technology Experiment for X-37 was intended to run IVHM software on-board the X-37 spacecraft. The X-37 is intended to be an unpiloted vehicle that would orbit the Earth for up to 21 days before landing on a runway. The objectives of the experiment were to demonstrate the benefits of in-flight IVHM to the operation of a Reusable Launch Vehicle, to advance the Technology Readiness Level of this IVHM technology within a flight environment, and to demonstrate that the IVHM software could operate on the Vehicle Management Computer. The scope of the experiment was to perform real-time fault detection and isolation for X-37's electrical power system and electro-mechanical actuators. The experiment used Livingstone, a software system that performs diagnosis using a qualitative, model-based reasoning approach that searches system-wide interactions to detect and isolate failures. Two of the challenges we faced were to make this research software more efficient so that it would fit within the limited computational resources that were available to us on the X-37 spacecraft, and to modify it so that it satisfied the X-37's software safety requirements. Although the experiment is currently unfunded, the development effort had value in that it resulted in major improvements in Livingstone's efficiency and safety. This paper reviews some of the details of the modeling and integration efforts, and some of the lessons that were learned.
A preliminary list of criteria is proposed for evaluation of solid waste processing technologies for research and technology development (R&TD) in the Advanced Life Support (ALS) Program. Completion of the proposed list by current and prospective ALS technology developers, with regard to specific missions of interest, may enable identification of appropriate technologies (or lack thereof) and guide future development efforts for the ALS Program solid waste processing area. An attempt is made to include criteria that capture information about the technology of interest as well as its system-wide impacts. Some of the criteria in the list are mission-independent, while the majority are mission-specific. In order for technology developers to respond to mission-specific criteria, critical information must be available on the quantity, composition and state of the waste stream, the wast processing requirements, as well as top-level mission scenario information (e.g. safety, resource recovery, planetary protection issues, and ESM equivalencies). The technology readiness level (TRL) determines the degree to which a technology developer is able to accurately report on the list of criteria. Thus, a criteria-specific minimum TRL for mandatory reporting has been identified for each criterion in the list. Although this list has been developed to define criteria that are needed to direct funding of solid waste processing technologies, this list processes significant overlap in criteria required for technology selection for inclusion in specific tests or missions. Additionally, this approach to technology evaluation may be adapted to other ALS subsystems.
At the aircraft level, a Vehicle-Level Reasoning System (VLRS) can be developed to provide aircraft with at least two significant capabilities: improvement of aircraft safety due to enhanced monitoring and reasoning about the aircrafts health state, and also potential cost savings by enabling Condition Based Maintenance (CBM). Along with the benefits of CBM, an important challenge facing aviation safety today is safeguarding against system and component failures and malfunctions. Faults can arise in one or more aircraft subsystem their effects in one system may propagate to other subsystems, and faults may interact.
This Interface Control Document (ICD) documents the airspace adaptation and air traffic inputs of NASA's Future ATM Concepts and Evaluation Tool (FACET). Its intended audience is the project manager, project team, development team, and stakeholders interested in interfacing with the system. FACET equips Air Traffic Management (ATM) researchers and service providers with a way to explore, develop and evaluate advanced air transportation concepts before they are field-tested and eventually deployed. FACET is a flexible software tool that is capable of quickly generating and analyzing thousands of aircraft trajectories. It provides researchers with a simulation environment for preliminary testing of advanced ATM concepts. Using aircraft performance profiles, airspace models, weather data, and flight schedules, the tool models trajectories for the climb, cruise, and descent phases of flight for each type of aircraft. An advanced graphical interface displays traffic patterns in two and three dimensions, under various current and projected conditions for specific airspace regions or over the entire continental United States. The system is able to simulate a full day's dynamic national airspace system (NAS) operations, model system uncertainty, measure the impact of different decision-makers in the NAS, and provide analysis of the results in graphical form, including sector, airport, fix, and airway usage statistics. NASA researchers test and analyze the system-wide impact of new traffic flow management algorithms under anticipated air traffic growth projections on the nation's air traffic system. In addition to modeling the airspace system for NASA research, FACET has also successfully transitioned into a valuable tool for operational use. Federal Aviation Administration (FAA) traffic flow managers and commercial airline dispatchers have used FACET technology for real-time operations planning. FACET integrates live air traffic data from FAA radar systems and weather data from the National Weather Service to summarize NAS performance. This information allows system operators to reroute flights around congested airspace and severe weather to maintain safety and minimize delay. FACET also supports the planning and post-operational evaluation of reroute strategies at the national level to maximize system efficiency. For the commercial airline passenger, strategic planning with FACET can result in fewer flight delays and cancellations. The performance capabilities of FACET are largely due to its architecture, which strikes a balance between flexibility and fidelity. FACET is capable of modeling the airspace operations for the continental United States, processing thousands of aircraft on a single computer. FACET was written in Java and C, enabling the portability of its software to a variety of operating systems. In addition, FACET was designed with a modular software architecture to facilitate rapid prototyping of diverse ATM concepts. Several advanced ATM concepts have already been implemented in FACET, including aircraft self-separation, prediction of aircraft demand and sector congestion, system-wide impact assessment of traffic flow management constraints, and wind-optimal routing.
Increasing numbers of aircraft are operating on the surface of airports throughout the world. Airport operations are forecast to grow by more that 50%, by the year 2005. Airport surface movement traffic would therefore be expected to become increasingly congested. Safety of these surface operations will become a focus as airport capacity planning efforts proceed toward the future. Several past events highlight the prevailing risks experienced while moving aircraft during ground operations on runways, taxiways, and other areas at terminal, gates, and ramps. The 1994 St. Louis accident between a taxiing Cessna crossing an active runway and colliding with a landing MD-80 emphasizes the importance of a fail-safe system for airport operations. The following study explores reports of incidents occurring on an airport surface that did not escalate to an accident event. The Aviation Safety Reporting System has collected data on surface movement incidents since 1976. This study sampled the reporting data from June, 1993 through June, 1994. The coding of the data was accomplished in several categories. The categories include location of airport, phase of ground operation, weather /lighting conditions, ground conflicts, flight crew characteristics, human factor considerations, and airport environment. These comparisons and distributions of variables contributing to surface movement incidents can be invaluable to future airport planning, accident prevention efforts, and system-wide improvements.
Path Loss Measurements were obtained on three (3) GPS equipped 757 aircraft. Systems measured were Marker Beacon, LOC, VOR, VHF (3), Glide Slope, ATC (2), DME (2), TCAS, and GPS. This data will provide the basis for assessing the EMI (Electromagnetic Interference) safety margins of comm/nav (communication and navigation) systems to portable electronic device emissions. These Portable Electronic Devices (PEDs) include all devices operated in or around the aircraft by crews, passengers, servicing personnel, as well as the general public in the airport terminals. EMI assessment capability is an important step in determining if one system-wide PED EMI policy is appropriate. This data may also be used comparatively with theoretical analysis and computer modeling data sponsored by NASA Langley Research Center and others.
This document defines an initial set of metrics for use by the NASA Airspace Systems Program (ASP). ASP consists of the NextGen-Airspace Project and the NextGen-Airportal Project. The work in each project is organized along multiple, discipline-level Research Focus Areas (RFAs). Each RFA is developing future concept elements in support of the Next Generation Air Transportation System (NextGen), as defined by the Joint Planning and Development Office (JPDO). In addition, a single, system-level RFA is responsible for integrating concept elements across RFAs in both projects and for assessing system-wide benefits. The primary purpose of this document is to define a common set of metrics for measuring National Airspace System (NAS) performance before and after the introduction of ASP-developed concepts for NextGen as the system handles increasing traffic. The metrics are directly traceable to NextGen goals and objectives as defined by the JPDO and hence will be used to measure the progress of ASP research toward reaching those goals. The scope of this document is focused on defining a common set of metrics for measuring NAS capacity, efficiency, robustness, and safety at the system-level and at the RFA-level. Use of common metrics will focus ASP research toward achieving system-level performance goals and objectives and enable the discipline-level RFAs to evaluate the impact of their concepts at the system level.
Safety-critical distributed flight control systems require robustness in the presence of faults. In general, these systems consist of a number of input/output (I/O) and computation nodes interacting through a fault-tolerant data communication system. The communication system transfers sensor data and control commands and can handle most faults under typical operating conditions. However, the performance of the closed-loop system can be adversely affected as a result of operating in harsh environments. In particular, High-Intensity Radiated Field (HIRF) environments have the potential to cause random fault manifestations in individual avionic components and to generate simultaneous system-wide communication faults that overwhelm existing fault management mechanisms. This paper presents the design of an experiment conducted at the NASA Langley Research Center's HIRF Laboratory to statistically characterize the faults that a HIRF environment can trigger on a single node of a distributed flight control system.
Severe weather events are likely occurrences on the Mississippi Gulf Coast. It is important to rapidly diagnose and mitigate the effects of storms on Stennis Space Center's rocket engine test complex to avoid delays to critical test article programs, reduce costs, and maintain safety. An Integrated Systems Health Management (ISHM) approach and technologies are employed to integrate environmental (weather) monitoring, structural modeling, and the suite of available facility instrumentation to provide information for readiness before storms, rapid initial damage assessment to guide mitigation planning, and then support on-going assurance as repairs are effected and finally support recertification. The system is denominated Katrina Storm Monitoring System (KStorMS). Integrated Systems Health Management (ISHM) describes a comprehensive set of capabilities that provide insight into the behavior the health of a system. Knowing the status of a system allows decision makers to effectively plan and execute their mission. For example, early insight into component degradation and impending failures provides more time to develop work around strategies and more effectively plan for maintenance. Failures of system elements generally occur over time. Information extracted from sensor data, combined with system-wide knowledge bases and methods for information extraction and fusion, inference, and decision making, can be used to detect incipient failures. If failures do occur, it is critical to detect and isolate them, and suggest an appropriate course of action. ISHM enables determining the condition (health) of every element in a complex system-of-systems or SoS (detect anomalies, diagnose causes, predict future anomalies), and provide data, information, and knowledge (DIaK) to control systems for safe and effective operation. ISHM capability is achieved by using a wide range of technologies that enable anomaly detection, diagnostics, prognostics, and advise for control: (1) anomaly detection algorithms and strategies, (2) fusion of DIaK for anomaly detection (model-based, numerical, statistical, empirical, expert-based, qualitative, etc.), (3) diagnostics/prognostics strategies and methods, (4) user interface, (5) advanced control strategies, (6) integration architectures/frameworks, (7) embedding of intelligence. Many of these technologies are mature, and they are being used in the KStorMS. The paper will describe the design, implementation, and operation of the KStorMS; and discuss further evolution to support other needs such as condition-based maintenance (CBM).