627 matching evidence objects
Ranked by relevance
Matching “military reports” across titles, summaries, and full OCR text.
100% match
…ng radar contact and visibility issues during flight. The conversation indicates a potential unidentified aerial phenomenon (UAP) situation, as the flight crew reports no radar replies and mentions traffic being extinguished.
100% match
…m Manfred F. Keller, an Automations Specialist at the FAA, regarding an incident involving aircraft JL1628 near Fairbanks, Alaska, on November 18, 1986. Keller reports that he analyzed radar data but found no indications of other traffic in the area.
100% match
…ity Assurance Specialist at the FAA, regarding the radar data analysis of the JL1628 incident that occurred on November 18, 1986, near Fairbanks, Alaska. Wylie reports that he found no unusual radar targets associated with the sighting.
100% match
This document contains beacon target reports from November 18, 1986, detailing various radar readings and subsystem totals related to unidentified aerial phenomena.
100% match
The document appears to be a technical report related to beacon target data, possibly from a radar or tracking system, with timestamps and various subsystem readings. The text is fragmented and contains numerous errors, making it difficult to interpret fully.
100% match
This document appears to be a technical report or data log related to unidentified aerial phenomena (UAP), containing various time-stamped entries and measurements, possibly from radar or tracking systems. The content is heavily encoded and lacks clear context, making it difficult to interpret without additional information.
100% match
This document appears to be a technical report or data log related to beacon systems, possibly involving radar or tracking systems. The text includes various numerical data points, likely representing measurements or operational parameters, but lacks clear context or coherent narrative.
100% match
This document appears to be a technical report or data log related to beacon systems, possibly involving radar or tracking systems. The content includes various numerical data points and references to subsystems, but lacks clear context or coherent narrative.
100% match
This document appears to be a technical report containing various data points related to unidentified aerial phenomena (UAP), including ranges, altitudes, and possibly radar tracking information. The text is heavily fragmented and includes numerous numerical values without clear context.
100% match
This document appears to be a report containing various data points related to unidentified aerial phenomena (UAP) observations, including coordinates, time ranges, and other technical specifications.
100% match
The document contains beacon target reports from November 18, 1986, detailing various radar readings and subsystem data related to unidentified aerial phenomena.
100% match
The document is a beacon target report detailing various radar readings and parameters from an unidentified aerial phenomenon observed on November 18, 1986. It includes timestamps, range, altitude, and other technical data related to the targets detected.
100% match
This document contains beacon target reports from November 18, 1986, detailing various radar readings and target identifications. The data includes timestamps, coordinates, and various metrics related to the detected targets.
100% match
This document appears to be a technical report or data log related to beacon signals, possibly from radar or tracking systems. The content includes various numerical data points and references to different subsystems, but lacks coherent narrative or context.
100% match
The document appears to be a technical report containing various data points and metrics related to unidentified aerial phenomena (UAP). The text includes numerous references to 'SUESYS' and 'SUBSYS', suggesting a structured data format, possibly related to radar or tracking systems. However, the content is largely garbled and lacks coherent context.
100% match
This document appears to be a technical report related to beacon systems, possibly involving radar or tracking data. The text includes various numerical data points and references to subsystems, but lacks coherent context or clear findings due to its fragmented nature.
100% match
The document appears to be a technical report with various data points, possibly related to radar or tracking systems. The text includes numerous numerical values and codes, but lacks coherent context or clear conclusions regarding UAP/UFO phenomena.
100% match
The document appears to be a technical report related to beacon and subsystem data, possibly from radar or tracking systems. The text includes various time stamps and mode C totals, indicating measurements or readings taken at specific intervals.
100% match
A cargo aircraft captain reported seeing irregular pulsating lights that he believed to be a UFO while flying over Alaska. The FAA concluded that the lights were likely caused by atmospheric conditions.
100% match
Captain Terauchi of Japan Airlines Flight #628 reported sightings of unusual lights while flying over Alaska on January 11, 1987. The lights appeared at different positions relative to the aircraft and were later attributed to village lights obscured by atmospheric conditions.