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 145 records · Page 8

The X-43A (Hyper-X) Flies Into the Record Books

The goal of the Hyper-X research program, conducted jointly by the NASA Dryden Flight Research Center and the NASA Langley Research Center, was to demonstrate and validate the technology, experimental techniques, and computation methods and tools for design and performance predictions of a hypersonic aircraft with an airframe-integrated, scramjet propulsion system. Three X-43A airframe-integrated, scramjet research vehicles were designed and fabricated to achieve that goal by flight test: two test flights at Mach 7 and one test flight at Mach 10. The first flight, conducted on June 2, 2001, experienced a launch vehicle failure and resulted in a 9-month mishap investigation. A two-year return-to-flight effort ensued and concluded when the second Mach 7 flight was successful on March 27, 2004. Just eight months later, on November 16, the X-43A successfully completed the third and final flight. These two flights were the first flight demonstrations, at Mach 7 and Mach 10 respectively, of an airframe-integrated, scramjet-powered, hypersonic vehicle.

Grindle, Laurie↗

Safely Containing Frangible Materials used in Space Flight Equipment

Glass fragments in a habitable zero-g environment can be very hazardous to the crew, with a potential for causing eye injuries or inhalation mishaps. With the advent of the Space Shuttle Program, NASA had to manage many shatterable items in the habitable compartment, brought to the spacecraft by payload developers, NASA experiments, crew equipment and the vehicle's own avionics and other instrumentation. This effort has continued in the International Space Station Program, and will be a part of every future manned space effort.

Bernstein, Karen S.↗

A Match Made in Space

Just before the space shuttle reaches orbit, its three main engines shut down so that it can achieve separation from the massive external tank that provided the fuel required for liftoff and ascent. In jettisoning the external tank, which is completely devoid of fuel at this point in the flight, the space shuttle fires a series of thrusters, separate from its main engines, that gives the orbiter the maneuvering ability necessary to safely steer clear of the descending tank and maintain its intended flight path. These thrusters make up the space shuttle s Reaction Control System. While the space shuttle s main engines only provide thrust in one direction (albeit a very powerful thrust), the Reaction Control System engines allow the vehicle to maneuver in any desired direction (via small amounts of thrust). The resulting rotational maneuvers are known as pitch, roll, and yaw, and are very important in ensuring that the shuttle docks properly when it arrives at the International Space Station and safely reenters the Earth s atmosphere upon leaving. To prevent the highly complex Reaction Control System from malfunctioning during space shuttle flights, and to provide a diagnosis if such a mishap were to occur, NASA turned to a method of artificial intelligence that truly defied the traditional laws of computer science.

Source record↗

NASA Hydrogen Peroxide Propellant Hazards Technical Manual

The Fire, Explosion, Compatibility and Safety Hazards of Hydrogen Peroxide NASA technical manual was developed at the NASA Johnson Space Center White Sands Test Facility. NASA Technical Memorandum TM-2004-213151 covers topics concerning high concentration hydrogen peroxide including fire and explosion hazards, material and fluid reactivity, materials selection information, personnel and environmental hazards, physical and chemical properties, analytical spectroscopy, specifications, analytical methods, and material compatibility data. A summary of hydrogen peroxide-related accidents, incidents, dose calls, mishaps and lessons learned is included. The manual draws from art extensive literature base and includes recent applicable regulatory compliance documentation. The manual may be obtained by United States government agencies from NASA Johnson Space Center and used as a reference source for hazards and safe handling of hydrogen peroxide.

Baker, David L.↗

Learning from Past Experiences

Space flight is a risky business. This truism has been bandied about since the earliest days of the space program. When asked by the young daughter of a coworker, one of the Mercury astronauts likened launching into space to "riding a Roman candle" -- it was both exciting and dangerous. Even in these more technologically advanced days, the solid rocket boosters and external tanks of the space shuttle provide a no less exciting, or dangerous, ride into space. However much the phrase "risk mitigation" is bandied about within the U.S. space program, there is still the history of the Apollo 1 fire during a ground test at Cape Canaveral, Fla., the loss of the shuttle Challenger during liftoff, and the loss of the shuttle Columbia when returning to Earth to remind us that while we give lip-service to risk management, we have not learned to manage risk as well as we ought. Moreover, there are many more less dramatic, but equally critical, incidents that have occurred in association with the space program that also highlight our inability to accurately gauge and manage risk. Why do we seem caught in a senseless spiral in which we focus most on risk only after a tragedy? Why do we repeat serious mishaps and not learn from our mistakes? This paper reviews some possible explanations for our risk-taking behavior and provides examples of interest to the NASA centers, while also discussing inter center and intra-center opportunities for sharing information to mitigate risk.

Hulet, Michael W.↗

Fiber Optic Wing Shape Sensing on NASA's Ikhana UAV

