National Technical Reports Library - NTRL

National Technical Reports Library

The National Technical Information Service acquires, indexes, abstracts, and archives the largest collection of U.S. government-sponsored technical reports in existence. The NTRL offers online, free and open access to these authenticated government technical reports. Technical reports and documents in its repository may be available online for free either from the issuing federal agency, the U.S. Government Publishing Office’s Federal Digital System website, or through search engines.




Details
Actions:
Download PDFDownload XML
Download

PATRIOT MISSILE DEFENSE: Software Problem Led to System Failure at Dhahran, Saudi Arabia.


ADA344865

Publication Date 1992
Page Count 18
Abstract On February 25, 1991, a Patriot missile defense system operating at Dhahran, Saudi Arabia, during Operation Desert Storm failed to track and intercept an incoming Scud. This Scud subsequently hit an Army barracks, killing 28 Americans. This report responds to Rep. Wolpe' request that the General Accounting Office(GAO) review the facts associated with this incident and determine if a computer software problem was involved. If so, the Reprentative asked GAO to provide information on what the specific software problem was, and what has been done to correct it. Appendix I details our objectives, scope, and methodology. The Patriot battery at Dhahran failed to track and intercept the Scud missile because of a software problem in the system's weapons control computer. This problem led to an inaccurate tracking calculation that became worse the longer the system operated. At the time of the incident, the battery had been operating continuously for over 100 hours. By then, the inaccuracy was serious enough to cause the system to look in the wrong place for the incoming Scud. The Patriot had never before been used to defend against Scud missiles nor was it expected to operate continuously for long periods of time. Two weeks before the incident, Army officials received Israeli data indicating some loss in accuracy after the system had been running for 8 consecutive hours. Consequently, Army officials modified the software to improve the system's accuracy. However, the modified software did not reach Dhahran until February 26,1991-the day after the Scud incident.
Keywords
  • Weapon system effectiveness
  • Surface to air missiles
  • Guided missile tracking systems
  • Ballistic missile intercept systems
  • Computer program reliability
  • Failure(Electronics)
  • Computer programs
  • Military operations
  • Israel
  • Iraq
  • Control systems
  • Computations
  • Defense systems
  • Attack
  • Army facilities
  • Failure
  • Accuracy
  • Long range(Time)
  • Weapon control
  • Saudi arabia
  • Barracks
  • Gao reports
  • Bmdo collection
  • Patriot missiles
  • Desert storm operation
Source Agency
  • Non Paid ADAS
Corporate Authors General Accounting Office, Washington, DC. Information Management and Technology Div.
Supplemental Notes Report to the Chairman, Subcommittee on Investigations and Oversight, Committee on Science, Space, and Technology, House of Representatives.
Document Type Technical Report
NTIS Issue Number 199817
PATRIOT MISSILE DEFENSE: Software Problem Led to System Failure at Dhahran, Saudi Arabia.
PATRIOT MISSILE DEFENSE: Software Problem Led to System Failure at Dhahran, Saudi Arabia.
ADA344865

  • Weapon system effectiveness
  • Surface to air missiles
  • Guided missile tracking systems
  • Ballistic missile intercept systems
  • Computer program reliability
  • Failure(Electronics)
  • Computer programs
  • Military operations
  • Israel
  • Iraq
  • Control systems
  • Computations
  • Defense systems
  • Attack
  • Army facilities
  • Failure
  • Accuracy
  • Long range(Time)
  • Weapon control
  • Saudi arabia
  • Barracks
  • Gao reports
  • Bmdo collection
  • Patriot missiles
  • Desert storm operation
  • Non Paid ADAS
Loading