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…
(2) to down-weight only slightly, or not at all, those failures that are random in
nature, that can still occur in replacement components, or that occur only once in
100 or several hundred launches in components that have not yet failed.
No matter what technique is employed, filtering is at best a compromise. The perfect
filter would somehow down-weight to some extent or entirely those failures that have
been "fixed" or made less likely, without down-weighting those random failures with
unknown causes. The filters considered in this study have no such capabilities; they
produce a result based solely on the launch sequence, and where in the sequence
failures have occurred.
In predicting vehicle failure probabilities from empirical data, large representative
samples are essential for a good estimate, and the more reliable the vehicle, the greater
the need for a large sample. For example, if some characteristic exists in exactly 1% of a
population, the probability is 0.37 that it will not appear in a random sample of 100,
and 0.61 that it will not appear if the sample size is 50. If the characteristic exists in 2%
of the population, it fails to- appear about 36% of the time in a random sample of 50.
For reasons presented above, the data samples for Atlas, Delta, and Titan have been
made as large as possible consistent with the notion of representative configurations, as
set forth in Ref. [4]. In RTI's judgment, the value of F that best weights the performance
data is 0.98, although a value anywhere in the interval 0.97 to 0.99 cannot be ruled out.
For consistency in data weighting, the same values of F have been used for all vehicle
programs. The differences in predicted failure probability that result from these three
F's are illustrated in Figure 4 for Atlas. The plots show the inverse relationship
between filter volatility and the value of F. For F = 0.97 vis-a-vis larger values, it can be
seen that the filtered failure probability jumps higher with each failure and drops at a
faster rate with each successful launch that follows.
9/10/96 22 RTI

Not linked to a story yet.

About this file

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