This document discusses the development of fiber optic wing shape sensing on NASA's Ikhana vehicle. The Dryden Flight Research Center's Aerostructures Branch initiated fiber-optic instrumentation development efforts in the mid-1990s. Motivated by a failure to control wing dihedral resulting in a mishap with the Helios aircraft, new wing displacement techniques were developed. Research objectives for Ikhana included validating fiber optic sensor measurements and real-time wing shape sensing predictions; the validation of fiber optic mathematical models and design tools; assessing technical viability and, if applicable, developing methodology and approaches to incorporate wing shape measurements within the vehicle flight control system; and, developing and flight validating approaches to perform active wing shape control using conventional control surfaces and active material concepts.

Richards, Lance↗

When All the Ducks Line Up

This viewgraph presentation gives an overview of the N2NA Pylon overheat mishap. The contents include: 1) Investigation Process; 2) Bottom Line; 3) Event Description / Damage; 4) Causal Tree Analysis; 5) Significant Observations; and 6) Major Recommendations.

Henwood, Bart E.↗

Information Extraction for System-Software Safety Analysis: Calendar Year 2007 Year-End Report

This annual report describes work to integrate a set of tools to support early model-based analysis of failures and hazards due to system-software interactions. The tools perform and assist analysts in the following tasks: 1) extract model parts from text for architecture and safety/hazard models; 2) combine the parts with library information to develop the models for visualization and analysis; 3) perform graph analysis on the models to identify possible paths from hazard sources to vulnerable entities and functions, in nominal and anomalous system-software configurations; 4) perform discrete-time-based simulation on the models to investigate scenarios where these paths may play a role in failures and mishaps; and 5) identify resulting candidate scenarios for software integration testing. This paper describes new challenges in a NASA abort system case, and enhancements made to develop the integrated tool set.

Malin, Jane T.↗

Aeroservoelastic Stability Analysis of the X-43A Stack

The first air launch attempt of an X-43A stack, consisting of the booster, adapter and Hyper-X research vehicle, ended in failure shortly after the successful drop from the National Aeronautics and Space Administration Dryden Flight Research Center (Edwards, California) B-52B airplane and ignition of the booster. The stack was observed to begin rolling and yawing violently upon reaching transonic speeds, and the grossly oscillating fins of the booster separated shortly thereafter. The flight then had to be terminated with the stack out of control. Very careful linear flutter and aeroservoelastic analyses were subsequently performed as reported herein to numerically duplicate the observed instability. These analyses properly identified the instability mechanism and demonstrated the importance of including the flight control laws, rigid-body modes, structural flexible modes and control surface flexible modes. In spite of these efforts, however, the predicted instability speed remained more than 25 percent higher than that observed in flight. It is concluded that transonic shock phenomena, which linear analyses cannot take into account, are also important for accurate prediction of this mishap instability.

Pak, Chan-gi↗

The NASA Engineering and Safety Center (NESC) GN and C Technical Discipline Team (TDT): Its Purpose, Practices and Experiences

This paper will briefly define the vision, mission, and purpose of the NESC organization. The role of the GN&C TDT will then be described in detail along with an overview of how this team operates and engages in its objective engineering and safety assessments of critical NASA projects. This paper will then describe key issues and findings from several of the recent GN&C-related independent assessments and consultations performed and/or supported by the NESC GN&C TDT. Among the examples of the GN&C TDT s work that will be addressed in this paper are the following: the Space Shuttle Orbiter Repair Maneuver (ORM) assessment, the ISS CMG failure root cause assessment, the Demonstration of Autonomous Rendezvous Technologies (DART) spacecraft mishap consultation, the Phoenix Mars lander thruster-based controllability consultation, the NASA in-house Crew Exploration Vehicle (CEV) Smart Buyer assessment and the assessment of key engineering considerations for the Design, Development, Test & Evaluation (DDT&E) of robust and reliable GN&C systems for human-rated spacecraft.

Dennehy, Cornelius J.↗

Did Vertigo Kill America's Forgotten Astronaut?

