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…
96. ITOS:-E (WTR), 16 July 73, Response Mode 4T, Flight Phase 2: Pump-motor failure
during second-stage bum at 490 seconds resulted in loss of hydraulic pressure,
loss of attitude control, and vehicle tumbling.
100. Skynet IIA, 19 Jan 74, Response Mode NA, Flight Phase 4 and 5: Flight was within
normal limits until impact point passed through Africa gate. During the second
bum of the second stage, a short circuit in the second-stage electronics package
resulted· in an improper spacecraft orbit. The satellite reentered the earth's
atmosphere five days later on 24 Jan 74.
101. WESTAR-B, 13 Apr 74, Response Mode NA, Flight Phase 1: One solid-rocket
motor carried to MECO, but mission was still a complete success.
102. SMS-A, 17 May 74, Response Mode NA, Flight Phase 1 and 5: Mission was a
partial success, although low first-stage velocity resulted from a liquid oxygen
pressure line failure, and a booster shroud that snagged before fully jettisoning.
Apogee was some 1,767 miles below the planned· value, and well outside three-
sigma limits.
130. ESRO-GOES, 20 Apr 77, Response Mode NA, Flight Phase 2.5 and 5: Due possibly
to a short circuit in· the second stage or failure in one of the two explosive bolts
that hold the stage 2/3 clamp band together, the third stage separated
prematurely from the second stage while spinning at only two rpms instead of the
normal 97 rpms. As a result, coning during third-stage bum resulted in a
spacecraft apogee nearly 13,000 miles low, and far outside three-sigma limits.
134. OTS, 13 Sep 77, Response Mode 4, Flight Phase 1: Core vehicle exploded at 57
seconds due to a burn through on the forward end of the #1 Castor IV motor.
155. DJr, 3 Aug 81, Response Mode NA, Flight Phase 2 and 5: Flight was considered a
success, although a 260-pound deficiency in fuel loading led to a premature
propellant-depletion shutdown of the second bum of the second stage and
degradation of final orbit. The inertial velocity at SECO was 240 ft/ sec lower than
planned. Final apogee was some 855 miles too low and well outside three-sigma
limits.
162. WESTAR-V, 9 June 82, Response Mode NA, Flight Phase 1: Booster performance
was low but mission was a success. Apogee and perigee were within three-sigma
limits.
178. GOES-G, 3 May 86, Response Mode 4, Flight Phase 1: An electrical short in a
control circuit in first-stage relay box caused premature main-engine shutdown at
71 seconds. Vehicle then tumbled and was broken up by aerodynamic forces.
RSO sent destruct at approximately 91 seconds.
9/10/96 144 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.