Evidence Explorer

This document appears to be a transcript of communication between pilots and air traffic control regarding an unidentified flying object (UFO) sighting. The conversation includes instructions for altitude adjustments and the involvement of military aircraft to investigate the sighting.

This document contains operational details related to air traffic control and military coordination in the context of air defense, specifically referencing NORAD and FAA operations.

This document is a personnel statement from Carl E. Henley, an Air Traffic Control Specialist at the Anchorage ARTCC, detailing an incident involving aircraft JL1628 on November 18, 1986. The report describes the communication between the aircraft and air traffic control regarding unidentified traffic in the vicinity.

This document is a personnel statement from an Air Traffic Control Specialist at the FAA regarding an incident involving aircraft JL1628 on November 18, 1986. The report details the communication between the aircraft and air traffic control, including the sighting of an unidentified object with white and yellow strobes.

This document appears to be a fragmented record related to unidentified aerial phenomena (UAP) from the National Archives, possibly detailing radar data or flight information from a specific date in 1986.

This document contains beacon target reports from November 18, 1986, detailing various radar readings and subsystem totals related to unidentified aerial phenomena.

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.

The document appears to be a technical report or data log related to aircraft tracking and radar systems, possibly involving unidentified aerial phenomena (UAP). It contains various timestamps, numerical data, and references to aircraft identifiers and control systems.

…nt appears to be a technical report or data log related to a beacon or surveillance system, containing various numerical values and codes, likely pertaining to radar or tracking data.

…rs 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.

This document contains beacon target reports from November 18, 1946, detailing various radar readings and system statuses. The data includes time stamps, altitudes, and other metrics related to unidentified aerial phenomena.

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.

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.

…ument 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.

This document appears to be a technical report or log related to radar data, possibly concerning unidentified aerial phenomena (UAP) from the early 1950s. The data includes timestamps, coordinates, and various system readings, but is largely obscured by formatting issues.

The document appears to be a technical report with time-stamped data related to subsystems and total measurements, possibly from a radar or monitoring system. The content is fragmented and lacks clear context.

This document appears to be a technical report or log related to radar data, possibly involving unidentified aerial phenomena (UAP). It contains various readings and metrics, but the text is largely garbled and lacks clear context.

This document appears to be a technical report or log related to radar or tracking systems, detailing various readings and subsystems over a period of time. The data includes timestamps, coordinates, and system statuses, but lacks clear context or explanation.

…nical report or log detailing various measurements and data points related to an unidentified aerial phenomenon, including coordinates, altitudes, and possibly radar readings.

This document appears to be a technical report or data log related to radar or tracking systems, detailing various metrics and readings over a specified time range. The content includes numerical data, possibly indicating object positions, velocities, and operational modes, but lacks clear context or coherent narrative.