Jump to content

Korean Air Lines Flight 007

From Alfawiki
Korean Air Lines Flight 007
Company typeCommercial airline flight
IndustryAviation
Founded1983-08-31 (date of flight)
Headquarters
Seoul
,
South Korea
ProductsPassenger air transport

Korean Air Lines Flight 007 Incident

Korean Air Lines Flight 007 (designated as KE007 by IATA and KAL007 by ICAO)[note 1] was a regularly scheduled route operated by Korean Air Lines, connecting New York City to Seoul with a stopover in Anchorage, Alaska. On September 1, 1983, this flight was intercepted and shot down by a Soviet Sukhoi Su-15TM Flagon-F interceptor. The Boeing 747-230B was flying from Anchorage to Seoul when a navigational error caused it to deviate into Soviet airspace. Mistaking the aircraft for an unauthorized U.S. reconnaissance plane, Soviet air defense forces launched air-to-air missiles after issuing warning shots. The plane crashed into the Sea of Japan near Moneron Island, located west of Sakhalin, resulting in the deaths of all 269 individuals on board, including 246 passengers and 23 crew members. Among the victims was U.S. Representative Larry McDonald. This tragedy remains the deadliest accident in Korean Air's history.

Initially, the Soviet government denied any involvement,[1] but subsequently acknowledged downing the aircraft, asserting it was engaged in a MASINT espionage mission.[2] The Soviet Communist Party's Politburo characterized the event as a deliberate U.S. provocation aimed at testing Soviet military readiness or inciting conflict.[3] The United States criticized the Soviet Union for hindering search and rescue efforts.[4] Furthermore, the Soviet Armed Forces withheld crucial evidence requested by the International Civil Aviation Organization (ICAO), including the flight data and cockpit voice recorders,[5] which were only released in 1992 after the dissolution of the USSR.[6]

Following this incident, U.S. aviation authorities revised aircraft monitoring protocols for flights departing Alaska. Additionally, President Ronald Reagan announced that once fully developed, satellite-based navigation via the Global Positioning System would be made freely accessible for civilian use worldwide as a public resource.[7]

Aircraft

The plane operating as Korean Air Lines Flight 007 was a Boeing 747-230B model, bearing Boeing serial number 20559. It was equipped with four Pratt & Whitney JT9D-7A engines. Initially delivered new to Condor in 1972 under the registration D-ABYH, the aircraft was acquired by Korean Air Lines in 1979, re-registered as HL7442, and was 11.5 years old at the time of the accident. This particular aircraft was the 186th Boeing 747 produced.

Passengers and crew

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

* Includes 76 passengers, 23 active crew members, and 6 deadheading crew[8][9]

File:Larry McDonald.jpg
Congressman Larry McDonald

Korean Air Lines Flight 007 took off from Gate 15 at John F. Kennedy International Airport, New York City, on August 31, 1983, at 00:25 EDT (04:25 UTC), departing approximately 35 minutes later than its scheduled time of 23:50 EDT on August 30 (03:50 UTC, August 31). The flight carried a total of 246 passengers alongside 23 crew members. Following a refueling stop at Ted Stevens Anchorage International Airport in Anchorage, Alaska, the aircraft resumed its journey to Seoul at 04:00 AHDT (13:00 UTC) on August 31, 1983. The cockpit team consisted of Captain Chun Byung-in (45 years old), First Officer Son Dong-hui (47), and Flight Engineer Kim Eui-dong (31). Captain Chun had accumulated 10,627 flight hours, including 6,618 on the Boeing 747; First Officer Son had logged a total of 8,917 hours with 3,411 on the same aircraft model; Flight Engineer Kim had flown for a total of 4,012 hours, with 2,614 hours on the Boeing 747.

This particular flight exhibited a notably high crew-to-passenger ratio due to the presence of six deadheading crew members. Twelve passengers were seated in the upper deck first-class section; business class was nearly full with nearly all of its approximately 24 seats occupied; meanwhile, economy class had roughly eighty vacant seats. Among those aboard were twenty-two children under twelve years old. About one hundred thirty passengers intended to connect to onward flights destined for cities such as Tokyo, Hong Kong, and Taipei.

Onboard was Congressman Larry McDonald from Georgia, who also served as the second president of the conservative John Birch Society. Soviet authorities claimed that former U.S. president Richard Nixon had been scheduled to sit next to McDonald on this flight but reportedly declined after receiving a CIA warning; this assertion appeared in reports from the New York Post and the Soviet news agency TASS. According to Franklin R. Gannon, a former aide to Nixon, although Nixon was offered a seat on Flight 007, he personally chose not to travel.

Deviation from Assigned Flight Path

Shortly after departing Anchorage, less than thirty seconds into the flight, KAL 007 received instructions from air traffic control (ATC) to adjust its magnetic heading to 220°.[8]: 31  This significant left turn of 100° served to shift the aircraft from its initial takeoff heading of 320° magnetic, aligned with the runway,[8]: 41  directing it closer to airway J501, which was the planned route toward Bethel. About a minute and a half later, ATC cleared the flight to "proceed direct Bethel when able."[10][11] The crew responded by initiating a subtle right turn to align with J501, achieving an approximate magnetic heading of 245° roughly three minutes after liftoff,[8]: 31  steering generally toward Bethel.

Upon reaching Bethel, the flight plan required KAL 007 to join the northernmost airway among five 50-mile-wide (80 km) routes known as the NOPAC (North Pacific) airways, which connect Alaska and Japan. The designated airway, R20 (Romeo Two Zero), skirts within 20 miles (32 km) of Soviet airspace near the Kamchatka Peninsula coast.

The Boeing 747-200’s autopilot lateral navigation system features four principal control modes: HEADING, VOR/LOC, ILS, and INS. HEADING mode maintains a fixed magnetic course set by the pilot. VOR/LOC mode keeps the aircraft on a specific course based on signals from ground-based VOR or Localizer beacons selected by the pilot. ILS mode guides the plane along both vertical and lateral course beams toward a runway designated by the pilot. INS mode enables automatic tracking between programmed waypoints loaded into the inertial navigation computer.

When flight plan waypoints are correctly entered into the INS system, switching the autopilot mode selector to INS causes the aircraft to automatically follow the programmed course line—provided it is oriented in the correct direction and remains within 7.5 nautical miles (13.9 km) of that course.[8]: 42  If the plane is farther than 7.5 nautical miles (13.9 km) from its planned route when changing from HEADING to INS mode, it will continue following the previously selected heading until it comes within that distance threshold. The autopilot software keeps INS mode in an "armed" state until proximity reaches less than 7.5 nautical miles (13.9 km), at which point it switches to "capture" and begins tracking the programmed course line.[12][8]: 42 

Typically, after takeoff, pilots engage HEADING mode to comply with ATC vectors and then switch to INS mode once cleared to intercept their intended navigation path.[12]

At departure time, Anchorage’s VOR beacon was offline due to maintenance.[13] The flight crew was informed via a NOTAM (Notice to Airmen), but this was not considered problematic since position verification could be performed at Bethel’s VORTAC beacon located 346 nautical miles (641 km) away. The aircraft was instructed to maintain 220° heading until receiving signals from Bethel; thereafter it could proceed directly by centering the VOR "to" course deviation indicator (CDI) and engaging autopilot in VOR/LOC mode. Upon passing Bethel, switching to INS mode would allow following route Romeo-20 around Soviet coastal areas en route to Seoul. Due to limited VOR coverage beyond Bethel, INS navigation was essential for this segment.

File:KAL007.svg
Simplified CIA map illustrating divergence between planned and actual flight paths

Approximately ten minutes post-takeoff, while maintaining a heading of 245°, KAL 007 began veering northward off its assigned track toward Bethel and maintained this altered heading for over five hours.[14]

Simulations conducted by the International Civil Aviation Organization (ICAO) using flight data recorder analysis concluded that this deviation likely resulted from continued operation of autopilot in HEADING mode beyond when it should have been switched to INS.[15][16] ICAO suggested two possible causes: either the crew failed to switch autopilot to INS after passing near Cairn Mountain, or they did select INS but the system remained in "armed" state without transitioning to "capture" because the aircraft was already more than 7.5 nautical miles (13.9 km) off course—the maximum tolerance for automatic capture by INS. Regardless of cause, autopilot stayed in HEADING mode unnoticed by pilots.[15]

At 27 minutes after departure, civilian radar based at Kenai, approximately 50 nautical miles (90 km) southwest of Anchorage with coverage extending up to 175 nautical miles (320 km),[8]: 10  tracked KAL 007 near Cairn Mountain about 160 nautical miles (300 km) west of Anchorage,[8]: 15  already showing it roughly 6 nautical miles (11 km) north of its planned route toward Bethel.[8]: 4–5, 43 

At 13:49 UTC (49 minutes after takeoff), KAL 007 reported reaching its Bethel waypoint located approximately 346 nautical miles (641 km)* west of Anchorage.[8]: 5  However, military radar from King Salmon, Alaska indicated that at that time the aircraft was about 12 nautical miles (22 km)* north of Bethel,[8]: 5, 43  continuing further off its intended track.[8]: 44  There is no indication that controllers or military personnel monitoring King Salmon radar were aware in real-time of this deviation or able to notify KAL 007.[17] Had INS navigation been engaged as planned, such an error would have far exceeded its typical accuracy margin of less than 2 nautical miles (3.7 km)* per hour.[8]: 43 [18]

Because KAL 007 strayed from its assigned path, it lost reliable access to short-range very high frequency (VHF) radio communications and requested that KAL 015—also bound for Seoul—relay position reports on its behalf.[19]</ref> The crew made this relay request three times. At 14:43 UTC, KAL 007 directly communicated an updated estimated time of arrival for waypoint NEEVA via long-range high frequency (HF) radio through Anchorage's international flight service station,[20] rather than utilizing VHF. HF transmissions cover greater distances but are susceptible to static and interference; VHF offers clearer reception preferred by pilots. The inability to maintain direct VHF contact did not alert KAL 007’s crew about their increasing navigational error,[21] nor did air traffic controllers find this unusual.[19] Between Bethel and waypoint NABIE, KAL 007 passed through part of the North American Aerospace Defense Command buffer zone—a restricted area north of Romeo-20 off limits for civilian flights.