On November 15, 1967, U.S. Air Force test pilot Major Michael J. Adams was killed while flying the X-15 rocket-propelled research vehicle in a parabolic spaceflight profile. This flight was part of a joint effort with NASA. An electrical short in one of the experiments aboard the vehicle caused electrical transients, resulting in excessive workload by the pilot. At altitude Major Adams inappropriately initiated a flat spin that led to a series of unusual aircraft attitudes upon atmospheric re-entry, ultimately causing structural failure of the airframe. Major Adams was known to experience vertigo (i.e. spatial disorientation) while flying the X-15, but all X-15 pilots most likely experienced vertigo (i.e. somatogravic, or "Pitch-Up", illusion) as a normal physiologic response to the accelerative forces involved. Major Adams probably experienced vertigo to a greater degree than did others, since prior aeromedical testing for astronaut selection at Brooks AFB revealed that he had an unusually high degree of labyrinthine sensitivity. Subsequent analysis reveals that after engine burnout, and through the zenith of the flight profile, he likely experienced the oculoagravic ("Elevator") illusion. Nonetheless, painstaking investigation after the mishap revealed that spatial disorientation (Type II, Recognized) was NOT the cause, but rather, a contributing factor. The cause was in fact the misinterpretation of a dual-use flight instrument (i.e. Loss of Mode Awareness), resulting in confusion between yaw and roll indications, with subsequent flight control input that was inappropriate. Because of the altitude achieved on this flight, Major Adams was awarded Astronaut wings posthumously. Understanding the potential for spatial disorientation, particularly the oculoagravic illusion, associated with parabolic spaceflight profiles, and understanding the importance of maintaining mode awareness in the context of automated cockpit design, are two lessons that have direct application to the commercial space industry today.

Bendrick, Gregg A.↗

Introduction and Mission Response Team (MRT)

On February 1, 2003 the Space Shuttle Columbia, returning to Earth with a crew of seven astronauts, disintegrated along a track extending from California to Louisiana. Observers on the ground filmed breakup of the spacecraft. Debris fell along a 567 statute mile track from Littlefield, Texas to Fort Polk, Louisiana; the largest ever recorded debris field. At the time of the accident the National Aeronautics and Space Administration (NASA) flight surgeon on-duty at the Mission Control Center (MCC) in Houston, Texas initiated the medical contingency response. The DOD surgeon at Patrick Air Force Base was notified, NASA medical personnel were recalled and the services of Armed Forces Institute of Pathology (AFIP) were requested. Subsequent to the accident the NASA flight surgeons that had supported the crew on orbit now provided medical support to the crewmember s families. Federal Emergency Management Agency (FEMA), the National Transportation Safety Board (NTSB), the Federal Bureau of Investigation (FBI) and numerous other federal, state and local agencies along with the citizens of Texas and Louisiana responded to the disaster. Search and recovery was managed from a Disaster Field Office (DFO) established in Lufkin, Texas. Mishap Investigation Team (MIT) medical operations were managed from Barksdale Air Force Base, Louisiana. Accident investigation teams (Columbia Accident Investigation Task Force (CAITF) and Columbia Accident Investigation Board (CAIB)) appointed immediately after the disaster included current and former authorities in space medicine. In August 2003, the CAIB concluded its investigation and released its findings in a report published in February 2004.

Pool, Sam↗

Armed Forces Institute of Pathology (AFIP)

The AFIP and NASA relationship was developed in an effort to appropriately respond to a space shuttle mishap. This briefing discusses the AFIP/NASA relationship with special emphasis being placed on search, recovery and identification activities

Mallak, Craig↗

Systems Engineering Technical Authority: A Path to Mission Success

The systems engineering of space missions to study planet Earth has been an important focus of the National Aeronautics and Space Administration (NASA) since its inception. But all space missions are becoming increasingly complex and this fact, reinforced by some major mishaps, has caused NASA to reevaluate their approach to achieving safety and mission success. A new approach ensures that there are adequate checks and balances in place to maximize the probability of safety and mission success. To this end the agency created the concept of Technical Authority which identifies a key individual accountable and responsible for the technical integrity of a flight mission as well as a project-independent reporting path. At the Goddard Space Flight Center (GSFC) this responsibility ultimately begins with the Mission Systems Engineer (MSE) for each satellite mission. This paper discusses the Technical Authority process and then describes some unique steps that are being taken at the GSFC to support these MSEs in meeting their responsibilities.

Andary, James F.↗

Exhaustive Thresholds and Resistance Checkpoints

Once deployed, all intricate systems that operate for a long time (such as an airplane or chemical processing plant) experience degraded performance during operational lifetime. These can result from losses of integrity in subsystems and parts that generally do not materially impact the operation of the vehicle (e.g., the light behind the button that opens the sliding door of the minivan). Or it can result from loss of more critical parts or subsystems. Such losses need to be handled quickly in order to avoid loss of personnel, mission, or part of the system itself. In order to manage degraded systems, knowledge of its potential problem areas and the means by which these problems are detected should be developed during the initial development of the system. Once determined, a web of sensors is employed and their outputs are monitored with other system parameters while the system is in preparation or operation. Just gathering the data is only part of the story. The interpretation of the data itself and the response of the system must be carefully developed as well to avoid a mishap. Typically, systems use a test-threshold-response paradigm to process potential system faults. However, such processing sub-systems can suffer from errors and oversights of a consistent type, causing system aberrant behavior instead of expected system and recovery operations. In our study, we developed a complete checklist for determining the completeness of a fault system and its robustness to common processing and response difficulties.

Easton, Charles↗

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

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↗