Search NASA⌕ Search

SEARCH · Search NASA

Results for “Hazard analysis”

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 91 records · Page 5

Pre-Flight Hazardous Gas Assessment Methodology for the Space Launch System

The complexity of the Artemis I liquid rocket propulsion systems produces many sources of hazards during the operation of the vehicle. Pre-flight hazardous gas leakages pose fire and explosion risks to rocket that could potentially lead to loss of the vehicle, mission, and crew. The National Aeronautics and Space Administration (NASA) uses a probability risk assessment strategy to assess the likelihood of the hazard and the consequence should the hazardous situation occur. For high probability hazards that pose a potentially catastrophic consequence to the vehicle, the most effective strategy for reducing the risk is accomplished by engineering and implementing systems that actively mitigate the hazard. A hazards analysis is completed to determine the likelihood and severity of each hazard. These hazard analyses are informed using relevant empirical data and physics-based analytical models. Time-accurate Computational Fluid Dynamics models used to quantify and understand the risks posed to Artemis I due to expulsions of hazardous gas near the vehicle. Several sources of hazardous gas that posed a risk to Artemis I during nominal pre-flight operations are analyzed in this work. The results of the analyses were used to develop flight rationale and make risk acceptance decisions for the Artemis I launch.

Brian R. Richardson↗

Pre-Flight Hazardous Gas Assessment Methodology for the Space Launch System

The complexity of the Artemis I liquid rocket propulsion systems produces many sources of hazards during the operation of the vehicle. Pre-flight hazardous gas leakages pose fire and explosion risks to rocket that could potentially lead to loss of the vehicle, mission, and crew. The National Aeronautics and Space Administration (NASA) uses a probability risk assessment strategy to assess the likelihood of the hazard and the consequence should the hazardous situation occur. For high probability hazards that pose a potentially catastrophic consequence to the vehicle, the most effective strategy for reducing the risk is accomplished by engineering and implementing systems that actively mitigate the hazard. A hazards analysis is completed to determine the likelihood and severity of each hazard. These hazard analyses are informed using relevant empirical data and physics-based analytical models. Time-accurate Computational Fluid Dynamics models used to quantify and understand the risks posed to Artemis I due to expulsions of hazardous gas near the vehicle. Several sources of hazardous gas that posed a risk to Artemis I during nominal pre-flight operations are analyzed in this work. The results of the analyses were used to develop flight rationale and make risk acceptance decisions for the Artemis I launch.

Brian R. Richardson↗

Demonstration of a Safety Analysis on a Complex System

For the past 17 years, Professor Leveson and her graduate students have been developing a theoretical foundation for safety in complex systems and building a methodology upon that foundation. The methodology includes special management structures and procedures, system hazard analyses, software hazard analysis, requirements modeling and analysis for completeness and safety, special software design techniques including the design of human-machine interaction, verification, operational feedback, and change analysis. The Safeware methodology is based on system safety techniques that are extended to deal with software and human error. Automation is used to enhance our ability to cope with complex systems. Identification, classification, and evaluation of hazards is done using modeling and analysis. To be effective, the models and analysis tools must consider the hardware, software, and human components in these systems. They also need to include a variety of analysis techniques and orthogonal approaches: There exists no single safety analysis or evaluation technique that can handle all aspects of complex systems. Applying only one or two may make us feel satisfied, but will produce limited results. We report here on a demonstration, performed as part of a contract with NASA Langley Research Center, of the Safeware methodology on the Center-TRACON Automation System (CTAS) portion of the air traffic control (ATC) system and procedures currently employed at the Dallas/Fort Worth (DFW) TRACON (Terminal Radar Approach CONtrol). CTAS is an automated system to assist controllers in handling arrival traffic in the DFW area. Safety is a system property, not a component property, so our safety analysis considers the entire system and not simply the automated components. Because safety analysis of a complex system is an interdisciplinary effort, our team included system engineers, software engineers, human factors experts, and cognitive psychologists.

Leveson, Nancy↗

Flight Computer Processing Avionics for Space Station Microgravity Experiments: A Risk Assessment of Commercial Off-the-Shelf Utilization

