Search NASA⌕ Search

SEARCH · Search NASA

Results for “safety certification”

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 37 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRS1997

Fatigue Reliability of Gas Turbine Engine Structures

The results of an investigation are described for fatigue reliability in engine structures. The description consists of two parts. Part 1 is for method development. Part 2 is a specific case study. In Part 1, the essential concepts and practical approaches to damage tolerance design in the gas turbine industry are summarized. These have evolved over the years in response to flight safety certification requirements. The effect of Non-Destructive Evaluation (NDE) methods on these methods is also reviewed. Assessment methods based on probabilistic fracture mechanics, with regard to both crack initiation and crack growth, are outlined. Limit state modeling techniques from structural reliability theory are shown to be appropriate for application to this problem, for both individual failure mode and system-level assessment. In Part 2, the results of a case study for the high pressure turbine of a turboprop engine are described. The response surface approach is used to construct a fatigue performance function. This performance function is used with the First Order Reliability Method (FORM) to determine the probability of failure and the sensitivity of the fatigue life to the engine parameters for the first stage disk rim of the two stage turbine. A hybrid combination of regression and Monte Carlo simulation is to use incorporate time dependent random variables. System reliability is used to determine the system probability of failure, and the sensitivity of the system fatigue life to the engine parameters of the high pressure turbine. 'ne variation in the primary hot gas and secondary cooling air, the uncertainty of the complex mission loading, and the scatter in the material data are considered.

Cruse, Thomas A.↗
NASA NTRS2000

International Agreement on Planetary Protection

The maintenance of a NASA policy, is consistent with international agreements. The planetary protection policy management in OSS, with Field Center support. The advice from internal and external advisory groups (NRC, NAC/Planetary Protection Task Force). The technology research and standards development in bioload characterization. The technology research and development in bioload reduction/sterilization. This presentation focuses on: forward contamination - research on the potential for Earth life to exist on other bodies, improved strategies for planetary navigation and collision avoidance, and improved procedures for sterile spacecraft assembly, cleaning and/or sterilization; and backward contamination - development of sample transfer and container sealing technologies for Earth return, improvement in sample return landing target assessment and navigation strategy, planning for sample hazard determination requirements and procedures, safety certification, (liaison to NEO Program Office for compositional data on small bodies), facility planning for sample recovery system, quarantine, and long-term curation of 4 returned samples.

Source record↗
NASA NTRS2004

Monitoring the Performance of a Neuro-Adaptive Controller

Traditional control has proven to be ineffective to deal with catastrophic changes or slow degradation of complex, highly nonlinear systems like aircraft or spacecraft, robotics, or flexible manufacturing systems. Control systems which can adapt toward changes in the plant have been proposed as they offer many advantages (e.g., better performance, controllability of aircraft despite of a damaged wing). In the last few years, use of neural networks in adaptive controllers (neuro-adaptive control) has been studied actively. Neural networks of various architectures have been used successfully for online learning adaptive controllers. In such a typical control architecture, the neural network receives as an input the current deviation between desired and actual plant behavior and, by on-line training, tries to minimize this discrepancy (e.g.; by producing a control augmentation signal). Even though neuro-adaptive controllers offer many advantages, they have not been used in mission- or safety-critical applications, because performance and safety guarantees cannot b e provided at development time-a major prerequisite for safety certification (e.g., by the FAA or NASA). Verification and Validation (V&V) of an adaptive controller requires the development of new analysis techniques which can demonstrate that the control system behaves safely under all operating conditions. Because of the requirement to adapt toward unforeseen changes during operation, i.e., in real time, design-time V&V is not sufficient.

Schumann, Johann↗
NASA NTRS2005

Remotely Operated Aircraft (ROA) Impact on the National Airspace System (NAS) Work Package, 2005: Composite Report on FAA Flight Plan and Operational Evaluation Plan. Version 7.0

The purpose of this document is to present the findings that resulted from a high-level analysis and evaluation of the following documents: (1) The OEP (Operational Evolution Plan) Version 7 -- a 10-year plan for operational improvements to increase capacity and efficiency in U.S. air travel and transport and other use of domestic airspace. The OEP is the FAA commitment to operational improvements. It is outcome driven, with clear lines of accountability within FAA organizations. The OEP concentrates on operational solutions and integrates safety, certification, procedures, staffing, equipment, avionics and research; (2) The Draft Flight Plan 2006 through 2010 -- a multi-year strategic effort, setting a course for the FAA through 2001, to provide the safest and most efficient air transportation system in the world; (3) The NAS System Architecture Version 5 -- a blueprint for modernizing the NAS and improving NAS services and capabilities through the year 2015; and (4) The NAS-SR-1000 System Requirements Specification (NASSRS) -- a compilation of requirements which describe the operational capabilities for the NAS. The analysis is particularly focused on examining the documents for relevance to existing and/or planned future UAV operations. The evaluation specifically focuses on potential factors that could materially affect the development of a commercial ROA industry, such as: (1) Design limitations of the CNS/ATM system, (2) Human limitations, The information presented was taken from program specifications or program office lead personnel.

