Search NASA⌕ Search

SEARCH · Search NASA

Results for “hardware failure”

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 325 records · Page 18

Complete time-resolved X-ray shape capability for a 10 MJ implosion: Milestone Report for MRT 8818

This report documents completion of MRT 8818, which established an upgraded equatorial time-resolved X-ray imaging capability for high-yield inertial confinement fusion experiments at the National Ignition Facility (NIF) using the equatorial Dilation X-ray Imager (DIXI). The need for this work arose from the sustained increase in fusion yield at NIF, which progressively intensified the neutron and gamma-ray environment experienced by target diagnostics. Although the existing polar imaging capability, particularly the Polar Dilation X-ray Imager (PDIXI), remained viable at high yields, the equatorial capability became inadequate because of radiation-induced failure of electronic readout hardware and increasing background levels that degraded image quality and ultimately caused saturation. The work performed under MRT 8818 addressed this limitation through a combination of hardware replacement, background characterization, and targeted mitigation. The DIXI backend was converted from CCD-based electronic readout to photographic film, and the principal sources of internally generated background were investigated using prior analyses, dedicated tests, and comparison with PDIXI performance on high-yield shots. This effort led to implementation of two principal improvements: a multilayer optical coating to suppress broadband radiation-induced background generated in the fiber-optic extension cylinder, and replacement of Kodak TMAX 400 film with Agfa Copex Rapid to reduce background generated directly in the film. These upgrades were completed in 2025 and performance assessment based on DT shot data since then, comparing with Polar DIXI and scaling of these experiments to 10 MJ indicates an expected signal-to-background ratio of approximately 34 for a single pinhole image, substantially exceeding the MRT 8818 completion criterion of SNR > 5.

70 PLASMA PHYSICS AND FUSION TECHNOLOGY↗

Lunar module program system safety

The application of system safety principles to the Lunar Module Program is summarized. Objectives of the program include elimination or reduction of risk to personnel, material, and facilities resulting from failures or malfunctions in hardware or procedures. Data also cover design, production, and test activity.

William E. Scarborough↗

Nondestructive evaluation of electroformed outer shells for regeneratively cooled thrust chambers

Electroforming is presently a prime technique for producing the outer jackets of regeneratively cooled thrust chambers for rocket engines. Good bond integrity of the electroformed joints adjacent to the coolant passages is important to the useful service life of these aerospace systems. This investigation demonstrated that nondestructive evaluation techniques such as ultrasonic 'C' scan, holography, and acoustic emission are capable of detecting low integrity bonds which could lead to premature failures in the subject hardware.

Malone, G. A.↗

Galileo spacecraft power distribution and autonomous fault recovery

There is a trend in current spacecraft design to achieve greater fault tolerance through the implemenation of on-board software dedicated to detecting and isolating failures. A combination of hardware and software is utilized in the Galileo power system for autonomous fault recovery. Galileo is a dual-spun spacecraft designed to carry a number of scientific instruments into a series of orbits around the planet Jupiter. In addition to its self-contained scientific payload, it will also carry a probe system which will be separated from the spacecraft some 150 days prior to Jupiter encounter. The Galileo spacecraft is scheduled to be launched in 1985. Attention is given to the power system, the fault protection requirements, and the power fault recovery implementation.

Detwiler, R. C.↗

Fault-tolerant, embedded CLIPS applications

The enhancements to CLIPS4.3 presented in this paper provide an embedded CLIPS application with the ability to continue operation with minimal to no loss of information in the event of a hardware or a software failure. Given an arbitrary failure, the CLIPS application's environment (fact-list, agenda, and pattern matching network) will be reconstructed to the point at which the failure was experienced. The environment reconstruction is based on state files to which the application periodically checks environment information (fact-list and agenda). The routine for checkpointing the state of the application is as efficient as possible so that the overhead introduced to normal execution of the application is minimal. The only assumptions made by the CLIPS application are that it is running under an operating system that guarantees it access to uncorrupt state files and that the application will be automatically restarted should it terminate abnormally.

