Korean Air Lines Flight 007

From Infogalactic: the planetary knowledge core
(Redirected from Korean Air Lines 007)
Jump to: navigation, search
Korean Air Lines Flight 007
250px
HL7442, the aircraft that was shot down, landing at Zurich airport in 1980.
Shootdown summary
Date September 1, 1983
Summary Shot down by the Soviet Air Forces after navigation error by KAL pilots
Site Sea of Japan, near Moneron Island, west of Sakhalin Island, Soviet Union
Lua error in package.lua at line 80: module 'strict' not found.
Passengers 246[1]
Crew 23[note 1]
Fatalities 269
Survivors 0
Aircraft type Boeing 747-230B
Operator Korean Air Lines
Registration HL7442
Flight origin John F. Kennedy International Airport,
New York City, New York, U.S.
Stopover Anchorage International Airport,
Anchorage, Alaska, U.S.
Destination Gimpo International Airport,
Gangseo-gu, Seoul, South Korea

Korean Air Lines Flight 007 (KE007/KAL007)[note 2] was a scheduled Korean Air Lines flight from New York City to Seoul via Anchorage, Alaska. On September 1, 1983, the South Korean airliner servicing the flight was shot down by a Soviet Sukhoi Su-15 interceptor. The Boeing 747 airliner was en route from Anchorage to Seoul, but due to a navigational mistake made by the KAL crew the airliner deviated from its original planned route and flew through Soviet prohibited airspace around the time of a U.S. aerial reconnaissance mission. The Soviet Air Forces treated the unidentified aircraft as an intruding U.S. spy plane, and destroyed it with air-to-air missiles, after firing warning shots which were likely not seen by the KAL pilots.[2] The Korean airliner eventually crashed in the sea near Moneron Island west of Sakhalin in the Sea of Japan. All 269 passengers and crew aboard were killed, including Larry McDonald, a United States Representative from Georgia. The Soviet Union found the wreckage under the sea two weeks later on September 15, and found the flight recorders in October, but this information was kept secret until 1992.

The Soviet Union initially denied knowledge of the incident,[3] but later admitted shooting down the aircraft, claiming that it was on a MASINT spy mission.[4] The Politburo of the Communist Party of the Soviet Union said it was a deliberate provocation by the United States[5] to probe the Soviet Union's military preparedness, or even to provoke a war. The White House accused the Soviet Union of obstructing search and rescue operations.[6] The Soviet Armed Forces suppressed evidence sought by the International Civil Aviation Organization (ICAO) investigation, such as the flight recorders,[7] which were released ten years later, after the dissolution of the Soviet Union.[8]

The incident was one of the most tense moments of the Cold War and resulted in an escalation of anti-Soviet sentiment, particularly in the United States.

As a result of the incident, the United States altered tracking procedures for aircraft departing from Alaska. In addition, the incident was one of the most important events that prompted the Reagan administration to allow worldwide access to the United States' Global Positioning System (GPS).[9][10]

Aircraft

<templatestyles src="Stack/styles.css"/>

File:Condor Boeing 747-230B (D-ABYH) at Düsseldorf Airport.jpg
The aircraft involved when still in service with Condor (1976).

The aircraft flying as Korean Air Lines Flight 007 was a Boeing 747-230B jet airliner with Boeing serial number 20559. The aircraft first flew on January 28, 1972, and was delivered on March 17, 1972, to German airline Condor with the registration D-ABYH. It was sold to the ITEL Corporation in February 1979 and leased to Korean Air Lines with the registration HL7442.[11][12]

Details of the flight

Passengers and crew

Nationality Victims
Australia 4
Hong Kong 12
Canada 8
Dominican Republic 1
India 1
Iran 1
Japan 28
Malaysia 1
Philippines 16
South Korea 105 *
Sweden 1
Republic of China 23
Thailand 5
United Kingdom 2
United States 62
Vietnam 1 **
Total 269

* 76 passengers, 23 active crew and 6 deadheading crew[13]
** A refugee from former South Vietnam in U.S[14][15]

Congressman Larry McDonald

The aircraft flying as Korean Air Lines Flight 007 departed Gate 15 of John F. Kennedy International Airport, New York City, on August 31, 1983, at 00:25 EDT (04:25 UTC), bound for Gimpo International Airport in Gangseo District, Seoul, 35 minutes behind its scheduled departure time of 23:50 EDT, August 30 (03:50 UTC, August 31). The flight was carrying 246 passengers and 23 crew members.[note 1][16] After refueling at Anchorage International Airport in Anchorage, Alaska, the aircraft departed for Seoul at 04:00 AHDT (13:00 UTC) on August 31, 1983. This leg of the journey was piloted by Captain Chun Byung-in, First Officer Son Dong-hui and Flight Engineer Kim Eui-dong.[17][18]

The aircrew had an unusually high ratio of crew to passengers, as six deadheading crew were on board.[19] Twelve passengers occupied the upper deck first class, while in business class almost all of the 24 seats were taken; in economy class, approximately 80 seats were empty. There were 22 children under the age of 12 years aboard. 130 passengers planned to connect to other destinations such as Tokyo, Hong Kong, and Taipei.[20] United States Congressman Larry McDonald from Georgia, who at the time was also the second president of the conservative John Birch Society, was on the flight.

Flight deviation from assigned route

After taking off from Anchorage, the flight was instructed by air traffic control (ATC) to turn to a heading of 220 degrees. Approximately 90 seconds later, ATC directed the flight to "proceed direct Bethel when able".[21][22] Upon arriving over Bethel, Alaska, KAL 007 entered the northernmost of five 50-mile (80 km) wide airways, known as the NOPAC (North Pacific) routes, that bridge the Alaskan and Japanese coasts. KAL 007's particular airway, R-20 (Romeo Two Zero), passes just 17.5 miles (28.2 km) from what was then Soviet airspace off the coast of the Kamchatka Peninsula.

The autopilot system of the 747-200 has four basic control modes: HEADING, VOR/LOC, ILS, and INS. The HEADING mode maintained a constant magnetic course selected by the pilot. The VOR/LOC mode maintained the plane on a specific course, transmitted from a VOR (VHF omnidirectional range, a type of short-range radio signal transmitted from ground beacons) or Localizer (LOC) beacon selected by the pilot. The ILS (instrument landing system) mode caused the plane to track both vertical and lateral course beacons, which led to a specific runway selected by the pilot. The INS (inertial navigation system) mode maintained the plane on lateral course lines between selected flight plan waypoints programmed into the INS computer.

When the INS navigation systems were properly programmed with the filed flight plan waypoints, the pilot could turn the autopilot mode selector switch to the INS position and the plane would then automatically track the programmed INS course line, provided the plane was headed in the proper direction and within 7.5 miles (12.1 km) of that course line. If, however, the plane was more than 7.5 miles (12.1 km) from the flight-planned course line when the pilot turned the autopilot mode selector from HEADING to INS, the plane would continue to track the heading selected in HEADING mode as long as the actual position of the plane was more than 7.5 miles (12.1 km) from the programmed INS course line. The autopilot computer software commanded the INS mode to remain in the "armed" condition until the plane had moved to a position less than 7.5 miles (12.1 km) from the desired course line. Once that happened, the INS mode would change from "armed" to "capture" and the plane would track the flight-planned course from then on.[23]

The HEADING mode of the autopilot would normally be engaged sometime after takeoff to comply with vectors from ATC, and then after receiving appropriate ATC clearance, to guide the plane to intercept the desired INS course line.[23]

The Anchorage VOR beacon was not operational at the time, as it was undergoing maintenance.[24] The crew received a NOTAM (Notice to Airmen) of this fact, which was not seen as a problem, as the captain could still check his position at the next VORTAC beacon at Bethel, 346 miles (557 km) away. The aircraft was required to maintain the assigned heading of 220 degrees, until it could receive the signals from Bethel, then it could fly direct to Bethel, as instructed by ATC, by centering the VOR "to" course deviation indicator (CDI) and then engaging the auto pilot in the VOR/LOC mode. Then, when over the Bethel beacon, the flight could start using INS mode to follow the waypoints that make up route Romeo-20 around the coast of the U.S.S.R. to Seoul. The INS mode was necessary for this route, since after Bethel the plane would be mostly out of range from VOR stations.

A simplified CIA map showing divergence of planned and actual flight paths

At about 10 minutes after take-off, flying on a heading of 245 degrees, KAL 007 began to deviate to the right (north) of its assigned route to Bethel, and continued to fly on this constant heading for the next five and a half hours.[25]

International Civil Aviation Organization (ICAO) simulation and analysis of the flight data recorder determined that this deviation was probably caused by the aircraft's autopilot system operating in HEADING mode, after the point that it should have been switched to the INS mode.[26][27] According to the ICAO, the autopilot was not operating in the INS mode either because the crew did not switch the autopilot to the INS mode (as they should have shortly after Cairn Mountain), or they did select the INS mode, but the computer did not transition from "armed" to "capture" condition because the aircraft had already deviated off track by more than the 7.5 miles (12.1 km) tolerance permitted by the inertial navigation computer. Whatever the reason, the autopilot remained in the HEADING mode, and the problem was not detected by the crew.[26]

At 28 minutes after takeoff, civilian radar at Kenai Peninsula on the eastern shore of Cook Inlet and with radar coverage 175 miles (282 km) west of Anchorage, tracked KAL 007 5.6 miles (9.0 km) north of where it should have been.[28]

When KAL 007 did not reach Bethel at 50 minutes after takeoff, a military radar at King Salmon, Alaska, tracked KAL 007 at 12.6 nautical miles (23.3 km) north of where it should have been. There is no evidence to indicate that civil air traffic controllers or military radar personnel at Elmendorf Air Force Base (who were in a position to receive the King Salmon radar output) were aware of KAL 007's deviation in real-time, and therefore able to warn the aircraft. It had exceeded its expected maximum deviation sixfold, 2 nautical miles (3.7 km) of error being the maximum expected drift from course if the inertial navigation system was activated.[28]

