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.

lOP SESRElHSOMINlHX1<br />

from Fort Meade was a series of summary reports<br />

issued between Sand 7 August. It is these reports<br />

which make up first official NSA judgment on<br />

what happened. Because of this, the summaries<br />

deserve a close look, s<strong>in</strong>ce they establish the tone<br />

and form for the later chronology, which became,<br />

<strong>in</strong> a way, the f<strong>in</strong>al NSA statement on what had<br />

happened.<br />

(TS//SI) NSA issued five summary and situation<br />

reports after the <strong>in</strong>cident, beg<strong>in</strong>n<strong>in</strong>g early on<br />

S August. Of the five, numbers "Rat" through<br />

"ROS," the pert<strong>in</strong>ent ones are the first three, especially<br />

the first and third. These three reports<br />

explicitly state that the 4 August attack occurred.<br />

Report "ROl" notes that the reports from the<br />

destroyer that it had sunk two torpedo boats were<br />

later "confirmed by a DRV message which stated<br />

'that we had sacrificed two ships and the rest are<br />

okay'." 166 The statement was a direct quote from<br />

the suspect NSA translation. It differed from the<br />

Vietnamese losses reported by the U.S. ships.<br />

NSA received all messages from the Desoto patrol<br />

via the JCS. All through the afternoon of 4<br />

August, the destroyers reported at first that three<br />

boats had been sunk, then later changed it to one<br />

sunk and one, possibly two, damaged.l'" The second<br />

post-<strong>in</strong>cident report, known as "Gulf of<br />

Tonk<strong>in</strong> SIGINT Situation Report No.1," <strong>in</strong>cluded<br />

the statement "follow<strong>in</strong>g the 4 August attack."<br />

(TS//SI) It was the third report that was the<br />

most open <strong>in</strong> support<strong>in</strong>g the idea of the second<br />

attack. It was stated <strong>in</strong> the lead sentence of the<br />

report that "This report is a summary of those<br />

DRV naval communications dur<strong>in</strong>g the period I­<br />

S August which demonstrate irrefutably that DRV<br />

naval boats did, <strong>in</strong> fact, engage <strong>in</strong> preplanned<br />

combat aga<strong>in</strong>st U.S. destroyers patroll<strong>in</strong>g <strong>in</strong><br />

<strong>in</strong>ternational waters." 168<br />

(TS//SI) However, the confident tone of the<br />

third report is belied by its th<strong>in</strong> layer of evidence.<br />

And this problem was noticed by some of its<br />

recipients. Late on the afternoon of 6 August, a<br />

DIA representative queried NSA if additional<br />

SIGINT was available from the 4 August <strong>in</strong>cident.<br />

He reported that Secretary McNamara was not<br />

satisfied with the contents of this third summary<br />

report, "that it was <strong>in</strong>sufficient for his purposes."<br />

In review<strong>in</strong>g the SIGINT from the <strong>in</strong>cident, it was<br />

discovered that there was a large gap with no<br />

<strong>in</strong>tercept - specifically, the time lead<strong>in</strong>g up to the<br />

supposed attack. Based on this discrepancy,<br />

urgent messages were sent to the field sites<br />

request<strong>in</strong>g all <strong>in</strong>tercept.l'" And, as we have seen,<br />

the field sites had noth<strong>in</strong>g else to add.<br />

(TS//SI) There are problems with the way this<br />

series of reports portrays the <strong>in</strong>formation <strong>in</strong><br />

them. For example, the first report mentions the<br />

salvage operations of the two damaged DRV torpedo<br />

boats which had been discussed earlier.<br />

However, unlike what we discovered, the summary<br />

does not go on to report that these operations<br />

cont<strong>in</strong>ued <strong>in</strong>to the time of the attack as reported<br />

by the mar<strong>in</strong>es at Phu Bai. The authors of the<br />

third report tried to address this with the speculation<br />

that the attack<strong>in</strong>g boats might have come<br />

from Quang Khe or some other base <strong>in</strong> the DRV<br />

Southern Command.'" But this has already been<br />

shown to be wrong s<strong>in</strong>ce the distance traveled for<br />

the boats to have attacked from the east could not<br />

have been accomplished because of the limitations<br />

of the boats' speed.<br />

(TS//SI) Perhaps the most serious problem,<br />

though, is the lack of any citation of source<br />

reports which made up the summaries. This is a<br />

critical po<strong>in</strong>t, s<strong>in</strong>ce the <strong>in</strong>formation referred to <strong>in</strong><br />

the summaries is com<strong>in</strong>g from already published,<br />

serialized NSA and field site reports and translations.<br />

The very lack of notes is odd s<strong>in</strong>ce this type<br />

of summary report<strong>in</strong>g required that source notes<br />

be <strong>in</strong>cluded. It seems that if the Agency was<br />

attempt<strong>in</strong>g to build a case demonstrat<strong>in</strong>g that an<br />

attack had occurred, then the source reports and<br />

translations which substantiated the position<br />

would have been <strong>in</strong>cluded. However, this was not<br />

the case. In fact, there were cases <strong>in</strong> which <strong>in</strong>formation<br />

used <strong>in</strong> the summaries as evidence, was,<br />

<strong>in</strong> fact, not related at all, or impossible to verify.<br />

lOP SESRElIfSOMIPHN)E1 Page 215

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

Saved successfully!

Ooh no, something went wrong!