Evidence Explorer

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

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

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

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.

This document appears to be a technical report or log related to radar data, possibly concerning unidentified aerial phenomena (UAP) from the early 1950s. The data includes timestamps, coordinates, and various system readings, but is largely obscured by formatting issues.

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.

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.