PURSUE Record — Japan Air Lines Flight 1628 — Alaska, November 17, 1986: Federal Aviation Administration / JAL crew · Northern Alaska, near Fort Yukon · Novembe

I have enough context. Here is the HTML editorial: ---

The PURSUE Release 01 set, published May 8, 2026 by the U.S. Department of War, includes one historical record filed under the title Japan Air Lines Flight 1628 — Alaska, November 17, 1986. It is classified as a HIST document — a historical case file — drawn from Federal Aviation Administration records and JAL crew reporting. The underlying source material originates from a 1987 FAA public report, with ongoing analysis in the years since. It is among the older cases in the release, predating the current era of dedicated UAP sensor programs by roughly three decades.

What this record contains

The single-part file covers the encounter reported by the crew of Japan Air Lines Flight 1628, a Boeing 747 cargo aircraft transiting from Iceland to Anchorage, Alaska. According to the official description included in the PURSUE Release 01 metadata, on November 17, 1986, the flight was tracked — or rather, tracked objects — over northern Alaska, near Fort Yukon, for approximately 50 minutes. The crew reported contact with three objects: two smaller craft followed by a much larger object. Captain Kenju Terauchi described the larger object as "walnut-shaped," positioned behind his aircraft, and the cockpit's airborne radar reportedly registered an object roughly twice the size of an aircraft carrier.

What separates this case from single-witness reports is a corroboration layer noted in the metadata. The JAL onboard radar reportedly registered the objects. Ground radar at the Anchorage Air Route Traffic Control Center tracked a contact during the same window. Elmendorf Air Force Base is also cited as having tracked the contact. The FAA's John Callahan, then-Division Chief of the Accidents and Investigations Branch, later stated publicly that the FAA investigation report had been suppressed by the CIA. The releasing agencies on record are the Federal Aviation Administration and the JAL crew. The case remains officially unresolved.

Sensor & operational context

By November 1986, commercial aviation radar systems were mature but purpose-built for weather avoidance and route spacing — not surveillance. A Boeing 747's onboard weather radar of that era produced primary returns, meaning an uncooperative object with no transponder would appear as a radar blip without identification data, impossible to distinguish by radar alone from large weather returns or certain atmospheric phenomena. Ground-based en-route radar at Anchorage ARTCC operated on similar principles for primary tracking. This doesn't discredit the reported contacts; it does mean that "tracked on radar" establishes presence of a return, not the nature of whatever generated it. The reported 50-minute duration and multi-platform corroboration — airborne, civilian ground radar, and military — is what elevates the case above typical single-source anomalies.

The operational geography matters too. The Alaska corridor in 1986 was among the most heavily monitored domestic airspaces in the United States precisely because of its proximity to Soviet airspace during the final years of the Cold War. That infrastructure gave the encounter an unusual density of tracking capability for a civilian route. It also meant any significant anomaly in that airspace would have had national security implications beyond aviation safety — which may bear on John Callahan's later allegation of CIA involvement in suppressing the report.

What this does and does not prove

The documented facts on record are: a commercial flight crew reported a prolonged visual and radar contact near Fort Yukon; multiple radar systems reportedly registered something in that airspace; the FAA conducted a formal investigation; and a senior FAA official later publicly alleged the resulting report was suppressed at the direction of another federal agency. What the record does not establish is the identity, origin, or nature of whatever the crew observed. "Walnut-shaped" and "twice the size of an aircraft carrier" are crew descriptions, reported in good faith, that have not been corroborated by any independent physical evidence in the public domain. The case is officially unresolved — meaning no explanation has been confirmed, not that an extraordinary explanation has been validated. The PURSUE release reproduces the record as investigative material, not a verdict.

How it fits PURSUE Release 01

This record occupies the historical tier of a release that spans 1947 through the contemporary period — 162 total documents, including 28 videos, 14 images, and 120 PDFs. The JAL 1628 file represents a category of case where civilian aviation infrastructure intersected with a formally unexplained aerial encounter, documented through FAA channels, corroborated (per the metadata) by military radar, and subsequently entangled in allegations of federal suppression. It sits alongside other historically significant cases in the PURSUE set that document the government's long-running and often discontinuous engagement with UAP reporting — from FBI field correspondence of the late 1940s through Department of War mission records from recent years. The analytical discipline the release demonstrates by including historical cases alongside contemporary sensor footage is worth noting: unresolved does not mean unexplainable, and the record itself is one data point in a much larger ongoing body of PURSUE coverage.

Editorial note: This analysis is independent commentary on a publicly released document. The original record, source links, and full release metadata are catalogued on the SkyLens UAP files page alongside every other case in the PURSUE Release 01 set.