Search NASA⌕ Search

SEARCH · Search NASA

Results for “mishaps”

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 163 records · Page 9
All sourcesNASA NTRSDOE OSTI
NASA NTRS2009

Fighting Testing ACAT/FRRP: Automatic Collision Avoidance Technology/Fighter Risk Reduction Project

This slide presentation reviews the work of the Flight testing Automatic Collision Avoidance Technology/Fighter Risk Reduction Project (ACAT/FRRP). The goal of this project is to develop common modular architecture for all aircraft, and to enable the transition of technology from research to production as soon as possible to begin to reduce the rate of mishaps. The automated Ground Collision Avoidance System (GCAS) system is designed to prevent collision with the ground, by avionics that project the future trajectory over digital terrain, and request an evasion maneuver at the last instance. The flight controls are capable of automatically performing a recovery. The collision avoidance is described in the presentation. Also included in the presentation is a description of the flight test.

Skoog, Mark A.↗
NASA NTRS2009

Software Tools Streamline Project Management

Three innovative software inventions from Ames Research Center (NETMARK, Program Management Tool, and Query-Based Document Management) are finding their way into NASA missions as well as industry applications. The first, NETMARK, is a program that enables integrated searching of data stored in a variety of databases and documents, meaning that users no longer have to look in several places for related information. NETMARK allows users to search and query information across all of these sources in one step. This cross-cutting capability in information analysis has exponentially reduced the amount of time needed to mine data from days or weeks to mere seconds. NETMARK has been used widely throughout NASA, enabling this automatic integration of information across many documents and databases. NASA projects that use NETMARK include the internal reporting system and project performance dashboard, Erasmus, NASA s enterprise management tool, which enhances organizational collaboration and information sharing through document routing and review; the Integrated Financial Management Program; International Space Station Knowledge Management; Mishap and Anomaly Information Reporting System; and management of the Mars Exploration Rovers. Approximately $1 billion worth of NASA s projects are currently managed using Program Management Tool (PMT), which is based on NETMARK. PMT is a comprehensive, Web-enabled application tool used to assist program and project managers within NASA enterprises in monitoring, disseminating, and tracking the progress of program and project milestones and other relevant resources. The PMT consists of an integrated knowledge repository built upon advanced enterprise-wide database integration techniques and the latest Web-enabled technologies. The current system is in a pilot operational mode allowing users to automatically manage, track, define, update, and view customizable milestone objectives and goals. The third software invention, Query-Based Document Management (QBDM) is a tool that enables content or context searches, either simple or hierarchical, across a variety of databases. The system enables users to specify notification subscriptions where they associate "contexts of interest" and "events of interest" to one or more documents or collection(s) of documents. Based on these subscriptions, users receive notification when the events of interest occur within the contexts of interest for associated document or collection(s) of documents. Users can also associate at least one notification time as part of the notification subscription, with at least one option for the time period of notifications.

Source record↗
NASA NTRS2010

Design for Minimum Risk

Design for Minimum Risk (DFMR) is a term used by NASA programs as an expansion of the general hazard reduction process where if an identified hazard cannot be eliminated, the design is modified to reduce the associated mishap risk to an acceptable level. DFMR is a set of specific requirements to minimize risk. DFMR is not well understood and there are many misconceptions concerning the meaning and use. This paper will provide insight into the use of DFMR for space applications; it s comparison to other hazard mitigation strategies and examples of how the approach has been used in the past. It will also highlight documents used by NASA on various programs to determine DFMR.

Wetherholt, Jon↗
NASA NTRS2010

NASA Tech Briefs, October 2010

