What Really Happened Over Alaska?

Introduction

The strongest reading is cautious: the case involved sincere, experienced witnesses, ambiguous radar indications, and a serious air-traffic response, but the official record does not confirm a solid craft tracking the aircraft. A December 1986 FAA memorandum says Anchorage Center radar data did “not confirm the presence” of the traffic reported by JAL 1628, while later sceptical analysis argued that parts of the sighting could be explained by radar correlation artefacts, ice-crystal or cloud effects, and bright celestial objects, especially Jupiter. The Black Vault Documents [Center for Inquiry]centerforinquiry.s3.amazonaws.comCenter for Inquiry

What the crew reported over Alaska

JAL 1628 was a cargo flight from Europe towards Japan, stopping at Anchorage. The event occurred on the Reykjavík-to-Anchorage leg, over eastern Alaska, with Captain Kenju Terauchi, First Officer Takanori Tamefuji, and Flight Engineer Yoshio Tsukuba aboard. FAA interview notes say the crew reported “unidentified air traffic” after departure from Reykjavík, with the aircraft at flight level 390 and flying at Mach 0.84 when the captain first described the object near the Potat intersection and the Air Defence Identification Zone. [The Black Vault Documents]documents.theblackvault.comThe Black Vault Documents

Terauchi’s account was dramatic. FAA notes record him saying the traffic appeared roughly seven to eight nautical miles ahead for about twelve minutes, that the range came from the aircraft’s onboard Bendix colour radar, and that he saw yellow, amber and green lights with a rotating beacon but no red lights. The notes also say he described two distinct sets of lights that appeared joined together, and that he judged the unknown traffic to be about the size of a Boeing 747 or larger. [The Black Vault Documents]documents.theblackvault.comThe Black Vault Documents

The reported geometry changed during the encounter. Terauchi said the lights shifted from horizontal to vertical and moved from in front of the aircraft to its port side, remaining there for about 35 minutes. He requested and received permission to make a 360-degree turn near Fairbanks, and later said the unknown traffic maintained its position during the turn. According to the same FAA interview notes, visual contact was lost roughly 40 nautical miles north of Talkeetna as the aircraft continued towards Anchorage. [The Black Vault Documents]documents.theblackvault.comThe Black Vault Documents

The timeline that makes the case compelling

The case remains famous because it was not merely a post-flight anecdote. The crew talked to Anchorage Air Route Traffic Control Center during the event, controllers queried military radar, the aircraft changed altitude and heading, and another airliner was asked to assist in visual confirmation.

The FAA chronology gives the key sequence in UTC. At about 02:19, JAL 1628 asked for traffic information; the controller advised there was no known traffic nearby, while the crew reported same-direction traffic about one mile ahead and apparently at their altitude. At 02:25, JAL said the traffic was visible on its radar at the 11 o’clock position, eight miles away. At 02:26, the Military Regional Operations Control Center reported a primary radar return in JAL 1628’s 10 o’clock position at eight miles, but at 02:27 it advised that it was no longer receiving returns near the aircraft. [The Black Vault Documents]documents.theblackvault.comThe Black Vault Documents

The aircraft then manoeuvred. At 02:31, the crew described the “plane” as “quite big”, and the controller approved deviations to avoid the traffic. At 02:32, JAL 1628 descended from flight level 350 to flight level 310, and the pilot said the traffic was descending “in formation”. At 02:35 and 02:36, controllers issued a heading change and then a 360-degree turn; Fairbanks Approach Control was asked whether it had radar returns near JAL 1628, and replied that it did not. [The Black Vault Documents]documents.theblackvault.comThe Black Vault Documents

The chronology also records the most ambiguous radar moment. At 02:38, ROCC told Anchorage Center it had confirmed a “flight of two” in JAL 1628’s position, with “other equipment” watching and one return described as primary-only. A minute later, JAL reported it no longer had the traffic in sight. By 02:42, ROCC said the traffic appeared to have dropped back and to the right, but that it was no longer tracking it. [The Black Vault Documents]documents.theblackvault.comThe Black Vault Documents

Why the radar record cuts both ways

For UFO advocates, the radar exchanges are the heart of the case: they suggest that something external to the crew’s perception may have been detected. That is a reasonable reason to treat the case as more substantial than a simple single-witness sighting. Contemporary press accounts also emphasised radar confirmation; UPI reported in late December 1986 that an air controller said radar showed a mysterious object following the JAL cargo flight, and a later UPI article said FAA and Alaska Air Command officials had discussed radar indications near the aircraft. [UPI]upi.comController confirms UFO sightingController confirms UFO sighting

