Evidence Explorer

2006-0527-F FOI 7-Y MARKER Document ID: 9507092 Row: 44 Position: 3 Section: 6 This is not a textual record. This is used as an administrative marker by the Clinton Presidential Library Staff. Stack: v Shelf: i Original OA/ID Number: 605 1 TO: PRESIDENT FROM: WHITE, JOHN KEYWORDS: LEGAL ISSUES SECURITY PERSONS: SUBJECT: ACTION: SEE 9507055 FOR FINAL ACTION D…

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

…UTION OFFICE BACKGROUNDER UNCLASSIFIED References: (a) James M. Inhofe National Defense Authorization Act of 2023 (b) Message: Unidentified Anomalous Phenomena Reporting and Material‐Disposition General Administration (Joint Staff, 191452ZMAY23) (c) Memorandum: Defense Department Response to Tiger Team Information Request re Unidentified Anomalous Phenomena …

…m Manfred F. Keller, an Automations Specialist at the FAA, regarding an incident involving aircraft JL1628 near Fairbanks, Alaska, on November 18, 1986. Keller reports that he analyzed radar data and found no indications of other traffic in the area where the pilot reported seeing something unusual.

…Anomaly Resolution Office (AARO), the effects of forced perspective and parallax can frequently explain excessively large sizes or high speeds described in UAP reports. In many cases, the

This document discusses a report from Captain Teraucht regarding an unidentified primary target detected by FAA Air Traffic Control in addition to his aircraft. It also references a confidential source indicating that this was not the first sighting of an unidentified object.

The document appears to be a fragmented and unclear text, possibly related to an investigation or report involving unidentified aerial phenomena (UAP). The content lacks coherent information and is difficult to interpret.

Synopsis: Analysis of a Metallic Specimen 012 Page determined to be Unclassified Reviewed by Chief of Staff, AARO IAW FY24 NDAA, Section 1841 (a)(1)(C) Date: 02/06/2025 All-Domain Anomaly Resolution Office Chief of Staff, AARO Authority: FY24 NDAA, now codified at 44 U.S.C. 2107 Date: 02/06/2025 Released in Full: ____X___; Released in Part ______ Case Number…

…from Samuel J. Rich, an Air Traffic Control Specialist at the Anchorage ARTCC, detailing an incident involving aircraft JL 1628 on November 18, 1986. The pilot reported seeing an unidentified large aircraft with yellow and white lights, which was not confirmed by radar.

Statement for the Record Dr. Jon Kosloski, Director, All-domain Anomaly Resolution Office Senate Armed Services Subcommittee on Emerging Threats and Capabilities November 19, 2024 Thank you, Chairwoman Gillibrand, Ranking Member Ernst, and distinguished members of the subcommittee. It is a pleasure to be here on behalf of the Department of Defense as the new…

…m Manfred F. Keller, an Automations Specialist at the FAA, regarding an incident involving aircraft JL1628 near Fairbanks, Alaska, on November 18, 1986. Keller reports that he analyzed radar data but found no indications of other traffic in the area.

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

…amuel J. Rich, an Air Traffic Control Specialist at the Anchorage ARTCC, detailing an incident involving aircraft JL 1628 on November 18, 1986, where the pilot reported seeing an unidentified large aircraft with yellow and white lights.

The document appears to be a technical report or data log related to unidentified aerial phenomena (UAP), containing various time-stamped entries and measurements. The content is heavily encoded and fragmented, making it difficult to extract coherent information.

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.

The document appears 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.

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.

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.

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.