Evidence Explorer

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.

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.

This document contains simulations related to the flight of Japan Air 1628 (JL1628) on November 18, 1986, detailing the plotted positions and interactions with unidentified objects during the flight.

This document is a personnel statement from an Air Traffic Control Specialist regarding an incident involving Japan Airlines Flight 628 on January 11, 1987, where the pilot reported an unidentified object in proximity to the aircraft.

…lot: 3} miles: ahe ra 6 La 2 NM es } ° 4 ~ in's nose, ow that’ the & t lignes. 2 ities Hen at rn lelosing in.on the lead ship and te avoid hitting the supposed target, he gained alti- ian Eee and=siid over’ to the other side of the object, The pilot had the object tn sight. P j7or a total of 2k'to 3 minutes and had a very good look at it from the top and bot…

…the lead - aircraft to identify it.as a 7th Fighter Bomber Squadron aircraft by the color of the ship's nose, he suddenly noticed that it seemd to ‘be towing a target. However, he knew that their squadron was not firing aerial gunnery that day. The pilot was rapidly | elosing in on the lead ship and to avoid hitting the supposed target, he gained alti- tude …

, Following statement furnished as required by APL, 20065, dtd 20 Apr 52, @ by dtd | : + (1)a Objects presented target that appeared to be alreraft on rader scopes, fT ere was no formtion ma i wae aS two objects appeared at the ane time, be definite target appeared at 6 miles from the station at about 1000 fect stationerye Dropped to about 500 feety climbed …

…, for approximately one minute, after which time I returned to operations and attempted to "pick-up" the object on the AN/FPS-3, At 2208 EST, I "picked-up" the target at GQ 4904 and tracked it for 17 minutes, heading 180 degrees at 55 to 60 knots, at which time, 2225 EST at GP 5249, the target faded into the station ground clutter. Upper beam lobe was the on…

…KE FORM.112 ~ s Gchcaecavion 783rd AC&W Squadron APPROWED 1 JUNE 1948" COUNTRY REPORT NO. IR-11-53 AIR INTELLIGENCE INFORMATION REPOR SUBJECT Report of Unusual Target FLYOBR AREA REPORTED ON FROM (Agency) Eastern Central Indiana 783rd ACG Squadron, Charleston, W. Va. DATE OF REPORT DATE OF INFORMATION EVALUATION 27 February 1953 25 February 1953 Al PREPARED …

… JUNE 1948 a 4 COUNTRY | REPORT NO. (LEA VE BLANR) y ge f en IR-11~53 AAG MA ie Gif i AIR INTELLIGENCE INFORMATION REPOR LE ee LT a a SUBJECT Report of Unusual Target FLYOBRPT AREA REPORTED ON —-— FROM (Agency) 763rd AC&! Squadron, Charleston, W. Va. Hastern Central Indiana DATE OF REPORT DATE OF INFORMATION EVALUATION 27 ¥ebruary 1953 25 February 1953 Al PR…

…15 Fa 0450 Fade In accordance with AFL 200-5 Paragraph ¢, dtd 20 April 1952, the followi information is submitted. 1. Radar sighting only, appeared as a normal target ex abrupt maneuvers were noted. Several individual targets were noted. @. Time of sighting was between 0118Z and @215:15 on 20 April 1953. d- Manner of sighting was Electronic, Speed was betwee…

…? erence Irom another radar set been observed recently, and are personnel th vhe effects caused by an interfering signal? scope", etc., were used to follow the target? f= DDT NT ow be os Das oe Pn toa te ) % i al Tat ne digs pr a oll t hau > RPM Normal. Was zed frequently during detection of unusual activity. ency of the transmitter? 1412 mcs i ere the gener…

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…

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.

This document appears to be a radar report detailing various time-stamped observations of unidentified aerial phenomena (UAP) with specific metrics such as altitude, speed, and coordinates. The data is presented in a tabulated format, indicating multiple observations over a period.

This document details an encounter involving Japan Airlines Flight 1628, which reported being followed by an unidentified object while flying over Alaska. The crew observed two lights and later described a large, globular craft that seemed to track their flight path. The FAA and military radar confirmed the presence of an object near the flight, leading to c…

This document discusses considerations affecting the interpretation of reports on Unidentified Flying Objects (UFOs), highlighting the complexities and challenges in analyzing such reports.

This report details a UFO sighting incident near Amarillo, TX, on June 5, 2018, involving multiple aircraft. NORAD reported no known activity, and a subsequent internet search indicated the visibility of the Space Station during that time.

This report details a Skywatch incident involving multiple aircraft that observed an unidentified aerial phenomenon on October 14, 2023. Despite initial concerns of a mission failure, Space OPS confirmed the mission was successful, and recovery operations are ongoing.

This incident report details a sighting of unidentified aerial phenomena (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.