957 matching evidence objects
Ranked by relevance
Matching “JAL Incident” across titles, summaries, and full OCR text.
100% match
This document is a personnel statement 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 confirmed by radar but had no known military traffic in the area.
100% match
1 Lead Staff Members: Daryl Johnson, DSO/SOSB 1. Reason for the briefing: ☐Information Meeting ☒Decision/Alignment Meeting ☐Other ________________ 2. Subject of the briefing: Updating flyover reporting guidance for SIDs to include Unidentified Anomalous Phenomenon (UAP)and potential impacts to Enhanced Weapons Rule reporting requirements 3. Bottom Line Up Fr…
100% match
This document is a personnel statement from Erland D. Stephens, an Air Traffic Control Specialist at the Anchorage ARTCC, detailing an incident involving Japan Airlines Flight 1628 on November 18, 1986, where the flight reported an unidentified object in proximity.
100% match
UNCLASSIFIED UNCLASSIFIED OFFICE OF THE DIRECTOR OF NATIONAL INTELLIGENCE Preliminary Assessment: Unidentified Aerial Phenomena 25 June 2021 UNCLASSIFIED 2 UNCLASSIFIED SCOPE AND ASSUMPTIONS Scope This preliminary report is provided by the Office of the Director of National Intelligence (ODNI) in response to the provision in Senate Report 116-233, accompanyi…
100% match
This document is a personnel statement from Anthony M. Wylie, a Quality Assurance Specialist 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.
100% match
UNCLASSIFIED UNCLASSIFIED THE DEPARTMENT OF DEFENSE ALL-DOMAIN ANOMALY RESOLUTION OFFICE Fiscal Year 2024 Consolidated Annual Report on Unidentified Anomalous Phenomena Information Cut Off: June 1, 2024 UNCLASSIFIED 1 UNCLASSIFIED Table of Contents I. EXECUTIVE SUMMARY ..........................................................................................…
100% match
This document is a personnel statement from 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.
100% match
This document is a personnel statement from Carl E. Henley, an Air Traffic Control Specialist at the Anchorage ARTCC, detailing an incident involving aircraft JL1628 on November 18, 1986. The report describes the communication between the aircraft and air traffic control regarding unidentified traffic in the vicinity.
100% match
UNCLASSIFIED UNCLASSIFIED THE DEPARTMENT OF DEFENSE ALL-DOMAIN ANOMALY RESOLUTION OFFICE Fiscal Year 2024 Consolidated Annual Report on Unidentified Anomalous Phenomena Information Cut Off: June 1, 2024 07 All-Domain Anomaly Resolution Office Chief of Staff, AARO Authority: FY24 NDAA, now codified at 44 U.S.C. 2107 Date: 02/05/2025 Released in Full: ____x___…
100% match
…garding the radar observations of Japan Airlines Flight 1628 on November 18, 1986. It clarifies previous statements about the radar targets observed during the incident.
100% match
This document is a transcription of communications regarding the Japan Airlines Flight 1628 incident on November 18, 1986, where the flight reported unidentified traffic during its flight near Alaska.
100% match
This document is a personnel statement 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.
100% match
This document is a personnel statement from Erland D. Stephens, an Air Traffic Control Specialist at the Anchorage ARTCC, detailing the incident involving Japan Airlines Flight 1628 on November 18, 1986, where the flight reported an unidentified object in close proximity.
100% match
This document is a personnel statement from 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.
100% match
This document is a personnel statement from Anthony M. Wylie, a Quality 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.
100% match
This document is a personnel statement from an Air Traffic Control Specialist at the FAA regarding an incident involving aircraft JL1628 on November 18, 1986. The report details the communication between the aircraft and air traffic control, including the sighting of an unidentified object with white and yellow strobes.
100% match
This document is a personnel statement from Samuel 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.
100% match
This document is a personnel statement from Erland D. Stephens, an Air Traffic Control Specialist at the Anchorage ARTCC, detailing an incident involving Japan Airlines Flight 1628 on November 18, 1986, where the flight reported an unidentified object in proximity.
100% match
… is a personnel statement from Anthony M. Wylie, a Quality Assurance Specialist at the Federal Aviation Administration, regarding the radar data analysis of an incident involving flight JL1628 near Fairbanks, Alaska, on November 18, 1986.
100% match
This document appears to be a communication related to an incident in the Alaskan region, possibly involving air traffic or military operations. The text is fragmented and contains various codes and contact numbers, indicating a procedural or operational context.