The Tehran Intercept

# The Tehran Intercept

[View on uap.fun](<https://uap.fun/encounters/tehran-1976/>)

Case file 005 · 1976

A brilliant light over Tehran. Two F-4 intercepts. A weapons panel gone dark—and an official report that became UFO lore.

![Illustration from behind a 1970s fighter pilot looking across Tehran at night toward one bright, unresolved light above the mountains.](<https://uap.fun/tehran-intercept-1976.webp>)

Not a real photo.

## At a glance

- **Date:** September 19, 1976
- **Location:** Tehran and the airspace south of the city
- **Classification:** Military radar-visual encounter
- **Record status:** Unresolved in the public record
- **Last updated:** September 16, 2026 at 11:44 AM CDT
- **Source review:** September 16, 2026 · Reviewed annually or when significant records emerge

## The story

### Telephone calls after midnight

At about 12:30 a.m. on September 19, 1976, an Imperial Iranian Air Force command post received four calls from residents of Tehran’s Shemiran district. The descriptions were uncertain from the beginning: some callers compared the object to a bird, others to a helicopter carrying a light. No helicopters were reported airborne. The officer contacted Mehrabad Airport, then went outside and saw something he judged larger and brighter than a star. That brief sequence—ordinary explanations considered, a direct look, then a decision to investigate—opened one of the most dramatic military UFO reports of the Cold War.

### The first Phantom turns away

An F-4 Phantom II left Shahrokhi Air Base at about 1:30 a.m. and headed toward a point roughly 40 nautical miles north of Tehran. The U.S. defense attaché report says the light was visible from 70 miles away. At an indicated range of about 25 nautical miles, the crew reported losing instrumentation, UHF radio, and the cockpit intercom. They abandoned the approach and turned back. According to the report, the systems returned when the aircraft moved away. The document does not name this crew; names attached to the first flight in later accounts should therefore be read as later identification, not text printed in the surviving message.

### A second crew finds a return

Ten minutes later, a second F-4 launched. Its pilot was later publicly identified as Parviz Jafari. The rear-seat crew member reportedly acquired a radar lock at 27 nautical miles, twelve o’clock high, with a closure rate recorded as 150 nautical miles per hour. As the distance fell to 25 nautical miles, the return appeared to move away and hold that separation. The report compares its radar return with a 707 tanker, but that wording concerns return strength, not a measured physical diameter. Visually, the crew could not resolve a body through the brilliance. They described rapidly alternating blue, green, red, and orange lights arranged in a rectangular pattern.

### The light that came toward them

South of Tehran, the crew reported a second bright light separating from the first and coming rapidly toward the aircraft. Jafari attempted to fire an AIM-9 missile. At that moment, the surviving account says, the weapons-control panel went out and both UHF and internal communications failed. He broke sharply into a turn and negative-G dive. The smaller light seemed to follow at three to four nautical miles, cut inside the turn, then return to the primary light in what the report called a perfect rejoin. The language records the crew’s perception during a fast night intercept; it is not an independent measurement of the light’s path or intention.

### A descent toward the dark ground

Soon afterward, another light appeared to descend from the primary object. The crew expected an impact, yet reported that it slowed near the ground and illuminated an area two to three kilometers wide. They descended from 25,000 to 15,000 feet to watch and mark the position. On the approach to Mehrabad, they reported intermittent interference along a particular bearing; a civil airliner in the vicinity also reported a communications failure but no visual sighting. The F-4 crew additionally described a cylinder-like light near final approach. The tower did not initially see it, then reportedly picked it up after the pilot supplied a direction.

### Daylight finds no landing trace

In daylight, the crew returned by helicopter to the dry lake bed where they believed the descending light had reached the ground. They found no object and no visible trace at the marked spot. West of the area, however, they detected a strong emergency-beacon signal near a small house. The residents said they had heard a loud noise and seen a lightning-like flash during the night. Later skeptical research identifies the signal as a type carried by U.S. C-141 transports and reports that such beacons had sometimes been released over the nearby mountains. The public report says radiation checks were planned; it does not include results.

### The cable travels through Washington

The incident entered the American record through the U.S. Defense Attaché Office in Tehran. A message dated September 22 was distributed through military and intelligence channels, including the Joint Chiefs of Staff, Department of State, CIA, NSA, White House, and senior commands in Europe and the Middle East. A later Defense Intelligence Agency evaluation called the report outstanding and listed features it considered valuable for study: multiple viewpoints, trained witnesses, a reported radar contact, and similar electromagnetic effects. Wide distribution shows that the report circulated; it does not by itself show that every recipient opened a separate investigation or accepted an extraordinary explanation.

![First scanned page of Captain Henry S. Shields’s U.S. Air Force article Now You See It, Now You Don’t, with crossed-out CONFIDENTIAL markings.](<https://uap.fun/tehran-1976-miji-page-1.jpg>)

The opening page of Capt. Henry S. Shields’s later U.S. Air Force article “Now You See It, Now You Don’t,” summarizing the Tehran encounter. It bears crossed-out CONFIDENTIAL markings and was declassified in 1981. The article is a military retelling, not the original operational message. United States Air Force; public domain in the United States, via Wikimedia Commons.

[Image source](<https://commons.wikimedia.org/wiki/File:Tehran_ufo_1976_1.jpg>)

### The pilot returns to the story

Jafari continued to describe the encounter after leaving active service, including at a 2007 National Press Club event in Washington. His later account supplied names, personal impressions, and a more vivid sense of the cockpit than the terse 1976 cable. It also arrived decades after the event. That makes it valuable as witness testimony and cultural history while requiring the usual separation between near-contemporaneous documentation and later memory. The case’s reputation grew from their overlap: the old message supplies a timed sequence, while Jafari gives the sequence a human voice.

### Jupiter, meteors, and unreliable electronics

The strongest conventional reading does not depend on one explanation for every reported light. Philip J. Klass and later Brian Dunning argued that Jupiter could account for at least part of the persistent star-like object, while meteors could account for short, fast lights. Dunning’s review cites contractor interviews alleging a history of intermittent electrical trouble in the second F-4 and uncertainty about whether the first aircraft was ever presented for repair. It also notes that a radar set needing adjustment or operating in manual track could complicate the reported lock. Those claims are later investigative testimony rather than surviving Iranian maintenance logs, but they offer a serious alternative to deliberate electronic interference.

### Why Tehran still holds the night

The public record preserves a compelling encounter without resolving it into a single object. It combines civilian calls, military crews, a reported radar return, communications failures, and an urgent weapons decision. Yet it lacks raw radar data, complete maintenance records, identified physical debris, photographs of the lights, and the promised follow-up test results. The mystery survives in that tension. Something prompted two intercepts over a capital city, and the people involved experienced it as immediate and dangerous. What the lights were—and whether all of the reported effects shared one cause—remains beyond what the available documents can establish.

## The evidence

### What the official message establishes

The declassified message establishes that the U.S. defense attaché system received and circulated an account of two Iranian F-4 intercepts, a radar lock reported by the second crew, temporary systems failures, additional lights, and a daylight search. Its reporting officer states that the information came through conversation with a sub-source who was an Iranian pilot. The cable is therefore a near-contemporaneous official record of what was reported, not a sensor log and not a transcript of every participant.

### What later sources add

Later interviews identify participants and preserve details absent from the cable. Researcher Bruce Maccabee’s reconstruction draws on interviews with controller Hossein Pirouzi and American avionics technicians; Dunning’s skeptical review relies on other contractor recollections and Klass’s investigation. Their conclusions conflict, particularly over the aircraft’s maintenance history. Without the underlying maintenance records and complete interview files, those later claims should be attributed rather than treated as settled fact.

### Classification is not confirmation

The document trail is authentic, and a later Air Force article carried classification markings before its release. Classification and wide routing show that the information moved through protected military channels. They do not identify the lights or prove hostile control of the aircraft systems. The available evidence supports the classification “unresolved in the public record,” not an extraterrestrial conclusion.

## Timeline

- **18 SEP 1976 · LATE NIGHT:** Residents in Tehran’s Shemiran district begin reporting a brilliant airborne light; Mehrabad personnel and an Iranian Air Force officer look for themselves.
- **19 SEP · 01:30:** The first F-4 launches from Shahrokhi Air Base and reports losing instruments and communications near the light before turning away.
- **19 SEP · 01:40:** The second F-4 launches. Its crew reports a radar lock, colored lights, a rapidly approaching secondary light, and temporary loss of weapons control and communications.
- **19 SEP · BEFORE DAWN:** The second crew observes a light descending toward the ground, reports further interference near Mehrabad, and lands after the encounter.
- **19 SEP · DAYLIGHT:** A helicopter search finds no trace at the apparent landing point but detects an emergency-beacon signal near a house west of the site.
- **22–23 SEP 1976:** The U.S. Defense Attaché Office report is dated and relayed through Joint Chiefs, diplomatic, intelligence, and military channels.
- **AUG 1977:** The three-page message is released following a Freedom of Information Act appeal, bringing the official account into public research.
- **OCT 1978:** The U.S. Air Force Security Service periodical MIJI Quarterly publishes “Now You See It, Now You Don’t,” a narrative retelling later declassified in 1981.
- **12 NOV 2007:** Retired Gen. Parviz Jafari recounts the second intercept publicly at the National Press Club in Washington, D.C.

## Sources & interviews

- [Joint Chiefs of Staff report concerning the sighting of a UFO in Iran on 19 September 1976](<https://media.defense.gov/2021/Jul/13/2002761354/-1/-1/0/JOINT_CHIEFS_STAFF_REPORT.PDF>) — U.S. Defense Attaché Office, Tehran · September 22, 1976 · NSA FOIA release
- [Routing and Transmittal Slip, DIA summary, and U.S. Defense Attaché report](<https://www.nsa.gov/Press-Room/Digital-Media-Center/Document-Gallery/igphoto/2002761364/>) — Defense Intelligence Agency · Declassified records hosted by NSA
- [“Now You See It, Now You Don’t”](<https://www.nsa.gov/Helpful-Links/NSA-FOIA/Declassification-Transparency-Initiatives/FOIA-Reports-and-Releases/FOIA-Reports-and-Releases-List/igphoto/2002761355/>) — Capt. Henry S. Shields, U.S. Air Force · MIJI Quarterly · October 1978 · NSA FOIA release
- [1976 Tehran UFO incident](<https://en.wikipedia.org/wiki/1976_Tehran_UFO_incident>) — Wikipedia · Orientation and reference trail · Consulted September 16, 2026
- [UFO sightings in Iran](<https://en.wikipedia.org/wiki/UFO_sightings_in_Iran>) — Wikipedia · Related overview · Consulted September 16, 2026
- [Iranian Jet Case](<http://nicap.org/reports/760919iranianjetcase.pdf>) — Bruce Maccabee · 2006 reconstruction using witness and technician interviews · NICAP archive
- [The Tehran 1976 UFO](<https://skeptoid.com/episodes/315>) — Brian Dunning · Skeptoid \#315 · June 19, 2012 · Skeptical analysis
- [Tehran F-4 incident document and research directory](<https://nicap.org/CATEGORIES/03-EME_Cases/760919tehran_dir.htm>) — NICAP and Project 1947 · RADCAT case directory
- [First page of “Now You See It, Now You Don’t”](<https://commons.wikimedia.org/wiki/File:Tehran_ufo_1976_1.jpg>) — Capt. Henry S. Shields, United States Air Force · Public domain via Wikimedia Commons

## A note on evidence

Unidentified describes a limit of the available information. It doesn’t identify an origin.

[Next case file: The Belgian UFO Wave](<https://uap.fun/encounters/belgian-ufo-wave/>)