Evidence Explorer

… (UAP) and the advanced technology associated with them. The speaker expresses interest in gathering information about sightings and comparing them to previous reports.

ALL- DOMAIN ANOMALY RESOLUTION OFFICE US Department ofDefense The US Defense Department & the UAP Mission Seán Kirkpatrick, Ph.D. Director, AARO FOR DISPLAY ONLY UNCLASSIFIED UNCLASSIFIED FOR DISPLAY ONLY All-Domain Anomaly Resolution Office Chief of Staff, AARO Authority: FY24 NDAA, now codified at 44 U.S.C. 2107 Date: 3/20/2025 Released in Full: X Case Num…

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.

UNCLASSIFIED UNCLASSIFIED All-domain Anomaly Resolution Office U.S. Department of Defense Case: “Go Fast” Case Resolution | February 6, 2025 Case Overview In January 2015, a U.S. Navy F/A-18F pilot recorded an object using a Forward Looking Infrared (FLIR) sensor about 13,000 feet above the Atlantic Ocean off the coast of Florida. The video appeared to show …

…ng radar contact and visibility issues during flight. The conversation indicates a potential unidentified aerial phenomenon (UAP) situation, as the flight crew reports no radar replies and mentions traffic being extinguished.

UNCLASSIFIED 1 UNCLASSIFIED All-domain Anomaly Resolution Office (AARO) U.S. Department of Defense Case: “The Puerto Rico Object” Case Resolution | 20 March 2025 Case Synopsis Location: Puerto Rico Date: April 26, 2013 Object Altitude (Reported): N/A Object Altitude (Assessed): 656 ft Object Speed (Reported): N/A Object Speed (Assessed): 8 mph Object Shape (…

This document contains beacon target reports from November 18, 1986, detailing various radar readings and subsystem totals related to unidentified aerial phenomena.

The document appears to be a fragmented and corrupted report related to unidentified aerial phenomena (UAP) sightings and investigations, primarily from the 1950s. It includes references to radar detections, military communications, and possible sightings of flying saucers, but the text is largely unintelligible due to formatting issues.

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 is a report template for individuals observing a fireball or meteor, requesting detailed information to aid in the scientific study of meteors.

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.

The document discusses the possibility of UFOs originating from Mars or Venus, analyzing the timing of potential space travel based on favorable launch and arrival windows. It suggests a method to statistically evaluate UFO sightings during these intervals to determine if there is a correlation with extraterrestrial visits.

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.

The document discusses a UFO sighting by the crew of Japan Airlines Flight 1628 on November 17, 1986, which was corroborated by radar data. The crew reported seeing strange lights, which were later analyzed and attributed to various factors, including the planet Jupiter and atmospheric conditions.

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 is a log from the Anchorage Air Traffic Control Center detailing operations and incidents on December 17, 1986. It includes reports of intermittent radar contact with an unknown target and mentions of volcanic activity from Mt. Pavlof.

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.

This document contains a series of beacon target reports from November 18, 1986, detailing various radar readings and observations related to unidentified aerial phenomena (UAP). The data includes timestamps, azimuth, range, and other technical specifications.

This document appears to be a report containing various data points related to unidentified aerial phenomena (UAP) observations, including coordinates, time ranges, and other technical specifications.

The document contains beacon target reports from November 18, 1986, detailing various radar readings and subsystem data related to unidentified aerial phenomena.