852 matching evidence objects
Ranked by relevance
Matching “Incident 226” across titles, summaries, and full OCR text.
100% match
The document appears to be a technical report containing data logs from a radar system, possibly related to unidentified aerial phenomena (UAP). The logs include various metrics such as time, coordinates, and subsystem information, but the text is heavily corrupted and lacks clear context.
100% match
This document appears to be a technical report detailing various readings and data points related to unidentified aerial phenomena (UAP) captured by radar systems. The data includes time stamps, coordinates, and other technical specifications.
100% match
This document contains beacon target reports from November 18, 1986, detailing various aircraft and their altitudes, speeds, and other parameters. The data appears to be collected from radar systems, indicating the presence of multiple aircraft in the airspace, some of which are not under FAA control.
100% match
This document contains radar data from a military exercise dated November 18, 1986, detailing various beacon targets and their corresponding altitudes, distances, and other metrics.
100% match
The document appears to be a technical report containing various data points and metrics related to unidentified aerial phenomena (UAP). The text includes numerous references to 'SUESYS' and 'SUBSYS', suggesting a structured data format, possibly related to radar or tracking systems. However, the content is largely garbled and lacks coherent context.
100% match
The document appears to be a fragmented and unclear text with no coherent information regarding UAP/UFO sightings or related phenomena.
100% match
…GE 3 OF 3 PAGES Air Almanac, The weather was ceiling and visibility unlimited and the stars were out. "The position of Venus at 1010 Zebra was local hour angle 226 degrees 12 minutes - declination south 22 degrees 58 minutes." ‘This information was taken from the ames 6. Uorne JAMES B, DONNELLY 2nd Lte.s USAF Intelligence Officer NOTE: THIS DOCUMENT CONTAINS…
100% match
/ "AF F ORM 112—PART | | he (CLASSIFICATION) APPROVED 1 JUNE 1948 COUNTRY REPORT NO. (LEAVE B, A A). % eras oH U o Sahe TRe3=53E LS wat —_ a . ee AIR INTELLIGENCE INFORMATION Rl REPORT FLYOBRPT i AREA REPORTED ON FROM (Agency) Long Island, New York 5th Ftr-Intep Sq., McGuire AFB, Trenton, NJ. DATE OF REPORT DATE OF INFORMATION EVALUATION 9 January 1953 29 Oc…
100% match
This document is a preliminary transcript of the Gemini 4 flight crew debriefing conducted on June 9, 1965. The crew discusses various aspects of their mission, including operational challenges, communications issues, and environmental control systems. They also reflect on their experiences during launch, powered flight, and the initial stages of orbital ope…
100% match
The document is a preliminary transcript of the Gemini 4 flight crew debriefing, focusing on the operational aspects of the mission, systems performance, and environmental conditions experienced during the flight. The crew discusses various systems, including the environmental control system, communications, and operational checks, providing insights into th…
100% match
The document is a technical debriefing transcript of the Gemini V mission, focusing on the flight crew's operational experiences and observations during the mission. It includes discussions on systems operations, visual sightings, experiments, and various technical aspects of the spacecraft's performance.
100% match
The 'Go Fast' case involves a U.S. Navy F/A-18F pilot recording an unidentified object over the Atlantic Ocean in January 2015. Analysis by the All-domain Anomaly Resolution Office (AARO) concluded that the object did not exhibit anomalous performance characteristics, with assessed speeds ranging from 5 mph to 92 mph at an altitude of approximately 13,000 fe…
100% match
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 …
100% match
This document appears to be a technical report containing various numerical data and parameters related to unidentified aerial phenomena (UAP) observed on November 18, 1945. The text includes references to subsystems, total counts, and various measurements, but lacks clear context due to its fragmented nature.
100% match
The document appears to be a technical report or data log related to unidentified aerial phenomena (UAP), containing various numerical data points and codes, likely from radar or tracking systems.
100% match
This document appears to be a technical report or data log related to radar systems, possibly involving unidentified aerial phenomena (UAP). It includes various numerical data points, likely representing radar readings, but lacks clear context or explanation.
100% match
The document appears to be a fragmented and poorly formatted text, possibly containing references to unidentified aerial phenomena (UAP) or related military activities. The content is largely unintelligible due to corruption or encoding issues.
100% match
This document appears to be a technical report or data log related to UAV (Unmanned Aerial Vehicle) systems, containing various metrics and parameters, possibly from a radar or telemetry system. The text is fragmented and includes numerical data that may represent flight paths, altitudes, or system statuses.
100% match
This document appears to be a technical report or data log related to unidentified aerial phenomena (UAP) observations, containing various numerical data and timestamps. The text is fragmented and includes references to subsystems and modes, suggesting it may be part of a larger dataset or analysis.
100% match
This document appears to be a technical report or data log related to unidentified aerial phenomena (UAP), containing various metrics and readings from a monitoring system. The data includes timestamps, coordinates, and various performance metrics, but lacks clear context or explanation.