After leaving U.S. territorial waters, Flight KAL 007 crossed the International Date Line, advancing local date from August 31 to September 1, 1983.

The aircraft continued drifting progressively farther off course—approximately 60 nautical miles (110 km) beyond waypoint NABIE, 100 nautical miles (190 km) past NUKKS, and about 160 nautical miles (300 km) beyond NEEVA—until reaching proximity of the Kamchatka Peninsula.[8]: 13 

Template:GeoGroup

Route J501 / R20 Waypoint[8]: 13  Planned Coordinates ATC Position KAL 007 Deviation

|- CAIRN MOUNTAIN Lua error: callParserFunction: function "#coordinates" was not found. Anchorage 6 nmi (11 km) |} |- BETHEL Lua error: callParserFunction: function "#coordinates" was not found. Anchorage 12 nmi (22 km) |} |- NABIE Lua error: callParserFunction: function "#coordinates" was not found. Anchorage 60 nmi (110 km) |} |- NUKKS Lua error: callParserFunction: function "#coordinates" was not found. Anchorage 100 nmi (190 km) |} |- NEEVA Lua error: callParserFunction: function "#coordinates" was not found. Anchorage 160 nmi (300 km) |} |- NINNO Lua error: callParserFunction: function "#coordinates" was not found. Anchorage |} |- NIPPI Lua error: callParserFunction: function "#coordinates" was not found. Anchorage/Tokyo Area Control Center Template:Convert 180 mi km abbr=on |} |- NYTIM Template:Coord 46 11.9 N 153 00.5 E type:landmark name=KAL007 NYTIM Tokyo Template:Convert 500 nmi km abbr=on (to impact point) |} |- NOKKA Template:Coord 42 23.3 N 147 28.8 E type:landmark name=KAL007 NOKKA Tokyo Template:Convert 350 nmi km abbr=on (to impact point) |} |- NOHO Template:Coord 40 25.0 N 145 00.0 E type:landmark name=KAL007 NOHO Tokyo Template:Convert 390 nmi km abbr=on (to impact point) |} }

Shoot-down

File:Su-15 Flagon.jpg
A Soviet Sukhoi Su-15 interceptor

Template:Location map+ By 1983, the Cold War rivalry between the United States and the Soviet Union had reached a peak not witnessed since the Cuban Missile Crisis, driven by multiple developments. These included the U.S. Strategic Defense Initiative, plans to deploy Pershing II missiles in Europe during March and April, and FleetEx '83-1, which was the largest naval exercise conducted in the North Pacific up to that time. The Soviet military leadership—especially the entrenched faction led by General Secretary Yuri Andropov and Defence Minister Dmitry Ustinov—perceived these moves as aggressive and destabilizing. They harbored deep mistrust toward U.S. President Ronald Reagan’s motives and feared he might be preparing a pre-emptive nuclear strike against the USSR. This anxiety led to the initiation of RYAN, a covert intelligence program launched by Andropov aimed at detecting any surprise nuclear attack they suspected Reagan was orchestrating.

During FleetEx '83 (29 March to 17 April 1983), aircraft from USS Midway (CV-41) and USS Enterprise (CVN-65) repeatedly conducted overflights of Soviet military sites in the Kuril Islands, provoking disciplinary actions against Soviet officers who failed to intercept them. In response, the Soviets expanded the RYAN program. Concurrently, heightened alert levels were maintained around the Kamchatka Peninsula due to a scheduled missile test at the Kura Missile Test Range on the same day KAL 007 was nearby. A United States Air Force Boeing RC-135 reconnaissance plane was also monitoring this missile launch from the area.

According to Soviet accounts, at 15:51 UTC, KAL 007 penetrated restricted airspace surrounding Kamchatka Peninsula—a buffer zone extending approximately 200 kilometers from the coast designated as a flight information region (FIR). Within this zone, a smaller 100-kilometer radius closest to Soviet territory was classified as prohibited airspace. When KAL 007 approached roughly 130 kilometers from Kamchatka’s shore, four MiG-23 fighters were scrambled to intercept the Boeing 747.

The Soviet forces encountered considerable difficulties in directing their high-speed interceptors toward KAL 007 before fuel constraints became critical. Additionally, as recounted by Soviet Air Force Captain Aleksandr Zuyev—who defected to the West in 1989—the pursuit was complicated because key radar facilities on Kamchatka had been disabled by Arctic storms ten days earlier. Local officials falsely reported successful repairs to Moscow when in fact the radar remained inoperative. Had this radar been functional, it would have allowed interception of the civilian aircraft approximately two hours earlier, providing ample opportunity for proper identification. Instead, KAL 007 traversed Kamchatka Peninsula and re-entered international airspace over the Sea of Okhotsk without interception. Zuyev later explained on 60 Minutes: "Some people lied to Moscow, trying to save their ass."

General Valeri Kamensky, commander of the Soviet Far East District Air Defense Forces, insisted that KAL 007 should be destroyed even if it was over neutral waters—but only after confirming it was not a civilian aircraft. However, his subordinate General Anatoly Kornukov—commander of Dolinsk-Sokol Air Base and future head of the Russian Air Force—argued that positive identification was unnecessary since the intruding plane had already crossed Kamchatka.

Template:Poemquote

After tracking KAL 007 for more than an hour as it entered and exited Soviet airspace, Soviet Air Defence Forces classified it as a hostile target upon its second incursion over Sakhalin Island airspace. Following an extended ground-controlled interception effort, three Su-15 fighters from Dolinsk-Sokol airbase along with a MiG-23 from Smirnykh Air Base made visual contact with KAL 007. Due to darkness, they failed to definitively identify it as a civilian aircraft—a fact revealed in Russian communication transcripts. The lead Su-15 pilot fired warning shots using his cannon—reporting later that he discharged four bursts totaling over 200 rounds loaded with armor-piercing ammunition rather than incendiaries—which likely went unnoticed.

At this juncture, KAL 007 contacted Tokyo Area Control Center requesting permission to climb to a higher flight level for fuel efficiency reasons; clearance was granted and the aircraft began ascending while reducing speed accordingly. The slower pace caused pursuing fighters to overshoot KAL 007—a maneuver misinterpreted by Soviet pilots as evasive action. The command to engage and shoot down KAL 007 was issued just before it exited Soviet airspace for a second time. Around 18:26 UTC, under pressure from General Kornukov and ground controllers determined not to allow escape into international airspace, the lead interceptor positioned itself for missile engagement and launched two K-8 (NATO reporting name: AA-3 "Anab") air-to-air missiles at the Boeing 747.

Recollection of the Shoot-Down by Soviet Pilot

In a 1991 discussion with Izvestia, Major Gennadiy Osipovich, the Su-15 interceptor pilot responsible for downing the aircraft, shared his memories of the incident. Contrary to the Soviet official narrative at the time, he recalled informing ground control about "blinking lights".[22] He further described the 747-230B, stating, "I observed two rows of windows and recognized it as a Boeing. I was aware it was a civilian aircraft. However, this held no significance for me. Converting a civilian plane into a military one is straightforward."[22] Osipovich added, "I did not report to ground control that it was a Boeing model; they never inquired."[23][22]

File:Sukhoi SU-15TM 2008 G2.jpg
K-8 missile (the missile type used against KAL 007) attached to the wing of a Sukhoi Su-15

Reflecting on the moment when KAL 007 reduced its speed while climbing from flight level 330 to flight level 350, and on his preparations for missile deployment, Osipovich remarked:

Template:Blockquote

Osipovich passed away on September 23, 2015, following a prolonged illness.[24]

Soviet command structure during the shoot-down

The transcripts of Soviet military communications in real time during the shoot-down reveal the command chain extending from the highest-ranking general down to Major Osipovich, the Su-15 pilot responsible for intercepting KAL 007.[25][26] The hierarchy, listed from bottom to top, is as follows:

  • Major Gennadiy Nikolayevich Osipovich,
  • Captain Titovnin, Combat Control Center – Fighter Division
  • Lt. Colonel Maistrenko, Acting Chief of Staff of Smirnykh Air Base Fighter Division, who confirmed the shoot-down directive to Titovnin.Template:Blockquote
  • Lt. Colonel Gerasimenko, Acting Commander of the 41st Fighter Regiment.Template:Blockquote
  • General Anatoly Kornukov, Commander at Sokol Air Base – Sakhalin.Template:Blockquote
  • General Valery Kamensky, Commander of the Far East Military District Air Defense Forces.Template:Blockquote
  • Army General Ivan Moiseevich Tretyak, Commander of the Far East Military District.Template:Blockquote

Flight after missile impact

At the moment of engagement, KAL 007 was maintaining a cruising altitude near 35,000 feet (11,000 m). Cockpit voice recorder tapes recovered show that the crew did not realize they had deviated from their planned route nor that they were infringing upon Soviet airspace.[27] Following missile detonation, the aircraft entered a 113-second upward arc caused by damage to a crossover cable linking the left inboard and right outboard elevators.

At 18:26:46 UTC (03:26 Japan Time; 06:26 Sakhalin time),[28] at the apex of this arc reaching approximately 38,250 feet (11,660 m),[27] autopilot was disengaged—either manually by pilots or automatically—after which manual control was assumed and the plane began descending back toward 35,000 feet (11,000 m). Between 18:27:01 and 18:27:09, the crew communicated with Tokyo Area Control Center indicating an intention to descend to "10,000" feet [3,000 m]. At 18:27:20, analysis of Digital Flight Data Recorder information by ICAO revealed that after a descent phase and a brief nose-up maneuver lasting about ten seconds, KAL 007 stabilized at its original altitude of 35,000 feet (11,000 m), with forward acceleration returning to zero and airspeed normalizing to pre-detonation levels.

