Blue Disclosure

Tehran 1976: two F-4s and the limits of the record

  • ID: BD-1976-THR
  • Date / time: 1976-09-19 · Approx. 00:30 onward, local time as reported; takeoffs 01:30 and 01:40
  • Jurisdiction: IRN
  • Classification: UNCLASSIFIED / PUBLIC RELEASE (source material originally CONFIDENTIAL)
  • Shape: Unresolved; rectangular arrangement of flashing lights reported, not a verified object outline
  • Duration: Exact duration not established; multiple reports and two sorties during the early morning
  • Location: Tehran region, Iran; Shemiran, airspace north and south of the city, and Mehrabad approach
  • Status: ARCHIVED
  • Sensors: VISUAL · REPORTED AIRBORNE RADAR
  • Evidence level: CONTEMPORARY MILITARY REPORT / REPORTED VISUAL AND AIRBORNE RADAR

Summary

In the early hours of 19 September 1976, Iranian civilians reported unusual lights over Tehran. Two Imperial Iranian Air Force F-4s were sent to investigate. A U.S. defense attaché report records the crews' accounts of a bright object, an airborne radar lock and temporary equipment failures. The surviving documents establish that these events were reported, not what caused them. No extraterrestrial origin is demonstrated.

Analyst notes

A night interception, recorded days later

At about 00:30 on 19 September, according to the U.S. report, the Iranian Air Force command post received four calls from residents of Tehran's Shemiran area. Descriptions varied: some callers described a bird-like object, others a helicopter with a light. Brigadier General Yousefi initially suggested stars, then looked outside and saw something resembling a star but larger and brighter. He ordered an F-4 from Shahrokhi Air Force Base to investigate. [1, 2]

The cable places the first takeoff at 01:30. It says that, as the aircraft approached to an estimated range of 25 nautical miles, the crew lost instrumentation and UHF and intercom communications. The aircraft turned away, after which the systems reportedly recovered. A second F-4 launched at 01:40. Its rear-seat crew member reported a radar lock at 27 nautical miles; the range then decreased to 25 nautical miles before the return appeared to move away and remain at that distance. [1, 2]

What the second crew reported

The report compares the strength of the radar return with that of a Boeing 707 tanker. That comparison is not a measurement of the object's physical size. Its visual dimensions were difficult to judge because of its brightness. The crew described rapidly flashing blue, green, red and orange lights arranged in a rectangular pattern. The pattern of lights should not be confused with a confirmed rectangular airframe. [1, 2]

As the pursuit continued south of Tehran, the crew reported another bright object apparently emerging from the main light and heading toward the F-4. The pilot attempted to fire an AIM-9 missile, but the weapons control panel and communications reportedly failed. The cable describes an evasive turn and dive, followed by the smaller light apparently returning to the main one. It does not report a missile launch. [1, 2]

The crew then described another light descending toward the ground and illuminating an area estimated at two to three kilometres across. During the subsequent approach to Mehrabad, the F-4 reported further communication and navigation problems. An approaching civilian airliner also reported communication failure in the same vicinity, but no visual sighting. A daylight helicopter visit found nothing at the presumed landing spot. A beeper signal and nearby residents' account of a loud noise and bright light were also recorded. These details do not establish a landing or the recovery of an unknown vehicle. [1, 2]

A real document is not a verified explanation

The U.S. Defense Attaché Office's message, dated 23 September 1976, is an intelligence information report, not a published technical investigation. Its source comment says the information came through a source speaking with a sub-source and one of the F-4 pilots. The cable does not name the aircrew. Its distribution to senior U.S. offices documents circulation, not agreement with a particular interpretation. [2]

An accompanying Defense Intelligence Agency evaluation rates the information highly and cites multiple witnesses, a reported radar correlation and reported electromagnetic effects. Those ratings concern the information submitted for assessment. They do not independently demonstrate that an external object caused the aircraft failures, and they do not identify the light. [2]

The USAF narrative 'Now You See It, Now You Don't' retells the encounter. It should not be counted as a separate sensor record or an independent sighting. The source set reviewed here contains no original radar recording, independently testable flight-data record or recovered material that would establish the nature of the reported object. [1-3]

Conventional explanations remain part of the file

Skeptical accounts have proposed Jupiter for at least some of the bright-light observations, meteors for some rapidly moving or descending lights, and equipment faults or radar interpretation errors for the aircraft reports. These are proposed explanations, not conclusions established by the cable. A bright planet alone would not explain every reported element; equally, an unexplained element is not evidence of an extraterrestrial vehicle. [4]

