Open Access Articles- Top Results for Korean Air Lines Flight 007

Korean Air Lines Flight 007

"Flight 007" redirects here. For other uses, see [[Flight 7 (disambiguation)#REDIRECTmw:Help:Magic words#Other
This page is a soft redirect.Flight 7]].

Korean Air Lines Flight 007
HL7442, the aircraft involved in the incident
Shootdown summary
Date 1 September 1983
Summary Airliner shootdown

Near Moneron Island, west of Sakhalin Island, Soviet Union
46°34′N 141°17′E / 46.567°N 141.283°E / 46.567; 141.283 (KAL007)Coordinates: 46°34′N 141°17′E / 46.567°N 141.283°E / 46.567; 141.283 (KAL007){{#coordinates:46|34|N|141|17|E|type:event|| |primary |name=KAL007

Passengers 246[1]
Crew 23[note 1]
Fatalities 269 (all)
Survivors 0
Aircraft type Boeing 747-230B
Operator Korean Air Lines
Registration HL7442 (previously D-ABYH)
Flight origin John F. Kennedy International Airport,
New York City, United States
Stopover Anchorage International Airport,
Anchorage, Alaska, United States
Destination Gimpo International Airport,
Gangseo-gu, Seoul, South Korea

Korean Air Lines Flight 007 (also known as KAL007 and KE007[note 2]) was a scheduled Korean Air Lines flight from New York City to Seoul via Anchorage. On September 1, 1983, the airliner serving the flight was shot down by a Soviet Su-15 interceptor near Moneron Island, west of Sakhalin Island, in the Sea of Japan. The interceptor's pilot was Major Gennadi Osipovich. All 269 passengers and crew aboard were killed, including Lawrence McDonald, Representative from Georgia in the United States House of Representatives. The aircraft was en route from Anchorage to Seoul when it flew through prohibited Soviet airspace around the time of a U.S. reconnaissance mission.

The Soviet Union initially denied knowledge of the incident,[2] but later admitted the shootdown, claiming that the aircraft was on a spy mission.[3] The Politburo said it was a deliberate provocation by the United States[4] to test 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.[5] The Soviet military suppressed evidence sought by the International Civil Aviation Organization (ICAO) investigation, such as the flight data recorders,[6] which were released eight years later after the collapse of the Soviet Union.[7]

The incident was one of the tensest moments of the Cold War and resulted in an escalation of anti-Soviet sentiment, particularly in the United States. The opposing points of view on the incident were never fully resolved. Consequently, several groups continue to dispute official reports and offer alternative theories of the event. The subsequent release of KAL 007 flight transcripts and flight recorders by the Russian Federation has clarified some details.

As a result of the incident, the United States altered tracking procedures for aircraft departing Alaska. The interface of the autopilot used on airliners was redesigned to make it more ergonomic.[8] In addition, the event was one of the most important single events that prompted the Reagan administration to allow worldwide access to the United States military's GNSS system, which was classified at the time. Today this system is widely known as GPS.

Details of the flight

Nationality Victims
23x15px Australia 2
23x15px British Hong Kong 12
23x15px Canada 8
23x15px Dominican Republic 1
Template:Country data India 1
Template:Country data Iran 1
Template:Country data Japan 28
23x15px Malaysia 1
23x15px Philippines 16
Template:Country data South Korea 105 *
23x15px Sweden 1
23x15px Taiwan 23
23x15px Thailand 5
23x15px United Kingdom 2
23x15px United States 62
23x15px Vietnam 1
Total 269

* 76 passengers, 23 active crew and 6 deadheading crew.[9]

The aircraft flying as Korean Air Lines Flight 007 was a commercial Boeing 747-230B delivered on January 28, 1972, with the serial number CN20559/186 and registration HL7442 (formerly D-ABYH[10] operated by Condor). The aircraft departed Gate 15 of John F. Kennedy International Airport, New York City on August 30, 1983, bound for Gimpo Airport in Gangseo-gu, Seoul, 35 minutes behind its scheduled departure time of 23:50 EDT (03:50 UTC, August 31). The flight was carrying 246 passengers and 23 crew members.[note 1][11] After refueling at Anchorage International Airport in Anchorage, Alaska, the aircraft, piloted on this leg of the journey by Captain Chun Byung-in,[12] departed for Seoul at 04:00 Alaska Time (13:00 UTC) on August 31, 1983.

The aircrew had an unusually high ratio of crew to passengers, as six deadheading crew were on board.[13] Twelve passengers occupied the upper deck first class, while in business almost all of 24 seats were taken; in economy class, approximately 80 seats did not contain passengers. There were 22 children under the age of 12 years aboard. One hundred and thirty passengers planned to connect to other destinations such as Tokyo, Hong Kong, and Taipei.[14]

U.S. congressman Lawrence McDonald from Georgia, who at the time was also the second president of the conservative John Birch Society, was on the flight. Senator Jesse Helms of North Carolina, Senator Steven Symms of Idaho, and Representative Carroll J. Hubbard, Jr. of Kentucky were aboard sister flight KAL 015, which flew 15 minutes behind KAL 007; they were headed, along with McDonald on KAL 007, to Seoul, South Korea, in order to attend the ceremonies for the thirtieth anniversary of the U.S.-South Korea Mutual Defense Treaty.[citation needed] The Soviets contended former U.S. president Richard Nixon was to have been seated next to Larry McDonald on KAL 007 but that the CIA warned him not to go, according to the New York Post and Telegraph Agency of the Soviet Union (TASS); this was denied by Nixon.[15]

Flight deviation from assigned route

Another photograph of HL7442.
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".[16][17] Upon arriving over Bethel, Alaska, flight 007 entered the northernmost of five Script error: No such module "convert". wide airways, known as the NOPAC (North Pacific) routes, that bridge the Alaskan and Japanese coasts. KAL 007's particular airway, R-20 (Romeo 20), passes just Script error: No such module "convert". from what was then Soviet airspace off the Kamchatka coast.

The autopilot system used at the time had 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 ground VOR (VHF omnidirectional range) or Localizer 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 Script error: No such module "convert". of that course line. If, however, the plane was more than Script error: No such module "convert". 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 Script error: No such module "convert". 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 Script error: No such module "convert". 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.[18]

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.[18]

The Anchorage VOR beacon was not operational because of maintenance.[19] 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, Script error: No such module "convert". 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 USSR 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, KAL 007, flying on a heading of 245 degrees, 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.[20]

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.[8][21] 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 (shortly after Cairn Mountain), or they did select the INS mode, but the computer did not transition from INERTIAL NAVIGATION ARMED to INS mode because the aircraft had already deviated off track by more than the Script error: No such module "convert". 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.[8]

At 28 minutes after takeoff, civilian radar at Kenai, on the eastern shore of Cook Inlet and with radar coverage Script error: No such module "convert". west of Anchorage, tracked KAL 007 Script error: No such module "convert". north of where it should have been.[22]

When KAL 007 did not reach Bethel at 50 minutes after takeoff, a military radar at King Salmon, Alaska, tracked KAL 007 at Script error: No such module "convert". 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, Script error: No such module "convert". of error being the maximum expected drift from course if the inertial navigation system was activated.[22]

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.[23] KAL 007 requested KAL 015 to relay its position three times in total. 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,[24] 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 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[22] and was not considered unusual by air traffic controllers.[23] Halfway between Bethel and waypoint NABIE, KAL 007 passed through the southern portion of the North American Air Defense 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—Script error: No such module "convert". off course at waypoint NABIE, Script error: No such module "convert". off course at waypoint NUKKS, and Script error: No such module "convert". off course at waypoint NEEVA—until it reached the Kamchatka Peninsula.[9]

Airway R20 waypoint Flight-planned coordinates ATC KAL 007 deviation
CAIRN MOUNTAIN N|155.328|W |type:mountain_region:US name=KAL007 Cairn Mountain


Anchorage Script error: No such module "convert".
BETHEL 47|32|N|161|45|21|W |type:city_region:US name=KAL007 Bethel


Anchorage Script error: No such module "convert".
NABIE 18.0|N|171|45.4|W |type:landmark name=KAL007 NABIE


Anchorage Script error: No such module "convert".
NUKKS 15|N|179|44.3|E |type:landmark name=KAL007 NUKKS


Anchorage Script error: No such module "convert".
NEEVA 40.7|N|172|11.8|E |type:landmark name=KAL007 NEEVA


Anchorage Script error: No such module "convert".
NINNO 21.5|N|165|22.8|E |type:landmark name=KAL007 NINNO


NIPPI 41.9|N|159|19.3|E |type:landmark name=KAL007 NIPPI


Anchorage/Tokyo Script error: No such module "convert".[25]
NYTIM 11.9|N|153|00.5|E |type:landmark name=KAL007 NYTIM


Tokyo Script error: No such module "convert". to point of impact
NOKKA 23.3|N|147|28.8|E |type:landmark name=KAL007 NOKKA


Tokyo Script error: No such module "convert". to point of impact
NOHO 25.0|N|145|00.0|E |type:landmark name=KAL007 NOHO


Tokyo Script error: No such module "convert". to point of impact


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 Pershing II missiles in Europe in March and April, and FleetEx '83, the largest fleet exercise held to date in the North Pacific.[26] The military hierarchy of the Soviet Union (particularly the old guard led by Soviet General Secretary Yuri Andropov and Soviet Defense Minister Dmitry Ustinov) viewed these actions as bellicose and destabilizing; they were deeply suspicious of US President Ronald Reagan's intentions and openly fearful he was planning a first strike nuclear attack against the Soviet Union. These fears culminated in Operation 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.[27]

Aircraft from USS Midway and USS Enterprise repeatedly overflew Soviet military installations in the disputed Kurile Islands during FleetEx '83,[28] resulting in the dismissal or reprimanding of Soviet military officials who had been unable to shoot them down.[29] On the Soviet side, Operation RYAN was expanded.[29] 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 that was scheduled for the same day. A United States Air Force RC-135 reconnaissance aircraft flying in the area was monitoring the missile test off the peninsula.[30]

At 15:51 UTC, according to Soviet sources,[22] KAL 007 entered the restricted airspace of the Kamchatka Peninsula. The buffer zone extended Script error: No such module "convert". from Kamchatka's coast and is known as a Flight Information Region (FIR). The Script error: No such module "convert". radius of the buffer zone nearest to Soviet territory had the additional designation of prohibited airspace. When KAL 007 was about Script error: No such module "convert". from the Kamchatka coast, one MiG-23 and three Su-15 Flagon fighters were scrambled to intercept the Boeing 747.[8]

Significant command and control problems were experienced trying to vector the fast military jets onto the Boeing 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 Arctic gales had knocked out Soviet radar ten days before.[31] The unidentified jetliner therefore crossed over the Kamchatka Peninsula back into international airspace over the Sea of Okhotsk without being intercepted.

The Commander of the Soviet Far East District Air Defense Forces, General Valery Kamensky,[32] 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" 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."

Soviet Air Defence Force units 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 re-entered their airspace over Sakhalin Island.[8] After the protracted ground-controlled interception, the three Su-15 fighters (from nearby Dolinsk-Sokol airbase) and the MiG-23[33] (from Smirnykh Air Base) managed to make visual contact with the Boeing. The pilot of the lead Su-15 fighter fired warning shots, but recalled later in 1991:[34]

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...

At this point, KAL 007 contacted Tokyo air traffic control 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, an action that 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 who were 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 Kaliningrad K-8 (NATO reporting name: AA-3 'Anab') air-to-air missiles at the plane.[35]

Soviet pilot's recollection of shootdown

In a 1991 interview with Izvestia, Major Genadi 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".[36] He continued, saying that "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..."[36] He furthermore did not provide a detailed description of the aircraft to his ground controllers: "I did not tell the ground that it was a Boeing-type plane; they did not ask me."[34][36][note 3]

File:Sukhoi SU-15TM 2008 G2.jpg
Kaliningrad R-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:

"They [KAL 007] quickly lowered their speed. They were flying at Script error: No such module "convert".. 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 2,000 meters... afterburners. Switched on the missiles and brought the nose up sharply. Success! I have a lock on."[37]

"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."[38]

Soviet command hierarchy of shootdown

File:Vladimir Putin with Anatoly Kornukov-1.jpg
Anatoly Kornukov receiving an award from Vladimir Putin in the Grand Kremlin Palace, Moscow (2000)

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.[39][40] In reverse order, they are:

  • Major Gennady 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."[41]

Post-attack flight

At the time of the attack, the plane had been cruising at an altitude of about Script error: No such module "convert".. 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.[42]

At 18:26:46 UTC,[43] at the apex of the arc at altitude Script error: No such module "convert".,[42] either the pilot was able to turn off the autopilot or the autopilot tripped and the plane began to descend to Script error: No such module "convert".. From 18:27:01 until 18:27:09, the flight crew reports to Tokyo Radio informing that KAL 007 to "descend to 10,000" [feet]. At 18:27:20, ICAO graphing of Digital Flight Data Recorder tapes show that after a descent phase and a 10 second "nose-up", KAL 007 is now leveled out at pre-missile detonation altitude of Script error: No such module "convert"., forward acceleration is now back to pre-missile detonation rate of zero acceleration, and air speed has returned to pre-detonation velocity.

Yaw (oscillations), begun at the time of missile detonation, continue decreasingly until the end of the minute 44 second portion 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 feet (18:30–18:31 UTC), rather than continue descending to 10,000 as previously reported to Tokyo Radio, continuing 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.[44] ICAO analysis concluded that the flight crew "retained limited control" of the aircraft.[45] Finally, the aircraft began to descend in spirals over Moneron Island before coming down Script error: No such module "convert"., killing all 269 on board.[note 4] 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 Script error: No such module "convert"..[46]

KAL 007 was probably attacked in international airspace, with a 1993 Russian report listing the location of the missile firing outside its territory at 46°46′27″N 141°32′48″E / 46.77417°N 141.54667°E / 46.77417; 141.54667 (KAL007){{#coordinates:46|46|27|N|141|32|48|E |type:event | |name=KAL007 }},[29][47] although the intercepting pilot stated otherwise in a subsequent interview. Initial reports that the airliner had been forced to land on Sakhalin were soon proved false. 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".[48]

A Japanese fisherman aboard the 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"[49] and smelled aviation fuel.[50]

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 Script error: No such module "convert"., and then, after almost 5 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:

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.[43] The hydraulics provided actuation for all the primary flight controls; all secondary flight controls except leading edge slats; and landing gear retraction, extension, gear steering, and wheel braking. Each primary flight control axis received power from all four hydraulic systems.[51] 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 Script error: No such module "convert".. 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".[43]
Left wing
Contrary to Major Osipovich's statement in 1991 that he had taken off half of KAL 007's left wing,[34] 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."[52]
The co-pilot reported to Captain Chun twice during the flight after the missile's detonation, "Engines normal, sir."[53]
Tail section
The first missile was radar-controlled and proximity fuzed, and detonated Script error: No such module "convert". behind the aircraft. Sending fragments forward, it either severed or unraveled the crossover cable from the left inboard elevator to the right elevator.[42] This, with damage to one of the four hydraulic systems, caused KAL 007 to ascend from Script error: No such module "convert"., at which point the autopilot was disengaged.
Shrapnel from the proximity fuzed air-to-air missile that detonated Script error: No such module "convert". behind the aircraft, punctured the fuselage and caused rapid decompression of the pressurized 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 total size of the ruptures to the pressurized fuselage was Script error: No such module "convert"..[54])

Search and rescue

As a result of Cold War tensions, the search and rescue operations of the Soviet Union were not co-ordinated 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.[55] The flight data recorders were the key pieces of evidence sought by both factions, 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.[56] 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.[57]

Soviet search and rescue mission to Moneron Island

The Soviets did not acknowledge shooting down the aircraft until September 6, 1983.[58] 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."[59]

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, 9 minutes after KAL 007 had disappeared from Soviet radar screens, and brought rescue helicopters from Khomutovo Air base, the civilian and military airport at Yuzhno-Sakhalinsk City in southern Sakhalin, and KGB boats to the area.[54]

The second search was ordered 8 minutes later by the Deputy Commander of the Far Eastern Military District, Gen. 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."[60] Moneron is just Script error: No such module "convert". long and Script error: No such module "convert". wide, located Script error: No such module "convert". due west of Sakhalin Island at 46°15′N 141°14′E / 46.250°N 141.233°E / 46.250; 141.233 (Moneron Island){{#coordinates:46|15|N|141|14|E|region:RU_type:isle|| | |name=Moneron Island }}; it is the only land mass in the whole Tatar Straits.

Search for KAL 007 in international waters

File:USNS Narragansett (T-ATF 167) deploys Deep Drone RSV.jpg
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.[61]

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)[62] 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 had been reclassified from a "Search and Rescue" (SAR) operation to a "Search and Salvage" (SAS).[63]

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 William Cockell was relieved of command of the Task Force and its Search and Salvage mission, and Rear Admiral Walter T. Piotti, Jr., was placed in command. First to be searched was a Script error: No such module "convert". "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 Script error: No such module "convert"., reaching to the west of Sakhalin Island. This was the "large probability" area. The search areas were outside the Script error: No such module "convert". Soviet-claimed territorial boundaries. The northwestern-most point of the search touched the Soviet territorial boundary closest to the naval port of Nevelsk on Sakhalin. Nevelsk was Script error: No such module "convert". from Moneron. This larger search was also unsuccessful.[63]

The vessels used in the search, for the Soviet side as well as the Allied side (U.S., 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 Script error: No such module "convert". "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.

Rear Admiral Walter T. Piotti Jr, commander of Task Force 71 of 7th Fleet would summarize the U.S. and Allied, and then the Soviets’, Search and Salvage operations:

“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.”[64]

File:After Action Report Map.jpg
U.S. Task Force 71 After action report map of search area in international waters.

These missions met with interference by the Soviets,[65] 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 (7 Sept.), attempted ramming of rigs used by the South Koreans in their quadrant search, hazardous maneuvering of the 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 the Kaiko Maru III, and radar lock-ons by a Soviet [[Kara class cruiser #REDIRECTmw:Help:Magic words#Other
This page is a soft redirect.Kara-class]] cruiser, the Petropavlovsk, and a [[Kashin class destroyer #REDIRECTmw:Help:Magic words#Other
This page is a soft redirect.Kashin-class]] destroyer, the Odarennyy, targeting U.S. naval vessels. USS Towers, escorting USS Conserver, experienced all of the above interference and was involved in a near-collision with the Odarennyy (September 23–27).[66][67]

According to the ICAO: "The location of the main wreckage was not determined... the approximate position was 46°34′N 141°17′E / 46.567°N 141.283°E / 46.567; 141.283 (KAL007){{#coordinates:46|34|N|141|17|E|type:event|| | |name=KAL007 }}, which was in international waters." This point is about Script error: No such module "convert". from Moneron Island, about Script error: No such module "convert". from the shore of Sakhalin and Script error: No such module "convert". from the point of attack.[68]

Rear Admiral Walter T. 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:[69]

"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."[35]

At a hearing of the ICAO on September 15, 1983, J. Lynn Helms, the head of the Federal Aviation Administration, stated:[5] "The U.S.S.R. 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 to Nevelsk on Sakhalin. On Monday, September 26, 1983, a delegation of seven Japanese and American 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 Americans and 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.[70] The Soviets said that these were all that they had retrieved; they had found floating in the water or washed up 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."[71]

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."[72] John Oldham had taken his seat in row 31 of KAL 007 wearing those cream white paint-spattered sneakers.[72]

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 Script error: No such module "convert". search area.[73]

Hokkaido finds

Eight days after the shootdown, human remains appeared on the north shore of Hokkaido, Japan. Hokkaido is about Script error: No such module "convert". below the southern tip of Sakhalin across the Soya Strait (the southern tip of Sakhalin is Script error: No such module "convert". from Moneron Island which lies to the west of Sakhalin). The ICAO concluded that these 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.[74]

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[75] of Sault Ste. Marie, Ontario, Canada, and the business card of passenger Kathy Brown-Spier.[76] These items generally come from the passenger cabin of an aircraft. None of the items found generally come from the cargo hold of a plane, such as suitcases, packing boxes, industrial machinery, instruments, and sports equipment.

Soviet diver reports

In 1991, 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.[34] After three days of searching using trawlers, side-scan sonar, and diving bells, the aircraft wreckage was located by Soviet searchers at a depth of Script error: No such module "convert". near Moneron Island.[34][77] 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 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..."[34]

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

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...’[79]

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 Viyacheslav 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."[80]

Political events

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 U.S.S.R.[81] 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.[82]

Secretary of State George P. Shultz held a press conference about the incident at 10:45 on 1 September, during which he divulged some details of intercepted Soviet communications and denounced the actions of the Soviet Union.[83]

General Secretary Yuri Andropov, on the advice of Defense Minister Dmitriy Ustinov, but against 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.[58] 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".[58][83] Some commentators believe that the inept manner in which the political events were handled by the Soviet government[84] was affected by the failing health of Andropov, who was permanently hospitalised in late September or early October 1983 (Andropov died the following February).[85]

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

On September 5, 1983, U.S. President Ronald 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".[86] The following day, the US 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 for the first time, mentioned the 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.[87] US President 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".[27] The move was seen by the Soviet leadership of 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.[58] The ShultzGromyko meeting went ahead, but was overshadowed by the KAL 007 event.[58] 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."[58] President 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 US. 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.[88]

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

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 US permanent representative to the UN under Ambassador Kirkpatrick, responded, "We will put no impediment in your way. The members of the US 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.[90]

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.[85] 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, without responding to signals and disobeying the orders of interceptor fighter planes".[3] They claimed its purpose was to probe the air defences of highly sensitive Soviet military sites in the Kamchatka Peninsula and Sakhalin Island.[3] The Soviet government expressed regret over the loss of life, but offered no apology and did not respond to demands for compensation.[91] Instead, the USSR blamed the CIA for this "criminal, provocative act".[3]



Since the aircraft had departed from US soil and US 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.[92]

The US 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.[93] 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)

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 U.S.S.R.) 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 aircraft's manufacturer (Boeing).

The ICAO investigation, led by Caj Frostell,[94] did not have the authority to compel the states involved to hand over evidence, instead having to rely on what they voluntarily submitted.[95] 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).[96]

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.[8] 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".[97]

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".[98] 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."[99] 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 sea for the first time on 15 September, two weeks after the plane had been shot down.[100]

