UAPRADUAP Research and Disclosure
Member Area

Tehran UFO Incident

·

Case Summary

In the early hours of 19 September 1976, civilian callers and Tehran’s control tower reported a brilliant object over northern Tehran. The Imperial Iranian Air Force scrambled two F-4 Phantom II interceptors from Shahrokhi Air Base.

Both crews reported temporary systems and communications anomalies as they closed. The second F-4, flown by Parviz Jafari with Jalal Damirian, reported a radar lock, rapidly flashing multi-coloured lights, apparent separation of smaller objects and weapons-system failure as it prepared to fire.

A U.S. Defense Intelligence Agency report summarised the Iranian debrief and called it an outstanding multi-witness, multi-sensor report. No object, raw radar tape or cockpit recording is publicly available, so the event’s identity remains unresolved.

Witnesses

Parviz JafariOther Tehran pilots and controllers

The 19 September 1976 Record

Initial reports and first intercept

At around 00:30, the IIAF received several reports from Shemiran. Tower personnel confirmed an intense light; a first F-4 launched around 01:30. The crew reported failure of instruments and communications at about 25 nautical miles, with recovery after turning away.

Second intercept

Jafari and Damirian launched around 01:40 and reported radar lock near 27 nautical miles, with a return compared to a large tanker. They described extremely bright flashing red, green, blue and orange lights. A smaller object appeared to detach and approach; weapons controls and communications reportedly failed before recovering after evasive action.

Official aftermath

Iranian personnel debriefed the crews with U.S. attendance. DIA distributed a summary to senior U.S. addressees. No recovery occurred and later public accounts must remain secondary to the 1976 record.

What the record establishes

  • Civilian, tower and military personnel reported a brilliant object.
  • Two F-4s intercepted and reported temporary system anomalies.
  • The second crew reported a radar return and visual sequence.
  • No publicly available raw sensor or recovered-object record identifies the cause.

How the Tehran Story Developed

The Iranian debrief and DIA summary are the primary record. Later accounts add claims of satellite detection, a “dogfight” and other details that require independent source support. The responsible approach is to rank the original reporting above later elaboration while testing astronomical, conventional-light and avionics explanations against the whole sequence.

About 00:30

Civilian calls and tower observation trigger an IIAF response.

About 01:30

First F-4 reports systems failure on closure and recovery after break-off.

About 01:40

Second F-4 reports radar lock, lights, apparent smaller objects and further anomalies.

After the interception, September 1976

Iranian personnel are debriefed and a report of the encounter circulates through US intelligence channels.

Evidence, Documents and Physical Record

Witness base

Airborne and ground observers

Calls, tower observation, two aircrews and controllers make the case more than a single-pilot account.

Sensor claim

Reported radar lock

The Jafari/Damirian debrief describes a large return, but public access does not include the raw radar material.

Aircraft effects

Temporary anomalies

Failures were reported on closure and recovery after manoeuvre; mechanism and independent logging remain unknown.

Official record

DIA evaluated the report seriously

The assessment documents official interest and source reliability; it is not an identification of the object.

Evidence Assessment & Hypotheses

Tehran's importance rests on the reported relationship between an intercept, radar contact and temporary aircraft systems failures. The intelligence documentation preserves a more substantial sequence than an isolated light report, yet the absence of raw sensor data prevents independent reconstruction of the associations. A radar return compared with a large aircraft is significant testimony about the instrument display; it is not a measured size or a recoverable track available for present analysis.

The reported recovery of systems after the interceptors broke off makes the closure correlation worth examining. Establishing interference from the light would require aircraft diagnostics and timing sufficient to distinguish it from equipment malfunction, cockpit workload or other electromagnetic conditions. Conventional failures cannot be assumed simply to dispose of the account, and repetition across two aircraft increases the need for a specific explanation. Conversely, temporal association does not identify the source or mechanism of the failures.

A bright astronomical source could address visual brilliance and colour under suitable conditions but would leave the reported radar and separation sequence to be explained. Aircraft or pyrotechnic proposals likewise require a fit to the observations rather than generic plausibility. The DIA's favourable evaluation indicates that the report merited attention; it does not settle these physical questions. The public record supports a consequential military encounter report with unresolved correlations, rather than a verified object whose exceptional performance or origin has been established.

Open Questions and Next Steps

Recovering original technical material and reconstructing the sky and aircraft systems are the clearest routes to narrowing the case.

Question

Do raw radar or cockpit records survive?

Answer

Their release would permit independent kinematic and systems analysis beyond debrief summaries.

Question

What was visible over Tehran?

Answer

Astronomical and meteorological reconstruction can test light-source alternatives without resolving radar by assumption.

Question

Are the failures technically reproducible?

Answer

Period F-4 maintenance and avionics literature could test ordinary failure modes under the reported intercept conditions.

1. Seek raw records

Search Iranian, U.S. and FOIA holdings for radar, IFF, CVR and detailed flight paths.

2. Rebuild conditions

Model the night sky, weather, aircraft traffic and intercept geometry.

3. Compare testimony

Align Jafari’s 1976 debrief with later public statements and supporting witnesses.

Witness Deep Dives

Review the airborne record alongside controllers, the first crew and civilian reports rather than relying only on later retellings.

Parviz JafariOther Tehran pilots and controllers

Source Library

The 1976 debrief and intelligence material outrank later expanded accounts.

Tier 1 Contemporary / Primary

Tier 2 Government / Archival

Tier 3 Historical / Critical

Further references and records

These bibliographic references and record descriptions do not have a direct document link here. Where the discussion relies on a later account of a record, the linked author remains the source for that account.

  • Iranian pilot/controller debrief and the recorded civilian/tower reports.
  • Defense Intelligence Agency evaluation and related JCS distribution of the Tehran report
  • Contemporary Iranian aircrew debriefs (Jafari and others)
  • Control-tower and civilian report summaries
  • Iranian Air Force and U.S. assistance/attaché material, if recoverable.
  • Technical analysis of astronomical and avionics-failure alternatives.
  • Jafari’s later public testimony—continuity evidence, secondary to 1976 debriefs.
  • Claims of definitive non-human technology—claim history, not confirmation.