Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “System safety”

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 685 records · Page 38

Internal Architecture of the Common Habitat

The core stage liquid oxygen tank of the Space Launch System can be manufactured as a habitat instead of as a propellant tank, with a common design such that it is equally suitable for use in 0g, 1/6g, 3/8g, 1g, or variable artificial gravity. This Common Habitat can be the central element of a human spaceflight architecture that encompasses the Moon, Mars, and other destinations within the inner solar system. The Common Habitat is specifically used within an alternative architecture study (that is not part of the current NASA baseline) as the core habitation element within a Lunar Basecamp, Mars Basecamp, and the Deep Space Exploration Vehicle. The Common Habitat internal architecture applies a design philosophy to separate crew functions according to deck. The lower deck is reserved for private functions. It includes eight private crew quarters and four waste and hygiene clusters – each with a private waste management compartment, private full body hygiene compartment, and foyer/clothes changing area. The mid deck is primarily allocated to mission-related working functions. It includes an exercise facility, fabrication / maintenance / repair facility, physical science laboratory (physics, geology, and astronomy), and life science laboratory (biology and human research). The mid deck also has four external hatches, clocked one every 90 degrees, centered on the vehicle vertical centerline. Each hatch has a 60-inch tall by 40-inch wide opening with the mid deck floor 16 inches below the bottom lip of the hatch opening. The upper deck is primarily allocated to group or social functions. It includes a large galley, wardroom with projector and display screen, plant growth chambers, bulk stowage, command and control station, medical facility, hygiene compartment, and vehicle subsystems. A Vertical Translation System, based in part on results from a GrabCAD public challenge, enables crew and equipment traverse between habitat decks in 0g, 1/6g, 3/8g, and 1g. A 40-inch by 60-inch vertical translation corridor ensures that anything that can fit through the external hatches can also be moved from deck to deck. The system includes three component systems: a deploying floor to safety barrier system that folds down to become a traversable floor when vertical translation is not in use and deploys to become a safety barrier during vertical translations; a folding ladder that stows in the ceiling when not in use; and an elevator platform that can attach to the ladder for cargo or incapacitated crew member transport. This system is complemented by a Horizontal Translation System, also based in part on the same GrabCAD challenge, provides for horizontal crew translation in microgravity but requires no vehicle reconfiguration for fractional or whole gravity operation. It relies primarily on gecko-inspired grippers, originally developed at Stanford and NASA JPL, attached to footwear to enable crew to emulate walking. Some handrails are also strategically placed throughout the Common Habitat to aid translation in both gravity and microgravity environments.

Common Habitat↗

2006 NASA Range Safety Annual Report

Throughout 2006, Range Safety was involved in a number of exciting and challenging activities and events, from developing, implementing, and supporting Range Safety policies and procedures-such as the Space Shuttle Launch and Landing Plans, the Range Safety Variance Process, and the Expendable Launch Vehicle Safety Program procedures-to evaluating new technologies. Range Safety training development is almost complete with the last course scheduled to go on line in mid-2007. Range Safety representatives took part in a number of panels and councils, including the newly formed Launch Constellation Range Safety Panel, the Range Commanders Council and its subgroups, the Space Shuttle Range Safety Panel, and the unmanned aircraft systems working group. Space based range safety demonstration and certification (formerly STARS) and the autonomous flight safety system were successfully tested. The enhanced flight termination system will be tested in early 2007 and the joint advanced range safety system mission analysis software tool is nearing operational status. New technologies being evaluated included a processor for real-time compensation in long range imaging, automated range surveillance using radio interferometry, and a space based range command and telemetry processor. Next year holds great promise as we continue ensuring safety while pursuing our quest beyond the Moon to Mars.

TenHaken, Ron↗

NASA Research to Expand UAS Operations for Disaster Response

Natural disasters can result in the loss of life and cost governments and private industry billions to recover each year. Over the past decade the rate and severity of natural disasters such as wildfires and hurricanes have resulted in increasingly negative impacts to communities, public health, natural ecosystems, and the economy. To help reduce these impacts, NASA’s Aeronautics Research Mission Directorate is working to advance technologies and enable the safe and efficient inclusion of novel aviation applications to better assist in disaster response. To execute on these efforts, NASA’s Advanced Capabilities for Emergency Response Operations (ACERO) and System-Wide Safety (SWS) projects have developed coordinated strategic research plans focused on aviation operations for disaster response. The ACERO project will be a multi-year effort that focuses on enabling the use of uncrewed aircraft systems (UAS) to improve firefighter safety and efficiency and enable the use of UAS to conduct new missions such as logistics and aerial suppression. The ACERO project will demonstrate technologies that support the Second Shift concept, enabling UAS and ground technologies to support aerial suppression in degraded visual conditions (e.g., heavy smoke, nighttime). The SWS project will be a multi-year effort that focuses on addressing the key safety barriers that are preventing the authorization of UAS operations in a variety of increasingly complex disaster response applications: post-hurricane response, medical courier, and urban disaster response. The SWS project will demonstrate an In-Time Aviation Safety Management System (IASMS) designed to effectively monitor, assess, and mitigate safety risks associated with hazards to UAS operations for disaster response. This paper will provide a deeper insight into NASA’s research and development plans and discuss how solutions developed in partnership with industry stakeholders and federal agencies will improve disaster response across the globe.