KAL 007's divergence prevented the aircraft from transmitting its position via shorter range very high frequency radio (VHF). It therefore requested KAL 015, also en route to Seoul, to relay reports to air traffic control on its behalf.[29] KAL 007 requested KAL 015 to relay its position three times. At 14:43 UTC, KAL 007 directly transmitted a change of estimated time of arrival for its next waypoint, NEEVA, to the international flight service station at Anchorage,[30] but it did so over the longer range high frequency radio (HF) rather than VHF. HF transmissions are able to carry a longer distance than VHF, but are vulnerable to electromagnetic interference and static; VHF is clearer with less interference, and preferred by flight crews. The inability to establish direct radio communications to be able to transmit their position directly did not alert the pilots of KAL 007 of their ever-increasing divergence[28] and was not considered unusual by air traffic controllers.[29] Halfway between Bethel and waypoint NABIE, KAL 007 passed through the southern portion of the North American Aerospace Defense Command buffer zone. This zone is north of Romeo 20 and off-limits to civilian aircraft.

Some time after leaving American territorial waters, KAL Flight 007 crossed the International Date Line, where the local date shifted from August 31, 1983, to September 1, 1983.

KAL 007 continued its journey, ever increasing its deviation—60 nautical miles (110 km) off course at waypoint NABIE, 100 nautical miles (190 km) off course at waypoint NUKKS, and 160 nautical miles (300 km) off course at waypoint NEEVA—until it reached the Kamchatka Peninsula.[13]:13

Romeo 20 waypoint Flight-planned coordinates ATC KAL 007 deviation
CAIRN MOUNTAIN Lua error in package.lua at line 80: module 'strict' not found. Anchorage 5.6 mi (9.0 km)
BETHEL Lua error in package.lua at line 80: module 'strict' not found. Anchorage 12.6 nmi (23.3 km)
NABIE Lua error in package.lua at line 80: module 'strict' not found. Anchorage 60 nmi (110 km)
NUKKS Lua error in package.lua at line 80: module 'strict' not found. Anchorage 100 nmi (190 km)
NEEVA Lua error in package.lua at line 80: module 'strict' not found. Anchorage 160 nmi (300 km)
NINNO Lua error in package.lua at line 80: module 'strict' not found. Anchorage
NIPPI Lua error in package.lua at line 80: module 'strict' not found. Anchorage/Tokyo 180 mi (290 km)[31]
NYTIM Lua error in package.lua at line 80: module 'strict' not found. Tokyo 500 nmi (930 km) to point of impact
NOKKA Lua error in package.lua at line 80: module 'strict' not found. Tokyo 350 nmi (650 km) to point of impact
NOHO Lua error in package.lua at line 80: module 'strict' not found. Tokyo 390 nmi (720 km) to point of impact

Shootdown

In 1983, Cold War tensions between the United States and Soviet Union had escalated to a level not seen since the Cuban Missile Crisis because of several factors. These included the United States' Strategic Defense Initiative, its planned deployment of the Pershing II weapon system in Europe in March and April, and FleetEx '83-1, the largest naval exercise held to date in the North Pacific.[32] The military hierarchy of the Soviet Union (particularly the old guard led by Soviet General Secretary Yuri Andropov and Minister of Defence Dmitry Ustinov) viewed these actions as bellicose and destabilizing; they were deeply suspicious of U.S. President Ronald Reagan's intentions and openly fearful he was planning a pre-emptive nuclear strike against the Soviet Union. These fears culminated in RYAN, the code name for a secret intelligence-gathering program initiated by Andropov to detect a potential nuclear sneak attack which he believed Reagan was plotting.[33]

Aircraft from USS Midway and USS Enterprise repeatedly overflew Soviet military installations in the Kuril Islands during FleetEx '83,[34] resulting in the dismissal or reprimanding of Soviet military officials who had been unable to shoot them down.[35] On the Soviet side, RYAN was expanded.[35] Lastly, there was a heightened alert around the Kamchatka Peninsula at the time KAL 007 was in the vicinity, because of a Soviet missile test at the Kura Missile Test Range that was scheduled for the same day. A United States Air Force Boeing RC-135 reconnaissance aircraft flying in the area was monitoring the missile test off the peninsula.[36]

At 15:51 UTC, according to Soviet sources,[28] KAL 007 entered the restricted airspace of the Kamchatka Peninsula. The buffer zone extended 200 kilometres (120 mi) from Kamchatka's coast and is known as a flight information region (FIR). The 100-kilometre (62 mi) radius of the buffer zone nearest to Soviet territory had the additional designation of prohibited airspace. When KAL 007 was about 130 kilometres (81 mi) from the Kamchatka coast, four MiG-23 fighters were scrambled to intercept the Boeing 747.[26]

Significant command and control problems were experienced trying to vector the fast military jets onto the 747 before they ran out of fuel. In addition, pursuit was made more difficult, according to Soviet Air Force Captain Aleksandr Zuyev, who defected to the West in 1989, because, ten days before, Arctic gales had knocked out the key warning radar on the Kamchatka Peninsula. Furthermore, he stated that local officials responsible for repairing the radar lied to Moscow, falsely reporting that they had successfully fixed the radar. Had this radar been operational, it would have enabled an intercept of the stray airliner roughly two hours earlier with plenty of time for proper identification as a civilian aircraft. Instead, the unidentified jetliner crossed over the Kamchatka Peninsula back into international airspace over the Sea of Okhotsk without being intercepted.[37] In his explanation to 60 Minutes, Zuyev stated:

Some people lied to Moscow, trying to save their ass.[38]

The Commander of the Soviet Far East District Air Defense Forces, General Valery Kamensky,[39] was adamant that KAL 007 was to be destroyed even over neutral waters but only after positive identification showed it not to be a passenger plane. His subordinate, General Anatoly Kornukov, commander of Sokol Air Base and later to become commander of the Russian Air Force, insisted that there was no need to make positive identification as the intruder aircraft had already flown over the Kamchatka Peninsula.

General Kornukov (to Military District Headquarters-Gen. Kamensky): (5:47) "...simply destroy [it] even if it is over neutral waters? Are the orders to destroy it over neutral waters? Oh, well."
Kamensky: "We must find out, maybe it is some civilian craft or God knows who."

Kornukov: "What civilian? [It] has flown over Kamchatka! It [came] from the ocean without identification. I am giving the order to attack if it crosses the State border."

Units of the Soviet Air Defence Forces that had been tracking the South Korean aircraft for more than an hour while it entered and left Soviet airspace now classified the aircraft as a military target when it reentered their airspace over Sakhalin.[26] After a protracted ground-controlled interception, the three Su-15 fighters (from nearby Dolinsk-Sokol airbase) and the MiG-23[40] (from Smirnykh Air Base) managed to make visual contact with the Boeing, but, due to the black of night, failed to make critical identification of the aircraft which Russian communications reveal. The pilot of the lead Su-15 fighter fired warning shots with its cannon, but recalled later in 1991, "I fired four bursts, more than 200 rounds. For all the good it did. After all, I was loaded with armor piercing shells, not incendiary shells. It's doubtful whether anyone could see them."[41]

At this point, KAL 007 contacted Tokyo Area Control Center, requesting clearance to ascend to a higher flight level for reasons of fuel economy; the request was granted, so the Boeing started to climb, gradually slowing as it exchanged speed for altitude. The decrease in speed caused the pursuing fighter to overshoot the Boeing and was interpreted by the Soviet pilot as an evasive maneuver. The order to shoot KAL 007 down was given as it was about to leave Soviet airspace for the second time. At around 18:26 UTC, under pressure from General Kornukov and ground controllers not to let the aircraft escape into international airspace, the lead fighter was able to move back into a position where it could fire two K-8 (NATO reporting name: AA-3 "Anab") air-to-air missiles at the plane.[2]

Soviet pilot's recollection of shootdown

In a 1991 interview with Izvestia, Major Gennadiy Osipovich, pilot of the Su-15 interceptor that shot the 747 down, spoke about his recollections of the events leading up to the shootdown. Contrary to official Soviet statements at the time, he recalled telling ground controllers that there were "blinking lights".[42] He continued, saying of the 747-230B, "I saw two rows of windows and knew that this was a Boeing. I knew this was a civilian plane. But for me this meant nothing. It is easy to turn a civilian type of plane into one for military use."[42] Osipovich stated, "I did not tell the ground that it was a Boeing-type plane; they did not ask me."[41][42]

K-8 missile (the type fired at KAL 007) mounted on the wing of a Sukhoi Su-15

Commenting on the moment that KAL 007 slowed as it ascended from flight level 330 to flight level 350, and then on his maneuvering for missile launch, Osipovich said:

<templatestyles src="Template:Blockquote/styles.css" />

They [KAL 007] quickly lowered their speed. They were flying at 400 km/h (249 mph). My speed was more than 400. I was simply unable to fly slower. In my opinion, the intruder's intentions were plain. If I did not want to go into a stall, I would be forced to overshoot them. That's exactly what happened. We had already flown over the island [Sakhalin]. It is narrow at that point, the target was about to get away... Then the ground [controller] gave the command: "Destroy the target...!" That was easy to say. But how? With shells? I had already expended 243 rounds. Ram it? I had always thought of that as poor taste. Ramming is the last resort. Just in case, I had already completed my turn and was coming down on top of him. Then, I had an idea. I dropped below him about two thousand metres (6,600 ft)... afterburners. Switched on the missiles and brought the nose up sharply. Success! I have a lock on.[43]

<templatestyles src="Template:Blockquote/styles.css" />

We shot down the plane legally... Later we began to lie about small details: the plane was supposedly flying without running lights or strobe light, that tracer bullets were fired, or that I had radio contact with them on the emergency frequency of 121.5 megahertz.[44]

Osipovich died on September 23, 2015, after a protracted illness.[45]

Soviet command hierarchy of shootdown

The Soviet real-time military communication transcripts of the shootdown suggest the chain of command from the top general to Major Osipovich, the Su-15 interceptor pilot who shot down KAL 007.[46][47] In reverse order, they are:

  • Major Gennadiy Nikolayevich Osipovich,
  • Captain Titovnin, Combat Control Center – Fighter Division
  • Lt. Colonel Maistrenko, Smirnykh Air Base Fighter Division Acting Chief of Staff, who confirmed the shootdown order to Titovnin
"Titovnin: You confirm the task?
"Maistrenko: Yes."
  • Lt. Colonel Gerasimenko, Acting Commander, 41st Fighter Regiment.
