Documents / Report

Department of the Air Force Report, 1996

U.S. Department of War · 1996-09-10 · 181 pages · text from the file's own layer

This final report, dated September 10, 1996, was prepared by the Research Triangle Institute for the Department of the Air Force's 45th and 30th Space Wing safety offices. Titled Modeling Unlikely Space-Booster Failures in Risk Calculations, it shows how rare Mode-5 failures, in which a rocket veers well off its intended flight line, are modeled in the DAMP risk-analysis program. An appendix lists Atlas, Delta, Titan and Thor launch and failure histories through August 1996.

From the source:Release of 2026-05-08 Incident: 9/10/96, N/A. This report describes the Modeling of Unlikely Space-Booster Failures in Risk Calculations, documenting historical launch failure modes and recommending corrective actions to address them using novel modelling techniques.

  • p. 88 …Vehicle loses control at or shortly after liftoff, with all flight directions equally likely. Destruct is…
  • p. 106 …121 (8) Missiles/Space Vehicle Files, 45th Space Wing, Wing Safety, Mission Flight Control and Analysis…
  • p. 111 …Such behavior did not necessarily prevent the attainment of some, or even all, mission objectives. 50…
  • p. 131 …Due to excess speed, spacecraft passed 22,000 miles in front of moon, and primary mission…
  • p. 132 …Although Atlas performance was satisfactory, the mission was apparently a failure. No other data available. 134…
  • p. 133 …A flight-control malfunction occurred at about 15 seconds at the start of the pitch program…
  • p. 137 …Vehicle became unstable when B2 pitch control was lost at 121 seconds. Loss of pitch control…
  • p. 138 …The missile then lost attitude control, executing a hard yaw rate tum throughout and beyond the…
  • p. 139 …of the rate gyro or an electrical failure in the pitch channel of the flight control…
  • p. 140 caused yaw and roll rates that the flight control system could not correct. As a result…
  • p. 151 …Attitude control lost during second stage coast period. Third stage spun up, but did not fire…
  • p. 153 …One solid-rocket motor carried to MECO, but mission was still a complete success. 102. SMS…
  • p. 169 …Missile tumbled out of control at 130 seconds, then broke up. 104. IHA (65-210), 1…
  • p. 170 …Nominal mission through transtage second burn shutdown. Attitude control system engine failed to shutdown following vernier…
  • p. 171 …However, satellite propulsion system malfunctioned putting satellite in uncontrollable position with no possibility of restoring mission…
  • p. 172 …control until propellant depletion. Trajectory inaccuracies were compensated for during Stage-2 burn, and the mission…
  • p. 180 …Missiles/Space Vehicle Files, 45th Space Wing, Wing Safety, Mission Flight Control and Analysis (SEO), 1957…
8. Summary
In RTI's risk-computation program DAMP, vehicle failures per se are not considered.
Instead each catastrophic failure is assumed to· produce one of five failure responses,
and it is these response modes that are modeled in DAMP. Although most catastrophic
failures result in impacts near the flight line, less likely malfunctions may cause debris
to fall either uprange or well away from the flight line. In DAMP, vehicle failures with
this potential are, for the most part, classified as Mode-5 failure responses. The
resulting impacts are modeled by a rather formidable-looking density function that
includes two shaping constants (A and B) that strongly influence the nature of the
impact-density function. To obtain absolute probabilities (or risks), the function must
be multiplied by-a probability-of-occurrence factor (p5). The primary purpose of this
study was to determine the best values for A, B, and p5 for various vehicle programs.
Other objectives not explicitly included in the statement of work were to develop
absolute failure probabilities for Atlas, Delta, and Titan and to derive relative
probabilities of occurrence for the five failure-response modes in DAMP.
Although some risk analyses may ignore unlikely failure-response modes, Section 2
demonstrates the _need for a Mode-5 response - or some similar response - through
brief descriptions of actual vehicle flights. Section 3 and Appendix B provide the
reader with a fuller understanding of the nature and intricacies of the Mode-5 impact-
density function. Together, they show how density-function shaping is affected by
values of A and B, and in particular how the Atlas IIAS launch-area risk _contours
change if the value of A is changed.
Section 4 is a philosophical discussion of methods of assessing vehicle failure
probability (or reliability). Two approaches are discussed, one strictly empirical, the
other a parts-analysis method that involves the assignment of failure probabilities to
individual parts, components, and systems. Although difficulties exist with both
approaches, the empirical method was chosen to estimate both absolute and relative
failure probabilities.
-As the first step in estimating failure probabilities empirically, performance histories
were gathered, summarized, and tabulated (Appendix D) by launch date for Atlas,
Delta, and Titan vehicle launches from the Eastern and Western Ranges, and for Thor
launches from the Eastern Range. Obtaining this information, and assigning response
modes and associated flight phases for each failure consumed a large portion of the
effort expended on this task.
A filtering (i.e., data weighting) technique was selected (see Section 5.1 and
Appendix C) and applied to the launch failure data to estimate overall failure
probabilities by flight phase (see Section D.1.3) for Atlas, Delta, and Titan vehicles. The
recommended failure probabilities are based on test results involving only those
vehicle configurations that are considered to be representative of current launch
9/10/% 74 RTI

Not linked to a story yet.

About this file

Report, from the pursue collection. The PDF is mirrored here; the original link is above. 181 pages are in the text index: search them above, or from the library's search.