SEARCH · Search NASA

Results for “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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 163 records · Page 9

All sources NASA NTRS DOE OSTI

NASA NTRS2003

Certification Processes for Safety-Critical and Mission-Critical Aerospace Software

This document is a quick reference guide with an overview of the processes required to certify safety-critical and mission-critical flight software at selected NASA centers and the FAA. Researchers and software developers can use this guide to jumpstart their understanding of how to get new or enhanced software onboard an aircraft or spacecraft. The introduction contains aerospace industry definitions of safety and safety-critical software, as well as, the current rationale for certification of safety-critical software. The Standards for Safety-Critical Aerospace Software section lists and describes current standards including NASA standards and RTCA DO-178B. The Mission-Critical versus Safety-Critical software section explains the difference between two important classes of software: safety-critical software involving the potential for loss of life due to software failure and mission-critical software involving the potential for aborting a mission due to software failure. The DO-178B Safety-critical Certification Requirements section describes special processes and methods required to obtain a safety-critical certification for aerospace software flying on vehicles under auspices of the FAA. The final two sections give an overview of the certification process used at Dryden Flight Research Center and the approval process at the Jet Propulsion Lab (JPL).

Nelson, Stacy↗

NASA NTRS2003

Certification Processes for Safety-Critical and Mission-Critical Aerospace Software

Nelson, Stacy↗

NASA NTRS2004

Synthesizing Safety Conditions for Code Certification Using Meta-Level Programming

In code certification the code consumer publishes a safety policy and the code producer generates a proof that the produced code is in compliance with the published safety policy. In this paper, a novel viewpoint approach towards an implementational re-use oriented framework for code certification is taken. It adopts ingredients from Necula's approach for proof-carrying code, but in this work safety properties can be analyzed on a higher code level than assembly language instructions. It consists of three parts: (1) The specification language is extended to include generic pre-conditions that shall ensure safety at all states that can be reached during program execution. Actual safety requirements can be expressed by providing domain-specific definitions for the generic predicates which act as interface to the environment. (2) The Floyd-Hoare inductive assertion method is refined to obtain proof rules that allow the derivation of the proof obligations in terms of the generic safety predicates. (3) A meta-interpreter is designed and experimentally implemented that enables automatic synthesis of proof obligations for submitted programs by applying the modified Floyd-Hoare rules. The proof obligations have two separate conjuncts, one for functional correctness and another for the generic safety obligations. Proof of the generic obligations, having provided the actual safety definitions as context, ensures domain-specific safety of program execution in a particular environment and is simpler than full program verification.

Eusterbrock, Jutta↗

NASA NTRS2005

Space-Based Range Safety and Future Space Range Applications

The National Aeronautics and Space Administration Space-Based Telemetry and Range Safety study is a multiphase project to demonstrate the performance, flexibility and cost savings that can be realized by using space-based assets for the Range Safety (global positioning system metric tracking data, flight termination command and range safety data relay) and Range User (telemetry) functions during vehicle launches and landings. Phase 1 included flight testing S-band Range Safety and Range User hardware in 2003 onboard a high-dynamic aircraft platform at Dryden Flight Research Center (Edwards, California) using the NASA Tracking and Data Relay Satellite System as the communications link. The current effort, Phase 2, includes hardware and packaging upgrades to the S-band Range Safety system and development of a high data rate Ku-band Range User system. The enhanced Phase 2 Range Safety Unit provided real-time video for three days during the historic GlobalFlyer (Scaled Composites, Mojave, California) flight in March, 2005. Additional Phase 2 testing will include a sounding rocket test of the Range Safety system and aircraft flight testing of both systems. Future testing will include a flight test on a launch vehicle platform. This report discusses both Range Safety and Range User developments and testing with emphasis on the Range Safety system. The operational concept of a future space-based range is also discussed.

Whiteman, Donald E.↗

NASA NTRS2005