disaster response↗

Exploring Methods to Collect and Analyze Data on Human Contributions to Aviation Safety: A Panel Discussion

Focusing on undesired operator behaviors is pervasive in system design and safety management cultures in aviation. This focus limits the data that are collected, the questions that are asked during data analysis, and therefore our understanding of what operators do in everyday work. Human performance represents a significant source of aviation safety data that includes both desired and undesired actions. When safety is characterized only in terms of errors and failures, the vast majority of human impacts on system safety and performance are ignored. The outcomes of safety data analyses dictate what is learned from those data, which in turn informs safety policies and safety-related decision making. When learning opportunities are systematically restricted by focusing only on rare failure events, not only do we learn less (and less often), but we can draw misleading conclusions by relying on a non-representative sample of human performance data. Changes in how we define and think about safety can highlight new opportunities for collection and analysis of safety-relevant data. Developing an integrated safety picture to better inform safety-related decision making and policies depends upon identifying, collecting, and interpreting safety-producing behaviors in addition to safety-reducing behaviors. Opportunities and challenges in collecting and analyzing the largely unexploited data on desired, safety-producing operator behaviors are discussed.

Aviation Safety↗

Exploring Methods to Collect and Analyze Data on Human Contributions to Aviation Safety: A Panel Discussion

Focusing on undesired operator behaviors is pervasive in system design and safety management cultures in aviation. This focus limits the data that are collected, the questions that are asked during data analysis, and therefore our understanding of what operators do in everyday work. Human performance represents a significant source of aviation safety data that includes both desired and undesired actions. When safety is characterized only in terms of errors and failures, the vast majority of human impacts on system safety and performance are ignored. The outcomes of safety data analyses dictate what is learned from those data, which in turn informs safety policies and safety-related decision making. When learning opportunities are systematically restricted by focusing only on rare failure events, not only do we learn less (and less often), but we can draw misleading conclusions by relying on a non-representative sample of human performance data. Changes in how we define and think about safety can highlight new opportunities for collection and analysis of safety-relevant data. Developing an integrated safety picture to better inform safety-related decision making and policies depends upon identifying, collecting, and interpreting safety producing behaviors in addition to safety reducing behaviors. The panel will discuss opportunities and challenges in collecting and analyzing the largely unexploited data on desired, safety-producing operator behaviors.

aviation safety↗

A Probabilistic Approach of Incorporating Safety and Reliability in System Designs for a Manned Mission to Mars

Conceptual stages in mission design often lack the input of quantitative safety and reliability assessments, simply because failure rates or other data are not yet available for systems that have not yet been designed. Absence of such data should not, however, prevent the development of a quantitative risk models with placeholders for missing data. Functions (that is, actions the systems must perform) in mission design will eventually require system probabilities of success, and there could be much learned from surrogate data, adequately bounded in uncertainty, used in a large event tree model of a complex mission.

Railsback, Jan W.↗

Testing a Run-Time Assurance Framework Coupled with Integrated Risk Mitigation Capabilities for Autonomous Urban UAS Flights

The In-Time Aviation Safety Management System (IASMS) Concept of Operations (ConOps) envisions new capabilities to monitor, assess, and mitigate flight safety risks. Systems will be tailored to mission type, vehicle/equipage type, operational environment, and safety risk tolerance. Within an IASMS framework, several capabilities may be implemented spanning three operational phases (pre-flight, in-flight, and post-flight/off-line); and consisting of lower level functions and information services which may reside onboard the aircraft, on third-party server(s), and/or on ground/operator station(s). Each capability will be designed to produce and disseminate safety-relevant information; perform detection, diagnosis, and prediction of unsafe situations; and/or execute mitigation actions when hazardous events warrant such changes. This paper focuses on recent testing of airborne capabilities that demonstrate inflight aspects of the overarching concept for autonomous unmanned aircraft systems (UAS) operations in urban environments. A flight test architecture is described that applies run-time assurance principles (e.g., executes independent of the unassured autopilot), real-time risk assessment, and a technique to execute contingencies if necessary either automatically or via pilot intervention. Several tests using small UAS were conducted to verify the assured in-flight risk mitigation capability. The paper draws significantly from a larger NASA technical report and recent prior conference papers, providing additional details. Data is analyzed for two representative flights to illustrate the performance for various sequential and simultaneous hazards used during testing. During each automated flight, several hazards are encountered at various points along the flight path. At each point, the hazard is mitigated by the system, with the vehicle then continuing to subsequent points. The paper concludes with lessons-learned regarding relevant aspects of the overarching IASMS concept and how it may be updated and further advanced in the future.

