The Tehran Intercept, 1976

It began with a switchboard full of calls. On the night of September 19, 1976, at around half past ten, people across northern Tehran looked up at a large, brilliant, multicolored light hanging in the sky and started reporting it. The calls reached Mehrabad Airport and the control tower of the Imperial Iranian Air Force, and the question they raised was blunt: what is that, and why is it just sitting there?

The man who took the question seriously was General Nader Yousefi, the assistant deputy commander of operations at the Air Force command post in Tehran. He checked with Mehrabad's tower, then stepped onto his own balcony to look for himself. What he saw was far brighter and larger than any star, and he refused to treat it as one. Yousefi ordered a fighter scrambled to intercept, and he would later confirm the events through official channels.

The first F-4 Phantom II reached the light, and its pilot could see it plainly, an intense glow he could not resolve into anything familiar. Then, as he closed to roughly 25 nautical miles, the aircraft began to fail him. His communications went out. His navigation instruments went with them. A modern fighter was going deaf and blind in the exact direction of the thing it had been sent to identify. The pilot broke off the intercept, turned away, and as he opened the distance his instruments came back to life as if nothing had happened.

So they sent a second one. This F-4 was flown by Major Parviz Jafari, and unlike the first crew he managed to hold the object on his own radar, acquiring it at about 27 nautical miles with a return so large it read like a Boeing 707 tanker. Up close it was extraordinary to look at: an intense light that cycled through red, green, and blue-white, flashing so fast the colors seemed to run together.

Then the object did something no tanker does. As Jafari bore in, a smaller luminous object detached from the primary and accelerated straight at his aircraft. He reacted the way a fighter pilot is trained to react, moving to fire an AIM-9 Sidewinder at the incoming shape. In that instant his weapons control panel went dead, and his UHF and internal communications died with it. No missile left the rail. Jafari threw the jet into a hard evasive turn; the smaller object followed him briefly, then broke off and rejoined the larger one.

The night was not finished. A second smaller object separated from the primary and dropped fast toward the ground. Jafari and his back-seat weapons officer, First Lieutenant Jalal Damirian, watched it descend, light up a wide stretch of terrain below, and then appear to settle gently onto the surface or hover just above it, still glowing.

Here is where the Tehran encounter separates itself from a thousand other lights in the sky. It did not stay a story. It became a document. A United States Defense Intelligence Agency evaluation of the report judged it a model of its kind: the source reliable, the information confirmed by more than one means. In the evaluator's own words it was 'an outstanding report,' and 'a classic which meets all the criteria necessary for a valid study of the UFO phenomenon,' its significance graded high.

And then it was passed around. The report was distributed to the White House, the Secretary of State, the Joint Chiefs of Staff, the National Security Agency, and the CIA. The real circulation list ran wider still, reaching the individual service chiefs and U.S. commands in Europe and the Middle East. Whatever the object was, the account of it landed on some of the most powerful desks in the American government within weeks.

None of this depended on a single excitable witness. The Imperial Iranian Air Force acknowledged the incident officially, generating scramble orders, pilot debriefings, and radar tracking records through the ordinary chain of command, and inside Iranian military circles the event was discussed as a genuinely anomalous one that defied conventional explanation.

By 2007 Jafari had retired as a general, and on November 12 that year he walked into the National Press Club in Washington and told the story under his own name, alongside a lineup of other military and aviation officials describing their own encounters. He described an object that outclassed anything he knew how to fly: it held its distance no matter how hard he pushed his Phantom, it changed position as if acceleration meant nothing to it, and it released and reabsorbed the smaller objects he had watched come at him. His account is also set down in Leslie Kean's 2010 book, UFOs: Generals, Pilots, and Government Officials Go on the Record.

This is not a tale told once and dropped. Jafari held to the same account for decades, and the research file grades him a highly credible witness: a career military officer with extensive tactical aviation experience, trained to tell an aircraft from a planet, trained to stay calm under pressure, and with a professional reputation on the line.

Set the drama aside and look at just the electronics, because that is where the case gets genuinely hard to dismiss. Two separate fighters lost systems, and they lost them at the worst possible moments: the first as it closed to identify the object, the second at the precise instant it moved to fire. Both times, the systems came back once the aircraft opened the range. The research file reads that timing as the tell. A random malfunction does not wait politely for the trigger pull, and it does not heal itself the moment you retreat.

Follow the logic and it points somewhere uncomfortable. If the failures were real and targeted, then something over Tehran could reach out and switch off specific systems, weapons and radios, on specific aircraft, at a distance, in 1976, a capability no air force on Earth possessed. And because the systems recovered rather than burned out, the file argues it looks less like a destructive pulse and more like an active suppression field that simply stopped affecting the jets once they left its reach.

Tehran is not the only case with this fingerprint. Selective, unexplained failures of military hardware have been reported around other encounters with anomalous objects, from missile systems going offline at Malmstrom Air Force Base to the electronics interference described in the Nimitz Tic Tac encounter. The aviation researcher Richard Haines, in a 2001 NARCAP study co-authored with Dominique Weinstein, catalogued fifty-seven pilot reports of electromagnetic effects on aircraft systems. Tehran sits comfortably inside that pattern.

One tempting conclusion has to be ruled out before it takes hold. If something could selectively disable an American-built fighter's weapons, was it simply an American secret weapon, a black-project test flown against an ally to see what it could do? [CONTRADICTED]. The research file rejects this outright, and the reasons are strong: the electromagnetic effects hit U.S.-supplied F-4s, the DIA expressed genuine intelligence interest rather than quiet familiarity, and the report was pushed to the very top of the U.S. government. A nation does not run a secret weapons test against an allied air force flying its own jets, then act surprised in writing at the highest levels.

The research file weighs the usual candidates. Jupiter was bright and well placed in the sky that night, and it is the explanation most often reached for. A re-entering satellite can throw a bright, descending light. A distant conventional aircraft can be misjudged. But the file finds each one wanting on the same grounds: Jupiter is a fixed point of light that produces no radar return, does not move, releases nothing, and disables no instruments; no satellite re-entry was on record for that date and place; and the men chasing the object were trained interceptor pilots holding it on radar, not stargazers guessing at a smudge.

That leaves the single most popular explanation to face directly, and the file does not let it pass. The idea that the crews were simply confused by Jupiter is [INSUFFICIENT]. Jupiter does not paint a radar return the size of a 707, it does not flash red and green and blue-white, it does not shed smaller objects that chase a fighter, and it certainly does not reach into a cockpit and switch off the weapons. The planet, at best, explains one bright light seen from the ground. It explains none of the rest.

The morning after, a helicopter crew was sent to the area where the second object had seemed to come down. They reported picking up a beeping signal from an open patch of ground, but they recovered nothing, no wreckage, no scorch, no material. The signal has a plausible, on-record explanation the file leaves out: investigators later traced a beeper in that area to an emergency locator transmitter thrown from a C-141 transport aircraft, apparently shaken loose by turbulence on an unrelated flight. That resolves the beep. It does not resolve what two crews watched descend and glow on the ground, and with no physical trace ever recovered, the landing itself stays exactly where the file puts it: inconclusive.

The last open thread is what may still be sitting in a vault. It is entirely plausible that both American and Iranian intelligence gathered more on that night than has ever been released, signals intelligence, sensor data, records that would sharpen or shrink the whole case. Until any of it surfaces, this stays speculation, but it is the reason no one can honestly call the file closed.