Search NASA⌕ Search

SEARCH · Search NASA

Results for “Flight 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 91 records · Page 5

First incremental buy for Increment 2 of the Space Transportation System (STS)

Thiokol manufactured and delivered 9 flight motors to KSC on schedule. All test flights were successful. All spent SRMs were recovered. Design, development, manufacture, and delivery of required transportation, handling, and checkout equipment to MSFC and to KSC were completed on schedule. All items of data required by DPD 400 were prepared and delivered as directed. In the system requirements and analysis area, the point of departure from Buy 1 to the operational phase was developed in significant detail with a complete set of transition documentation available. The documentation prepared during the Buy 1 program was maintained and updated where required. The following flight support activities should be continued through other production programs: as-built materials usage tracking on all flight hardware; mass properties reporting for all flight hardware until sample size is large enough to verify that the weight limit requirements were met; ballistic predictions and postflight performance assessments for all production flights; and recovered SRM hardware inspection and anomaly identification. In the safety, reliability, and quality assurance area, activities accomplished were assurance oriented in nature and specifically formulated to prevent problems and hardware failures. The flight program to date has adequately demonstrated the success of this assurance approach. The attention focused on details of design, analysis, manufacture, and inspection to assure the production of high-quality hardware has resulted in the absence of flight failures. The few anomalies which did occur were evaluated, design or manufacturing changes incorporated, and corrective actions taken to preclude recurrence.

Source record↗

Global Response of the Space Shuttle External Tank with the Presence of Intertank Stringer Cracks and Radius Blocks

After propellant was loaded into the external tank (ET), the November 5, 2010 launch of Space Shuttle mission STS-133 was scrubbed due to a gaseous hydrogen leak located in a vent line near the ground umbilical and ET connection. Subsequent visual inspections identified cracks in the sprayed-on foam insulation in the forward end of the ET intertank segment, adjacent to the liquid oxygen (LOX) tank, as shown in Figure 1. These cracks necessitated repair of the foam due to debris concerns that violated launch constraints. As part of the repair process, the affected foam was removed to reveal cracks in the underlying external hat stiffeners on the intertank, as shown in Figure 2. Ultimately, five stiffeners were discovered to be cracked adjacent to the LOX tank. As the managing center for the ET Project, NASA Marshall Space Flight Center (MSFC) coordinated failure investigation and repair activities among multiple organizations, which included the ET prime contractor (Lockheed Martin Space Systems Michoud Operations), the Space Shuttle Program Office at the NASA Johnson Space Center (JSC), the NASA Kennedy Space Center (KSC), and the NASA Engineering and Safety Center (NESC). STS-133 utilized the external tank designated as ET-137. Many aspects of the investigation have been reported previously in Refs. 1-7, which focus on the root cause of the failures, the flight readiness rationale and the local analyses of the stringer failures and repair. This paper summarizes the global analyses that were conducted on ET-137 as part of the NESC effort during the investigation, which was conducted primarily to determine if the repairs that were introduced to the stringers would alter the global response of the ET. In the process of the investigation, a new STAGS tabular input capability was developed to more easily introduce the aerodynamic pressure loads using a method that could easily be extended to incorporate finite element property data such as skin and stiffener thicknesses and beam cross-sectional properties.

Lovejoy, Andrew E.↗

Sliding Mode Control of the X-33 with an Engine Failure