Following publication of the report, the ICAO adopted a resolution condemning the Soviet Union for the attack.[101] 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.[102] 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."[103]

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.[104] 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;[105] the fate of KAL 007 was known inside this timeframe.[104]

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.[106]

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.[34][107] 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.[108]

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."[109] 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.[110] 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 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.[7] Also handed over at the same time were tapes of the ground to air communications of the Soviet military.[111] 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.[111]

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

Soviet memoranda

File:Ship 1.jpg
The 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 5] 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),[112] 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.[113][114]

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"[115]

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 was very problematical to retrieve anything, especially as the U.S.S.R. was not particularly interested".[116]

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.[117] 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.[118] The ICAO report continued to support the initial assertion that KAL 007 accidentally flew in Soviet airspace,[97] 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 1/2 NM 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",[119] 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 Maj. Osipovich in his Sukhoi 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.[120]

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.[120]

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."[42]

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 Script error: No such module "convert". behind the tail caused punctures to the pressurized passenger cabin.[54] 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."[121]

Two expert witnesses testified at a Court of Appeals trial on 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."[122]

Alternative theories

Flight 007 has been the subject of ongoing controversy and has spawned a number of conspiracy theories.[123] Many of these are based on the suppression of evidence such as the flight data recorders,[112] unexplained details such as the role of a USAF RC-135 surveillance aircraft,[30][124] or merely Cold War disinformation and propaganda.[125][126][127]


