1990 Gulf War

MIM-104 Patriot in the 1990 Gulf War

U.S.-led coalition forces fielded MIM-104 Patriot batteries in Saudi Arabia and Israel during the 1990 Gulf War to defend against Iraqi Scud and Al-Hussein ballistic missiles, making Patriot a prominent but heavily scrutinized tactical ballistic-missile defense system.

Evidence Map

ClaimSources
Patriot battalions were deployed to Saudi Arabia and Israel during Operation Desert Shield/Desert Storm to defend against Iraqi Scud missiles.

Sources: GAO Dhahran Software Failure, CSIS Patriot

The Army rapidly modified Patriot fire units and accelerated PAC-2 missile supply for the faster Iraqi Al-Hussein threat.

Sources: GAO Patriot Performance Not Supported

A Patriot battery at Dhahran failed to intercept an incoming Scud on February 25, 1991 because of a software-related tracking problem after extended operation.

Sources: GAO Dhahran Software Failure

Postwar GAO reviews found that the Army's initial success assessments were not supported by the cited records and that conclusive performance data did not exist.

Sources: GAO Patriot Performance Not Supported, GAO Data Does Not Exist

CSIS describes Gulf War Patriot performance as inconclusive and notes that the PAC-2 warhead sometimes failed to fully destroy incoming missiles.

Sources: CSIS Patriot

Timeline

MIM-104 Patriot In 1990 Gulf War

  1. Patriot modified and deployed for the Scud threat

    GAO reported that the Army and prime contractor rapidly modified Patriot software so deployed Gulf units could engage Iraq's faster extended-range Scud/Al-Hussein missiles.

    Sources: GAO Patriot Performance Not Supported

  2. First Scud engagements and PAC-2 supply

    By the first Scud engagement in January 1991, GAO reported that PAC-2 missiles had been supplied to all Patriot units, with about 600 PAC-2 missiles in the Gulf region by the end of the month.

    Sources: GAO Patriot Performance Not Supported

  3. Dhahran Patriot battery fails to intercept incoming Scud

    A Patriot battery at Dhahran failed to track and intercept an Iraqi Scud, which struck an Army barracks and killed 28 U.S. soldiers.

    Sources: GAO Dhahran Software Failure

  4. GAO questions the 70 percent success assessment

    GAO testified that the Patriot Project Manager's assessment that Patriot was successful against 70 percent of Iraqi Scuds was not supported by the two principal documents cited.

    Sources: GAO Patriot Performance Not Supported

  5. GAO says conclusive performance data does not exist

    GAO reported that the Army did not collect performance data during Desert Storm sufficient to conclusively determine how many targets Patriot killed or failed to kill.

    Sources: GAO Data Does Not Exist

Documented Use

Direct proof of use

The MIM-104 Patriot is directly documented in 1990 Gulf War service through U.S. Government Accountability Office reviews of Operation Desert Storm. GAO reported that Patriot battalions were deployed to Saudi Arabia and Israel after Operation Desert Shield began and were placed to defend key assets, military personnel, and citizens against Iraqi Scud missiles.

GAO's April 1992 testimony described Patriot as a surface-to-air guided missile system that the Army modified and supplied with PAC-2 missiles for the Gulf War's Iraqi Scud threat. By the first Scud engagement in January 1991, the Army had supplied PAC-2 missiles to all units, and by the end of that month about 600 PAC-2 missiles were in the Gulf region.

CSIS Missile Threat summarizes the same conflict role: during the Gulf War, Patriot was used in an anti-aircraft and ballistic-missile defense role against Iraqi Scud and Al-Hussein missiles fired at Israel and Saudi Arabia.

Sources: GAO Dhahran Software Failure, GAO Patriot Performance Not Supported, CSIS Patriot

Timeline

Patriot's Gulf War role changed quickly after Iraq's August 1990 invasion of Kuwait. GAO reported that, at the time of the invasion, Patriot had no capability to engage Iraq's extended-range Al-Hussein version of the Scud. Within less than a week, the Army and its prime contractor incorporated software modifications so Patriot fire units could engage the faster missiles, and those changes went into the first units deployed to the Gulf in August 1990.

The operational record then moved from emergency adaptation to combat engagement. GAO reported that after Patriot began engaging Scuds, two additional software changes were made to increase intercept altitude and reduce false-target detection. GAO also recorded that the first Scud engagement came in January 1991, after PAC-2 missiles had been supplied to all units.

The best documented individual incident was the failed Dhahran engagement on February 25, 1991. GAO found that a Patriot battery at Dhahran, Saudi Arabia failed to track and intercept an incoming Scud because of a software problem in the weapon control computer; the Scud struck an Army barracks and killed 28 U.S. soldiers.

Sources: GAO Patriot Performance Not Supported, GAO Dhahran Software Failure

Operational role

In the Gulf War, Patriot was fielded as a defensive system for fixed and high-value areas rather than as a maneuver weapon. GAO described Patriot battalions in Saudi Arabia and Israel defending key assets, military personnel, and civilians from Iraqi Scud missiles; CSIS describes Patriot's conflict role as attempts to engage Iraqi Scud and Al-Hussein missiles fired at Israel and Saudi Arabia.

The system's wartime configuration centered on PAC-2 adaptation. GAO reported that PAC-1 software had given Patriot a limited anti-tactical-missile capability and that PAC-2 added a faster fuze and larger-fragment warhead intended to engage the front of incoming missiles, where the warhead was located.

Postwar evidence did not support simple claims of a near-perfect intercept record. GAO's April 1992 testimony found that the Patriot Project Manager's assessment of 70 percent success against Iraqi Scuds was not supported by the two principal source documents cited. GAO's September 1992 report went further, concluding that the data needed to conclusively demonstrate how well Patriot performed in Desert Storm did not exist.

Sources: GAO Dhahran Software Failure, GAO Patriot Performance Not Supported, GAO Data Does Not Exist, CSIS Patriot

Dhahran failure and assessment limits

GAO's Dhahran report attributed the February 25, 1991 failure to a precision problem in Patriot's weapon control computer. Alpha Battery had been operating for more than 100 consecutive hours, and the resulting time-calculation inaccuracy caused the system's range gate to shift so far that it could not track the incoming Scud.

The same report stated that modified software to compensate for the inaccurate time calculation arrived in Dhahran on February 26, the day after the Scud incident. GAO also noted that Patriot had never before been used to defend against Scud missiles and was not expected to operate continuously for long periods.

The broader performance record remained contested because the Army did not collect the kind of range-test data needed for conclusive evaluation. GAO reported that only about 9 percent of Patriot engagements had the strongest evidence for a warhead kill, while other assessments depended on limited radar data, delayed site visits, photographs, interviews, and incomplete unit records.

Sources: GAO Dhahran Software Failure, GAO Data Does Not Exist, GAO Patriot Performance Not Supported

Sources