Black Echo

NSA and the Six-Day War Intercepts

The Six-Day War intercept record is not a complete set of raw wartime tapes. It is a partial but powerful public archive made of daily war reporting, presidential intelligence excerpts, and above all the post-attack USS Liberty intercepts that became the best-known surviving slice of NSA’s 1967 Middle East SIGINT record.

NSA and the Six-Day War Intercepts

NSA and the Six-Day War intercepts is one of the most important surviving public records of Cold War-era wartime SIGINT in the Middle East.

It matters because it sits at the intersection of four worlds:

  • real-time war reporting,
  • presidential current intelligence,
  • naval SIGINT vulnerability,
  • and the public afterlife of the USS Liberty incident.

This is a crucial point.

There is no single complete public transcript of the Six-Day War.

What exists instead is a layered archive:

  • wartime PDB excerpts,
  • current-intelligence situation reports,
  • the NSA USS Liberty release set,
  • and later FRUS memoranda and historical reconstructions.

That is why this entry matters so much. It explains the surviving 1967 record as a record.

Quick profile

  • Topic type: historical record
  • Core subject: the surviving public SIGINT and all-source reporting archive of the June 1967 Arab-Israeli war
  • Main historical setting: the Six-Day War of 5–10 June 1967, especially the 8 June USS Liberty attack and its aftermath
  • Best interpretive lens: not one dramatic tape, but a declassified wartime archive made of current reporting and one highly visible intercept dossier
  • Main warning: the public record is important, but still partial and uneven

What this entry covers

This entry is not only about USS Liberty.

It covers a 1967 war archive:

  • what the surviving record includes,
  • what kinds of wartime intelligence products are public,
  • why the Liberty intercepts dominate the archive,
  • how the released PDBs fit in,
  • and what the surviving material can and cannot show about the war.

So NSA and the Six-Day War Intercepts should be read broadly. It names a body of evidence, not a single recording.

What the public intercept record actually is

The phrase Six-Day War intercepts can be misleading if it suggests a complete battlefield tape library.

That is not what the public has.

The surviving public archive is made of:

  • declassified all-source President’s Daily Brief excerpts,
  • situation reports preserved in the NSA Liberty release page,
  • post-attack intercept summaries,
  • and later intelligence memoranda built from available communications and reporting.

That matters because the archive is shaped by declassification politics. The most dramatic surviving material is often the material later pulled into controversy, especially the Liberty case. The broader battlefield SIGINT stream is much less fully visible.

The first wartime PDB: 5 June 1967

The declassified 5 June 1967 PDB is one of the clearest public starting points.

It matters because it captures the war at the moment of outbreak. That PDB said hostilities had begun early that morning, described heavy fighting in the air and along the Egyptian border, and reported Israeli strikes on Egyptian airfields. Most importantly, it said that although reports were still fragmentary, the signs pointed to an Israeli initiative.

This is historically important.

Because it shows that the presidential daily product was already turning early-source reporting into strategic judgment on the first day of war. The finished prose is not labeled “SIGINT” line by line, but it belongs to the kind of all-source crisis reporting in which SIGINT could be one of the most sensitive inputs.

The 6 June PDB and the pace of collapse

The 6 June 1967 PDB deepened that picture.

It reported that Cairo and Damascus were calling for attacks on U.S. and other Western interests, described a rapidly worsening Arab political reaction, and assessed that Israel had gained an early and perhaps overwhelming victory in the air. It also said firm information on ground action remained sparse even as Israeli battlefield success mounted.

That matters because it shows the structure of wartime daily intelligence:

  • firm on some points,
  • uncertain on others,
  • compressed for presidential consumption,
  • and still reflecting the speed of events.

The Six-Day War record survives partly in these compressed daily judgments.

The 7 June and 8 June daily picture

The PDBs for 7 June and 8 June continued the pattern.

The 7 June brief reported that Israeli planes were still striking Jordanian positions, that Israeli forces appeared to hold substantial parts of Sinai, and that Egyptian retreat was becoming evident. The 8 June brief said the UN ceasefire order was being disregarded, that Israel had largely accomplished its objectives in Sinai, and that panic and anger were spreading in Arab capitals.

