IRAN / 19 September 1976 as reported; individual times use the original message’s clock
Tehran, 1976: lights, interceptors and reported equipment failures
A declassified message describes bright lights and F-4 interceptions over Iran. The investigation separates reported observations, instrument claims and the records needed to establish a common physical cause.
Tehran and reported approach areas · Approximate orientation marker for the named locality, not an exact encounter, burial, ritual or excavation position.
Assessment: An official report of an unusual aerial episode is documented. The light’s identity and a common cause for all reported effects remain unestablished by these messages.
Investigation and inspector’s assessment
The mystery and the documented account
An NSA-hosted verbatim message forwards information about the 19 September 1976 incident. It describes civilian calls from Tehran’s Shemiran area, a bright object and launches of two F-4 aircraft. The account reports loss and restoration of instrumentation or communications during an approach and a radar lock during the second interception. A second NSA-hosted Joint Chiefs document contains related message material. These are preserved reports, not raw cockpit recordings or a continuous radar trace. Their overlap is documentary transmission, not two independent sensor detections supplied for inspection. [S1] [S2]
The question worth investigating
Can the visual observations, radar statements and equipment failures be matched in time and position from original logs? A report of temporal association does not establish that the observed light caused a failure.
Evidence, provenance and uncertainty
The scans contain typographic or OCR ambiguities and should be transcribed from the image. Distances and speeds are reported estimates with limited calibration context. The cited pages provide no complete maintenance history or original radar recording. Government custody does not turn every statement into a verified technical conclusion. [S1] [S2]
Inspector’s assessment
An official report of an unusual aerial episode is documented. The light’s identity and a common cause for all reported effects remain unestablished by these messages.
Next research and discriminating evidence
Transcribe each message version with line-level references. Preserve units and ambiguous abbreviations. Seek original flight, radar and maintenance records and compare their clocks before proposing causation. Check ordinary astronomical and aerial candidates against each specific bearing and time rather than using one label for the entire episode.
Documentary chronology
- About 00:30, 19 September 1976
The message describes calls reporting unusual lights. [S1]
- About 01:30
The first F-4 launch and reported instrument difficulties are described. [S1]
- About 01:40
The message describes a second launch and reported radar acquisition. [S1]
- 30 September 2026
Eklipsis compiles this English documentary investigation from the named sources. No field visit or new eyewitness interview is claimed.
Dates distinguish the event, the creation of a record and its later publication. Approximate dates remain approximate.
Evidence ledger
Documented in the named record
A declassified message records reported F-4 interceptions and instrument difficulties on 19 September 1976.
Not established by the selected evidence
The messages independently prove an extraterrestrial craft caused every reported equipment failure.
Editorial assessment; stated limits apply
An official report of an unusual aerial episode is documented. The light’s identity and a common cause for all reported effects remain unestablished by these messages.
Hypothesis review
Several observations and equipment issues with ordinary causes
Candidate framework
- Supporting considerations
- Reports combine different observers and systems.
- Limits and objections
- Each candidate needs a timed and technical match.
- Discriminating test
- Compare sky reconstruction and maintenance evidence with each observation.
One unusual physical source causing correlated effects
Open interpretation
- Supporting considerations
- The message describes effects during approaches.
- Limits and objections
- Association is reported without raw corroborating logs.
- Discriminating test
- Require synchronised sensor and technical records linking the same source to the failures.
Inspector’s next steps
Trace the earliest accessible record
For Tehran, 1976: lights, interceptors and reported equipment failures, record author or storyteller, collection date, language, translation, page and exact scope. Distinguish evidence of a story being told from evidence of its events. Note which full documents remain unavailable.
Investigate the central question
Transcribe each message version with line-level references. Preserve units and ambiguous abbreviations. Seek original flight, radar and maintenance records and compare their clocks before proposing causation. Check ordinary astronomical and aerial candidates against each specific bearing and time rather than using one label for the entire episode.
Compare explanations without merging evidence
Compare sky reconstruction and maintenance evidence with each observation. Require synchronised sensor and technical records linking the same source to the failures. Preserve contradictions and unsuccessful searches; proposed work remains unperformed.
These are proposed research tasks, not completed fieldwork or requests already sent to an archive.
Documents and source register
Original reports, scans, catalogue records and later analyses are identified separately. Alternate copies of the same document do not add independent evidence. Follow the named archive for full access information.
NSA archive — Verbatim wire message, Iran case
Preserves reported observations; not a raw radar or cockpit recording.
Language: en
Open original source ↗NSA archive — Joint Chiefs of Staff report
Overlapping transmission of the incident account; not independent corroboration.
Language: en
Open original source ↗Downloadable working files
The pack contains the English dossier, a structured case record, source register, chronology, evidence ledger, hypothesis comparison and inspector task sheet. Downloaded source documents, when available for redistribution, are identified in the pack manifest. Other documents remain direct source links.
- English dossier · Markdown
- Structured case · JSON
- Chronology · CSV
- Evidence ledger · CSV
- Hypothesis comparison · CSV
- Source register · CSV
- Inspector task sheet · Markdown
- File manifest and attribution · JSON
Eklipsis authored this synthesis and its working sheets. The original archives and researchers retain credit for their documents. This is a documentary investigation, not a claim that Eklipsis conducted the historical fieldwork.