Yaw oscillations initiated at missile impact gradually diminished over a one-minute and forty-four-second period recorded on tape. Contrary to immediate catastrophic failure assumptions, the Boeing did not disintegrate or crash instantly but continued a slow descent for approximately four minutes before leveling off at around 16,424 feet (5,006 m) (between 18:30 and 18:31 UTC), rather than descending further to the previously reported altitude of 10,000 feet (3,000 m) as communicated to Tokyo Area Control Center. The aircraft maintained this altitude for nearly five additional minutes until about 18:35 UTC.

The final cockpit voice recorder entry occurred at 18:27:46 during this descent phase. By 18:28 UTC, reports indicated the aircraft was turning northward.[29] ICAO's evaluation concluded that limited flight control was retained by the crew,[30] but this control lasted only about five minutes before being lost entirely. Subsequently, the plane entered a rapid spiral descent over Moneron Island spanning approximately 2.6 miles (4.2 km), broke apart mid-air and crashed into waters off Sakhalin Island’s west coast. All 269 occupants perished.[note 2] Osipovich visually observed the aircraft descending slowly over Moneron Island before it disappeared from long-range military radar near Wakkanai, Japan at about 1,000 feet (300 m) elevation.[31]

KAL 007 was likely engaged in international airspace; a Russian report from 1993 places the missile launch coordinates outside Soviet territory at Lua error: callParserFunction: function "#coordinates" was not found.,[32][33] although subsequent interviews with the intercepting pilot presented differing accounts regarding location. Early assertions that KAL 007 had been compelled to land on Sakhalin were later disprovedTemplate:Fix/category[citation needed]. One such claim relayed via telephone by Orville Brockman—the FAA’s Washington office spokesperson—to Larry McDonald’s press secretary stated that FAA officials in Tokyo had been informed by Japan’s Civil Aviation Bureau that "Japanese self-defense force radar tracked Air Korea landing within Soviet territory on Sakhalin Island and manifest confirmed Congressman McDonald aboard."[34]

A Japanese fisherman aboard 58th Chidori Maru reported to Japan’s Maritime Safety Agency (cited in ICAO analysis) hearing an aircraft flying low without visual confirmation; subsequently he perceived “a loud noise followed by a bright flash on the horizon,” then “another muffled sound accompanied by a less intense flash”[35] along with an odor resembling aviation fuel.[36]

Soviet command reaction to post-detonation flight

Despite the interceptor pilot's report to ground control stating "Target destroyed," Soviet command, including senior officers, expressed surprise and concern over KAL 007's continued flight, its ability to regain altitude, and maintain control. This apprehension persisted throughout KAL 007's subsequent steady flight at an altitude of 16,424 ft (5,006 m), and extended for nearly five minutes during its spiral descent near Moneron Island.

Missile impact on aircraft

Based on the ICAO's examination of the flight data recorder and cockpit voice recorder, the following damage to the aircraft was identified:

Hydraulic systems

KAL 007 was equipped with four redundant hydraulic systems. Systems one, two, and three sustained damage or were destroyed, while system four remained unaffected.[28] These hydraulics controlled all primary and secondary flight surfaces (excluding leading edge slats), as well as landing gear operations including retraction, extension, steering, and braking. Power for each primary flight control axis was supplied by all four hydraulic systems.[37] Following missile detonation, the aircraft experienced yaw oscillations due to impairment of the dual channel yaw damper. Such yawing would not have occurred if hydraulic systems one or two were fully functional. Consequently, the control column did not move forward post-detonation (which it should have under autopilot) to lower the plane back to its prior altitude of 35,000 feet (11,000 m). This lack of autopilot correction suggests that hydraulic system three, responsible for the autopilot actuator controlling the elevators, was compromised. As KAL 007 climbed, both airspeed and acceleration began to decline. Approximately twenty seconds after detonation, a click was audible in the cabin—the "automatic pilot disconnect warning." Either pilot manually disengaged the autopilot and attempted to push the control column forward to descend. Although autopilot was switched off, manual control did not activate until twenty seconds later, indicating failure in hydraulic systems one and two. With wing flaps retracted, control authority was limited to the right inboard aileron and the innermost spoiler sections on both wings.[28]

Left wing

Contrary to Major Osipovich's 1991 claim that half of KAL 007's left wing had been severed,[23] ICAO findings determined the wing remained intact: "The interceptor pilot reported that the initial missile struck near the tail while a second missile removed half of the left wing... This assertion is likely incorrect. The missiles were launched two seconds apart and detonated accordingly. The first explosion occurred at 18:26:02 UTC. The final radio communications from KE007 to Tokyo Radio took place between 18:26:57 and 18:27:15 UTC via HF [high frequency]. The aircraft’s HF 1 radio antenna was located on the left wingtip, indicating that this portion of the wing was undamaged at that time. Additionally, subsequent maneuvers by the aircraft did not suggest significant damage to the left wing."[38]

Engines

During the flight, following the missile explosions, the co-pilot communicated twice with Captain Chun, confirming, "Engines operating normally, sir."

Tail section

The initial missile, guided by radar and equipped with a proximity fuze, detonated approximately 50 metres (160 ft) behind the aircraft. The explosion propelled fragments forward, which either cut or unraveled the crossover cable connecting the left inboard elevator to the right elevator. Alongside damage to one of the aircraft's four hydraulic systems, this caused KAL 007 to climb from 35,000 to 38,250 feet (10,670 to 11,660 m), prompting disengagement of the autopilot.

Fuselage

The proximity-fuzed air-to-air missile that exploded roughly 50 metres (160 ft) behind the plane released shrapnel that pierced the fuselage, resulting in rapid decompression of the pressurized cabin. Analysis by ICAO experts determined that the rupture area on the pressurized fuselage measured approximately 1.75 square feet (0.163 m2), based on the 11-second delay recorded between the missile detonation sound and the cockpit alarm activation captured by the cockpit voice recorder.

Search and rescue

Amid Cold War hostilities, Soviet search and rescue efforts were conducted independently from those of the United States, South Korea, and Japan. This lack of coordination meant no exchange of information occurred; instead, each side aimed to disrupt or gather evidence against the other. Both governments prioritized recovering the flight data recorders, with the United States demanding that an ICAO independent observer accompany one of its search vessels if these devices were located. The ambiguity of maritime boundaries in open waters led to frequent clashes among numerous opposing naval forces assembled in the vicinity.

Soviet search and rescue operation near Moneron Island

The Soviet authorities did not admit to shooting down the plane until September 6, which was five days following the incident.[39] Eight days post-incident, Marshal of the Soviet Union and Chief of General Staff Nikolai Ogarkov claimed ignorance regarding the exact crash location of KAL 007, stating, "We could not provide a precise location where [KAL 007] went down because we ourselves were unaware of it initially."[40]

Nearly a decade later, the Russian Federation released transcripts of Soviet military communications revealing that at least two official search and rescue (SAR) missions were dispatched within thirty minutes of the attack. These missions targeted the last Soviet-confirmed position of the descending aircraft near Moneron Island. The initial search was launched from Smirnykh Air Base in central Sakhalin at 18:47 UTC, just nine minutes after KAL 007 vanished from Soviet radar. This operation deployed rescue helicopters from Khomutovo Air Base (the military unit based at Yuzhno-Sakhalinsk Airport in southern Sakhalin) alongside Soviet Border Troops vessels to the vicinity.[41]

A subsequent search order came eight minutes later from General Strogov, Deputy Commander of the Far Eastern Military District, which involved civilian trawlers operating near Moneron. His directive was clear: "The border guards. What ships do we currently have close to Moneron Island? If they are civilian, dispatch them there immediately."[42] Moneron Island measures approximately 4.5 miles (7.2 km) in length and 3.5 miles (5.6 km) in width, situated 24 miles (39 km) directly west of Sakhalin Island at Lua error: callParserFunction: function "#coordinates" was not found.; it is the sole landmass within the entire Tatar Strait.

Search efforts for KAL 007 in international waters

File:USNS Narragansett (T-ATF 167) deploys Deep Drone RSV.jpg
Deployment of the submersible Deep Drone from USNS Narragansett (T-ATF 167).

Immediately following the downing, South Korea—being the aircraft's owner and thus holding primary jurisdiction—appointed the United States and Japan as responsible for search and salvage activities. This designation effectively prohibited Soviet salvage operations outside their territorial waters. Should the Soviets have attempted salvage beyond their jurisdiction, U.S. forces would have been legally justified to use force to prevent recovery of any aircraft components.[43]

On the day of the incident, Rear Admiral William A. Cockell, Commander of Task Force 71, along with a minimal staff transported by helicopter from Japan, boarded USS Badger (then positioned near Vladivostok)[43] on September 9. He later transferred to destroyer USS Elliot to assume command as Officer in Tactical Command (OTC) over Search and Rescue (SAR) operations. Surface search activities commenced immediately and continued through September 13; underwater searches began on September 14. By September 10, with no survivors located, Task Force 71’s mission shifted from "Search and Rescue" (SAR) to "Search and Salvage" (SAS).[44]

File:Odarennyy1983.jpg
The Soviet Kashin class destroyer Odarennyy shadows Task Force 71 ships conducting searches for Korean Airlines Flight 007 under the United States Seventh Fleet.

Rear Admiral Walter T. Piotti, Jr., assumed command of Task Force 71’s search and salvage operations from Rear Admiral Cockell on October 17. The initial focus was a 60-square-mile (160 km2) "high probability" zone but yielded no results. On October 21, Task Force 71 broadened its search area to encompass approximately 225 square miles (583 km2), forming an arc around Soviet territorial waters north of Moneron Island and extending westward toward Sakhalin Island—this constituted the "large probability" zone. These search zones were beyond the 12-nautical-mile (22 km) limit claimed by the Soviets as territorial waters. The northwestern boundary approached closest to Nevelsk naval port on Sakhalin, about 46 nautical miles (85 km) from Moneron Island; however, this extended search also failed to locate wreckage.[44]

