CIA Files: SARAH Rescue Tech Hidden in MKUltra Vault

# A Rescue Radio Manual in the MKUltra Files: What Is SARAH Doing Here?

When researchers comb through the CIA's declassified MKUltra archive — a collection notorious for its documentation of covert mind control experiments, drug testing on unwitting subjects, and some of the most ethically troubling programs in American intelligence history — they do not expect to find a dry technical manual about aircraft radio equipment. Yet sitting in the vault, stamped with a 2012 declassification approval, is exactly that: a step-by-step operational memo explaining how aircrews should use a piece of survival hardware called SARAH to locate and communicate with downed personnel.

The document, catalogued under CIA-RDP78-03535A000500010001-3 and dated September 1956, describes procedures for operating SARAH — Search And Rescue And Homing — equipment aboard aircraft. Its presence in the MKUltra collection is itself a historical curiosity worth examining. But the contents of the memo, once you look past the archival misfiling, reveal a genuinely fascinating slice of Cold War survival technology that underpinned military rescue operations at the height of global tensions.

SARAH was not a classified weapons system or an exotic espionage tool. It was a radio homing device designed around a single urgent purpose: finding people who needed to be rescued. A survivor — a downed pilot, a ditched aircrew member, anyone equipped with a personal beacon — could transmit a signal that SARAH-equipped aircraft and surface vessels would detect and home in on. The system bridged voice communication and beacon-based homing, meaning rescuers could not only locate a survivor but speak with them directly, a capability that, in 1956, represented meaningful technological sophistication.

The memo walks aircrew through the procedure in careful, unambiguous steps. When a search aircraft's cathode ray tube display — the CRT, an oscilloscope-style screen that visualized incoming radio signals — began showing the characteristic pulse pattern of a survivor's beacon, the operator was instructed to flip the SARAH/NORMAL INTERCOM switch to SARAH mode and set the Transmitter-Receiver function switch to RX R/T, placing the system in receive mode for voice communication. The survivor could then transmit their message. To reply, the operator switched to TX R/T and spoke into the headset microphone, or, if the installation included a press-to-talk switch, simply pressed that button while leaving the function selector in place.

A small but telling technical note in the document describes what happened on the CRT display when the survivor pressed their own LISTEN button to receive a reply: the screen would show several small signal pulses equally spaced along the trace. Operators were told they could verify this by switching to RX B mode and observing the display. This kind of real-time visual confirmation — using a scope to verify that the communication loop was functioning correctly — reflects how seriously engineers had thought through the reliability challenges of rescue operations in contested or remote environments.

The section of the memo designated as standby operation is where the document becomes especially interesting from an operational standpoint. The memo acknowledges a practical limitation head-on: the search aircraft that found the survivor might not be the aircraft capable of actually rescuing them. In that scenario, the search aircraft was instructed to remain on station and activate its own transmitter in TX B/TUNE TX mode, broadcasting a pulse signal of the same type as the survivor's personal beacon. The key advantage here was altitude. A transmitter broadcasting from an aircraft circling at 5,000 feet could be received at ranges far exceeding what a ground-level personal beacon could achieve.

The memo offers a concrete example that brings this to life. A rescue launch — a surface vessel — could receive signals from the orbiting aircraft at ranges exceeding 40 miles. The launch would home on those signals as it closed the distance, navigating toward the general area of the survivor's position. Only when the vessel came within six to seven miles would it begin to pick up the weaker signal from the survivor's own personal beacon transmitter. At that point, the launch would shift its homing to the beacon itself, tracking it directly to the survivor. The aircraft, in this model, was functioning as a high-altitude relay and amplifier for a signal that would otherwise be too faint to guide rescuers from a distance.

This layered approach — aircraft relay homing giving way to direct beacon homing at close range — reflects a thoughtful systems design. It accounted for the real-world limitations of low-powered personal survival equipment and compensated for them by using the physics of altitude to dramatically extend effective range. In an era before GPS, before satellite communication, before any of the digital location infrastructure we take for granted today, this was the architecture that kept downed aircrews alive: radio pulses, cathode ray tubes, and an aircrew member watching a screen and working a function switch.

So why is this document in the MKUltra archive? The honest answer is almost certainly bureaucratic rather than conspiratorial. The CIA-RDP78 document series encompasses a broad range of materials from the Agency's Technical Services Division and related offices, and document series are sometimes grouped by administrative origin rather than subject matter. A 1956 technical memo produced or procured by the same office handling certain MKUltra-adjacent programs could end up filed and later declassified within the same archival block. Researchers working through intelligence archives encounter this kind of cross-contamination regularly.

But that mundane explanation doesn't make the document any less worth reading. Tucked into one of the most controversial archives in CIA history is a quiet reminder that Cold War intelligence bureaucracies were vast, sprawling machines — and that the same institutional structures producing programs as dark as MKUltra were simultaneously working on something as straightforward and humane as making sure a pilot floating in the ocean could be heard.

The open question this document leaves on the table is a simple one: how many other technical and operational documents from this era remain buried in archives that haven't been fully indexed or searched — and what might they tell us about the full scope of Cold War-era programs, both disturbing and mundane, that the CIA was running simultaneously?

— DeClassX