PRECEDENT // OPEN-SOURCE HISTORICAL ARCHIVE EST. 2026 // EVERY CLAIM SOURCED
Declassified
FILE INDEX — PUBLIC RECORD

PRECEDENT

History doesn't repeat itself. But it sets a precedent.

Every conflict in the headlines has a forgotten precedent — a moment that already showed us how it ends. PRECEDENT finds them: short, cinematic history that explains the present, and lays out the record behind every claim.

01

The Series

Series A — Priority File

Closest Calls

The catastrophes the world barely survived.

The wars, weapons, and disasters that came within one switch, one decision, or one accident of changing everything — and the records that prove how close it got.

  • 01The Biological Attack America Almost Didn't Survive
  • 02The Frozen Island That Nearly Started Nuclear War
  • 03The War That Only Happened on Odd-Numbered Days
  • 04There's a Hydrogen Bomb Buried in North Carolina
  • 05A Soviet Screen Said America Had Launched
  • 06The US Military Lost a Nuke in Georgia
  • 078 Nazi Spies Landed in America
  • 08Japan Invaded American Soil and Held It for a Year
  • 09German U-Boats Were Sinking Ships Off America's Beaches
  • 10Japan's Deadliest Balloon Attack on US Soil
  • 11A Soviet City Was Poisoned by Its Own Secret Weapon
  • 12North Korea Shot Down 31 Americans — and We Never Fired Back
  • 13The Second Attack on Pearl Harbor Almost No One Knows About
  • 14In 1942, Los Angeles Fired 1,400 Shells at an Enemy That Wasn't There
  • 15A Soviet Nuclear Sub Sank Near Hawaii — Then America Stole It
  • 16A Soviet Nuclear Satellite Crashed Into North America — And Most Of It Was Never Found
  • 17In 1999, Two Nuclear Nations Went to War Three Miles Above the Earth
  • 18The Himalayan War That Broke Out During the Cuban Missile Crisis
  • 19Four Years After Saigon Fell, China Invaded Vietnam
  • 2031 Elite Soldiers Trained for 2 Years to Breach the Blue House
  • 21Eisenhower's Nuclear Threat Over These Two Islands
  • 22The Soviet Sub That Nearly Started WWIII — And the Crew That Stopped It
  • 23The Uninhabited Rocks That Nearly Started a War Between NATO Allies
  • 24The Only Time Soviet and Israeli Pilots Ever Dogfought
  • 25A Nuclear-Armed Soviet Submarine Ran Aground Inside Sweden
  • 26The Taliban Took Their Plane. A Year Later, They Took It Back
  • 27Even India's Own Admirals Doubt They Sank This Submarine
  • 28France's Own Paratroopers Took a City in Three Hours
  • 29Not a Tower Shot. Not an Airdrop. China's Only Nuclear Missile Test.
  • 30North Korea's 1983 Plot to Kill a President
  • 31An Intercepted Order Said Kill Them All
  • 32The 1978 Invasion of Chile That Was Called Off With the Fleet at Sea
  • 33The Soviets Shot a Passenger Jet Over the Arctic and Almost Everyone Survived
  • 34In 1938 China Broke the Yellow River to Stop Japan
  • 35America Sent B-52s and a Carrier to Cut Down One Tree in the Korean DMZ
Series B — Field File

Chokepoint Files

The waterways — and supply chains — empires fight over, then and now.

The straits, canals, and sea-lanes that decide wars, and the economic chokeholds that work the same mechanism. The precedent is always older than the headline.

  • 01The Day the U.S. Navy Destroyed Iran's Fleet
  • 02They Were Trapped Here for 8 Years
  • 03A Tiny Boat Sank a Warship in 1967
  • 04The U.S. Made a Whole Country in Three Days
  • 05How Britain's WWI Strategy Could Defeat China Today
  • 06They Turned a Wrecked Tanker Into a Weapon
  • 07How Arab Oil Wrote Beijing's Playbook
  • 08Hong Kong Was the Test Run for Taiwan
  • 09How Xi Jinping Weaponizes "Century of Humiliation"
  • 10Nineteen Ships Were Hit in Six Weeks. Egypt's Suspect Was a Civilian Ferry.
Series C — Standing File

The Japan Files

One country, one century, and the argument it is still having with itself.

Japan's road from empire to pacifist constitution to rearmament — the wartime record, the postwar bargain, and the policy shift now underway in the Pacific. Episodes from this cluster are filed above under their own case numbers; the series is collected as a playlist on the channel.

Open the Japan Files playlist →
03

Latest Transmissions

04

The Case Files

Filter by series
Case File
FILE 76-PCLOSEST CALLS · 35
America Sent B-52s and a Carrier to Cut Down One Tree in the Korean DMZ

A poplar tree blocked the line of sight between two United Nations Command posts inside the Joint Security Area. A five-man work party went out to trim it. North Korean guards took the work party's own axes and killed two American officers with them. Three days later the tree came down behind the largest show of force the DMZ had seen since the armistice.

EVENT: 18–21 AUG 1976 · JOINT SECURITY AREA, PANMUNJOM
Trigger
A poplar obscuring the sightline between UNC Checkpoint 3 and Observation Post 5 in the Joint Security Area — an area where both sides moved freely under the armistice
The killing
18 Aug 1976. Korean People's Army guards attacked the trimming detail; Capt. Arthur Bonifas and 1st Lt. Mark Barrett died of their injuries
The response
Operation Paul Bunyan, 21 Aug — a 16-man engineer team felled the tree escorted by a task force of roughly 800 men, with helicopter gunships, B-52s from Guam and the USS Midway carrier group overhead
The other side
Reported figures put 150–200 KPA troops at the scene with crew-served weapons emplaced. They watched. Nobody fired
Outcome
The tree was removed in under an hour. Kim Il-sung issued a statement of regret — the only one of its kind on record from the North over a DMZ incident
Precedent
Overwhelming, visibly telegraphed force used to close an incident rather than open one — the template argued over every time the DMZ produces a body

Sources & Record

  1. “Korean axe murder incident” — the incident, Operation Paul Bunyan, and the aftermath.
  2. Maj. Vandon E. Jenerette, The Forgotten DMZ, Military Review (US Army Command and General Staff College, May 1988) — the operational account from inside the command.
  3. Note: the size of the North Korean force present on 21 August is reported in a range across sources and is given here as a range, not a figure. The composition of the escort force is drawn from the US Forces Korea after-action record.
Case File
FILE 38-HCLOSEST CALLS · 34
In 1938 China Broke the Yellow River to Stop Japan and Drowned Its Own People

With the Japanese army advancing on Zhengzhou, the Chinese Nationalist government ordered its own engineers to breach the Yellow River dikes at Huayuankou. The flood did slow the advance. It also drowned or starved hundreds of thousands of Chinese civilians, and for seven years the government let the world believe Japanese bombing had done it.

EVENT: JUN 1938 · HUAYUANKOU, HENAN
Decision
June 1938 — Nationalist forces under Chiang Kai-shek breached the southern dike at Huayuankou to halt the Japanese drive on Zhengzhou and the Longhai railway
Scale
Roughly 54,000 km² inundated across Henan, Anhui and Jiangsu; the river shifted its course southward for nine years
Human cost
Estimates of the dead range from about 400,000 to 890,000; approximately four million displaced. No single figure is agreed
Military effect
The advance on Zhengzhou was stopped and Japanese movement was disrupted for months — but Wuhan fell in October 1938 regardless
The cover story
The breach was publicly attributed to Japanese aerial bombing. The Nationalist government did not acknowledge responsibility until 1945
Afterward
The flooded zone contributed to the conditions behind the 1942–43 Henan famine; the dikes were closed in 1947

Sources & Record

  1. Diana Lary, Drowned Earth: The Strategic Breaching of the Yellow River Dyke, 1938, War in History 8:2 (2001) — the decision, the deception, and the casualty debate.
  2. Micah S. Muscolino, The Ecology of War in China: Henan Province, the Yellow River, and Beyond, 1938–1950 (Cambridge University Press, 2015) — the long environmental and famine aftermath.
  3. “1938 Yellow River flood” — chronology and the range of published estimates.
  4. Note: casualty estimates for Huayuankou are genuinely unsettled and vary by a factor of two across the scholarship. The range is stated; no single number is asserted.
Case File
FILE 78-JCLOSEST CALLS · 33
The Soviets shot a passenger jet over the Arctic in 1978 and almost everyone survived

A Korean Air Lines Boeing 707 bound for Seoul drifted off course over the Arctic and crossed into Soviet airspace above the most heavily defended ground in the USSR. An interceptor put a missile into its left wing. The aircraft came down on a frozen lake, and 107 of the 109 people aboard walked away.

EVENT: 20 APR 1978 · KOLA PENINSULA, USSR
Flight
Korean Air Lines 902, Paris–Anchorage–Seoul, Boeing 707, 20 April 1978
The deviation
A navigation error sent the aircraft into a long right-turning arc that carried it southeast, over the Barents Sea and into Soviet airspace above the Kola Peninsula
The intercept
A Sukhoi Su-15 fired an air-to-air missile that destroyed part of the left wing. Two passengers were killed
The landing
The crew descended through cloud and put the aircraft down on the frozen surface of a lake near Kem, Karelia, roughly two hours after being hit
Survivors
107 of 109 aboard survived. Passengers and crew were held and then released; the captain and navigator were detained longer
Precedent
Five years later the same air-defence problem produced Korean Air Lines 007 — and that time nobody survived

