F-16 Reference

F-16 Aircraft Database

F-16 Accidents & Mishaps for the United States Air Force

[Back to F-16 Aircraft Database menu | Missing Photos | Hall of Fame]



Found 523 aircraft, displaying 376- 390 [Sorted by Date]
Date Status Local S/N Aircraft AF/Unit Version Info Details
27 Feb 1991 [ act] 88495 88- 0495 USAF 4 TFS F-16C Block 40 C Details
Probably an SA-8 exploded near the left external tank area. Fragments from the SAM hit the lower left side of the intake, including right through the intake. The left wing had a 2x3 inch hole and the main wing root had damage underneith. Stabilizers were peppered as well as the exhaust tail feathers. Part of the radome was also sheared off, but that damage was done during the crash landing at Rafha, Saudi Arabia when the nose gear would not extend. Major Ed 'Spot' Schumacher was a pilot who was visiting from the Fighter Weapons School and had deployed to Desert Storm with the 4th TFS. The aircraft returned to Hill AFB in a crate from Dahrain AB.
22 Feb 1991 [ act] 88510 88- 0510 USAF 510 FS F-16C Block 40 D Details
28 Jan 2013 [ w/o] 88510 88- 0510 USAF 510 FS F-16C Block 40 D News Article Details
The F-16 was part of a formation when it crashed in the Adriatic Sea between Cervia and Cesenatico around 19:00 hours local. The pilot, Capt. Lucas Gruenther, was sadly killed.
25 Feb 2010 [ w/o] 88513 88- 0513 USAF 36 FS F-16C Block 40 D Details
The right main landing gear collapsed upon landing. An attached AGM-65 missile scraped the runway and the jet veered off the runway to the right.
15 Jun 2003 [ act] 88516 88- 0516 USAF 421 FS F-16C Block 40 D Details
Got hit on the ground by F-16C (88-0421) caused by a hydraulic failure of the other F-16. Cost to repair was $1.1 million and was conducted by the 649th CLSS over a period of two years once work started.
29 Mar 2016 [ w/o] 88518 88- 0518 USAF 421 FS F-16C Block 40 D News Article Details
Crashed right after take off from Bagram AB in Afghanistan at 20:30 local after suffering an engine failure. The pilot ejected safely.
24 Aug 1998 [ w/o] 88519 88- 0519 USAF 36 FS F-16C Block 40 D Details
Crashed into the sea at 18:15 hours about one mile off the coast from Kangnung, South Korea. The aircraft was on a routine training flight. Pilot, Captain David W. Murphy, ejected safely. The aircraft suffered an engine burn through.
23 Feb 1993 [ w/o] 88523 88- 0523 USAF 69 FS F-16C Block 40 D Details
Crashed onto an island on Lake Sinclair, Georgia after an engine failure during a LANTIRN check mission. The pilot, 1st Lt. Ted D. Satcher, ejected safely.
01 Aug 1990 [ act] 88527 88- 0527 USAF 36 TFS F-16C Block 42 D Details
The aircraft ran off the runway after an emergency landing. No-one was hurt.
18 Sep 2007 [ w/o] 88529 88- 0529 USAF 510 FS F-16C Block 40 D News Article Details
The aircraft crashed on a routine training sortie out of Aviano AB in the early evening near the mountains of Belluno. The pilot, Maj. Timothy Palmer, ejected safely.
17 Oct 2001 [ act] 88533 88- 0533 USAF 4 FS F-16C Block 40 D AIB Report Details
Went off the runway during takeoff roll at Hill AFB at 21:50 hours on a night training flight. The aircraft veered off the runway forcing the pilot to eject. Cause was a blown nose gear tire which resulted in loss of directional control. Pilot, Captain Casey J. Tidgewell, sustained only minor injuries. Damage to the aircraft was significant. Cause of the crash was a blown nose wheel which severed important wires and control was lost.
07 Jan 1998 [ act] 88537 88- 0537 USAF 4 FS F-16C Block 40 D AIB Report Details
Collided with F-16 (#88-0449) who suffered a gash in the wing and a lost missile and its rack. The pilot was Captain Scott Hufford, who was able to nurse the aircraft into Michael Army Air Field, Utah.
Nov 1997 [ act] 88541 88- 0541 USAF 510 FS F-16C Block 40 D Details
The F-16 landed nose-down when its nose landing gear wouldn't extend on approach. No-one got injured and the aircraft was swiftly repaired.
08 Aug 2000 [ w/o] 88542 88- 0542 USAF 422 TES F-16C Block 42 D News Article Details
Mid-air collision with another F-16C (90-0809) from the same squadron. The pilot, Major David Kossler, was forced to eject. His aircraft impacted the side of Mormon Mountain. While the other aircraft, piloted by Major Brandon Sweat, landed safely with minor damage. It was about 17:00 hours near Morman Mesa, which is 50 miles northeast of Nellis. The aircraft were part of a four ship formation. The aircraft that survived the collision was repaired and first noticed in service by August 2001 at Nellis AFB as a detachment from Eglin AFB
06 May 2023 [ w/o] 88549 88- 0549 USAF 80 FS F-16C Block 40 D News Article Details
The aircraft crashed during a routine training sortie 10 nautical miles from Osan AB at approximately 09:45h local time. The pilot ejected safely.

First – Previous – 1 – 2 – 3 – 4 – 5 – 6 – 7 – 8 – 9 – 10 – 11 – 12 – 13 – 14 – 15 – 16 – 17 – 18 – 19 – 20 – 21 – 22 – 23 – 24 – 25 – 26 – 27 – 28 – 29 – 30 – 31 – 32 – 33 – 34 – 35 – Next – Last


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

Mar 04, 2022 - 09:51 AM
F-16 CRASH

I couldn't find the Edwards AFB crash of 2001 in this list. I was trying to find what tail number it was.


Mar 04, 2024 - 06:45 AM
Jan 82

Some time in the 80s a f16 landing at nellis missed the the arresting Hook and went thru the barrier at end of runway and came to rest in 3 pieces on the golf course

Pilot was cut out of cockpit and walked away





Please use this form to add any list any error or omissions you find in the above text.

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.