Evidence Explorer

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.

…ument 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 appears to be a technical report or data log related to radar or tracking systems, detailing various parameters such as time, altitude, and coordinates. The text includes numerous entries with numerical data that may pertain to unidentified aerial phenomena (UAP) or other aerial targets.

This document appears to be a technical report related to radar data analysis, possibly concerning unidentified aerial phenomena (UAP). It includes various subsystems and total counts, but the text is heavily corrupted and lacks coherent context.

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.

This document appears to be a technical report or data log related to beacon signals, possibly from radar or tracking systems. The content includes various numerical data points and references to different subsystems, but lacks coherent narrative or context.

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

This document appears to be a technical report related to beacon systems, possibly involving radar or tracking data. The text includes various numerical data points and references to subsystems, but lacks coherent context or clear findings due to its fragmented nature.

The document appears to be a technical report with various data points, possibly related to radar or tracking systems. The text includes numerous numerical values and codes, but lacks coherent context or clear conclusions regarding UAP/UFO phenomena.

The document appears to be a technical report related to beacon and subsystem data, possibly from radar or tracking systems. The text includes various time stamps and mode C totals, indicating measurements or readings taken at specific intervals.

A cargo aircraft captain reported seeing irregular pulsating lights that he believed to be a UFO while flying over Alaska. The FAA concluded that the lights were likely caused by atmospheric conditions.

…light, digappera- ive aftex about 8 miuutes. Other objects not sighted vieunlly. ‘The uier- nigned has had three and one half years experience in Al/uPie] type radar presentations ! | | ; | Pak 7 Ge (6) Weather at the time of observations Sky < clears visibility « 10 miles; 4 nde = West at 10 knots; altimeter reading © 30017, : Per 7 Ge (7) Bo legion] explim…

This document details various sightings and investigations of unidentified aerial phenomena (UAP) in Washington State between 1952 and 1960, primarily reported to the FBI. It includes eyewitness accounts of large metallic objects, descriptions of their movements, and the responses from local authorities and military personnel.

…mena (UAP) by a commercial aircraft, AAL1913, which reported a TCAS resolution advisory (RA) involving multiple unidentified objects while flying at FL 260. No radar returns were detected, and other aircraft in the vicinity also reported similar encounters.

… JULY 19, 1952. “TBRIEFY,"HE STATES INA NEWSPAPER ARTICLE, "...0UR JOB 18 TO CONSTANTLY MONITOR THE SKIES ARGUND THE NATIONS CAPITOL WITH THE ELECTRONIC EYE OF RADAR...” SHORTLY AFTER MIDNIGHT ON THAT DATE, SEVENPIPS APPEARED SUDDENLY ON THE CONTROL CENTER'S SCOPE. ED NUGENT, JIM COPELAND, AND JIM R

595553

This document discusses the unusual visual and radar sighting reported by the crew of Japan Airlines Flight 1628 on November 17, 1986. The communication details observations made by the flight crew, including descriptions of lights and radar readings, and requests for further information.

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

…w 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 is a personnel statement from Carl E. Henley, an Air Traffic Control Specialist at the Anchorage ARTCC, regarding the radar observations of Japan Airlines Flight 1628 on November 18, 1986. It clarifies previous statements about the radar targets observed during the incident.