This matters because it shows that the public war record is not just a post-Liberty archive. The president was seeing a daily sequence of fused current intelligence as the war unfolded.

That daily sequence is one of the most important contexts for understanding the role of SIGINT in the war, even if the released brief does not spell out every source.

The 9 June PDB and the political turn

By 9 June, the PDB was already shifting toward post-ceasefire political consequences.

It reported that the ceasefire had been observed on most fronts during the night, that Israel was discussing the terms of a permanent settlement, and that Soviet officials appeared shocked by the speed of the Arab military collapse. It also pointed to rising danger for U.S. facilities because of Arab resentment against the West.

That matters because the daily brief was tracking more than troop movement. It was translating the war into:

  • battlefield outcome,
  • diplomatic leverage,
  • superpower perception,
  • and danger to Americans abroad.

This is one reason the Six-Day War daily record belongs in an NSA archive at all. SIGINT-fed current intelligence is not only about tactical awareness. It is also about turning a war into a full crisis picture.

The NSA Liberty release page

The most important single public directory for the 1967 intercept record is NSA’s USS Liberty historical release page.

That matters because it shows the scope of the surviving 1967 dossier:

  • Arab/Israel Confrontation files,
  • Arab/Israeli Situation reports,
  • Arab-Israel Situation Report updates,
  • attack summaries,
  • authority messages,
  • and later follow-up analyses.

This is a crucial point.

The Liberty page is not just about one ship. It also preserves part of the wider intelligence atmosphere of 8 June 1967, the day the attack occurred. That makes it one of the closest things the public has to a concentrated 1967 SIGINT release set.

Why USS Liberty dominates the archive

USS Liberty dominates the public archive because controversy forced release.

That matters because it explains the shape of the surviving record.

The United States did not declassify the Six-Day War SIGINT archive as one clean war-history package. Instead, the most extensive public materials cluster around the incident that became the most politically and historically sensitive: the Israeli attack on the U.S. technical research ship USS Liberty on 8 June 1967.

This is why readers have to be careful. The Liberty intercepts are central. But they are not the whole of Six-Day War SIGINT.

What the strongest public intercepts actually show

The strongest released communications are the post-attack intercepts involving Israeli helicopters and Hatzor air control.

That matters because people often imagine the public record includes a full live audio chain of the attack itself. It does not.

The FRUS 22 June 1967 NSA telegram states explicitly that the activity described is based on Israeli plain-language VHF/UHF voice communications intercepted between 1229Z and 1328Z on 8 June and that it deals solely with the aftermath of the attack. It adds that there are no COMINT reflections of the actual attack itself in that available record.

This is one of the most important facts in the whole archive. It defines both the strength and the limitation of the public intercept record.

The helicopter-ground control sequence

The released aftermath sequence is still extremely important.

According to the same NSA telegram:

  • at 1230Z, helicopters were dispatched to check for survivors from an unidentified “warship,”
  • at about 1234Z, Hatzor clarified the ship as Egyptian,
  • at 1307Z, helicopters were told to take Egyptian-speaking survivors to El Arish and English-speaking survivors to Lod,
  • and at 1312Z, one helicopter apparently reported seeing an American flag, prompting a further check.

That matters because these communications became the most famous surviving evidence of confusion, delayed recognition, and identification uncertainty after the attack.

The 13 June CIA memorandum

The 13 June 1967 CIA intelligence memorandum in FRUS remains one of the most valuable interpretive documents in the archive.

It says:

  • none of the communications of the attacking aircraft and torpedo boats is available,
  • the intercepted helicopter-control conversations leave little doubt that the Israelis failed to identify the Liberty as a U.S. ship before or during the attack,
  • and the first available relevant communications begin only after the strike, when rescue and identification questions were already underway.

This matters because it shows the U.S. government trying to build a disciplined analytic case from a partial record. The archive preserves uncertainty, but not emptiness.

The 13 June INR memorandum

The same day, the State Department’s Bureau of Intelligence and Research produced another important memorandum.

That document states that no traffic pertaining to Israeli military communications in the zone had appeared in the record before and during the air and sea attacks, that the first intercept was logged at 1231Z, presumably three minutes after the torpedo strike, and that later messages included the question: “did it clearly signal an American flag?”