Mitigating Motion Base Safety Issues: The NASA LaRC CMF Implementation

The NASA Langley Research Center (LaRC), Cockpit Motion Facility (CMF) motion base design has taken advantage of inherent hydraulic characteristics to implement safety features using hardware solutions only. Motion system safety has always been a concern and its implementation is addressed differently by each organization. Some approaches rely heavily on software safety features. Software which performs safety functions is subject to more scrutiny making its approval, modification, and development time consuming and expensive. The NASA LaRC's CMF motion system is used for research and, as such, requires that the software be updated or modified frequently. The CMF's customers need the ability to update the simulation software frequently without the associated cost incurred with safety critical software. This paper describes the CMF engineering team's approach to achieving motion base safety by designing and implementing all safety features in hardware, resulting in applications software (including motion cueing and actuator dynamic control) being completely independent of the safety devices. This allows the CMF safety systems to remain intact and unaffected by frequent research system modifications.

Bryant, Richard B., Jr.↗

NASA NTRS2005

Space-Based Range Safety and Future Space Range Applications

The National Aeronautics and Space Administration (NASA) Space-Based Telemetry and Range Safety (STARS) study is a multiphase project to demonstrate the performance, flexibility and cost savings that can be realized by using space-based assets for the Range Safety [global positioning system (GPS) metric tracking data, flight termination command and range safety data relay] and Range User (telemetry) functions during vehicle launches and landings. Phase 1 included flight testing S-band Range Safety and Range User hardware in 2003 onboard a high-dynamic aircraft platform at Dryden Flight Research Center (Edwards, California, USA) using the NASA Tracking and Data Relay Satellite System (TDRSS) as the communications link. The current effort, Phase 2, includes hardware and packaging upgrades to the S-band Range Safety system and development of a high data rate Ku-band Range User system. The enhanced Phase 2 Range Safety Unit (RSU) provided real-time video for three days during the historic Global Flyer (Scaled Composites, Mojave, California, USA) flight in March, 2005. Additional Phase 2 testing will include a sounding rocket test of the Range Safety system and aircraft flight testing of both systems. Future testing will include a flight test on a launch vehicle platform. This paper discusses both Range Safety and Range User developments and testing with emphasis on the Range Safety system. The operational concept of a future space-based range is also discussed.

Whiteman, Donald E.↗

NASA NTRS2005

Implementation of Programmatic Quality and the Impact on Safety

The purpose of this paper is to discuss the implementation of a programmatic quality assurance discipline within the International Space Station Program and the resulting impact on safety. NASA culture has continued to stress safety at the expense of quality when both are extremely important and both can equally influence the success or failure of a Program or Mission. Although safety was heavily criticized in the media after Col~imbiaa, strong case can be made that it was the failure of quality processes and quality assurance in all processes that eventually led to the Columbia accident. Consequently, it is possible to have good quality processes without safety, but it is impossible to have good safety processes without quality. The ISS Program quality assurance function was analyzed as representative of the long-term manned missions that are consistent with the President s Vision for Space Exploration. Background topics are as follows: The quality assurance organizational structure within the ISS Program and the interrelationships between various internal and external organizations. ISS Program quality roles and responsibilities with respect to internal Program Offices and other external organizations such as the Shuttle Program, JSC Directorates, NASA Headquarters, NASA Contractors, other NASA Centers, and International Partner/participants will be addressed. A detailed analysis of implemented quality assurance responsibilities and functions with respect to NASA Headquarters, the JSC S&MA Directorate, and the ISS Program will be presented. Discussions topics are as follows: A comparison of quality and safety resources in terms of staffing, training, experience, and certifications. A benchmark assessment of the lessons learned from the Columbia Accident Investigation (CAB) Report (and follow-up reports and assessments), NASA Benchmarking, and traditional quality assurance activities against ISS quality procedures and practices. The lack of a coherent operational and sustaining quality assurance strategy for long-term manned space flight. An analysis of the ISS waiver processes and the Problem Reporting and Corrective Action (PRACA) process implemented as quality functions. Impact of current ISS Program procedures and practices with regards to operational safety and risk A discussion regarding a "defense-in-depth" approach to quality functions will be provided to address the issue of "integration vs independence" with respect to the roles of Programs, NASA Centers, and NASA Headquarters. Generic recommendations are offered to address the inadequacies identified in the implementation of ISS quality assurance. A reassessment by the NASA community regarding the importance of a "quality culture" as a component within a larger "safety culture" will generate a more effective and value-added functionality that will ultimately enhance safety.