Sources & Record

  1. “Korean Air Lines Flight 902” — the route, the intercept, and the forced landing.
  2. Soviet Air Defence Forces records released after 1991, as summarised in the accident literature, for the interception sequence and the weapon used.
  3. Note on direction: four sources place the deviation as a right-turning arc carrying the aircraft southeast. A single account describes a northerly track and also uniquely claims cannon fire rather than a missile; it is not relied on here.
  4. Note on the cockpit exchange: accounts that the interceptor pilot identified the aircraft as civilian before being ordered to fire rest on thin 1978 primary sourcing and are not asserted in the episode or in this file.
Case File
FILE 78-BCLOSEST CALLS · 32
The 1978 invasion of Chile that was called off with the fleet already at sea

Argentina and Chile had spent a decade arguing over three islands at the bottom of the continent. In December 1978 Argentina launched Operación Soberanía to take them. The ships sailed, the troops moved — and the operation was called off hours in, for reasons that were not one reason.

EVENT: 22 DEC 1978 · BEAGLE CHANNEL, TIERRA DEL FUEGO
Dispute
Sovereignty over Picton, Lennox and Nueva at the eastern mouth of the Beagle Channel, and the maritime boundary that followed from them
The trigger
A 1977 binding arbitral award granted the islands to Chile. Argentina declared the award null in January 1978
The operation
Operación Soberanía, launched 22 December 1978 — an amphibious and land offensive with the fleet at sea and units across the Andes on the move
The stand-down
Called off the same day. The record supports three converging causes and does not isolate one: severe weather in the operating area, intelligence on Chilean defensive preparations, and a Vatican intervention
The mediation
Pope John Paul II sent Cardinal Antonio Samoré as personal mediator; both governments accepted mediation on 8 January 1979
Resolution
The 1984 Treaty of Peace and Friendship, ratified after an Argentine referendum, settled the islands on Chile with maritime concessions to Argentina

Sources & Record

  1. Mark Laudy, The Vatican Mediation of the Beagle Channel Dispute: Crisis Intervention and Forum Building (Carnegie Commission on Preventing Deadly Conflict, 2000) — the mediation and the timing of the stand-down.
  2. “Operation Soberanía” — the order of battle and the sequence on 22 December.
  3. “Beagle conflict” — the arbitration, the nullity declaration, and the 1984 treaty.
  4. Note: popular accounts frequently credit the stand-down to the Vatican alone or to weather alone. The causes are stated here together because the record does not support isolating one.
Case File
FILE 78-SCLOSEST CALLS · 31
An Intercepted Order Said Kill Them All. France Moved the Jump Up a Day

Katangese rebels crossing from Angola seized the mining town of Kolwezi, where roughly three thousand European expatriates lived and worked. France put the 2nd Foreign Parachute Regiment onto the town by air, jumping onto a drop zone it had not surveyed, with borrowed parachutes.

EVENT: 13–21 MAY 1978 · KOLWEZI, SHABA, ZAIRE
The seizure
13 May 1978 — the Front for the National Liberation of the Congo crossed from Angola and took Kolwezi, centre of Zaire's cobalt and copper production
At risk
Roughly 3,000 European expatriate residents, alongside a far larger Congolese civilian population, inside a town held by an armed force
The French operation
Operation Léopard — the 2e Régiment étranger de parachutistes under Col. Philippe Erulin jumped on 19 May from Zairean-staged aircraft, using unfamiliar American parachutes
The Belgian operation
Operation Red Bean landed at Kolwezi airport from 20 May, tasked with evacuation rather than combat — the two national operations were not jointly commanded
The toll
Roughly 700 dead in total is the commonly cited figure, of whom about 170 were European; Congolese deaths were the larger share and are less precisely recorded
Precedent
The template for European rapid-intervention operations in Africa, and the case study argued over every time one is proposed since

Sources & Record

  1. “Battle of Kolwezi” — the seizure, both operations, and the casualty accounting.
  2. Pierre Sergent, La Légion saute sur Kolwezi (Presses de la Cité, 1978) — the regimental account of Operation Léopard, written from participant testimony.
  3. Thomas P. Odom, Shaba II: The French and Belgian Intervention in Zaire in 1978 (Combat Studies Institute, US Army CGSC, 1993) — the standard English-language operational study.
  4. Note: casualty totals for Kolwezi vary substantially between French, Belgian and Congolese accounts, and the European figure is far better documented than the Congolese one. The commonly cited totals are given as such.
Case File
FILE 83-RCLOSEST CALLS · 30
Not a Gunman. Not a Timer. A Bugle Sounded Too Early. North Korea's 1983 Plot to Kill a President

North Korean agents placed explosives in the roof of the Martyrs' Mausoleum in Rangoon and waited for the South Korean president to arrive for a wreath-laying. They detonated on a cue. The cue was wrong by a few minutes, and Chun Doo-hwan was still in his car.

EVENT: 9 OCT 1983 · RANGOON, BURMA
Target
President Chun Doo-hwan of South Korea, on a state visit to Burma, due at the Martyrs' Mausoleum on the morning of 9 October 1983
Method
Explosive devices concealed in the roof of the mausoleum, command-detonated by agents positioned nearby
The error
The charge was fired when a bugle sounded during the arrival sequence — taken as the president's arrival. Chun's motorcade was still minutes away
The dead
21 killed, including South Korean Deputy Prime Minister Suh Suk-joon and Foreign Minister Lee Bum-suk, alongside Burmese nationals; dozens injured
Attribution
Burma's investigation identified North Korean military agents. One, Kang Min-chul, was captured and confessed; Burma severed relations with Pyongyang and withdrew its recognition
Precedent
Decapitation as declared statecraft — and the reason every subsequent South Korean presidential trip is planned around it

Sources & Record

  1. “Rangoon bombing” — the attack, the casualties, and the Burmese investigation and verdict.
  2. Report of the Government of the Socialist Republic of the Union of Burma on the findings of its enquiry (November 1983), as summarised in the diplomatic record — the basis for the severing of relations.
  3. Note: the precise arrival cue that triggered the early detonation is reconstructed from the agents' confessions and Burmese investigative findings; accounts differ in detail on what was heard and by whom.
Case File
FILE 66-NCLOSEST CALLS · 29
Not a Tower Shot. Not an Airdrop. China's Only Nuclear Missile Test.

Every other nuclear power tested warheads on towers, from aircraft, or underground. On 27 October 1966 China fired a ballistic missile carrying a live nuclear warhead across roughly 800 kilometres of its own territory and detonated it at the far end. It has not been done that way since, by anyone.

EVENT: 27 OCT 1966 · JIUQUAN → LOP NUR, CHINA
The shot
27 October 1966 — a DF-2A medium-range ballistic missile launched from the Jiuquan test area carrying a live fission warhead
Distance
Roughly 800–900 km downrange, terminating at the Lop Nur test site in Xinjiang
Yield
Approximately 12 kilotons, detonated as an airburst over the target area
What made it unique
The flight path crossed Chinese territory. No other nuclear state has flight-tested a live warhead on a ballistic missile over its own landmass
Why
China needed to prove a deliverable weapon, not a device, and lacked an ocean test range of the kind the US and USSR used
Precedent
The demonstration that a nuclear programme had become a nuclear arsenal — the threshold every later programme is measured against

Sources & Record

  1. John Wilson Lewis and Xue Litai, China Builds the Bomb (Stanford University Press, 1988) — the authoritative account of the programme and the 27 October 1966 combined test.
  2. “Project 596” and the associated Chinese nuclear test list — chronology and yields.
  3. Note: yield and downrange distance are drawn from the published Chinese test record as reconstructed in the Western literature; both are given as approximations.
Feature File
FILE 87-ECHOKEPOINT FILES · FEATURE FILE
The Only Time America Put Its Flag on Another Country's Oil Tankers

Iran and Iraq had spent years attacking each other's oil exports, and Kuwait's tankers were being hit in the crossfire. Kuwait asked Washington and Moscow both. Washington's answer was to reregister eleven Kuwaiti tankers as American ships and escort them — putting the US flag, and the US Navy's obligations, on another country's cargo.

EVENT: 1987–1988 · PERSIAN GULF / STRAIT OF HORMUZ
The problem
The Tanker War phase of the Iran–Iraq conflict: hundreds of merchant vessels attacked in the Gulf through the mid-1980s, with neutral shipping increasingly the target
Kuwait's move
Kuwait approached both superpowers for protection in late 1986 — a request Washington read as a Soviet opening in the Gulf
The mechanism
Operation Earnest Will, from July 1987 — eleven Kuwaiti tankers reflagged as US vessels, crewed accordingly, and escorted by US warships
It went wrong immediately
On the first convoy, 24 July 1987, the reflagged Bridgeton struck a mine. The escorts had no minesweeping capability with them and followed the damaged tanker in
The escalation
USS Samuel B. Roberts was mined on 14 April 1988. Four days later Operation Praying Mantis destroyed much of Iran's operational surface navy
Precedent
Reflagging as a legal instrument of intervention — and the standing argument about who is obliged to keep Hormuz open