This is historically important because it reinforces the central caution of the whole archive: the strongest available COMINT is after-the-fact and identification-focused, not a full real-time attack transcript.

Why clear weather and the flag matter so much

The FRUS and CIA summaries both emphasize details that later became central to historical argument:

  • the weather was clear,
  • the ship’s hull number GTR 5 was prominently displayed,
  • and an American flag was flying.

That matters because the released communications and later analysis revolve around the tension between visible identifiers and delayed recognition. The archival record does not resolve every controversy. But it shows why the question became so enduring.

This is exactly the kind of issue that turns a wartime intercept file into a long-lived historical dossier.

Attack on a Sigint Collector

The NSA historical monograph Attack on a Sigint Collector, the USS Liberty is the most substantial official retrospective treatment of the episode.

It matters because it does not just reproduce a transcript. It reconstructs:

  • why Liberty was there,
  • what the attack did to the U.S. cryptologic system,
  • what communications existed,
  • and how NSA organized itself in response.

This is historically important because it shows the institutional side of the Six-Day War intercept story. The attack did not simply generate evidence. It generated a cryptologic emergency.

The broader 8 June situation reports

The NSA Liberty release page also preserves several wartime reporting files from 8 June 1967:

  • Arab/Israel Confrontation,
  • Arab/Israeli Situation (As of 1200 EDT 8 June 67),
  • Arab-Israel Situation Report, 1100,
  • and Arab-Israel Situation Report, 1200.

These matter because they preserve the wider war atmosphere around the Liberty attack. The attack happened inside an already fast-moving crisis that included:

  • ceasefire disputes,
  • Arab political collapse,
  • battlefield confusion,
  • and escalating U.S. concern about regional backlash.

This is why the Six-Day War intercept archive cannot be reduced only to the ship.

What the archive does not show well

The public archive is much weaker on certain questions.

It does not provide:

  • a complete transcript chain for prewar Israeli or Arab military communications,
  • a full live recording of the attack itself,
  • or a complete publicly accessible set of all NSA collection against the war’s land and air operations.

That matters because readers sometimes project more completeness into the archive than it really has.

The surviving record is powerful. But it is still a surviving record, not the total wartime archive.

SIGINT and the daily presidential picture

One of the reasons this topic belongs in the NSA section is that the Six-Day War shows how SIGINT could shape the daily presidential picture even when source lines are hidden.

The PDB sequence from 5–9 June tracked:

  • the apparent Israeli initiative,
  • Arab air losses,
  • ground uncertainty,
  • ceasefire breakdowns,
  • Soviet reactions,
  • and danger to U.S. interests.

That matters because the released briefs show the output of an all-source system in crisis. SIGINT often mattered most when it disappeared into the prose.

This is one of the deeper lessons of the archive. The more polished the daily product becomes, the harder it is to see the raw upstream source structure.

Why the record is narrower than the 1973 archive

Compared with the public 1973 Yom Kippur War archive, the Six-Day War record is narrower in analytic depth.

That matters because it explains the shape of research on these wars.

The 1967 record is dramatic and incident-centered. The 1973 record is richer for studying warning and estimate failure. By contrast, the Six-Day War public SIGINT archive is strongest where it intersects with the Liberty case and with daily crisis reporting.

That is not a weakness. It is simply the shape declassification gave the archive.

Why this belongs in the NSA section

A reader could argue that this is partly a CIA current-intelligence story or a USS Liberty story.

That is true.

But it belongs in declassified / nsa because the surviving record is one of the clearest public examples of how NSA-era wartime SIGINT enters history: through release pages, through after-action monographs, through intercepted voice summaries, and through the hidden source layer beneath presidential crisis briefings.

This is not just a naval incident story. It is a SIGINT archive story.

Why it matters in this encyclopedia

This entry matters because NSA and the Six-Day War Intercepts is one of the strongest surviving public slices of 1967 Middle East SIGINT.

It is not only:

  • a USS Liberty story,
  • a June 8 story,
  • or a PDB story.

It is also:

  • a wartime current-intelligence story,
  • a post-attack intercept story,
  • a declassified archival story,
  • an example of how SIGINT enters presidential crisis awareness,
  • and a cornerstone entry for anyone building serious pages on declassified NSA history.