Huls, Dale Thomas↗

NASA NTRS2011

C-Band Airport Surface Communications System Engineering-Initial High-Level Safety Risk Assessment and Mitigation

This document is being provided as part of ITT's NASA Glenn Research Center Aerospace Communication Systems Technical Support (ACSTS) contract: "New ATM Requirements--Future Communications, C-Band and L-Band Communications Standard Development." ITT has completed a safety hazard analysis providing a preliminary safety assessment for the proposed C-band (5091- to 5150-MHz) airport surface communication system. The assessment was performed following the guidelines outlined in the Federal Aviation Administration Safety Risk Management Guidance for System Acquisitions document. The safety analysis did not identify any hazards with an unacceptable risk, though a number of hazards with a medium risk were documented. This effort represents an initial high-level safety hazard analysis and notes the triggers for risk reassessment. A detailed safety hazards analysis is recommended as a follow-on activity to assess particular components of the C-band communication system after the profile is finalized and system rollout timing is determined. A security risk assessment has been performed by NASA as a parallel activity. While safety analysis is concerned with a prevention of accidental errors and failures, the security threat analysis focuses on deliberate attacks. Both processes identify the events that affect operation of the system; and from a safety perspective the security threats may present safety risks.

Zelkin, Natalie↗

NASA NTRS2011

Achieving the Proper Balance Between Crew and Public Safety

A paramount objective of all human-rated launch and reentry vehicle developers is to ensure that the risks to both the crew onboard and the public are minimized within reasonable cost, schedule, and technical constraints. Past experience has shown that proper attention to range safety requirements necessary to ensure public safety must be given early in the design phase to avoid additional operational complexities or threats to the safety of people onboard, and the design engineers must give these requirements the same consideration as crew safety requirements. For human spaceflight, the primary purpose and operational concept for any flight safety system is to protect the public while maximizing the likelihood of crew survival. This paper will outline the policy considerations, technical issues, and operational impacts regarding launch and reentry vehicle failure scenarios where crew and public safety are intertwined and thus addressed optimally in an integrated manner. An overview of existing range and crew safety policy requirements will be presented. Application of these requirements and lessons learned from both the Space Shuttle and Constellation Programs will also be discussed. Using these past programs as examples, the paper will detail operational, design, and analysis approaches to mitigate and balance the risks to people onboard and in the public. Manned vehicle perspectives from the Federal Aviation Administration (FAA) and Air Force organizations that oversee public safety will be summarized as well. Finally, the paper will emphasize the need to factor policy, operational, and analysis considerations into the early design trades of new vehicles to help ensure that both crew and public safety are maximized to the greatest extent possible.

Gowan, John↗

NASA NTRS2011

Application of the Life Safety Code to a Historic Test Stand