"Gerasimenko: (to Kornukov) Task received. Destroy target 60–65 with missile fire. Accept control of fighter from Smirnikh."
  • General Anatoly Kornukov, Commander of Sokol Air Base – Sakhalin.
"Kornukov: (to Gerasimenko) I repeat the task, Fire the missiles, Fire on target 60–65. Destroy target 60–65... Take control of the MiG 23 from Smirnikh, call sign 163, call sign 163 He is behind the target at the moment. Destroy the target!... Carry out the task, Destroy it!"
  • General Valery Kamensky, Commander of Far East Military District Air Defense Forces.
"Kornukov: (To Kamensky) ...simply destroy [it] even if it is over neutral waters? Are the orders to destroy it over neutral waters? Oh, well."
  • Army General Ivan Moiseevich Tretyak, Commander of the Far East Military District.
"Weapons were used, weapons authorized at the highest level. Ivan Moiseevich authorized it. Hello, hello.", "Say again.", "I cannot hear you clearly now.", "He gave the order. Hello, hello, hello.", "Yes, yes.", "Ivan Moiseevich gave the order, Tretyak.", "Roger, roger.", "Weapons were used at his order."[48]

Post-attack flight

At the time of the attack, the plane had been cruising at an altitude of about 35,000 feet (11,000 m). Tapes recovered from the airliner's cockpit voice recorder indicate that the crew were unaware that they were off course and violating Soviet airspace. Immediately after missile detonation, the airliner began a 113-second arc upward because of a damaged crossover cable between the left inboard and right outboard elevators.[49]

At 18:26:46 UTC (03:26 Japan Time; 06:26 Sakhalin time),[50] at the apex of the arc at altitude 38,250 feet (11,660 m),[49] the autopilot disengaged (this was either done by the pilots, or it disengaged automatically). Now being controlled manually, the plane began to descend to 35,000 feet (11,000 m). From 18:27:01 until 18:27:09, the flight crew reported to Tokyo Area Control Center informing that KAL 007 to "descend to 10,000" [feet; 3,000 m]. At 18:27:20, ICAO graphing of Digital Flight Data Recorder tapes showed that after a descent phase and a 10 second "nose-up", KAL 007 was leveled out at pre-missile detonation altitude of 35,000 ft (11,000 m), forward acceleration was back to pre-missile detonation rate of zero acceleration, and air speed had returned to pre-detonation velocity.

Yaw (oscillations), begun at the time of missile detonation, continued decreasingly until the end of the 1 minute 44 second section of the tape. The Boeing did not break up, explode or plummet immediately after the attack; it continued its gradual descent for four minutes, then leveled off at 16,424 ft (5,006 m) (18:30–18:31 UTC), rather than continuing to descend to 10,000 ft (3,000 m) as previously reported to Tokyo Area Control Center. It continued at this altitude for almost five more minutes (18:35 UTC).

The last cockpit voice recorder entry occurred at 18:27:46 while in this phase of the descent. At 18:28 UTC, the aircraft was reported turning to the north.[51] ICAO analysis concluded that the flight crew "retained limited control" of the aircraft.[52] However, this only lasted for five minutes. The crew then lost all control. The aircraft began to descend rapidly in spirals over Moneron Island for 2.6 miles (4.2 km). The aircraft then broke apart in mid-air and crashed into the ocean, just off the West coast of the Sakhalin Island. All 269 people on board were killed.[note 3] The aircraft was last seen visually by Osipovich, "somehow descending slowly" over Moneron Island. The aircraft disappeared off long range military radar at Wakkanai, Japan, at a height of 1,000 feet (300 m).[53]

KAL 007 was probably attacked in international airspace, with a 1993 Russian report listing the location of the missile firing outside its territory at Lua error in package.lua at line 80: module 'strict' not found.,[35][54] although the intercepting pilot stated otherwise in a subsequent interview. Initial reports that the airliner had been forced to land on Sakhalin were soon proven false[citation needed]. One of these reports conveyed via phone by Orville Brockman, the Washington office spokesman of the Federal Aviation Administration, to the press secretary of Larry McDonald, was that the FAA in Tokyo had been informed by the Japanese Civil Aviation Bureau that "Japanese self-defense force radar confirms that the Hokkaido radar followed Air Korea to a landing in Soviet territory on the island of Sakhalinska and it is confirmed by the manifest that Congressman McDonald is on board".[55]

A Japanese fisherman aboard 58th Chidori Maru later reported to the Japanese Maritime Safety Agency (this report was cited by ICAO analysis) that he had heard a plane at low altitude, but had not seen it. Then he heard "a loud sound followed by a bright flash of light on the horizon, then another dull sound and a less intense flash of light on the horizon"[56] and smelled aviation fuel.[57]

Soviet command response to post-detonation flight

Though the interceptor pilot reported to ground control, "Target destroyed", the Soviet command, from general on down, indicated surprise and consternation at KAL 007's continued flight, and ability to regain its altitude and maneuver. This consternation continued through to KAL 007's subsequent level flight at altitude 16,424 ft (5,006 m), and then, after almost five minutes, through its spiral descent over Moneron Island. (See Korean Air Lines Flight 007 transcripts from 18:26 UTC onwards: "Lt. Col. Novoseletski: Well, what is happening, what is the matter, who guided him in — he locked on why didn't he shoot it down?")

Missile damage to plane

The following damage to the aircraft was determined by the ICAO from its analysis of the flight data recorder and cockpit voice recorder:

Hydraulics

KAL 007 had four redundant hydraulic systems of which systems one, two, and three were damaged or destroyed. There was no evidence of damage to system four.[50] The hydraulics provided actuation of all primary and secondary flight controls (except leading edge slats in the latter) as well as of landing gear retraction, extension, gear steering, and wheel braking. Each primary flight control axis received power from all four hydraulic systems.[58] Upon missile detonation, the jumbo jet began to experience oscillations (yawing) as the dual channel yaw damper was damaged. Yawing would not have occurred if hydraulic systems one or two were fully operational. The result is that the control column did not thrust forward upon impact (it should have done so as the plane was on autopilot) to bring down the plane to its former altitude of 35,000 feet (11,000 m). This failure of the autopilot to correct the rise in altitude indicates that hydraulic system number three, which operates the autopilot actuator, a system controlling the plane's elevators, was damaged or out. KAL 007's airspeed and acceleration rate both began to decrease as the plane began to climb. At twenty seconds after missile detonation a click was heard in the cabin, which is identified as the "automatic pilot disconnect warning" sound. Either the pilot or co-pilot had disconnected the autopilot and was manually thrusting the control column forward in order to bring the plane lower. Though the autopilot had been turned off, manual mode did not begin functioning for another twenty seconds. This failure of the manual system to engage upon command indicates failure in hydraulic systems one and two. With wing flaps up, "control was reduced to the right inboard aileron and the innermost of spoiler section of each side".[50]

Left wing

Contrary to Major Osipovich's statement in 1991 that he had taken off half of KAL 007's left wing,[41] ICAO analysis found that the wing was intact: "The interceptor pilot stated that the first missile hit near the tail, while the second missile took off half the left wing of the aircraft... The interceptor's pilot's statement that the second missile took off half of the left wing was probably incorrect. The missiles were fired with a two-second interval and would have detonated at an equal interval. The first detonated at 18:26:02 UTC. The last radio transmissions from KE007 to Tokyo Radio were between 18:26:57 and 18:27:15 UTC using HF [high frequency]. The HF 1 radio aerial of the aircraft was positioned in the left wing tip suggesting that the left wing tip was intact at this time. Also, the aircraft's maneuvers after the attack did not indicate extensive damage to the left wing."[59]

Engines

The co-pilot reported to Captain Chun twice during the flight after the missiles' detonation, "Engines normal, sir."[60]

Tail section

The first missile was radar-controlled and proximity fuzed, and detonated 50 metres (160 ft) behind the aircraft. Sending fragments forward, it either severed or unraveled the crossover cable from the left inboard elevator to the right elevator.[49] This, with damage to one of the four hydraulic systems, caused KAL 007 to ascend from 35,000 to 38,250 feet (10,670 to 11,660 m), at which point the autopilot was disengaged.

Fuselage

Fragments from the proximity fuzed air-to-air missile that detonated 50 metres (160 ft) behind the aircraft, punctured the fuselage and caused rapid decompression of the pressurised cabin. The interval of 11 seconds between the sound of missile detonation picked up by the cockpit voice recorder and the sound of the alarm sounding in the cockpit enabled ICAO analysts to determine that the size of the ruptures to the pressurised fuselage was 1.75 square feet (0.163 m2).[61]

Search and rescue

As a result of Cold War tensions, the search and rescue operations of the Soviet Union were not coordinated with those of the United States, South Korea, and Japan. Consequently no information was shared, and each side endeavored to harass or obtain evidence to implicate the other.[62] The flight data recorders were the key pieces of evidence sought by both governments, with the United States insisting that an independent observer from the ICAO be present on one of its search vessels in the event that they were found.[63] International boundaries are not well defined on the open sea, leading to numerous confrontations between the large number of opposing naval ships that were assembled in the area.[64]

Soviet search and rescue mission to Moneron Island

The Soviets did not acknowledge shooting down the aircraft until September 6, five days after the flight was shot down.[65] Eight days after the shootdown, Marshal of the Soviet Union and Chief of General Staff Nikolai Ogarkov denied knowledge of where KAL 007 had gone down; "We could not give the precise answer about the spot where it [KAL 007] fell because we ourselves did not know the spot in the first place."[66]

Nine years later, the Russian Federation handed over transcripts of Soviet military communications that showed that at least two documented search and rescue (SAR) missions were ordered within a half-hour of the attack, to the last Soviet verified location of the descending jumbo jet over Moneron Island. The first search was ordered from Smirnykh Air Base in central Sakhalin at 18:47 UTC, nine minutes after KAL 007 had disappeared from Soviet radar screens, and brought rescue helicopters from Khomutovo Air base (the military unit at Yuzhno-Sakhalinsk Airport in southern Sakhalin), and Soviet Border Troops boats to the area.[61]

