Jump to content

Page:Iran Air Flight 655 investigation.djvu/64

From Wikisource
This page has been validated.

SECRET NOFORN

data showed only Mode III-6760 at this time. (IO Exhibit 91,  , p.626)

U
(c) (S) Not all RCI indications are displayed in an operator's CRO because RCI data is not always correlated with a track in the system. IFF data in C&D is always correlated with a track number. (AF Exhibit Enclosure 17).

U
(d) (S) Multiple CIC personnel recalled hearing F-14 report on internal net 15 or 16, or recall it being said aloud. ( , p. 812;  , p. 677;  , p. 537;  , p. 637;  , p. 560;  , p. 543;  , p. 570;  , p. 593;  , p. 650).

U
(e) (S)   (CSC) never saw Mode II, but   (AIC) saw Mode II-1100 and Mode III-6675 on his CRO.   (AAWC) also saw Mode II-1100. USS VINCENNES's system still held no IFF Mode II and held Mode III-6760 for TN 4131. ( , p.537;  , p. 706;  , p. 727) (IO Exhibit 91).

U
(f) (S)   (TIC) reported rechallenging TN 4131 after Mode II report but only got a Mode III ( , p. 678).

U
(g) (S)  (WCC2-SIDES) noted TN 4131 climb to 5000 ft. (IO Exhibit 57,  , p. 236}.

U
(h) (S) TN 4131. went out of SPY-1A low elevation. SPY-1 data then became altitude source at operator consoles and on Link 11. (IO Exhibit 91).

U
(i) (S) TN 4131 was at range of 34 NM, BRG 025, ALT 6160, and a SPD 334. (IO Exhibit 91).

U
(j) (S)   ("GW") reported an inbound Iranian F-14 to "GB on MEF Execution net (BRG 025/RNG 32NM). He also reported on the net that he had warned TN 4131 and that the challenge was ignored. (IO Exhibit 203).

U
(k) (S)   ("GW") recalled making a MEF Execution net report when TN 4131 was at 32 NM and recalled an earlier altitude of 9800 ft when TN 4131 was between 38-40 NM. (  pp. 813, 814).

U
(l) (S) USS VINCENNES ordered to take tactical control of USS SIDES by "GS". (IO Exhibit 203).

U
(m) (S) TN 4131 reported as "Astro" (F-14) over AAW C&R/DSA net by TIC. (IO Exhibit 203).

U
(n) (S)  (OSDA) tagged TN 4131 as F-14 on the LSD. ( , p. 781).

48

SECRET NOFORN