Evidence Explorer

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.

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

…s, an Air Traffic Control Specialist at the Anchorage ARTCC, detailing the incident involving Japan Airlines Flight 1628 on November 18, 1986, where the flight reported an unidentified object in close proximity.

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

…ity Assurance Specialist at the FAA, regarding 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 Carl E. Henley, an Air Traffic Control Specialist at the Anchorage ARTCC, regarding the radar observations related to Japan Airlines Flight 1628 on November 18, 1986.

…amuel J. Rich, an Air Traffic Control Specialist at the Anchorage ARTCC, detailing an incident involving aircraft JL 1628 on November 18, 1986, where the pilot reported seeing an unidentified large aircraft with yellow and white lights.

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.

…ns, an Air Traffic Control Specialist at the Anchorage ARTCC, detailing an incident involving Japan Airlines Flight 1628 on November 18, 1986, where the flight reported an unidentified object in proximity.

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

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

This document appears to be a technical log or report detailing various measurements and data points, possibly related to radar or tracking systems. The data includes timestamps, coordinates, and other metrics, 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, 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.