Sources & Record

  1. Michael A. Palmer, On Course to Desert Storm: The United States Navy and the Persian Gulf (Naval Historical Center, 1992) — the official service history of Earnest Will.
  2. David Crist, The Twilight War: The Secret History of America's Thirty-Year Conflict with Iran (Penguin, 2012) — the decision-making behind reflagging and the escalation to Praying Mantis.
  3. “Operation Earnest Will” — chronology, convoy record, and the Bridgeton and Samuel B. Roberts mining incidents.
  4. See also Chokepoint Files No. 01 in this archive for Operation Praying Mantis, the engagement this operation ended in.
Case File
FILE 84-RCHOKEPOINT FILES · 10
Nineteen Ships Were Hit in Six Weeks. Egypt's Suspect Was a Civilian Ferry.

Through the summer of 1984 merchant ships began taking underwater damage in the Gulf of Suez and the Red Sea — one after another, on one of the busiest trade routes on earth. There was no attacking navy. There were mines, and Egypt's investigators kept coming back to a civilian ro-ro ferry that had transited the canal days before the first explosion.

EVENT: JUL–SEP 1984 · GULF OF SUEZ / RED SEA
The pattern
Roughly nineteen merchant vessels of multiple nationalities damaged by underwater explosions between July and September 1984, across the Gulf of Suez and the northern Red Sea
The suspect
Egyptian investigation focused on the Libyan-operated ro-ro ferry Ghat, which transited the Suez Canal shortly before the attacks began
The claim
An organisation calling itself Islamic Jihad claimed responsibility; the claim was not independently substantiated and attribution remained contested
The response
A five-nation minehunting effort — the United States, United Kingdom, France, Italy and the Netherlands, with a separate Soviet effort — swept the affected waters
The evidence
A Soviet-manufactured mine was recovered by British forces, consistent with a type available to several states; it did not by itself establish who laid it
Precedent
A chokepoint closed by a deniable weapon delivered from a civilian hull — the same problem that recurs in the Gulf and the Bab-el-Mandeb

Sources & Record

  1. “1984 Red Sea ship attacks” — the sequence of incidents, the multinational clearance effort, and the attribution dispute.
  2. US Navy mine warfare accounts of the 1984 Red Sea clearance operation, for the composition of the international effort and the recovered ordnance.
  3. Note: responsibility for the 1984 mining has never been established in any forum. The Egyptian focus on the Ghat and the Islamic Jihad claim are both reported here as what was asserted at the time, not as findings.
Case File
FILE 61-ACLOSEST CALLS · 28
France's Own Paratroopers Took a City in Three Hours — and Paris Expected Them Next

Four French generals opposed to de Gaulle's Algerian policy seized Algiers overnight using France's own elite paratroop regiment. For four days Paris genuinely expected them to come next — tanks went out around the National Assembly, and de Gaulle went on the radio to speak past the officers to the conscripts.

EVENT: 21–26 APR 1961 · ALGIERS, FRENCH ALGERIA
The generals
Maurice Challe, André Zeller, Edmond Jouhaud and Raoul Salan, opposed to negotiations with the FLN and to Algerian self-determination
The seizure
Night of 21–22 April 1961 — the 1er Régiment étranger de parachutistes took the key points of Algiers in hours, effectively without a fight
Paris
The government invoked Article 16 emergency powers. Armour and troops were deployed in the capital against the possibility of an airborne landing
The broadcast
De Gaulle's 23 April address was aimed at conscript soldiers listening on transistor radios rather than at their officers. Mass compliance by conscripts is generally credited with breaking the putsch
Collapse
The putsch failed by 26 April. Challe and Zeller surrendered; Salan and Jouhaud went underground and into the OAS. The 1er REP was disbanded
The nuclear question
France detonated its fourth atomic test at Reggane in the Sahara on 25 April, during the putsch. The popular account is that the shot was rushed to deny the device to the rebels; historians including Bruno Tertrais have questioned that reading, noting the existing test schedule and the device's condition. The episode does not assert a resolution and neither does this file

Sources & Record

  1. “Algiers putsch of 1961” — the seizure, the response in Paris, and the collapse.
  2. Alistair Horne, A Savage War of Peace: Algeria 1954–1962 (Macmillan, 1977) — the standard narrative history, including the broadcast and the conscripts' response.
  3. Bruno Tertrais, on the April 1961 Reggane test and its relationship to the putsch — the source of the dissent from the popular ‘keep the bomb from the generals’ account.
  4. Note: the Gerboise Verte question is live in the literature. Both readings are presented; neither is asserted.
Feature File
FILE 731-FCLOSEST CALLS · FEATURE FILE
Japan Weaponized Plague on Civilians. America Made Sure No One Paid.

Unit 731 ran human experimentation and biological-weapons development at Pingfang outside Harbin for more than a decade, and field-tested what it built on Chinese towns. At the end of the war the United States acquired the programme's data and, in exchange, kept its directors out of the war crimes dock. That bargain, not the laboratory, is the part with the longer shadow.

EVENT: 1932–1945 · PINGFANG, HARBIN, MANCHURIA — AND AFTER
The programme
Unit 731 of the Kwantung Army, headquartered at Pingfang near Harbin, under Lt. Gen. Shirō Ishii — biological warfare research conducted on living human subjects
The victims
Prisoners referred to in unit records by a euphemism rather than as people. Chinese, Korean, Soviet and other nationals; deaths at the facility are generally estimated in the thousands
Field use
Plague-infected material and other agents were released against Chinese population centres, including Ningbo and Changde. Deaths from the field campaigns are estimated far higher than those at the facility and are not precisely known
The destruction
August 1945 — the Pingfang complex was demolished on order and records were burned as Soviet forces advanced
The bargain
US investigators obtained the programme's human-experimentation data; the principal figures were not prosecuted at the Tokyo tribunal. The Soviet Union tried twelve men separately at Khabarovsk in 1949
What the data was worth
Postwar American assessments of the material's scientific value were mixed, and the question of whether the immunity purchased anything useful remains disputed

Sources & Record

  1. Sheldon H. Harris, Factories of Death: Japanese Biological Warfare 1932–45 and the American Cover-up, rev. ed. (Routledge, 2002) — the standard scholarly account of both the programme and the immunity arrangement.
  2. Nazi War Crimes and Japanese Imperial Government Records Interagency Working Group, Researching Japanese War Crimes Records: Introductory Essays (US National Archives, 2006) — the declassification record and what the American files do and do not contain.
  3. Materials on the Trial of Former Servicemen of the Japanese Army Charged with Manufacturing and Employing Bacteriological Weapons (Foreign Languages Publishing House, Moscow, 1950) — the Khabarovsk trial record.
  4. Note: victim totals for Unit 731 are contested across national historiographies and no agreed figure exists for either the facility or the field campaigns. Ranges are indicated rather than a single number asserted.
Case File
FILE 71-GCLOSEST CALLS · 27
Even India's Own Admirals Doubt They Sank This Submarine

Pakistan's only long-range submarine sailed 4,800 kilometres around India to hunt the carrier INS Vikrant and mine the approaches to Visakhapatnam. It never came home. India credits a destroyer's depth charges. Some of India's own senior officers have never been convinced.

EVENT: 3–4 DEC 1971 · OFF VISAKHAPATNAM, BAY OF BENGAL
The boat
PNS Ghazi, formerly USS Diablo — a Tench-class boat on loan, Pakistan's only long-range submarine
The mission
Transit from Karachi around the subcontinent to the Bay of Bengal to locate and sink INS Vikrant and mine the Visakhapatnam approaches
The loss
The submarine was destroyed off Visakhapatnam on the night of 3–4 December 1971 with all hands, 92 aboard
India's account
INS Rajput reported a disturbance and dropped two depth charges shortly before an underwater explosion was recorded
The dissent
Alternative explanations — an internal explosion during mine-laying, or the boat detonating one of its own mines — are held by researchers and by some Indian naval officers. The wreck lies in shallow water and has been surveyed without settling it
Precedent
A contested kill claim that neither navy can close, forty years on, with the wreck in reach

Sources & Record

  1. “PNS Ghazi” — the boat, the mission, the loss, and the competing explanations.
  2. Indian Navy official history, Transition to Triumph: History of the Indian Navy 1965–1975 — the Rajput account as the service records it.
  3. Note: the cause of Ghazi's loss is disputed and this file does not assert one. The Indian depth-charge claim and the internal-explosion and own-mine explanations are all reported as live.
Case File
FILE 96-KCLOSEST CALLS · 26
The Taliban Took Their Plane. A Year Later, They Took It Back

A Russian cargo aircraft carrying ammunition to Kabul was forced down by a Taliban fighter jet and impounded at Kandahar with its seven-man crew. They were held for more than a year. Then they talked their guards into letting them run the engines for maintenance, and flew the aircraft out.