NASA/Marshall Space Flight Center (MSFC) is continually looking for ways to reduce the costs and schedule and minimize the technical risks during the development of microgravity programs. One of the more prominent ways to minimize the cost and schedule is to use off-the-shelf hardware (OTS). However, the use of OTS often increases the risk. This paper addresses relevant factors considered during the selection and utilization of commercial off-the-shelf (COTS) flight computer processing equipment for the control of space station microgravity experiments. The paper will also discuss how to minimize the technical risks when using COTS processing hardware. Two microgravity experiments for which the COTS processing equipment is being evaluated for are the Equiaxed Dendritic Solidification Experiment (EDSE) and the Self-diffusion in Liquid Elements (SDLE) experiment. Since MSFC is the lead center for Microgravity research, EDSE and SDLE processor selection will be closely watched by other experiments that are being designed to meet payload carrier requirements. This includes the payload carriers planned for the International Space Station (ISS). The purpose of EDSE is to continue to investigate microstructural evolution of, and thermal interactions between multiple dendrites growing under diffusion controlled conditions. The purpose of SDLE is to determine accurate self-diffusivity data as a function of temperature for liquid elements selected as representative of class-like structures. In 1999 MSFC initiated a Center Director's Discretionary Fund (CDDF) effort to investigate and determine the optimal commercial data bus architecture that could lead to faster, better, and lower cost data acquisition systems for the control of microgravity experiments. As part of this effort various commercial data acquisition systems were acquired and evaluated. This included equipment with various form factors, (3U, 6U, others) and equipment that utilized various bus structures, (VME, PC104, STD bus). This evaluation of hardware was performed in conjunction with a trade study that considered over twenty (20) different factors relevant to the selection of an optimum design approach. These factors included; safety, sizing and timing, radiation hardness and single event upset, power consumption, heat dissipation, size and volume, expected service life, maintainability, heritage, operating systems, requirements for software reuse, availability of compatible interface boards, relative cost, schedule, reliability, EMI/EMC factors, "hot swap" capability, standards for conduction cooling, I/O capabilities, unique carrier requirements and operating system considerations. The approach to evaluate Safety as part of this study included a review of the Preliminary Hazard Analysis (PHA) for each of the experiment designs and a determination of how each hazard could be addressed and eliminated when different processors were selected. This included evaluating various design approaches and trade-offs between fault tolerant designs and fail-safe designs in accordance with NSTS 1700.7B. This will include the results of radiation testing where available. Various operating systems, such as VxWorks, Linux, QNX, and Embedded NT are evaluated and the advantages and disadvantages of their utilization are also addressed. Design implementation strategies for the various operating systems are considered and discussed. This paper presents the results and recommendations from this trade study. Preliminary conclusions from this study are that safety concerns from lack or radiation testing on COTS equipment can be addressed by additional testing and design considerations, the PC104 bus provided adequate I/O for the SDLE and EDSE microgravity experiments, and PC104 bus components offered significant advantages over VME and cPCI for weight and space reductions.

Estes, Howard↗

Assurance of Fault Management: Risk-Significant Adverse Condition Awareness

Fault Management (FM) systems are ranked high in risk-based assessment of criticality within flight software, emphasizing the importance of establishing highly competent domain expertise to provide assurance for NASA projects, especially as spaceflight systems continue to increase in complexity. Insight into specific characteristics of FM architectures seen embedded within safety- and mission-critical software systems analyzed by the NASA Independent Verification Validation (IVV) Program has been enhanced with an FM Technical Reference (TR) suite. Benefits are aimed beyond the IVV community to those that seek ways to efficiently and effectively provide software assurance to reduce the FM risk posture of NASA and other space missions. The identification of particular FM architectures, visibility, and associated IVV techniques provides a TR suite that enables greater assurance that critical software systems will adequately protect against faults and respond to adverse conditions. The role FM has with regard to overall asset protection of flight software systems is being addressed with the development of an adverse condition (AC) database encompassing flight software vulnerabilities.Identification of potential off-nominal conditions and analysis to determine how a system responds to these conditions are important aspects of hazard analysis and fault management. Understanding what ACs the mission may face, and ensuring they are prevented or addressed is the responsibility of the assurance team, which necessarily should have insight into ACs beyond those defined by the project itself. Research efforts sponsored by NASAs Office of Safety and Mission Assurance defined terminology, categorized data fields, and designed a baseline repository that centralizes and compiles a comprehensive listing of ACs and correlated data relevant across many NASA missions. This prototype tool helps projects improve analysis by tracking ACs, and allowing queries based on project, mission type, domain component, causal fault, and other key characteristics. The repository has a firm structure, initial collection of data, and an interface established for informational queries, with plans for integration within the Enterprise Architecture at NASA IVV, enabling support and accessibility across the Agency. The development of an improved workflow process for adaptive, risk-informed FM assurance is currently underway.

