The Tehran Incident

The Tehran case has something many sightings lack: a sober military document, written close to the event, by people whose job was assessing threats — not chasing saucers. That a U.S. intelligence agency thought the night worth a detailed memo is, in the end, the most striking thing about it.

What happened

Around half past midnight on September 19, 1976, the control tower at Tehran’s Mehrabad airport began fielding calls about a brilliant, multicolored light over the city. After a check confirmed no known aircraft in the area, the Imperial Iranian Air Force scrambled an F-4 Phantom from Shahrokhi Air Base.

According to the crew’s account, as the jet closed on the object its instruments and communications failed; when the pilot broke off, the systems returned. A second F-4 was launched. Its backseater reported acquiring a radar lock on the object — described as roughly the size of a tanker aircraft. When the pilot attempted to fire an AIM-9 missile at a smaller object that, he said, detached from the main one and came toward his aircraft, his weapons control and instrumentation reportedly went dead. The objects eventually departed, and the jet recovered its systems.

The events were summarized in a Defense Intelligence Agency report distributed to the White House, the Secretary of State, the CIA, the NSA, and others. The memo’s evaluation page graded the case unusually highly for reliability and noted it met the criteria of a “classic” study case — an outlier in the dry language of intelligence reporting.

Why it matters

Tehran is a cornerstone of the “electromagnetic effects” pattern — cases in which witnesses report aircraft systems, weapons, or vehicles being disrupted in the presence of an unidentified object. Whatever the cause, the consistency of those reports across decades and continents is part of what keeps the subject from being purely a matter of lights in the sky.

The skeptical reconstruction is detailed and not unreasonable: a bright celestial object (Jupiter was prominent that autumn), combined with the known temperament of early F-4 avionics under stress, fatigue, and the adrenaline of a night scramble. That can explain much of the report; whether it explains the coordinated equipment failures on two separate aircraft is where defenders push back.

For this field guide, Tehran belongs with the [[1989-belgian-wave]] and the [[2004-nimitz-tic-tac]] encounter as a case where the witnesses were trained military aircrew and the documentation came from inside official channels — making it far harder to wave away than a roadside snapshot.