The second search was ordered eight minutes later by the Deputy Commander of the Far Eastern Military District, General Strogov, and involved civilian trawlers that were in the area around Moneron. "The border guards. What ships do we now have near Moneron Island, if they are civilians, send [them] there immediately."[67] Moneron is just 4.5 miles (7.2 km) long and 3.5 miles (5.6 km) wide, located 24 miles (39 km) due west of Sakhalin Island at Lua error in package.lua at line 80: module 'strict' not found.; it is the only land mass in the whole Tatar Straits.

Search for KAL 007 in international waters

The submersible Deep Drone is deployed from the fleet tug, USNS Narragansett (T-ATF 167).

Immediately after the shootdown, South Korea, owner of the aircraft and therefore prime considerant for jurisdiction, designated the United States and Japan as search and salvage agents, thereby making it illegal for the Soviet Union to salvage the aircraft, providing it was found outside Soviet territorial waters. If it did so, the United States would now be legally entitled to use force against the Soviets, if necessary, to prevent retrieval of any part of the plane.[68]

On the same day as the shootdown, Rear Admiral William A. Cockell, Commander, Task Force 71, and a skeleton staff, taken by helicopter from Japan, embarked in USS Badger (stationed off Vladivostok at time of the flight)[68] on September 9 for further transfer to the destroyer USS Elliot to assume duties as Officer in Tactical Command (OTC) of the Search and Rescue (SAR) effort. Surface search began immediately and on into September 13. U.S. underwater operations began on September 14. On September 10, 1983, with no further hope of finding survivors, Task Force 71's mission was reclassified from a "Search and Rescue" (SAR) operation to a "Search and Salvage" (SAS).[69]

The Soviet Kashin class destroyer Odarennyy shadows ships of Task Force 71, 7th Fleet as they conduct search operations for Korean Airlines Flight 007.

On October 17, Rear Admiral Walter T. Piotti, Jr. took command of the Task Force and its Search and Salvage mission from Rear Admiral Cockell. First to be searched was a Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). "high probability" area. This was unsuccessful. On October 21, Task Force 71 extended its search within coordinates encompassing, in an arc around the Soviet territorial boundaries north of Moneron Island, an area of 225 square miles (583 km2), reaching to the west of Sakhalin Island. This was the "large probability" area. The search areas were outside the 12-nautical-mile (22 km) Soviet-claimed territorial boundaries. The northwesternmost point of the search touched the Soviet territorial boundary closest to the naval port of Nevelsk on Sakhalin. Nevelsk was 46 nautical miles (85 km) from Moneron. This larger search was also unsuccessful.[69]

The vessels used in the search, for the Soviet side as well as the US side (US, South Korea, Japan) were both civilian trawlers, especially equipped for both the SAR and SAS operations, and various types of warships and support ships. The Soviet side also employed both civilian and military divers. The Soviet search, beginning on the day of the shootdown and continuing until November 6, was confined to the Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). "high probability" area in international waters, and within Soviet territorial waters to the north of Moneron Island. The area within Soviet territorial waters was off-limits to the U.S., South Korean, and Japanese boats. From September 3 to 29, four ships from South Korea had joined in the search.

Piotti Jr, commander of Task Force 71 of 7th Fleet would summarize the US and Allied, and then the Soviets', Search and Salvage operations:

<templatestyles src="Template:Blockquote/styles.css" />

Not since the search for the hydrogen bomb lost off Palomares, Spain, has the U.S. Navy undertaken a search effort of the magnitude or import of the search for the wreckage of KAL Flight 007.

Within six days of the downing of KAL 007, the Soviets had deployed six ships to the general crash site area. Over the next 8 weeks of observation by U.S. naval units this number grew to a daily average of 19 Soviet naval, naval-associated and commercial (but undoubtedly naval-subordinated) ships in the Search and Salvage (SAS) area. The number of Soviet ships in the SAS area over this period ranged from a minimum of six to a maximum of thirty-two and included at least forty-eight different ships comprising forty different ship classes.[70]
U.S. Task Force 71 After action report map of search area in international waters

These missions met with interference by the Soviets,[71] in violation of the 1972 Incident at Sea agreement, and included false flag and fake light signals, sending an armed boarding party to threaten to board a U.S.-chartered Japanese auxiliary vessel (blocked by U.S. warship interposition), interfering with a helicopter coming off the USS Elliot (Sept. 7), attempted ramming of rigs used by the South Koreans in their quadrant search, hazardous maneuvering of Gavril Sarychev and near-collision with the USS Callaghan (September 15, 18), removing U.S. sonars, setting false pingers in deep international waters, sending Backfire bombers armed with air-to-surface nuclear-armed missiles to threaten U.S. naval units, criss-crossing in front of U.S. combatant vessels (October 26), cutting and attempted cutting of moorings of Japanese auxiliary vessels, particularly Kaiko Maru III, and radar lock-ons by a Soviet Kara-class cruiser, Petropavlovsk, and a Kashin-class destroyer, Odarennyy, targeting U.S. naval ships and the U.S. Coast Guard Cutter USCGC Douglas Munro (WHEC-724), USS Towers, escorting USS Conserver, experienced all of the above interference and was involved in a near-collision with Odarennyy (September 23–27).[72][73]

According to the ICAO: "The location of the main wreckage was not determined... the approximate position was Lua error in package.lua at line 80: module 'strict' not found., which was in international waters." This point is about 41 miles (66 km) from Moneron Island, about 45 miles (72 km) from the shore of Sakhalin and 33 miles (53 km) from the point of attack.[74]

Piotti Jr, commander of Task Force 71 of 7th Fleet, believed the search for KAL 007 in international waters to have been a search in the wrong place and assessed:[75]

Had TF [task force] 71 been permitted to search without restriction imposed by claimed territorial waters, the aircraft stood a good chance of having been found. No wreckage of KAL 007 was found. However, the operation established, with a 95% or above confidence level, that the wreckage, or any significant portion of the aircraft, does not lie within the probability area outside the 12 nautical mile area claimed by the Soviets as their territorial limit.[2]

At a hearing of the ICAO on September 15, 1983, J. Lynn Helms, the head of the Federal Aviation Administration, stated:[6] "The USSR has refused to permit search and rescue units from other countries to enter Soviet territorial waters to search for the remains of KAL 007. Moreover, the Soviet Union has blocked access to the likely crash site and has refused to cooperate with other interested parties, to ensure prompt recovery of all technical equipment, wreckage and other material."

Human remains and artifacts

Surface finds

File:Korean Air Lines Flight 007 - Shoes.jpg
Passengers' footwear retrieved by Soviets from the crash site

No body parts were recovered by the Soviet search team from the surface of the sea in their territorial waters, though they would later turn over clothes and shoes to a joint U.S.–Japanese delegation at Nevelsk on Sakhalin. On Monday, September 26, 1983, a delegation of seven Japanese and U.S. officials arriving aboard the Japanese patrol boat Tsugaru, had met a six-man Soviet delegation at the port of Nevelsk on Sakhalin Island. KGB Major General A. I. Romanenko, the Commander of the Sakhalin and Kuril Islands frontier guard, headed the Soviet delegation. Romanenko handed over to the U.S. and the Japanese, among other things, single and paired footwear. With footwear that the Japanese also retrieved, the total came to 213 men's, women's and children's dress shoes, sandals, and sports shoes.[76] The Soviets indicated these items were all that they had retrieved floating or on the shores of Sakhalin and Moneron islands.

Family members of KAL 007 passengers later stated that these shoes were worn by their loved ones for the flight. Sonia Munder had no difficulty recognizing the sneakers of her children, one of Christian age 14 and one of Lisi age 17, by the intricate way her children laced them. Another mother says, "I recognized them just like that. You see, there are all kinds of inconspicuous marks which strangers do not notice. This is how I recognized them. My daughter loved to wear them."[77]

Another mother, Nan Oldham, identified her son John's sneakers from a photo in Life magazine of 55 of the 213 shoes—apparently, a random array on display those first days at Chitose Air Force Base in Japan. "We saw photos of his shoes in a magazine," says Oldham, "We followed up through KAL and a few weeks later, a package arrived. His shoes were inside: size 11 sneakers with cream white paint."[78] John Oldham had taken his seat in row 31 of KAL 007 wearing those cream white paint-spattered sneakers.[78]

Nothing was found by the joint U.S.–Japanese–South Korean search and rescue/salvage operations in international waters at the designated crash site or within the 225-square-nautical-mile (770 km2) search area.[79]

Hokkaido finds

Eight days after the shootdown, human remains and other types of objects appeared on the north shore of Hokkaido, Japan. Hokkaido is about 30 miles (48 km) below the southern tip of Sakhalin across the La Pérouse Strait (the southern tip of Sakhalin is 35 miles (56 km) from Moneron Island which is west of Sakhalin). The ICAO concluded that these bodies, body parts and objects were carried from Soviet waters to the shores of Hokkaido by the southerly current west of Sakhalin Island. All currents of the Strait of Tartary relevant to Moneron Island flow to the north, except this southerly current between Moneron Island and Sakhalin Island.[80]

These human remains, including body parts, tissues, and two partial torsos, totaled 13. All were unidentifiable, but one partial torso was that of a Caucasian woman as indicated by auburn hair on a partial skull, and one partial body was of an Asian child (with glass embedded). There was no luggage recovered. Of the non-human remains that the Japanese recovered were various items including dentures, newspapers, seats, books, eight KAL paper cups, shoes, sandals, and sneakers, a camera case, a "please fasten seat belt" sign, an oxygen mask, a handbag, a bottle of dish washing fluid, several blouses, an identity card belonging to 25-year-old passenger Mary Jane Hendrie of Sault Ste. Marie, Ontario, Canada, and the business cards of passengers Kathy Brown-Spier and Mason Chang.[81][82] These items generally came from the passenger cabin of the aircraft. None of the items found generally came from the cargo hold of the plane, such as suitcases, packing boxes, industrial machinery, instruments, and sports equipment.

Russian diver reports

In 1991, after the collapse of the Soviet Union, Russian newspaper Izvestia published a series of interviews with Soviet military personnel who had been involved in salvage operations to find and recover parts of the aircraft.[41] After three days of searching using trawlers, side-scan sonar, and diving bells, Soviet searchers located the aircraft wreckage at a depth of 174 metres (571 ft) near Moneron Island.[41][83] Since no human remains or luggage were found on the surface in the impact area, the divers expected to find the remains of passengers who had been trapped in the submerged wreckage of the aircraft on the seabed. When they visited the site two weeks after the shootdown, they found that the wreckage was in small pieces, and found no bodies:

I had the idea that it would be intact. Well, perhaps a little banged up... The divers would go inside the aircraft and see everything there was to see. In fact it was completely demolished, scattered about like kindling. The largest things we saw were the braces which are especially strong—they were about one and a half or two meters long and 50–60 centimeters wide. As for the rest—broken into tiny pieces...[41]

According to Izvestia, the divers had only ten encounters with passenger remains (tissues and body parts) in the debris area, including one partial torso.[84]

Tinro ll submersible Captain Mikhail Igorevich Girs' diary: Submergence 10 October. Aircraft pieces, wing spars, pieces of aircraft skin, wiring, and clothing. But—no people. The impression is that all of this has been dragged here by a trawl rather than falling down from the sky...[85]

Vyacheslav Popov: "I will confess that we felt great relief when we found out that there were no bodies at the bottom. Not only no bodies; there were also no suitcases or large bags. I did not miss a single dive. I have quite a clear impression: The aircraft was filled with garbage, but there were really no people there. Why? Usually when an aircraft crashes, even a small one... As a rule there are suitcases and bags, or at least the handles of the suitcases."

A number of civilian divers, whose first dive was on September 15, two weeks after the shootdown, state that Soviet military divers and trawls had been at work before them:

Diver Vyacheslav Popov: "As we learned then, before us the trawlers had done some 'work' in the designated quadrant. It is hard to understand what sense the military saw in the trawling operation. First drag everything haphazardly around the bottom by the trawls, and then send in the submersibles?...It is clear that things should have been done in the reverse order."

ICAO also interviewed a number of these divers for its 1993 report: "In addition to the scraps of metal, they observed personal items, such as clothing, documents and wallets. Although some evidence of human remains was noticed by the divers, they found no bodies."[86]

Political events

Initial Soviet denial

Marshal Nikolai Ogarkov during his September 9, 1983, press conference on the shootdown of Korean Air Lines Flight 007

General Secretary Yuri Andropov, on the advice of Defense Minister Dmitriy Ustinov, but against the advice of the Foreign Ministry, initially decided not to make any admission of downing the airliner, on the premise that no one would find out or be able to prove otherwise.[65] Consequently the TASS news agency reported twelve hours after the shootdown only that an unidentified aircraft, flying without lights, had been intercepted by Soviet fighters after it violated Soviet airspace over Sakhalin. The aircraft had allegedly failed to respond to warnings and "continued its flight toward the Sea of Japan".[65][87] Some commentators believe that the inept manner in which the political events were handled by the Soviet government[88] was affected by the failing health of Andropov, who was permanently hospitalised in late September or early October 1983 (Andropov died the following February).[89]

In a 2015 interview Igor Kirillov, the senior Soviet news anchor, said that he was initially given a printed TASS report to announce over the news on September 1, which included an "open and honest" admission that the plane was shot down by mistake (a wrong judgement call by the Far Eastern Air Defence Command). However, at the moment the opening credits of the Vremya evening news programme rolled in, an editor ran in and snatched the sheet of paper from his hand, handing him another TASS report which was "completely opposite" to the first one and to the truth.[90]

U.S. reaction and further developments

File:KAL 007 protests.jpg
Demonstrators near the White House protest the Soviet shootdown of KAL 007 (September 2, 1983)

The shootdown happened at a very tense time in U.S.–Soviet relations during the Cold War. The U.S. adopted a strategy of releasing a substantial amount of hitherto highly classified intelligence information in order to exploit a major propaganda advantage over the Soviet Union.[91]

Six hours after the plane was downed, the South Korean government issued an announcement that the plane had merely been forced to land abruptly by the Soviets, and that all passengers and crew were safe.[92] U.S. Secretary of State George P. Shultz held a press conference about the incident at 10:45 on September 1, during which he divulged some details of intercepted Soviet communications and denounced the actions of the Soviet Union.[87]

On September 5, 1983, President Reagan condemned the shooting down of the airplane as the "Korean airline massacre", a "crime against humanity [that] must never be forgotten" and an "act of barbarism... [and] inhuman brutality".[93] The following day, the U.S. ambassador to the UN Jeane Kirkpatrick delivered an audio-visual presentation in the United Nations Security Council, using audio tapes of the Soviet pilots' radio conversations and a map of Flight 007's path in depicting its shooting down. Following this presentation, TASS acknowledged for the first time that the aircraft had indeed been shot down after warnings were ignored. The Soviets challenged many of the facts presented by the U.S., and revealed the previously unknown presence of a USAF RC-135 surveillance aircraft whose path had crossed that of KAL 007.

On September 7, Japan and the United States jointly released a transcript of Soviet communications, intercepted by the listening post at Wakkanai, to an emergency session of the United Nations Security Council.[94] Reagan issued a National Security Directive stating that the Soviets were not to be let off the hook, and initiating "a major diplomatic effort to keep international and domestic attention focused on the Soviet action".[33] The move was seen by the Soviet leadership as confirmation of the West's bad intentions.

A high level U.S.–Soviet summit, the first in nearly a year, was scheduled for September 8, 1983, in Madrid.[65] The ShultzGromyko meeting went ahead, but was overshadowed by the KAL 007 event.[65] It ended acrimoniously, with Shultz stating: "Foreign Minister Gromyko's response to me today was even more unsatisfactory than the response he gave in public yesterday. I find it totally unacceptable."[65] Reagan ordered the Federal Aviation Administration (FAA) on September 15, 1983, to revoke the license of Aeroflot Soviet Airlines to operate flights to and from the United States. Aeroflot flights to North America were consequently available only through Canadian and Mexican cities, forcing the Soviet foreign minister to cancel his scheduled trip to the UN. Aeroflot service to the U.S. was not restored until April 29, 1986.[95]

An emergency session of the ICAO was held in Montreal, Canada.[96] On September 12, 1983, the Soviet Union used its veto to block a United Nations resolution condemning it for shooting down the aircraft.[64]

Shortly after the Soviet Union shot down KAL 007, the Port Authority of New York and New Jersey, operating the commercial airports around New York City, denied Soviet aircraft landing rights, in violation of the United Nations Charter that required the host nation to allow all member countries access to the UN. In reaction, TASS and some at the UN raised the question of whether the UN should move its headquarters from the United States. Charles Lichenstein, acting U.S. permanent representative to the UN under Ambassador Kirkpatrick, responded, "We will put no impediment in your way. The members of the U.S. mission to the United Nations will be down at the dockside waving you a fond farewell as you sail off into the sunset." Administration officials were quick to announce that Lichenstein was speaking only for himself.[97]

In the Cold War context of Operation RYAN, the Strategic Defence Initiative, Pershing II missile deployment in Europe, and the upcoming Exercise Able Archer, the Soviet Government perceived the incident with the South Korean airliner to be a portent of war.[89] The Soviet hierarchy took the official line that KAL Flight 007 was on a spy mission, as it "flew deep into Soviet territory for several hundred kilometres [miles], without responding to signals and disobeying the orders of interceptor fighter planes".[4] They claimed its purpose was to probe the air defences of highly sensitive Soviet military sites in the Kamchatka Peninsula and Sakhalin Island.[4] The Soviet government expressed regret over the loss of life, but offered no apology and did not respond to demands for compensation.[98] Instead, the Soviet Union blamed the CIA for this "criminal, provocative act".[4]

In a comparative study of the two tragedies published in 1991, political scientist Robert Entman points out that with KAL 007, "the angle taken by the US media emphasised the moral bankruptcy and guilt of the perpetrating nation. With Iran Air 655, the frame de-emphasised guilt and focused on the complex problems of operating military high technology".[99]

Investigations

NTSB

Since the aircraft had departed from U.S. soil and U.S. nationals had died in the incident, the National Transportation Safety Board (NTSB) was legally required to investigate. On the morning of September 1, the NTSB chief in Alaska, James Michelangelo, received an order from the NTSB in Washington at the behest of the State Department requiring all documents relating to the NTSB investigation to be sent to Washington, and notifying him that the State Department would now conduct the investigation.[100]

The U.S. State Department, after closing the NTSB investigation on the grounds that it was not an accident, pursued an ICAO investigation instead. Commentators such as Johnson point out that this action was illegal, and that in deferring the investigation to the ICAO, the Reagan administration effectively precluded any politically or militarily sensitive information from being subpoenaed that might have embarrassed the administration or contradicted its version of events.[101] Unlike the NTSB, ICAO can subpoena neither persons nor documents and is dependent on the governments involved—in this incident, the United States, the Soviet Union, Japan, and South Korea—to supply evidence voluntarily.

Initial ICAO investigation (1983)

The International Civil Aviation Organization (ICAO) had only one experience of investigation of an air disaster prior to the KAL 007 shootdown. This was the incident of February 21, 1973, when Libyan Arab Airlines Flight 114 was shot down by Israeli F-4 jets over the Sinai Peninsula. ICAO convention required the state in whose territory the accident had taken place (the Soviet Union) to conduct an investigation together with the country of registration (South Korea), the country whose air traffic control the aircraft was flying under (Japan), as well as the country of the aircraft's manufacturer (USA).

The ICAO investigation, led by Caj Frostell,[102] did not have the authority to compel the states involved to hand over evidence, instead having to rely on what they voluntarily submitted.[103] Consequently, the investigation did not have access to sensitive evidence such as radar data, intercepts, ATC tapes, or the Flight Data Recorder (FDR) and Cockpit Voice Recorder (CVR) (whose discovery the U.S.S.R. had kept secret). A number of simulations were conducted with the assistance of Boeing and Litton (the manufacturer of the navigation system).[104]

The ICAO released their report December 2, 1983, which concluded that the violation of Soviet airspace was accidental: One of two explanations for the aircraft's deviation was that the autopilot had remained in HEADING hold instead of INS mode after departing Anchorage. They postulated that this inflight navigational error was caused by either the crew's failure to select INS mode, or the inertial navigation's not activating when selected, because the aircraft was already too far off track.[26] It was determined that the crew did not notice this error or subsequently perform navigational checks, that would have revealed that the aircraft was diverging further and further from its assigned route. This was later deemed to be caused by a "lack of situational awareness and flight deck coordination".[105]

