PDA

View Full Version : Japan Air Lines flight 1628 incident



airdog07
January 13th, 2014, 03:21 PM
Japan Air Lines flight 1628 incident From Wikipedia, the free encyclopedia
Jump to: navigation (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#mw-navigation), search (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#p-search)
Japan Air Lines flight 1628 was a UFO (https://en.wikipedia.org/wiki/UFO) incident that occurred on November 17, 1986 involving a Japanese (https://en.wikipedia.org/wiki/Japan) Boeing 747 (https://en.wikipedia.org/wiki/Boeing_747) cargo aircraft (https://en.wikipedia.org/wiki/Cargo_aircraft). The aircraft was en route from Paris (https://en.wikipedia.org/wiki/Paris) to Narita (https://en.wikipedia.org/wiki/Narita,_Chiba), Tokyo[1] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-JapanToday-1) with a cargo of Beaujolais (https://en.wikipedia.org/wiki/Beaujolais_%28wine%29) wine.[2] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-Herald-2) On the Reykjavík (https://en.wikipedia.org/wiki/Reykjav%C3%ADk) to Anchorage (https://en.wikipedia.org/wiki/Anchorage) section of the flight, at 5:11 PM over eastern Alaska (https://en.wikipedia.org/wiki/Alaska), the crew first witnessed two unidentified objects to their left. These abruptly rose from below and closed in to escort their aircraft. Each had two rectangular arrays of what appeared to be glowing nozzles or thrusters, though their bodies remained obscured by darkness. When closest, the aircraft's cabin was lit up and the captain could feel their heat in his face. These two craft departed before a third, much larger disk-shaped object started trailing them, causing the pilots to request a change of course.[3] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-Lawhon-3) Anchorage Air Traffic Control (https://en.wikipedia.org/wiki/Air_Traffic_Control) obliged and requested an oncoming United Airlines (https://en.wikipedia.org/wiki/United_Airlines) flight to confirm the unidentified traffic, but when it and a military craft sighted JAL 1628 at about 5:51 PM, no other craft could be distinguished.[3] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-Lawhon-3) The sighting of 50 minutes[4] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-future-4) ended in the vicinity of Mt. McKinley (https://en.wikipedia.org/wiki/Mount_McKinley).[5] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-Harper-5)[6] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-haines-6)


Observationhttps://upload.wikimedia.org/wikipedia/commons/thumb/d/df/USA_Alaska_location_map.svg/360px-USA_Alaska_location_map.svg.png (https://en.wikipedia.org/wiki/File:USA_Alaska_location_map.svg)



Locations of the Flight 1628 and subsequent incidents
The first stage of the sighting occurred from point A to B, where two objects were observed.[7] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-7) Two and a half months later, Flight AS-53 recorded an unidentified object near McGrath, and a military plane observed an object between Elmendorf and Eielson air force bases.


On November 17, 1986, the Japanese crew of a JAL (https://en.wikipedia.org/wiki/Japan_Airlines) Boeing 747 (https://en.wikipedia.org/wiki/Boeing_747) cargo freighter witnessed three unidentified objects after sunset, while flying over eastern Alaska (https://en.wikipedia.org/wiki/Alaska), USA. The objects seemed to prefer the cover of darkness to their left, and to avoid the brighter skies to their right.[8] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-Terauchi-8) At least the first two of the objects were observed by all three crew members: Captain Kenju Terauchi, an ex-fighter pilot (https://en.wikipedia.org/wiki/Fighter_pilot) with more than 10,000 hours flight experience,[1] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-JapanToday-1) in the cockpit's left-hand seat; co-pilot (https://en.wikipedia.org/wiki/First_Officer_%28civil_aviation%29) Takanori Tamefuji in the right-hand seat; and flight engineer (https://en.wikipedia.org/wiki/Flight_engineer) Yoshio Tsukuba.
The routine cargo flight entered Alaska on auto-pilot, cruising at 565 mph (909 km/h) at an altitude of 35,000 ft (11,000 m).[5] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-Harper-5) At 5:09 PM, the Anchorage (https://en.wikipedia.org/wiki/Anchorage) ATC (https://en.wikipedia.org/wiki/Air_traffic_controller) advised a new heading towards Talkeetna (https://en.wikipedia.org/wiki/Talkeetna,_Alaska), Alaska.
Two objectsAs soon as JAL 1628 straightened out of its turn, at 05:11 PM, Captain Terauchi noticed two craft to his far left, and some 2,000 ft (610 m) below his altitude, which he assumed to be military aircraft (https://en.wikipedia.org/wiki/Military_aircraft). These were pacing his flight path and speed.[8] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-Terauchi-8) At 5:18 or 5:19 PM the two objects abruptly veered to a position about 500 ft (150 m) or 1,000 ft (300 m) in front of the aircraft, assuming a stacked configuration.
In doing so they activated "a kind of reverse thrust, and [their] lights became dazzlingly bright".[1] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-JapanToday-1) To match the speed of the aircraft from their sideways approach, the objects displayed what Terauchi described as a disregard for inertia (https://en.wikipedia.org/wiki/Inertia): "The thing was flying as if there was no such thing as gravity. It sped up, then stopped, then flew at our speed, in our direction, so that to us it [appeared to be] standing still. The next instant it changed course. ... In other words, the flying object had overcome gravity."[1] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-JapanToday-1) The "reverse thrust" caused a bright flare for 3 to 7 seconds,[8] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-Terauchi-8) to the extent that captain Terauchi could feel the warmth of their glows.
Air traffic control was notified at this point (i.e. 5:19:15 PM), who could not confirm any traffic in the indicated position. After 3 to 5 minutes the objects assumed a side-to-side configuration, which they maintained for another 10 minutes. They accompanied the aircraft with an undulating motion, and some back and forth rotation of the jet nozzles, which seemed to be under automatic control,[8] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-Terauchi-8) causing them to flare with brighter or duller luminosity.
Each object had a square shape, consisting of two rectangular arrays of what appeared to be glowing nozzles or thrusters, separated by a dark central section. Captain Terauchi speculated in his drawings, that the objects would appear cylindrical[5] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-Harper-5) if viewed from another angle, and that the observed movement of the nozzles could be ascribed to the cylinders' rotation. The objects left abruptly at about 5:23:13 PM, moving to a point below the horizon to the east.[8] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-Terauchi-8)

Excerpt of communication with Anchorage ARTC Center

Time Speaker Dialog
5:18 or 19 PM AKST AARTCC[note 1] audio tape [Two craft, first noticed at a distance at 5:11 PM, approach to within 500–1,000 ft from the cockpit.]

5:19:15 JAL-1628, First officer[8] Anchorage Center, Japan Air 1628, ah, do you have any traffic, ah, seven [i.e. eleven] o'clock above?

5:19:24 AARTCC, JAL1628 heavy, say again...
5:19:28 JAL-1628 Do you have any traffic in front of us?
5:19:32 AARTCC JAL1628 heavy, roger.
5:19:36 JAL-1628 Ah, roger and, ah, we in sight, ah, two traffic, ah, in front of us one mile about.
5:19:49 AARTCC JAL1628, roger, do you have.., ah, can you identify the aircraft?
5:19:58 JAL-1628 Ah, we are not sure, but we have traffic in sight now.
5:20:04 AARTCC JAL1628 heavy, Roger. Maintain visual contact with your traffic and, ah, can you say the altitude of the traffic?
5:20:14 JAL-1628 Uh, almost the same altitude.
5:20:21 AARTCC JAL 1628 Roger. Would you like a higher or lower altitude?
5:20:27 JAL-1628 Ah, no, negative. JAL1628.
5:21:19 AARTCC JAL1628 heavy, see if you are able to identify the type of aircraft, ah, and see if you can tell whether it's military or civilian.
5:21:35 JAL-1628 JAL1628. We cannot identify the type, ah, but we can see, ah, navigation lights and ah, strobe lights.
5:21:48 AARTCC Roger, sir. Say the color of the strobe and beacon lights.
5:21:56 JAL-1628 The color is, ah, white and yellow, I think.
5:22:03 AARTCC White and yellow. Thank you.
5:21 AARTCC, Watch supervisor’s entry Daily Record of Facility Operation
5:21 PM. JL1628, HB747, BIKF-ANC reported traffic at his altitude (FL350) one mile with a white and yellow strobe. AAL ROC[note 2] and EDF ROCC notified.[note 3] No known traffic identified.

After 3 to 5 minutes the two craft change their relative position, which is not reported to AARTCC,[8] and the captain unsuccessfully attempts to photograph them.
5:22:11 AARTCC [Requests information about weather and clouds]
5:22:41 AARTCC [Informs JAL-1628 that transmissions are garbled and asks them to change transmitting frequencies.]
5:23:05 JAL-1628 [Reports clouds below them].
5:23:13 JAL-1628 And now the target, ah, traffic is extinguished [i.e. disappeared]. We cannot see it now.
VHF transmissions have returned to normal after 10 to 15 minutes of heavy interference.[8]
5:23:19 AARTCC JAL1628 Roger. And I'm not receiving any radar replies.

MothershipWhere the first objects disappeared, Captain Terauchi now noticed a pale band of light that mirrored their altitude, speed and direction.[3] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-Lawhon-3) Setting their onboard radar scope to a 25 nautical miles (46 km) range, he confirmed an object in the expected 10 o'clock direction at about 7.5 nmi (13.9 km) distance,[4] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-future-4) and informed ATC of its presence. Anchorage found nothing on their radar, but Elmendorf (https://en.wikipedia.org/wiki/Elmendorf_Air_Force_Base) ROCC, directly in his flight path, reported a "surge primary return" after some minutes.[3] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-Lawhon-3)
As the city lights of Fairbanks (https://en.wikipedia.org/wiki/Fairbanks,_Alaska) began to illuminate the object, captain Terauchi believed to perceive the outline of a gigantic spaceship on his port side (https://en.wikipedia.org/wiki/Port_side) that was "twice the size of an aircraft carrier". It was however outside first officer Tamefuji's field of view.[11] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-ADNews-14) Terauchi immediately requested a change of course to avoid it.[4] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-future-4) The object however followed him "in formation", or in the same relative position throughout the 45 degree turn, a descent from 35,000 to 31,000 ft, and a 360 degree turn.[12] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-evening-15) The short-range radar at Fairbanks airport (https://en.wikipedia.org/wiki/Fairbanks_International_Airport) however failed to register the object.[3] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-Lawhon-3)
Anchorage ATC offered military intervention, which was declined by the pilot, due to his knowledge of the Mantell incident (https://en.wikipedia.org/wiki/Mantell_UFO_incident).[4] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-future-4) The object was not noted by any of two planes which approached JAL 1628 to confirm its presence, by which time JAL 1628 had also lost sight of it. JAL 1628 arrived safely in Anchorage at 18:20.
AftermathCaptain Terauchi cited in the official Federal Aviation Administration (https://en.wikipedia.org/wiki/Federal_Aviation_Administration) report that the object was a UFO. In December 1986, Terauchi gave an interview to two Kyodo News (https://en.wikipedia.org/wiki/Kyodo_News) journalists. JAL soon grounded him for talking to the press, and moved him to a desk job. He was only reinstated as a pilot years afterwards, and retired eventually in north Kanto (https://en.wikipedia.org/wiki/Kant%C5%8D_region), Japan.[1] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-JapanToday-1)
Kyodo News contacted Paul Steucke, the FAA public information officer in Anchorage on December 24, and received confirmation of the incident, followed by UPI (https://en.wikipedia.org/wiki/United_Press_International) on the 29th.[12] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-evening-15)[13] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-MaccabeeFSP-16) The FAA's Alaskan Region consulted John Callahan,[note 4] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-17) the FAA Division Chief of the Accidents and Investigations branch, as they wanted to know what to tell the media about the UFO.[14] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-Callahan-18) John Callahan was unaware of any such incident, considering it a likely early flight of a stealth bomber (https://en.wikipedia.org/wiki/Northrop_Grumman_B-2_Spirit), then in development. He asked the Alaskan Region to forward the relevant data to their technical center in Atlantic City (https://en.wikipedia.org/wiki/Atlantic_City,_New_Jersey), New Jersey, where he and his superior played back the radar data and tied it in with the voice tapes by videotaping the concurrent playbacks.[14] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-Callahan-18)
A day later at FAA headquarters they briefed Vice Admiral Donald D. Engen, who watched the whole video of over half an hour, and asked them not to talk to anybody until they were given the OK, and to prepare an encompassing presentation (https://en.wikipedia.org/wiki/Dog_and_pony_show) of the data for a group of government officials the next day.[15] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-Good-19) The meeting was attended by representatives of the FBI, CIA and President Reagan’s Scientific Study Team, among others. Upon completion of the presentation, all present were told that the incident was secret and that their meeting "never took place". According to Callahan, the officials considered the data to represent the first instance of recorded radar data on a UFO, and they took possession of all the presented data.[14] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-Callahan-18) John Callahan however managed to retain the original video, the pilot's report and the FAA's first report in his office.[15] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-Good-19) The forgotten target print-outs of the computer data were also rediscovered, from which all targets can be reproduced that were in the sky at the time.[14] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-Callahan-18)
After a three-month investigation, the FAA formally released their results at a press conference held on March 5, 1987. Here Paul Steucke retracted earlier FAA suggestions that their controllers confirmed a UFO,[12] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-evening-15) and ascribed it to a "split radar image" which appeared with unfortunate timing. He clarified that "the FAA [did] not have enough material to confirm that something was there", and though they were "accepting the descriptions by the crew" they were "unable to support what they saw".[11] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-ADNews-14) The McGrath incident was revealed here amongst the ample set of documents supplied to the journalists.
The sighting received special attention from the media,[16] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-20) as a supposed instance of the tracking of UFOs on both ground[12] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-evening-15) and airborne radar, while being observed by experienced airline pilots, with subsequent confirmation by an FAA Division Chief.
Subsequent Alaskan sightingsFlight AS-53 UFOOn 29 January 1987[11] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-ADNews-14)[note 5] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-21) at 18:40 PM,[17] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-FAA290187-22) Alaska Airlines (https://en.wikipedia.org/wiki/Alaska_Airlines) Flight 53 observed a fast moving object on their onboard weather radar. While at 35,000 ft (11,000 m), some 60 miles (97 km) west of McGrath (https://en.wikipedia.org/wiki/McGrath,_Alaska), on a flight from Nome (https://en.wikipedia.org/wiki/Nome,_Alaska) to Anchorage (https://en.wikipedia.org/wiki/Anchorage), the radar registered a strong target in their 12 o'clock position, at 25 miles (40 km) range.
While they could not distinguish any object or light visually, they noticed that the radar object was increasing its distance at a very high rate. With every sweep of their radar, about 1 second apart, the object added five miles to its distance, translating to a speed of 18,000 mph (29,000 km/h).[17] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-FAA290187-22)[18] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-FAA060287-23) The pilot however relayed a speed of 'a mile a second' to the control tower, or a speed of 3,600 mph (5,800 km/h),[19] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-FAA090287-24) but confirmed that the target exceeded both the 50 mi (80 km) and 100 mi (160 km) ranges of their radar scope in a matter of seconds.[17] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-FAA290187-22)[18] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-FAA060287-23) The object was outside the radar range of the Anchorage ARTCC,[17] (https://en.wikipedia.org/wiki/Japan_Air_Lines_flight_1628_incident#cite_note-FAA290187-22) and additional radar data covering the specified time and location failed to substantiate the pilots' claim.

Excerpt from communication with Anchorage ATC (ZAN)[19][20]
Time Speaker Dialog
18:39:29 AS-53 Center, fifty-three.
18:39:30 ZAN Alaska fifty-three, go ahead.
18:39:33 AS-53 Any traffic in this, ah, area do you? Headed towards Anchorage.
18:39:36 ZAN Ah, I have one coming outbound from Anchorage towards McGrath at this time. It's a Piper Navajo at twelve thousand and, ah, I have a same direction Ryan Air Beech zero two estimating over McGrath zero four zero eight at two five zero. Other than that I don't have any other airplanes.

18:39:52 AS-53 Okay we're just curious up at about our altitude, ah, headed that direction, thanks. You haven't had any UFO reports lately, huh?
18:40:10 ZAN Well, I was just getting ready to ask you about that, ah, could you tell me, ah, the position of that aircraft?
18:40:15 AS-53 Yea, it's just underneath our radar. Picked up a blip. Moving about a mile a second. Just pulled out straight ahead of us, and disappeared. (garbled) shot at him but ah ... Then he was there, then he was gone.
18:40:26 ZAN Alaska fifty-three, Roger. And, ah, ah, did you have any visual sighting with that aircraft or anything like that?
18:40:32 AS-53 Negative. We just picked up on radar the, ah, traffic and, ah, just watched it, just pulled out straight ahead of us and just disappeared in a matter of seconds.
18:40:41 ZAN Alaska fifty-three, Roger. Standby please.
18:44:31 AS-53 Anchorage. Alaska fifty-three, McGrath.
18:44:34 ZAN Alaska fifty-three go ahead.
18:44:36 AS-53 Fifty-three McGrath at zero three four four level three five zero. Anchorage zero four one four landing.
18:44:45 ZAN Alaska fifty-three, Roger. Contact Anchorage Center one one eight point two six zero DME southeast of McGrath. And I just checked on this, we don't have military as active. There shouldn't be any military aircraft. Over, we're, ah, not talking too at this time operating in your vicinity. Ah, have you shown any else on radar since that last, ah, contact?
18:45:03 AS-53 Ah, no sir.
18:45:06 ZAN Alaska fifty-three. Will see you next time. Good day.
18:45:08 AS-53 (garbled transmission)

KC-135 observationA US Air Force (https://en.wikipedia.org/wiki/US_Air_Force) KC-135 (https://en.wikipedia.org/wiki/Boeing_KC-135_Stratotanker) jet flying from Anchorage to Fairbanks once again observed a very large, disk-shaped object on January 30, 1987. The pilot reported that the object was 12 m (40 ft) from the aircraft. The object then disappeared out of sight.

Excerpts of communication with Anchorage ATC Center[20]
Speaker Dialog
KC-135 Do you have traffic for us around one o'clock? Can't really tell the distance. Seems to be about low altitude.
AATCC Actor two nine. Negative. I have no traffic in your one o'clock.
...
KC-135 We're from California. Just visiting up here. People see this sort of thing a lot? Apart from the Japan Airline types?
AATCC Actor two nine. Very rare seeing the lights up there.
...
AATCC Actor two nine. The quality assurance staff at Anchorage Center here request that you give them a call after you land at Eielson.
KC-135 That is concerning the object we were looking at?
AATCC Affirmative sir.



https://www.youtube.com/watch?v=dMn1PiNZfkU