population activity↗

Reliability and quality assurance on the MOD 2 wind system

The Safety, Reliability, and Quality Assurance (R&QA) approach developed for the largest wind turbine generator, the Mod 2, is described. The R&QA approach assures that the machine is not hazardous to the public or to the operating personnel, is operated unattended on a utility grid, demonstrates reliable operation, and helps establish the quality assurance and maintainability requirements for future wind turbine projects. The significant guideline consisted of a failure modes and effects analysis (FMEA) during the design phase, hardware inspections during parts fabrication, and three simple documents to control activities during machine construction and operation.

Mason, W. E. B.↗

Propulsion safety almost equals mission safety

Propulsion system hardware and monitoring/control software constitute a given manned or unmanned aerospace system's primary risk-management issue. The present inquiry into the reasons for this dominance attempts to identify development routes to the reduction of propulsion-related management risk issues. A 'life management plan' for propulsion systems would give attention to service life requirements, criteria for the monitoring and evaluation of useful life, a method for the tracking of service life, criteria for hardware reusability and operations inspection, and hardware preassembly screening practices.

Roth, Gilbert L.↗

Systems Analysis of NASA Aviation Safety Program: Final Report

A three-month study (February to April 2010) of the NASA Aviation Safety (AvSafe) program was conducted. This study comprised three components: (1) a statistical analysis of currently available civilian subsonic aircraft data from the National Transportation Safety Board (NTSB), the Federal Aviation Administration (FAA), and the Aviation Safety Information Analysis and Sharing (ASIAS) system to identify any significant or overlooked aviation safety issues; (2) a high-level qualitative identification of future safety risks, with an assessment of the potential impact of the NASA AvSafe research on the National Airspace System (NAS) based on these risks; and (3) a detailed, top-down analysis of the NASA AvSafe program using an established and peer-reviewed systems analysis methodology. The statistical analysis identified the top aviation "tall poles" based on NTSB accident and FAA incident data from 1997 to 2006. A separate examination of medical helicopter accidents in the United States was also conducted. Multiple external sources were used to develop a compilation of ten "tall poles" in future safety issues/risks. The top-down analysis of the AvSafe was conducted by using a modification of the Gibson methodology. Of the 17 challenging safety issues that were identified, 11 were directly addressed by the AvSafe program research portfolio.

Jones, Sharon M.↗

Early Warning: Development of Confidential Incident Reporting Systems

Accidents hardly ever happen without warning. The combination, or sequence, of failures and mistakes that cause an accident may indeed be unique but the individual failures and mistakes rarely are. In the USA in 1974 the crews on two different aircraft misunderstood the same aeronautical chart and descended towards their destination dangerously early towards a mountain. The first crew were in good weather conditions and could see the mountain and resolved their misinterpretation of the chart. The second crew six weeks later were not so lucky. In cloud they had no clues to point out their mistake nor the presence of the mountain. The resulting crash and the ensuing inquiry, which brought to light the previous incident, shocked the country but gave it the impetus to instigate a safety reporting system. This system eventually became the NASA's Aviation Safety Reporting System (ASRS). The programme collects incident reports from pilots, controllers, mechanics, cabin attendants and many others involved in aviation operations. By disseminating this safety information the ASRS has helped enormously to give US airlines and airspace the highest safety standards. Accident prevention is a goal sought by everyone in the aviation industry and establishing effective incident reporting programmes can go a long way toward achieving that goal. This article will describe the steps and issues required to establish an incident reporting system. The authors summarize the lessons learned from the ASRS, now in its twentieth year of operation and from the Confidential Human Factors Reporting (HER) Programme run by British Airways, an airline that is a recognized world leader in safety reporting and analysis. The differences between government and airline operation of confidential safety reporting systems will be addressed.

OLeary, Mike J.↗

Overview of Threats and Failure Models for Safety-Relevant Computer-Based Systems