The report included a statement by the Soviet Government claiming "no remains of the victims, the instruments or their components or the flight recorders have so far been discovered".[106] This statement was subsequently shown to be untrue by Boris Yeltsin's release in 1993 of a November 1983 memo from KGB head Viktor Chebrikov and Defence Minister Dmitriy Ustinov to Yuri Andropov. This memo stated "In the third decade of October this year the equipment in question (the recorder of in-flight parameters and the recorder of voice communications by the flight crew with ground air traffic surveillance stations and between themselves) was brought aboard a search vessel and forwarded to Moscow by air for decoding and translation at the Air Force Scientific Research Institute."[107] The Soviet Government statement would further be contradicted by Soviet civilian divers who later recalled that they viewed wreckage of the aircraft on the bottom of the sea for the first time on September 15, two weeks after the plane had been shot down.[108]

Following publication of the report, the ICAO adopted a resolution condemning the Soviet Union for the attack.[109] Furthermore, the report led to a unanimous amendment in May 1984 – though not coming into force until October 1, 1998 – to the Convention on International Civil Aviation that defined the use of force against civilian airliners in more detail.[110] The amendment to section 3(d) reads in part: "The contracting States recognize that every State must refrain from resorting to the use of weapons against civil aircraft in flight and that, in case of interception, the lives of persons on board and the safety of aircraft must not be endangered."[111]

U.S. Air Force radar data

It is customary for the Air Force to impound radar trackings involving possible litigation in cases of aviation accidents.[112] In the civil litigation for damages, the United States Department of Justice explained that the tapes from the Air Force radar installation at King Salmon, Alaska pertinent to KAL 007's flight in the Bethel area had been destroyed and could therefore not be supplied to the plaintiffs. At first Justice Department lawyer Jan Van Flatern stated that they were destroyed 15 days after the shootdown. Later, he said he had "misspoken" and changed the time of destruction to 30 hours after the event. A Pentagon spokesman concurred, saying that the tapes are re-cycled for reuse from 24–30 hours afterwards;[113] the fate of KAL 007 was known inside this timeframe.[112]

Interim developments

Hans Ephraimson-Abt, whose daughter Alice Ephraimson-Abt had died on the flight, chaired the American Association for Families of KAL 007 Victims. He single-handedly pursued three U.S. administrations for answers about the flight, flying to Washington 250 times and meeting with 149 State Department officials. Following the dissolution of the U.S.S.R., Ephraimson-Abt persuaded U.S. Senators Ted Kennedy, Sam Nunn, Carl Levin, and Bill Bradley to write to the Soviet President, Mikhail Gorbachev requesting information about the flight.[114]

Glasnost reforms in the same year brought about a relaxation of press censorship; consequently reports started to appear in the Soviet press suggesting that the Soviet military knew the location of the wreckage and had possession of the flight data recorders.[41][115] On December 10, 1991, Senator Jesse Helms of the Committee on Foreign Relations, wrote to Boris Yeltsin requesting information concerning the survival of passengers and crew of KAL 007 including the fate of Congressman Larry McDonald.[116]

On June 17, 1992, President Yeltsin revealed that after the 1991 failed coup attempt concerted attempts were made to locate Soviet-era documents relating to KAL 007. He mentioned the discovery of "a memorandum from K.G.B. to the Central Committee of the Communist Party," stating that a tragedy had taken place and adding that there are documents "which would clarify the entire picture." Yeltsin said the memo continued to say that "these documents are so well concealed that it is doubtful that our children will be able to find them."[117] On September 11, 1992, Yeltsin officially acknowledged the existence of the recorders, and promised to give the South Korean government a transcript of the flight recorder contents as found in KGB files.

In October 1992, Hans Ephraimson-Abt led a delegation of families and U.S. State Department officials to Moscow at the invitation of President Yeltsin.[118] During a state ceremony at St. Catherine's Hall in the Kremlin, the KAL family delegation was handed a portfolio containing partial transcripts of the KAL 007 cockpit voice recorder, translated into Russian, and documents of the Politburo pertaining to the tragedy.

In November 1992, President Yeltsin handed the two recorder containers to Korean President Roh Tae-Woo, but not the tapes themselves. The following month, the ICAO voted to reopen the KAL 007 investigation in order to take the newly released information into account. The tapes were handed to ICAO in Paris on January 8, 1993.[8] Also handed over at the same time were tapes of the ground to air communications of the Soviet military.[119] The tapes were transcribed by the Bureau d'Enquêtes et d'Analyses pour la sécurité de l'Aviation Civile (BEA) in Paris in the presence of representatives from Japan, The Russian Federation, South Korea, and the United States.[119]

A 1993 official enquiry by the Russian Federation absolved the Soviet hierarchy of blame, determining that the incident was a case of mistaken identity.[89] On May 28, 1993, the ICAO presented its second report to the Secretary-General of the United Nations.

Soviet memoranda

File:Mikhail Merchink.jpg
Mikhail Merchink, lead Soviet vessel in simulated search

In 1992, Russian President Boris Yeltsin disclosed five top-secret memos dating from a few weeks after the downing of KAL 007 in 1983.[note 4] The memos contained Soviet communications (from KGB Chief Viktor Chebrikov and Defense Minister Dmitriy Ustinov to General Secretary Yury Andropov) that indicated that they knew the location of KAL 007's wreckage while they were simulating a search and harassing the American Navy; they had found the sought-after cockpit voice recorder on October 20, 1983 (50 days after the incident),[120] and had decided to keep this knowledge secret, the reason being that the tapes could not unequivocally support their firmly held view that KAL 007's flight to Soviet territory was a deliberately planned intelligence mission.[121][122]

<templatestyles src="Template:Quote_box/styles.css" />

Simulated search efforts in the Sea of Japan are being performed by our vessels at present in order to dis-inform the U.S. and Japan. These activities will be discontinued in accordance with a specific plan...

Therefore, if the flight recorders shall be transferred to the western countries their objective data can equally be used by the U.S.S.R. and the western countries in proving the opposite view points on the nature of the flight of the South Korean airplane. In such circumstances a new phase in anti-Soviet hysteria cannot be excluded.

In connection with all mentioned above it seems highly preferable not to transfer the flight recorders to the International Civil Aviation Organization (ICAO) or any third party willing to decipher their contents. The fact that the recorders are in possession of the U.S.S.R. shall be kept secret...

As far as we are aware neither the U.S. nor Japan has any information on the flight recorders. We have made necessary efforts in order to prevent any disclosure of the information in future.

Looking to your approval.

D. Ustinov, V. Chebrikov (photo)[note 5] December 1983

The third memo acknowledges that analysis of the recorder tapes showed no evidence of the Soviet interceptor attempting to contact KAL 007 via radio nor any indication that the KAL 007 had been given warning shots.

However in case the flight recorders shall become available to the western countries their data may be used for: Confirmation of no attempt by the intercepting aircraft to establish a radio contact with the intruder plane on 121.5 MHz and no tracers warning shots in the last section of the flight[123]

That the Soviet search was simulated (while knowing the wreckage lay elsewhere) also is suggested by the article of Mikhail Prozumentshchikov, Deputy Director of the Russian State Archives of Recent History, commemorating the twentieth anniversary of the airplane's shootdown. Commenting on the Soviet and American searches: "Since the U.S.S.R., for natural reasons, knew better where the Boeing had been downed...it was very problematical to retrieve anything, especially as the U.S.S.R. was not particularly interested".[124]

Revised ICAO report (1993)

On November 18, 1992, Russian President Boris Yeltsin, in a goodwill gesture to South Korea during a visit to Seoul to ratify a new treaty, released both the flight data recorder (FDR) and cockpit voice recorder (CVR) of KAL 007.[125] Initial South Korean research showed the FDR to be empty and the CVR to have an unintelligible copy. The Russians then released the recordings to the ICAO Secretary General.[126] The ICAO report continued to support the initial assertion that KAL 007 accidentally flew in Soviet airspace,[105] after listening to the flight crew's conversations recorded by the CVR, and confirming that either the aircraft had flown on a constant magnetic heading instead of activating the INS and following its assigned waypoints, or, if it had activated the INS, it had been activated when the aircraft had already deviated beyond the 7<templatestyles src="Sfrac/styles.css" />1/2-nautical mile Desired Track Envelope within which the waypoints would have been captured.

In addition, the Russian Federation released "Transcript of Communications. U.S.S.R. Air Defence Command Centres on Sakhalin Island" transcripts to ICAO—this new evidence triggered the revised ICAO report in 1993 "The Report of the Completion of the Fact Finding Investigation",[127] and is appended to it. These transcripts (of two reels of tape, each containing multiple tracks) are time specified, some to the second, of the communications between the various command posts and other military facilities on Sakhalin from the time of the initial orders for the shootdown and then through the stalking of KAL 007 by Major Osipovich in his Su-15 interceptor, the attack as seen and commented on by General Kornukov, Commander of Sokol Air Base, down the ranks to the Combat Controller Captain Titovnin.[128]

The transcripts include the post-attack flight of KAL 007 until it had reached Moneron Island, the descent of KAL 007 over Moneron, the initial Soviet SAR missions to Moneron, the futile search of the support interceptors for KAL 007 on the water, and ending with the debriefing of Osipovich on return to base. Some of the communications are the telephone conversations between superior officers and subordinates and involve commands to them, while other communications involve the recorded responses to what was then being viewed on radar tracking KAL 007. These multi-track communications from various command posts telecommunicating at the same minute and seconds as other command posts were communicating provide a "composite" picture of what was taking place.[128]

The data from the CVR and the FDR revealed that the recordings broke off after the first minute and 44 seconds of KAL 007's post missile detonation 12 minute flight. The remaining minutes of flight would be supplied by the Russia 1992 submission to ICAO of the real-time Soviet military communication of the shootdown and aftermath. The fact that both recorder tapes stopped exactly at the same time 1 minute and 44 seconds after missile detonation (18:38:02 UTC) without the tape portions for the more than 10 minutes of KAL 007's post detonation flight before it descended below radar tracking (18:38 UTC) finds no explanation in the ICAO analysis: "It could not be established why both flight recorders simultaneously ceased to operate 104 seconds after the attack. The power supply cables were fed to the rear of the aircraft in raceways on opposite sides of the fuselage until they came together behind the two recorders."[49]

