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…
388. 5003C AC-21 (OAO-B), 30 Nov 70, Response Mode 4, Flight Phase 2: Since the
nose fairing failed to separate, Centaur did not have enough energy to make orbit.
Payload impacted in Africa.
392. 5405C AC-24 (Mariner 8 Mars), 8 May 71, Response Mode 4T, Flight Phase 3:
Mission requirements were not met. The Atlas boost phase was normal. Shortly
after Centaur main-engine start, pitch stabilization was lost due to failure. of the
rate gyro or an electrical failure in the pitch channel of the flight control system.
The vehicle began an accelerated nose-down tumbling motion that subsequently
resulted in early and erratic main-engine shutdown due to propellant starvation.
397. SLV-3A (Agena), 4 Dec 71, Response Mode 4, Flight Phase 1: Sustainer engine
turbine damage during engine start resulted in hot gas leaks and eventual failure
of thrust-section hardware. Vehicle broke up at 87 seconds.
419. 5015D AC-33 (Intelsat IV F-6), 20 Feb 75, Response Mode 4T, Flight Phase 2: The
Atlas booster-section electrical disconnect failed at booster staging. The harness
was pulled apart, so flight-control avionics was unable to maintain vehicle
stability: Missile appeared normal until the IP stopped at 200 seconds.
Precautionary destruct was sent at 414 seconds.
420. 71F (AFSC), 12 Apr 75: Response Mode 4, Flight Phase 1: Although an abnormal
overpressure occurred at the base of the missile 620 msec before liftoff, the vehicle
appeared normal until about 45 seconds when sustainer manifold and fuel-pump
pressures began dropping. By 61 seconds, both the sustainer and vernier engines
had shut down. Booster engines continued thrusting until about 123 seconds
when the IIP stopped moving and radar operator reported multiple pieces. The
breakup apparently resulted from an external explosion in the flame bucket that
damaged the thrust section. Destruct was sent at 303 seconds when missile
elevation dropped to 5°.
432. 5701D AC-43 (Intelsat IVA F-5), 29 Sep 77, Response Mode 4T, Flight Phase 1: A
leak in the booster hot-gas generator at 2.3 seconds resulted in a fire in the thrust
section at 36.5 seconds. The vehicle went into a violent maneuver at 54.9 seconds,
failing the structure. The Atlas exploded at 55.8 seconds, leaving the Centaur
intact. The Centaur was destroyed by the RSO at 61.7 seconds.
457. 19F (NOAA-B), 29 May 80: Response Mode NA, Flight Phase 1: Failure of
turbopump seal allowed fuel to enter the gear box resulting in 21 % low thrust by
the Bl booster engine. The payload was inserted into- an abnormal orbit and the
mission was lost.
460. 68E, 8 Dec 80: Response Mode 5, Flight Phase 1: Flight appeared normal until
102.7 seconds when the lube oil pressure on the B2 booster engine suddenly
dropped. At 120.1 seconds, the engine shut down, followed 385 msec later by
guidance shutdown of the Bl engine. The asymmetric thrust during shutdown
9/10/96 130 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.