Both sides employed a combination of civilian trawlers specially outfitted for SAR and SAS tasks alongside various warships and support vessels during their respective searches. The Soviets utilized both civilian and military divers in their efforts starting on the day of the shoot-down until November 6; their operations focused on the 60-square-mile (160 km2) "high probability" region in international waters as well as within Soviet territorial waters north of Moneron Island—the latter area being off-limits to U.S., South Korean, and Japanese vessels. Between September 3 and 29, four South Korean ships participated in these operations.

Rear Admiral Piotti Jr., leading Task Force 71 under the U.S. Seventh Fleet, summarized both Allied and Soviet search efforts:

Template:Blockquote

File:After Action Report Map.jpg
Map from U.S. Task Force 71 After Action Report depicting international waters search area

These operations encountered Soviet obstruction,[45] contravening provisions of the 1972 Incidents at Sea agreement. Interference included deceptive light signals resembling false flags; dispatching an armed boarding party threatening a U.S.-chartered Japanese auxiliary vessel (prevented by U.S warship intervention); obstructing a helicopter departing USS Elliot on September 7; attempted ramming against South Korean rig vessels during quadrant searches; hazardous maneuvers by Gavril Sarychev resulting in near collisions with USS Callaghan on September 15 and September 18; removal of U.S sonar equipment; deployment of counterfeit emergency pingers in deep international waters; deployment of nuclear-capable Tupolev Tu-22M Backfire bombers threatening U.S naval units; crossing paths dangerously close to U.S combatant ships on October 26; cutting moorings of Japanese auxiliary vessels like Kaiko Maru III; radar missile lock-ons by Soviet Kara-class cruiser Petropavlovsk and Kashin-class destroyer Odarennyy targeting U.S naval vessels including Coast Guard cutter Douglas Munro (WHEC-724), USS Towers (DDG-9), escorting USS Conserver (ARS-39), with near collisions involving Odarennyy between September 23–27.[46][47]

The ICAO reported: "The main wreckage location was not definitively identified... approximate position was Lua error: callParserFunction: function "#coordinates" was not found., situated in international waters." This site lies roughly 41 miles (66 km) from Moneron Island’s shore, about 45 miles (72 km) offshore from Sakhalin Island’s coast and approximately 33 miles (53 km) from where the attack occurred.[48]

Rear Admiral Piotti Jr., reflecting on Task Force 71’s international waters search for KAL 007 concluded:[49]

Had Task Force 71 been authorized to conduct unrestricted searches beyond claimed territorial limitations imposed by the Soviets, there was a strong likelihood that KAL 007 would have been located. No wreckage was found within these constraints; however, it is established with over a 95% confidence level that no significant debris lies within areas outside Soviet territorial claims extending twelve nautical miles.[50]

During an ICAO hearing on September 15, 1983, J. Lynn Helms—head of the Federal Aviation Administration—stated:[4] "The USSR denied access to foreign search and rescue teams within its territorial waters for recovery efforts related to KAL 007 remains. Furthermore, it obstructed entry to probable crash sites and declined cooperation with other involved parties aimed at expediting retrieval of technical equipment, wreckage pieces, and related materials."

Surface discoveries

The Soviet search team did not recover any human remains from the sea surface within their territorial waters; however, they later handed over clothing and footwear to a joint U.S.–Japanese delegation at Nevelsk on Sakhalin. On Monday, September 26, 1983, a group of seven officials from Japan and the United States, arriving aboard the Japanese patrol vessel Tsugaru, met with a six-member Soviet delegation at Nevelsk port on Sakhalin Island. Leading the Soviet side was KGB Major General A. I. Romanenko, who commanded the frontier guard for Sakhalin and the Kuril Islands. Romanenko presented various items to the U.S. and Japanese representatives, including single shoes and pairs of footwear. Alongside additional shoes recovered by the Japanese, the total count reached 213 pieces consisting of men's, women's, and children's dress shoes, sandals, and athletic shoes. The Soviets stated these were all the items they had retrieved either floating in the water or found along the shores of Sakhalin and Moneron islands.

Relatives of KAL 007 passengers later confirmed that these shoes belonged to their family members who had been on the flight. Sonia Munder easily identified her children's sneakers—Christian’s (14 years old) and Lisi’s (17 years old)—due to their distinctive lacing patterns. Another mother remarked, "I recognized them immediately. There are subtle marks unnoticed by others that only family members recognize. That’s how I knew. My daughter loved wearing those shoes."

Nan Oldham was able to identify her son John’s sneakers from a photograph published in Life magazine showing 55 out of the 213 shoes displayed during the initial days at Chitose Air Force Base in Japan. "We saw pictures of his shoes in a magazine," Oldham recalled, "We pursued it through KAL, and a few weeks later a package arrived containing his shoes: size 11 sneakers with cream white paint." John Oldham had boarded KAL 007 wearing those cream white paint-speckled sneakers.

The combined search and rescue/salvage missions conducted by U.S., Japanese, and South Korean teams in international waters at the designated crash site yielded no findings within the 225-square-nautical-mile (770 km2) search radius.

Findings on Hokkaido

Approximately eight days post-incident, human remains along with other debris washed ashore on Hokkaido's northern coast in Japan. Situated roughly 30 miles (48 km) south of Sakhalin’s southern tip across the La Pérouse Strait, Hokkaido lies near key currents influencing debris movement (the southern tip of Sakhalin is about 35 miles (56 km) from Moneron Island, located west of Sakhalin). The ICAO determined that these bodies, body fragments, and objects had been transported by a southerly current flowing west of Sakhalin Island from Soviet waters to Hokkaido’s coastline. While most currents around Moneron Island in the Strait of Tartary flow northward, this particular southerly current between Moneron Island and Sakhalin Island is an exception.

The human remains discovered numbered thirteen in total and included body parts, tissue fragments, and two partial torsos. Identification was not possible for any; however, one torso was identified as belonging to a Caucasian female based on auburn hair found on a partial skull, while another partial body was that of an Asian child with embedded glass fragments. No luggage was recovered among these remains. Non-human items collected by Japanese authorities encompassed dentures, newspapers, aircraft seats, books, eight KAL-branded paper cups, various types of footwear such as shoes, sandals, and sneakers; additionally found were a camera case, a "please fasten seat belt" sign, an oxygen mask, a handbag, a bottle of dishwashing detergent, several blouses, an identity card for passenger Mary Jane Hendrie from Sault Ste. Marie, Ontario, Canada, as well as business cards belonging to passengers Kathy Brown-Spier and Mason Chang. These objects chiefly originated from the passenger cabin. Items typically stored in the cargo hold—such as suitcases, packing crates, industrial equipment, instruments, or sports gear—were notably absent from the recovered debris.

Russian diver accounts

File:Moneron Island.jpg
Moneron Island

Following the collapse of the Soviet Union in 1991, the Russian publication Izvestia released a series of interviews with former Soviet military personnel who had participated in salvage missions aimed at locating and retrieving parts of the downed aircraft.[23] Utilizing trawlers, side-scan sonar, and diving bells over a three-day period, Soviet search teams discovered the aircraft wreckage at an approximate depth of 174 metres (571 ft) near Moneron Island.[23][51] Since no human remains or luggage surfaced in the impact zone, divers anticipated locating passenger remains trapped within the submerged fuselage on the seabed. However, upon visiting the site two weeks post-crash, they observed that the wreckage was fragmented into small pieces and found no bodies:

“I expected the wreck to be largely intact—perhaps somewhat damaged. Divers would be able to enter and inspect everything inside. Instead, it was completely destroyed, scattered like kindling wood. The largest fragments encountered were sturdy braces measuring roughly one and a half to two meters long and 50–60 centimeters wide. The remainder was shattered into tiny fragments...”[23]

According to Izvestia, only ten instances of passenger remains—such as tissue and body parts—were encountered within the debris field, including one partial torso.[52]

Diary entry from Tinro ll submersible Captain Mikhail Igorevich Girs on October 10: Aircraft fragments including wing spars, skin panels, wiring, and clothing were observed; however, no human bodies were found. It appeared that much of this debris had been dragged across the sea floor by a trawl rather than having fallen directly from the aircraft in flight...[53]

Vyacheslav Popov remarked: “I must admit we experienced significant relief upon realizing there were no bodies on the seabed. Not only were there no bodies, but also no suitcases or large bags. I did not miss a single dive and have a vivid memory: The aircraft was filled with debris, but truly devoid of people. Why is this? Usually when an aircraft crashes—even a small one—there are suitcases or bags present, or at least suitcase handles.”Template:Fix/category[citation needed]

Civilian divers who conducted their initial dive on September 15—approximately two weeks after the incident—reported that Soviet military divers and trawlers had already operated in the area prior to their arrival:

Diver Vyacheslav Popov stated: “We later learned that before our arrival, trawlers had already performed some ‘work’ within the designated sector. It is difficult to comprehend what purpose the military saw in dragging everything indiscriminately across the seabed with trawls before deploying submersibles... Clearly, operations should have been conducted in reverse order.”

The ICAO also interviewed several of these divers for its 1993 investigation report: "Besides metal fragments, personal belongings such as clothing, documents, and wallets were observed. Although some evidence of human remains was noted by divers, no complete bodies were recovered."[54]

Soviet initial response

Following the advice of Defense Minister Dmitriy Ustinov but contrary to the counsel of the Foreign Ministry, General Secretary Yuri Andropov chose at first to deny any responsibility for downing the airliner, operating under the assumption that the truth would remain undiscovered or unprovable.[39] As a result, the Soviet news agency TASS issued a statement twelve hours post-incident, describing only that an unidentified aircraft flying without lights had been intercepted by Soviet fighters after infringing on Soviet airspace above Sakhalin. The report claimed the aircraft ignored warnings and "continued its flight toward the Sea of Japan".[39][55] Some analysts suggest that the poor handling of political communications by the Soviet leadership[56] was influenced by Andropov’s deteriorating health, as he was hospitalized permanently in late September or early October 1983 and passed away in February of the following year.[57]

