F-16 Aircraft Database

F-16 Accidents & Mishaps for the Republic of Korea Air Force




Found 12 aircraft, displaying termsofuse.html-12 [Sorted by Date]
Date Status Local S/N Aircraft AF/Unit Version Info Details
08 Jun 2001 [w/o] 84-372 84-1372 RoKAF 19 FW F-16D Block 32A Details
Damaged turbine blades in the aircraft's engine's compressor and exhaust caused this aircraft to crash at Andong at 8:35h local. Both pilots escaped safely.
27 Jan 2006 [w/o] 85-576 85-1576 RoKAF 19 FW F-16C Block 32A News Article Details
At 9:50 hours this F-16 crashed during a training mission right after it took off at Chung Ju AB. The pilot, Maj. Kim, ejected safely and is only slightly injured.
19 Nov 2004 [w/o] 85-581 85-1581 RoKAF 19 FW F-16C Block 32B Details
No details are known.
08 Apr 1993 [w/o] 87-655 87-1655 RoKAF 19 FW F-16C Block 32F Details
Impacted the mountains near Chungwon, Korea killing the pilot. The aircraft was returning to base. Weather was good, but it was night.
18 Sep 2002 [w/o] 90-938 90-0938 RoKAF 19 FW F-16D Block 32Q Details
Damage done to fuel pipes during maintenance has caused this aircraft to crash at Nakdong firing range, near Sangju. Both pilots escaped safely.
18 Sep 1997 [w/o] 92-004 92-4004 RoKAF 120 TFS F-16C Block 52J Details
During a training mission in the Chungnam Province the F-16 slammed into a mountain side at about 14:05 hours. The pilot, Capt. Park Kun, ejected safely. The accident was caused by a crack in a terminal fuel pipe (designated PF4) causing supply shut down.
06 Aug 1997 [w/o] 92-016 92-4016 RoKAF 20 TFW F-16C Block 52M Details
During a training flight the F-16 crashed into a field in Youju at around 13:56 hours. The pilot escaped unhurt just before the crash. The crash was caused by a failure in the fuel demand/supply system of the aircraft's engine which shut off the engine.
24 Jan 2003 [act] 92-038 92-4038 RoKAF 20 FW F-16D Block 52K Details
Due to a heavy landing the main gear collapsed. Aircraft was upright but on external tanks.
31 Mar 2009 [w/o] 92-048 92-4048 RoKAF 123 FS F-16D Block 52N News Article Details
Crashed in the Yellow Sea off Taean County, about 150km south-west of Seoul at 12:20h local. Lieutenant Colonel Sohn and Captain Kwak ejected safely.
13 Feb 2007 [w/o] 93-053 93-4053 RoKAF 155 FS F-16C Block 52D News Article Details
The aircraft crashed during an air-to-ground firing exercise over the West Sea near Boryeong, South Chungcheong Province at around 11.00hours local. The pilot, Captain Wu, ejected safely.
26 Feb 2002 [w/o] 93-087 93-4087 RoKAF 157 FS F-16C Block 52D Video footage Details
Fire broke out after takeoff from Sosan AB. Pilot, Captain Roon, ejected safely. The aircraft came down in a rice patty. The crash was caused by material defects in the engine blades.
20 Jul 2007 [w/o] 93-117 93-4117 RoKAF 157 FS F-16D Block 52D News Article Details
The F-16D crashed around 21:00h local time after taking off from Seosan AFB. The two crew members are presumed to have been killed.



Abbreviations and symbols:
[act] Active [i/a] Instructional Airframe [sto] Stored (e.g. at AMARG)
[cld] Cancelled Order [msh] Involved in Mishap [w/o] Write-off
[con] Converted [o/o] On Order
[des] Destroyed (drone) [pre] Preserved (museum, gateguard) T/V LM Aero Type/Version (Construction) number
[emb] Embargoed [scr] Scrapped Photo Available



Any aircraft or serials missing from this list? Did you see incorrect, incomplete, or outdated data?
Add your corrections at the bottom of this page or send them to us!
[Back to the F-16 Aircraft Database]


Errors and Omissions
Bjorn
May 12, 2006 - 04:09 PM
RoKAF mishaps
Editors note: Hereby mishap that we know happened but where we lack the serial number to complete the list: 06/30/2003: A RoKAF viper made a very hard landing at Choongwon at 15:00 hours. The pilot ejected but the aircraft slided further on the runway. This was not a w/o.



Note: Errors and omissions in the above text can be added here. Please note: your comments will be displayed immediately on this page.

If you wish to send a private comment to the webmasters, please use the Contact Us link.