The Conspiratory
Case File No. 3805-H● Declassified · Confirmed

The Gulf of Tonkin incident that launched the Vietnam War was misrepresented

By Colin PetersonJuly 8, 2026

Where the evidence lands: Proven
The destroyer USS Maddox underway at sea in the early 1960s
The destroyer USS Maddox (DD-731), central to the 1964 Gulf of Tonkin incident, underway at sea in the early 1960s (U.S. Navy). Credit: U.S. Navy. Public domain · Source
That the Gulf of Tonkin Resolution of August 1964, which gave President Lyndon Johnson broad authority to wage war in Vietnam without a formal declaration, was passed on the basis of a second North Vietnamese torpedo-boat attack on US destroyers that never actually happened, and that the intelligence used to justify it was distorted rather than merely mistaken.
The short answer

Proven. Confirmed by the NSA's own declassified internal history: the second attack used to justify escalation did not occur, and the signals intelligence was misrepresented to suggest it had.

First circulated
1964–1971
Era
Cold War era
Sources
12

The full story

One real battle, and one that probably wasn't

On 2 August 1964, the destroyer USS Maddox was cruising the Gulf of Tonkin on a DESOTO patrol, a signals-intelligence mission that skirted North Vietnamese waters to map coastal radar. Three North Vietnamese P-4 torpedo boats came out to meet it. The Maddox fired first, in what it described as warning shots; the North Vietnamese boats pressed the attack with torpedoes and machine-gun fire, aircraft from the carrier USS Ticonderoga strafed the boats, and the exchange left the Maddox with a single bullet hole and the North Vietnamese with a damaged squadron and several dead sailors. Nobody seriously disputes that this happened. It is the least controversial fact in the entire episode.

The trouble starts two nights later. On 4 August, in heavy seas and poor visibility, the Maddox and a second destroyer, the USS Turner Joy, began picking up radar contacts, sonar returns and radio intercepts that their crews read as another torpedo-boat attack: one that, this time, would be cited by name in the resolution that sent America to war.

The case for it

The night of phantoms

Give the men on the ships their due: this was not obviously a hoax from where they stood. For nearly two hours, from around 21:40 to 23:35 local time, the destroyers' radar and sonar operators reported dozens of contacts, the kind of chaotic, ambiguous readings a storm and adrenaline can produce even without an enemy present. Task force commander Captain John J. Herrick initially reported the ships under attack, and for a few hours that report was the only one Washington had.

But Herrick himself walked it back almost immediately, and in writing. At 01:27, he cabled: “Review of action makes many reported contacts and torpedoes fired appear doubtful. Freak weather effects on radar and overeager sonarmen may have accounted for many reports. No actual visual sightings by Maddox. Suggest complete evaluation before any further action taken.” An hour later he added that the “entire action leaves many doubts.” By that evening, he had traced the phantom torpedoes to a specific and mundane cause: his own sonarman, in rough seas, had been picking up the ship's own propeller beat and mistaking it for enemy torpedoes.

The most vivid eyewitness account is not from a sonar log but from the air. Commander James Stockdale, a Navy pilot who overflew the destroyers throughout the alleged engagement, later described watching the entire episode unfold beneath him and seeing nothing that matched it: “I had the best seat in the house to watch that event, and our destroyers were just shooting at phantom targets — there were no PT boats there... there was nothing there but black water and American firepower.” No pilot from either carrier reported sighting a boat that night.

The task force commander who reported the attack was, within hours, the same man cabling Washington to doubt it.

What the NSA's own historian found

For decades, all of this (Herrick's cables, Stockdale's account, the absence of any wreckage or bodies from a supposedly sunk North Vietnamese boat) remained circumstantial. Suggestive, but not proof that anyone had deliberately misrepresented anything; a bad night at sea is not, by itself, a scandal.

That changed with a document the National Security Agency fought for years to keep secret. In 2001, NSA historian Robert J. Hanyok completed an internal study titled Skunks, Bogies, Silent Hounds, and the Flying Fish: The Gulf of Tonkin Mystery, 2–4 August 1964, for the Agency's classified journal, Cryptologic Quarterly. Hanyok and other agency historians pushed from 2002 onward to make it public; senior NSA officials resisted, reportedly wary of comparisons to another war being justified by flawed intelligence, in Iraq. The impasse broke only after researcher Matthew M. Aid filed a Freedom of Information Act request in 2004 and reporter Scott Shane wrote about the standoff in The New York Times; the NSA then released Hanyok's study, alongside more than 140 other Gulf of Tonkin documents, on 1 December 2005.