In a 2015 interview, senior Soviet news anchor Igor Kirillov revealed that he was initially provided with a printed TASS statement to read on September 1, which contained a candid admission that the plane had been mistakenly shot down due to an error by the Far Eastern Air Defence Command. However, just as the Vremya evening news began, an editor abruptly replaced his script with another TASS report that contradicted both the initial version and reality.[58]

U.S. response and subsequent actions

File:KAL 007 protests.jpg
Protesters outside the White House demonstrating against the Soviet downing of KAL 007 (September 2, 1983)
File:Korean Association of NY on the news regarding KAL 007 (1983).jpg
Korean American community in New York reacting to news of the shootdown (1 September 1983)

The incident occurred amid heightened tensions in U.S.–Soviet relations during the Cold War. The United States pursued a strategy of releasing extensive classified intelligence material to gain a significant propaganda edge over the Soviet Union.[59]

Six hours after the event, South Korea announced that their aircraft had only been forced into an emergency landing by Soviet forces and that all passengers and crew remained unharmed.[60]Template:Page needed At 10:45 on September 1, U.S. Secretary of State George P. Shultz held a press briefing where he revealed intercepted Soviet communications and strongly condemned Soviet actions.[55]

On September 5, President Reagan denounced the attack as the "Korean airline massacre," labeling it "a crime against humanity [that] must never be forgotten" and describing it as "an act of barbarism... [and] inhuman brutality".[61] The next day, U.S. Ambassador to the United Nations Jeane Kirkpatrick presented an audio-visual briefing at the United Nations Security Council, featuring recordings of Soviet pilots’ radio transmissions alongside a map tracing Flight 007’s course leading up to its destruction. Following this presentation, TASS admitted for the first time that the aircraft had been shot down after disregarding warnings. The Soviets disputed much of the U.S.-provided evidence and disclosed for the first time that a USAF RC-135 surveillance plane had crossed paths with KAL 007.

File:Over the horizon antenna.JPG
Japanese signals intelligence listening station at Wakkanai

On September 7, Japan and the United States jointly submitted transcripts of intercepted Soviet communications from their listening post at Wakkanai to an emergency session of the United Nations Security Council.[62] President Reagan issued a National Security Directive emphasizing that Soviet accountability would not be overlooked and launching "a major diplomatic effort to maintain international and domestic focus on Soviet actions".[63] This approach was perceived by Soviet officials as confirmation of Western hostility.

A high-level summit between U.S. and Soviet officials—their first in nearly twelve months—was planned for September 8 in Madrid.[39] The meeting between George P. Shultz and Andrei Gromyko proceeded but was dominated by discussions surrounding KAL 007.[39] The talks concluded on a sour note with Shultz declaring: "Foreign Minister Gromyko's response to me today was even more unsatisfactory than his public statements yesterday. I find it totally unacceptable."[39] In response, President Reagan imposed further restrictions on Aeroflot’s operations including shutting down their ticket offices within the United States. Earlier restrictions on Aeroflot flight routes to and from America had been implemented starting January 1982.[64]

An urgent session of the ICAO convened in Montreal, Canada.[65] On September 12, using its veto power at the United Nations Security Council, Moscow blocked a resolution condemning its role in shooting down KAL 007.[66]

Shortly after this event, New York City’s Port Authority—which manages commercial airports serving New York—denied landing permissions for Soviet aircraft despite obligations under the United Nations Charter requiring host nations to grant access to all member states for UN purposes. In retaliation, TASS and some UN delegates questioned whether it was appropriate for the UN headquarters to remain located within U.S. territory. Acting U.S. permanent representative Charles Lichenstein responded sarcastically that they would not obstruct any move and joked about bidding farewell at dockside as they departed. Officials quickly clarified that Lichenstein’s remarks reflected his personal opinion only.[67]

Against the backdrop of Cold War tensions involving Operation RYAN, deployment of Pershing II missiles in Europe, President Reagan’s Strategic Defence Initiative, and forthcoming Exercise Able Archer ’83, Soviet authorities viewed this incident as an ominous indicator of potential conflict.[57] Officially maintaining that KAL Flight 007 was conducting espionage activities—asserting it "penetrated deep into Soviet territory for several hundred kilometres [miles], ignoring signals and disobeying interceptor fighter orders"—the Soviets contended its mission was reconnaissance aimed at probing defenses near strategic locations such as Kamchatka Peninsula and Sakhalin Island.[2] While expressing sorrow over casualties suffered, Moscow offered no formal apology nor compensation demands.[68] Instead, they accused the CIA of orchestrating this "criminal provocation".[2]

In a comparative analysis published in 1991 by political scientist Robert Entman, contrasting coverage of KAL 007 with that of Iran Air Flight 655—which was shot down by a U.S. warship in 1988—he observed that U.S. media framed KAL 007 as highlighting moral culpability and wrongdoing by its perpetrator nation while framing Iran Air Flight 655 more as a complex technological mishap minimizing guilt.[69]

NTSB

Because the flight originated from U.S. territory and involved the deaths of American citizens, the National Transportation Safety Board (NTSB) was mandated by law to conduct an inquiry. On the morning of September 1, James Michelangelo, the NTSB chief in Alaska, was instructed by the NTSB headquarters in Washington—acting on behalf of the State Department—to forward all materials related to the investigation to Washington. He was also informed that the State Department would assume responsibility for the investigation.[70]

After concluding that the incident was not accidental, the U.S. State Department terminated the NTSB’s inquiry and initiated an International Civil Aviation Organization (ICAO) investigation. Analysts like Johnson have argued that this transfer of responsibility was unlawful, suggesting that by delegating the investigation to ICAO, the Reagan administration effectively prevented potentially sensitive political or military evidence from being subpoenaed—evidence that might have contradicted their official narrative or caused embarrassment.[71] Unlike the NTSB, ICAO lacks subpoena power over individuals or documentation and must rely on voluntary cooperation from the involved nations—in this case, the United States, Soviet Union, Japan, and South Korea—to provide relevant information.

Initial ICAO investigation (1983)

Prior to the KAL 007 incident, ICAO had only once been involved in investigating an aviation disaster—the downing of Libyan Arab Airlines Flight 114 by Israeli F-4 fighters over the Sinai Peninsula on February 21, 1973. According to ICAO convention, the state where the event occurred (the Soviet Union) was responsible for leading the investigation alongside the country where the aircraft was registered (South Korea), as well as Japan, whose air traffic control managed the flight's airspace, and the United States, as manufacturer of the aircraft.

The ICAO-led inquiry was headed by Caj Frostell,[72] but lacked authority to compel any of the participating nations to submit evidence; it depended entirely on voluntary disclosures.[73] As a result, crucial materials such as radar recordings, intercept communications, air traffic control tapes, and data from both the Flight Data Recorder (FDR) and Cockpit Voice Recorder (CVR)—which had been kept secret by Soviet authorities—were unavailable. The investigation included several simulations conducted with assistance from Boeing and Litton, which produced the navigation system.[74]

On December 2, 1983, ICAO published its report concluding that entry into Soviet airspace was unintentional. One possible cause for this deviation was identified as the autopilot remaining engaged in HEADING hold rather than switching to INS mode after leaving Anchorage. The report suggested that either the crew failed to select INS mode or that it did not activate because the aircraft had already drifted off course.[15] The crew reportedly did not detect this navigational mistake nor perform subsequent checks that would have revealed increasing divergence from their assigned route. This oversight was attributed to a "lack of situational awareness and flight deck coordination".[75]

The report included a declaration from Soviet authorities stating that "no remains of victims, instruments or their components or flight recorders have been found to date".[76] However, this claim was later disproven when Boris Yeltsin released a November 1983 memorandum in 1993 from KGB chief Viktor Chebrikov and Defence Minister Dmitriy Ustinov to Yuri Andropov. The document revealed that in late October of that year, flight recorders had been recovered and transported by air to Moscow for analysis at an Air Force research facility.[77] Additionally, Soviet civilian divers recalled viewing parts of the wreckage on the seabed as early as September 15—just two weeks after the shoot-down.[78]

Following release of its findings, ICAO passed a resolution condemning the Soviet Union for its attack.[79] Moreover, these events prompted a unanimous amendment in May 1984—though it did not take effect until October 1, 1998—to the Convention on International Civil Aviation. This revision provided more explicit definitions regarding use of force against civilian aircraft.[80] The amended section 3(d) states in part: "Contracting States acknowledge that no State shall resort to weapons against civil aircraft in flight and that during interception operations both passenger lives and aircraft safety must be preserved."[81]

Radar records from the U.S. Air Force

In aviation accident cases that may lead to legal action, it is standard practice for the Air Force to seize radar tracking data. During the civil lawsuit concerning damages, the United States Department of Justice disclosed that the radar recordings from the Air Force station at King Salmon, Alaska—relevant to KAL 007's flight near Bethel—had been destroyed and thus were unavailable to the plaintiffs. Initially, Justice Department attorney Jan Van Flatern claimed these tapes were erased 15 days following the shoot-down. He later corrected himself, stating the destruction occurred approximately 30 hours after the incident. A Pentagon representative confirmed this timeline, explaining that such tapes are typically recycled within 24 to 30 hours; notably, the outcome of KAL 007 was already known within this period.[82]

Developments during the interim period

File:Boris Yeltsin 21 February 1989-1.jpg
Boris Yeltsin

Hans Ephraimson-Abt, father of Alice Ephraimson-Abt who perished on the flight, led the American Association for Families of KAL 007 Victims. He tirelessly sought answers across three U.S. administrations, making approximately 250 trips to Washington and engaging with 149 officials from the State Department. After the U.S.S.R.'s collapse, Ephraimson-Abt convinced Senators Ted Kennedy, Sam Nunn, Carl Levin, and Bill Bradley to send a letter to Soviet President Mikhail Gorbachev requesting details about the incident.[83]