Hicks, Jaye↗

Preloaded joint analysis methodology for space flight systems

This report contains a compilation of some of the most basic equations governing simple preloaded joint systems and discusses the more common modes of failure associated with such hardware. It is intended to provide the mechanical designer with the tools necessary for designing a basic bolted joint. Although the information presented is intended to aid in the engineering of space flight structures, the fundamentals are equally applicable to other forms of mechanical design.

Chambers, Jeffrey A.↗

Work on Planetary Atmospheres and Planetary Atmosphere Probes

A summary final report of work accomplished is presented. Work was performed in the following areas: (1) Galileo Probe science analysis, (2) Galileo probe Atmosphere Structure Instrument, (3) Mars Pathfinder Atmosphere Structure/Meteorology instrument, (4) Mars Pathfinder data analysis, (5) Science Definition for future Mars missions, (6) Viking Lander data analysis, (7) winds in Mars atmosphere Venus atmospheric dynamics, (8) Pioneer Venus Probe data analysis, (9) Pioneer Venus anomaly analysis, (10) Discovery Venus Probe Titan probe instrument design, and (11) laboratory studies of Titan probe impact phenomena. The work has resulted in more than 10 articles published in archive journals, 2 encyclopedia articles, and many working papers. This final report is organized around the four planets on which there was activity, Jupiter, Mars, Venus, and Titan, with a closing section on Miscellaneous Activities. A major objective was to complete the fabrication, test, and evaluation of the atmosphere structure experiment on the Galileo probe, and to receive, analyze and interpret data received from the spacecraft. The instrument was launched on April 14, 1989. Calibration data were taken for all experiment sensors. The data were analyzed, fitted with algorithms, and summarized in a calibration report for use in analyzing and interpreting data returned from Jupiter's atmosphere. The sensors included were the primary science pressure, temperature and acceleration sensors, and the supporting engineering temperature sensors. Computer programs were written to decode the Experiment Data Record and convert the digital numbers to physical quantities, i.e., temperatures, pressures, and accelerations. The project office agreed to obtain telemetry of checkout data from the probe. Work to extend programs written for use on the Pioneer Venus project included: (1) massive heat shield ablation leading to important mass loss during entry; and (2) rapid planet rotation, which introduced terms of motion not needed on Venus. When the Galileo Probe encountered Jupiter, analysis and interpretation of data commenced. The early contributions of the experiment were to define (1) the basic structure of the deep atmosphere, (2) the stability of the atmosphere, (3) the upper atmospheric profiles of density, pressure, and temperature. The next major task in the Galileo Probe project was to refine, verify and extend the analysis of the data. It was the verified, and corrected data, which indicated a dry abiabatic atmosphere within measurement accuracy. Temperature in the thermosphere was measured at 900 K. Participation in the Mars atmospheric research included: (1) work as a team member of the Mars Atmosphere Working Group, (2) contribution to the Mars Exobiology Instrument workshop, (3) asssistance in planning the Mars global network and (4) assitance in planning the Soviet-French Mars mission in 1994. This included a return to the Viking Lander parachute data to refine and improve the definition of winds between 1.5 and 4 kilometer altitude at the two entry sites. The variability of the structure of Mars atmosphere was addressed, which is known to vary with season, latitude, hemisphere and dust loading of the atmosphere. This led to work on the Pathfinder project. The probe had a deployable meteorology mast that had three temperature sensors, and a wind sensor at the tip of the mast. Work on the Titan atmospheric probe was also accomplished. This included developing an experiment proposal to the European Space Agency (ESA), which was not selected. However, as an advisor in the design and preparation of the selected experiment the researcher interacted with scientist on the Huygens Probe Atmosphere Structure Experiment. The researcher also participated in the planning for the Venus Chemical Probe. The science objectives of the probe were to resolve unanswered questions concerning the minor species chemistry of Venus' atmosphere that control cloud formation, greenhouse effectiveness, and the thermal structure. The researcher also reviewed problems with the Pioneer Venus Probe, that caused anomalies which occurred on the Probes at and below 12.5 km level of the Venus' atmosphere. He convened and participated in a workshop that concluded the most likely hardware cause was insulation failure in the electrical harness outside the Probes' pressure vessels. It was discovered that the shrink tubing material failed at 600K. This failure could explain the anomalies experienced by the probes. The descent data of the Pioneer probes, and the Soviet Vega Lander was analyzed to evaluate the presence of small scale gravity waves in and below the Venus cloud layer.