Ascent flight control of the X-3 is performed using two XRS-2200 linear aerospike engines. in addition to aerosurfaces. The baseline control algorithms are PID with gain scheduling. Flight control using an innovative method. Sliding Mode Control. is presented for nominal and engine failed modes of flight. An easy to implement, robust controller. requiring no reconfiguration or gain scheduling is demonstrated through high fidelity flight simulations. The proposed sliding mode controller utilizes a two-loop structure and provides robust. de-coupled tracking of both orientation angle command profiles and angular rate command profiles in the presence of engine failure, bounded external disturbances (wind gusts) and uncertain matrix of inertia. Sliding mode control causes the angular rate and orientation angle tracking error dynamics to be constrained to linear, de-coupled, homogeneous, and vector valued differential equations with desired eigenvalues. Conditions that restrict engine failures to robustness domain of the sliding mode controller are derived. Overall stability of a two-loop flight control system is assessed. Simulation results show that the designed controller provides robust, accurate, de-coupled tracking of the orientation angle command profiles in the presence of external disturbances and vehicle inertia uncertainties, as well as the single engine failed case. The designed robust controller will significantly reduce the time and cost associated with flying new trajectory profiles or orbits, with new payloads, and with modified vehicles

Shtessel, Yuri B.↗

CRYOGENIC UPPER STAGE SYSTEM SAFETY

NASA s Exploration Initiative will require development of many new systems or systems of systems. One specific example is that safe, affordable, and reliable upper stage systems to place cargo and crew in stable low earth orbit are urgently required. In this paper, we examine the failure history of previous upper stages with liquid oxygen (LOX)/liquid hydrogen (LH2) propulsion systems. Launch data from 1964 until midyear 2005 are analyzed and presented. This data analysis covers upper stage systems from the Ariane, Centaur, H-IIA, Saturn, and Atlas in addition to other vehicles. Upper stage propulsion system elements have the highest impact on reliability. This paper discusses failure occurrence in all aspects of the operational phases (Le., initial burn, coast, restarts, and trends in failure rates over time). In an effort to understand the likelihood of future failures in flight, we present timelines of engine system failures relevant to initial flight histories. Some evidence suggests that propulsion system failures as a result of design problems occur shortly after initial development of the propulsion system; whereas failures because of manufacturing or assembly processing errors may occur during any phase of the system builds process, This paper also explores the detectability of historical failures. Observations from this review are used to ascertain the potential for increased upper stage reliability given investments in integrated system health management. Based on a clear understanding of the failure and success history of previous efforts by multiple space hardware development groups, the paper will investigate potential improvements that can be realized through application of system safety principles.

Smith, R. Kenneth↗

Wind-tunnel Tests of a 2-engine Airplane Model as a Preliminary Study of Flight Conditions Arising on the Failure of the Engine

Wind tunnel tests of a 15-foot-span model of a two-engine low wing transport airplane were made as a preliminary study of the emergency arising from the failure of one engine in flight. Two methods of reducing the initial yawing moment resulting from the failure of one engine were investigated and the equilibrium conditions were explored for two basic modes on one engine, one with zero angle of sideslip and the other with several degrees of sideslip. The added drag resulting from the unsymmetrical attitudes required for flight on one engine was determined for the model airplane. The effects of the application of power upon the stability, controllability, lift, and drag of the model airplane were measured. A dynamic pressure survey of the propeller slipstream was made in the neighborhood of the tail surfaces at three angles of attack. The added parasite drag of the model airplane resulting from the unfavorable conditions of flight on one engine was estimated. From 35 to 50 percent of this added drag was due to the drag of the dead engine propeller and the other 50 to 65 percent was due to the unsymmetrical attitude of the airplane. The mode of flight on one engine in which the angle of sideslip was zero was found to require less power than the mode in which the angle of sideslip was several degrees.

Hartman, Edwin P↗

An improved approach for flight readiness certification: Methodology for failure risk assessment and application examples, volume 1