Passenger pain and suffering

Passenger pain and suffering was an important factor in determining the level of compensation that was paid by Korean Air Lines.

Fragments from the proximity fused R-98 medium range air-to-air missile exploding 50 metres (160 ft) behind the tail caused punctures to the pressurized passenger cabin.[61] When one of the flight crew radioed Tokyo Area Control one minute and two seconds after missile detonation his breathing was already "accentuated", indicating to ICAO analysts that he was speaking through the microphone located in his oxygen mask, "Korean Air 007 ah... We are... Rapid compressions. Descend to 10,000."[129]

Two expert witnesses testified at a trial before then Magistrate Judge Naomi Reice Buchwald of the United States District Court for the Southern District of New York. They addressed the issue of pre-death pain and suffering. Captain James McIntyre, an experienced Boeing 747 pilot and aircraft accident investigator, testified that shrapnel from the missile caused rapid decompression of the cabin, but left the passengers sufficient time to don oxygen masks: "McIntyre testified that, based upon his estimate of the extent of damage the aircraft sustained, all passengers survived the initial impact of the shrapnel from the missile explosion. In McIntyre's expert opinion, at least 12 minutes elapsed between the impact of the shrapnel and the crash of the plane, and the passengers remained conscious throughout."[130]

Alternative theories

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Flight 007 has been the subject of ongoing controversy and has spawned a number of conspiracy theories.[131] Many of these are based on the suppression of evidence such as the flight data recorders,[120] unexplained details such as the role of a USAF RC-135 surveillance aircraft,[36][132] the untimely destruction of the U.S. Air Force's King Salmon radar data, Cold War disinformation and propaganda and Gennadiy Osipovich's (the Soviet fighter pilot who shot down flight 007) statement that although he knew the plane was a civilian aircraft, he suspected that it could have been being used as a spy plane.[133][134][135]

Aftermath

"The Tower of Prayer", a monument to KAL 007 at Cape Sōya, Japan

The FAA temporarily closed Airway R-20, the air corridor that Korean Air Flight 007 was meant to follow, on September 2.[136] Airlines fiercely resisted the closure of this popular route, the shortest of five corridors between Alaska and the Far East. It was therefore reopened on October 2 after safety and navigational aids were checked.[137][138]

NATO had decided, under the impetus of the Reagan administration, to deploy Pershing II and Gryphon cruise missiles in West Germany.[139] This deployment would have placed missiles just 6–10 minutes striking distance from Moscow. Support for the deployment was wavering and it looked doubtful that it would be carried out. When the Soviet Union shot down Flight 007, the U.S. was able to galvanize enough support at home and abroad to enable the deployment to go ahead.[140]

The unprecedented disclosure of the communications intercepted by the United States and Japan revealed a considerable amount of information about their intelligence systems and capabilities. National Security Agency director Lincoln D. Faurer commented: "...as a result of the Korean Air Lines affair, you have already heard more about my business in the past two weeks than I would desire... For the most part this has not been a matter of unwelcome leaks. It is the result of a conscious, responsible decision to address an otherwise unbelievable horror."[141] Changes that the Soviets subsequently made to their codes and frequencies reduced the effectiveness of this monitoring by 60%.[142]

The U.S. KAL 007 Victims' Association, under the leadership of Hans Ephraimson-Abt, successfully lobbied U.S. Congress and the airline industry to accept an agreement that would ensure that future victims of airline incidents would be compensated quickly and fairly by increasing compensation and lowering the burden of proof of airliner misconduct.[118] This legislation has had far reaching effects for the victims of subsequent aircraft disasters.

The U.S. decided to utilize military radars to extend air traffic control radar coverage from 200 to 1,200 miles (320 to 1,930 km) out from Anchorage.[note 7] The FAA also established a secondary radar system (ATCBI-5) on Saint Paul Island. In 1986, the United States, Japan and the Soviet Union set up a joint air traffic control system to monitor aircraft over the North Pacific, thereby giving the Soviet Union formal responsibility to monitor civilian air traffic, and setting up direct communication links between the controllers of the three countries.[143]

President Reagan announced on September 16, 1983, that the Global Positioning System (GPS) would be made available for civilian use, free of charge, once completed in order to avert similar navigational errors in the future.[9][10] Furthermore, the interface of the autopilot used on large airliners was modified to make it more obvious whether it is operating in HEADING mode or INS mode.[26]

The regular air route between Seoul and Moscow started in April 1990 as the result of the Nordpolitik policy of South Korea, operated by Aeroflot and Korean Air; meanwhile, all 9 of Korean Air's European routes would start passing through Soviet airspace. This was the first time Korean Air aircraft was officially permitted to pass through Soviet airspace.[144]

Alvin Snyder, the director of worldwide television for the United States Information Agency,[145] was the producer of the video shown to the U.N. Security Council on September 6, 1983.[146] In an article in The Washington Post on September 1, 1996, he stated that he had been given only limited access to the transcripts of the Soviet communication when he produced the video in 1983.[146] When he received full insight into the Soviet transmissions in 1993, he says he realised that: "The Russians (sic) believed the plane to be an RC-135 reconnaissance plane"[146] and that "Osipovich (the Soviet fighter pilot) could not identify the plane"[146] and "That he fired warning cannon shots and tipped his wings, an international signal to force the plane to land".[146] Some of these statements were contradicted by the pilot in an interview with The New York Times,[42] in which he confirmed that he did fire warning shots, but that they would not have been visible as they were not tracers.[147]

In a March 15, 2001, interview, Valery Kamensky, then Commander of the Soviet Far East Military District Air Defense Force and direct superior to General Kornukov, opined that such a shootdown of a civilian passenger plane could not happen again in view of the changing political conditions and alliances. In this interview, Kamensky stated, "It is still a mystery what happened to the bodies of the crew and passengers on the plane. According to one theory, right after the rocket's detonation, the nose and tail section of the jumbo fell off and the mid fuselage became a sort of wind tunnel so the people were swept through it and scattered over the surface of the ocean. Yet in this case, some of the bodies were to have been found during the search operations in the area. The question of what actually happened to the people has not been given a distinct answer."[148]

On September 1, 2003, commenting in a 20th anniversary of the shootdown article in RIA Novosti, Mikhail Prozumentshchikov, Deputy Director of the Russian State Archives of Recent History disclosed that the Soviet naval forces in the search for KAL 007 in international waters, already "knew better where [it] had been downed" while conducting their search, and that nothing was found "especially as the USSR was not particularly interested."[149]

In 2015, Japan's Ministry of Foreign Affairs declassified diplomatic documents which revealed that two months after the catastrophe, a high-ranking official of the U.S. administration confidentially informed Japan's diplomats that the Soviet Union had mistaken the aircraft with an American reconnaissance plane.[150]

Korean Air still flies from New York JFK International Airport to Seoul. However, the flight no longer stops at Anchorage or flies to Gimpo International Airport as it now flies directly to Incheon International Airport. Flight number 007 has been retired since, using flight numbers for two separate flights as 82, 85 and 250. As of September 2018, the separate flights were using an Airbus A380 and a Boeing 777.[151]

Popular culture

Lua error in package.lua at line 80: module 'strict' not found.

  • Two television movies were produced about the incident; both films were produced before the fall of the Soviet Union allowed access to archives:
  • KGO-TV in San Francisco aired a trailer in November 1983 for an upcoming news special report titled "Green Street Reds", about suspicious activities at the Soviet consulate. In the trailer, they depict Santa Claus and his reindeer being shot down by a Soviet missile. Angry parents complained to KGO about the poor impression the image of Santa's death made upon young children.[152]
  • The incident is used as a plot point in the episode "Brandy Station" of Deutschland 83.
  • The incident is referenced in the film A Kiss Before Dying, when hitchhiker Jonathan Corliss (Matt Dillon), in need of a new identity, is prompted to kill the driver when the driver tells him he was left an orphan when both his parents went down on the plane.
  • Irish guitarist and singer Gary Moore's song "Murder in the Skies" was written about this incident. The song was included on Moore's album Victims of the Future, which was released two months after the shootdown in December 1983.
  • The Canadian television show Mayday on the National Geographic Channel covered this accident in a Season 9 episode entitled "Target is Destroyed".
  • This tragedy was used as inspiration for The West Wing episode "The Wake Up Call" in which an Iranian fighter pilot shoots down a British airliner over the Caspian Sea. The airliner was off course and drifting into Iranian airspace. It is said that the airliner was mistaken by the pilot for an American RC-135 spy plane.
  • In the card-driven strategy game Twilight Struggle, "Soviets Shoot Down KAL-007" is a US card that can potentially hand the US an instant win, or otherwise greatly benefit the US.[153]
  • The incident is depicted in the alternate history TV series For All Mankind, in the second season episode entitled "Don't Be Cruel". The show references the spy mission theory, implying that the U.S. military was using the flight to spy on the (fictionalized) launch site of the Soviet Buran shuttle. Additionally, real-life NASA Administrator Thomas O. Paine is killed on KAL 007.

Maps

<templatestyles src="Col-float/styles.css" />

The locations of the incident and the airports
New York City
New York City
Anchorage
Anchorage
Seoul
Seoul
Crash site
Crash site
Location of the incident and the airports

<templatestyles src="Col-float/styles.css" />

Crash site is located in Sakhalin
Crash site
Crash site
Crash site off Sakhalin
File:KA Flight 007.gif
CIA map of KAL Flight 007

See also

Footnotes

  1. 1.0 1.1 3 cockpit crew, 20 cabin crew and 6 deadheading crew (ICAO 93, Sect. 1.3, p. 6)
  2. KAL 007 was used by air traffic control, while the public flight booking system used KE 007
  3. The last plotted radar position of the target was 18:35 hours at 5,000 meters." (ICAO '93, p. 53, para. 2.15.8)
  4. These memos were published in the Soviet news magazine, Izvestia #228, October 15, 1992, shortly after being made public by Yeltsin.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. For illustration only—KAL 007 did not necessarily use this type of recorder.
  7. These radars had been used in 1968 to alert Seaboard World Airlines Flight 253A in a similar situation.