File:KAL Monument.jpg
"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.[128] 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.[129][130]

NATO had decided, under the impetus of the Reagan administration, to deploy Pershing II and cruise missiles in West Germany.[131] 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.[132]

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: " 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."[133] Changes that the Soviets subsequently made to their codes and frequencies reduced the effectiveness of this monitoring by 60%.[134]

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.[110] 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 Script error: No such module "convert". out from Anchorage.[note 8] 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.[135]

President Ronald 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 future.[136][137] 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.[8]

Alvin Snyder, the director of worldwide television for the United States Information Agency,[138] was the producer of the video shown to the U.N. Security Council on September 6, 1983.[139] 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.[139] 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"[139] and that "Osipovich (the Soviet fighter pilot) could not identify the plane"[139] and "That he fired warning cannon shots and tipped his wings, an international signal to force the plane to land".[139] Some of these statements were contradicted by the pilot in an interview with The New York Times,[36] in which he confirmed that he did fire warning shots, but that they would not have been visible as they were not tracers.[140]

In a March 15, 2001 interview, Valery Kamensky, then Commander of the Soviet Far East Military District Air Defense Force and direct superior to Gen. 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.”[141]

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."[142]

Popular culture

  • Two television movies were produced about the incident; both films were produced before the fall of the Soviet Union allowed access to archives:
    • Shootdown (1988), starring Angela Lansbury, John Cullum, and Kyle Secor, was based on the book of the same title by R.W. Johnson, about the efforts of Nan Moore (Lansbury), the mother of a passenger, to get answers from the US and Soviet governments.
    • The British Granada Television documentary drama Coded Hostile, screened on September 7, 1989, detailed the US military and governmental investigation, highlighting the likely confusion of Flight 007 with the USAF RC-135 in the context of routine US SIGINT/COMINT missions in the area. Written by Brian Phelan and directed by David Darlow, it starred Michael Murphy, Michael Moriarty, and Chris Sarandon. It was screened by HBO in the United States under the title Tailspin – Behind the Korean Airliner Tragedy on August 20, 1989. An updated version of Coded Hostile was screened in the UK on August 31, 1993, incorporating details of the 1992 UN investigation.
  • Lee Greenwood has stated that he wrote the song "God Bless the USA" in response to his feelings about the shooting down of Korean Air Lines Flight 007. "The song just about wrote itself," Greenwood said in the book God Bless the USA (by Greenwood and Gwen McLin). "The words seemed to flow naturally from the music, and came out with total honesty. They were an expression of my feelings of pride. To me, America seemed just like a rookery, a place where we have a chance to grow, unmolested and free."[143]
  • KGO-TV in San Francisco aired an advertisement in November 1983 for an upcoming news special report titled "Green Street Reds", about suspicious activities at the Soviet Consulate. In the ad, they depict Santa Claus and all his reindeer being blown out of the sky by a Soviet missile. The advertisement was produced by Davis, Johnson, Mogul & Colombatto. Angry parents complained to KGO about the poor impression the image of Santa's death made upon young children.[144]
  • Sri Lankan singer Anton Jones' Sinhala language song, "Koriyan Guwan Yanaya" ("Korean Airplane") tells the story of the incident


