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 SE6REl"ff60MIPHff)(1<br />

pleted, T-146 was ordered to Bay Chay, a po<strong>in</strong>t<br />

near Haiphong harbor.!" Shortly afterwards, T­<br />

142 <strong>in</strong>formed Haiphong that the very busy T-146<br />

was now to tow T-336 back, but s<strong>in</strong>ce the latter<br />

boat was short of fuel, the T-333, which was short<br />

of oil but under tow from the Bach Dang, could<br />

transfer one to five tons of its fuel to its sister vesse1.<br />

112 At 1830Z on 4 August (0l30G on 5 August),<br />

the navy monitor<strong>in</strong>g site at San Miguel <strong>in</strong>tercepted<br />

T-142's report to Haiphong that T-146 had<br />

completed its preparations for the two torpedo<br />

boats by OlOOG 5 August (1800Z 4 August). 113 So,<br />

<strong>in</strong> reality, none of the boats named <strong>in</strong> the orig<strong>in</strong>al<br />

attack Critic <strong>in</strong> fact participated <strong>in</strong> anyth<strong>in</strong>g but<br />

salvage efforts.<br />

~Remember, Capta<strong>in</strong> Herrick did not know<br />

that the orig<strong>in</strong>al Critic was really an <strong>in</strong>terpretation,<br />

and that there was no explicit reference to an<br />

attack on his ships. He accepted the Critic's contents<br />

as <strong>in</strong>tercept of actual Vietnamese plans to<br />

attack his ships when he <strong>in</strong>formed the<br />

Ticonderoga task group commander of his decision<br />

to leave the area. He added his own twist to<br />

the report to <strong>in</strong>clude specifically the unsupported<br />

amplification mention<strong>in</strong>g the <strong>in</strong>volvement of<br />

North Vietnamese P-4 torpedo boats when only<br />

one was mentioned as a potential participant <strong>in</strong><br />

the unidentified operations, and then only if it<br />

could be refueled.l'"<br />

(S//SO The possibility that, even if the <strong>in</strong>terpretation<br />

was <strong>in</strong>correct, the Mar<strong>in</strong>e Critic was<br />

justified <strong>in</strong> light of the events from two days earlier,<br />

does not stand up when we consider that<br />

another site, the navy <strong>in</strong>tercept station at San<br />

Miguel, Philipp<strong>in</strong>es, had translated the same<br />

"operations order," but reported it <strong>in</strong> a much different<br />

fashion. The navy translated the same<br />

<strong>in</strong>tercept and then reported it at a Priority precedence,<br />

two levels below a Critic (or one level<br />

above Rout<strong>in</strong>e). The navy analysts titled the<br />

report "REPLENISHMENT OF DRV NAVAL<br />

VESSEL." The San Miguel report translated the<br />

critical sentence as: "T146 SUPPLY FUEL FOR<br />

THE 333 IN ORDER TO GIVE ORDERS TO PUT<br />

INTO OPERATION ((2 GR G)) \,VITH T146." 115<br />

(S//S1) The difference (and correctness/<br />

<strong>in</strong>correctness) between the translations is not as<br />

important as the fact that San Miguel reported<br />

the "operation" as be<strong>in</strong>g noth<strong>in</strong>g more than the<br />

refuel<strong>in</strong>g of the damaged torpedo boats. This was<br />

<strong>in</strong> l<strong>in</strong>e with an earlier <strong>in</strong>tercept of a query from<br />

Haiphong to T-142 ask<strong>in</strong>g ifT-333 had been refueled<br />

yet. 116 Unfortunately, because the San Miguel<br />

version was a lower precedence, it was released<br />

much later. In fact, it came out at 1838Z (0038G),<br />

some two hours after the destroyers had stopped<br />

shoot<strong>in</strong>g.<br />

(g//gI) The quandary created by the reports<br />

about the salvage operations is this: If the orig<strong>in</strong>al<br />

suspect vessels, the two Swatow-class patrol<br />

and two damaged P-4 torpedo boats, were not<br />

participat<strong>in</strong>g <strong>in</strong> the anticipated "attack" aga<strong>in</strong>st<br />

the Desoto patrol, then who exactly was go<strong>in</strong>g to<br />

attack No other messages had been <strong>in</strong>tercepted<br />

which suggested that any other DRV boats were<br />

handed the mission of attack<strong>in</strong>g the American<br />

destroyers. In fact, there was no <strong>in</strong>tercept at all<br />

which h<strong>in</strong>ted at an attack; noth<strong>in</strong>g at all like what<br />

had been <strong>in</strong>tercepted on 2 August. So, if the orig<strong>in</strong>al<br />

culprits were <strong>in</strong>volved <strong>in</strong> salvage operations,<br />

then just what was go<strong>in</strong>g on <strong>in</strong> the Gulf of<br />

Tonk<strong>in</strong><br />

(~//~I) For NSA and the rest of the SIGINT<br />

participants, the second Phu Bai report should<br />

have acted as a brake to any further report<strong>in</strong>g<br />

about an attack. It directly contradicted the <strong>in</strong>terpretation<br />

- remember, it was an <strong>in</strong>terpretation<br />

only - conta<strong>in</strong>ed <strong>in</strong> the <strong>in</strong>itial Critic which<br />

claimed an attack was be<strong>in</strong>g prepared. At this<br />

po<strong>in</strong>t, all the SIGINT community could accurately<br />

state was that there was no signals <strong>in</strong>telligence<br />

reflect<strong>in</strong>g a planned or ongo<strong>in</strong>g attack aga<strong>in</strong>st the<br />

Desoto mission.<br />

(TS//SI) Except this is not what happened.<br />

The second Phu Bai report was not used to report<br />

Page 202<br />

lOP SEEiREl"ff60MltHHX1

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

Saved successfully!

Ooh no, something went wrong!