Military Morse Stories: Blinking POWs, Tap-Code Networks and the SOE's Secret Signals

2026-08-04 · History

The military history of morse code is usually told as systems: signal corps, training pipelines, field telegraph. But the moments people remember are stories — individuals who used the code when everything else had been taken from them. This page collects three of the strongest, from three different wars, each showing a different face of the same craft: a signal sent with the body under cameras, a network built through prison walls, and a war fought from a French attic with a suitcase radio and a pencil. Together they explain why militaries kept teaching the code long after the technology moved on.

The blink that beat the censors (Vietnam, 1966)

Jeremiah Denton was a United States Navy aviator shot down over North Vietnam in July 1965 and imprisoned in Hanoi. In May 1966 his captors staged a televised interview — propaganda, designed to show a well-treated prisoner. Denton answered the questions with the composure his captors wanted, describing his treatment as tolerable. And while he spoke, he blinked in morse code — slowly, deliberately, letter by letter: T-O-R-T-U-R-E.

The technique and its execution are both worth sitting with. He had to assume an untrained receiver — someone copying by hand, letter by letter, from a recording — so he paced his blinking slower than any radio operator would ever send, and he sustained it through an entire interview without letting his face break. American naval intelligence, examining the footage, decoded the message: confirmation, straight from inside the prison system, that American POWs were being tortured. Denton spent nearly eight years as a prisoner, was repatriated in 1973, and later was elected to the United States Senate. The footage of the interview survives and is the single most-cited piece of "morse in the wild" in existence — the story, and how anyone can learn the same skill, is covered in our blink-signaling guide.

How do you run a prison as a network? The Hanoi Hilton tap code

Solitary confinement is designed to be an information vacuum: no letters, no visitors, no speech between cells. The prisoners of the Hanoi Hilton — the American name for Hòa Lò prison — defeated it with their knuckles. Cell-to-cell, and eventually camp-to-camp, ran a communication system built on the tap code: a 5×5 grid of the alphabet (I and J sharing a cell in some variants, C and K in the common American POW form) addressed by pairs of knocks — row, then column. Four knocks, pause, three knocks: a letter. Spelled out one painful pair at a time, through walls, in the dark.

Why not straight morse, which some of the aviators knew from their military signaling training? Because the tap code is *timing-insensitive*. Morse lives and dies by the difference between a dot and a dash — a ratio, maintained by sender and judged by receiver. Through a concrete wall, by exhausted men tapping with their fists, that ratio collapses. Counting knocks does not. The prisoners' choice was the same engineering judgment a radio operator makes picking a mode for bad conditions: sacrifice speed, buy reliability. (The full comparison of the two systems — and how to learn each — is on our tap code page.)

What they built with it has rarely been matched. Senior prisoners, among them officers like James Stockdale who later received the Medal of Honor, organized a chain of command *through the walls*: new arrivals were authenticated by tapped questions only the right man could answer, orders for unified resistance to propaganda moved cell to cell, and men in solitary received both news and instruction by knock. Prisoners describe it as the difference between enduring and belonging. The network's raw bandwidth was a few letters a minute; its throughput, measured in sanity and coordination, was enormous.

What was it like to be an SOE wireless operator?

Move back a war and the picture inverts: instead of prisoners using code to survive captivity, agents using code to wage war from inside occupation. The Special Operations Executive was the British organization charged, in Winston Churchill's famous charge, with setting Europe ablaze — sabotage, subversion, support of resistance networks — and almost none of it functioned without radio. Every dropped weapons consignment, every arms request, every coordination message to and from London traveled as morse code keyed by a *wireless telegraphy operator*, usually young, usually working alone in an attic or a back room with a suitcase-sized set.