Topics covered include: Hybrid Architecture Active Wavefront Sensing and Control; Carbon-Nanotube-Based Chemical Gas Sensor; Aerogel-Positronium Technology for the Detection of Small Quantities of Organic and/or Toxic Materials; Graphene-Based Reversible Nano-Switch/Sensor Schottky Diode; Inductive Non-Contact Position Sensor; High-Temperature Surface-Acoustic-Wave Transducer; Grid-Sphere Electrodes for Contact with Ionospheric Plasma; Enabling IP Header Compression in COTS Routers via Frame Relay on a Simplex Link; Ka-Band SiGe Receiver Front-End MMIC for Transponder Applications; Robust Optimization Design Algorithm for High-Frequency TWTs; Optimal and Local Connectivity Between Neuron and Synapse Array in the Quantum Dot/Silicon Brain; Method and Circuit for In-Situ Health Monitoring of Solar Cells in Space; BGen: A UML Behavior Network Generator Tool; Platform for Post-Processing Waveform-Based NDE; Electrochemical Hydrogen Peroxide Generator; Fabrication of Single, Vertically Aligned Carbon Nanotubes in 3D Nanoscale Architectures; Process to Create High-Fidelity Lunar Dust Simulants; Lithium-Ion Electrolytes Containing Phosphorous-Based, Flame-Retardant Additives; InGaP Heterojunction Barrier Solar Cells; Straight-Pore Microfilter with Efficient Regeneration; Determining Shear Stress Distribution in a Laminate; Self-Adjusting Liquid Injectors for Combustors; Handling Qualities Prediction of an F-16XL-Based Reduced Sonic Boom Aircraft; Tele-Robotic ATHLETE Controller for Kinematics - TRACK; Three-Wheel Brush-Wheel Sampler; Heterodyne Interferometer Angle Metrology; Aligning Astronomical Telescopes via Identification of Stars; Generation of Optical Combs in a WGM Resonator from a Bichromatic Pump; Large-Format AlGaN PIN Photodiode Arrays for UV Images; Fiber-Coupled Planar Light-Wave Circuit for Seed Laser Control in High Spectral Resolution Lidar Systems; On Calculating the Zero-Gravity Surface Figure of a Mirror; Optical Modification of Casimir Forces for Improved Function of Micro- and Nano-Scale Devices; Analysis, Simulation, and Verification of Knowledge-Based, Rule-Based, and Expert Systems; Core and Off-Core Processes in Systems Engineering; Digital Reconstruction Supporting Investigation of Mishaps; and Template Matching Approach to Signal Prediction.

Source record↗
NASA NTRS2002

Performance and Safety Characteristics of Sanyo NiCd Cells

NiCd batteries are widely used for high drain applications like power tools and also in other portable equipment like cameras, PCs, etc. NASA and Dreamtime Holdings, Inc. worked together to have the capability of a High Definition TV (HDTV) on the ISS and Space Shuttle. The Sanyo HD camcorder was used on the STS 105 fight in July, 2001 . The camcorder used two versions of a NiCd battery. One was a cOlnmercial off-the-shelf Sony BP90 battery pack that had Sanyo NiCd D cells. The other was a modified battery (FBP-90) made by Frezzi Energy, which also had the same Sanyo NiCd D cells. The battery has 10 NiCd D cells in series to form a 12 V pack with 5.0 Ah capacity. Our current study involved the perforn1ance and abuse tests on the Sanyo NiCd 5.0 Ah D cells. The best combination of charge/discharge current rate is 0.3C for charge and 1/2e for discharge within 200 cycles. No significant changes in capacity were observed in 200 cycles. The cell also showed capability of 5C (25.0A) high rate discharge. In overcharge and overdischarge tests, all tested cells passed the tests without venting. In imbalance tests, the battery pack could be charged and discharged only at relatively low current. At charge current of 1.0A or less, the imbalanced cells in the battery pack displayed relatively high temperatures during charge or discharge. The cells functioned normally during internal short and no mishap occurred during external short. Cells passed exposure tests at 80 C and no leakage till 150 C during heat-tovent tests.

Deng, Yi↗
NASA NTRS2010

Reducing Seal Adhesion in Low Impact Docking Systems

Silicone elastomers, used in seals for airlocks or other sealing surfaces in space, are sticky in their as-received condition. Because of the sticking, a greater force may be needed to separate the mating surfaces. If the adhesion is sufficiently high, a sudden unpredicted movement of the spacecraft during undocking, vibration, or uneven release could pull off the seal, resulting in a damage that would have to be repaired before another docking. The damaged seal can result in significant gas leakage and possibly in a catastrophic mishap impacting the safety of the crew. It is also possible that a compromised seal could result in a delayed but sudden gas leak that could put the crew at unexpected risk. This is especially of concern for androgynous seals, which have identical mating surfaces on both sides for interchangeability and redundancy. Such seals typically have elastomer-on-elastomer sealing surfaces. To reduce sticking, one could use release agents such as powders and lubricants, but these can be easily removed and transferred to other surfaces, causing uneven sealing and contamination. Modification of the elastomer surface to make a more slippery and less sticky surface that is integral with the bulk elastomer would be more desirable.

Banks, Bruce A.↗
NASA NTRS2010

Hydrogen Fire in a Storage Vessel