The difficulty is that the internal FAA record is more restrained than the headlines. The December 1986 Anchorage ARTCC memorandum states that “radar data recorded by Anchorage Center does not confirm the presence of the traffic reported by Flight 1628” and that no further information had been received from civil or military sources at that time. The same chronology says a later review of Anchorage ARTCC radar tracking data “failed to confirm any targets in close proximity” to JAL 1628. [The Black Vault Documents]documents.theblackvault.comThe Black Vault Documents

The difference matters. A controller or military radar operator can report a possible primary return during a live event, while a later technical review can still judge that the recorded data do not establish a separate aircraft or craft. That does not prove the crew saw nothing; it means the radar record is not the clean, independent confirmation sometimes claimed in simplified retellings.

The failed visual confirmation is just as important

One of the most underplayed details is that other aircraft were brought into the situation and did not see the object. At 02:45, Anchorage Center issued a 10-degree turn to a northbound United Airlines flight, with pilot agreement, in an attempt to confirm the traffic. At 02:50, the United crew reported that they had the JAL aircraft in sight against a light background, but could not see any other traffic. At 02:53, JAL 1628 advised that it no longer had contact with the traffic. [The Black Vault Documents]documents.theblackvault.comThe Black Vault Documents

Philip J. Klass’s 1987 Skeptical Inquirer analysis stressed this point. He wrote that two aircraft in the area, United Airlines Flight 69 and a USAF C-130 transport, were vectored or volunteered to look for the reported object, but neither crew saw an unidentified object near JAL 1628. According to Klass, the United crew readily saw the JAL 747 but not the reported luminous object; the C-130 crew also saw the JAL aircraft but nothing else nearby. [Center for Inquiry]centerforinquiry.s3.amazonaws.comCenter for Inquiry [Center for Inquiry]centerforinquiry.s3.amazonaws.comCenter for Inquiry

This does not automatically disprove the sighting. The geometry, lighting, distance, cockpit workload, and brief viewing windows all matter. But it does weaken the claim that a large, solid object was plainly pacing the 747 in a way that should have been unmistakable to nearby observers.

What the other crew members add and limit

The three JAL crew members are often treated as if they gave one unified account. The record is more complex. The FAA interviews and later analysis suggest that the crew agreed on seeing unusual lights, but not necessarily on Terauchi’s most dramatic interpretation of a vast structured craft.

Klass’s review of the FAA interview material says Flight Engineer Tsukuba described the initial lights as a cluster of undulating lights, different from town lights, but was unable to describe a definite shape for either reported object. Tsukuba also reportedly said that when first interviewed immediately after the incident he was not sure whether the object was a UFO, and that his mind had not changed. [Center for Inquiry]centerforinquiry.s3.amazonaws.comCenter for Inquiry

First Officer Tamefuji’s account also appears more cautious than Terauchi’s. He described what at first looked like two small aircraft slightly below altitude, but when asked whether he could distinguish the lights from a star, he answered “No”. When shown Terauchi’s sketch of a giant walnut-shaped object, he reportedly said he had not seen anything like that, though he allowed that connecting the lights might imply a large object. [Center for Inquiry]centerforinquiry.s3.amazonaws.comCenter for Inquiry

That distinction is central to judging witness credibility. The case does not require dismissing the crew as unreliable. It does require separating the shared observation of unusual lights from the captain’s more expansive interpretation of a “mothership” or giant craft.

The official position was limited, not a full debunking

The FAA did not present itself as a scientific UFO-investigation body. In the 1987 Skeptical Inquirer article, Klass quoted FAA Alaskan Region public affairs officer Paul Steucke as saying the agency lacked both the resources and the Congressional mandate to investigate UFO sightings scientifically, including analysis of stars, planets, magnetic fields, and viewing angles. The FAA’s role was primarily aviation safety, records handling, and air-traffic documentation. [Center for Inquiry]centerforinquiry.s3.amazonaws.comCenter for Inquiry

That limited mandate is often misunderstood. It means the FAA’s file is valuable because it preserves communications, interviews, logs and radar-related material, not because it provides a definitive scientific verdict on what the crew saw. The U.S. National Archives listing confirms the existence of the FAA record series for the JAL 1628 release, while The Black Vault’s archive page shows the breadth of surviving material, including crew interview notes, Terauchi’s written statement, radio transcripts, flight path charts, facility logs, radar recordings and news clippings. [National Archives]archives.govSource details in endnotes. [The Black Vault]documents.theblackvault.comThe Black Vault DocumentsThe Black Vault Documents

The best official-summary sentence is therefore negative but narrow: the FAA record does not confirm unidentified traffic in close proximity to JAL 1628. It does not prove that Terauchi invented the sighting, and it does not prove that nothing unusual was perceived. It says the objective aviation data were insufficient to establish the reported traffic as a confirmed target. [The Black Vault Documents]documents.theblackvault.comThe Black Vault Documents

The main sceptical explanations

