Air France Flight 1628 Alaska encounter
Also known as: JAL Flight 1628 UFO, Japan Airlines Alaska incident, JAL Cargo Flight 1628 Alaska encounter
This dossier is a research synthesis sourced using AI, not documentary evidence. Use the reference leads to check important claims.
The canonical title is potentially misleading: the case is widely remembered as Japan Airlines or JAL Cargo Flight 1628, rather than as an Air France operation. It concerns a cargo Boeing 747 crew’s report of unusual illuminated objects during a November 1986 flight over Alaska, followed by contacts with air-traffic control and later discussion of radar records. The captain, Kenju Terauchi, became the principal public narrator and described lights, apparent maneuvering, and a very large dark form that seemed to accompany the aircraft. His two fellow crew members were generally reported as having observed at least some lights, although later accounts differ over what each man saw, how long they saw it, and whether they accepted the captain’s interpretation. The incident became important in UFO literature because it appears to combine pilot testimony, cockpit observation, controller involvement, primary-radar discussion, and later FAA correspondence. Those elements do not establish an extraordinary object. They instead create a case in which several imperfect evidence streams have been repeatedly joined together in retelling. Visual observations from a moving aircraft at night can be distorted by viewing angle, distance, atmospheric conditions, reflections, stars or planets, and other traffic. Primary radar can show transient or ambiguous returns, while the absence of a transponder-associated target prevents an easy identification but does not itself identify a cause. The public record is also filtered through interviews, advocacy literature, document releases, and summaries that may simplify technical qualifications. A careful treatment should preserve the reported fear and professional concern of the crew, while separating their perceptions from claims about the object’s physical nature. The underlying event remains unresolved in the limited sense that no universally accepted identification accounts for every recollected detail, but it is not verified evidence of a paranormal or extraterrestrial craft.
- Words
- 2,376
- Observations
- 11
- Reference leads
- 5
- Validation score
- 100/100
Chronology
On 17 November 1986, a Japan Airlines cargo Boeing 747 operating as Flight 1628 was reported to have been travelling through Alaskan airspace on a route involving Anchorage during the evening or night portion of its journey. Recalled summaries place the encounter near the Fairbanks region, though locations, headings, altitudes, and exact times should be checked against controller logs and flight records.
The crew reported seeing lights ahead of or alongside the aircraft and informed air-traffic control. The controller response reportedly included efforts to establish whether another aircraft or radar target was present, and the aircraft was offered or made changes in direction intended to test whether the perceived traffic remained in relation to the 747.
After landing, the crew’s experience entered an administrative and investigatory process involving FAA personnel and later media attention. The chronology after the flight is less linear than many summaries suggest, because radar discussion, official correspondence, interviews, and document circulation occurred at different times and were later treated as though they were a single contemporaneous evidentiary record.
During subsequent years, the incident was repeatedly retold in UFO books, television material, pilot-focused discussions, and online compilations. These retellings often foreground the alleged size of a mothership and the radar aspect, while giving less attention to variation among witnesses and uncertainty over what specific radar systems recorded.
People, Organisations, and Setting
The central witness was Captain Kenju Terauchi, the 747 commander, whose detailed account strongly shaped the case’s later identity. Recalled accounts name First Officer Takanori Tamefuji and flight engineer Yoshio Tsukuda as the other cockpit crew, but the precise spelling of names, their statements, and the degree of agreement should be verified from original records.
Japan Airlines, commonly described in this case as JAL Cargo, operated the flight. The relevant institutional setting also includes Anchorage-area air-traffic-control services and the Federal Aviation Administration, whose personnel were drawn into the immediate operational response and later review. No institutional involvement should be read as official confirmation that an anomalous craft was present.
The setting was remote Alaskan airspace at night, with few visual ground references and extensive distances between aircraft, airfields, and radar coverage. Such conditions can make visual range and bearing unusually difficult to estimate, especially when a crew is looking through cockpit windows from a high-altitude aircraft and interpreting lights against a dark sky.
The aircraft was a large cargo Boeing 747, not a small private aircraft. Its multi-person cockpit and radio contact provide more observational context than a solitary sighting, but common work space and communication can also influence how crew members attend to, label, and remember an ambiguous stimulus.
Reported Phenomena
The best-known reported feature was a group of bright lights described as being in front of the aircraft or near its flight path. Terauchi’s later descriptions commonly characterize some lights as unusually close, vivid, and apparently responsive to the aircraft, but such descriptions are witness reports rather than calibrated measurements of distance, size, speed, or acceleration.
Accounts describe the lights as white, amber, yellow, or otherwise warm-toned depending on the retelling. They were said to appear to move, to remain positioned relative to the 747, and at points to illuminate the cockpit area. Reported illumination can arise from a nearby source, but it can also be affected by glare, reflections, window geometry, adaptation to darkness, and the crew’s changing attention.
A later and especially dramatic element was the claimed appearance of a large, dark, disc-like or walnut-shaped mass behind or near the aircraft. It was alleged to be visible largely by its outline against the night sky rather than by clear surface detail. The reported immense scale depends on an assumed distance, which was not independently established.
The crew’s behavior reportedly included concern, repeated observation, radio reports, and willingness to test the sighting through course changes. The captain was described as alarmed but engaged in normal flight communication. There is no recalled basis for treating the crew’s stress response as evidence either for or against the external reality of a light source.
Some later presentations conflate the initial lights, the supposed large object, and alleged radar traffic into one continuously tracked object. That synthesis should be resisted unless contemporaneous transcripts demonstrate that the same position, time interval, and target identity were being discussed.
Investigation and Records
Air-traffic-control involvement is a major reason the incident attracted attention. Controllers reportedly checked traffic and discussed whether a radar return could be correlated with the crew’s position. The key research task is to distinguish primary radar, secondary-surveillance radar, transponder information, controller display interpretation, and any later reconstruction, because these systems answer different questions.
Recalled FAA-related discussion indicates that some reviewers believed there was radar-relevant information during part of the event, whereas other interpretations treated returns as weak, intermittent, uncorrelated, or compatible with ordinary radar ambiguity. A radar indication without an identified transponder target can justify further inquiry, but it does not on its own demonstrate a solid object, let alone an exotic vehicle.
The flight’s route, meteorological conditions, celestial conditions, military and civilian traffic, radar coverage, and raw communications are all more probative than later summaries. A rigorous review would compare timestamps from the cockpit report, controller tapes, radar plots, and any flight-data record before deciding whether separate observations align.
Later FAA correspondence and the circulation of material associated with aviation investigator John Callahan helped publicize the case. The existence of correspondence or a briefing shows that officials addressed a reported aviation event; it should not be treated as an institutional conclusion about alien visitation or paranormal causation.
Disputes and Competing Interpretations
The strongest disagreement concerns radar. Proponents often describe the case as radar-confirmed, while skeptical accounts stress that reports of returns may have been provisional, not continuously correlated, or attributed to normal artifacts and traffic. These positions can both arise when different writers rely on different systems, intervals, or versions of the records.
Witness agreement is also disputed. The captain’s elaborate account is usually much more detailed than accounts attributed to the other crew members. That gap may reflect genuinely different viewing positions or attention, later reticence, language and translation differences, or a broader divergence in interpretation; it prevents treating a single narrative as three identical testimonies.
Possible mundane explanations include distant aircraft lights, a bright astronomical object, ice-crystal or haze-related optical effects, ground or city lights seen at an unfamiliar angle, cockpit reflections, and misinterpretation of radar returns. No single alternative should be asserted as conclusively established without checking the time-specific evidence, but each illustrates why the extraordinary interpretation is not compelled.
Conversely, the event cannot be dismissed merely by saying that pilots are incapable of error. Pilots can provide valuable observations under operational pressure, yet expertise in flying does not automatically supply reliable night-time range estimation, object classification, or radar interpretation. The evidentiary question is narrower: which details are independently supported and which are later inference.
Transmission, Genre, and Commercial Influences
The case moved from operational reporting into UFO culture through pilot interviews, document discussions, books, lecture circuits, television programming, magazine articles, and later internet summaries. Each transmission stage favored a different type of material: aviation accounts emphasized procedure, UFO media emphasized spectacle, and online retellings often condensed the case into a claim that a jumbo jet was chased by a giant UFO.
The memorable image of a huge mothership has strong narrative value. It supplies scale, danger, and a technologically sophisticated witness, making it more likely to be selected for commercial nonfiction, broadcast dramatization, and algorithmically circulated content than the less vivid issues of radar qualification or conflicting crew emphasis.
Translation and paraphrase are material risks. Japanese-language witness remarks, English-language interviews, and later retellings may not preserve the same distinctions between seeing a light, inferring an object, and estimating its dimensions. Researchers should locate the earliest accessible wording before relying on polished quotations found in secondary sources.
The case belongs to a modern aviation-UFO genre in which professional witnesses and technical systems lend authority to a mystery. That genre does not make the report fraudulent, but it can encourage a dramatic coherence that exceeds the uneven, ambiguous nature of live flight operations.
Cross-Case Connections
For comparison, this case belongs with reports that combine a moving aircraft, night visual stimuli, radio contact, and alleged radar corroboration. Useful comparisons should be made at the level of evidence structure rather than by presuming a shared cause or a common class of craft.
Its most distinctive motif is the mismatch between a highly elaborated principal witness account and more limited corroboration from companions and instruments. Similar patterns arise in many anomalous-experience records and call for separate tracking of observation, interpretation, later memory, and publication history.
Another useful motif is the operational test: a controller or crew changes heading, altitude, or speed to determine whether a phenomenon remains associated with the aircraft. Such maneuvers can be informative, but apparent persistence may still result from a distant fixed light, a changing viewing geometry, or incomplete radar correlation.
The case should also be connected to institutional-handling narratives, in which routine documentation, uncertainty, and later requests for information are represented as either suppression or confirmation. Comparing the original administrative purpose of records with later claims made for them is essential.
Limits and Research Priorities
This dossier is a recalled synthesis, not a documentary reconstruction. It does not establish the precise route, duration, track geometry, weather, radar plots, or verbatim statements, and none of the suggested references has been consulted for this entry.
The canonical title’s Air France wording is itself a data-quality warning, because the familiar case attribution is to Japan Airlines Flight 1628. Future cataloguing should retain the supplied title for retrieval while clearly marking JAL as the reported operator and checking whether any separate Air France association was introduced through indexing error.
Priority sources for verification are contemporaneous controller communications, radar-system documentation, FAA memoranda with provenance, the crew’s earliest signed or recorded statements, meteorological data, flight records, and a complete account of known traffic. Later books and documentaries are valuable for tracing transmission but should not silently replace primary operational records.
The appropriate conclusion is unresolved identification under uncertain evidence, not verified paranormal contact. A well-supported mundane explanation may account for some or all elements, and an unexplained remainder, if any, would still be a limit of the available evidence rather than proof of an extraordinary cause.
Chronology
Reported Alaskan flight encounter.
JAL Cargo Flight 1628’s crew reported unusual lights while operating over Alaska and contacted air-traffic control.
reportedController and radar response.
Controllers reportedly checked for traffic and considered radar information while communicating with the aircraft.
reportedFAA review and correspondence.
FAA personnel and associated aviation officials reportedly reviewed aspects of the report and generated material later cited in discussions of the case.
approximatePublic UFO-case circulation.
Pilot accounts, official-document claims, and radar interpretations were circulated through UFO literature and media.
documentedCondensed popular retellings.
Online summaries increasingly presented the encounter as a radar-confirmed giant-UFO chase, often without preserving technical uncertainty.
documentedPeople and roles
Kenju Terauchi.
Captain and principal public witness.He is widely associated with the most detailed descriptions of the lights and large dark form, but the exact wording requires primary-source checking.
Takanori Tamefuji.
First officer, as named in recalled accounts.He is commonly identified as a cockpit witness, though the scope of his agreement with the captain should be separately verified.
Yoshio Tsukuda.
Flight engineer, as named in recalled accounts.He is commonly identified as the third cockpit crew member, with later summaries varying on his observations.
Japan Airlines or JAL Cargo.
Reported aircraft operator.The operational designation and exact flight-routing details require checking against company and aviation records.
Federal Aviation Administration.
United States aviation regulator and later record holder.FAA involvement concerns operational reporting and review, not a recalled finding that the object was extraordinary.
Anchorage-area air-traffic-control personnel.
Operational controllers.They reportedly communicated with the aircraft and evaluated available traffic and radar information.
John Callahan.
Later FAA-associated figure in public accounts.He is frequently mentioned in relation to later discussion and circulation of FAA material, which should be verified in context.
Connections to explore
Aviation witness authority.
The report gains credibility in popular treatment from professional flight crew involvement, while still requiring scrutiny of perceptual conditions and evidence quality.
Suggested search: pilot UFO cases night flight perception aviation witness reliability.Visual report plus radar ambiguity.
The case is useful for separating visual testimony from primary radar, secondary radar, and controller interpretation.
Suggested search: UFO cases primary radar secondary radar controller correlation.Relative-motion illusion.
Apparent pacing or following can occur when an observer in a moving aircraft views a distant light with changing geometry.
Suggested search: aviation night flying apparent motion distant lights visual illusion.Principal-witness amplification.
A vivid captain narrative alongside less detailed companion testimony is a useful cross-case pattern for studying memory and transmission.
Suggested search: UFO case witness discrepancy principal witness retelling.Institutional-document mythology.
Later readers may treat routine inquiry, memos, and incomplete technical records as proof of either confirmation or concealment.
Suggested search: FAA UFO records institutional handling document interpretation.Unretrieved reference leads
FAA material concerning Japan Airlines Flight 1628.
Federal Aviation Administration. · Official correspondence and operational records.
Suggested for establishing the scope of FAA review, controller involvement, and technical qualifications around radar discussion.
Suggested search: FAA JAL Flight 1628 Alaska 1986 correspondence radar.Air-traffic-control communications and radar records for the 17 November 1986 incident.
Anchorage-area air-traffic-control services. · Operational records.
Suggested for reconstructing timestamps, controller statements, known traffic, and the distinction between radar systems.
Suggested search: JAL 1628 November 17 1986 Anchorage ATC tapes radar records.Statements by the Flight 1628 crew.
Kenju Terauchi, Takanori Tamefuji, and Yoshio Tsukuda. · Witness statements and interviews.
Suggested for comparing the earliest available accounts and assessing agreement among cockpit crew members.
Suggested search: Kenju Terauchi Takanori Tamefuji Yoshio Tsukuda Flight 1628 statements.Analysis associated with John Callahan’s discussion of the incident.
John Callahan. · Later aviation-administrative account.
Suggested for tracing how FAA-related material was publicly characterized and separating recollection from original documentation.
Suggested search: John Callahan JAL Flight 1628 FAA Alaska.Contemporary weather, traffic, and astronomical data for Alaska on 17 November 1986.
Relevant meteorological, aviation, and astronomical record holders. · Contextual technical records.
Suggested for testing ordinary explanations involving atmospheric conditions, traffic, and visible celestial objects.
Suggested search: Alaska Fairbanks 17 November 1986 weather astronomical sky aviation traffic.