On October 23, 2007, the operations team began a procedure to sample the Liquid Hydrogen (LH2) storage vessels ("tanks"), and associated transfer system. This procedure was being performed to determine the conditions within the system, and if necessary, to purge the system of any excess Gaseous Hydrogen (GH2) in preparation for reactivation of the system. The system had not been used since 2003. The LH2 storage system contains two (2) spherical pressure vessels of 225,000 gallons in volume, with a maximum working pressure (MAWP) of 50 psig. Eight inch transfer piping connects them to the usage point. Operations began with activation of the burnstack for the LH2 storage area. Pneumatic (GN2) systems in the storage area were then activated and checked. Pressurization of storage tank number 1 with gaseous nitrogen (GN2) was initiated, with a target pressure of 10 psig, at which point samples were planned to be taken. At 5 psig, a loud noise was heard in the upper area of tank number 2. Smoke was seen exiting the burnstack and from the insulation on vent lines for both tanks. At this time tank number 1 was vented and the pressurization system was secured. The mishap resulted in physical damage to both storage tanks, as well as to some of the piping for both tanks. Corrective action included repair of the damaged hardware by a qualified contractor. Preventive action included documented organizational policy and procedures for establishing standby and mothball conditions for facilities and equipment, including provisions as detailed in the investigation report recommendations: Recommendation 1: The using organization should define necessary activities in order to place hydrogen systems in long term periods of inactivity. The defined activities should address requirements for rendering inert, isolation (i.e., physical disconnect, double block and bleed, etc.) and periodic monitoring. Recommendation 2: The using organization should develop a process to periodically monitor hazardous systems for proper configuration (i.e., a daily/weekly/monthly check sheet to verify critical purges are active).

Hester, Zena M.↗
NASA NTRS2011

Flying Unmanned Aircraft: A Pilot's Perspective

The National Aeronautics and Space Administration (NASA) is pioneering various Unmanned Aircraft System (UAS) technologies and procedures which may enable routine access to the National Airspace System (NAS), with an aim for Next Gen NAS. These tools will aid in the development of technologies and integrated capabilities that will enable high value missions for science, security, and defense, and open the door to low-cost, extreme-duration, stratospheric flight. A century of aviation evolution has resulted in accepted standards and best practices in the design of human-machine interfaces, the displays and controls of which serve to optimize safe and efficient flight operations and situational awareness. The current proliferation of non-standard, aircraft-specific flight crew interfaces in UAS, coupled with the inherent limitations of operating UAS without in-situ sensory input and feedback (aural, visual, and vestibular cues), has increased the risk of mishaps associated with the design of the "cockpit." The examples of current non- or sub- standard design features range from "annoying" and "inefficient", to those that are difficult to manipulate or interpret in a timely manner, as well as to those that are "burdensome" and "unsafe." A concerted effort is required to establish best practices and standards for the human-machine interfaces, for the pilot as well as the air traffic controller. In addition, roles, responsibilities, knowledge, and skill sets are subject to redefining the terms, "pilot" and "air traffic controller", with respect to operating UAS, especially in the Next-Gen NAS. The knowledge, skill sets, training, and qualification standards for UAS operations must be established, and reflect the aircraft-specific human-machine interfaces and control methods. NASA s recent experiences flying its MQ-9 Ikhana in the NAS for extended duration, has enabled both NASA and the FAA to realize the full potential for UAS, as well as understand the implications of current limitations. Ikhana is a Predator-B/Reaper UAS, built by General Atomics, Aeronautical Systems, Inc., and modified for research. Since 2007, the aircraft has been flown seasonally with a wing-mounted pod containing an infrared scanner, utilized to provide real-time wildfire geo-location data to various fire-fighting agencies in the western U.S. The multi-agency effort included an extensive process to obtain flight clearance from the FAA to operate under special provisions, given that UAS in general do not fully comply with current airspace regulations (e.g. sense-and-avoid requirements).

Pestana, Mark E.↗
NASA NTRS2011

Assessment of CFD-based Response Surface Model for Ares I Supersonic Ascent Aerodynamics

