Evidence Explorer

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 describes the communication between the flight crew and air traffic control regarding unidentified traffic.

A cargo aircraft crew reported observing irregular pulsating lights and a large black object while flying over Alaska. The FAA concluded that the lights were likely caused by atmospheric conditions.

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.

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

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.

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

The document appears to be a technical report containing numerical data and system readings, possibly related to radar or tracking systems. The text is fragmented and lacks clear context, making it difficult to ascertain specific details about UAP/UFO sightings or incidents.

The document appears to be a fragmented and unclear record, possibly related to a technical analysis or report involving numerical data and measurements. The content lacks coherent context and is difficult to interpret.