This document presents a high-level overview of the threats to safety-relevant computer-based systems, including (1) a description of the introduction and activation of physical and logical faults; (2) the propagation of their effects; and (3) function-level and component-level error and failure mode models. These models can be used in the definition of fault hypotheses (i.e., assumptions) for threat-risk mitigation strategies. This document is a contribution to a guide currently under development that is intended to provide a general technical foundation for designers and evaluators of safety-relevant systems.

Torres-Pomales, Wilfredo↗

In-Time Safety Management for Part 139 Airports

Today’s airports are complex multi-faceted ecosystems. Currently, of the 517 certificated airports, 270 are required to use safety management systems (SMSs) to identify and mitigate known hazards and emergent risks and to voluntarily share safety data with commercial operators and tenants. Airports manage a wide variety of hazards. These traffic hubs have direct responsibilities, such as removing foreign object debris from runways and taxiways and configuring runways to help prevent against incursions and tail strikes during takeoff. To ensure safety in the future NAS, the National Academies recommended an In-time Aviation Safety Management System (IASMS). An IASMS will employ services, functions, and capabilities (SFCs) to identify and mitigate hazards that are proactively and predictively managed based on data analytics of detected anomalies, precursors, and trends. SFCs would scale with airport complexity and environmental conditions using increasingly automated systems to respond proactively to hazards and, by using integrated data sources and predictive safety analytical methods, discover new, never before seen risks.

IASMS↗

Formal Methods in the Development of Highly Assured Software for Unmanned Aircraft Systems

In traditional software development methodologies, operational and functional requirements of systems are often specified in structured natural language notations. These restricted notations provide good documentation support, but only provide limited support for semantic analysis. These notations are generally not rich enough to unambiguously specify the requirements of safety-critical systems that, for example, involve complex numerical computations or that interact with the physical environment. Examples of these safety-critical systems are autonomous vehicles such as unmanned aircraft systems. This talk advocates the use of expressive formal logics, such as higher-order logic, to specify the operational and functional requirement of unmanned systems and to prove the correctness of these requirements. Semantic analysis of requirements written in higher-order logic is supported through the use of interactive theorem provers. Formal models serve as ideal reference implementations of functional requirements. Hence, formal logics enable software validation techniques where software implementations can be checked against functional requirements in a mechanical way. The Formal Methods group in the Safety-Critical Avionics Systems Branch at NASA Langley Research Center has conducted research on the development and application of formal verification techniques to safety-critical applications of interest to NASA for more than 30 years. This talk illustrates the use of formal methods in the development of highly-assured autonomous unmanned aircraft systems.

Formal Methods↗

Architecting Safer Autonomous Aviation Systems

The aviation literature gives relatively little guidance to practitioners about the specifics of architecting systems for safety, particularly the impact of architecture on allocating safety requirements, or the relative ease of system assurance resulting from system or subsystem level architectural choices. As an exemplar, this paper considers common architectural patterns used within traditional aviation systems and explores their safety and safety assurance implications when applied in the context of integrating artificial intelligence (AI) and machine learning (ML) based functionality. Considering safety as an architectural property, we discuss both the allocation of safety requirements and the architectural trade-offs involved early in the design lifecycle. This approach could be extended to other assured properties, similar to safety, such as security. We conclude with a discussion of the safety considerations that emerge in the context of candidate architectural patterns that have been proposed in the recent literature for enabling autonomy capabilities by integrating AI and ML. A recommendation is made for the generation of a property-driven architectural pattern catalogue.

Architecture patterns↗

Architecting Safer Autonomous Aviation Systems

The aviation literature gives relatively little guidance to practitioners about the specifics of architecting systems for safety, particularly the impact of architecture on allocating safety requirements, or the relative ease of system assurance resulting from system or subsystem level architectural choices. As an exemplar, this paper considers common architectural patterns used within traditional aviation systems and explores their safety and safety assurance implications when applied in the context of integrating artificial intelligence (AI) and machine learning (ML) based functionality. Considering safety as an architectural property, we discuss both the allocation of safety requirements and the architectural trade-offs involved early in the design lifecycle. This approach could be extended to other assured properties, similar to safety, such as security. We conclude with a discussion of the safety considerations that emerge in the context of candidate architectural patterns that have been proposed in the recent literature for enabling autonomy capabilities by integrating AI and ML. A recommendation is made for the generation of a property-driven architectural pattern catalogue.

Architecture patterns↗

In-space propellant logistics and safety

Preliminary guidelines for the basic delivery system and safety aspects of the space shuttle configuration in connection with the transport, handling, storage, and transfer of propellants are developed. It is shown that propellants are the major shuttle space load and influence shuttle traffic modeling significantly.

Source record↗

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.↗