Fairbanks Alaska Airspace

Fairbanks Alaska Airspace marks the Interior Alaska segment where Japan Air Lines Flight 1628, a Boeing 747 freighter, reported unidentified traffic while inbound from Keflavik to Anchorage on 17 November 1986. The location is anchored near Fairbanks International Airport because FAA records place the aircraft in the Fairbanks vicinity when controllers queried Fairbanks Approach and requested the 360-degree maneuver that became the case's central airspace event.¹²³⁴

The status here is confirmed as an official FAA and NARA record location, not as confirmation that the reported traffic was an extraordinary craft. NARA catalogs the underlying FAA series in Record Group 237, while the FAA's own public release said the agency was unable to confirm the reported UFO event after reviewing radar data.¹⁵⁶

  Geographic Profile

Fairbanks International Airport sits southwest of Fairbanks at roughly 64.8154 N, 147.8567 W, matching the mapped anchor used here for the local controlled-airspace context.⁷ The broader en route environment was handled by Anchorage Air Route Traffic Control Center, which today describes itself as the northern, eastern, and western-most ARTCC, responsible for more than two million square miles of airspace with limited radar coverage across Alaska.⁸

In the 1986 record, the flight path is repeatedly described as flowing from the Alaska-Canada border through Fort Yukon, Fairbanks, and onward toward Anchorage. FAA interview notes recorded that the crew could see FAI and that the aircraft performed its 360-degree turn over the Fairbanks area.⁵

  Origin Of The Report

The story originated in live operational calls, not in later folklore. FAA chronology says that at 0219 UTC on 18 November 1986, corresponding to the evening of 17 November in Alaska, JAL 1628 asked Anchorage Center for traffic information and then reported same-direction traffic about one mile ahead at its altitude.³

At 0225 UTC, the crew reported that the traffic appeared on their onboard radar at the 11 o'clock position, eight miles away. One minute later, Anchorage Center contacted the Elmendorf Regional Operations Control Center, which advised that it had a primary radar return near the reported position before later reporting that the return was gone.³⁴

By 0235 UTC, the aircraft was near Fairbanks. Anchorage Center asked Fairbanks Approach Control whether it saw other traffic near JAL 1628, and Fairbanks replied that it did not see anything aside from the JAL target. Anchorage Center then cleared course deviations, approved a descent from FL350 to FL310, and requested a right 360-degree turn so the crew could report whether the traffic stayed with them.³⁴

  Crew And Controller Record

FAA interview notes identified the crew as Captain Kenjyu Terauchi, First Officer Takanori Tamefuji, and Flight Engineer Yoshio Tsukuda, and described the interviews as concerning unknown air traffic that accompanied the route from the Alaska-Canada border toward Fairbanks and Anchorage.⁵

The notes also recorded that the crew used onboard color radar, described the object as at least Boeing 747-sized, reported lights of several colors, and was assessed by FAA interviewers as normal, professional, and rational, with no drug or alcohol involvement noted.⁵

Controller statements preserved the working uncertainty inside the room. One Anchorage controller said ROCC had a primary target where JAL 1628 reported traffic, that single primary returns appeared several times, and that the reported traffic seemed to stay with the aircraft during turns and descent near FAI.⁹

The same controller statement also records the check against United Airlines Flight 69. United was vectored toward JAL 1628 with pilot concurrence, saw the Japan Air Lines aircraft, and reported no other visible traffic around it.⁴⁹

  Radar Interpretation

The case's evidentiary tension comes from the difference between real-time impressions and later technical review. FAA chronology recorded intermittent military and controller radar concern during the event, but concluded that later Anchorage ARTCC radar tracking review failed to confirm targets close to JAL 1628.³⁹

FAA's radar analysis described the second-target effect as uncorrelated primary and beacon returns from the same aircraft. The analysis said about 61 minutes of data were reviewed, found no abnormality matching the pilot's reported target, and considered the returns normal for the Murphy Dome radar system and nearby terrain.⁶

On 5 March 1987, FAA's Alaskan Region released the packet publicly. The press release said the FAA normally did not investigate UFO sightings, but had pursued this one as an air-traffic safety question; it closed by saying the safety of the air traffic control system had not been compromised and that no further investigation was planned.⁵⁶

  Archival Evolution

The public case evolved through three overlapping records: the crew's visual and onboard-radar account, the controller and ROCC coordination record, and the FAA's later technical explanation. That split is why Fairbanks remains one of the strongest aviation UAP case-study locations while still carrying an official FAA conclusion of unconfirmed traffic.³⁹⁵⁶

NARA's textual guide now lists the FAA series as Information Releases Relating to Unidentified Flying Object, 1986, specifically tied to Japan Airlines Flight 1628 and National Archives Identifier 733667. NICAP's hosted Bruce Maccabee reconstruction later helped circulate the extended case narrative and critique of the FAA radar interpretation outside the original release packet.¹¹⁰

  Timeline

  References

  References

1. archives.gov ↩ ↩² ↩³

2. documents.theblackvault.com ↩

3. documents.theblackvault.com ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷ ↩⁸ ↩⁹ ↩¹⁰ ↩¹¹

4. documents.theblackvault.com ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷

5. documents.theblackvault.com ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷

6. documents.theblackvault.com ↩ ↩² ↩³ ↩⁴ ↩⁵

7. dot.alaska.gov ↩

8. faa.gov ↩

9. documents.theblackvault.com ↩ ↩² ↩³ ↩⁴

10. nicap.org ↩