Military Report
Unclassified Complete
733667-001-012-0003
National Archives and Records Administration
Confidence
85%
Credibility
90%
View original document ↗ hosted at the official government source
Intelligence summary
This document provides a chronological account of the alleged UAP sightings reported by Japan Airlines Flight 1628 on November 18, 1986, detailing interactions between the flight crew and air traffic control regarding unidentified traffic.
Tags & topics
Air traffic controlAviation SafetyMilitary CoordinationUAP Flight 1628Japan AirlinesMilitary InvolvementRadar TrackingUFO
Extracted timeline
Jun 15, 1986
Document Date (year hint)
Document Date (year hint) for 733667-001-012-0003
Jun 16, 2026
Ingestion Date
Ingestion Date for 733667-001-012-0003
Jun 16, 2026
Document Record Date
Document Record Date for 733667-001-012-0003
Jun 16, 2026
Update Date
Update Date for 733667-001-012-0003
Entities mentioned
Full document text
2,460 characters, transcribed via OCR. Errors reflect the source scan. Compare with the original ↗
ee
(
\
0219
0225
0226
0227
0231
0232
0235
0236
0238
0239
0242
0244
0245
0248
DEG 18 1986
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.
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.
JL1628 informed ZAN that the traffic was now visible on their radar,
in their 11 o'clock position at 8 miles.
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.
The ROCC contacted ZAN to advise they were no longer receiving any
radar returns in the vicinity of JL1628.
JL1628 advised that the “plane” was “quite big”, at which time the ZAN
controller approved any course deviations needed to avoid the traffic.
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”.
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.
JL1628 was issued a 360 degree turn and asked to inform ZAN if the
traffic stayed with them.
The ROCC called ZAN advising they had confirmed a "flight of two” in
JL1628's position. They advised they had some “other equipment
-watching this”, and one was a primary target only.
JL1628 told ZAN they no longer had the traffic in sight.
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.
JL1628 advised the traffic was now at 9 o'clock
ZAN issued a 10 degree turn to a northbound United Airlines flight,
after pilot concurrence, in an attempt to confirm the traffic.
JL1628 told ZAN the traffic was now at 7 o'clock, 8 miles.