EVENT: AUG 1995 – AUG 1996 · KANDAHAR, AFGHANISTAN
The interception
3 August 1995 — an Ilyushin Il-76 operated by the Tatarstan firm Aerostan, carrying ammunition to the Rabbani government in Kabul, was forced to land at Kandahar by a Taliban MiG-21
The crew
Seven Russian airmen, held at Kandahar alongside the impounded aircraft
The captivity
378 days. Negotiations for their release ran through Moscow, Islamabad and third parties without result
The escape
16 August 1996 — the crew persuaded their captors to permit engine and systems maintenance on the aircraft, then took off
The flight
They flew to Sharjah in the United Arab Emirates and on to Russia. All seven survived
Precedent
One of very few successful mass escapes by aircrew flying out their own impounded aircraft

Sources & Record

  1. “1995 Aerostan incident” — the interception, the captivity, and the escape.
  2. Contemporary Reuters and Associated Press reporting, August 1995 and August 1996, for the forced landing and the arrival at Sharjah.
  3. Note: the degree of Taliban negligence versus crew deception in the escape is described differently in Russian and Afghan accounts. The duration of captivity is given at 378 days per the consensus of published accounts.
Case File
FILE 81-WCLOSEST CALLS · 25
A Nuclear-Armed Soviet Submarine Ran Aground Inside Sweden — Then Moscow's Fleet Showed Up

A Soviet submarine ran hard aground in restricted Swedish waters, well inside the defences of Sweden's principal naval base. It sat there for ten days. Swedish measurements of the hull indicated warhead material aboard, and a Soviet naval force came south while a neutral country decided what it was willing to do.

EVENT: 27 OCT – 6 NOV 1981 · GÅSEFJÄRDEN, NEAR KARLSKRONA, SWEDEN
The grounding
27 October 1981 — Soviet Whiskey-class submarine S-363 grounded in Gåsefjärden, inside the restricted military area around the Karlskrona naval base
The claim
The Soviet Union described it as a navigational accident caused by equipment failure. The position was deep inside waters requiring deliberate transit to reach
The measurement
Swedish defence researchers measured gamma radiation from the hull and reported a signature consistent with uranium-238, indicating warhead material aboard — most plausibly nuclear-armed torpedoes
The standoff
A Soviet naval force moved toward Swedish waters. Sweden held the submarine, interrogated its commander ashore, and did not permit a Soviet salvage operation
Resolution
Sweden released the submarine on 6 November 1981 after ten days. It was towed clear and handed over at the territorial limit
Precedent
The high-water mark of Sweden's submarine intrusion crisis, and the case that still frames what an armed neutral can enforce

Sources & Record

  1. “Soviet submarine S-363” — the grounding, the detention, and the release.
  2. Swedish Defence Research Establishment (FOA) measurements of the hull, as reported in the Swedish government's public statements of November 1981 — the basis for the warhead-material finding.
  3. Report of the Submarine Defence Commission (Ubåtsskyddskommissionen, Sweden, 1983) — the official Swedish assessment of the intrusion problem.
  4. Note: the episode says ‘warhead material’ rather than ‘nuclear torpedoes’ deliberately. The measurement establishes the presence of a uranium-238 signature; the specific weapon is an inference, and a well-supported one, but an inference.
Case File
FILE 70-RCLOSEST CALLS · 24
The Only Time Soviet and Israeli Pilots Ever Dogfought

By 1970 Soviet pilots were flying combat air patrols over Egypt in Egyptian markings. Israel decided to find out whether they would fight, staged an air raid designed to look routine, and ambushed the response. It is the only air battle in history fought directly between Soviet and Israeli aircrew.

EVENT: 30 JUL 1970 · GULF OF SUEZ, EGYPT
Context
The War of Attrition. Soviet personnel deployed to Egypt from 1970 under Operation Kavkaz, flying MiG-21s and manning air defences
The bait
30 July 1970 — an Israeli strike package flew a profile designed to read as a routine four-ship raid, with additional Mirage and Phantom formations positioned out of sight
The engagement
Soviet-flown MiG-21s were drawn into the ambush over the Gulf of Suez
The result
Four to five Soviet MiG-21s were shot down; Soviet pilots were killed. No Israeli aircraft was lost. Figures differ slightly between Israeli and Russian accounts
Consequence
A ceasefire in the War of Attrition took effect on 7 August 1970, a week later
Precedent
Direct combat between a superpower's aircrew and a client state's adversary, fought and then unacknowledged by both capitals for decades

Sources & Record

  1. “Operation Rimon 20” — the plan, the engagement, and the claimed and admitted losses.
  2. Isabella Ginor and Gideon Remez, Foxbats over Dimona: The Soviets' Nuclear Gamble in the Six-Day War and their subsequent work on Operation Kavkaz — the scale and rules of the Soviet deployment to Egypt.
  3. Note: Israeli accounts generally claim five MiG-21s downed; Russian accounts generally acknowledge four. Both figures are in circulation and the range is given rather than a single number.
Case File
FILE 96-ICLOSEST CALLS · 23
The Uninhabited Rocks That Nearly Started a War Between NATO Allies

Two uninhabited rocks in the Aegean, with a combined area measured in hectares and a permanent population of goats, brought Greece and Turkey to the point of shooting at each other. Both are NATO members. It took an American envoy working the phones overnight to stop it.

EVENT: DEC 1995 – JAN 1996 · IMIA / KARDAK, AEGEAN SEA
The spark
25 December 1995 — the Turkish cargo ship Figen Akat ran aground on one of the islets. Its captain refused Greek assistance, stating the vessel was in Turkish waters
Escalation
Through January 1996 the dispute moved from salvage law to sovereignty. Flags were planted and removed by both sides, with journalists filming
The confrontation
By 31 January both navies had warships in the immediate area and both had put personnel on the islets
The deaths
A Greek Navy helicopter crashed during the crisis, killing its three crew. It remains the only loss of life
The intervention
US envoy Richard Holbrooke worked both capitals through the night; both sides withdrew to a formula of no ships, no troops, no flags
Precedent
The unresolved sovereignty of Aegean features, and the reason a fishing boat in the wrong water is still a NATO problem

Sources & Record

  1. “Imia–Kardak military crisis” — the sequence from the grounding to the withdrawal.
  2. Richard Holbrooke's published account of the overnight mediation, and contemporary US State Department briefings of 31 January – 1 February 1996.
  3. Note: the cause of the Greek helicopter crash was investigated and attributed to an accident. Alternative claims circulate in both countries and are not supported by the official finding.
Case File
FILE 61-KCLOSEST CALLS · 22
The Soviet Sub That Nearly Started WWIII — And the Crew That Stopped It

The Soviet Union's first nuclear ballistic-missile submarine lost reactor coolant in the North Atlantic with no backup cooling system fitted. Eight men went into the reactor compartment in raincoats and gas masks to build a coolant line by hand. They saved the boat. None of them lived long.

EVENT: 4 JUL 1961 · NORTH ATLANTIC, NEAR JAN MAYEN
The boat
K-19, Project 658 — NATO designation Hotel-class — the first Soviet nuclear-powered ballistic missile submarine, commissioned 1960
The failure
4 July 1961 — a rupture in the primary coolant loop of the starboard reactor. No backup cooling system had been installed
The fix
An engineering team welded an improvised coolant line inside the reactor compartment, working in shifts with no meaningful protective equipment
The cost
Eight of the repair party died within weeks of acute radiation exposure. Further crew deaths followed in later years
The wider danger
The boat was operating in the North Atlantic near NATO exercise areas. Accounts differ on how a reactor breach there would have been read; that it would have been read badly is a judgement, not a documented finding
Precedent
A first-of-class warship rushed into service with a known omission — and a crew that absorbed the consequence

Sources & Record

  1. “Soviet submarine K-19” — the accident, the repair, and the casualty record.
  2. Peter A. Huchthausen, K-19: The Widowmaker (National Geographic, 2002) — built on crew testimony released after 1991.
  3. Note: the claim that the accident could have precipitated a wider confrontation is an assessment offered by participants and later writers, not an established finding. It is presented as such in the episode and here.
Case File
FILE 55-YCLOSEST CALLS · 21
Eisenhower's Nuclear Threat Over These Two Islands

The People's Liberation Army took a pair of small islands off the Chinese coast in its first combined air, sea and land operation. Within weeks the United States had evacuated a whole island group, Congress had pre-authorised the use of American forces, and the president had told a press conference that atomic weapons would be used the way one uses a bullet.

EVENT: JAN–APR 1955 · YIJIANGSHAN & THE DACHEN ISLANDS
The assault
18 January 1955 — the PLA's first joint air, naval and amphibious operation, against the Yijiangshan Islands held by Nationalist forces. The garrison was overrun
The consequence
The Dachen (Tachen) Islands became untenable. In February the US Seventh Fleet evacuated the garrison and the civilian population — some 14,000 to 15,000 people
Washington's commitment
The Formosa Resolution, passed 29 January 1955, pre-authorised the president to use US armed forces to defend Taiwan and related positions
The threat
On 16 March 1955 Eisenhower told reporters that against a strictly military target he saw no reason tactical atomic weapons should not be used as one would use a bullet. Dulles had signalled the same days earlier
Resolution
Zhou Enlai signalled willingness to negotiate at the Bandung Conference in April 1955 and the crisis wound down without a settlement of the islands' status
Precedent
The offshore islands stayed the trigger. The same ground produced the 1958 crisis — Closest Calls No. 03 in this archive

