09.01.2015 Views

spartans_in_darkness

spartans_in_darkness

spartans_in_darkness

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

l'QP 5lIiSRIil'lISQMIPll'HX1<br />

(8//Sn On 2 August, the SIGINT system performed<br />

admirably when it provided sufficient<br />

warn<strong>in</strong>g to the Maddox to allow it to defend itself<br />

aga<strong>in</strong>st the attack by the three DRV torpedo<br />

boats. At the same time, the American cryptologists<br />

were able to observe the DRV naval C3I<br />

system <strong>in</strong> action. From this they should have<br />

developed a profile from which further timely<br />

warn<strong>in</strong>gs could be deduced. Dur<strong>in</strong>g 3 August,<br />

both sides ma<strong>in</strong>ta<strong>in</strong>ed a distant watchfulness,<br />

though tensions rema<strong>in</strong>ed high - high enough,<br />

perhaps, for the field site at Phu Bai to confuse<br />

salvage operations around the island of Hon Me<br />

for a pre-attack concentration of forces.<br />

G~//SI) The 4 August <strong>in</strong>cident began <strong>in</strong> the<br />

early afternoon due to a significant error <strong>in</strong> analysis<br />

by the Mar<strong>in</strong>e cont<strong>in</strong>gent at Phu Bai. This mistake<br />

set <strong>in</strong> the m<strong>in</strong>ds of the crew of the two<br />

destroyers the idea that they shortly would be<br />

attacked. This error of <strong>in</strong>terpretation by the<br />

Mar<strong>in</strong>e unit at Phu Bai was a mistake, as we have<br />

seen, which was not committed by the navy site at<br />

San Miguel. Nor was the Critic transmitted by<br />

Phu Bai questioned or corrected at NSA. This may<br />

have been <strong>in</strong> l<strong>in</strong>e with an unspoken policy of not<br />

second-guess<strong>in</strong>g field sites s<strong>in</strong>ce they were "closer"<br />

to the action. However, under Critic procedures,<br />

Phu Bai had to supply the technical <strong>in</strong>formation<br />

upon which it based its alert. When the<br />

discrepancy between what the <strong>in</strong>tercept actually<br />

said and what the Mar<strong>in</strong>e detachment reported<br />

became known, NSA should have cautioned the<br />

recipients of the Critic. However, this did not<br />

happen.<br />

(8//S1) Three hours later, at almost the same<br />

moment that the American destroyers opened<br />

fire on the approach<strong>in</strong>g radar return, Phu Bai<br />

issued another report which stated that the specific<br />

boats, which had been identified as be<strong>in</strong>g<br />

readied for an attack, <strong>in</strong> reality, were to be towed<br />

to Haiphong for repairs. This salvage operation<br />

would be the subject of several more reports dur<strong>in</strong>g<br />

the rest of the even<strong>in</strong>g of 4 August. S<strong>in</strong>ce no<br />

other boats were referenced <strong>in</strong> the orig<strong>in</strong>al<br />

"attack" message, the cryptologists at NSA found<br />

themselves without any SIGINT evidence support<strong>in</strong>g<br />

the reports of an ambush. The Phu Bai<br />

reports had effectively cancelled out the orig<strong>in</strong>al<br />

Critic. However, the response by NSA was to<br />

counter the SIGINT evidence with an unfounded<br />

speculation that the boats the Desoto patrol<br />

thought were attack<strong>in</strong>g it came from Quang Khe.<br />

And it has been demonstrated how impossible<br />

this scenario was.<br />

(S//~I) It also has been established that none<br />

of the C3I associated with DRV naval attack of 2<br />

August was present on 4 August. Aside from sporadic<br />

North Vietnamese coastal track<strong>in</strong>g, which<br />

ended hours before the two destroyers turned<br />

east, there was no <strong>in</strong>tercept to suggest the North<br />

Vietnamese had anyth<strong>in</strong>g more than the usual<br />

<strong>in</strong>terest <strong>in</strong> the two ships. Nor, for that matter, was<br />

there any <strong>in</strong>tercept of any DRV naval communications<br />

which suggested <strong>in</strong> any manner that an<br />

attack was planned, much less that one actually<br />

was occurr<strong>in</strong>g. In fact, Hanoi seemed more <strong>in</strong>terested<br />

<strong>in</strong> warn<strong>in</strong>g its boats of the patrol's presence,<br />

view<strong>in</strong>g the Americans as a threat to its navy. For<br />

the cryptologic community, this lack of any attack<br />

C3I is one of the most critical po<strong>in</strong>ts of the Gulf of<br />

Tonk<strong>in</strong> crisis. Yet, NSA never addressed the issue<br />

<strong>in</strong> any reports or activity summaries it published<br />

concern<strong>in</strong>g the 4 August <strong>in</strong>cident.<br />

(S//SI) Instead, NSA would issue summaries<br />

with scattered tidbits of contentious and unreferenced<br />

<strong>in</strong>tercept ("Khoai had met the enemy" and<br />

the purported aerial track<strong>in</strong>g) to support the<br />

notion that an attack had been planned and that<br />

it had been carried out. The extensive amount of<br />

SIGINT evidence that contradicted both the <strong>in</strong>itial<br />

attack order and the notion that any North<br />

Vietnamese boats were <strong>in</strong>volved <strong>in</strong> any "military<br />

operations," other than salvage of the two damaged<br />

torpedo boats, was either misrepresented or<br />

excluded from all NSA produced post-<strong>in</strong>cident<br />

summaries, reports, or chronologies. NSA's failure<br />

to deal with both issues, the lack of any attack<br />

C3I and the contradictory SIGINT, especially<br />

Page 222<br />

lOP SE6RElH60MIPH!a

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

Saved successfully!

Ooh no, something went wrong!