Evidence Explorer

This document appears to be an index or table of contents for a collection of records related to a specific flight incident, including radar data and personnel statements.

This document details a communication from United Flight regarding Japan Airlines flight JL1628, indicating a lack of visual contact with other traffic and a subsequent radar review that did not confirm any nearby targets.

The document appears to be a fragmented record possibly related to a reconnaissance or tracking operation, with references to coordinates and time stamps. The context is unclear due to the incomplete nature of the text.

…pears to be a technical report or data sheet related to an unidentified aerial phenomenon, with various numerical values and codes that may pertain to radar or tracking systems.

This document appears to be a simulation report related to a flight tracking exercise involving Japan Air 1628, dated November 18, 1986. It includes specific details about the data entered into a display system for plotting the flight's trajectory.

This report details an incident involving two commercial aircraft observing unidentified lights in the vicinity of Stillwater, OK, on April 9, 2022. The lights were reported by the flight crews of UAL2330 and DAL309, both flying at high altitudes.

This document is a Skywatch Incident Report detailing multiple sightings of an unidentified aerial phenomenon by commercial aircraft on August 4, 2023.

…ght 69 and air traffic control regarding an unidentified flying object (UFO) observed near Japan Air Flight 1628. The conversation highlights the difficulty in tracking the object and the lack of visual confirmation from the pilots.

This document is a personnel statement from Anthony M. Wylie, a Quality Assurance Specialist at the FAA, regarding the JL1628 incident in Alaska on November 18, 1986. Wylie reviewed radar data and found no unusual targets in the vicinity of the reported sightings.

…etween Japan Air Flight 1628 and air traffic control regarding an unidentified primary target following the aircraft. The conversation indicates military radar tracking an object in close proximity to the flight, raising concerns about safety and the potential need for military intervention.

This document is a personnel statement from Anthony M. Wylie, a Quality 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 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.

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

…e document discusses the phenomenon of uncorrelated radar signals, specifically the differences between primary radar returns and secondary beacon returns when tracking aircraft.

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

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.