Hanyok's conclusion, from inside the agency that generated the original intelligence, was unambiguous: the August 4 attack did not happen. He found that the signals intercepts cited at the time as evidence of a second attack in fact referred to North Vietnamese boats recovering vessels damaged in the real August 2 battle, not preparing a new one. Some of the confusion, his analysis showed, traced to translation: one intercepted Vietnamese phrase could be read as either a military operation or simply boats being towed a long distance for repair, and it was read the way that fit what everyone already expected. Analysts, he concluded, had made “an active effort... to make SIGINT fit the claim” of an attack. Of the intelligence actually available that night, he wrote, “the overwhelming body of reports, if used, would have told the story that no attack occurred.” Only the fragments that supported an attack were passed to policymakers.

“The overwhelming body of reports, if used, would have told the story that no attack occurred.”

None of this required North Vietnamese vessels to be present for the story to look convincing. It required only that the ambiguous evidence be filtered in one direction and the doubts filtered out, a bureaucratic distortion rather than an invented battle from whole cloth, but a distortion with the same consequence.

Two decades, two document releases

The full picture only assembled itself in stages, across two separate declassifications forty years apart. The first came in 1971, when military analyst Daniel Ellsberg leaked the Pentagon Papers (the Defense Department's own classified history of the war, commissioned by Secretary of Defense Robert McNamara) to the press. Among its revelations was that internal doubts about the August 4 incident had existed from the very first hours, well before the public was told otherwise.

McNamara himself spent decades defending the official account. Testifying before the Senate Foreign Relations Committee on 6 August 1964, he stated that “our Navy played no part in, was not associated with, was not aware of, any South Vietnamese actions, if there were any”, denying any connection to the covert raids conducted under the codename OPLAN 34A. Records that surfaced later show the claim was untrue: McNamara had already told Johnson privately that the 34A raids, with which the Maddox's patrol was in fact coordinated, “had some bearing on the attacks.” His public account shifted only decades later. In the 2003 documentary The Fog of War, he conceded there had been no attack on 4 August. In 1995, meeting his former adversary, North Vietnamese general Võ Nguyên Giáp, McNamara asked directly what had happened that night. Giáp's answer was two words: “Absolutely nothing.”

Johnson's own doubts surfaced in private almost as quickly. According to journalist Stanley Karnow, in his 1983 history Vietnam: A History, Johnson told an aide within days of the alleged attack, “Hell, those dumb, stupid sailors were just shooting at flying fish.” None of that private skepticism reached the public account at the time. Decades later, historian Edwin Moise's exhaustive 1996 study of the declassified record and interviews with participants on both sides reached, independently, the same conclusion the NSA would only confirm in 2005: the August 4 attack was a mistake, not a real engagement.

The second release was the NSA's own, in 2005, not a leak this time, but a forced disclosure under freedom-of-information law, of the agency's internal admission that its own signals intelligence had been mishandled. Between them, the two releases turned a persistent rumor into a documented finding: not from outside critics, but from the Department of Defense's leaked internal history and the NSA's own declassified one.

What the doubtful night actually bought

The speed of the congressional response was not entirely improvised. Assistant Secretary of State William Bundy had a draft war-powers resolution finished by early June 1964 (two months before any Gulf of Tonkin incident) after his brother, national security adviser McGeorge Bundy, told the National Security Council that Johnson wanted a North Vietnamese attack on US forces, rather than Viet Cong action inside South Vietnam, as the trigger before sending it to Congress. Johnson held the draft back through the summer, reportedly so it would not compete with the Civil Rights Act for congressional attention. The events of 2–4 August gave him the occasion he had been waiting for.

None of this remained an academic dispute about naval sensors, because of what followed within seventy-two hours. On 7 August 1964, citing “renewed hostile actions against United States ships in the Gulf of Tonkin,” Congress passed the Gulf of Tonkin Resolution, authorizing President Johnson “to take all necessary steps, including the use of armed force,” to defend US forces and allies in Southeast Asia. The Senate passed it 88 to 2, with only Senators Wayne Morse and Ernest Gruening opposed; the House recorded no votes against it at all, passing it 416 to 0, though Kentucky Republican Eugene Siler, who opposed the resolution but was absent that day, arranged to be formally “paired” against it, calling it an attempt to “seal the lips of Congress against future criticism.”

That resolution became the legal basis for the escalation of American combat operations in Vietnam for the next nine years, in the absence of a formal declaration of war. It rested, in significant part, on an incident that (on the evidence of the task force commander who reported it, the pilot who overflew it, and the intelligence agency that generated the signals used to justify it) almost certainly did not occur as described.

How the record reads now, in the Navy's own histories

The most important shift since 2005 is that the finding is no longer confined to one classified NSA monograph fought loose by a Freedom of Information Act request. It has migrated into the official, public record of the institutions that were closest to the events. The Navy's own Naval History and Heritage Command now states flatly, on its public history pages, that “later investigation revealed that the 4 August attack did not happen” and that no North Vietnamese vessels had been present. This is the service whose destroyers reported the attack, writing off its own alarm.

The U.S. Naval Institute, whose Naval History magazine speaks to and for the Navy's officer corps, went further. In a February 2008 analysis, The Truth About Tonkin, Lieutenant Commander Pat Paterson worked through the roughly 200 documents the NSA declassified across 2005 and 2006 and concluded that senior officials had distorted the intelligence record before the American public. Read beside Hanyok's study, it is a second, independent institutional pass over the same primary sources reaching the same place.

And the man who sold the incident to Congress ended up agreeing. In the 2003 documentary The Fog of War, former Defense Secretary Robert McNamara said plainly that the August 4 attack had never happened. When the intelligence agency that produced the intercepts, the naval service whose ships were involved, the institute that represents its officers, and the defense secretary who briefed the resolution all arrive at the same conclusion, the burden has shifted: it is now the denial of the finding, not the finding itself, that stands against the weight of the record.

“Later investigation revealed that the 4 August attack did not happen.” That is not a critic's line. It is the U.S. Navy's own history of its own ships.

Why people believe

Filtered, not fabricated

The precise, honest finding is narrower than the popular shorthand, and worth stating carefully. This is not a documented case of political leaders inventing a battle from nothing to manufacture a war: the sailors on the Maddox and Turner Joy appear to have genuinely believed, in the moment, that they were under attack. What is documented, by the NSA's own historian working from the agency's own archives, is that the intelligence used to confirm that belief to Congress and the public was selectively filtered and misrepresented after the fact, discarding the doubts of the commander on the scene in favor of the version that supported military action.

That distinction (misrepresentation of ambiguous events, rather than premeditated fabrication of an attack) is itself the substantiated finding, and it is a serious one. A war fought for nine years, under a nearly unanimous congressional mandate, rested in part on a night that the government's own signals-intelligence agency now says never happened the way it was told. The doubts were real, they were contemporaneous, and they were filtered out before they reached the vote.

Not a fabricated battle, but a real doubt that was filtered out before it ever reached the floor of Congress.

Advertisement
Open questions

What's still unexplained

  • Whether the misrepresentation of August 4 was deliberate deception at the top or an honest sensor-and-nerves error that was compounded, down the chain, by pressure to confirm what commanders already believed is still argued by historians. Hanyok's own language (that analysts made 'an active effort... to make SIGINT fit the claim') points to something more active than a passive mistake, yet he stops short of alleging conscious fabrication by policymakers, and Edwin Moise's decades-long study of the declassified record and participant interviews concludes the initial confusion was a genuine mistake. Where ordinary bias shades into deliberate distortion, and at what level of the chain of command, has no settled answer.
  • How much Lyndon Johnson personally understood, and when, is unresolved. He is reported to have told an aide within days that 'those dumb, stupid sailors were just shooting at flying fish' (private skepticism sitting oddly beside his public certainty), yet the surviving tape recordings of his calls with McNamara on the night of August 4 itself show the two discussing how to retaliate, not doubting that an attack had occurred. Whether Johnson's doubt was live in real time or arrived only after the fact, as the public record suggests, remains a genuinely open question.
  • Assistant Secretary of State William Bundy had a draft war-powers resolution finished by early June 1964, two months before any Gulf of Tonkin incident, after being told Johnson wanted a North Vietnamese attack on US forces, rather than Viet Cong action inside South Vietnam, as his trigger for sending it to Congress. That the resolution predated the incident it was said to answer is documented; whether this shows an administration poised to seize on any sufficiently ambiguous incident, or one that had already committed to seeking war powers and would have found its occasion regardless of what happened on August 4, is a matter of interpretation the record does not settle.
  • The vote tallies were slightly less uniform than they appear. Kentucky Republican Eugene Siler, who had already decided not to seek reelection, arranged to be formally 'paired' against the resolution while absent from the House floor specifically so his opposition would be recorded, calling the measure an attempt to 'seal the lips of Congress against future criticism.' How much broader unease existed among members who nonetheless voted yes, in a chamber that debated the resolution for well under a day, is not something the record can settle at this distance.

Point by point

The claim: There really was a North Vietnamese attack on a US ship in the Gulf of Tonkin.

What the record shows: Confirmed, but only for August 2. Three North Vietnamese P-4 torpedo boats attacked the USS Maddox that day; the exchange is documented by both sides and is not seriously disputed. It is the second, August 4 incident (the one actually cited in the resolution's operative language) that is the problem.

The claim: The August 4 attack was fabricated by the Johnson administration out of nothing.

What the record shows: Not quite, and precision matters here. The Maddox and Turner Joy crews genuinely believed, in real time, that they were under attack amid a storm, confusing radar returns and an inexperienced sonarman who was later found to be hearing the ship's own propeller. The distortion came afterward, when ambiguous and contradictory signals intelligence was filtered, in Hanyok's words, to 'make SIGINT fit the claim', and only the reports supporting an attack were passed up the chain.

The claim: The officers actually on the scene had doubts at the time.

What the record shows: Confirmed. Captain John J. Herrick, commanding the task force, cabled Washington within hours: 'Review of action makes many reported contacts and torpedoes fired appear doubtful. Freak weather effects on radar and overeager sonarmen may have accounted for many reports.' Navy pilot James Stockdale, who flew low over the scene during the alleged attack, later said he had 'the best seat in the house' and saw 'no boats, no wakes, no ricochets off boats, nothing but black water and American firepower.'

The claim: The intelligence agencies knew, or should have known, that the case was weak.

What the record shows: Confirmed by the NSA's own historian. Robert J. Hanyok's internal study, declassified in 2005, concluded that 'the overwhelming body of reports, if used, would have told the story that no attack occurred,' and that intercepts cited as evidence of a second attack in fact concerned North Vietnamese vessels recovering boats damaged on August 2, not staging a new one.

The claim: This was all revealed decades later through official channels, not leaks alone.

What the record shows: Confirmed, though it took both. The 1971 Pentagon Papers leak first showed that doubts existed from the start; the government's own 2005 NSA declassification, prompted by a Freedom of Information Act request, then supplied the underlying signals-intelligence analysis that explained why.

The claim: Even if one NSA historian said so, no official body ever formally accepted that the August 4 attack did not happen.

What the record shows: It is now the settled institutional account, not a lone dissent. The Navy's own Naval History and Heritage Command states on its public history pages that 'the 4 August attack did not happen' and that no North Vietnamese vessels had been present. The U.S. Naval Institute's Naval History magazine reached the same conclusion in a 2008 analysis by Lieutenant Commander Pat Paterson, drawing on the roughly 200 documents the NSA declassified across 2005 and 2006. When the service whose destroyers were involved and the institute that speaks for its officer corps both say the second attack never occurred, this has left the realm of revisionism.

The claim: Robert McNamara eventually admitted the whole incident was a deliberate hoax.

What the record shows: Not quite, and the distinction is the crux of the case. In the 2003 documentary The Fog of War, McNamara stated plainly that the August 4 attack never happened, a real reversal from the certainty he projected to Congress in 1964. But he framed it as an honest error compounded under pressure rather than a knowing fabrication at the top, and where genuine confusion shaded into deliberate misrepresentation is exactly the question historians still argue. What is no longer in dispute is the bottom line: there was no second attack.

Timeline

  1. 1964-08-02Three North Vietnamese torpedo boats engage the USS Maddox, a US destroyer on a signals-intelligence patrol in the Gulf of Tonkin. This attack is real and not in dispute.
  2. 1964-08-04In heavy weather, the Maddox and USS Turner Joy report radar and sonar contacts they believe are a second torpedo-boat attack. No physical evidence (wreckage, bodies, or debris) is ever recovered.
  3. 1964-08-07Congress passes the Gulf of Tonkin Resolution, citing 'renewed hostile actions' on August 4; the Senate votes 88–2 and the House votes unanimously.
  4. 1971The leaked Pentagon Papers reveal that internal doubts about the August 4 incident existed from the very start, contradicting the public certainty presented at the time.
  5. 1995Former Defense Secretary Robert McNamara meets former North Vietnamese commander Võ Nguyên Giáp, who tells him nothing happened on August 4.
  6. 2005The NSA declassifies over 140 documents, including historian Robert J. Hanyok's internal study concluding the August 4 attack did not occur and that signals intelligence had been mishandled and skewed to fit the claim that it had.
The primary sources

From the case file

The actual records: declassified, released, or leaked. We link straight to each document in its official archive, so you never have to take our word for it. Read the originals yourself.

Connected in the archive

Other case files that cite the same sources

Where the evidence lands

Proven. Confirmed by the NSA's own declassified internal history: the second attack used to justify escalation did not occur, and the signals intelligence was misrepresented to suggest it had.

Reviewed by Colin Peterson · Last reviewed July 18, 2026 · How we rate

Common questions

Is Gulf of Tonkin true?

Proven. Confirmed by the NSA's own declassified internal history: the second attack used to justify escalation did not occur, and the signals intelligence was misrepresented to suggest it had.

What is Gulf of Tonkin?

The naval battle that supposedly launched America into Vietnam turned out to be half real. The first attack happened. The second (the one Congress voted on) almost certainly did not, and the National Security Agency's own declassified history says the signals intelligence used to sell it was misread and then misrepresented.

What does the evidence show?

Confirmed, but only for August 2. Three North Vietnamese P-4 torpedo boats attacked the USS Maddox that day; the exchange is documented by both sides and is not seriously disputed. It is the second, August 4 incident (the one actually cited in the resolution's operative language) that is the problem.

Why do people believe it?

Because, again, the core claim is true: the second incident is now understood, on the intelligence community's own authority, not to have happened as reported, which is a rare thing for a government to concede about its own war-starting evidence.

What is still unresolved?

Whether the misrepresentation of August 4 was deliberate deception at the top or an honest sensor-and-nerves error that was compounded, down the chain, by pressure to confirm what commanders already believed is still argued by historians. Hanyok's own language (that analysts made 'an active effort... to make SIGINT fit the claim') points…

Sources

  1. 1.Skunks, Bogies, Silent Hounds, and the Flying Fish: The Gulf of Tonkin Mystery, 2–4 August 1964, Robert J. Hanyok, National Security Agency (Cryptologic Quarterly, declassified 2005) (2005)
  2. 2.Gulf of Tonkin: Declassified Documents Collection, National Security Agency (2005)
  3. 3.Newly Declassified National Security Agency History Questions Early Vietnam War Communications Intelligence, National Security Archive, George Washington University (2005)
  4. 4.Report of the Office of the Secretary of Defense Vietnam Task Force (the Pentagon Papers), U.S. National Archives and Records Administration (2011)
  5. 5.Tonkin Gulf Resolution (H.J. Res. 1145), August 7, 1964, U.S. National Archives, Milestone Documents (1964)
  6. 6.Senate Roll Call Tally Sheet, Tonkin Gulf Resolution, August 7, 1964, U.S. Senate Historical Office (1964)
  7. 7.The Gulf of Tonkin Incident, 40 Years Later: Flawed Intelligence and the Decision for War in Vietnam, National Security Archive, George Washington University (Electronic Briefing Book No. 132, ed. John Prados) (2004)
  8. 8.The Gulf of Tonkin the 1964 Incidents, Naval History and Heritage Command, U.S. Navy
  9. 9.The Truth About Tonkin, Pat Paterson, Naval History Magazine, U.S. Naval Institute (2008)
  10. 10.Gulf of Tonkin incident (1964), Encyclopaedia Britannica
  11. 11.Tonkin Gulf and the Escalation of the Vietnam War, Edwin E. Moise, University of North Carolina Press (1996)
  12. 12.Vietnam: A History, Stanley Karnow, Viking Press (1983)
Embed this verdict on your site

Paste this snippet to show our sourced verdict as a small card, with a link back to the full case file. Free to use.

<iframe src="https://theconspiratory.com/embed/gulf-of-tonkin" title="The Conspiratory verdict" width="520" height="190" style="border:0;max-width:100%" loading="lazy"></iframe>

Help us investigate

This is a living case file. If you spot an error or know evidence we missed, tell us, and weigh in on where you land.

Where do you land?

Cast your read on this one.

What did we miss?

Spotted an error or know a source worth chasing? Every note is read by a human.

Comments

Add your take. Comments are read and approved by a human before they appear, so keep it on topic and civil. Please do not accuse named, living people of crimes.

Saved on this device so you keep the same name next time. No account needed.

Related case files

Related topics

Advertisement
Written by Colin Peterson · Published July 8, 2026 · Updated July 18, 2026. The Conspiratory lays out the claim, the case on every side, and the sources, so you can weigh it yourself. Spotted a stronger source? Corrections are welcome.