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…
caused yaw and roll rates that the flight control system could not correct. As a
result, attitude control was lost and the thrusting sustainer pivoted the missile to a
retrofire attitude before the vehicle could be stabilized. After the booster package
was jettisoned, the missile was stabilized and decelerating in the retrofire mode
by 148 seconds. The sustainer continued thrusting in this attitude until 282.9
seconds when reentry heating apparently caused sustainer shutdown and vehicle
breakup.
464. 5039D AC-59 (FLTSATCOM), 6 Aug 81, Response Mode NA, Flight Phase 1 and 5:
The basic mission was accomplished although three increasingly severe shock
events were recorded at 56.2, 70,7, and 120.8 seconds. The structural damage
sustained by the spacecraft severely limited on-orbit operations.
466. 76E (NAVSTAR VII), 18 Dec 81: Response Mode 2, Flight Phase 1: Shortly after
clearing the launch tower at an altitude of about two tower heights, the thrust
performance of the Bl engine began to decay. The engine was shut down
completely by 7.4 seconds. The unbalanced thrust caused the missile to pitch over
to the right, and travel horizontally for about one second. It then pitched toward
the ground. A small explosion .occurred about one-third of the way down,
followed by a larger explosion when the missile impacted the ground directly
behind the launch pad about 19 seconds after liftoff. Cause of the engine failure
was plugging of the gas-generator fuel-cooling parts that resulted in a gas-
generator bum-through.
477. 5042G AC-62 (Intelsat V), 9 Jun 84, Response Mode 4T, Flight Phase 4:
Performance was normal until an abnormal shock event occurred at
Atlas/Centaur separation. Subsequent data indicated that a Centaur oxygen tank
leak resulted in a loss of 1483 pounds of LOX during Centaur first burn. The leak
resulted in the LOX tank pressure falling below the LH2 tank pressure, which led
to collapse of the intermediate bulkhead during the coast phase. Bulkhead
collapse caused unexpected tumbling forces during coast. The Centaur engines
restarted after coast, but burned for only 6 or 7 secorids of a planned 90-second
bum.
489. 5048G AC-67 (FLTSATCOM F-6), 26 Mar 87, Response Mode 4T, Flight Phase 1:
Vehicle performance was normal till 48.4 seconds, when the vehicle was struck by
lightning. As a result, the guidance computer commanded a hard right tum
which caused vehicle breakup due to inertial and aerodynamic loads. RSO sent
destruct at 70.7 seconds.
498. 5050 AC-70 (BS-3H COMSAT), 18 Apr 91, Response Mode 4T, Flight Phase 3:
Atlas performance was normal. Although both Centaur main engines began the
start sequence properly, the C-1 turbo-machinery decelerated and stopped,
leaving the C-1 engine thrust at the ignition level. Air entering through the stuck-
open check valve liquefied and froze in the LH2 pump and gear box of the C-1
9/10/96 131 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.