Source record↗
NASA NTRS2003

Lessons Learned from Mir - A Payload Perspective

Among the principal objectives of the Phase 1 NASA/Mir program were for the United States to gain experience working with an international partner, to gain working experience in long-duration space flight, and to gain working experience in planning for and executing research on a long-duration space platform. The Phase 1 program was to provide to the US early experience prior to the construction and operation of the International Space Station (Phase 2 and 3). While it can be argued that Mir and ISS are different platforms and that programmatically Phase 1 and ISS are organized differently, it is also clear that many aspects of operating a long-duration research program are platform independent. This can be demonstrated by a review of lessons learned from Skylab, a US space station program of the mid-1970's, many of which were again "learned" on Mir and are being "learned" on ISS. Among these are optimum crew training strategies, on-orbit crew operations, ground support, medical operations and crew psychological support, and safety certification processes

Uri, John J.↗
NASA NTRS2014

Space Shuttle Boundary Layer Transition Flight Experiment Ground Testing Overview

In support of the Boundary Layer Transition (BLT) Flight Experiment (FE) Project in which a manufactured protuberance tile was installed on the port wing of Space Shuttle Orbiter Discovery for STS-119, STS- 128, STS-131 and STS-133 as well as Space Shuttle Orbiter Endeavour for STS-134, a significant ground test campaign was completed. The primary goals of the test campaign were to provide ground test data to support the planning and safety certification efforts required to fly the flight experiment as well as validation for the collected flight data. These test included Arcjet testing of the tile protuberance, aerothermal testing to determine the boundary layer transition behavior and resultant surface heating and planar laser induced fluorescence (PLIF) testing in order to gain a better understanding of the flow field characteristics associated with the flight experiment. This paper provides an overview of the BLT FE Project ground testing. High-level overviews of the facilities, models, test techniques and data are presented, along with a summary of the insights gained from each test.

Karen T Berger↗
NASA NTRS2020

Urban Air Mobility (UAM) Working Groups

The NASA Aeronautics Research Mission Directorate (ARMD) is bringing together public, private, and academic organizations to collaborate with NASA in Urban Air Mobility (UAM) working groups. The primary purpose of the working groups is to accelerate the development of safe, high-volume UAM flight operations in the existing and anticipated future national airspace system. In coordination with the Grand Challenge series, industry developments and other ARMD efforts, these working groups will contribute to the enablement of UAM markets. Working group activities will seek to align the community on concepts to enable UAM, including communicating industry demonstrations and R&D priorities. The collaborative efforts will facilitate the identification of critical parameters and standards necessary to develop the framework and approach for safety, certification, airspace, aircraft concepts, technologies, and architectures. The realization of the UAM vision will be possible only though the efforts and contributions of multiple stakeholders, each possessing the necessary authority, expertise, and/or resources to fulfill a critical role in UAM's development, approval, and implementation. The applicable participants will become integral to the UAM working groups and will provide a platform for those stakeholders to collaborate and impact the overall ecosystem.

Kopardekar, Parimal H.↗
NASA NTRS2014

TPSAS-NF1676L-19423-DND

In support of the Boundary Layer Transition (BLT) Flight Experiment (FE) Project in which a manufactured protuberance tile was installed on the port wing of Space Shuttle Orbiter Discovery for STS-119, STS-128, STS-131 and STS-133 as well as Space Shuttle Endeavour for STS-134, a significant wind tunnel test campaign was completed. The primary goals of the test campaign were to provide ground test data to support the planning and safety certification efforts required to fly the flight experiment as well as validation for the collected flight data. These test included Arcjet testing of the tile protuberance, aerothermal testing to determine the boundary layer transition behavior and resultant surface heating and planar laser induced fluorescence (PLIF) testing in order to gain a better understanding of the flow field characteristics of the flight experiment. This paper provides an overview of the BLT FE Project ground testing. High-level overviews of the facilities, models, test techniques and data are presented, along with a summary of the insights gained from each test.

Karen T Berger↗
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

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 NTRS2016

Certification Strategies using Run-Time Safety Assurance for Part 23 Autopilot Systems