Sources & Record

  1. Gordon H. Chang, To the Nuclear Brink: Eisenhower, Dulles, and the Quemoy-Matsu Crisis, International Security 12:4 (1988) — the standard treatment of the nuclear deliberations.
  2. “First Taiwan Strait Crisis” — the Yijiangshan assault, the Dachen evacuation, and the Formosa Resolution.
  3. Appu K. Soman, Double-Edged Sword: Nuclear Diplomacy in Unequal Conflicts — The United States and China, 1950–1958 (Praeger, 2000).
  4. Note: Eisenhower's remark is quoted from the public presidential press conference transcript of 16 March 1955. Whether it constituted a deliberate signal or an unguarded answer is argued in the literature.
Case File
FILE 68-BCLOSEST CALLS · 20
31 Elite Soldiers Trained for 2 Years to Breach the Blue House

North Korea trained a thirty-one-man commando unit for two years against a full-scale replica of the South Korean presidential residence, then sent it through the DMZ to kill President Park Chung-hee. It got within a few hundred metres of the gate before a police challenge on a Seoul street turned into a firefight.

EVENT: 17–21 JAN 1968 · SEOUL, SOUTH KOREA
The unit
Unit 124 of the Korean People's Army — 31 men, trained over roughly two years, reportedly against a full-scale mock-up of the Blue House compound
The infiltration
The team crossed the DMZ on the night of 17–18 January 1968 and moved south on foot toward Seoul
The woodcutters
The commandos encountered South Korean woodcutters, lectured them and released them. The woodcutters reported the contact to police
The stop
On 21 January, dressed in South Korean army uniforms, the team was challenged by police within a short distance of the Blue House. The challenge became a firefight in central Seoul
The outcome
Most of the unit was killed in the pursuit that followed. One, Kim Shin-jo, was captured alive; one is confirmed to have returned north. South Korean police and civilian dead included the Jongno police chief
Two days later
The USS Pueblo was seized off Wonsan on 23 January 1968. Washington chose not to retaliate for either event

Sources & Record

  1. “Blue House raid” — the unit, the infiltration, and the pursuit.
  2. Daniel P. Bolger, Scenes from an Unfinished War: Low-Intensity Conflict in Korea, 1966–1969, Leavenworth Papers No. 19 (US Army Command and General Staff College, 1991) — the authoritative operational study of the period.
  3. Note: the exact distance the team reached from the residence is reported differently across sources, from roughly one hundred metres to several hundred. A range is indicated rather than a figure asserted.
Case File
FILE 79-VCLOSEST CALLS · 19
Four Years After Saigon Fell, China Invaded Vietnam

Vietnam had just beaten the United States, then invaded Cambodia and removed China's ally from power. China's answer was to put a quarter of a million soldiers across Vietnam's northern border to, in Deng Xiaoping's phrase, teach a lesson — while Moscow was treaty-bound to Hanoi and massed on China's other frontier.

EVENT: 17 FEB – 16 MAR 1979 · SINO-VIETNAMESE BORDER
The trigger
Vietnam's December 1978 invasion of Cambodia, which removed the Chinese-backed Khmer Rouge, following the expulsion of ethnic Chinese from Vietnam and a November 1978 Soviet–Vietnamese friendship treaty
The force
Chinese estimates of the invading force run to roughly 200,000–250,000 troops, committed from 17 February 1979
The constraint
The Soviet Union was obliged by treaty to Vietnam and had substantial forces on China's northern border. China planned the operation deliberately shallow and short to keep it below the threshold of Soviet intervention
The cost
Casualties on both sides ran into the tens of thousands within a month. Chinese and Vietnamese figures differ sharply and neither is independently verified
The end
China took Lang Son, declared the lesson delivered, and withdrew by 16 March. Border fighting nonetheless continued intermittently until 1991
Precedent
A nuclear power fighting a limited punitive war inside another nuclear power's security guarantee, and calibrating it to stay short of the guarantor

Sources & Record

  1. Xiaoming Zhang, Deng Xiaoping's Long War: The Military Conflict between China and Vietnam, 1979–1991 (University of North Carolina Press, 2015) — the standard account, drawing on Chinese military sources.
  2. Edward C. O'Dowd, Chinese Military Strategy in the Third Indochina War (Routledge, 2007).
  3. “Sino-Vietnamese War” — chronology and the range of published casualty claims.
  4. Note: casualty figures for this war remain contested and politically loaded on both sides. Ranges are indicated rather than a single number asserted.
Case File
FILE 62-HCLOSEST CALLS · 18
The Himalayan War That Broke Out During the Cuban Missile Crisis

Four days into the Cuban Missile Crisis, China attacked India along two Himalayan fronts at once. For a month the world's attention was somewhere else entirely. Nehru wrote to Kennedy asking for American fighter squadrons; Washington was otherwise engaged, and by the time it wasn't, China had stopped on its own.

EVENT: 20 OCT – 21 NOV 1962 · AKSAI CHIN & NEFA, HIMALAYAS
The dispute
Two separately contested sectors — Aksai Chin in the west, crossed by a Chinese road, and the McMahon Line in the east. India's Forward Policy pushed posts into disputed ground from 1961
The offensive
20 October 1962 — simultaneous Chinese attacks in both sectors, four days after the Cuban Missile Crisis became public in Washington
The ground
Fighting at altitudes above 14,000 feet, against Indian units that were not equipped, acclimatised or supplied for it
The appeal
In November Nehru wrote to President Kennedy requesting American air support, including fighter squadrons. The request went in while Washington's attention was on Cuba
The end
China declared a unilateral ceasefire on 21 November 1962, withdrew in the eastern sector, and retained Aksai Chin
Precedent
The Line of Actual Control was never settled. The same ground produced the Galwan Valley clash in 2020

Sources & Record

  1. Bruce Riedel, JFK's Forgotten Crisis: Tibet, the CIA, and the Sino-Indian War (Brookings Institution Press, 2015) — the American side, including the Nehru correspondence and its timing against Cuba.
  2. Steven A. Hoffmann, India and the China Crisis (University of California Press, 1990) — the Indian decision-making and the Forward Policy.
  3. “Sino-Indian War” — chronology and the published casualty figures.
  4. Note: Indian official casualty figures are used where cited; Chinese figures are far less complete. No composite total is asserted.
Case File
FILE 99-KCLOSEST CALLS · 17
In 1999, Two Nuclear Nations Went to War Three Miles Above the Earth

A year after India and Pakistan tested nuclear weapons, their armies fought a shooting war on Himalayan ridgelines above 16,000 feet — the first direct clash between two nuclear-armed states since the Sino-Soviet border fighting of 1969. In Washington, intelligence reports said Pakistan's nuclear arsenal was being readied while the artillery was still firing.

EVENT: MAY–JUL 1999 · KARGIL, KASHMIR
Trigger
Pakistani soldiers and militants crossed the Line of Control in winter, seizing Indian ridge positions above Kargil
Battlefield
Peaks of ~16,000–18,000 ft — among the highest-altitude ground combat ever fought
Indian response
Operation Vijay — uphill infantry assaults under artillery, plus air strikes kept on India's side of the LoC
Nuclear dimension
U.S. intelligence reported Pakistan preparing its nuclear-capable missile force; Clinton confronted PM Sharif with it on July 4, 1999
Resolution
At Blair House, Sharif agreed to withdraw behind the LoC with no quid pro quo; fighting ended by late July
Precedent
The test case for "limited war under the nuclear shadow" — the phrase strategists still refuse to trust

Sources & Record

  1. "Kargil War" — the intrusion, Operation Vijay, and the withdrawal.
  2. Bruce Riedel, American Diplomacy and the 1999 Kargil Summit at Blair House, CASI Policy Paper No. 5 (University of Pennsylvania, 2002) — the firsthand White House account of the nuclear-preparation intelligence and the July 4 meeting.
  3. Peter R. Lavoy (ed.), Asymmetric Warfare in South Asia: The Causes and Consequences of the Kargil Conflict (Cambridge University Press, 2009) — the standard scholarly study, including the nuclear dimension.
  4. Note: casualty figures are genuinely disputed — India's official toll is ~527 dead; Pakistani losses are contested across sources from several hundred to several thousand. No single number is asserted. The nuclear-preparation report is attributed to Riedel's account, as the record attributes it.
Case File
FILE 78-KCLOSEST CALLS · 16
A Soviet Nuclear Satellite Crashed Into North America — And Most Of It Was Never Found

In January 1978 a Soviet nuclear-powered surveillance satellite tumbled out of orbit and broke apart over the Canadian Arctic, scattering radioactive debris across a stretch of frozen wilderness the size of a small country. NORAD tracked it the whole way down — and could do nothing but watch it fall.

EVENT: 24 JAN 1978 · NORTHWEST TERRITORIES, CANADA
Satellite
Kosmos 954 — a RORSAT ocean-recon craft with an onboard nuclear reactor
Reentry
Jan 24, 1978, over the Northwest Territories near Great Slave Lake
Debris field
~124,000 km² along the "Cosmos track," toward Baker Lake
Recovery
Operation Morning Light — joint U.S.–Canada team, months on foot and by air
Recovered
~0.1% of the fuel; the core disintegrated on reentry into fine particulate
Aftermath
Canada billed the USSR ~C$6M; settled 1981 for ~C$3M

