Two Imperial Iranian Air Force F-4s were launched after reports of a brilliant object over Tehran. The second crew reported an airborne radar lock. Both intercepts were associated with reported communications or instrument problems. The surviving US defence record is genuine. The object is not identified.
The US defence attaché report says the Imperial Iranian Air Force command post received four calls from citizens in the Shemiran area of Tehran shortly after midnight. Brigadier General Yousefi looked for himself, saw a brilliant object and ordered an intercept.
The episode then escalated in steps. The first aircraft reported system loss and withdrew. The second acquired a radar return and pressed closer. A smaller light was reported to separate from the main object. Then the weapons-control panel and communications failed.
Civilians report a strange brilliant object over the city.
Instrumentation and communications reportedly fail at about 25 nautical miles.
The second crew reports a lock at 27 nautical miles, 12 o'clock high.
A smaller bright object is reported moving away from the main light toward the F-4.
The crew attempts to employ an AIM-9; weapons control and communications reportedly fail.
Mehrabad Airport was one of the aviation nodes involved in the wider reporting picture. The 1973 image helps anchor the story in the Tehran that existed before the revolution — not in the mythology the case later accumulated.
The NSA hosts the surviving US Defense Attaché/DIA package and a Joint Chiefs copy concerning the 19 September 1976 sighting. That gives Tehran a documentary foundation much stronger than a case reconstructed solely from later interviews.
But the document is still a report of reported events. It proves the military response was documented at the time. It does not substitute for the missing radar tape, maintenance records or cockpit telemetry.
OPEN THE OFFICIAL REPORT →The second F-4's back-seater reportedly acquired a radar lock at 27 nautical miles, 12 o'clock high. The target's size on the scope was described in the US report as comparable to a 707 tanker. As the range decreased to 25 nautical miles, the object reportedly moved away fast enough to preserve that separation.
That is an unusually important claim. But it remains one step removed from direct sensor evidence: the cable tells us what the crew reported the radar displayed. The underlying radar recording does not survive in the package.
There is no surviving raw radar image to reproduce. So the flagship deliberately uses the document and the reported figures, not an invented glowing scope that could be mistaken for evidence.
The first F-4 reportedly lost instrumentation and communications while closing on the object. The pilot broke off.
During the second intercept, after a smaller object was reported approaching, the pilot attempted an AIM-9 engagement. The weapons-control panel and communications reportedly failed.
If the failures were caused by the phenomenon, Tehran becomes an extraordinary electronic-interference case. If they were ordinary F-4 faults occurring during a confusing night interception, much of the mystery contracts.
The surviving record cannot decide the question. The maintenance logs and instrument records needed to test causation are precisely what we do not have.
The contemporaneous US report names Yousefi as the senior officer who looked for himself, saw the bright object and ordered an F-4 scramble.
Later public testimony identifies Jafari as the pilot of the second F-4. His later recollections are useful but remain distinct from the anonymous crew description in the 1976 cable.
The US Defense Attaché in Tehran is named in the surviving report. The incident was then circulated through American defence and intelligence channels.
The opening object may have been astronomical. The report says Yousefi saw something similar to a star, but larger and brighter. A bright planet can produce that first impression. Meteors or other ordinary lights may also account for brief moving or descending elements.
Aircraft faults are the strongest conventional challenge to the systems narrative. F-4 avionics could fail. A malfunction occurring while closing on an unidentified light would naturally feel connected to the encounter.
But “Jupiter” does not automatically reproduce a radar lock, and “equipment fault” does not establish why two intercept narratives contained proximity-linked system problems. Those pieces need to be tested individually.
Potentially strong for the initial brilliant star-like visual. It does not by itself generate an airborne radar return or aircraft systems failures.
Potentially strong for instrument and communications loss. The key question is whether the timing with proximity was causal or coincidental.
Could contribute to short-lived moving or descending lights. They do not naturally reproduce the full second-intercept account.
The message was circulated through senior defence and intelligence channels and survives in declassified files. That proves the event was reported and judged worth forwarding. It does not mean DIA, NSA or the Joint Chiefs independently verified an exotic craft.
The most useful contribution would be something that lets the 1976 report be tested rather than merely retold.
Do not submit classified, restricted, operationally sensitive or otherwise protected information.
Tehran remains a major military UAP case because the extraordinary sequence is not solely a late story. A contemporary US defence report records civilian calls, two fighter intercepts, a radar lock during the second encounter, repeated system failures and a smaller light apparently separating from the primary object.
That is substantial.
It is also not the same as possessing raw sensor data. The cable relays Iranian reporting. The radar tape, maintenance records and telemetry that could establish whether the failures were genuinely proximity-linked are absent. No authenticated image of the object survives.
A bright astronomical object may explain the opening visual. Equipment faults may explain some or all of the electronic effects. Other ordinary lights may explain individual parts of the sequence. But no single conventional reconstruction has been demonstrated from the surviving primary evidence to reproduce the whole second intercept.
The strongest conclusion is narrower than the legend and more interesting than a dismissal:
On 19 September 1976, two Iranian F-4 crews were sent after an unidentified aerial report. The second crew reported radar contact and an aborted weapons attempt amid systems failures. The United States documented the incident soon afterwards. The target was never identified in the surviving record, and the evidence needed to decide whether the failures were caused by it is missing.
In the early hours of 19 September 1976, residents in Tehran reported a bright object in the sky. Iranian Air Force pilot Parviz Jafari was sent to investigate and described a luminous object that appeared to change position. A second F-4 crew also became involved. The case later drew attention because a U.S. Defense Intelligence Agency report summarized the incident and described radar, visual, and equipment-related claims.
The record is not a single uninterrupted observation. Pilots were operating at night, the object was seen at different distances, and the reported loss of weapons or communications capability is part of a contested account rather than independently verified physical evidence. The DIA report establishes that the event was considered worthy of intelligence reporting; it does not prove the object’s origin.
Tehran remains important because the witnesses were military pilots and the event produced an official written summary. The strongest analysis keeps pilot testimony, radar information, reported instrument effects, and later retellings in separate categories.
Residents in Tehran report a bright object, prompting military attention during the night.
An Iranian pilot is directed toward the object and describes a bright target with unusual movement.
A second aircraft becomes involved, and the reported encounter includes disputed claims about weapons and instrument effects.
A U.S. Defense Intelligence Agency report summarizes the incident and preserves its military significance.
Compare with Nimitz for another military encounter where pilot testimony, sensors and later interpretation form separate evidence layers.
US Defense Attaché / DIA routing package, 19 September 1976 sighting (declassified, hosted by NSA) · Joint Chiefs of Staff copy of the Tehran report · DIA Intelligence Report (PDF) — 1976 Iran incident (Black Vault) · NSA — U.S. Government and the Iran Case · Joint Chiefs of Staff Report (Black Vault) · Later public testimony of Parviz Jafari (second-intercept pilot)