An improved methodology for quantitatively evaluating failure risk of spaceflight systems to assess flight readiness and identify risk control measures is presented. This methodology, called Probabilistic Failure Assessment (PFA), combines operating experience from tests and flights with engineering analysis to estimate failure risk. The PFA methodology is of particular value when information on which to base an assessment of failure risk, including test experience and knowledge of parameters used in engineering analyses of failure phenomena, is expensive or difficult to acquire. The PFA methodology is a prescribed statistical structure in which engineering analysis models that characterize failure phenomena are used conjointly with uncertainties about analysis parameters and/or modeling accuracy to estimate failure probability distributions for specific failure modes. These distributions can then be modified, by means of statistical procedures of the PFA methodology, to reflect any test or flight experience. Conventional engineering analysis models currently employed for design of failure prediction are used in this methodology. The PFA methodology is described and examples of its application are presented. Conventional approaches to failure risk evaluation for spaceflight systems are discussed, and the rationale for the approach taken in the PFA methodology is presented. The statistical methods, engineering models, and computer software used in fatigue failure mode applications are thoroughly documented.

Moore, N. R.↗

An improved approach for flight readiness certification: Methodology for failure risk assessment and application examples. Volume 2: Software documentation

An improved methodology for quantitatively evaluating failure risk of spaceflight systems to assess flight readiness and identify risk control measures is presented. This methodology, called Probabilistic Failure Assessment (PFA), combines operating experience from tests and flights with engineering analysis to estimate failure risk. The PFA methodology is of particular value when information on which to base an assessment of failure risk, including test experience and knowledge of parameters used in engineering analyses of failure phenomena, is expensive or difficult to acquire. The PFA methodology is a prescribed statistical structure in which engineering analysis models that characterize failure phenomena are used conjointly with uncertainties about analysis parameters and/or modeling accuracy to estimate failure probability distributions for specific failure modes, These distributions can then be modified, by means of statistical procedures of the PFA methodology, to reflect any test or flight experience. Conventional engineering analysis models currently employed for design of failure prediction are used in this methodology. The PFA methodology is described and examples of its application are presented. Conventional approaches to failure risk evaluation for spaceflight systems are discussed, and the rationale for the approach taken in the PFA methodology is presented. The statistical methods, engineering models, and computer software used in fatigue failure mode applications are thoroughly documented.

Moore, N. R.↗

An improved approach for flight readiness certification: Methodology for failure risk assessment and application examples. Volume 3: Structure and listing of programs

An improved methodology for quantitatively evaluating failure risk of spaceflight systems to assess flight readiness and identify risk control measures is presented. This methodology, called Probabilistic Failure Assessment (PFA), combines operating experience from tests and flights with engineering analysis to estimate failure risk. The PFA methodology is of particular value when information on which to base an assessment of failure risk, including test experience and knowledge of parameters used in engineering analyses of failure phenomena, is expensive or difficult to acquire. The PFA methodology is a prescribed statistical structure in which engineering analysis models that characterize failure phenomena are used conjointly with uncertainties about analysis parameters and/or modeling accuracy to estimate failure probability distributions for specific failure modes. These distributions can then be modified, by means of statistical procedures of the PFA methodology, to reflect any test or flight experience. Conventional engineering analysis models currently employed for design of failure prediction are used in this methodology. The PFA methodology is described and examples of its application are presented. Conventional approaches to failure risk evaluation for spaceflight systems are discussed, and the rationale for the approach taken in the PFA methodology is presented. The statistical methods, engineering models, and computer software used in fatigue failure mode applications are thoroughly documented.

Moore, N. R.↗

Synthesizing a New Launch Vehicle Failure Probability Based on Historical Flight Data