The maintenance evidence is disputed. Brian Dunning's skeptical account, drawing on Philip J. Klass's inquiries, describes a history of electrical problems and possible radar misinterpretation. Bruce Maccabee's reconstruction instead cites technicians who said that later checks found the electronics operating normally. These retrospective accounts cannot be treated as a single agreed maintenance finding. [4, 5]

Assessment

Tehran belongs in an archive because a contemporary military report and a DIA evaluation preserve a consequential account of a night interception. They support confidence that the incident was reported through official channels. They provide much less certainty about the physical event behind the descriptions. The case remains unidentified in the reviewed record, with disputed conventional explanations and no demonstrated extraordinary origin. We document the report without upgrading its claims into established physical facts.

Editorial score: 3/5 for the documentary account only, not for alien origin. The score is not a scientific measurement. The exact witness total and encounter coordinates are not established.

Sources

  1. Joint Chiefs of Staff report, 23 September 1976 - https://media.defense.gov/2021/Jul/13/2002761354/-1/-1/0/JOINT_CHIEFS_STAFF_REPORT.PDF Primary source, 3-page scan. Read all pages visually; original formatting and reported distances checked.

  2. Routing slip, DIA evaluation and U.S. Defense Attaché report - https://media.defense.gov/2021/Jul/13/2002761364/-1/-1/0/ROUTING_SLIP_UFO_IRAN.PDF Primary source, 6-page package. Read all pages visually, including the source comment on page 6. Routing slip dated 8 December 1978, not the incident date.

  3. Now You See It, Now You Don't - https://media.defense.gov/2021/Jul/13/2002761355/-1/-1/0/NOW_YOU_SEE.PDF Later USAF narrative, not an independent encounter record.

  4. The Tehran 1976 UFO, 19 June 2012 - https://skeptoid.com/episodes/315 Skeptical secondary analysis. Used for attributed conventional hypotheses, not to overwrite the primary report.

  5. Iranian Jet Case, September 19, 1976 - https://www.nicap.org/reports/760919_tehran_Maccabee_report.pdf Research reconstruction drawing on interviews and contemporary press. Used for the conflicting retrospective maintenance account; its speculative conclusion is not adopted.

  6. The Vault Files: 1976 Iran Incident - https://www.theblackvault.com/casefiles/the-1976-iran-incident/ Secondary document history and context. The official NSA scans, rather than this synthesis, govern the narrative.

Source reliability

3/5. An ordinal source assessment, not a probability or a conclusion about the event’s origin.

Coordinates

  • Latitude: 35.6892
  • Longitude: 51.389

Sources

  • U.S. Defense Attaché Office information report IR 6 846 0139 76, 23 September 1976; JCS / NSA scan
  • DIA evaluation and routing-slip package; overlapping report, not independent sensor evidence
  • Brian Dunning, Skeptoid (2012), attributed conventional explanations
  • Bruce Maccabee, reconstruction; conflicting retrospective maintenance account

Documents

ROUTING AND TRANSMITTAL SLIP — UFO IRAN

Routing and Transmittal Slip (Optional Form 41) from Louis E. Foster, ROS-3A, DIA, dated 8 Dec 78, remark 'Per telecon'. Part of the 2021 release on the Tehran 1976 incident.

REPORTED UFO SIGHTING — TEHRAN, IRAN, 19 SEPTEMBER 1976

Excerpted transcription of the USDAO Tehran message forwarding information on the 19 September 1976 UFO sighting in Iran. Transcribed from a low-quality scan; omissions marked [...].

Timeline

Approx. 00:30 local: · Command post receives four civilian calls; Yousefi observes a bright light and orders an interception, according to the cable.

01:30 local: · First F-4 takes off; the crew later reports instrumentation and communication failures on approach and recovery after turning away.

01:40 local: · Second F-4 takes off; the cable records a reported radar lock and subsequent encounter with smaller lights and equipment failures.

Later that morning: · Mehrabad approach reports include further interference and a separate civilian airliner's communication failure without a visual sighting.

Daylight, date not separately specified: · Helicopter checks the presumed landing area; nothing is noticed at the reported spot. A beeper signal and nearby residents' account are recorded.

23 September 1976: · U.S. Defense Attaché Office transmits information report IR 6 846 0139 76.