Software Verification & Validation↗

Adapting safety requirements analysis to intrusion detection

Several requirements analysis techniques widely used in safety-critical systems are being adapted to support the analysis of secure systems. Perhaps the most relevant system safety techique for Intrusion Detection Systems is hazard analysis.

requirements analysis safety intrusion detection↗

International Space Station (ISS) Low Pressure Intramodule Quick Disconnect Failures

A failure of an ISS intermodule Quick Disconnect (QD) during protoflight vibration testing of ISS regenerative Environmental Control and Life Support (ECLS) hardware led to the discovery of QD design, manufacturing, and test flaws which can yield the male QD susceptible to failure of the secondary housing seal and inadequate housing assembly locking mechanisms. Discovery of this failure had large implications when considering that currently there are 399 similar units on orbit and approximately 1100 units on the ground integrated into flight hardware. Discovery of the nature of the failure required testing and analysis and implementation of a recovery plan requiring part screening and review of element level and project hazard analysis to determine if secondary seals are required. Implementation also involves coordination with the Nodes and MPLM project offices, Regenerative ECLS Project, ISS Payloads, JAXA, ESA, and ISS Logistics and Maintenance.

Lewis, John F.↗

Review of Exploration Systems Development (ESD) Integrated Hazard Development Process: Appendices - Volume 1

The Chief Engineer of the Exploration Systems Development (ESD) Office requested that the NASA Engineering and Safety Center (NESC) perform an independent assessment of the ESD's integrated hazard development process. The focus of the assessment was to review the integrated hazard analysis (IHA) process and identify any gaps/improvements in the process (e.g., missed causes, cause tree completeness, missed hazards). This document contains the outcome of the NESC assessment.

Smiles, Michael D.↗

Review of Exploration Systems Development (ESD) Integrated Hazard Development Process: Volume 2 - Appendices

The Chief Engineer of the Exploration Systems Development (ESD) Office requested that the NASA Engineering and Safety Center (NESC) perform an independent assessment of the ESD's integrated hazard development process. The focus of the assessment was to review the integrated hazard analysis (IHA) process and identify any gaps/improvements in the process (e.g. missed causes, cause tree completeness, missed hazards). This document contains the outcome of the NESC assessment.

Smiles, Michael D.↗

Scoping, Tailoring, and Abstraction Refinement in the Hazard Assessment Process

Hazard assessment is an engineering activity that produces insight into which states of thing being engineered might be hazardous. In aviation contexts, it is often performed for certification credit at both the aircraft and system levels during the early design phase of the system’s lifecycle. However, novel aircraft paradigms such as urban air mobility (UAM) operations might either violate assumptions on which traditional aviation hazard assessment is based or simply possess attributes that would make other approaches more effective. In this paper, we define the key concepts underpinning hazard assessment and identify the limitations and assumptions inherent in hazard analysis. We analyze popular techniques to show how they embody these key concepts. We identify ways in which hazard assessment may be scoped and tailored to an application. And, using worked examples, we discuss how, where, and why such tailoring might be needed, especially in novel contexts.

Aviation Safety↗

COLD-SAT feasibility study safety analysis

The Cryogenic On-orbit Liquid Depot-Storage, Acquisition, and Transfer (COLD-SAT) satellite presents some unique safety issues. The feasibility study conducted at NASA-Lewis desired a systems safety program that would be involved from the initial design in order to eliminate and/or control the inherent hazards. Because of this, a hazards analysis method was needed that: (1) identified issues that needed to be addressed for a feasibility assessment; and (2) identified all potential hazards that would need to be controlled and/or eliminated during the detailed design phases. The developed analysis method is presented as well as the results generated for the COLD-SAT system.

Mchenry, Steven T.↗

Integrated Safety Analysis Teams