Part 23 aircraft operation, and in particular general aviation, is relatively unsafe when compared to other common forms of vehicle travel. Currently, there exists technologies that could increase safety statistics for these aircraft; however, the high burden and cost of performing the requisite safety critical certification processes for these systems limits their proliferation. For this reason, many entities, including the Federal Aviation Administration, NASA, and the US Air Force, are considering new options for certification for technologies that will improve aircraft safety. Of particular interest, are low cost autopilot systems for general aviation aircraft, as these systems have the potential to positively and significantly affect safety statistics. This paper proposes new systems and techniques, leveraging run-time verification, for the assurance of general aviation autopilot systems, which would be used to supplement the current certification process and provide a viable path for near-term low-cost implementation. In addition, discussions on preliminary experimentation and building the assurance case for a system, based on these principles, is provided.

automatic collision avoidance↗
NASA NTRS2012

Certification of Safety-Critical Software Under DO-178C and DO-278A

The RTCA has recently released DO-178C and DO-278A as new certification guidance for the production of airborne and ground-based air traffic management software, respectively. Additionally, RTCA special committee SC-205 has also produced, at the same time, five other companion documents. These documents are RTCA DO-248C, DO-330, DO-331, DO- 332, and DO-333. These supplements address frequently asked questions about software certification, provide guidance on tool qualification requirements, and illustrate the modifications recommended to DO-178C when using model-based software design, object oriented programming, and formal methods. The objective of this paper is to first explain the relationship of DO-178C to the former DO-178B in order to give those familiar with DO- 178B an indication of what has been changed and what has not been changed. With this background, the relationship of DO-178C and DO-278 to the new DO-278A document for ground-based software development is shown. Last, an overview of the new guidance contained in the tool qualification document and the three new supplements to DO-178C and DO-278A is presented. For those unfamiliar with DO-178B, this paper serves to provide an entry point to this new certification guidance for airborne and ground-based CNS/ATM software certification.

Jacklin, Stephen A.↗
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 NTRS2004

JDD, Inc. Database

JDD Inc, is a maintenance and custodial contracting company whose mission is to provide their clients in the private and government sectors "quality construction, construction management and cleaning services in the most efficient and cost effective manners, (JDD, Inc. Mission Statement)." This company provides facilities support for Fort Riley in Fo,rt Riley, Kansas and the NASA John H. Glenn Research Center at Lewis Field here in Cleveland, Ohio. JDD, Inc. is owned and operated by James Vaughn, who started as painter at NASA Glenn and has been working here for the past seventeen years. This summer I worked under Devan Anderson, who is the safety manager for JDD Inc. in the Logistics and Technical Information Division at Glenn Research Center The LTID provides all transportation, secretarial, security needs and contract management of these various services for the center. As a safety manager, my mentor provides Occupational Health and Safety Occupation (OSHA) compliance to all JDD, Inc. employees and handles all other issues (Environmental Protection Agency issues, workers compensation, safety and health training) involving to job safety. My summer assignment was not as considered "groundbreaking research" like many other summer interns have done in the past, but it is just as important and beneficial to JDD, Inc. I initially created a database using a Microsoft Excel program to classify and categorize data pertaining to numerous safety training certification courses instructed by our safety manager during the course of the fiscal year. This early portion of the database consisted of only data (training field index, employees who were present at these training courses and who was absent) from the training certification courses. Once I completed this phase of the database, I decided to expand the database and add as many dimensions to it as possible. Throughout the last seven weeks, I have been compiling more data from day to day operations and been adding the information to the database. It now consists of seven different categories of data (carpet cleaning, forms, NASA Event Schedules, training certifications, wall and vent cleaning, work schedules, and miscellaneous) . I also did some field inspecting with the supervisors around the site and was present at all of the training certification courses that have been scheduled since June 2004. My future outlook for the JDD, Inc. database is to have all of company s information from future contract proposals, weekly inventory, to employee timesheets all in this same database.

Miller, David A., Jr.↗
NASA NTRS2002

NASA/Navy Benchmarking Exchange (NNBE). Volume 1. Interim Report. Navy Submarine Program Safety Assurance

The NASA/Navy Benchmarking Exchange (NNBE) was undertaken to identify practices and procedures and to share lessons learned in the Navy's submarine and NASA's human space flight programs. The NNBE focus is on safety and mission assurance policies, processes, accountability, and control measures. This report is an interim summary of activity conducted through October 2002, and it coincides with completion of the first phase of a two-phase fact-finding effort.In August 2002, a team was formed, co-chaired by senior representatives from the NASA Office of Safety and Mission Assurance and the NAVSEA 92Q Submarine Safety and Quality Assurance Division. The team closely examined the two elements of submarine safety (SUBSAFE) certification: (1) new design/construction (initial certification) and (2) maintenance and modernization (sustaining certification), with a focus on: (1) Management and Organization, (2) Safety Requirements (technical and administrative), (3) Implementation Processes, (4) Compliance Verification Processes, and (5) Certification Processes.

SUBSAFE PROGRAM↗
NASA NTRS2013

NASA's Commercial Crew Program, the Next Step in U.S. Space Transportation