The sceptical case has several parts rather than one simple claim. The most cited explanations involve radar artefacts, bright planets, moonlit ice crystals or clouds, and interpretation drift between immediate reports and later interviews.

Klass argued that one radar issue could be explained by an “uncorrected primary and beacon target”, a known radar phenomenon in which a primary reflection and transponder return are not properly correlated. In his account, FAA specialist Dennis R. Simantel treated such uncorrected primary returns as not uncommon because of timing issues involving the aircraft transponder and radar target-correlation circuitry. [Center for Inquiry]centerforinquiry.s3.amazonaws.comCenter for Inquiry

The visual explanation is more layered. Klass placed bright Jupiter low in the south-eastern sky and argued that, from Terauchi’s vantage point, it could have appeared near the direction in which he later reported the object. He also noted Mars was visible but much fainter. For the earlier “cluster of lights”, he proposed moonlight reflecting from turbulent ice-crystal clouds, possibly producing undulating flame-coloured lights, with changing cloud conditions explaining disappearance and reappearance. [Center for Inquiry]centerforinquiry.s3.amazonaws.comCenter for Inquiry

A key supporting point for the ice-crystal and misidentification argument is a later January 1987 report by Terauchi in roughly the same area. Klass wrote that Terauchi again reported unusual lights and a large dark shape, but when radar did not confirm an object, he and the FAA later agreed those lights were probably from small villages diffused by thin clouds of ice crystals. [Center for Inquiry]centerforinquiry.s3.amazonaws.comCenter for Inquiry

Sceptical explanations are not perfectly tidy. They have to account for a dynamic pilot report, cockpit radar impressions, live controller concern, and the crew’s sense of proximity and motion. But they do identify real weaknesses in the extraordinary interpretation: non-confirming radar review, no visual confirmation by nearby aircraft, differing crew descriptions, and known perceptual traps in night flying.

Why Terauchi’s credibility is debated

Captain Terauchi was an experienced professional pilot, and the FAA interview notes do not portray the crew as impaired or frivolous. That is one reason the case attracted international attention. However, pilot experience does not make a witness immune to misperception, especially in darkness, at altitude, with ambiguous lights and a high workload.

The controversy around Terauchi is not simply that he reported a UFO. FAA notes include an addendum from a confidential Japan Airlines source stating that this was not his first sighting of an unidentified aircraft. Klass went further, describing Terauchi as a “UFO repeater” and noting his apparent belief that UFOs were extraterrestrial, including his use of language such as “spaceship” and “mothership”. [The Black Vault Documents]documents.theblackvault.comThe Black Vault Documents

That affects evidential weight, not personal honesty. A witness can be sincere and still interpret ambiguous lights through an existing expectation. The strongest version of the case treats Terauchi as a credible aviation witness for what he perceived; the weaker version treats his most dramatic conclusions about size, structure and intent as interpretations requiring independent corroboration.

What remains unresolved

The JAL 1628 sighting remains unresolved in a limited, careful sense: no single explanation has been universally accepted for every part of the crew’s experience. The FAA file confirms that the crew reported unusual lights, that controllers took the report seriously, that military radar operators at moments discussed possible returns, and that the aircraft manoeuvred in response. Those are real features of the case, not later folklore. [The Black Vault Documents]documents.theblackvault.comThe Black Vault Documents

But the case is not unresolved in the stronger sense often implied online: it is not a clean, multi-sensor confirmation of a giant craft following a 747 for nearly an hour. The later FAA radar review did not confirm targets near JAL 1628; Fairbanks Approach reported no radar returns at a key moment; United 69 and a USAF C-130 did not see the reported object; and the crew’s later descriptions diverged on shape and certainty. The Black Vault Documents [Center for Inquiry]centerforinquiry.s3.amazonaws.comCenter for Inquiry

The most defensible conclusion is that JAL 1628 is a high-value case for studying how aviation UFO reports develop under real operational conditions. It combines trained witnesses, live air-traffic handling, preserved documentation, disputed radar interpretation, and plausible perceptual explanations. Its significance lies less in proving an extraordinary craft than in showing why serious UFO cases can be both genuinely puzzling and evidentially fragile.

Endnotes

1. Source: archives.gov
   Link: https://www.archives.gov/research/topics/uaps/rg-collections

2. Source: documents.theblackvault.com
   Title: The Black Vault Documents
   Link: https://documents.theblackvault.com/documents/ufos/jal1628/733667-001-012.pdf

3. Source: centerforinquiry.s3.amazonaws.com
   Title: Center for Inquiry
   Link: https://centerforinquiry.s3.amazonaws.com/wp-content/uploads/sites/29/1987/07/22165315/p04.pdf

4. Source: documents.theblackvault.com
   Title: The Black Vault Documents
   Link: https://documents.theblackvault.com/documents/ufos/jal1628/733667-001-005.pdf