The Ascent Force and Moment Aerodynamic (AFMA) Databases (DBs) for the Ares I Crew Launch Vehicle (CLV) were typically based on wind tunnel (WT) data, with increments provided by computational fluid dynamics (CFD) simulations for aspects of the vehicle that could not be tested in the WT tests. During the Design Analysis Cycle 3 analysis for the outer mold line (OML) geometry designated A106, a major tunnel mishap delayed the WT test for supersonic Mach numbers (M) greater than 1.6 in the Unitary Plan Wind Tunnel at NASA Langley Research Center, and the test delay pushed the final delivery of the A106 AFMA DB back by several months. The aero team developed an interim database based entirely on the already completed CFD simulations to mitigate the impact of the delay. This CFD-based database used a response surface methodology based on radial basis functions to predict the aerodynamic coefficients for M > 1.6 based on only the CFD data from both WT and flight Reynolds number conditions. The aero team used extensive knowledge of the previous AFMA DB for the A103 OML to guide the development of the CFD-based A106 AFMA DB. This report details the development of the CFD-based A106 Supersonic AFMA DB, constructs a prediction of the database uncertainty using data available at the time of development, and assesses the overall quality of the CFD-based DB both qualitatively and quantitatively. This assessment confirms that a reasonable aerodynamic database can be constructed for launch vehicles at supersonic conditions using only CFD data if sufficient knowledge of the physics and expected behavior is available. This report also demonstrates the applicability of non-parametric response surface modeling using radial basis functions for development of aerodynamic databases that exhibit both linear and non-linear behavior throughout a large data space.

Hanke, Jeremy L.↗
NASA NTRS2011

X-43A Final Flight Observations

The presentation will provide an overview of the final flight of the NASA X-43A project. The project consisted of three flights, two planned for Mach 7 and one for Mach 10. The first flight, conducted on June 2, 2001, was unsuccessful and resulted in a nine-month mishap investigation. A two-year return to flight effort ensued and concluded when the second Mach 7 flight was successfully conducted on March 27, 2004. The third and final flight, which occurred on November 16, 2004, was the first Mach 10 flight demonstration of an airframe-integrated, scramjet-powered, hypersonic vehicle. As such, the final flight presented first time technical challenges in addition to final flight project closeout concerns. The goals and objectives for the third flight as well as those for the project will be presented. The configuration of the Hyper-X stack including the X-43A, Hyper-X launch vehicle, and Hyper-X research vehicle adapter wil also be presented. Mission differences, vehicle modifications and lessons learned from the first and second flights as they applied to the third flight will also be discussed. Although X-43A flight 3 was always planned to be the final flight of the X-43A project, the X-43 program had two other vehicles and corresponding flight phases in X-43C and X-43B. Those other projects never manifested under the X-43 banner and X-43A flight 3 also became the final flight of X-43 program.

Grindle, Laurie↗
NASA NTRS2011

Safety and Mission Assurance: A NASA Perspective

Safety and Mission Assurance (S&MA) consists of the safety, reliability, maintainability, software assurance and quality disciplines, which are applied to reduce the probability of mishaps and ensure mission success. NASA uses a risk management process which requires various organizations to identify, analyze and mitigate/control risks associated with operations and decision making processes.

Higginbotham, Scott Alan↗
NASA NTRS2005

Adaptable System for Vehicle Health and Usage Monitoring

Aircraft and other vehicles are often kept in service beyond their original design lives. As they age, they become susceptible to system malfunctions and fatigue. Unlike future aircraft that will include health-monitoring capabilities as integral parts in their designs, older aircraft have not been so equipped. The Adaptable Vehicle Health and Usage Monitoring System is designed to be retrofitted into a preexisting fleet of military and commercial aircraft, ships, or ground vehicles to provide them with state-of-the-art health- and usage-monitoring capabilities. The monitoring system is self-contained, and the integration of it into existing systems entails limited intrusion. In essence, it has bolt-on/ bolt-off simplicity that makes it easy to install on any preexisting vehicle or structure. Because the system is completely independent of the vehicle, it can be certified for airworthiness as an independent system. The purpose served by the health-monitoring system is to reduce vehicle operating costs and to increase safety and reliability. The monitoring system is a means to identify damage to, or deterioration of, vehicle subsystems, before such damage or deterioration becomes costly and/or disastrous. Frequent monitoring of a vehicle enables identification of the embryonic stages of damage or deterioration. The knowledge thus gained can be used to correct anomalies while they are still somewhat minor. Maintenance can be performed as needed, instead of having the need for maintenance identified during cyclic inspections that take vehicles off duty even when there are no maintenance problems. Measurements and analyses acquired by the health-monitoring system also can be used to analyze mishaps. Overall, vehicles can be made more reliable and kept on duty for longer times. Figure 1 schematically depicts the system as applied to a fleet of n vehicles. The system has three operational levels. All communication between system components is by use of wireless transceivers operating at frequencies near 433 MHz. Electromagnetic-interference tests have demonstrated that the radio-frequency emissions from the transceivers do not influence civilian aircraft communication and navigation systems.

Woodart, Stanley E.↗
NASA NTRS2011

The Psychology of Safety