New launch vehicles have historically had significantly higher failure probabilities in early flights than what has been predicted using Probabilistic Risk Assessment. Work on a new methodology originally started with ARES I-X and the Common Standards Working Group (CSWG) for range safety applications. CSWG consists of the Federal Aviation Administration (FAA), Air Force, and NASA. Historical launch vehicle data was viewed as the best predictor of success/failure for launches of new vehicles. A launch vehicle database was developed that includes all launches from 1980-2017 (both US and foreign). Entries to the database include: Vehicle by model type; Launch dates; Failure description; Failure Result (Loss Of Vehicle (LOV)/Loss Of Mission (LOM); Failure cause (when available); Vehicle designs (stages/engines/etc.)

Early flight risk↗

Aircraft Engine Run-to-Failure Dataset Under Real Flight Conditions for Prognostics and Diagnostics

A key enabler of intelligent maintenance systems is the ability to predict the remaining useful lifetime (RUL) of its components, i.e., prognostics. The development of data-driven prognostics models requires datasets with run-to-failure trajectories. However, large representative run-to-failure datasets are often unavailable in real applications because failures are rare in many safety-critical systems. To foster the development of prognostics methods, we develop a new realistic dataset of run-to-failure trajectories for a fleet of aircraft engines under real flight conditions. The dataset was generated with the Commercial Modular Aero-Propulsion System Simulation (CMAPSS) model developed at NASA. The damage propagation modelling used in this dataset builds on the modelling strategy from previous work and incorporates two new levels of fidelity. First, it considers real flight conditions as recorded on board of a commercial jet. Second, it extends the degradation modelling by relating the degradation process to its operation history. This dataset also provides the health respectively fault class. Therefore, besides its applicability to prognostics problems, the dataset can be used for fault diagnostics.

CMAPPS↗

Spacecraft Software Maintenance: An Effective Approach to Reducing Costs and Increasing Science Return

Flight software is a mission critical element of spacecraft functionality and performance. When ground operations personnel interface to a spacecraft, they are typically dealing almost entirely with the capabilities of onboard software. This software, even more than critical ground/flight communications systems, is expected to perform perfectly during all phases of spacecraft life. Due to the fact that it can be reprogrammed on-orbit to accommodate degradations or failures in flight hardware, new insights into spacecraft characteristics, new control options which permit enhanced science options, etc., the on- orbit flight software maintenance team is usually significantly responsible for the long term success of a science mission. Failure of flight software to perform as needed can result in very expensive operations work-around costs and lost science opportunities. There are three basic approaches to maintaining spacecraft software--namely using the original developers, using the mission operations personnel, or assembling a center of excellence for multi-spacecraft software maintenance. Not planning properly for flight software maintenance can lead to unnecessarily high on-orbit costs and/or unacceptably long delays, or errors, in patch installations. A common approach for flight software maintenance is to access the original development staff. The argument for utilizing the development staff is that the people who developed the software will be the best people to modify the software on-orbit. However, it can quickly becomes a challenge to obtain the services of these key people. They may no longer be available to the organization. They may have a more urgent job to perform, quite likely on another project under different project management. If they havn't worked on the software for a long time, they may need precious time for refamiliarization to the software, testbeds and tools. Further, a lack of insight into issues related to flight software in its on-orbit environment, may find the developer unprepared for the challenges. The second approach is to train a member of the flight operations team to maintain the spacecraft software. This can prove to be a costly and inflexible solution. The person assigned to this duty may not have enough work to do during a problem free period and may have too much to do when a problem arises. If the person is a talented software engineer, he/she may not enjoy the limited software opportunities available in this position; and may eventually leave for newer technology computer science opportunities. Training replacement flight software personnel can be a difficult and lengthy process. The third approach is to assemble a center of excellence for on-orbit spacecraft software maintenance. Personnel in this specialty center can be managed to support flight software of multiple missions at once. The variety of challenges among a set of on-orbit missions, can result in a dedicated, talented staff which is fully trained and available to support each mission's needs. Such staff are not software developers but are rather spacecraft software systems engineers. The cost to any one mission is extremely low because the software staff works and charges, minimally on missions with no current operations issues; and their professional insight into on-orbit software troubleshooting and maintenance methods ensures low risk, effective and minimal-cost solutions to on-orbit issues.

Shell, Elaine M.↗

Project Ares 3

The mission of Project Ares is to design and fabricate an Earth prototype, autonomous flying rover capable of flying on the Martian surface. The project was awarded to California State University, Northridge (CSUN) in 1989 where an in-depth paper study was completed. The second year's group, Project Ares 2, designed and fabricated a full-scale flight demonstration aircraft. Project Ares 3, the third and final group, is responsible for propulsion system design and installation, controls and instrumentation, and high altitude testing. The propulsion system consists of a motor and its power supply, geartrain, and propeller. The motor is a four-brush DC motor powered by a 50-V NiCd battery supply. A pulley and belt arrangement is used for the geartrain and includes light weight, low temperature materials. The propeller is constructed from composite materials which ensures high strength and light weight, and is specifically developed to provide thrust at extremely high altitudes. The aircraft is controlled with a ground-based radio control system and an autopilot which will activate in the event that the control signal is lost. A transponder is used to maintain radar contact for ground tracking purposes. The aircraft possesses a small, onboard computer for collecting and storing flight data. To safeguard the possibility of computer failure, all flight data is transmitted to a ground station via a telemetry system. An initial, unpowered, low-level test flight was completed in August of 1991. Testing of systems integration in the second low-level test flight resulted in loss of elevator control which caused considerable damage on landing. Complete failure analysis and repairs are scheduled for September of 1992.

Raymer, Dan↗

A pilot rating scale for evaluating failure transients in electronic flight control systems

A pilot rating scale was developed to describe the effects of transients in helicopter flight-control systems on safety-of-flight and on pilot recovery action. The scale was applied to the evaluation of hardovers that could potentially occur in the digital flight-control system being designed for a variable-stability UH-60A research helicopter. Tests were conducted in a large moving-base simulator and in flight. The results of the investigation were combined with existing airworthiness criteria to determine quantitative reliability design goals for the control system.

Hindson, William S.↗

Excitations for Rapidly Estimating Flight-Control Parameters

A flight test on an F-15 airplane was performed to evaluate the utility of prescribed simultaneous independent surface excitations (PreSISE) for real-time estimation of flight-control parameters, including stability and control derivatives. The ability to extract these derivatives in nearly real time is needed to support flight demonstration of intelligent flight-control system (IFCS) concepts under development at NASA, in academia, and in industry. Traditionally, flight maneuvers have been designed and executed to obtain estimates of stability and control derivatives by use of a post-flight analysis technique. For an IFCS, it is required to be able to modify control laws in real time for an aircraft that has been damaged in flight (because of combat, weather, or a system failure). The flight test included PreSISE maneuvers, during which all desired control surfaces are excited simultaneously, but at different frequencies, resulting in aircraft motions about all coordinate axes. The objectives of the test were to obtain data for post-flight analysis and to perform the analysis to determine: 1) The accuracy of derivatives estimated by use of PreSISE, 2) The required durations of PreSISE inputs, and 3) The minimum required magnitudes of PreSISE inputs. The PreSISE inputs in the flight test consisted of stacked sine-wave excitations at various frequencies, including symmetric and differential excitations of canard and stabilator control surfaces and excitations of aileron and rudder control surfaces of a highly modified F-15 airplane. Small, medium, and large excitations were tested in 15-second maneuvers at subsonic, transonic, and supersonic speeds. Typical excitations are shown in Figure 1. Flight-test data were analyzed by use of pEst, which is an industry-standard output-error technique developed by Dryden Flight Research Center. Data were also analyzed by use of Fourier-transform regression (FTR), which was developed for onboard, real-time estimation of the derivatives.

Moes, Tim↗

Intelligent situation assessment and response aiding in flight emergencies

A knowledge-based pilot aiding system which performs situation assessment and response aiding is described. The system uses a causal model of the flight domain to both simulate the effects of identified failures on flight and to derive responses during emergencies. The model represents information at two levels of abstraction: Boolean, which simply states whether a subsystem or aircraft component is normal or abnormal, and qualitative, which expresses the subsystem or component status as one of several qualitative values, such as increasing, decreasing, or stable.

Hudlicka, Eva↗