09.01.2015 Views

spartans_in_darkness

spartans_in_darkness

spartans_in_darkness

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

'fOP SE6REl'1i'60MIN'fO*1<br />

dur<strong>in</strong>g the critical hours lead<strong>in</strong>g up to the retaliatory<br />

air strikes of 5 August, rema<strong>in</strong>s its most glar<strong>in</strong>g<br />

shortcom<strong>in</strong>g <strong>in</strong> this <strong>in</strong>cident.<br />

(~//~I) We have seen as well the many technical<br />

problems with the supposed "after-action"<br />

translation. This product, upon which the adm<strong>in</strong>istration<br />

based so much of its case, appears to<br />

have been the result of a gross analytic error of<br />

comb<strong>in</strong><strong>in</strong>g two separate messages, each deal<strong>in</strong>g<br />

with separate <strong>in</strong>cidents, <strong>in</strong>to a s<strong>in</strong>gle translation.<br />

There were more problems, such as the actual<br />

translation of the term "comrades" and how it<br />

was rendered <strong>in</strong>to "boats" by NSA. Here, the analytic<br />

problems mix with those discovered about<br />

the available records: the orig<strong>in</strong>al decrypted<br />

Vietnamese text, and an important translation<br />

from San Miguel cannot be located. Consider<strong>in</strong>g<br />

the importance of this translation to the adm<strong>in</strong>istration's<br />

case, the fact that the orig<strong>in</strong>al text cannot<br />

be found (and was not used as earlv as October<br />

1964) is unusual. That these orig<strong>in</strong>al texts and<br />

translation are the only miss<strong>in</strong>g papers <strong>in</strong> the San<br />

Miguel reports allows for suspicion to shade any<br />

further discourses.<br />

(£//£1) What we are confronted with is the<br />

same conundrum that confronted the NSA analysts<br />

at the time. We have discussed earlier that,<br />

for the most part, the NSA personnel <strong>in</strong> the crisis<br />

center who reported the second Gulf of Tonk<strong>in</strong><br />

<strong>in</strong>cident believed that it had occurred. The problem<br />

for them was the SIGINT evidence. The evidence<br />

that supported the contention that an<br />

attack had occurred was scarce and nowhere as<br />

strong as would have been wanted. The overwhelm<strong>in</strong>g<br />

body of reports, if used, would have<br />

told the story that no attack had happened. So a<br />

conscious effort ensued to demonstrate that the<br />

attack occurred.<br />

(£//£I) The exact "how" and "why" for this<br />

effort to provide only the SIGINT that supported<br />

the claim of an attack rema<strong>in</strong> unknown. There are<br />

no "smok<strong>in</strong>g gun" memoranda or notes buried <strong>in</strong><br />

the files that outl<strong>in</strong>e any plan or state a justification.<br />

Instead, the paper record speaks for itself on<br />

what happened: what few product (six) were<br />

actually used, and how 90 percent of them were<br />

kept out of the chronology; how contradictory<br />

SIGINT evidence was answered both with speculation<br />

and fragments lifted from context; how the<br />

complete lack of Vietnamese C31 was not<br />

addressed; and, f<strong>in</strong>ally, how critical orig<strong>in</strong>al<br />

Vietnamese text and subsequent product were no<br />

longer available. From this evidence, one can easily<br />

deduce the deliberate nature of these actions.<br />

And this observation makes sense, for there was a<br />

purpose to them: This was an active effort to<br />

make SIGINT fit the claim of what happened dur<strong>in</strong>g<br />

the even<strong>in</strong>g of 4 August <strong>in</strong> the Gulf of Tonk<strong>in</strong>.<br />

(S//£I) The question why the NSA personnel<br />

handled the product the way they did will probably<br />

never be answered. The notion that they were<br />

under "pressure" to deliver the story that the<br />

adm<strong>in</strong>istration wanted simply cannot be supported.<br />

Ifthe participants are to be believed, and they<br />

were adamant <strong>in</strong> assert<strong>in</strong>g this, they did not bend<br />

to the desires of adm<strong>in</strong>istration officials. Also,<br />

such "environmental" factors as overworked crisis<br />

center personnel and lack of experienced l<strong>in</strong>guists<br />

are, for the most part, not relevant when<br />

consider<strong>in</strong>g the entire period of the crisis and<br />

follow-up. As we have seen, the efforts to ensure<br />

that the only SIGINT publicized would be that<br />

which supported the contention that an attack<br />

had occurred cont<strong>in</strong>ued long after the crisis had<br />

passed. While the product <strong>in</strong>itially issued on the 4<br />

August <strong>in</strong>cident may be contentious, th<strong>in</strong>, and<br />

mistaken, what was issued <strong>in</strong> the Gulf of Tonk<strong>in</strong><br />

summaries beg<strong>in</strong>n<strong>in</strong>g late on 4 August was deliberately<br />

skewed to support the notion that there<br />

had been an attack. What was placed <strong>in</strong> the official<br />

chronology was even more selective. That the<br />

NSA personnel believed that the attack happened<br />

and, as a result, rationalized the contradictory<br />

evidence away is probably all that is necessary to<br />

know <strong>in</strong> order to understand what was done.<br />

They walked alone <strong>in</strong> their counsels.<br />

'fOP SEeRE1'N60Mltml*1 Page 223

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!