NASA has conducted a study to assess alternatives to refurbishing existing launch vehicle modal test facilities as opposed to developing new test facilities to meet the demands of a very fiscally constrained test and evaluation environment. The results of this study showed that Marshall Space Flight Center (MSFC) Test Stand (TS) 4550 could be made compliant, within reasonable cost and schedule impacts, if safety processes and operational limitations were put in place to meet the safety codes and concerns of the Fire Marshall. Trades were performed with key selection criteria to ensure that appropriate levels of occupant safety are incorporated into test facility design modifications. In preparation for the ground vibration tests that were to be performed on the Ares I launch vehicle, the Ares Flight and Integrated Test Office (FITO) organization evaluated the available test facility options, which included the existing mothballed structural dynamic TS4550 used by Apollo and Shuttle, alternative ground vibration test facilities at other locations, and construction of a new dynamic test stand. After an exhaustive assessment of the alternatives, the results favored modifying the TS4550 because it was the lowest cost option and presented the least schedule risk to the NASA Constellation Program for Ares Integrated Vehicle Ground Vibration Test (IVGVT). As the renovation design plans and drawings were being developed for TS4550, a safety concern was discovered the original design for the construction of the test stand, originally built for the Apollo Program and renovated for the Shuttle Program, was completed before NASA s adoption of the currently imposed safety and building codes per National Fire Protection Association Life Safety Code [NFPA 101] and International Building Codes. The initial FITO assessment of the design changes, required to make TS4550 compliant with current safety and building standards, identified a significant cost increase and schedule impact. An effort was launched to thoroughly evaluate the applicable life safety requirements, examine the context in which they were derived, and determine a means by which the TS4550 modifications could be made within budget and on schedule, while still providing the occupants with appropriate levels of safety.

Askins, Bruce↗

NASA NTRS2012

2011 NASA Range Safety Annual Report

Welcome to the 2011 edition of the NASA Range Safety Annual Report. Funded by NASA Headquarters, this report provides a NASA Range Safety overview for current and potential range users. As is typical with odd year editions, this is an abbreviated Range Safety Annual Report providing updates and links to full articles from the previous year's report. It also provides more complete articles covering new subject areas, summaries of various NASA Range Safety Program activities conducted during the past year, and information on several projects that may have a profound impact on the way business will be done in the future. Specific topics discussed and updated in the 2011 NASA Range Safety Annual Report include a program overview and 2011 highlights; Range Safety Training; Range Safety Policy revision; Independent Assessments; Support to Program Operations at all ranges conducting NASA launch/flight operations; a continuing overview of emerging range safety-related technologies; and status reports from all of the NASA Centers that have Range Safety responsibilities. Every effort has been made to include the most current information available. We recommend this report be used only for guidance and that the validity and accuracy of all articles be verified for updates. Once again the web-based format was used to present the annual report. We continually receive positive feedback on the web-based edition and hope you enjoy this year's product as well. As is the case each year, contributors to this report are too numerous to mention, but we thank individuals from the NASA Centers, the Department of Defense, and civilian organizations for their contributions. In conclusion, it has been a busy and productive year. I'd like to extend a personal Thank You to everyone who contributed to make this year a successful one, and I look forward to working with all of you in the upcoming year.

Dumont, Alan G.↗

NASA NTRS2013

Evolution of International Space Station Program Safety Review Processes and Tools

The International Space Station Program at NASA is constantly seeking to improve the processes and systems that support safe space operations. To that end, the ISS Program decided to upgrade their Safety and Hazard data systems with 3 goals: make safety and hazard data more accessible; better support the interconnection of different types of safety data; and increase the efficiency (and compliance) of safety-related processes. These goals are accomplished by moving data into a web-based structured data system that includes strong process support and supports integration with other information systems. Along with the data systems, ISS is evolving its submission requirements and safety process requirements to support the improved model. In contrast to existing operations (where paper processes and electronic file repositories are used for safety data management) the web-based solution provides the program with dramatically faster access to records, the ability to search for and reference specific data within records, reduced workload for hazard updates and approval, and process support including digital signatures and controlled record workflow. In addition, integration with other key data systems provides assistance with assessments of flight readiness, more efficient review and approval of operational controls and better tracking of international safety certifications. This approach will also provide new opportunities to streamline the sharing of data with ISS international partners while maintaining compliance with applicable laws and respecting restrictions on proprietary data. One goal of this paper is to outline the approach taken by the ISS Progrm to determine requirements for the new system and to devise a practical and efficient implementation strategy. From conception through implementation, ISS and NASA partners utilized a user-centered software development approach focused on user research and iterative design methods. The user-centered approach used on the new ISS hazard system utilized focused user research and iterative design methods employed by the Human Computer Interaction Group at NASA Ames Research Center. Particularly, the approach emphasized the reduction of workload associated with document and data management activities so more resources can be allocated to the operational use of data in problem solving, safety analysis, and recurrence control. The methods and techniques used to understand existing processes and systems, to recognize opportunities for improvement, and to design and review improvements are described with the intent that similar techniques can be employed elsewhere in safety operations. A second goal of this paper is to provide and overview of the web-based data system implemented by ISS. The software selected for the ISS hazard systemMission Assurance System (MAS)is a NASA-customized vairant of the open source software project Bugzilla. The origin and history of MAS as a NASA software project and the rationale for (and advantages of) using open-source software are documented elsewhere (Green, et al., 2009).