The introduction of Glasnost reforms in that same year led to a loosening of press restrictions in the Soviet Union; as a result, media reports began emerging indicating that Soviet military authorities were aware of the crash site and had possession of the flight recorders.[23][84] On December 10, 1991, Senator Jesse Helms from the Committee on Foreign Relations addressed a letter to Boris Yeltsin seeking information regarding any survivors among KAL 007’s passengers and crew, including Congressman Larry McDonald.[85]

On June 17, 1992, President Yeltsin disclosed that following the failed coup attempt in 1991, efforts were undertaken to locate Soviet-era documents related to KAL 007. He referenced finding "a memorandum from K.G.B. to the Central Committee of the Communist Party," which acknowledged a tragedy had occurred and mentioned documents "that would clarify the entire picture." Yeltsin noted that this memo further stated these documents were so deeply hidden that it was unlikely future generations would uncover them.[86] Subsequently, on September 11, 1992, Yeltsin officially confirmed the existence of the flight recorders and pledged to provide South Korea with transcripts derived from KGB files.

In October 1992, Hans Ephraimson-Abt led a group comprising family members and U.S. State Department representatives on a visit to Moscow at President Yeltsin’s invitation.[87] During an official ceremony held at St. Catherine's Hall within the Kremlin, this delegation received a portfolio containing partial translations into Russian of the KAL 007 cockpit voice recorder transcripts alongside Politburo documents related to the disaster.

During a November 1992 official trip aimed at strengthening bilateral ties in Seoul, President Yeltsin handed over two flight recorder containers to Korean President Roh Tae-woo, though he did not provide the actual tapes. The International Civil Aviation Organization (ICAO) subsequently voted in December to reopen investigations into KAL 007 in light of this new information. On January 8, 1993, ICAO took possession of these tapes in Paris.[6] Alongside these were recordings of communications between Soviet ground control and military aircraft.[88] The Bureau of Enquiry and Analysis for Civil Aviation Safety (BEA) in Paris transcribed these materials with representatives present from Japan, Russia, South Korea, and the United States.[88]

A formal inquiry conducted by Russia in 1993 cleared Soviet leadership of responsibility for the incident, concluding it was a case of mistaken identity.[57] On May 28 that year, ICAO submitted its second report to the Secretary-General of the United Nations.

Soviet memoranda

File:Mikhail Merchink.jpg
Mikhail Merchink, primary Soviet vessel in the mock search operation

In 1992, Russian President Boris Yeltsin revealed five classified memos originating a few weeks after the 1983 downing of KAL 007.[note 3] These communications from KGB Chief Viktor Chebrikov and Defense Minister Dmitriy Ustinov to General Secretary Yuri Andropov demonstrated that the Soviets were aware of KAL 007's crash site while conducting a simulated search and actively disrupting the U.S. Navy; notably, they recovered the crucial cockpit voice recorder on October 20, 1983—50 days post-incident.[89] This information was deliberately withheld because the recordings failed to conclusively support their entrenched belief that KAL 007’s flight into Soviet airspace was a premeditated intelligence operation.[90][91]

Template:Quote box

The third memorandum confirms that examination of the recorder tapes revealed no signs that the Soviet interceptor attempted radio communication with KAL 007 or fired warning shots.

However, if flight recorders become accessible to Western countries, their data might confirm there was no effort by the intercepting aircraft to establish radio contact with the intruder plane on frequency 121.5 MHz and no tracer warning shots were fired during the final segment of the flight.[92]

The notion that Soviet search efforts were merely a façade—despite knowing where the wreckage lay—is further supported by Mikhail Prozumentshchikov, Deputy Director of the Russian State Archives of Recent History, in his article commemorating the twentieth anniversary of the shoot-down. Reflecting on Soviet and American search operations, he stated: "Since naturally the U.S.S.R. had superior knowledge regarding where the Boeing was downed...it was quite challenging to recover anything, especially considering that the U.S.S.R. had little genuine interest."[93]

Updated ICAO Investigation (1993)

During his visit to Seoul on November 18, 1992, Russian President Boris Yeltsin made a diplomatic gesture toward South Korea by handing over the flight data recorder (FDR) and cockpit voice recorder (CVR) from KAL 007 as part of a treaty ratification process. Early examinations conducted by South Korean officials found the FDR to be blank, while the CVR contained only an unintelligible duplicate. Subsequently, the Russian authorities transferred these recordings to the ICAO Secretary General. The ICAO's findings reaffirmed the initial conclusion that KAL 007 had inadvertently entered Soviet airspace, based on the analysis of cockpit conversations captured by the CVR. The report suggested that the aircraft either maintained a fixed magnetic heading without engaging the Inertial Navigation System (INS) to follow its designated waypoints or, if the INS was activated, it occurred after the plane had already strayed beyond the 0.5-nautical mile Desired Track Envelope necessary for waypoint acquisition.

File:Grossi-7.png
Example of a digital flight data recorder and cockpit voice recorder[note 4]

Furthermore, Russia provided ICAO with "Transcript of Communications. U.S.S.R. Air Defence Command Centres on Sakhalin Island," which formed part of the revised 1993 ICAO document titled "The Report of the Completion of the Fact-Finding Investigation." These transcripts consist of two reels containing multiple communication tracks, precisely time-stamped—some down to the second—detailing exchanges among command centers and military units on Sakhalin Island. They cover events starting from the initial shoot-down orders, through Major Osipovich’s pursuit of KAL 007 in his Su-15 interceptor, and include real-time commentary from General Kornukov, commander of Sokol Air Base, as well as communications descending through the chain of command to Combat Controller Captain Titovnin.

The transcripts further document KAL 007’s flight path following the missile strike until it reached Moneron Island, its subsequent descent over Moneron, Soviet search and rescue operations in the area, unsuccessful attempts by support interceptors to locate debris on water, and conclude with Osipovich’s post-mission debriefing upon return to base. These communications feature both telephone conversations among commanding officers issuing directives and recorded responses correlating to radar observations of KAL 007. The simultaneous multi-track transmissions from various command posts create a comprehensive overview of operational activities during the incident.

Data extracted from both the CVR and FDR indicated that recordings ceased abruptly after 1 minute and 44 seconds into KAL 007’s 12-minute flight following missile impact. The remainder of this flight segment was reconstructed using Russia’s 1992 submission to ICAO comprising real-time Soviet military communications related to the attack and its aftermath. Notably, both recorder tapes terminated simultaneously at precisely 104 seconds post-detonation (18:38:02 UTC), leaving more than ten minutes of subsequent flight unrecorded before radar contact was lost at 18:38 UTC. The ICAO report acknowledged this unexplained simultaneous cessation, noting that power cables for both recorders ran separately along opposite sides of the fuselage before converging behind them, offering no clear reason for their concurrent failure.

Passenger distress and suffering

The extent of passenger pain and suffering played a significant role in determining the compensation awarded by Korean Air Lines.

Fragments from the R-98 medium-range air-to-air missile, which detonated approximately 50 metres (160 ft) behind the tail, caused perforations in the pressurized passenger cabin. When a crew member contacted Tokyo Area Control just over a minute after the missile explosion, his breathing was notably labored, suggesting he was speaking through the microphone integrated into his oxygen mask: "Korean Air 007 ah... We are... Rapid compressions. Descend to 10,000."[94]

During proceedings before then magistrate judge Naomi Reice Buchwald of the United States District Court for the Southern District of New York, two expert witnesses provided testimony regarding pre-impact pain and suffering. Captain James McIntyre, a seasoned Boeing 747 pilot and aircraft accident investigator, explained that shrapnel from the missile caused rapid decompression of the cabin; however, passengers had adequate time to use their oxygen masks: "McIntyre testified that based on his assessment of the damage sustained by the aircraft, all passengers survived the initial missile shrapnel impact. He opined that at least 12 minutes passed from the moment of shrapnel impact until the plane crashed, during which passengers remained conscious."[95]

Alternate explanations

Flight 007 has been surrounded by controversy and has given rise to numerous alternative explanations.[96] Many theories hinge on alleged suppression of evidence such as flight data recorders,[89] unresolved aspects including the involvement of a USAF RC-135 reconnaissance aircraft,[97][98] destruction of U.S. Air Force King Salmon radar records at an inopportune time, Cold War era propaganda and disinformation campaigns, and statements from Osipovich—the Soviet pilot who downed Flight 007—who acknowledged awareness that it was a civilian plane but suspected it might have been used for espionage.[99][100][101]

In his 1985 publication, American historian and professor Alexander Dallin concluded that while it was unlikely the aircraft entered restricted Soviet airspace unintentionally, there was no conclusive proof indicating it did so deliberately.[102]

Aftermath

File:KAL Monument.jpg
"The Tower of Prayer", a monument to KAL 007 at Cape Sōya, Japan

Two television films dramatizing the event were created prior to the Soviet Union's dissolution, which later permitted access to archival materials. The 1988 telefilm Shootdown, featuring Angela Lansbury, John Cullum, and Kyle Secor, was adapted from R.W. Johnson’s book of the same name. It portrayed Nan Moore (played by Lansbury), a mother seeking explanations from both U.S. and Soviet authorities regarding her child's fate. Subsequently, the British Granada Television produced the docudrama Coded Hostile, broadcast on ITV on September 7, 1989. This film focused on the U.S. military and governmental inquiry, emphasizing the probable misidentification of Flight 007 as a USAF RC-135 amid routine SIGINT/COMINT operations in the region. Written by Brian Phelan and directed by David Darlow, it starred Michael Murphy, Michael Moriarty, and Chris Sarandon. An updated version aired on Channel 4 in the UK on August 31, 1993, incorporating findings from the 1992 United Nations investigation.

On September 26, 1983, an incident involving a false nuclear alarm nearly escalated into nuclear conflict. Following the shootdown, Soviet military protocols were primed for immediate retaliation upon detecting a first strike. However, an optical illusion caused their early warning system to malfunction, triggering a false alert.

The Federal Aviation Administration (FAA) temporarily suspended use of Airway R-20—the designated flight path for Korean Air Flight 007—on September 2.[103] Despite strong opposition from airlines due to its status as the shortest among five corridors connecting Alaska and Eastern Asia, the route was reopened on October 2 after thorough safety and navigational aid inspections.[104][105]

