733667-001-012

Tab 1 Tab 2 Tab 3 Tab 4 Tab 5 Tab 6 Tab 7 Tab 8 Tab 9 ,- t l INDEX Index Chronology of Events Transcription Flight Path Chart Personnel Statements Daily Record of Facility Operations, FAA Form 7230-4 Position Logs, FAA Form 7230-10 ZAN EARTS Continuous Data Recordings, (radar tracking data). Simulated Radar Data -JL1628 U.S.~rtrnent of Transponation Federal Aviation Administration Subject : INFORMATION: Unidentified Traffic Sighting by Japan Airlines From: Air Traffic Manager, Anchorage ARTCC, ZAN-1 To: Manager, Air Traffic Division, AAL-500 ATTN: Evaluation Specialist, AAL-51"4 Memorandum Date: OE.C 1 8 1986 Reply to Attn. of: The attached chronology summarizes the communications and actions of Japan Airlines Flight 1628 on November 18, 1986. Radar data recorded by Anchorage Center does not confirm the presence of the traffic reported by Flight 1628. No further information has been received from civil or military sources since the date of the sightings. Major Johnson of the ~lmendorf Regional Operations Command Center (ROCC) is checking their re·c·ords and the operations personnel for further details. He will forward any additional information to Anchorage Center as soon as possible. Should you have any questions or need additional information, contact Tony Wylie, Quality Assurance Specialist, 269-1162. Original sigoeg ~ Quentin J. Gates Attachment DEC l 8 198b The following is a chronological summary of the alleged aircraft sightings by Japan Airlines Flight 1628, on November 18, 1986: All times listed are approximate UTC unless otherwise specified. 0219 -The pilot of JL1628 requested traffic information from the ZAN Sector 15 controller. When the controller advised there was no traffic in the vicinity, JL1628 responded that they had same direction traffic, approximately 1 mile in front, and it appeared to be at their altitude. When queried about any identifiable markings, the pilot responded that they could only see white and yellow strobes. 0225 -JL1628 informed ZAN that the traffic was now visible on their radar, in their 11 o'clock position at 8 miles. 0226 -ZAN contacted the Military Regional Operations Control Center, (ROCC), and asked if they were receiving any radar returns near the position of JL1628. The ROCC advised that they were receiving a primary radar return in JL1628's 10 o'clock position at 8 miles. 0227 -The ROCC contacted ZAN to advise they were no longer receiving any radar returns in the vicinity of JL1628. 0231 -JL1628 advised that the "plane" was "quite big", at which time the ZAN controller approve~ any course deviations needed to avoid the traffic. 0232 JL1628 requested and received a descent from FL350 to FL310. When asked if the traffic was descending also, the pilot stated it was descending "in formation". 0235 -JL1628 requested and received a heading change to two one zero. The aircraft was now in the vicinity of Fairbanks and ZAN contacted Fairbanks Approach Control asking if they had any radar returns near JL1628's position. The Fairbanks Controller advised they did not. 0236 -JL1628 was issued a 360 degree turn and asked to inform ZAN if the traffic stayed with them. 0238 -The ROCC called ZAN advising they had confirmed a "flight of t-wo" in JL1628's position. They advised they had some "other equipment :·watching this", and one was a primary target only. 0 239 -JL1628 told ZAN they no longer had the traffic in sight. 0242 -The ROCC advised it looked as though the traffic had dropped back and to the right of JL1628, however, they were no longer tracking it. 0244 -JL1628 advised the traffic was now at 9 o'clock 0245 -ZAN issued a 10 degree turn to a northbound Unite d Airlines flight, after pilot concurrence, in a n attempt to confirm the traffic. 0248 -JL1628 told ZAN the traffic was now at 7 o'clock, 8 miles. ' . .. DEC 18 1986 0250 -The northbound . United Flight advised they had the Japan Airlines flight in sight, against a light background, and could not see any other traffic. 0253 -JL1628 advised they no longer had contact with the traffic. A subsequent review of ANC ARTCC's radar tracking data failed to confirm any targets in close proximity to JL1628.