Today's complex systems require understanding beyond one person s capability to comprehend. Each system requires a team to divide the system into understandable subsystems which can then be analyzed with an Integrated Hazard Analysis. The team must have both specific experiences and diversity of experience. Safety experience and system understanding are not always manifested in one individual. Group dynamics make the difference between success and failure as well as the difference between a difficult task and a rewarding experience. There are examples in the news which demonstrate the need to connect the pieces of a system into a complete picture. The Columbia disaster is now a standard example of a low consequence hazard in one part of the system; the External Tank is a catastrophic hazard cause for a companion subsystem, the Space Shuttle Orbiter. The interaction between the hardware, the manufacturing process, the handling, and the operations contributed to the problem. Each of these had analysis performed, but who constituted the team which integrated this analysis together? This paper will explore some of the methods used for dividing up a complex system; and how one integration team has analyzed the parts. How this analysis has been documented in one particular launch space vehicle case will also be discussed.

Wetherholt, Jonathan C.↗

Safety and Performance Analysis of the Non-Radar Oceanic/Remote Airspace In-Trail Procedure

This document presents a safety and performance analysis of the nominal case for the In-Trail Procedure (ITP) in a non-radar oceanic/remote airspace. The analysis estimates the risk of collision between the aircraft performing the ITP and a reference aircraft. The risk of collision is only estimated for the ITP maneuver and it is based on nominal operating conditions. The analysis does not consider human error, communication error conditions, or the normal risk of flight present in current operations. The hazards associated with human error and communication errors are evaluated in an Operational Hazards Analysis presented elsewhere.

Carreno, Victor A.↗

MSL DSENDS EDL Analysis and Operations

This paper presents the operations experience of the JPL EDL (Entry, Descent, and Landing) trajectory simulation team, focusing on events in the week before landing and EDL itself. A brief description of the EDL trajectory simulation tool used for targeting and simulation verification analysis will be presented, including a high level discussion of the required modeling. Initialization and output interfaces used for landing hazard analysis will also be covered, along with discussion of real-time EDL event detection using radiometric Doppler data.

Entry, descent, and landing (EDL)↗

Safety Sufficiency for NextGen: Assessment of Selected Existing Safety Methods, Tools, Processes, and Regulations

NextGen is a complex socio-technical system and, in many ways, it is expected to be more complex than the current system. It is vital to assess the safety impact of the NextGen elements (technologies, systems, and procedures) in a rigorous and systematic way and to ensure that they do not compromise safety. In this study, the NextGen elements in the form of Operational Improvements (OIs), Enablers, Research Activities, Development Activities, and Policy Issues were identified. The overall hazard situation in NextGen was outlined; a high-level hazard analysis was conducted with respect to multiple elements in a representative NextGen OI known as OI-0349 (Automation Support for Separation Management); and the hazards resulting from the highly dynamic complexity involved in an OI-0349 scenario were illustrated. A selected but representative set of the existing safety methods, tools, processes, and regulations was then reviewed and analyzed regarding whether they are sufficient to assess safety in the elements of that OI and ensure that safety will not be compromised and whether they might incur intolerably high costs.

Xu, Xidong↗

Database for Safety-Oriented Tracking of Chemicals

SafetyChem is a computer program that maintains a relational database for tracking chemicals and associated hazards at Johnson Space Center (JSC) by use of a Web-based graphical user interface. The SafetyChem database is accessible to authorized users via a JSC intranet. All new chemicals pass through a safety office, where information on hazards, required personal protective equipment (PPE), fire-protection warnings, and target organ effects (TOEs) is extracted from material safety data sheets (MSDSs) and recorded in the database. The database facilitates real-time management of inventory with attention to such issues as stability, shelf life, reduction of waste through transfer of unused chemicals to laboratories that need them, quantification of chemical wastes, and identification of chemicals for which disposal is required. Upon searching the database for a chemical, the user receives information on physical properties of the chemical, hazard warnings, required PPE, a link to the MSDS, and references to the applicable International Standards Organization (ISO) 9000 standard work instructions and the applicable job hazard analysis. Also, to reduce the labor hours needed to comply with reporting requirements of the Occupational Safety and Health Administration, the data can be directly exported into the JSC hazardous- materials database.

Stump, Jacob↗

Operations analysis (study 2.1). Contingency analysis

Future operational concepts for the space transportation system were studied in terms of space shuttle upper stage failure contingencies possible during deployment, retrieval, or space servicing of automated satellite programs. Problems anticipated during mission planning were isolated using a modified 'fault tree' technique, normally used in safety analyses. A comprehensive space servicing hazard analysis is presented which classifies possible failure modes under the catagories of catastrophic collision, failure to rendezvous and dock, servicing failure, and failure to undock. The failure contingencies defined are to be taken into account during design of the upper stage.

Source record↗