Evidence Explorer

This document appears to be a transcript or communication log involving Japan Air flight JL1628, detailing its request for descent and interactions with air traffic control.

This document appears to be a transcript of air traffic control communications involving Japan Air flight 1628 and its interaction with radar operators near Fairbanks, Alaska. The conversation indicates that the flight was deviating from its path and was being monitored for traffic.

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 appears to be a position log from the Anchorage Air Route Traffic Control Center dated November 18, 1986. The text is largely illegible and contains various references to FAA forms and procedures.

This document appears to be a position log from the Anchorage Air Route Traffic Control Center dated November 18, 1986. It includes references to various codes and personnel responsible for certain positions, but the text is largely garbled and lacks coherent information.

This document contains a series of beacon target reports from November 18, 1986, detailing various radar readings and observations related to unidentified aerial phenomena (UAP). The data includes timestamps, azimuth, range, and other technical specifications.

The document appears to be a technical report or data log related to unidentified aerial phenomena (UAP), containing various time-stamped entries and measurements. The content is heavily encoded and fragmented, making it difficult to extract coherent information.

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.

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.

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

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.

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

This document appears to be a technical report or log detailing various measurements and data points related to an unidentified aerial phenomenon, including coordinates, altitudes, and possibly radar readings.

The document appears to be a technical report or data log related to unidentified aerial phenomena (UAP), containing various numerical data points and system classifications. The text is heavily encoded and lacks clear context, making it difficult to interpret specific details.

This document appears to be a technical report or data log related to unidentified aerial phenomena (UAP) tracking, containing various numerical data points and system identifiers. The text is fragmented and lacks clear context, making it difficult to interpret the specific findings or implications.

…appears to be a technical report detailing various data points related to unidentified aerial phenomena (UAP) observations, including time stamps, coordinates, and various metrics such as speed and altitude.

This document appears to be a technical report or log related to unidentified aerial phenomena (UAP) tracking, detailing various measurements and system outputs over a specified time period. The data includes coordinates, altitudes, and system modes, but lacks clear context or interpretation.

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.