The operators' job combined the skills of a radio ham, a courier, and a fugitive. Transmissions had to be short — German direction-finding teams in vans cruised the cities triangulating illicit signals, and standard practice warned operators to keep each transmission brief, move after sending, and rotate locations — which meant keying fast, cleanly, first time, while someone watched the street. The danger was chronic and the fate of captured operators notoriously grim. The best-known name is Noor Inayat Khan, the first female wireless operator SOE sent into France, dropped in 1943 to a Paris network that was rolled up almost immediately; left as effectively the last operator in the capital, she continued transmitting for months, was eventually betrayed, refused under interrogation to reveal anything, and was executed at Dachau in September 1944. She was posthumously awarded the George Cross. Her tool was a morse key; her shield was discipline.

How did one-time pads work with morse?

The agents' messages arrived in London as groups of letters and digits — and this is where the era's other great cryptologic idea enters. SOE traffic was encrypted largely with one-time pads: truly random key material, printed in pad form, where each key group is used exactly once and destroyed. Used correctly, the system is the only encryption known to be unbreakable in principle — not hard, *impossible* — because any ciphertext maps to any plaintext with equal probability. The radio link carried gibberish; the pad, in a locked briefcase or memorized block, carried the meaning.

Notice the clean division of labor between the two technologies, because it explains a century of pairings: morse moved bits; the cipher protected them. The operator's craft — what this site teaches — was transmission: recognizing your scheduled contact, keying groups accurately through interference, confirming receipt, tearing down fast. The cryptographer's craft happened before and after, in pencil. A single wrong group on the key was a garble London would query; a reused pad was a network's death. Operators drilled on sending cipher groups precisely because random text, with no word shapes to anticipate, is the hardest material to key accurately — it is pure letter-pattern fluency with no help from context.

The same layered design ran through the whole era. SOS handled distress below the cipher; operational security — schedules, authentication, changeable frequencies — wrapped everything above it. Radio war was an information-systems war a full generation before the phrase existed.

What happens when the enemy runs your radio? The radio game

The darkest chapter of the wireless war belongs to the counterintelligence technique the British called the *radio game*: capture an operator, keep the key transmitting, and impersonate the network. The tool that was supposed to defeat it was the security check — a deliberate quirk agreed in advance with London, a memorized false slip or telltale that a coerced operator could omit to signal capture. The system worked only if London honored it. In the Netherlands, between 1942 and 1944, it failed catastrophically: German counterintelligence captured successive operators, learned or tolerated their checks, and ran the networks themselves — a deception the Allies long mistook for their own people's sloppiness. Dropping zones, arms, and agents flowed into German hands across dozens of operations before the truth became undeniable; the episode is remembered by the Allied codename dispute over it and by the Dutch underground's own name for the affair, *Englandspiel*, the "English game."

The lesson generalized far beyond 1945, and it is really a lesson about signaling itself: a channel that authenticates nothing authenticates whoever holds it. Modern practice — call signs, authentication tables, cryptographic handshakes — exists because a fist, a frequency, and fluent morse were once enough to impersonate a network. When you read that militaries drilled operators on a recognizable sending style, the *fist* that hams still prize, remember that in occupied Europe an individual rhythm was also, briefly, a security credential.

What do all three stories share?

Strip away the settings — prison camp, attic, war — and the same three elements recur. A degraded channel: eyelids, concrete walls, a suitcase transmitter with a van hunting it. A minimum alphabet: two elements, or two knocks, carry everything. A human paying the cost of every element sent. That last one is why these stories, and not others, survive. The code in each case was not machinery doing work; it was discipline doing work, with the code as its notation. It is the same property the escape-room world borrows for drama and assistive technology borrows for communication — the code runs on whatever the body can still produce.

The craft itself is open to anyone now. Learn the letters with the structured course and the chart; practice until random text — the operator's acid test — comes off your key cleanly; try audio decoding to feel what copying through noise was like. Then read the three stories again, in order: a man blinking slower than speech, prisoners counting knocks through walls, a woman in a Paris attic sending groups she could not read, to a city she could not see, in a rhythm she trusted absolutely.

Hidden Morse Code in Pop Culture: EasterMorse Code in Movies and Games: The Sign