Under pressure from the Reagan administration, NATO resolved to deploy Pershing II and Gryphon cruise missile systems in West Germany.[106] These deployments would have positioned missiles within approximately six to ten minutes’ striking distance of Moscow.Template:Fix/category[citation needed] Prior to the shootdown, support for this deployment was uncertain and appeared unlikely to proceed. However, the downing of Flight 007 enabled the United States to rally sufficient domestic and international backing to move forward with implementation.[107]

The unprecedented release of intercepted communications by the United States and Japan exposed significant details about their intelligence operations and capabilities. National Security Agency director Lincoln D. Faurer remarked: "...due to the Korean Air Lines incident, more has been revealed about my organization in recent weeks than I would have preferred... Mostly this was not due to unauthorized leaks but rather a deliberate and responsible choice to confront an otherwise unimaginable tragedy."[108] Subsequently, Soviet alterations to their codes and frequencies diminished the effectiveness of this surveillance by approximately sixty percent.[109]

Led by Hans Ephraimson-Abt, the U.S. KAL 007 Victims' Association successfully advocated before both Congress and airline industry stakeholders for legislation that would guarantee prompt and equitable compensation for future airline disaster victims by increasing payout amounts and easing legal proof requirements regarding airline negligence.[87] This legislation has had lasting impacts on compensation frameworks for subsequent aviation tragedies.

To enhance radar coverage for air traffic control around Anchorage, the U.S. extended military radar range from approximately 200 to 1,200 miles (320 to 1,930 km).[note 5] Additionally, the FAA installed a secondary surveillance radar system (ATCBI-5) on Saint Paul Island. By 1986, the United States, Japan, and the Soviet Union established a joint air traffic control arrangement overseeing North Pacific airspace. This accord assigned formal responsibility to the Soviet Union for civilian air traffic monitoring and created direct communication channels among controllers from all three nations.[110]

On September 16, 1983, a White House press secretary issued a statement regarding Korean Air Lines Flight 007’s downing that included an announcement about making GPS technology available for civil aviation with an anticipated completion date in 1988.[111] While sometimes interpreted as releasing a formerly classified military project for public use, GPS was designed from inception for both military and civilian navigation purposes.[112]

In April 1990, as part of South Korea’s Nordpolitik policy, regular flights between Seoul and Moscow commenced operation through cooperation between Aeroflot and Korean Air. Concurrently, all nine of Korean Air’s European routes began traversing Soviet airspace—marking the first official authorization for Korean Air planes to enter Soviet-controlled skies.[113]

Alvin Snyder, who served as director of worldwide television at the United States Information Agency,[114] produced the video presented to the United Nations Security Council on September 6, 1983.[115] In a retrospective article published in The Washington Post in September 1996, he revealed that his access to Soviet communication transcripts during production was limited.[115] Upon gaining full access in 1993, Snyder acknowledged that "the Russians believed the aircraft was an RC-135 reconnaissance plane,"[115] that "Osipovich (the Soviet pilot) was unable to positively identify it,"[115] and that "he fired warning cannon shots alongside wing-tip signals internationally recognized as commands to land."[115] Some statements contradicted those made by Osipovich himself during an interview with The New York Times,[22] where he confirmed firing warning shots but noted they were not tracer rounds and thus not visible.[116]

In an interview dated March 15, 2001, Valery Kamensky—then commander of the Soviet Far East Military District Air Defense Force and superior officer to General Kornukov—expressed belief that such an incident involving civilian aircraft would be unlikely under evolving political circumstances and alliances. Kamensky also commented on uncertainties surrounding what happened to passengers' bodies after impact: "One hypothesis suggests that following missile detonation both nose and tail sections detached while mid-fuselage acted like a wind tunnel dispersing occupants across ocean surfaces; however some bodies were reportedly recovered during searches. The ultimate fate remains unresolved."[117]

Two monuments commemorate those lost aboard KAL 007: In Hokkaido’s Cape Sōya stands the Tower of Prayer, a ninety-foot structure comprising two hundred sixty-nine white stones symbolizing each victim; meanwhile in Seoul at South Korea’s National Mang-Hyang Cemetery resides the granite KAL Memorial Tower honoring those who perished.[118][119]

Marking two decades since the tragedy on September 1, 2003, Mikhail Prozumentshchikov—Deputy Director of Russia’s State Archives of Recent History—revealed via RIA Novosti that Soviet naval forces involved in searching international waters already possessed accurate knowledge regarding where KAL 007 had crashed but found no significant evidence due to limited interest from USSR authorities.[120]

Korean Air continues service between New York City's JFK Airport and Seoul, though flights now operate nonstop directly to Incheon International Airport, bypassing stops at Anchorage or Gimpo International Airport. The original flight number '007' has been retired; three separate flights now bear numbers '82,' '86,' and '250.' As of October 2025, flight '250' is operated with a Boeing 777F cargo aircraft; flight '86' uses a Boeing 777-300ER, while flight '82' employs an Airbus A380.[121]

In popular culture

The American sci-fi television drama For All Mankind made reference to the incident in its second season, episode seven, by featuring NASA Administrator Thomas O. Paine as a passenger aboard the flight. Within the episode, characters propose different theories for the aircraft's destruction, including the notion of a spy plane (as it passes over the fictional launch site of Buran), or suggest that Paine himself was the primary target, reflecting the series’ alternate history take on the Space Race.

Lee Greenwood composed the song "God Bless the USA" inspired by his emotional response to the downing of Korean Air Lines Flight 007. In his book God Bless the USA, co-written with Gwen McLin, Greenwood explained that the lyrics emerged naturally from the melody as a sincere expression of his American patriotism.

In November 1983, San Francisco's KGO-TV broadcast a promotional commercial for an upcoming news special titled "Green Street Reds," which examined suspicious activities at the Soviet Consulate General. The advertisement depicted Santa Claus and his reindeer being struck down by a Soviet missile. This ad was created by Richard Williams Animation. The graphic portrayal sparked complaints from parents concerned about its negative impact on children’s perceptions of Santa Claus.

The 1984 album Victims of the Future by Gary Moore included a track titled "Murder in the Skies," which addressed Flight 007.

HBO released Tailspin: Behind the Korean Airliner Tragedy in 1989, a film starring Michael Moriarty, Michael Murphy, Chris Sarandon, and Harris Yulin, dramatizing the events surrounding Korean Air Lines Flight 007.

The 1991 thriller A Kiss Before Dying made multiple references to the tragedy.

The ninth season of Cineflix’s series Mayday featured an episode titled "Target Is Destroyed" (S09E05) that recounted this event.

The shootdown was portrayed in the 2024 biographical film Reagan.

In 1984, Italian punk group CCCP - Fedeli alla linea released their debut EP Ortodossia, which included "Spara Jurij," a song inspired by the KAL007 incident. The title, translating to "Yuri, shoot," and its lyrics allude to Yuri Andropov, then leader of the Soviet Union.

See also

Footnotes

  1. ↑ In commercial aviation, two distinct airline identifiers exist. The ICAO code KAL 007, used by air traffic control, differs from the IATA code KE007, which appears on tickets and booking platforms.Template:Citation needed lead
  2. ↑ The last radar position plotted for the target was at 18:35 hours at an altitude of approximately 5,000 meters." (ICAO '93, p. 53)
  3. ↑ These documents were published in the Soviet news magazine, Izvestia #228, October 15, 1992, shortly after Yeltsin's disclosure.
  4. ↑ Illustrative only – this model may differ from KAL 007’s actual equipment.
  5. ↑ These radars had previously been employed in a comparable alert during the Seaboard World Airlines Flight 253A incident in 1968.