Many studies of mishaps show that human error is a factor in a significant majority of accidents. Trying to decide how to change human behavior to be safer is generally the biggest challenge of any safety program. However, understanding the human psyche is the first step to changing behavior. Many studies focus on the before and after of an accident, but what about the thoughts of a person in the commission of an unsafe act? This is a less understood area. Examining it reveals why it is not well comprehended. This paper attempts to examine a part of the thought process, with an eye to helping influence people to less hurtful actions.

Anderson, Brenda Lindley↗
NASA NTRS2005

Close-Call Action Log Form

"Close Call Action Log Form" ("CCALF") is the name of both a computer program and a Web-based service provided by the program for creating an enhanced database of close calls (in the colloquial sense of mishaps that were avoided by small margins) assigned to the Center Operations Directorate (COD) at Johnson Space Center. CCALF provides a single facility for on-line collaborative review of close calls. Through CCALF, managers can delegate responses to employees. CCALF utilizes a pre-existing e-mail system to notify managers that there are close calls to review, but eliminates the need for the prior practices of passing multiple e-mail messages around the COD, then collecting and consolidating them into final responses: CCALF now collects comments from all responders for incorporation into reports that it generates. Also, whereas it was previously necessary to manually calculate metrics (e.g., numbers of maintenance-work orders necessitated by close calls) for inclusion in the reports, CCALF now computes the metrics, summarizes them, and displays them in graphical form. The reports and all pertinent information used to generate the reports are logged, tracked, and retained by CCALF for historical purposes.

Spuler, Linda M.↗
NASA NTRS2011

Flight Systems Integration and Test

Topics to be Covered in this presentation are: (1) Integration and Test (I&T) Planning (2) Integration and Test Flows (3) Overview of Typical Mission I&T (4) Supporting Elements (5) Lessons-Learned and Helpful Hints (6) I&T Mishaps and Failures (7) The Lighter Side of I&T and (8) Small-Group Activity. This presentation highlights a typical NASA "in-house" I&T program (1) For flight systems that are developed by NASA at a space flight center (like GSFC) (2) Requirements well-defined: qualification/acceptance, documentation, configuration management. (3) Factors: precedents, human flight, risk-aversion ("failure-phobia"), taxpayer dollars, jobs and (4) Some differences among NASA centers, but generally a resource-intensive process

Wright, Michael R.↗
NASA NTRS2005

Safety Auditing and Assessments

Safety professionals typically do not engage in audits and independent assessments with the vigor as do our quality brethren. Taking advantage of industry and government experience conducting value added Independent Assessments or Audits benefits a safety program. Most other organizations simply call this process "internal audits." Sources of audit training are presented and compared. A relation of logic between audit techniques and mishap investigation is discussed. An example of an audit process is offered. Shortcomings and pitfalls of auditing are covered.

Goodin, James Ronald (Ronnie)↗
NASA NTRS2012

Hazard Analysis for Pneumatic Flipper Suitport/Z-1 Manned Evaluation, Chamber B, Building 32

One of the characteristics of an effective safety program is the recognition and control of hazards before mishaps or failures occur. Conducting potentially hazardous tests necessitates a thorough hazard analysis in order to protect our personnel from injury and our equipment from damage. The purpose of this hazard analysis is to define and address the potential hazards and controls associated with the Z1 Suit Port Test in Chamber B located in building 32, and to provide the applicable team of personnel with the documented results. It is imperative that each member of the team be familiar with the hazards and controls associated with his/her particular tasks, assignments, and activities while interfacing with facility test systems, equipment, and hardware. The goal of this hazard analysis is to identify all hazards that have the potential to harm personnel and/or damage facility equipment, flight hardware, property, or harm the environment. This analysis may also assess the significance and risk, when applicable, of lost test objectives when substantial monetary value is involved. The hazards, causes, controls, verifications, and risk assessment codes have been documented on the hazard analysis work sheets in appendix A of this document. The preparation and development of this report is in accordance with JPR 1700.1, JSC Safety and Health Handbook.

Source record↗
NASA NTRS2013

Morpheus 1.5A Lander Failure Investigation Results

On August 9th, 2012, the Morpheus 1.5 Vertical Testbed (VTB) crashed during Free Flight 2 (FF2) at KSC SLF, resulting in the loss of 1.5 VTB hardware. JSC/KSC Morpheus team immediately executed the pre‐rehearsed Emergency Action Plan to protect personnel and property, so damage was limited to 1.5 VTB hardware. JSC/KSC Morpheus team secured data and mapped & recovered debris. Project had pre‐declared loss of VTB to be a test failure, not a mishap.

Munday, Steve↗