Sources & Record

  1. "Kosmos 954" — the satellite, the reactor, and the uncontrolled reentry.
  2. "Operation Morning Light" — the U.S.–Canada debris recovery across the Arctic.
  3. Atomic Energy Control Board of Canada / Health Canada — the official post-recovery assessment (the ~0.1%-recovered figure originates with the regulator).
  4. Note: roughly 0.1% of the fuel was physically recovered; Canadian regulators assessed the dispersed residue as low-risk. The reactor core broke up on reentry — it was never an intact object on the ground.
Case File
FILE 68-ACLOSEST CALLS · 15
A Soviet Nuclear Sub Sank Near Hawaii — Then America Stole It

In 1968 a Soviet ballistic-missile submarine sank in the deep Pacific northwest of Hawaii, taking its crew and its nuclear missiles to the seabed. Six years later the CIA built a 600-foot ship and a cover story about mining the ocean floor — to raise it in secret.

EVENT: MAR 1968 / 1974 · NORTH PACIFIC
Submarine
K-129 — a Soviet Golf II-class diesel sub carrying nuclear ballistic missiles
Sank
March 1968, ~1,500 nautical miles NW of Hawaii; cause never established
U.S. program
Project Azorian (1974) — the Hughes Glomar Explorer and a giant lifting claw
Cover story
Howard Hughes "deep-sea manganese mining"
Recovered
A portion of the hull; the full yield remains classified
Legacy
The "Glomar response" — "neither confirm nor deny" — born from Phillippi v. CIA (1976)

Sources & Record

  1. "Soviet submarine K-129" — the loss and its unresolved cause.
  2. "Project Azorian" — the CIA recovery, the Glomar Explorer, and the cover story.
  3. CIA, "Project AZORIAN: The Story of the Hughes Glomar Explorer," Studies in Intelligence (declassified) — the Agency's own account.
  4. Note: the sinking's cause remains officially undetermined, and the quantity recovered in 1974 is still classified.
Case File
FILE 42-LCLOSEST CALLS · 14
In 1942, Los Angeles Fired 1,400 Shells at an Enemy That Wasn't There

Days after a Japanese submarine shelled the California coast, an air-raid alarm threw Los Angeles into a blackout — and for an hour, anti-aircraft batteries fired more than a thousand shells into the night sky at an enemy that was never there.

EVENT: 24–25 FEB 1942 · LOS ANGELES, CA
Date
Night of Feb 24–25, 1942 — a day after the Ellwood shelling (Feb 23)
Barrage
~1,400+ anti-aircraft rounds over roughly one hour
Target
Never confirmed — no enemy aircraft, no bombs, none downed
Deaths
Several, from heart attacks and traffic accidents during the blackout
1942 dispute
Navy called it a false alarm; the Army insisted aircraft were present
1983 finding
Office of Air Force History: "war nerves," likely a stray weather balloon

Sources & Record

  1. "Battle of Los Angeles" — the barrage, the blackout, and the absent enemy.
  2. "Bombardment of Ellwood" — the submarine shelling of Feb 23 that primed the panic.
  3. Office of Air Force History, The Army Air Forces in World War II — the 1983 assessment attributing the event to war nerves and a likely weather balloon.
  4. Note: no enemy aircraft were ever confirmed; the institutional record (1983) treats it as a false alarm, not an unsolved sighting.
Case File
FILE 42-KCLOSEST CALLS · 13
The Second Attack on Pearl Harbor Almost No One Knows About

Three months after Pearl Harbor, Japan tried again — flying two giant flying boats across open ocean, refueling from a submarine at a deserted reef, to bomb Honolulu in the dark. Clouds, not defenses, saved the city.

EVENT: 4 MAR 1942 · OAHU, HAWAII
Operation
"Operation K" — the night of March 4, 1942
Aircraft
2 × Kawanishi H8K "Emily" flying boats, from Wotje, Marshall Islands
Refuel
By submarine at French Frigate Shoals, ~560 mi NW of Oahu
Result
Cloud cover scattered the bombs onto Mt. Tantalus — no damage
Consequence
The U.S. garrisoned French Frigate Shoals — denying it to Japan before Midway
Distinction
One of the longest two-plane bombing missions of the war

Sources & Record

  1. "Operation K" — the second raid on Oahu and its failure in cloud.
  2. "French Frigate Shoals" — the refueling reef the U.S. then occupied.
  3. U.S. Naval History and Heritage Command — the operational record of the March 1942 raid.
  4. Note: the bombing did no damage; the lasting effect was the U.S. occupation of the refueling reef, which blunted a planned reconnaissance ahead of Midway.
Case File
FILE 69-ECLOSEST CALLS · 12
North Korea Shot Down 31 Americans — and We Never Fired Back

In 1969 North Korean fighters shot down an unarmed American reconnaissance plane over international waters, killing all 31 men aboard — the single deadliest loss of U.S. aircrew of the Cold War. The United States, weighing nuclear options, ultimately did nothing.

EVENT: 15 APR 1969 · SEA OF JAPAN
Aircraft
U.S. Navy EC-121M Warning Star — unarmed reconnaissance
Date
April 15, 1969, over the Sea of Japan, ~90+ mi off North Korea
Attackers
Two North Korean MiG-21s
Toll
All 31 aboard killed (30 Navy, 1 Marine)
Context
15 months after the seizure of the USS Pueblo (1968)
Response
Nixon administration weighed retaliation, incl. nuclear options — chose none

Sources & Record

  1. "1969 EC-121 shootdown incident" — the attack, the casualties, and the U.S. non-response.
  2. U.S. Naval History and Heritage Command — the loss record of the EC-121M and its crew.
  3. Note: the U.S. resumed reconnaissance flights with fighter escort but took no military action; the deadliest single loss of U.S. aircrew in the Cold War went unanswered.
Case File
FILE 79-SCLOSEST CALLS · 11
A Soviet City Was Poisoned by Its Own Secret Weapon

A spring morning in 1979 — an invisible cloud drifted over part of a Soviet city, and people downwind began to die. The source was a military bioweapons plant where weaponized anthrax had leaked into the air. The state blamed bad meat, and buried the truth for thirteen years.

EVENT: APR 1979 · SVERDLOVSK, USSR
Date
Early April 1979 (release ~April 2)
City
Sverdlovsk (now Yekaterinburg), USSR
Source
Compound 19 — a Soviet military bioweapons facility; an aerosol of weaponized anthrax
Spread
A narrow downwind plume; workers downwind among the first to die
Toll
At least ~64, possibly 100+ (disputed)
Cover-up
Blamed on tainted meat; admitted as a military release by Yeltsin in 1992 — 13 years later

Sources & Record

  1. "Sverdlovsk anthrax leak" — the release, the cover story, and the 1992 admission.
  2. Matthew Meselson et al., "The Sverdlovsk Anthrax Outbreak of 1979," Science (1994) — the epidemiological study mapping the lethal downwind corridor to Compound 19.
  3. Note: the death toll is genuinely disputed (~64 to 100+); the range is given deliberately, with no single number asserted.
Case File
FILE 42-OCHOKEPOINT FILES · 06
They Turned a Wrecked Tanker Into a Weapon

Across the bay from Gibraltar, an interned Italian tanker sat rusting in neutral Spain. Inside its hull, Italian frogmen cut a secret underwater hatch and ran a covert war — riding manned torpedoes into the British anchorage to sink Allied ships, for nearly a year, undetected.

EVENT: 1942–1943 · ALGECIRAS BAY / GIBRALTAR
Unit
Decima Flottiglia MAS — Italy's naval-commando frogmen
Base
SS Olterra — an interned Italian tanker at Algeciras, neutral Spain
Method
A hidden hatch cut below the waterline; "maiale" manned torpedoes launched submerged
Target
Allied shipping anchored at Gibraltar, across the bay
Result
Several merchant ships sunk or damaged, 1942–43 — the base never found while operating
Precedent
Covert denial of a chokepoint, run from a "neutral" doorstep

Sources & Record

  1. "Decima Flottiglia MAS" — the unit, the manned torpedoes, and the Gibraltar raids.
  2. Jack Greene & Alessandro Massignani, The Black Prince and the Sea Devils (Da Capo, 2004) — the standard history of the Decima MAS and the Olterra base.
  3. Note: tallies of ships hit from the Olterra vary by source; the base operated from late 1942 until the Italian armistice in September 1943.
Case File
FILE 73-OCHOKEPOINT FILES · 07
How Arab Oil Wrote Beijing's Playbook

In October 1973, Arab oil producers turned a commodity into a weapon — cutting production and embargoing the United States over its support for Israel. Prices roughly quadrupled, and the industrial West learned that a supply chain can be a chokepoint with no strait on the map. It is the precedent every modern economic-coercion strategy stands on.