Lester, Peter↗

STS-56 Launch Attempt Press Conference

Dick Young introduces Dr. Jack Kaye, Program Scientist for NASA, Brewster Shaw, Deputy Program Manager Space Shuttle, and Robert Sieck, Kennedy Space Center (KSC) Launch Director in a press conference regarding the failed launch attempt of the Discovery Orbiter. The hardware problem causing the failure is discussed, and questions from the press are answered.

Source record↗

Rocket Science for the Internet

Rainfinity, a company resulting from the commercialization of Reliable Array of Independent Nodes (RAIN), produces the product, Rainwall. Rainwall runs a cluster of computer workstations, creating a distributed Internet gateway. When Rainwall detects a failure in software or hardware, traffic is shifted to a healthy gateway without interruptions to Internet service. It more evenly distributes workload across servers, providing less down time.

Source record↗

Integration of the Remote Agent for the NASA Deep Space One Autonomy Experiment

This paper describes the integration of the Remote Agent (RA), a spacecraft autonomy system which is scheduled to control the Deep Space 1 spacecraft during a flight experiment in 1999. The RA is a reusable, model-based autonomy system that is quite different from software typically used to control an aerospace system. We describe the integration challenges we faced, how we addressed them, and the lessons learned. We focus on those aspects of integrating the RA that were either easier or more difficult than integrating a more traditional large software application because the RA is a model-based autonomous system. A number of characteristics of the RA made integration process easier. One example is the model-based nature of RA. Since the RA is model-based, most of its behavior is not hard coded into procedural program code. Instead, engineers specify high level models of the spacecraft's components from which the Remote Agent automatically derives correct system-wide behavior on the fly. This high level, modular, and declarative software description allowed some interfaces between RA components and between RA and the flight software to be automatically generated and tested for completeness against the Remote Agent's models. In addition, the Remote Agent's model-based diagnosis system automatically diagnoses when the RA models are not consistent with the behavior of the spacecraft. In flight, this feature is used to diagnose failures in the spacecraft hardware. During integration, it proved valuable in finding problems in the spacecraft simulator or flight software. In addition, when modifications are made to the spacecraft hardware or flight software, the RA models are easily changed because they only capture a description of the spacecraft. one does not have to maintain procedural code that implements the correct behavior for every expected situation. On the other hand, several features of the RA made it more difficult to integrate than typical flight software. For example, the definition of correct behavior is more difficult to specify for a system that is expected to reason about and flexibly react to its environment than for a traditional flight software system. Consequently, whenever a change is made to the RA it is more time consuming to determine if the resulting behavior is correct. We conclude the paper with a discussion of future work on the Remote Agent as well as recommendations to ease integration of similar autonomy projects.

Dorais, Gregory A.↗

Causes and Mitigation of Fuel Pilot Operated Valve Pilot Seal Extrusion in Space Shuttle Orbiter Primary RCS Thrusters

