Evidence Explorer

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 document outlines proposed updates to the reporting guidelines for unidentified anomalous phenomena (UAP) flyovers, particularly in relation to nuclear facilities and the establishment of secure reporting mechanisms.

… report details a Skywatch incident involving an unidentified aerial phenomenon (UAP) observed near DAA on October 16, 2021. Multiple agencies were involved in tracking the target, but no visual confirmation was made.

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 an unidentified aerial phenomenon (UAP) encounter on February 24, 2023, involving radar tracking and military response.

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

Current & Future Flyover Reporting Guidance for SIDs: A Proposal11545 Rockville PikeOne White Flint NorthRockville, MD 20852 Agenda Introduction SID Flyover Reporting Guidelines Update Needed? AARO UAP Reporting Requirement EC. 1673. UNIDENTIFIED ANOMALOUS PHENOMENA REPORTING PROCEDURES. (a) Mechanism for Authorized Reporting.-- (1) Establishment.--The Secre…

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

This document provides a chronological account of the alleged UAP sightings reported by Japan Airlines Flight 1628 on November 18, 1986, detailing interactions between the flight crew and air traffic control regarding unidentified traffic.

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

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

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