Notes

  1. Aviation Safety Database
  2. 2.0 2.1 2.2 Maier, KAL 007 Mystery
  3. Young & Launer, pp. xiii, 47
  4. 4.0 4.1 4.2 4.3 Sputnik, The Truth and Lies about the South Korean Airliner
  5. Pearson, p. 145
  6. 6.0 6.1 Congressional Record, September 20, 1983, pp. S12462-S12464
  7. Soviet news magazine, Izvestia #228, October 16, 1992
  8. 8.0 8.1 Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 Pellerin, United States Updates Global Positioning System Technology: New GPS satellite ushers in a range of future improvements.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. 13.0 13.1 Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Johnson, p. 6
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Doerner, p. 5
  19. Allardyce and Gollin, August 2007, p. 51
  20. Doerner, p. 4
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. ICAO 1983, appendix C, p. 2.
  23. 23.0 23.1 Lua error in package.lua at line 80: module 'strict' not found.
  24. Rosenthal, p. 70
  25. Daniloff, p. 304
  26. 26.0 26.1 26.2 26.3 26.4 26.5 Degani, 2001
  27. Milde, p. 53
  28. 28.0 28.1 28.2 28.3 Pearson (1987), p. 40
  29. 29.0 29.1 Fred Wyler, Individually and as a Personal Representative of the Estate of William Paul Wyler, Deceased, for the Benefit of Himself and Helen C. Wyler, et al., Appellants v Korean Air Lines Company, Ltd., et al. (United States Court of Appeals, District of Columbia Circuit April 3, 1991). Text
  30. Kleiner, Korea, a Century of Change
  31. Johnson, p. 16
  32. Johnson, p. 55
  33. 33.0 33.1 Richelson, p. 385
  34. Pry, p. 20
  35. 35.0 35.1 35.2 Fischer, A Cold War Conundrum: The 1983 Soviet War Scare
  36. 36.0 36.1 Schultz, p. 367
  37. Radar Outage Cited in KAL Tragedy, Los Angeles Times (from Reuters) January 02, 1993
  38. CBS' "60 Minutes" interview, aired January 3, 1993
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. 41.0 41.1 41.2 41.3 41.4 41.5 41.6 Illesh, The Mystery of the KAL-007
  42. 42.0 42.1 42.2 42.3 Gordon, Ex-Soviet Pilot Still Insists KAL 007 Was Spying
  43. Izvestia, 1991.
  44. Izvestia 1991 interview with Gennadi Osipovich, as quoted in: Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. 49.0 49.1 49.2 49.3 ICAO '93, p. 55
  50. 50.0 50.1 50.2 ICAO '93, p. 54
  51. ICAO '93, Information Paper No. 1, p. 132
  52. ICAO '93, sect. 3.38, p. 61
  53. Johnson, p. 30
  54. Oberg, KAL 007: The Real Story
  55. KAL 007:Cover-Up, David Pearson, Summit Press, N.Y., 1987, p. 122
  56. ICAO '93, 1.2.1, p. 5
  57. Daniloff, p. 300
  58. Norris and Wagner, Boeing
  59. ICAO '93, p. 39
  60. Lua error in package.lua at line 80: module 'strict' not found.
  61. 61.0 61.1 61.2 ICAO '93, Information Paper 1, p. 93
  62. Lua error in package.lua at line 80: module 'strict' not found.
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. 64.0 64.1 Isaacson et al., 1983
  65. 65.0 65.1 65.2 65.3 65.4 65.5 Oberdorfer, p. 51
  66. Lua error in package.lua at line 80: module 'strict' not found.
  67. ICAO, '93, Information Paper No. 1., pp. 95–96
  68. 68.0 68.1 Shootdown, R.W. Johnson, Viking, New York, 1985, p. 194
  69. 69.0 69.1 ICAO '93, p. 17, sect. 1.11.7
  70. After Action Report Department of the Navy, Commander, Surface Combat Force Seventh Fleet. CTF75/N32:kpm,4730, Ser 011, 15 November 1983
  71. Lua error in package.lua at line 80: module 'strict' not found.
  72. Winkler, p. 47
  73. Commander of Task Force 71 of U.S. 7th Fleet, stated in his After Action Report (Department of the Navy, Commander, Surface Combat Force Seventh Fleet. CTF75/N32:kpm,4730, Ser 011, November 15, 1983)
  74. ICAO Report, p. 28
  75. After Action Report (Department of the Navy, Commander, Surface Combat Force Seventh Fleet. CTF75/N32:kpm,4730, Ser 011, November 15, 1983)
  76. KAL 007: The Cover-up, David Pearce, Summit Books, N.Y., 1987, p. 250
  77. Izvestia, February 1991, p. 7
  78. 78.0 78.1 Lua error in package.lua at line 80: module 'strict' not found.
  79. Brun, pp. 143–44.
  80. Kantakov and Shevchenko, In situ observations of Tsushima and West Sakhalin currents near La Perouse (Soya) Strait
  81. Lua error in package.lua at line 80: module 'strict' not found.
  82. Pearson, p. 235
  83. Lua error in package.lua at line 80: module 'strict' not found.
  84. World Wide Issues, February 6, 1991, p. 21
  85. Izvestia, 28 May 1991, p. 8
  86. ICAO '93, Sect. 1.12.4
  87. 87.0 87.1 Daniloff, p. 294
  88. Dallin, p. 89
  89. 89.0 89.1 89.2 Pry, pp. 27–32
  90. Lua error in package.lua at line 80: module 'strict' not found.
  91. Johnson, pp. 117–21
  92. Lua error in package.lua at line 80: module 'strict' not found.
  93. Lua error in package.lua at line 80: module 'strict' not found.
  94. Ball, pp. 42–46
  95. The Current Digest of the Soviet Press.
  96. Lua error in package.lua at line 80: module 'strict' not found.
  97. Luck, Mixed Messages: American Politics and International Organization, 1919–1999, p. 64
  98. Johnson, p. 110
  99. Lua error in package.lua at line 80: module 'strict' not found.
  100. Pearson, p. 127
  101. Johnson, p. 227
  102. Lua error in package.lua at line 80: module 'strict' not found.
  103. Johnson, p. 231
  104. Johnson, p. 232
  105. 105.0 105.1 Lua error in package.lua at line 80: module 'strict' not found.
  106. Appendix F, ICAO 83
  107. Izvestia #228, October 16, 1992
  108. May 7, 1991, p. 6
  109. Merrills, p. 61
  110. Lua error in package.lua at line 80: module 'strict' not found.
  111. Lua error in package.lua at line 80: module 'strict' not found.
  112. 112.0 112.1 Pearson, p. 309
  113. U.S. District Court, District of Columbia, In re: Korean Airlines disaster of September 1, 1983, February 28, 1985
  114. Lua error in package.lua at line 80: module 'strict' not found.
  115. Charles, p. 16
  116. Lua error in package.lua at line 80: module 'strict' not found.
  117. Lua error in package.lua at line 80: module 'strict' not found.
  118. 118.0 118.1 Lua error in package.lua at line 80: module 'strict' not found.
  119. 119.0 119.1 Lua error in package.lua at line 80: module 'strict' not found.
  120. 120.0 120.1 Lua error in package.lua at line 80: module 'strict' not found.
  121. Daniloff, p. 303
  122. Andrew, p. 60
  123. Conclusions by the Group of Experts of the Defense Ministry, KGB of the U.S.S.R. and Ministry of Aerospace Industry, Head of the Group Lieutenant-General of Aviation Makarov Staff of the Group Lieutenant-General Engineer Tichomirov Major-General Engineer Didenko Major -General of Aviation Stepanov Major -General of Aviation Kovtun Corresponding Member of Academy of Sciences of the U.S.S.R. Fedosov November 28, 1983
  124. Lua error in package.lua at line 80: module 'strict' not found.
  125. Ross, East Asia in Transition: Toward a New Regional Order
  126. Lua error in package.lua at line 80: module 'strict' not found.
  127. Lua error in package.lua at line 80: module 'strict' not found.
  128. 128.0 128.1 ICAO '93, Information Paper No. 1, pp. 48–208
  129. ICAO '93, p. 35
  130. See Hollie v. Korean Air Lines Co., Ltd., 60 F.3d 90 (2d Cir. 1995) (decision from the United States Court of Appeals for the Second Circuit Nos. 907, 1057 August Term, 1994 (Argued: April 5, 1995, Decided: July 12, 1995, Docket Nos. 94–7208, 94–7218)).
  131. Knight, p. 381
  132. Johnson, p. 175
  133. Pry, p. 31
  134. Pearson, p. 17
  135. Young, p. 137
  136. Lua error in package.lua at line 80: module 'strict' not found.
  137. Lua error in package.lua at line 80: module 'strict' not found.
  138. Pearson, p. 256
  139. Blacker, p. 308
  140. Johnson, p. 75
  141. Lua error in package.lua at line 80: module 'strict' not found.
  142. Baltimore Sun, September 15, 1983, via Johnson, p. 60
  143. Taubman, Keeping the Air Lanes Free: Lessons of a Horror.
  144. Lua error in package.lua at line 80: module 'strict' not found.
  145. Lua error in package.lua at line 80: module 'strict' not found.
  146. 146.0 146.1 146.2 146.3 146.4 "Flight 007: The rest of the story", Washington Post, September 1, 1996.
  147. Discovery Channel, episode "Unsolved History, KAL 007"
  148. Fakty i Kommentarii, March 15, 2001
  149. Lua error in package.lua at line 80: module 'strict' not found.
  150. Lua error in package.lua at line 80: module 'strict' not found.
  151. Lua error in package.lua at line 80: module 'strict' not found.
  152. Lua error in package.lua at line 80: module 'strict' not found.
  153. Lua error in package.lua at line 80: module 'strict' not found.

References

Lua error in package.lua at line 80: module 'strict' not found.

Books

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

Journals

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.[permanent dead link]
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

Online sources

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found. This article was adapted from a book chapter, entitled "The Crash of Korean Air Lines Flight 007," which appeared in Degani, A. (2004). Taming HAL: Designing Interfaces Beyond 2001. New York: St. Martin's Press (Palgrave-Macmillan)
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found..
  • Lua error in package.lua at line 80: module 'strict' not found.

Further reading

External links