Extrusion of a polytetrafluoroethylene (PTFE) pilot seal located in the Space Shuttle Orbiter Primary Reaction Control Subsystem (PRCS) thruster fuel valve has been implicated in 68 ground and on-orbit fuel valve failures. A rash of six extrusion-related in-flight anomalies over a six-mission span from December 2001 to October 2002 led to heightened activity at various NASA centers, and the formation of a multidisciplinary team to solve the problem. Empirical and theoretical approaches were used. For example, thermomechanical analysis (TMA) and exposure tests showed that some extrusion is produced by thermal cycling; however, a review of thruster service histories did not reveal a strong link between thermal cycling and extrusion. Calculations showed that the amount of observed extrusion often exceeded the amount allowed by thermally-induced stress relief. Failure analysis of failed hardware also revealed the presence of fuel-oxidizer reaction product (FORP) inside the fuel valve pilot seal cavity, and differential scanning calorimetry (DSC) showed that the FORP was intimately associated with the pilot seal material. Component-level exposure tests showed that FORP of similar composition could be produced by adjacent oxidizer valve leakage in the absence of thruster firing. Specific gravity data showed that extruded fuel valve pilot seals were less dense than new pilot seals or oxidizer valve pilot seals, indicating permanent modification of the PTFE occurred during service. It is concluded that some thermally-induced extrusion is unavoidable; however, oxidizer leakage-induced extrusion is mostly avoidable and can be mitigated. Several engineering level mitigation strategies are discussed.

Waller, Jess M.↗

Extravehicular Mobility Unit (EMU) / International Space Station (ISS) Coolant Loop Failure and Recovery

Following the Colombia accident, the Extravehicular Mobility Units (EMU) onboard ISS were unused for several months. Upon startup, the units experienced a failure in the coolant system. This failure resulted in the loss of Extravehicular Activity (EVA) capability from the US segment of ISS. With limited on-orbit evidence, a team of chemists, engineers, metallurgists, and microbiologists were able to identify the cause of the failure and develop recovery hardware and procedures. As a result of this work, the ISS crew regained the capability to perform EVAs from the US segment of the ISS.

Lewis, John F.↗

The Hyper-X Flight Systems Validation Program

For the Hyper-X/X-43A program, the development of a comprehensive validation test plan played an integral part in the success of the mission. The goal was to demonstrate hypersonic propulsion technologies by flight testing an airframe-integrated scramjet engine. Preparation for flight involved both verification and validation testing. By definition, verification is the process of assuring that the product meets design requirements; whereas validation is the process of assuring that the design meets mission requirements for the intended environment. This report presents an overview of the program with emphasis on the validation efforts. It includes topics such as hardware-in-the-loop, failure modes and effects, aircraft-in-the-loop, plugs-out, power characterization, antenna pattern, integration, combined systems, captive carry, and flight testing. Where applicable, test results are also discussed. The report provides a brief description of the flight systems onboard the X-43A research vehicle and an introduction to the ground support equipment required to execute the validation plan. The intent is to provide validation concepts that are applicable to current, follow-on, and next generation vehicles that share the hybrid spacecraft and aircraft characteristics of the Hyper-X vehicle.

Redifer, Matthew↗

Space Transportation System Availability Requirement and Its Influencing Attributes Relationships

It is important that engineering and management accept the need for an availability requirement that is derived with its influencing attributes. It is the intent of this paper to provide the visibility of relationships of these major attribute drivers (variables) to each other and the resultant system inherent availability. Also important to provide bounds of the variables providing engineering the insight required to control the system's engineering solution, e.g., these influencing attributes become design requirements also. These variables will drive the need to provide integration of similar discipline functions or technology selection to allow control of the total parts count. The relationship of selecting a reliability requirement will place a constraint on parts count to achieve a given availability requirement or if allowed to increase the parts count will drive the system reliability requirement higher. They also provide the understanding for the relationship of mean repair time (or mean down time) to maintainability, e.g., accessibility for repair, and both the mean time between failure, e.g., reliability of hardware and availability. The concerns and importance of achieving a strong availability requirement is driven by the need for affordability, the choice of using the two launch solution for the single space application, or the need to control the spare parts count needed to support the long stay in either orbit or on the surface of the moon. Understanding the requirements before starting the architectural design concept will avoid considerable time and money required to iterate the design to meet the redesign and assessment process required to achieve the results required of the customer's space transportation system. In fact the impact to the schedule to being able to deliver the system that meets the customer's needs, goals, and objectives may cause the customer to compromise his desired operational goal and objectives resulting in considerable increased life cycle cost of the fielded space transportation system.

