Page:Iran Air Flight 655 investigation.djvu/44

 U (7)  A normal MEF augmenter pre-deployment schedule would have included in addition to the exercises listed in Finding of Facts A.6.a. (4) and (5), two Middle East Force Exercises (MEFEXs) at PMTC, PT Mugu, California, and PMRF Barking Sands, Hawaii. USS VINCENNES did not conduct these exercises because of her early deployment and accelerated transit to Subic Bay, RP. (IO Exhibit 166, Encl 4).

U (8)  USS VINCENNES was provided AEGIS Training Center Briefs on lessons learned on the operation of SPY-1A radar in the Strait of Hormuz/Persian Gulf by AEGIS Training Center, Dahlgren, VA, while inport Subic Bay, RP, on 11 May 1988. (IO Exhibit 166: Encl 8, 9, and 9a).

U (9)  During a four day period (9-12 May), USS VINCENNES conducted the following Middle East Force training in the Subic Bay operating areas: two missile firings (both successful), one war-at-sea strike exercise (against 17 aircraft), CIWS tracking/firing, Silkworm profiles, air intercept controlling, anti-fast patrol boat exercises (night and day), surface gunnery, and surface to air gunnery. (IO Exhibit 166: Encl 17, 18, 19, 20, and 20a).

U (10)  The WASEX conducted on 9 May 1988 included 17 attacking aircraft: 10 USAF (4 Wild Weasel and 6 Pave Tack) and 7 USMC (4 A-6 and 3 F/A-18). A post exercise critique was conducted on 10 May with USAF, USMC, and USS VINCENNES personnel present. USS VINCENNES Large Screen Display (LSD) information was used to reconstruct the events of the exercise. This reconstruction revealed USS VINCENNES had to discriminate threat aircraft from numerous other air contacts in the area including USAF AIR-AIR missile participants and normal air traffic in the vicinity of Clark AFB and Crow Valley, RP. However, Mode IV IFF information was the primary source for identification and discrimination between friendly and belligerent aircraft. (IO Exhibit 166: Encl 17 and 20a).

U (11)  Prior to arrival Subic Bay, RP, USS VINCENNES modified her Battle Organization to conform to the expected “GW” assignment in the Middle East Force. In a meeting with the CO, XO, CSO and OPSO in attendance, the CO decided that CSO and OPS officer would stand watch as "GW", operating from the embarked commander’s console (LSD #2). "GW" (CSO or OPSO) would then monitor the MEFEX communication net and provide the continuous connectivity both for air and surface SITREPS, in the traditional AAWC sense, as well as act as the primary point of contact for the ship over MEFEX net. (Rogers p. 834, p. 809, 818,  p. 788).

U (12)  By modifying the Battle Organization, the Commanding Officer did not intend that the "GW" position would usurp the authority of the TAO, but act in support of the TAO.