That makes it indispensable to the encyclopedia.

Frequently asked questions

What are the “Six-Day War intercepts”?

They are the surviving public archive of declassified intelligence materials tied to the June 1967 Arab-Israeli war, especially wartime PDB excerpts, Arab-Israel situation reports, and the USS Liberty intercept dossier.

Is there one complete public transcript of the war?

No. The public record is partial. It preserves fragments of wartime reporting and a much more explicit set of post-attack Liberty communications, but not a complete battlefield intercept archive.

Why is USS Liberty so central?

Because the Liberty attack produced the most extensive declassification pressure and therefore the richest surviving public SIGINT release set from the war.

Did the released intercepts capture the actual attack?

No. The FRUS June 22 NSA telegram explicitly says the available communications deal only with the aftermath and that there are no COMINT reflections of the actual attack itself in that file.

What did the released helicopter intercepts show?

They showed Israeli helicopters and Hatzor control discussing survivors, initial identification of the ship as Egyptian, later concern over whether it was flying an American flag, and uncertainty about the ship’s identity after the attack.

Did the PDB cover the Six-Day War in real time?

Yes. Declassified PDB excerpts from June 5, 6, 7, 8, and 9 tracked the opening Israeli initiative, Arab air losses, ground fighting, ceasefire problems, and regional political consequences.

Were those PDBs pure SIGINT products?

No. They were all-source current-intelligence products. But SIGINT could have been one of the most important upstream sources behind their judgments.

Why is the public 1967 record considered incomplete?

Because many source lines remain redacted, the archive is strongest only around specific released dossiers, and the government did not publish a full, unified war SIGINT history for the whole conflict.

Suggested internal linking anchors

  • NSA and the Six-Day War intercepts
  • Six-Day War intercept record
  • NSA 1967 Middle East SIGINT
  • USS Liberty and the Six-Day War intercept record
  • Arab-Israel situation reports June 1967
  • Hatzor helicopter intercepts
  • declassified Six-Day War signals intelligence
  • June 1967 war intercept archive

References

  1. https://www.nsa.gov/Helpful-Links/NSA-FOIA/Declassification-Transparency-Initiatives/Historical-Releases/USS-Liberty/
  2. https://www.nsa.gov/portals/75/documents/news-features/declassified-documents/uss-liberty/chronology-events/attack-sigint.pdf
  3. https://history.state.gov/historicaldocuments/frus1964-68v19/ch2
  4. https://history.state.gov/historicaldocuments/frus1964-68v19/d151
  5. https://history.state.gov/historicaldocuments/frus1964-68v19/d172
  6. https://history.state.gov/historicaldocuments/frus1964-68v19/d186
  7. https://history.state.gov/historicaldocuments/frus1964-68v19/d202
  8. https://history.state.gov/historicaldocuments/frus1964-68v19/d230
  9. https://history.state.gov/historicaldocuments/frus1964-68v19/d284
  10. https://history.state.gov/historicaldocuments/frus1964-68v19/d285
  11. https://history.state.gov/historicaldocuments/frus1964-68v19/d319
  12. https://www.nsa.gov/portals/75/documents/news-features/declassified-documents/cryptologic-histories/cold_war_ii.pdf
  13. https://www.nsa.gov/portals/75/documents/news-features/declassified-documents/cryptologic-spectrum/Remember_the_Liberty.pdf
  14. https://www.history.navy.mil/content/dam/nhhc/research/library/online-reading-room/ships/attackliberty/srh-256-liberty-final.pdf

Editorial note

This entry treats the Six-Day War intercepts as a surviving public archive, not as a claim that the entire 1967 SIGINT picture is now open. The archive is strongest where later controversy forced disclosure, especially in the USS Liberty case, and strongest in current-intelligence terms where declassified PDBs preserve how Washington saw the war day by day. The most important caution is simple: the public record becomes most explicit after the attack, not during the attack itself. That limitation does not make the archive weak. It makes it historically precise. It shows how wartime intelligence often survives in fragments, and how those fragments can still reveal a great deal about crisis monitoring, delayed identification, and the hidden SIGINT layer beneath finished intelligence.