Rhodes, Russell E.↗

Space Transportation System Availability Requirements and Its Influencing Attributes Relationships

It is important that engineering and management accept the need for an availability requirement that is derived with its influencing attributes. It is the intent of this paper to provide the visibility of relationships of these major attribute drivers (variables) to each other and the resultant system inherent availability. Also important to provide bounds of the variables providing engineering the insight required to control the system's engineering solution, e.g., these influencing attributes become design requirements also. These variables will drive the need to provide integration of similar discipline functions or technology selection to allow control of the total parts count. The relationship of selecting a reliability requirement will place a constraint on parts count to achieve a given availability requirement or if allowed to increase the parts count will drive the system reliability requirement higher. They also provide the understanding for the relationship of mean repair time (or mean down time) to maintainability, e.g., accessibility for repair, and both the mean time between failure, e.g., reliability of hardware and availability. The concerns and importance of achieving a strong availability requirement is driven by the need for affordability, the choice of using the two launch solution for the single space application, or the need to control the spare parts count needed to support the long stay in either orbit or on the surface of the moon. Understanding the requirements before starting the architectural design concept will avoid considerable time and money required to iterate the design to meet the redesign and assessment process required to achieve the results required of the customer's space transportation system. In fact the impact to the schedule to being able to deliver the system that meets the customer's needs, goals, and objectives may cause the customer to compromise his desired operational goal and objectives resulting in considerable increased life cycle cost of the fielded space transportation system.

Rhodes, Russell E.↗

Space Transportation System Availability Requirement and Its Influencing Attributes Relationships

It is important that engineering and management accept the need for an availability requirement that is derived with its influencing attributes. It is the intent of this paper to provide the visibility of relationships of these major attribute drivers (variables) to each other and the resultant system inherent availability. Also important to provide bounds of the variables providing engineering the insight required to control the system's engineering solution, e.g., these influencing attributes become design requirements also. These variables will drive the need to provide integration of similar discipline functions or technology selection to allow control of the total parts count. The relationship of selecting a reliability requirement will place a constraint on parts count to achieve a given availability requirement or if allowed to increase the parts count will drive the system reliability requirement higher. They also provide the understanding for the relationship of mean repair time (or mean down time) to maintainability, e.g., accessibility for repair, and both the mean time between failure, e.g., reliability of hardware and availability. The concerns and importance of achieving a strong availability requirement is driven by the need for affordability, the choice of using the two launch solution for the single space application, or the need to control the spare parts count needed to support the long stay in either orbit or on the surface of the moon. Understanding the requirements before starting the architectural design concept will avoid considerable time and money required to iterate the design to meet the redesign and assessment process required to achieve the results required of the customer's space transportation system. In fact the impact to the schedule to being able to deliver the system that meets the customer's needs, goals, and objectives may cause the customer to compromise his desired operational goal and objectives resulting in considerable increased life cycle cost of the fielded space transportation system.

reliability↗

Overview of Nondestructive Evaluation Capabilities at NASA MSFC

Nondestructive evaluation (NDE) methods examine material integrity without impairing its usefulness. The NDE team at NASA Marshall Space Flight Center (MSFC) in Huntsville, Alabama is responsible for applying existing methods to new hardware designs and material systems, probability of detection studies to quantify detection capabilities, overseeing NDE requirements for flight hardware, inspecting development articles and flight hardware, engineering support for failure investigations, and investigating emerging NDE methods. NASA MSFC has been on the cutting edge of developing new NDE techniques, first for the space shuttle, then for composite structures, and most recently for additive manufacturing (AM). Standard in-house inspection capabilities include eddy current, magnetic particle, liquid penetrant, ultrasonic, and radiographic testing (including computed tomography). Other advanced inspection capabilities include infrared flash thermography, shearography, acoustic emission, and microwave/millimeter wave testing. Some recent research studies include AM probability of detection testing, investigating in-situ process monitoring methods for AM, and correlating the NDE response of true fatigue cracks with artificial notches.

nondestructive evaluation↗