Japan Airlines Flight 1628 encounter
Also known as: JAL 1628, Japan Air Lines Flight 1628, JAL 1628 Alaska UFO incident, Captain Kenju Terauchi encounter, JA8047 incident
This dossier is a research synthesis sourced using AI, not documentary evidence. Use the reference leads to check important claims.
Japan Air Lines (usually rendered Japan Airlines in later English-language writing) Flight 1628 was a scheduled Boeing 747 freighter service from Paris to Tokyo, routed through Anchorage, Alaska. On 17 November 1986 its three-person Japanese flight crew reported unusual lights while crossing eastern and central Alaska at night. The event is generally associated with the region around Fort Yukon, Fairbanks, and the route toward Anchorage, although later accounts often compress the geography into “near Fairbanks” or “over Alaska.” It is not a Japanese territorial sighting: its Japan-related features are the airline, aircraft registration often given as JA8047, and Japanese crew. The event is one of the most frequently cited late twentieth-century aviation-UAP cases because it combined a detailed cockpit report, real-time radio contact with air-traffic control, FAA follow-up, and a later public controversy about radar. The basic narrative is reasonably stable at a high level but should not be mistaken for a settled technical reconstruction. Captain Kenju Terauchi, with first officer Takanori Tamefuji and flight engineer Yoshio Tsukuda generally identified as the other crewmen, initially reported two bright objects in front of or to the left of the freighter. The captain later described a much larger illuminated presence that appeared to move with, or remain near, the aircraft. His subsequent descriptions famously used immense apparent dimensions and unusual shapes, commonly summarized as a walnut- or shell-like form, a “mother ship,” or an object whose lights seemed to revolve. Such language records a witness’s estimate under difficult night-flight conditions; it does not provide a measured object size, range, or physical morphology. At least some of the report’s more dramatic imagery comes from post-event interviewing and retelling rather than from a single contemporaneous statement, a distinction that needs document-by-document checking. Controllers at Anchorage Air Route Traffic Control Center communicated with the crew and reportedly considered radar information, including primary-radar-like returns at some points. The crew was asked about maneuvering; a turn was apparently made in an attempt to determine whether the observed object remained associated with the aircraft. Later narratives often say that radar “confirmed” a huge craft shadowing the 747. That is much stronger than the cautious conclusion warranted by the recalled record. The important question is not merely whether an intermittent extra return occurred, but which radar system produced it, what its plot-processing and coverage limitations were, whether its timing and position correlated with the visual report, whether known traffic or clutter was excluded, and whether a controller’s conversational remark was later elevated into a formal finding. Secondary surveillance data reliably identify a cooperating transponder-equipped aircraft, while an uncorrelated primary return has substantially different evidential meaning. The available recollection suggests ambiguity rather than an unambiguous multi-sensor track. FAA interest and the later work of aviation psychologist and UFO researcher Richard F. Haines gave the episode unusual durability. Haines conducted or circulated materials concerning crew testimony and FAA-related records, and the case entered UFO books, television programs, websites, and later UAP compilations. That transmission history matters: the case is commonly marketed as a “radar-visual” encounter, a label that can imply more coherent instrument corroboration than primary records may support. It also became a pilot-credibility narrative, emphasizing Terauchi’s experience and calm professional status. Professional experience is relevant to the seriousness of the report, but it cannot by itself solve problems of astronomical identification, angular-size estimation, visual autokinesis, cockpit-window reflections, navigation-light geometry, radar clutter, or memory change after repeated interviews. Several ordinary or non-extraordinary explanatory families need to remain active in any investigation. Bright celestial bodies, especially Jupiter and other conspicuous night-sky lights, have been proposed in connection with portions of the sighting; this requires reconstruction of the precise time, aircraft heading, altitude, weather, window orientation, and celestial azimuth and elevation. Distant aircraft, military traffic, satellites or re-entering debris, and ground lights altered by atmospheric conditions are other possibilities, though each has to fit the reported movement and route rather than merely being listed. A cloud layer, ice crystals, haze, auroral or other atmospheric illumination, and reflection of cockpit or instrument lights could change apparent brightness and depth cues. The extraordinary apparent size of the larger object may principally reflect an unknown distance; without range, converting angular appearance into dimensions is invalid. Radar alternatives include weather, ground/terrain effects, multipath, anomalous propagation, electronic interference, and the ordinary difficulties of interpreting sparse long-range primary returns. None of these alternatives is established here; equally, an unresolved record is not positive verification of nonhuman craft. For cross-case comparison, JAL 1628 is especially useful as a case of layered evidence rather than as an evidential monolith. It offers three crew positions, contemporaneous ATC interaction, a reported maneuver intended to test pacing, subsequently discussed radar, an institutional review, and a vigorous retrospective media life. Each layer has a different chain of custody and different vulnerabilities. Cockpit perceptions may be sincere yet uncertain in range; ATC recordings preserve communication but not necessarily visual truth; radar data require system-specific interpretation; reports and diagrams record a witness’s account at a particular time; later interviews may be richer but shaped by questioning and publicity. A strong research reconstruction should therefore build a minute-by-minute table that separates direct crew observations, controller statements, recorded data, later investigator interpretations, and claims made only in secondary UFO literature. It should also distinguish the initial two-light report from the later large-object narrative rather than presuming they were the same phenomenon.
- Words
- 4,079
- Observations
- 12
- Reference leads
- 6
- Validation score
- 100/100
Ordered chronology and reconstruction points
The flight was a Japan Air Lines Boeing 747 cargo operation traveling Paris–Anchorage–Tokyo on the evening of 17 November 1986. The flight was in U.S. airspace over Alaska, not on a route “from Anchorage to Paris,” a reversal that appears in some casual retellings. Its onward destination, routing, departure and arrival times, call sign, registration, altitude, headings, and the respective times used by aircraft and ATC should be taken from dispatch, flight-plan, and FAA records rather than from summaries. The cold, dark, sparsely lit Alaskan environment is relevant both to the perceived isolation of the event and to visual range-estimation difficulties.
During the eastern-Alaska portion of the flight, the crew reported two unusually bright lights. Recalled accounts place them ahead of the 747 and/or to its left, with a perceived relationship to the aircraft that changed over time. Captain Terauchi is normally the principal descriptive witness; the degree to which the first officer and flight engineer independently saw every reported feature is an essential but frequently blurred issue. A reconstruction should preserve who said what, whether the observation was unaided or through a specific window, and whether each crewmember made an independent contemporary report.
The crew contacted Anchorage-area air-traffic services, and controllers discussed whether they could see corresponding traffic or returns. Accounts describe an ATC-requested or ATC-discussed maneuver, often a turn, intended to test the apparent companion’s relation to the 747. That operational element is significant because a change of heading can help distinguish a fixed astronomical object, a distant object, another aircraft, or an internal reflection. It is not a controlled experiment: a pilot’s perception, the relative motion of a distant light, and the time delay in radar display processing can all complicate interpretation.
At a later stage of the reported encounter, Terauchi described a larger object or luminous assemblage. Later literature commonly assigns a duration of roughly fifty minutes to the broader episode, but the start and end points may combine observations, radio discussions, and later recollection. The airplane continued to Anchorage and landed safely; no collision, wake-turbulence event, equipment failure, structural damage, or reported injury is central to the remembered case record. The absence of such effects does not explain the lights, but it limits claims about close physical interaction.
After landing, crew accounts were documented and the FAA reviewed the incident. Haines later became prominent in organizing, analyzing, or publicizing material. Through the late 1980s and following decades, the episode moved from official paperwork and aviation reporting into UFO-specialist literature and mass-media formats. Retellings increasingly foregrounded a giant craft, a military-radar pursuit, and an official “unexplained” outcome. These may be interpretations of parts of the file, not a substitute for an agency technical conclusion.
People, institutions, aircraft, and setting
Captain Kenju Terauchi is the central named witness and is commonly portrayed as an experienced long-haul cargo pilot. First officer Takanori Tamefuji and flight engineer Yoshio Tsukuda are generally named as the other two members of the crew. Their shared aircraft environment makes this a multiple-witness report, but not three wholly independent observations in the forensic sense: they could communicate, view the same scene from nearby positions, and influence one another’s attention. Differences in their later statements, if any, should be recorded rather than treated as defects or silently harmonized.
The operational institutions were Japan Air Lines, Anchorage air-traffic-control facilities including Anchorage ARTCC, and the FAA. Military radar or military personnel are often mentioned in derivative narratives. Researchers should establish exactly which military unit, system, operator, and record is actually documented before treating military involvement as fact. “FAA investigated” can likewise mean anything from routine collection and review of reports to a formal technical study; the surviving correspondence and internal memoranda should determine the scope.
The setting was high-altitude night flight across Alaska in November: potentially very dark surroundings, extensive snow-covered terrain, limited ground-light reference, winter weather, and large distances. Such a setting can make lights unusually salient and give few stable cues for distance, speed, or scale. It also lies in airspace where military, civil, weather, and long-range surveillance arrangements can be more complex than a simple single-radar narrative suggests. Location labels such as Fort Yukon, Fairbanks, Mount McKinley/Denali, and Anchorage may refer to different stages of a long route rather than a single fixed encounter point.
Richard F. Haines, a former NASA research scientist and aviation-oriented UFO investigator, is a key transmission figure rather than an original eyewitness. His investigations and publications are valuable discovery leads because they may preserve interviews, drawings, and FAA correspondence. Their interpretive framing must nevertheless be separated from the underlying records. The case later became commercially valuable to publishers, documentary producers, UFO conferences, and online content creators because a professional airline crew plus radar is a highly legible narrative formula.
Reported sensory, positional, and behavioral phenomena
The initial visual phenomenon is usually described as two bright or luminous objects/lights. Accounts vary in color, structure, placement, and motion, and some later descriptions attribute pulsation, changing intensity, or a regular arrangement of lights. The most defensible normalized description is therefore “two conspicuous lights perceived from the cockpit at night,” not two measured vehicles. Researchers should retrieve diagrams and the earliest crew interviews to determine whether features such as square windows, exhaust-like illumination, or rotating lights were contemporaneous details or later elaborations.
Terauchi’s later account involved a much larger apparently illuminated object. Popular summaries characterize it as very large, sometimes using an extraordinary comparison to an aircraft carrier or a much larger “mother ship.” Such phrases convey perceived scale, not instrument-derived dimensions. Apparent size is a product of angular extent and unknown range; an object can look enormous if assumed nearby, while a bright distant source can appear to occupy a psychologically imposing part of a dark visual field. No sound, physical contact, onboard instrument disruption, or unambiguous photographic evidence is reliably recalled as part of the core claim.
The reported behavior included apparent pacing, maintaining a relative position, and continuing after a heading change. These are strong phenomenological claims because they concern relative movement, but they need time-stamped aircraft headings and object bearings. A fixed celestial source can appear to shift with turns and can be misperceived as following; another aircraft may also maintain a broadly similar geometry without being close. Conversely, if reliable bearing changes remain inconsistent with fixed celestial positions and known traffic, that would sharpen rather than settle the anomaly.
Radio exchanges reportedly include the crew asking controllers about traffic and controllers discussing radar information. Communications are evidence that an unusual report was made in real time; they do not themselves identify the external source. The often-repeated claim of multiple independent radars tracking the same huge object remains disputed. It should be decomposed into radar site, radar type, exact timestamps, raw versus processed data, target quality, and correlation with both the aircraft and the crew’s stated bearing.
Investigation, source hierarchy, and testable methods
The highest-priority sources are FAA operational records: ATC voice recordings or transcripts, flight-progress strips, radar plots or retained data, controller statements, facility logs, weather records, and correspondence created close to the event. Japan Air Lines dispatch records, crew reports, aircraft maintenance records, and the original flight plan would provide an independent airline-side chronology. Availability, completeness, and provenance must be established; a transcript published by a researcher is not equivalent to the original recording, and a controller recollection years later is not equivalent to a contemporaneous log.
A technical review should reconstruct the 747’s position, altitude, ground speed, heading, and turn geometry at short intervals. It should then calculate astronomical bearings for bright planets, stars, moonlight, satellite passes, and any plausible re-entry. Meteorological analysis should include cloud, icing-crystal conditions, visibility, auroral activity, and temperature inversions. Known civil and military traffic needs examination, while recognizing that absence from a public aircraft database does not prove absence from the airspace. This is how conventional explanations become testable propositions rather than generic dismissals.
Radar analysis needs special care. Secondary surveillance radar can show the JAL aircraft’s transponder response and does not automatically detect an unknown companion. Primary radar can detect non-cooperative returns but is subject to clutter, propagation anomalies, interpolation, beam geometry, and limited persistence. A legitimate conclusion requires comparison of raw or nearest-raw plots, sensor configuration, weather, target histories, and controller display procedures. A screen observation reported in a conversation should not be recast as a continuously tracked object with known size.
The FAA’s ultimate language should be quoted only after checking the relevant original document. Researchers should avoid both poles: asserting that the FAA verified an alien craft, or claiming officials disposed of the whole event through a single demonstrated mundane cause. The likely current evidential state is that real people made a real report, official personnel responded operationally, and the relationship among visual perceptions, any extra radar returns, and candidate ordinary sources remains contested.
Disagreements, alternative explanations, and evidential limits
One major dispute is the degree of crew agreement. Later accounts center on Terauchi’s vivid testimony, sometimes leaving readers with the impression that every crewmember saw the same structured giant object for the same duration. The original reports may show a more qualified distribution of perception. This does not imply bad faith; in an aircraft cockpit, viewing direction, task workload, seat position, expectation, and visual acuity differ. It does mean the dossier should treat “the crew reported” and “the captain reported” as analytically distinct statements.
A second dispute concerns astronomy. Jupiter has been suggested as an explanation for at least part of the visual report in skeptical analyses, potentially accompanied by another bright source. The proposal is plausible enough to test but cannot be accepted on name recognition alone. A correct assessment requires local horizon geometry and timing; a planet’s fixed celestial motion has predictive value, whereas a vague claim that it was “visible that night” does not. Bright-source misidentification can coexist with a separate unexplained radar or traffic issue, so a single explanation need not cover every reported detail.
A third dispute concerns radar. Proponents emphasize primary returns and controller interest as independent corroboration. Critics argue that the recorded returns were intermittent, insufficiently correlated, possibly ordinary traffic or radar artifact, and not evidence of a giant structured object. Both positions can overreach if they do not reproduce the system data. Radar is not a direct visual camera and cannot measure the reported object’s apparent visual size. The correct status is disputed correlation, not confirmed tracking of a nonhuman vehicle.
Finally, the case’s public meaning has been shaped by institutional ambiguity. Aviation agencies frequently focus on safety and traffic separation, not ontological identification; a lack of a conclusive identification can be described in sensational media as official admission of mystery. Conversely, an agency’s reluctance to endorse an extraordinary interpretation does not establish that every witness was mistaken. The neutral conclusion is bounded uncertainty: the event is documented as a report and response, while its external cause is not established by the recalled evidence.
Transmission history, genre, and commercial influence
The event belongs to the “pilot plus radar” genre of UFO/UAP storytelling. That genre uses professional authority, recorded communications, and technical language to distinguish itself from casual ground sightings. It is rhetorically powerful: a commercial captain is presented as trained, radar appears objective, and government involvement implies validation. Cross-case work should therefore assess not only data quality but the recurring narrative package—experienced aircrew, large luminous object, controller uncertainty, radar hint, and later official ambiguity.
Haines’s work is a central bridge between operational records and the UFO research community. Later authors have republished diagrams, selected remarks, radar claims, and portions of FAA materials, often without maintaining a clear boundary between original records, Haines’s interpretations, and an author’s embellishment. Television documentaries and internet videos tend to favor the enormous-object comparison and to condense a complicated sequence into a direct chase. Such condensation can erase contradictory crew observations, uncertainty in range, and the difference between a controller query and a radar conclusion.
The airline’s national identity also contributed to circulation. English-language audiences sometimes frame it as a Japanese airline’s encounter with a U.S. government radar system, producing an international-authority narrative even though the location was Alaska. Errors introduced in transmission include calling the carrier Air France, calling the case an Alaska Airlines event, placing it over Japan, and treating all references to Fairbanks, Fort Yukon, and Anchorage as the same location. These errors are useful markers for tracing derivative rather than primary sourcing.
Commercial incentives do not mean the incident was fabricated. They do mean repeated retelling can stabilize compelling imagery, reward certainty, and select the most dramatic version of a witness’s account. A useful citation audit would tag each claim by source type: crew report, controller transcript, FAA internal or public document, investigator interview, book, magazine, broadcast documentary, or web summary. It should also note translation issues, since Japanese crew testimony may have passed through English-language interpretation.
Cross-case connections and reusable motifs
This case shares the motif of an aircrew observing lights at night while ATC conducts a safety-oriented inquiry. Comparable cases should be coded for number and role of witnesses, whether the report was made in real time, whether a maneuver was attempted, whether visual bearings were recorded, and whether the aircraft or crew experienced any operational consequences. The distinctive JAL 1628 combination is a long-haul cargo 747, winter Alaskan setting, and later radar controversy—not simply the presence of a pilot witness.
A second transferable motif is disputed sensor corroboration. Many UAP cases acquire authority through claims that radar, military sensors, or multiple stations “confirmed” a target. For comparison, distinguish raw detection, operator observation, display track, formal correlation, and retrospective assertion. Record whether the sensor data were retained, independently analyzed, and tied to a particular visual bearing. JAL 1628 is a cautionary benchmark because later claims of certainty may exceed what ambiguous primary radar can establish.
A third motif is apparent pacing by lights of unknown range. It occurs across aviation, maritime, road, and ground-observer reports and often produces very large inferred size estimates. Comparative research should capture environmental reference cues, cockpit/window reflections, flight heading changes, weather, celestial candidates, and observer attention. The motif does not decide between mundane and unknown causes; it highlights a repeatable perceptual and geometric problem.
A final connection is the post-event professional-witness narrative. Pilot credentials, institutional records, and later public interviews can confer prestige while also amplifying a selected account. Cases should be compared for the gap between contemporaneous operational language and later narrative detail, for incentives created by books and media, and for whether a claimed official investigation reached an actual technical conclusion or merely retained a report.
Limits of this recalled dossier
This dossier is a research map, not a documentary finding. Specific times, exact headings, weather, route segments, radar sites, the availability of recordings, and the wording of FAA conclusions all require verification. The title and date are high-confidence identifiers; exact technical claims are not. In particular, no conclusion should be drawn here that multiple radars tracked one object continuously, that an object had a known gigantic physical size, or that military authorities confirmed an extraordinary craft.
The case should not be collapsed into either credulous or dismissive shorthand. It is reasonable to say that an airline crew made an unusual report and that air-traffic authorities engaged with it. It is not warranted to claim proof of extraterrestrial, nonhuman, or paranormal activity. Nor is it methodologically sound to assume that a suggested planet, aircraft, or radar artifact conclusively resolves the entire sequence without a time-resolved reconstruction. The evidentially responsible endpoint may remain partly unresolved.
Priority verification questions are: What did each crewmember report immediately after the event? What exactly did the ATC recording say? Which radar system, if any, displayed an uncorrelated return, and at what times? What were the aircraft’s maneuver and bearing geometry? Which celestial and traffic candidates fit those times? What did the FAA actually conclude in writing? Answering these questions will make this a useful comparative aviation case even if no single external cause can be identified.
Chronology
Scheduled cargo operation enters Alaska route
JAL Flight 1628, a Boeing 747 freighter traveling Paris–Anchorage–Tokyo, crossed Alaskan airspace on a night leg. Exact route, registration, and timing require airline and FAA records.
documentedInitial lights reported
The crew reportedly observed two bright lights from the cockpit in eastern Alaska, commonly associated with the Fort Yukon/Fairbanks region.
reportedAir-traffic communications and radar discussion
Anchorage-area controllers communicated with the flight about the observation and discussed traffic/radar-related information. The exact nature of any extra return is disputed.
reportedLarge illuminated object described
Captain Terauchi later described a much larger luminous object or assemblage, with apparent pacing and changing positional relationship to the aircraft.
reportedManeuver used to assess apparent companion
Accounts describe a turn or other heading change intended to see whether the observed phenomenon remained with the aircraft; exact geometry requires verification.
reportedArrival at Anchorage and reporting
The flight landed safely at Anchorage, followed by crew reporting and aviation-authority attention. No core account identifies damage or injury.
documentedFAA review and later investigator circulation
FAA materials and subsequent work associated with Richard F. Haines became central to the case’s public record and debate.
documentedMedia canonization
Books, documentaries, and online summaries increasingly presented the case as a major radar-visual encounter, sometimes overstating technical corroboration.
documentedPeople and roles
Kenju Terauchi
Captain of JAL Flight 1628; principal named eyewitnessCommonly associated with the most detailed later descriptions of the lights and larger object. His exact contemporaneous and later statements should be compared.
Takanori Tamefuji
First officerGenerally named as a cockpit witness; the scope of his independent observations requires primary-source checking.
Yoshio Tsukuda
Flight engineerGenerally named as the third crew member; distinguish his observations from those of the captain.
Anchorage Air Route Traffic Control Center personnel
Air-traffic controllersReceived and responded to the report. Individual identities, statements, and system access should be established from original records.
Federal Aviation Administration
U.S. civil aviation authorityAssociated with collection/review of operational information; the precise form and conclusion of its review need verification.
Richard F. Haines
Aviation psychologist and later UFO investigatorImportant secondary investigator and transmitter of case material, not an original airborne witness.
Japan Air Lines / Japan Airlines
Aircraft operatorAirline naming varies by source and era. Dispatch, crew, and maintenance materials are potentially high-value primary sources.
Connections to explore
Nighttime professional-aircrew report
A trained cockpit crew reported unusual lights during an operational flight and communicated with ATC in real time. Compare witness roles, cockpit layout, workload, and independence of observations.
Suggested search: commercial pilot UAP reports nighttime ATC transcript cockpit crewVisual report plus ambiguous radar
The case is a benchmark for separating a reported visual observation from primary-radar-like returns, secondary surveillance, controller impressions, and later claims of corroboration.
Suggested search: aviation UAP primary radar visual correlation controller transcript analysisApparent pacing and extreme size inference
Lights of unknown range can seem to follow an aircraft and encourage huge size estimates. Compare documented bearings, turns, celestial geometry, and range assumptions.
Suggested search: pilot sighting apparent pacing celestial misidentification angular sizeInstitutional ambiguity becomes media proof
Operational FAA response and an unresolved identification were transformed in later circulation into a stronger narrative of official confirmation.
Suggested search: UFO case transmission FAA records documentary exaggeration radar confirmationArctic or remote-flight perceptual setting
Darkness, few external reference points, winter atmosphere, and complex surveillance coverage recur in remote-route aviation cases.
Suggested search: Alaska aviation unusual lights radar anomalous propagation winter nightUnretrieved reference leads
FAA records concerning Japan Air Lines Flight 1628
Federal Aviation Administration / Anchorage air-traffic facilities · Operational recordings, correspondence, radar-related records, and investigative file
Primary evidence for chronology, controller statements, and the precise scope of any official review.
Suggested search: FAA Japan Air Lines Flight 1628 November 17 1986 Anchorage ARTCC recordsJapan Air Lines Flight 1628 crew and dispatch materials
Japan Air Lines / Japan Airlines · Airline operational records
Potentially establishes flight route, crew reports, dispatch sequence, maintenance status, and aircraft details independently of UFO literature.
Suggested search: Japan Air Lines JAL 1628 JA8047 November 1986 crew report AnchorageRichard F. Haines publications and case materials on JAL 1628
Richard F. Haines · Investigator report, interviews, and secondary analysis
A major pathway through which crew testimony and FAA-related material entered public discussion; assess against originals.
Suggested search: Richard F Haines JAL 1628 Alaska 1986 reportContemporary Alaska and aviation press coverage
Newspapers and trade press · Contemporaneous reporting
Useful for identifying what was publicly asserted before later narrative consolidation and for locating named officials.
Suggested search: Japan Airlines Flight 1628 Alaska November December 1986 newspaperAstronomical ephemeris and meteorological archives for 17 November 1986
Astronomical and weather-data institutions · Contextual technical records
Needed to test bright-planet, atmospheric, cloud, auroral, and visibility explanations against flight geometry.
Suggested search: Alaska 17 November 1986 weather Jupiter azimuth aviation routeAviation radar technical documentation for Anchorage-region facilities
FAA and radar-system technical sources · Technical manuals and radar-analysis records
Necessary to interpret any alleged primary returns without treating radar displays as direct images of objects.
Suggested search: Anchorage ARTCC radar system 1986 primary secondary surveillance coverage