Ratterman, Christian D.↗

NASA NTRS2024

Survey of Methods for Assessing Safety Compliance of sUAS BVLOS Operations

To ensure the safety of small Unmanned Aircraft System (sUAS) Beyond Line of Sight (BVLOS) operations in the National Airspace System (NAS), the FAA offers a guideline on how sUAS operators can demonstrate compliance with FAA rules, including regulations, advisory circulars, policy statements, and acceptable means of compliance (AMOC), using a formal and top-down approach. According to FAA Advisory Circular 23.2010-1, the AMOC refers to “one method, but not the only method, to show compliance with a regulatory requirement.” It is common for regulations to include a performance and safety standard rather than a detailed design or operation requirement, which allows for flexibility in fulfilling the regulatory requirements while still achieving a predetermined level of safety. This technical report explores existing frameworks for sUAS BVLOS safety analysis. It begins by discussing how sUAS BVLOS operations can be strategically deconflicted and then discusses their hazards. The next step is to establish safety assessment methods commonly used by the aviation industry and the FAA, illustrate how these methods can be applied to several safety-critical air traffic systems, and list collision models that the FAA and industry use. This investigation documents the processes for assessing safety risks in sUAS BVLOS operations and will allow sUAS BVLOS operations to be assessed for safety compliance more efficiently.

sUAS BVLOS Operations↗

NASA NTRSDate not supplied

An in-Time Aviation Safety Management System Concept of Operations and Modernization of the National Airspace System

The National Airspace System (NAS) is growing in complexity of aircraft, missions, and operations. In response, many organizations have published papers and concepts of operations (ConOps) for new and enhanced safety systems. The National Academies’ vision for an In-time Aviation Safety Management System (IASMS) is integral to Federal Aviation Administration (FAA) modernization efforts. The National Aeronautics and Space Administration (NASA) System-Wide Safety (SWS) project is conducting safety research, exploring solutions, and defining the safety needs of future missions, such as Advanced Air Mobility (AAM) and autonomous aircraft operating in a more connected, flexible, and dynamic airspace. IASMS enables and provides a path for bringing FAA’s operational vision to fruition through increasingly automated safety systems that integrate services, functions, and capabilities (SFCs). These SFCs provide the necessary responsiveness to monitor, assess, and mitigate known hazards and emergent risks. This paper describes how safety in today’s air transportation system will need to evolve, identifies key points regarding in-time safety, and explores the criticality of IASMS in the future NAS.

IASMS↗

NASA NTRSDate not supplied

An In-time Aviation Safety Management System Concept of Operations and Modernization of the National Airspace System

Airspace↗

NASA NTRS2014

Industry Initiated Core Safety Attributes for Human Spaceflight for the 7th IAASS Conference

