Evidence Explorer

This document is a personnel statement from Joseph Rollins, an Air Traffic Control Specialist at the FAA, detailing the incident involving Japan Airlines Flight 1628 on November 18, 1986, where the flight reported unidentified traffic north of Fairbanks, Alaska.

This document is a personnel statement from Joseph Rollins, an Air Traffic Control Specialist at the Anchorage ARTCC, detailing the incident involving Japan Airlines Flight 1628 on November 18, 1986. The report outlines the communication between the flight and air traffic control regarding unidentified traffic.

This document is a personnel statement from an FAA employee regarding an incident involving aircraft JL1628 near Fairbanks, Alaska, on November 18, 1986. The report indicates that the FAA could not find any radar indications of other aircraft in the area during the reported incident.

This document contains beacon target reports with various time stamps and associated data, likely related to unidentified aerial phenomena (UAP) tracking.

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.

The document appears to be a technical report containing various numerical data related to a tracking system, possibly associated with unidentified aerial phenomena (UAP). The text includes references to target reports, ranges, and modes, but lacks coherent context or detailed explanations.

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.

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

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

The document appears to be a technical report containing data logs from a radar system, possibly related to unidentified aerial phenomena (UAP). The logs include various metrics such as time, coordinates, and subsystem information, but the text is heavily corrupted and lacks clear context.

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

…nt appears to be a technical report detailing various parameters and readings from a radar system, possibly related to unidentified aerial phenomena (UAP). The data includes timestamps, altitude, and other metrics, but lacks clear context or explanation.

The document appears to be a technical report or data log related to radar tracking, possibly involving unidentified aerial phenomena (UAP). It includes various parameters such as time, coordinates, and modes of operation, but the text is largely garbled and lacks clear context.

The document appears to be a technical report or data log related to a system's performance metrics, possibly involving radar or tracking systems. It includes various subsystem readings and metrics but lacks clear context or explanation.

This document appears to contain technical data related to a tracking or monitoring system, possibly associated with UAP/UFO sightings, based on the context of the source.

The document appears to be a technical report or log related to unidentified aerial phenomena (UAP), containing various data points likely associated with radar or tracking systems. The text includes numerical values and codes that may represent coordinates, times, and other parameters relevant to UAP sightings or tracking.

The document appears to be a technical report containing numerical data related to unidentified aerial phenomena (UAP) observations, including coordinates, times, and possibly radar readings. The text is heavily corrupted and lacks coherent context.

…document appears to be a technical report or log detailing various measurements and readings related to an unidentified aerial vehicle (UAV) or phenomenon. The data includes timestamps, coordinates, and various parameters that suggest tracking or monitoring of aerial objects.