Lua error in Module:Location_map at line 371: attempt to index field 'ParserFunctions' (a nil value).
Crash site in Sakhalin Oblast

See also

Lua error in package.lua at line 80: module 'Module:Portal/images/u' not found.


  1. ^ a b 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. ^ This omission of the identity of KAL 007 as a Boeing by Osipovich is evident in the communications subsequently released by the Russian Federation with the combat controller, Captain Titovnin (see Flight timeline and transcripts).
  4. ^ "The last plotted radar position of the target was 18:35 hours at 5,000 meters." (ICAO '93, p. 53, para. 2.15.8)
  5. ^ These memos were published in the Soviet news magazine, Izvestia #228, October 16, 1992, shortly after being made public by Yeltsin.
  6. ^ "Photo of Chebrikov". Retrieved 5 April 2010. 
  7. ^ For illustration only—KAL 007 did not necessarily use this type of recorder.
  8. ^ These radars had been used in 1968 to alert Seaboard World Airlines Flight 253 in a similar situation.


  1. ^ Aviation Safety Database
  2. ^ Young & Launer, pp. xiii,47
  3. ^ a b c d Sputnik, The Truth and Lies about the South Korean Airliner
  4. ^ Pearson, p. 145
  5. ^ a b Congressional Record, September 20, 1983, pp. S12462-S12464
  6. ^ Soviet news magazine, Izvestia #228, October 16, 1992
  7. ^ a b "KAL Tapes To Be Handed Over To ICAO" (PDF) (Press release). International Civil Aviation Organization. January 1993. Retrieved 31 January 2009. 
  8. ^ a b c d e f g Degani, 2001
  9. ^ a b ICAO, 1993, p15, Section 2.8.1
  10. ^ Kilroy
  11. ^ Johnson, p. 6
  12. ^ Doerner, p. 5
  13. ^ Allardyce and Gollin, August 2007, pg51
  14. ^ Doerner, pg4
  15. ^ "Soviets Say Nixon Had Been Booked on Flight 007". Washington Post. 25 September 1983. Retrieved 3 July 2013. 
  16. ^ "Statement by Walter F. Luffsey, Associate Administrator for Aviation Standards, Before the House Committee on Science and Technology, Subcommittee on Transportation, Aviation and Weather Concerning Navigation Systems" (PDF). 19 September 1983. Retrieved 11 February 2009. 
  17. ^ ICAO 1983, appendix C, p. 2.
  18. ^ a b "KAL autopilot modes" (PDF). 
  19. ^ Rosenthal, pg70
  20. ^ Daniloff, p. 304
  21. ^ Milde, p53
  22. ^ a b c d Pearson (1987), pg40
  23. ^ a b 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 3 April 1991). Text
  24. ^ Kleiner, Korea, a Century of Change
  25. ^ Johnson, p. 16
  26. ^ Johnson, p. 55
  27. ^ a b Richelson, p. 385
  28. ^ Pry, p. 20
  29. ^ a b c Fischer, A Cold War Conundrum: The 1983 Soviet War Scare
  30. ^ a b Schultz, p. 367
  31. ^ CBS' "60 Minutes" interview, January 3, 1983
  32. ^ "Kamenski Interview". Rescue 007. Retrieved 5 April 2010. 
  33. ^ "Jean Kirkpatrick's Address to the United Nations". New York Times. September 7, 2983. p. 15.  Check date values in: |date= (help);
  34. ^ a b c d e f g Illesh, The Mystery of the KAL-007
  35. ^ a b Maier, KAL 007 Mystery
  36. ^ a b c d Gordon, Ex-Soviet Pilot Still Insists KAL 007 Was Spying
  37. ^ Izvestia, 1991.
  38. ^ Izvestia 1991 interview with Gennadi Osipovich, as quoted in: Daniloff, Nicholas (2008). "The KAL Shootdown". Of Spies and Spokesmen: My Life as a Cold War Correspondent (reprint, illustrated ed.). University of Missouri Press. p. 301. ISBN 978-0-8262-1793-6. Retrieved 5 August 2009. 
  39. ^ Osipovich, Gennady (9 September 1996), "Interview", The New York Times .
  40. ^ Information paper (1), ICAo, 1993, p. 190 .
  41. ^ Information Paper (1), ICAO, 1993, pp. 60, 61 .
  42. ^ a b c d ICAO '93, p. 55
  43. ^ a b c ICAO '93, p. 54
  44. ^ ICAO'93, Information Paper No. 1. p. 132,
  45. ^ ICAO '93, sect. 3.38, p. 61
  46. ^ Johnson, p. 30
  47. ^ Oberg, KAL 007: The Real Story
  48. ^ KAL 007:Cover-Up, David Pearson, Summit Press, N.Y., 1987,pg.122
  49. ^ ICAO, '93, 1.2.1, pg. 5
  50. ^ Daniloff, p. 300
  51. ^ Norris and Wagner, Boeing
  52. ^ ICAO '93, p39
  53. ^ "CVR transcript Korean Air Flight 007 – 31 AUG 1983". Aviation Safety Network. October 16, 2004. Retrieved 22 January 2009. 
  54. ^ a b c ICAO '93, Information Paper 1, p. 93
  55. ^ Uriel Rosenthal, Michael T. Charles, Paul 't Hart (1989). Coping with Crises: The Management of Disasters, Riots, and Terrorism. C.C. Thomas. ISBN 0-398-05597-1. Retrieved 11 February 2009. 
  56. ^ "ICAO Council Examines Follow-Up of Korean Air Lines Incident" (PDF) (Press release). International Civil Aviation Organization. October 1983. Retrieved 31 January 2009. 
  57. ^ a b Isaacson et al., 1983
  58. ^ a b c d e f Oberdorfer, p. 51
  59. ^ Marshal Nikolai Ogarkov (9 September 1983). Press conference (Speech). Moscow. 
  60. ^ ICAO, '93, Information Paper No. 1., pp. 95–96
  61. ^ Shootdown, R.W. Johnson, Viking, New York, 1985, pg 194
  62. ^ Shootdown, R.W. Johnson, Viking, N.Y. 1985,pg.194
  63. ^ a b ICAO '93, pg. 17. sect. 1.11.7
  64. ^ After Action Report (Department of the Navy, Commander, Surface Combat Force Seventh Fleet. CTF75/N32:kpm,4730,Ser 011, 15 November 1983
  65. ^ "USS Sterett Association". September 1, 1983. Retrieved 5 April 2010. 
  66. ^ Winkler, p. 47
  67. ^ 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, 15 November 1983)
  68. ^ ICAO Report, p. 28
  69. ^ After Action Report (Department of the Navy, Commander, Surface Combat Force Seventh Fleet. CTF75/N32:kpm,4730,Ser 011, 15 November 1983)
  70. ^ KAL 007: The Cover-up, David Pearce, Summit Books, N.Y., 1987, pg. 250
  71. ^ Izvestia, February, 1991, pg. 7
  72. ^ a b Princeton Alumni Weekly, 15 December 1999
  73. ^ Brun, pp. 143–44.
  74. ^ Kantakov and Shevchenko, In situ observations of Tsushima and West Sakhalin currents near La Perouse (Soya) Strait
  75. ^ Photo Mary Jane Hendrie
  76. ^ Pearson, p. 235
  77. ^ Andrey Illesh (May 21, 1991). "?". Izvestia. p. 6. 
  78. ^ World Wide Issues: 21. February 6, 1991.  Missing or empty |title= (help)
  79. ^ Izvestia, 28 May 1991, p. 8
  80. ^ ICAO '93, Sect. 1.12.4
  81. ^ Johnson, pp. 117–21
  82. ^ Johnson, RW, Shootdown: The verdict on KAL 007 .
  83. ^ a b Daniloff, p. 294
  84. ^ Dallin, p. 89
  85. ^ a b c Pry, pp. 27–32
  86. ^ Reagan, Ronald (September 5, 1983). "Address to the Nation on the Soviet Attack on a Korean Civilian Airliner" (Press release). U Texas; United States Government. Retrieved 12 January 2009. 
  87. ^ Ball, pp. 42–46
  88. ^ The Current Digest of the Soviet Press.
  89. ^ Reagan, Ronald (September 17, 1983). "Radio Address to the Nation on the Soviet Attack on a Korean Civilian Airliner" (Press release). U Texas; United States Government. Retrieved 11 January 2009. 
  90. ^ Luck, Mixed Messages: American Politics and International Organization, 1919–1999, p. 64
  91. ^ Johnson, p. 110
  92. ^ Pearson, p. 127
  93. ^ Johnson, p. 227
  94. ^ "ISASI—Air Safety Through Accident Investigation". January 1, 2004. Retrieved August 15, 2012. 
  95. ^ Johnson, p. 231
  96. ^ Johnson, p. 232
  97. ^ a b "ICAO Completes Fact-Finding Investigation" (Press release). Montreal. June 16, 1993. Retrieved 16 January 2009. 
  98. ^ Appendix F, ICAO 83
  99. ^ Izvestia #228, October 16, 1992
  100. ^ 7 May 1991, p. 6
  101. ^ Merrills, p. 61
  102. ^ "Infractions of the Convention On International Civil Aviation". Montreal: International Civil Aviation Organization. March 5, 1999. Retrieved 6 January 2009. [dead link]
  103. ^ "A Review of United States Assistance to Peruvian Counter-Drug Air Interdiction Efforts and the Shootdown of a Civilian Aircraft on April 20, 2001" (PDF). Select Committee on Intelligence. October 2001. Retrieved 14 February 2009. 
  104. ^ a b Pearson, p. 309
  105. ^ U.S. District Court, District of Columbia, In re: Korean Airlines disaster of September 1, 1983, February 28, 1985
  106. ^ The New York Times, January 7, 1991
  107. ^ Charles, p. 16
  108. ^ "Helms' letter to Yeltsin". October 25, 2008. Retrieved 5 April 2010. 
  109. ^ Wines, Michael (June 18, 1992). "Summit In Washington: Reporter's Notebook; The 'Burly' Yeltsin Acquires a New Kind of Stature: Major World Figure". New York Times. Retrieved 30 January 2009. 
  110. ^ a b Hoffman, Jan (March 31, 1997). "Grieving Father's 14-Year Crusade Helps Air Crash Victims". The New York Times. Retrieved 22 January 2009. 
  111. ^ a b Sayle, Murray (December 13, 1993). "Closing The File On Flight 007". The New Yorker. Retrieved 31 January 2009. 
  112. ^ a b Bohlen, Celestine (October 16, 1992). "Tape Displays the Anguish On Jet the Soviets Downed". New York Times. Retrieved 1 February 2009. 
  113. ^ Daniloff, p. 303
  114. ^ Andrew, p. 60
  115. ^ 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
  116. ^ Mikhail Prozumentshchikov (September 1, 2003). "Commentary: 20th Anniversary of Flight 007". RIA Novosti via Retrieved 13 January 2009. 
  117. ^ Ross, East Asia in Transition: Toward a New Regional Order
  118. ^ "KAL Tapes to be Handed Over to ICAO" (PDF) (Press release). Montreal. January 1993. Retrieved 14 January 2009. 
  119. ^ "ICAO Completes Fact-Finding Investigation" (PDF) (Press release). Montreal: International Civil Aviation Organization. 1993. Retrieved 6 January 2009. 
  120. ^ a b ICAO '93, Information Paper No. 1, pp. 48–208
  121. ^ ICAO '93, p. 35
  122. ^ 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
  123. ^ Knight, p. 381
  124. ^ Johnson, p. 175
  125. ^ Pry, p. 31
  126. ^ Pearson, p. 17
  127. ^ Young, p. 137
  128. ^ "FAA Suspends Use of Route Korean Airliner Had Been Assigned". The Washington Post. September 3, 1983. p. A22. 
  129. ^ "Air France Plane Follows KAL 007 Flight Path". Associated Press. October 4, 1983. 
  130. ^ Pearson, p. 256
  131. ^ Blacker, p. 308
  132. ^ Johnson, p. 75
  133. ^ "Speech to the National Military Intelligence Association". Aerospace Daily: 99. September 25, 1983. 
  134. ^ Baltimore Sun, September 15, 1983  Missing or empty |title= (help) via Johnson, p. 60
  135. ^ Taubman, Keeping the Air Lanes Free: Lessons of a Horror.
  136. ^ Pace (1995). "GPS History, Chronology, and Budgets". The Global Positioning System (PDF). et al. Rand. p. 248. ISBN 0-8330-2349-7. 
  137. ^ Pellerin, United States Updates Global Positioning System Technology: New GPS satellite ushers in a range of future improvements.
  138. ^ "U.S. Foreign Affairs in the New Information Age". Northwestern. Retrieved 5 April 2010. 
  139. ^ a b c d e "Flight 007: The rest of the story", Washington Post, September 1, 1996.
  140. ^ Discovery Channel, episode "Unsolved History, KAL 007"
  141. ^ Fakty i Kommentarii, 15 March 2001
  142. ^ "James Oberg's Pioneering Space". Retrieved August 15, 2012. 
  143. ^ Campbell, Ramsey (23 May 1993). "Lake Woman Co-Authors Story Behind "God Bless the U.S.A."". Retrieved 14 July 2010. 
  144. ^ "Angry Reaction to Santa Ad". Argus-Press (Owosso, Michigan). Associated Press. 16 November 1983. Retrieved 28 November 2013. 




Online sources

Further reading

External links

External images
16px Pre-shootdown photos of the aircraft,

Unknown extension tag "indicator"