EVENT: OCT 1973 – MAR 1974 · GLOBAL OIL MARKET
Trigger
The October 1973 Arab–Israeli War; U.S. resupply of Israel
Weapon
OAPEC production cuts + a total embargo on the U.S. and other supporters of Israel
Price shock
Oil roughly quadrupled — from ~$3 to ~$12 per barrel by early 1974
Impact
Fuel rationing, gas lines, and recession across the industrial West
Lifted
March 1974 — after the leverage had already been proven
Precedent
Supply-chain dominance as a political weapon — the mechanism behind today's rare-earth and export-control chokeholds

Sources & Record

  1. U.S. Dept. of State, Office of the Historian, "Oil Embargo, 1973–1974" — the official account of the embargo and its effects.
  2. "1973 oil crisis" — the production cuts, the price shock, and the aftermath.
  3. Daniel Yergin, The Prize: The Epic Quest for Oil, Money, and Power (Simon & Schuster, 1991) — the standard history of oil as a strategic weapon.
  4. Note: the "quadrupled" figure describes the posted-price move from roughly $3 to ~$12/barrel between October 1973 and early 1974; exact figures vary slightly by benchmark and are rounded as popular history responsibly rounds.
Case File
FILE 44-FCLOSEST CALLS · 10
Japan's Deadliest Balloon Attack on US Soil

Japan launched thousands of paper-and-rubber balloons carrying bombs into the jet stream, aiming them across the entire Pacific Ocean at the American mainland. Most failed. One came down in an Oregon forest — and killed a pregnant woman and five children on a church picnic.

EVENT: NOV 1944 – MAY 1945 · PACIFIC NORTHWEST, U.S.
Weapon
Fu-Go — hydrogen balloons ~33 ft across, riding the jet stream ~5,000 mi from Japan
Launched
~9,000+ from Nov 1944 — meant to start forest fires and spread panic
Reach
Fragments found across the western U.S. and Canada
The deaths
May 5, 1945, near Bly, Oregon — Elsie Mitchell (pregnant) and five children
Distinction
The only deaths from enemy action on the U.S. mainland in WWII
The blackout
A U.S. press blackout hid the landings — denying Japan feedback, ending the campaign

Sources & Record

  1. "Fu-Go balloon bomb" — the campaign, the jet-stream mechanism, and the press blackout.
  2. "Mitchell Monument" — the Bly, Oregon memorial to the six victims of May 5, 1945.
  3. Robert C. Mikesh, Japan's World War II Balloon Bomb Attacks on North America (Smithsonian Annals of Flight) — the standard technical history.
  4. Note: the six victims near Bly were the only people killed by enemy action on the continental U.S. during the war.
Case File
FILE 42-DCLOSEST CALLS · 09
German U-Boats Were Sinking Ships Off America's Beaches

In the first months of 1942, German U-boats hunted freely along the American East Coast — torpedoing ships within sight of the beaches while the cities behind them stayed lit, silhouetting every target. More people died in those waters than at Pearl Harbor.

EVENT: JAN–AUG 1942 · U.S. EAST COAST
Operation
Paukenschlag ("Drumbeat") — opened Jan 1942 with 5 U-boats
Known as
The "Second Happy Time" — to the U-boat crews
Toll
~600 ships / ~3.1M tons sunk in American waters, 1942
Deaths
~5,000 — roughly double Pearl Harbor
Witnessed
SS Gulfamerica burned off Jacksonville Beach in view of crowds (Apr 1942)
Why
No coastal convoys at first; cities resisted blackout for months

Sources & Record

  1. "Second Happy Time" — the campaign record, tonnage, and the lit-coast failure.
  2. Michael Gannon, Operation Drumbeat (Harper & Row, 1990) — the standard history of the first U-boat wave on the American coast.
  3. SS Gulfamerica — the tanker torpedoed within sight of Jacksonville Beach, April 10, 1942.
  4. Note: ship and tonnage totals for 1942 vary with how "American waters" is bounded; figures here follow the standard campaign accounting.
Case File
FILE 42-ACLOSEST CALLS · 08
Japan Invaded American Soil and Held It for a Year

In June 1942 a Japanese force seized two American islands at the end of the Aleutian chain — the first foreign seizure of U.S. territory since the War of 1812. The villagers were shipped to a prison camp in Japan. Taking the islands back ended in one of the largest banzai charges of the war.

EVENT: JUN 1942 – AUG 1943 · ATTU & KISKA, ALASKA
Seized
Kiska Jun 6, Attu Jun 7, 1942 — unopposed
Captives
42 Attu villagers sent to Otaru, Hokkaido; 16 died in captivity
Retaken
Battle of Attu, May 11–30, 1943 (U.S. 7th Infantry Div.)
Distinction
The only WWII land battle on incorporated U.S. soil
Toll
U.S. 549 killed, 1,148 wounded · Japan 2,351 killed, 28 captured
Ending
Yamasaki's banzai charge, May 29; Kiska found abandoned Aug 15

Sources & Record

  1. "Battle of Attu" — the campaign, casualty record, the final charge, and the fate of the Attu villagers.
  2. National Park Service, Aleutian Islands WWII National Historic Area — incl. the Lost Villages record and the Attu Boy survivor memoir.
  3. Smithsonian Magazine, "Unraveling the Mysteries of the Battle of Attu".
  4. Note: counts of Attuan deaths in captivity vary — 16 of the 42 imprisoned per the battle record; some accounts count 21+ including infants born in Japan.
Case File
FILE 42-PCLOSEST CALLS · 07
8 Nazi Spies Landed in America

Eight trained saboteurs stepped off German U-boats onto American beaches carrying explosives, roughly $175,000 in U.S. cash, and a two-year target list. The plot didn't fail because they were caught. It failed because one of them picked up a phone and called the FBI.

EVENT: JUN 1942 · AMAGANSETT, NY / PONTE VEDRA, FL
Landings
Jun 13, 1942 — Amagansett, NY (U-202); Jun 17 — Ponte Vedra Beach, FL (U-584)
Training
Quenz Lake sabotage school, near Brandenburg
Targets
Aluminum plants, rail chokepoints (Hell Gate Bridge, Horseshoe Curve), canal locks
The break
George Dasch phoned the FBI Jun 14; surrendered in Washington Jun 19
Roundup
All 8 in custody by Jun 27 — before a single act of sabotage
Verdict
Secret military tribunal; 6 executed Aug 8, 1942; Dasch & Burger deported 1948

Sources & Record

  1. FBI History, "Nazi Saboteurs and George Dasch" — the Bureau's own case record.
  2. "Operation Pastorius" — the landings, the targets, and the collapse of the plot.
  3. Ex parte Quirin, 317 U.S. 1 (1942) — the Supreme Court ruling upholding the military tribunal.
Case File
FILE 39-ACLOSEST CALLS · 04
There's a Hydrogen Bomb Buried in North Carolina

A B-52 broke apart over North Carolina and dropped two four-megaton hydrogen bombs on American soil. One went through nearly its entire arming sequence — a single low-voltage switch was all that stopped the detonation. The other buried itself in a field, and its core was never recovered.

EVENT: 24 JAN 1961 · FARO / GOLDSBORO, NC
Aircraft
B-52G, Seymour Johnson AFB
Weapons
2 × Mark 39 Mod 2 (~3.8 MT each)
Yield scale
~250× Hiroshima, per bomb
Arming
3 of 4 safeties defeated; last switch held
Bomb 2
Secondary stage never recovered
Status
USAF holds an easement over the site

Sources & Record

  1. Parker F. Jones, "Goldsboro Revisited" — the declassified 1969 Sandia memo, hosted by the National Security Archive; the assessment that a detonation was "credible."
  2. Eric Schlosser, Command and Control (Penguin, 2013) — the book that surfaced the memo via FOIA.
  3. PBS American Experience, "Command and Control: Goldsboro, 1961".
  4. Incident record, incl. the buried secondary stage and the USAF easement: 1961 Goldsboro B-52 crash.
Case File
FILE 731CLOSEST CALLS · 01
The Biological Attack America Almost Didn't Survive

Japan's Unit 731 weaponized the bubonic plague. In the final months of WWII it drew up a plan to carry the disease across the Pacific and release it over San Diego — a strike scheduled for weeks after Japan ultimately surrendered.

EVENT: 1945 · UNIT 731
Program
Unit 731, Harbin, occupied Manchuria
Director
Gen. Shirō Ishii
Operation
Cherry Blossoms at Night (finalized Mar 1945)
Method
I-400 submarines → floatplanes, plague-flea bombs
Target
San Diego / Southern California
Outcome
Set for Sep 22, 1945; never launched — Japan surrendered Aug 15

Sources & Record

  1. Operation Cherry Blossoms at Night — the plan, the I-400 submarines, and the intended strike on the U.S. West Coast.
  2. Unit 731 — the documented record of Japan's biological-warfare program under Gen. Ishii.
  3. Sheldon H. Harris, Factories of Death: Japanese Biological Warfare, 1932-45 (Routledge) — the standard scholarly history.
  4. Note: some historians date the operation's cancellation to spring 1945 rather than the surrender; the plan itself is documented and was never carried out.
Case File
FILE 69-ZCLOSEST CALLS · 02
The Frozen Island That Nearly Started Nuclear War