Now that the NASA Commercial Crew Program (CCP) is beginning its full certification contract for crew transportation to the International Space Station (ISS), is it time for industry to embrace a minimum set of core safety attributes? Those attributes can then be evolved into an industry-led set of basic safety standards and requirements. After 50 years of human space travel sponsored by governments, there are two basic conditions that now exist within the international space industry. The first, there is enough of a space-faring history to encourage the space industry to design, develop and operate human spaceflight systems without government contracts for anything other than services. Second, industry is capable of defining and enforcing a set of industry-based safety attributes and standards for human spaceflight to low-Earth orbit (LEO). This paper will explore both of these basic conditions with a focus on the safety attributes and standards. In the United States, the Federal Aviation Administration (FAA) is now starting to dialogue with industry about the basic safety principles and attributes needed for potential future regulatory oversight. This process is not yet formalized and will take a number of years once approval is given to move forward. Therefore, throughout the next few years, it is an excellent time and opportunity for industry to collaborate together and develop the core set of attributes and standards. As industry engages and embraces a common set of safety attributes, then government agencies, like the FAA and NASA can use that industry-based product to strengthen their efforts on a safe commercial spaceflight foundation for the future. As the commercial space industry takes the lead role in establishing core safety attributes, and then enforcing those attributes, the entire planet can move away from governmental control of design and development and let industry expand safe and successful space operations in LEO. At that point the governmental agencies can focus on oversight of the industries' defined standards and enforcement for common welfare of the space-faring populous and overall public safety.

crew transportation↗

NASA NTRS2014

Querying Safety Cases

Querying a safety case to show how the various stakeholders' concerns about system safety are addressed has been put forth as one of the benefits of argument-based assurance (in a recent study by the Health Foundation, UK, which reviewed the use of safety cases in safety-critical industries). However, neither the literature nor current practice offer much guidance on querying mechanisms appropriate for, or available within, a safety case paradigm. This paper presents a preliminary approach that uses a formal basis for querying safety cases, specifically Goal Structuring Notation (GSN) argument structures. Our approach semantically enriches GSN arguments with domain-specific metadata that the query language leverages, along with its inherent structure, to produce views. We have implemented the approach in our toolset AdvoCATE, and illustrate it by application to a fragment of the safety argument for an Unmanned Aircraft System (UAS) being developed at NASA Ames. We also discuss the potential practical utility of our query mechanism within the context of the existing framework for UAS safety assurance.

Safety Case↗

NASA NTRS2017

Technology and Tool Development to Support Safety and Mission Assurance

The Assurance Case approach is being adopted in a number of safety-mission-critical application domains in the U.S., e.g., medical devices, defense aviation, automotive systems, and, lately, civil aviation. This paradigm refocuses traditional, process-based approaches to assurance on demonstrating explicitly stated assurance goals, emphasizing the use of structured rationale, and concrete product-based evidence as the means for providing justified confidence that systems and software are fit for purpose in safely achieving mission objectives. NASA has also been embracing assurance cases through the concepts of Risk Informed Safety Cases (RISCs), as documented in the NASA System Safety Handbook, and Objective Hierarchies (OHs) as put forth by the Agency's Office of Safety and Mission Assurance (OSMA). This talk will give an overview of the work being performed by the SGT team located at NASA Ames Research Center, in developing technologies and tools to engineer and apply assurance cases in customer projects pertaining to aviation safety. We elaborate how our Assurance Case Automation Toolset (AdvoCATE) has not only extended the state-of-the-art in assurance case research, but also demonstrated its practical utility. We have successfully developed safety assurance cases for a number of Unmanned Aircraft Systems (UAS) operations, which underwent, and passed, scrutiny both by the aviation regulator, i.e., the FAA, as well as the applicable NASA boards for airworthiness and flight safety, flight readiness, and mission readiness. We discuss our efforts in expanding AdvoCATE capabilities to support RISCs and OHs under a project recently funded by OSMA under its Software Assurance Research Program. Finally, we speculate on the applicability of our innovations beyond aviation safety to such endeavors as robotic, and human spaceflight.

Mission Assuranc↗