Evidence Explorer

This document details a communication exchange between Japan Air flight 1628 and the Fairbanks FAA tower regarding unidentified traffic observed by the flight. The exchange indicates that the flight was deviating from its course due to an unidentified object, with no military aircraft reported in the area.

This document appears to be a transcript of radio communications involving Japan Air flight JL1628 and Anchorage Center, discussing traffic and flight instructions.

This document is a personnel statement from John L. Aarnink, an Air Traffic Control Specialist at the FAA, detailing his observations during the Japan Airlines Flight 1628 incident on November 18, 1986, near Fairbanks, Alaska.

This document is a personnel statement from 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.

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

This document is a personnel statement from John L. Aarnink, an Air Traffic Control Specialist at the Anchorage ARTCC, detailing his observations during the Japan Airlines Flight 1628 incident on November 18, 1986.

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 is a personnel statement from Anthony M. Wylie, a Quality Assurance Specialist at the Federal Aviation Administration, regarding the radar data analysis of an incident involving flight JL1628 near Fairbanks, Alaska, on November 18, 1986.

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

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

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

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.

…time, altitude, and coordinates. The text includes numerous entries with numerical data that may pertain to unidentified aerial phenomena (UAP) or other aerial targets.

…ial phenomena (UAP) observed on November 19, 1986. The report includes various measurements such as range, altitude, and other parameters associated with radar targets.

This document appears to be a technical report related to radar data analysis, possibly concerning unidentified aerial phenomena (UAP). It includes various subsystems and total counts, but the text is heavily corrupted and lacks coherent context.

This document contains radar data from a military exercise dated November 18, 1986, detailing various beacon targets and their corresponding altitudes, distances, and other metrics.

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.

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.