The Commercial Crew Program (CCP) is leading NASA's efforts to develop the next U.S. capability for crew transportation and rescue services to and from the International Space Station (ISS) by the middecade timeframe. The outcome of this capability is expected to stimulate and expand the U.S. space transportation industry. NASA is relying on its decades of human space flight experience to certify U.S. crewed vehicles to the ISS and is doing so in a two phase certification approach. NASA certification will cover all aspects of a crew transportation system, including: Development, test, evaluation, and verification. Program management and control. Flight readiness certification. Launch, landing, recovery, and mission operations. Sustaining engineering and maintenance/upgrades. To ensure NASA crew safety, NASA certification will validate technical and performance requirements, verify compliance with NASA requirements, validate that the crew transportation system operates in the appropriate environments, and quantify residual risks. The Commercial Crew Program will present progress to date and how it manages safety and reduces risk.

Mango, Edward J., Jr.↗
NASA NTRS2013

NASA's Commercial Crew Program, The Next Step in U.S. Space Transportation

The Commercial Crew Program (CCP) is leading NASA's efforts to develop the next U.S. capability for crew transportation and rescue services to and from the International Space Station (ISS) by the mid-decade timeframe. The outcome of this capability is expected to stimulate and expand the U.S. space transportation industry. NASA is relying on its decades of human space flight experience to certify U.S. crewed vehicles to the ISS and is doing so in a two phase certification approach. NASA Certification will cover all aspects of a crew transportation system, including development, test, evaluation, and verification; program management and control; flight readiness certification; launch, landing, recovery, and mission operations; sustaining engineering and maintenance/upgrades. To ensure NASA crew safety, NASA Certification will validate technical and performance requirements, verify compliance with NASA requirements, validate the crew transportation system operates in appropriate environments, and quantify residual risks.

Mango, Edward J.↗
NASA NTRS2013

NASA Activity Update for the 2013 Unmanned Vehicle Systems International (UVSI) Yearbook

This year s report offers a high level perspective on some of the UAS related activities in which NASA is involved, both internal and external to the agency. Internally, NASA issued UAS operational policy on certification of NASA UAS and aircrew. A team of NASA UAS experts and operators analyzed all current procedures and best practices to design the policy. An update to the agencies Aircraft Operations Management Manual incorporated a new chapter to address UAS planning, preflight operations, flight operations, flight crew requirements, airworthiness and flight safety reviews. NASA UAS are classified into three categories based on weight and airspeed. Aircrews, including observers, are classified by how they interface with the UAS, and the policy defines qualifications, training, and currency. The NASA flight readiness approval process identifies risks and mitigations in order to reduce the likelihood and/or consequence of the risk to an acceptable level. The UAS operations process incorporates all aspects of airworthiness, flight standards and range safety exactly the same processes used for NASA manned aircraft operations. NASA has two internal organizations that routinely operate UAS. The Science Mission Directorate utilizes UAS as part of its Airborne Science Program and is the most frequent operator of NASA UAS in both national and international airspace. The Aeronautics Research Mission Directorate conducts UAS flight operations in addition to conducting research important to the UAS community. This past year the Science Mission Directorate supported the Hurricane and Severe Storm Sentimental (HS3) Mission with two NASA Global Hawk platforms. HS3 is a five-year mission specifically targeted to investigate the processes that underlie hurricane formation. During the 2012 portion of this mission the Global Hawk overflew hurricanes Leslie and Nadine in the Atlantic Ocean completing 6 flights and accumulating more than 148 flight hours. Another multi-year mission was initiated last year when the Sensor Integrated Environmental Remote Research Aircraft (SIERRA) UAS began surveying faults in California s Surprise Valley. A team of scientists and engineers from the United States Geological Survey (USGS), NASA Ames Research Center, Central Washington University, and Carnegie Mellon University will measure magnetic fields using ground surveys and the SIERRA to map the geophysics below the surface of Surprise Valley. The data collected will be used to generate 3D maps of the geophysical data of the area. The Aeronautics Mission Directorate continues its collaboration with Boeing to conduct UAS flight operations of the X-48C, a modified version of the X-48B originally built by Cranfield Aerospace, United Kingdom. The Aeronautics Mission Directorate utilizes vehicles of this size for a wide variety of research studies. Most of these operations are conducted within restricted airspace. The Aeronautics Research Mission Directorate also sponsors the UAS in the National Airspace System (NAS) Project, which is working in close cooperation with the Federal Aviation Administration (FAA) to address critical challenges associated with routine UAS operations in civil airspace. The project is focused on separation assurance and collision avoidance systems and algorithms, command and control for non-military operations including spectrum allocation requirements, human system interaction issues, and safety and certification topics.

Bauer, Jeffrey E.↗