On a tiny, uninhabited island in a frozen river, a planned Chinese ambush of Soviet border guards spiraled into weeks of fighting — and Soviet officials are documented to have weighed a preemptive nuclear strike on China.

EVENT: 2 MAR 1969 · USSURI RIVER
Place
Zhenbao / Damansky Island, Ussuri River
Dates
Mar 2, 1969 (ambush); Mar 15 (second battle)
Trigger
Chinese ambush of Soviet border troops
Casualties
~58 Soviet / ~29+ Chinese (disputed)
Escalation
USSR weighed a strike on China's nuclear sites
Aftermath
Pushed Beijing toward the U.S.; island ceded to China, 1991

Sources & Record

  1. Sino-Soviet border conflict (1969) — the Zhenbao/Damansky clashes and the nuclear brinkmanship that followed.
  2. Lyle J. Goldstein, "Return to Zhenbao Island" (The China Quarterly) and CNA studies on the 1969 crisis — scholarship on the Soviet nuclear-strike deliberations.
  3. Hoover Institution analyses of the 1969 border conflicts as a Cold War turning point.
  4. Note: casualty figures are self-reported by each side and remain contested.
Case File
FILE 58-KCLOSEST CALLS · 03
The War That Only Happened on Odd-Numbered Days

When China shelled the Nationalist-held island of Kinmen in 1958, Washington came to the edge of nuclear war over it. The crisis cooled into one of history's strangest cease-fires: the two sides shelled each other only on alternating days — a ritual bombardment that lasted about two decades.

EVENT: 23 AUG 1958 · KINMEN (QUEMOY)
Conflict
Second Taiwan Strait Crisis
Opened
Aug 23, 1958 — 40,000+ shells on day one
Sides
PRC (PLA) vs ROC (Taiwan), backed by the U.S.
U.S. role
Escorted resupply convoys; nuclear use weighed
The deal
PRC shelled odd days, ROC even days
Duration
~20 years, until U.S.–PRC normalization (1979)
Case File
FILE 83-PCLOSEST CALLS · 05
A Soviet Screen Said America Had Launched

Just after midnight, a Soviet early-warning bunker reported that the United States had launched its nuclear missiles. The duty officer had minutes to pass it up the chain — which meant retaliation. Convinced the computer was wrong, he called it a false alarm. It was.

EVENT: 26 SEP 1983 · SERPUKHOV-15
Officer
Lt. Col. Stanislav Petrov, Soviet Air Defense
System
Oko early-warning satellites, Serpukhov-15
Alert
1, then up to 5 U.S. ICBMs “launched”
Real cause
Sunlight off high cloud, misread by satellites
His call
False alarm — did not report it up
Context
3 weeks after the KAL 007 shootdown
Case File
FILE 58-TCLOSEST CALLS · 06
The US Military Lost a Nuke in Georgia

After a midair collision, a B-47 pilot jettisoned a hydrogen bomb into the shallow water off Tybee Island to save his crippled plane. The Air Force searched for two months, never found it, and gave up. It is still down there.

EVENT: 5 FEB 1958 · WASSAW SOUND, GA
Date
Feb 5, 1958 — B-47 / F-86 midair collision
Weapon
Mark 15 hydrogen bomb (~7,600 lb)
Jettisoned
Into Wassaw Sound, ~15 mi from Savannah
Search
~2 months; declared lost, Apr 1958
Likely
Buried under 5–15 ft of silt
2001 USAF view
Leave it; capsule contents disputed

Sources & Record

  1. "1958 Tybee Island mid-air collision" — the collision, jettison, and failed recovery.
  2. Center for Arms Control and Non-Proliferation, "Fact Sheet: The Missing Tybee Bomb".
  3. NPR, "For 50 Years, Nuclear Bomb Lost in Watery Grave".
  4. Note: whether the bomb held a fissile capsule is disputed — a 1966 Congressional document and the Air Force have differed.
Case File
FILE 88-MCHOKEPOINT FILES · 01
The Day the U.S. Navy Destroyed Iran's Fleet

After an Iranian mine nearly sank a U.S. frigate, the Navy retaliated in a single day, sinking or crippling much of Iran's surface fleet. It remains the largest U.S. surface naval battle since WWII — the precedent shadowing every U.S.–Iran clash in the Gulf today.

EVENT: 18 APR 1988 · PERSIAN GULF
Date
Apr 18, 1988 (one day)
Trigger
USS Samuel B. Roberts hit an Iranian mine (Apr 14)
U.S. action
2 oil platforms destroyed; frigate Sahand & boat Joshan sunk; frigate Sabalan crippled
Distinction
Largest U.S. surface action since 1945
First
U.S. Navy's only surface-to-surface missile exchange
Pairs with
2026 Strait of Hormuz tensions
Case File
FILE 67-SCHOKEPOINT FILES · 02
They Were Trapped Here for 8 Years

When the Six-Day War slammed both ends of the Suez Canal shut, fourteen cargo ships were caught in the middle — and stayed stranded for eight years. The crews built their own micro-society while desert sand slowly buried their hulls.

EVENT: 1967–1975 · GREAT BITTER LAKE
Trigger
Six-Day War, June 1967 — Egypt blocked the canal
Trapped
14 ships in the Great Bitter Lake (8 nations)
Nickname
“Yellow Fleet” — coated in desert sand
Crews
Formed the Great Bitter Lake Association
Freed
1975, after the canal was cleared
Condition
Only 2 ships left under their own power
Case File
FILE 67-ECHOKEPOINT FILES · 03
A Tiny Boat Sank a Warship in 1967

The first warship ever sunk by a ship-launched guided missile. Small Egyptian missile boats killed an Israeli destroyer from miles away — the moment cheap standoff weapons could sink capital ships, and the precedent for today's drone-and-missile naval war.

EVENT: 21 OCT 1967 · OFF PORT SAID
Target
INS Eilat (ex-HMS Zealous), ~1,710-ton destroyer
Date / place
Oct 21, 1967 · ~13 nm off Port Said
Attacker
Egyptian Komar-class missile boats
Weapon
Soviet P-15 "Styx" missiles — 3 of 4 struck
Losses
47 of 199 crew killed; ~100 wounded
Significance
First warship sunk by a guided anti-ship missile

Sources & Record

  1. INS Eilat (1967 sinking) — the engagement, the Styx missiles, and the casualty record.
  2. U.S. Naval Institute, Naval History and Proceedings — analyses of the Eilat as the first warship sunk by a guided anti-ship missile and its doctrinal impact.
  3. Note: the Eilat was a WWII-era destroyer (ex-HMS Zealous) transferred to Israel in 1955.
Case File
FILE 03-PCHOKEPOINT FILES · 04
The U.S. Made a Whole Country in Three Days

When Colombia refused to hand over canal rights, the United States backed a Panamanian revolt, recognized the new country three days later, and signed a treaty granting itself the Canal Zone “in perpetuity.” A nation was manufactured to build a waterway.

EVENT: NOV 1903 · ISTHMUS OF PANAMA
1903
Colombia's senate rejected the Hay-Herrán canal treaty
Nov 3
Panama declared independence (U.S.-backed)
USS Nashville
Blocked Colombian troops from crossing
Nov 6
U.S. recognized Panama — three days later
Nov 18
Hay–Bunau-Varilla Treaty → U.S. Canal Zone
Terms
$10M + $250k/yr; canal completed 1914
Case File
FILE 14-BCHOKEPOINT FILES · 05
How Britain’s WWI Strategy Could Defeat China Today

In WWI, a naval blockade slowly starved Germany — hundreds of thousands of civilians died without a shot fired at them. A century later, China fears the same fate through a single strait it does not control: the “Malacca Dilemma.”

PRECEDENT: 1914–19 BLOCKADE → MALACCA TODAY
Precedent
Allied naval blockade of Germany, 1914–1919
Method
Foodstuffs declared contraband; supply cut off
Toll
Est. 400,000+ German civilian deaths (figures vary)
Today
~80% of China's oil transits the Strait of Malacca
The fear
A U.S.-led blockade could choke that lifeline
Term
“Malacca Dilemma,” coined by Hu Jintao, 2003

Sources & Record

  1. "Blockade of Germany (1914–1919)" — the starvation blockade and its civilian toll.
  2. Hoover Institution, "The Malacca Myth: Lessons on Economic Warfare from the History of Naval Blockades".
  3. "Malacca dilemma" — the chokepoint vulnerability it names.
05

The Feature Files

The full-length investigations — where a case file becomes the whole story: the precedent, its escalations, and the line to today's headlines, traced start to finish.

06

How These Are Made

PRECEDENT is an independent, one-person archive. The visuals are AI-generated cinematic reconstructions — illustrative atmosphere, never claimed as documentary footage, and disclosed as synthetic on every upload.

The history is not. Every figure, date, and claim is drawn from primary documents and established scholarship, rounded only where popular history responsibly rounds, and attributed in-line where a claim is contested. The case files above exist so you can check the work yourself.

Sourced

Each episode carries its primary record — memos, accident summaries, scholarship — listed in this archive.

Disclosed

AI-generated visuals are labeled as synthetic content on every video. No footage is presented as real.

Adversarially checked

Scripts are pressure-tested for overclaim before publication. Accuracy is the gate, not the score.

07

The Distribution List