5. Source: upi.com
   Title: Controller confirms UFO sighting
   Link: https://www.upi.com/Archives/1986/12/30/Controller-confirms-UFO-sighting/4431536302800/

6. Source: upi.com
   Title: JAL pilot describes UFO
   Link: https://www.upi.com/Archives/1986/12/31/JAL-pilot-describes-UFO/6559536389200/

7. Source: archives.gov
   Link: https://www.archives.gov/research/topics/uaps/textual-and-microfilm

8. Source: catalog.archives.gov
   Link: https://catalog.archives.gov/id/733667

9. Source: faa.gov
   Link: https://www.faa.gov/sites/faa.gov/files/2022-09/fy21-oct20-apr21.xlsx

10. Source: faa.gov
    Link: https://www.faa.gov/sites/faa.gov/files/2022-09/fy18-jun18-sep18.xlsx

11. Source: faa.gov
    Link: https://www.faa.gov/foia/electronic_reading_room/logs/afn-afn-20250121-fy23-oct22-mar23.xlsx

12. Source: faa.gov
    Title: afn afn 20250303 fy24 oct23 mar24.xlsx
    Link: https://www.faa.gov/foia/electronic_reading_room/logs/afn-afn-20250303-fy24-oct23-mar24.xlsx

13. Source: faa.gov
    Link: https://www.faa.gov/foia/electronic_reading_room/logs/afn-afn-20250121-fy23-apr23-sept23.xlsx

14. Source: faa.gov
    Title: grants 2001.xls
    Link: https://www.faa.gov/sites/faa.gov/files/airports/aip/grant_histories/grants-2001.xls

15. Source: upi.com
    Link: https://www.upi.com/Archives/1986/12/31/A-veteran-pilot-whose-UFO-sighting-was-confirmed-on/2755536389200/

16. Source: archive.org
    Link: https://archive.org/details/jal1628

17. Source: theblackvault.com
    Title: the vault files 1986 alaska jal flight 1628
    Link: https://www.theblackvault.com/casefiles/the-vault-files-1986-alaska-jal-flight-1628/

18. Source: documents.theblackvault.com
    Link: https://documents.theblackvault.com/documents/ufos/jal1628/733667-001-015.pdf

19. Source: documents.theblackvault.com
    Link: https://documents.theblackvault.com/documents/ufos/jal1628/733667-001-003.pdf

20. Source: documents.theblackvault.com
    Link: https://documents.theblackvault.com/documents/ufos/jal1628/733667-02-001.pdf

21. Source: as.amphilsoc.org
    Link: https://as.amphilsoc.org/repositories/2/resources/2894

22. Source: cdn.centerforinquiry.org
    Link: https://cdn.centerforinquiry.org/wp-content/uploads/sites/29/1987/07/22165315/p04.pdf

Additional References

1. Source: youtube.com
   Title: Pilot Reports Massive UFO Mothership Twice the Size of Aircraft Carrier
   Link: https://www.youtube.com/watch?v=VXbe4Z7oP00
   Source snippet

   Boeing 747 Followed by a UFO | An Out Of This World Encounter | Japan Air Lines Flight 1628...

2. Source: youtube.com
   Link: https://www.youtube.com/watch?v=h4wK6LTERss
   Source snippet

   Pilot Reports Massive UFO Mothership Twice the Size of Aircraft Carrier...

3. Source: skepticalinquirer.org
   Link: https://skepticalinquirer.org/authors/philip-j-klass/

4. Source: skeptoid.com
   Link: https://skeptoid.com/episodes/1005

5. Source: commons.wikimedia.org
   Link: https://commons.wikimedia.org/wiki/File%3ANews_media_contacts_to_FAA%2C_page_16%28Original_caption-_JAL-1628%28UFO%29%2C_FAA_Press_Conference%2C_March_5%2C_1987%2C_Anchorage%2C_Alaska%29%2833421621511%29.jpg
   Published: March 5, 1987

6. Source: reddit.com
   Link: https://www.reddit.com/r/skeptic/comments/168r8du/has_anyone_watched_brian_dunnings_from_skeptoid/

7. Source: reddit.com
   Link: https://www.reddit.com/r/ufo/comments/110x5o3/huge_ufo_in_the_skies_over_alaska_witnessed_by/

8. Source: skepticalinquirer.org
   Link: https://skepticalinquirer.org/wp-content/uploads/sites/29/2019/03/Issue-04-8.pdf

9. Source: skeptoid.com
   Link: https://skeptoid.com/episodes/703

10. Source: mykss.com
    Link: https://mykss.com/en/article/japan-airlines-flight-1628-alaska-ufo-encounter-1986-eyewitness-testimonies-cross-examined-again/