Notes

  1. ↑ Young & Launer, pp. xiii, 47
  2. ↑ 2.0 2.1 2.2 Sputnik, The Truth and Lies about the South Korean Airliner
  3. ↑ Pearson, p. 145
  4. ↑ 4.0 4.1 Congressional Record, September 20, 1983, pp. S12462–S12464
  5. ↑ Soviet news magazine, Izvestia #228, October 16, 1992
  6. ↑ 6.0 6.1 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  7. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  8. ↑ 8.00 8.01 8.02 8.03 8.04 8.05 8.06 8.07 8.08 8.09 8.10 8.11 8.12 8.13 8.14 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  9. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  10. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Luffsey
  11. ↑ ICAO 1983, appendix C, p. 2.
  12. ↑ 12.0 12.1 Cite error: Invalid <ref> tag; no text was provided for refs named degani
  13. ↑ Rosenthal, p. 70
  14. ↑ Daniloff, p. 304
  15. ↑ 15.0 15.1 15.2 Cite error: Invalid <ref> tag; no text was provided for refs named NASA
  16. ↑ Milde, p. 53
  17. ↑ Pearson, pp. 40-41
  18. ↑ Pearson, p. 40
  19. ↑ 19.0 19.1 Cite error: Invalid <ref> tag; no text was provided for refs named Wyler
  20. ↑ Kleiner, Korea, a Century of Change
  21. ↑ Pearson (1987), p. 40
  22. ↑ 22.0 22.1 22.2 22.3 Gordon, Ex-Soviet Pilot Still Insists KAL 007 Was Spying
  23. ↑ 23.0 23.1 23.2 23.3 23.4 23.5 Cite error: Invalid <ref> tag; no text was provided for refs named Illesh-Eng
  24. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  25. ↑ Gennady Osipovich interview, The New York Times, September 9, 1996
  26. ↑ ICAO '93, Information Paper No. 1, p. 190
  27. ↑ 27.0 27.1 ICAO '93, p. 55
  28. ↑ 28.0 28.1 28.2 ICAO '93, p. 54
  29. ↑ ICAO '93, Information Paper No. 1, p. 132
  30. ↑ ICAO '93, sect. 3.38, p. 61
  31. ↑ Johnson, p. 30
  32. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Fischer
  33. ↑ Oberg, KAL 007: The Real Story
  34. ↑ "KAL 007: Cover-Up", David Pearson, Summit Press, New York, 1987, p.122
  35. ↑ ICAO '93, section 1.2.1, p.5
  36. ↑ Daniloff, p.300
  37. ↑ Norris and Wagner, Boeing
  38. ↑ ICAO '93, p. 39
  39. ↑ 39.0 39.1 39.2 39.3 39.4 39.5 Oberdorfer, p. 51
  40. ↑ Template:Cite speech
  41. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named ICAO93-93
  42. ↑ ICAO, '93, Information Paper No. 1., pp. 95–96
  43. ↑ 43.0 43.1 Shootdown, R.W. Johnson, Viking, New York, 1985, p. 194
  44. ↑ 44.0 44.1 ICAO '93, p. 17, sect. 1.11.7
  45. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  46. ↑ Winkler, p.47
  47. ↑ Commander Task Force 71 After Action Report (Department of Navy)
  48. ↑ ICAO Report p.28
  49. ↑ After Action Report Department of Navy
  50. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Maier
  51. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  52. ↑ World Wide Issues, February 6, 1991, p. 21
  53. ↑ Izvestia, 28 May 1991, p. 8
  54. ↑ ICAO '93, Sect. 1.12.4
  55. ↑ 55.0 55.1 Daniloff, p. 294
  56. ↑ Dallin, p. 89
  57. ↑ 57.0 57.1 57.2 Pry, pp. 27–32
  58. ↑ Template:Cite interview
  59. ↑ Johnson, pp. 117–121
  60. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  61. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  62. ↑ Ball, pp. 42–46
  63. ↑ Richelson, p. 385
  64. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  65. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  66. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Time1983-09-26
  67. ↑ Luck, Mixed Messages: American Politics and International Organization, 1919–1999, p. 64
  68. ↑ Johnson, p. 110
  69. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  70. ↑ Pearson, p. 127
  71. ↑ Johnson, p. 227
  72. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  73. ↑ Johnson, p. 231
  74. ↑ Johnson, p. 232
  75. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named ICAO 2
  76. ↑ Appendix F, ICAO 83
  77. ↑ Izvestia #228, October 16, 1992
  78. ↑ May 7, 1991, p. 6
  79. ↑ Merrills, p. 61
  80. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  81. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  82. ↑ U.S. District Court, District of Columbia, In re: Korean Airlines disaster of September 1, 1983, February 28, 1985
  83. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  84. ↑ Charles, p. 16
  85. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  86. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  87. ↑ 87.0 87.1 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  88. ↑ 88.0 88.1 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  89. ↑ 89.0 89.1 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  90. ↑ Daniloff, p. 303
  91. ↑ Andrew, p. 60
  92. ↑ Conclusions by Group of Experts from Defense Ministry, KGB of U.S.S.R., and Ministry of Aerospace Industry; Head: Lieutenant-General Makarov Group members: Lieutenant-General Engineer Tichomirov Major-General Engineer Didenko Major-General Aviation Stepanov Major-General Aviation Kovtun Corresponding Member Academy of Sciences Fedosov November 28, 1983
  93. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  94. ↑ ICAO '93, p. 35
  95. ↑ 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)).
  96. ↑ Knight, p. 381
  97. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Schultz367
  98. ↑ Johnson, p. 175
  99. ↑ Pry, p. 31
  100. ↑ Pearson, p. 17
  101. ↑ Young, p. 137
  102. ↑ Dallin, A. (1985). BLACK BOX: KAL 007 and the Superpowers [Book]. University of California Press. https://annas-archive.org/md5/84a60acc79e2b0ad3e7491edabdcac18
  103. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  104. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  105. ↑ Pearson, p. 256
  106. ↑ Blacker, p. 308
  107. ↑ Johnson, p. 75
  108. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  109. ↑ The Baltimore Sun, September 15, 1983, via Johnson, p. 60
  110. ↑ Taubman, Keeping the Air Lanes Free: Lessons of a Horror.
  111. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  112. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  113. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  114. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  115. ↑ 115.0 115.1 115.2 115.3 115.4 "Flight 007: The rest of the story", The Washington Post, September 1, 1996.
  116. ↑ Discovery Channel, episode "Unsolved History, KAL 007"
  117. ↑ Fakty i Kommentarii, March 15, 2001
  118. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  119. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  120. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  121. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).

References

Template:Library resources box

Books

  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Template:Fix/category[dead link]
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).

Journals

  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).Template:Fix/category[permanent dead link]
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).

Online references

  • ASN Aircraft Accident Boeing 747-230B HL7442 Sakhalin Okhotsk Sea – Aviation Safety Database, accessed January 22, 2009
  • Degani, Asaf. Korean Air Lines Flight 007: Lessons From the Past and Insights for the Future. NASA Ames Research Center, September 18, 2001. Available at NASA archives, accessed January 10, 2009. This work is derived from a chapter titled "The Crash of Korean Air Lines Flight 007" in Degani’s 2004 book, Taming HAL: Designing Interfaces Beyond 2001, published by St. Martin's Press (Palgrave-Macmillan).
  • Ephraimson, Hans. "Korean Bribe Rekindles Flight 007 Issues." The New York Times, Letters to the Editor section, January 20, 1996. Retrieved January 13, 2009.
  • Fischer, Benjamin B. "A Cold War Conundrum: The 1983 Soviet War Scare." Central Intelligence Agency publication, March 17, 2007. Archived copy available as of January 14, 2009; original source no longer active. Accessed January 10, 2009.
  • Gordon, Michael R. "Ex-Soviet Pilot Still Insists KAL 007 Was Spying." The New York Times, December 9, 1996. Accessed January 13, 2009.
  • Gwertzman, Bernard. "A New US Transcript Indicates Soviet Pilot Fired 'Cannon Bursts'." The New York Times, September 12, 1983. Retrieved September 1, 2008.
  • Kantakov, Gennady A., and George V. Shevchenko. "In situ observations of Tsushima and West Sakhalin currents near La Perouse (Soya) Strait." North Pacific Marine Science Organization report, January 12, 1999. Archived version from July 17, 2011; original link inactive. Accessed January 8, 2009.
  • Pellerin, Cheryl. "United States Updates Global Positioning System Technology: New GPS satellite ushers in a range of future improvements." United States Government release, February 3, 2006. Archived March 5, 2008; retrieved January 6, 2009.
  • Taubman, Philip. "Khabarovsk Journal; Keeping the Air Lanes Free: Lessons of a Horror." The New York Times, September 17, 1987. Accessed January 8, 2009.
  • Wilkes Jr., Donald E. "The Death Flight of Larry McDonald." Flagpole Magazine, page 7, September 3, 2003. Archived March 14, 2012; original source no longer available.
  • Witkin, Richard. "Soviet Pilot Insists Downed Korean Jet Was Spy Plane." The New York Times, May 19, 1991. Accessed January 25, 2009.

Further reading

  • Bamford, James. The Puzzle Palace: A Report on America's Most Secret Agency. Penguin Books, 1983. ISBN 0-14-006748-5. [1]
  • Clubb, Oliver. KAL Flight 007: The Hidden Story. The Permanent Press, 1985. ISBN 0-932966-59-4. [2] (registration required)
  • Corcoran, Farrel. "KAL 007 and the Evil Empire: Mediated Disaster and Rationalization Forms." Critical Studies in Media Communication 3(3) (1986): 297–316.
  • Kirkpatrick, Jeane Jordan. Legitimacy and Force, chapter "KAL-007: Violating the Norms of Civil Conduct". Transaction, Inc., 1988. ISBN 0-88738-100-6. Pages 374–375. [3] (registration required)
  • Luttwak, Edward N. Strategy and History, chapter "Delusions of Soviet Weakness". Transaction, Inc., 1985. ISBN 0-88738-065-4. Pages 241–243. [4]
  • Maier, Timothy (April 17, 2001). "KAL 007 Mystery." Insight on the News. Archived version available.
  • Morgan, Craig A. "The Downing of Korean Air Lines Flight 007." Yale Journal of International Law 11 (1985): 231+. Online version: [5]
  • Rohmer, Richard. Massacre 007: The Story of the Korean Air Lines Flight 007. Hodder Headline Australia, 1984. ISBN 0-340-36447-5. [6]
  • "Secrets of the Black Box: KAL 007." The History Channel, aired 2006.
  • Snyder, Alvin. Warriors of Disinformation: American Propaganda, Soviet Lies, and the Winning of the Cold War. Arcade Publishing, 1995. ISBN 1-55970-389-X. [7]
  • St. John, Jeffrey. Day of the Cobra: The True Story of KAL Flight 007. Thomas Nelson, 1984. ISBN 0-8407-5381-0. [8] (registration required)
  • Shootdown, IMDb title Q954941.
  • Tailspin: Behind the Korean Airliner Tragedy, IMDb title Q43208915.
  • Soviet Air Force Transcripts at Airliners.net archive: [9]
  • Bickel v. Korean Air Lines case details at Alt law archive: [10] (archived)
  • Hollie v. Korean Air Lines case information at Find law: [11]
  • "KAL Flight 007 25 Years On," The First Post (UK). Archived link available.
  • USS Sterett: Photographs and eyewitness account of US-Soviet naval encounter archived at Sterett.net.
  • Ronald Reagan's televised announcement regarding the downing of KAL 007 on YouTube: video ID 9VA4W1wDMAk.
  • KAL 007 Search and Recovery Operations aboard USS Sterett CG 31 video on YouTube: video ID YglShO6ChW0.
  • FBI files concerning KAL 007 hosted by the Internet Archive.
  • KAL 007 Passenger List as of April 17, 2001 at Rescue007.org.

External links

Template:Cold War Template:Korean Air Template:Aviation accidents and incidents in 1983 Template:Aviation accidents and incidents in the Soviet Union in the 1980s and 1990s Template:Soviet Union–United States relations Lua error in mw.title.lua at line 359: bad argument #2 to 'title.new' (unrecognized namespace name 'Portal'). Lua error in Module:Authority_control at line 159: attempt to index field 'wikibase' (a nil value).