Evidence Explorer

…ified as a UAP while flying at FL330 near Nantucket, MA. The FAA was notified, but no evasive action was taken and there was no impact to the National Airspace System.

…erial phenomena (UAP) activity involving a Pilatus PC-12 aircraft near Dallas, Texas, on March 10, 2024. The aircraft reported sighting a black unmanned aerial system (UAS) while flying at 1,500 feet.

… 5, 2024, American Airlines flight 1913 reported UAP activity while en route from Chicago O'Hare to Phoenix. The crew experienced a Traffic Collision Avoidance System (TCAS) Resolution Advisory (RA) due to two slow-moving aircraft and another aircraft traveling in the opposite direction, all reported to be light grey in color. No radar returns were detected …

595507

This document is a letter from Paul Steucke of the FAA to Dr. Richard F. Haines regarding the JAL 1628 flight incident and related radar data. It discusses the availability of radar tapes and data, and invites Dr. Haines to visit the Anchorage Air Route Traffic Control Center.

This document details an incident involving unidentified air traffic observed by the crew of JAL flight 1628 on November 17, 1987, as they approached Anchorage, Alaska. The crew reported seeing strange lights that changed position and were confirmed on radar by air traffic control.

The document discusses the radar data related to Japan Airlines flight 1628, which experienced uncorrelated radar signals during its flight on November 17, 1986. FAA experts analyzed the radar data and explained the phenomenon of uncorrelated targets, emphasizing that this occurrence coincided with a pilot's sighting of an unidentified object.

This document analyzes radar data related to the JAL-1628 incident on November 18, 1986, which involved an alleged UFO sighting. The analysis indicates that the radar returns were normal and did not show any abnormalities associated with the reported UFO.

This document details an incident involving unidentified air traffic observed by the crew of Japan Airlines flight 1628 while approaching Anchorage on November 17. The crew reported seeing strange lights that changed position and were confirmed on radar by air traffic control.

This document details two incidents of unidentified air traffic sightings reported by flight crews in Alaska in January 1987. The first incident involved an Alaska Airlines Boeing 737 that detected a fast-moving target on its radar, while the second incident involved a Japan Airlines Boeing 747 pilot who reported unusual lights in front of his aircraft.

A cargo aircraft crew reported observing irregular pulsating lights and a large black object while flying over Alaska. The FAA concluded that the lights were likely caused by atmospheric conditions.

This document appears to be a communication or report related to air traffic control and military operations, specifically referencing NORAD and FAA operations in the Anchorage area. It includes technical terms and acronyms relevant to aviation and air defense.

This document contains operational details related to air traffic control and military coordination in the context of air defense, specifically referencing NORAD and FAA operations.

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.

This document contains beacon target reports from November 18, 1946, detailing various radar readings and system statuses. The data includes time stamps, altitudes, and other metrics related to unidentified aerial phenomena.

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.

…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 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 related to a system's performance metrics, possibly involving UAP/UFO detection systems. It includes various subsystem readings, timestamps, and performance indicators.