TAB C – Chemical Evidence – Scud Incidents In KTO

Table 7. Chemical Warfare Agent Evidence

Date/ Time (1991)

Area

Reports on Test Results or Indications

(MULTIPLE PAGE TABLE)

Jan 20 9:43 PM

Dhahran

  • Numerous M256 kit, M8A1 alarms, and Chemical Agent Monitor (CAM) tests/checks produced negative results.[185]

  • Impact was assessed as high explosive.[186]

Jan 21 12:29 AM

Dhahran

  • Fox nuclear-biological-chemical reconnaissance vehicles detected no chemical contamination.[187]

Jan 21 12:42 AM

Riyadh

  • At least two Scuds exploded on impact. See Table 4 and Selected Incident detail.

  • No confirmation of nuclear-biological-chemical contamination. All clear reported.[188]

Jan 21 10:18 PM

Dhahran

  • Struck in water – no damage/casualties reported.[189]

Jan 22 3:41 AM

Riyadh

  • No casualties or damage. See Table 4.

Jan 22 7:10 AM

Dhahran

  • Numerous negative CAM results. However, one CAM produced one-bar (very low concentration) for G nerve agent, but later checks with M256 kit proved negative.[190]

Jan 23 10:54 PM

Dhahran

  • An M8A1 alarm did not alert.[191]

Jan 23 10:54 PM

Riyadh

  • United States/Saudi police desk reported no nuclear-biological-chemical alarms. NBC reported all clear. Then Saudis reported mustard reading in area, but Explosive Ordnance Disposal team checked and found nothing.[192]
  • French investigated one suspected impact area but found no crater or contamination.[193]

Jan 25 10:23 PM

Riyadh

  • One warhead explosion demolished Saudi building.
  • NBC personnel sent to roof of Ministry of Defense and Aviation building (location of United States Central Command Headquarters) after impact about one mile away – reported all clear.[194]
  • Received all clear from Explosive Ordnance Disposal at strike site.[195]

Jan 26 3:28 AM

Dhahran

  • Reporting contains no indications of chemical agent delivery or casualties. See Table 3.

Jan 26 10:46 PM

Riyadh

  • Reporting contains no indications of chemical agent delivery or casualties. See Table 4.

Jan 28 10:55 PM

Riyadh

  • Reporting contains no indications of chemical agent delivery or casualties. See Table 4.

Feb 3 12:41 AM

Riyadh

  • Warhead detonated damaging several buildings. See Table 4 and Significant Incidents.

Feb 8 1:54 AM

Riyadh

  • Warhead exploded (indicating high-explosive warhead). See Table 4.

Feb 11 10:20 PM

Riyadh

  • Warhead exploded. See table 4.
  • All clear for NBC contamination reported.[196]

Feb 14 11:45 AM

Hafir Al Batin

  • No casualties or chemical munitions use reported.[197] See also Table 5 and Significant Incidents.
  • Ground and aerial reconnaissance performed and no contamination found.[198]

Feb 16 2:01 AM

Al Jubayl

  • Warhead recovered and confirmed as high explosive. See Table 3.

Feb 21 5:06 PM

KKMC

  • No chemical agent exposure reported. See Table 5 and Significant Incidents.

Feb 22 2:31 AM

Bahrain

  • One of three Scuds hit water. No report of chemical warheads in operational reporting.

Feb 23 4:59 AM

Dhahran

  • Reporting contains no indications of chemical agent delivery or casualties. See Table 3.

Feb 24 4:32 AM

Riyadh

  • No explosion, no injuries. See Table 4.

Feb 24 12:17 PM

KKMC

  • No explosion. See Table 5.

Feb 24 9:23 PM

Riyadh

  • All clear for chemicals called. Dud warhead confirmed as high explosive by Explosive Ordnance Disposal.[199]

Feb 25 8:32 PM

Dhahran

  • High explosive warhead hit barracks with extensive damage and casualties. No chemical casualties.[200]

Feb 26 1:26 AM

Qatar

  • Impacted in water 40 miles off Qatar. See Table 3.


| First Page | Prev Page | Next Page |