F-16 Aircraft Database

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

Found 486 aircraft, displaying 151-165 [Sorted by Date]
Date Status Local S/N Aircraft AF/Unit Version Info Details
10 Jan 2002 [w/o] 83133 83-1133 USAF 119 FS F-16C Block 25A Details
Crashed in a heavily wooded area near a highway at Warren Grove Weapons Training Range, New Jersey. Major Robert G. McNally ejected safely.
29 Jan 1997 [w/o] 83134 83-1134 USAF 61 FS F-16C Block 25A Details
The aircraft crashed on the Barry M. Goldwater range near Gila Bend, Arizona. The pilot, capt. Robert Churchill, ejected safely.
31 Aug 2000 [w/o] 83138 83-1138 USAF 119 FS F-16C Block 25A News Article Details
Pilot ejected safely at 1,700 feet over the Atlantic one mile off the coast of Brigantine, New Jersey. The aircraft had engine problems at 15:40 hours, while on a flight of four aircraft. The pilot was picked up by a police boat and transferred to a Coast Guard ship. At 16,000 feet the pilot felt vibrations and immediate deceleration. The cause was a failure and subsequent liberation of a turbine blade from the 3rd stage of the turbine section resulting in damage to the oil system.
01 Sep 1992 [w/o] 83139 83-1139 USAF 314 FS F-16C Block 25A Details
Crashed onto the Barry M. Goldwater range, Arizona. Aircraft experienced an engine failure due to FOD while participating in an ACM IUT sortie. The aircraft was flown by Capt. Eddie "Lizzard" Moran USMC, an F/A-18 pilot on exchange to the USAF. The engine had just been reinstalled in the airframe after returning from a civilian contractor located in Texas. This was the second flight after the installation. The first flight was flown by a student on an instrument training sortie. A tool was left inside the shroud that protects the levers that control the variable compressor blades.
15 May 2007 [act] 83148 83-1148 USAF 119 FS F-16C Block 25B AIB Report Details
Released some flares during an exercise. The flares were deployed below the minimum AGL and started a fire on the test range which eventually consumed up to 18,000 acres and destroying four houses.
25 Jul 1987 [w/o] 83149 83-1149 USAF 33 TFS F-16C Block 25B Details
Crashed somewhere in Jordan.
04 Sep 1990 [w/o] 83151 83-1151 USAF 33 TFS F-16C Block 25B Details
Wingman observed fire coming out of engine during a training sortie. The pilot, Capt. Richard Setzer, was forced to eject. The pilot safely ejected over the Saudi Arabian Peninsula (Abu Dhabi). It was a pre-war loss and wreckage was recovered in attempt to find spare parts, but "none" were usable.
20 Apr 2005 [act] 83159 83-1159 USAF 134 FS F-16C Block 25B News Article Details
Came in to low for landing and struck some runway lights which caused the main landing gear to collapse. Colonel Douglas Fick stayed with the aircraft and was uninjured. The landing happened in severe weather conditions which made the pilot to abort two consequent landing attempts. Trying for a third attempt, he came in too low.
17 Jun 2004 [act] 83161 83-1161 USAF 61 FS F-16C Block 25B News Article Details
Belly landed at Luke AFB. Extremely minor damage, repaired quickly.
11 Apr 2006 [w/o] 83164 83-1164 USAF 62 FS F-16C Block 25B News Article Details
The plane crashed at 09.55 hours local time. The pilot safely ejected right after flames were seen at the rear end of the jet. The F-16 went down in the Northwest Valley, in a farm field near Loop 303 and Indian School Road. The accident occured shortly after the jet took off from Luke AFB for a two-ship training mission. The pilot, 26-year-old Captain Jason Attaway, ejected safely. An explosion of the Pratt & Whitney engine was blamed for the crash.
21 Mar 2001 [i/a] 83169 83-1169 USAF 40 FLTS F-16B Block 15Q AIB Report Details
Aircraft suffered a class A mishap when it ingested a pelican at Eglin AFB and the motor shelled out. The aircraft landed safely at Duke Auxiliary Field and fire broke out. Both pilots managed to walk away without injury but aircraft had major fire damage. The aircraft is now being used on the test range at Eglin AFB, Florida.
01 Jul 1994 [w/o] 83173 83-1173 USAF 182 FS F-16B Block 15S Details
Crashed at about 10:20 hours some 100 mile from Kelly AFB, Texas, at the Crystal Military Operating Area. The incident was during a training mission. Both crew ejected safely and where treated for minor injuries.
20 Sep 1999 [w/o] 83179 83-1179 USAF 61 FS F-16D Block 25A Details
Crashed through the fence at the end of the runway at Luke AFB, Arizona. Overshot the runway after touchdown. Sheared the nose and undercarriage off. The aircraft landed without battery power, so the tail hook nor the brakes operated.
16 Jan 2004 [act] 83184 83-1184 USAF 62 FS F-16D Block 25B News Article Details
Canopy inadvertently jettisoned. Damage was repairable.
10 Feb 1995 [act] 83185 83-1185 USAF 309 FS F-16D Block 25B Details
Collided with F-16C (88-0478) at Luke AFB, Arizona. Aircraft only lost its nosecone and was repaired.

First Previous 123456789101112131415161718192021222324252627282930313233 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

Apr 05, 2017 - 05:18 PM
Urgent question from News Organization

Can you please call me? I'm looking at your data, and want to reference it, and your website, in a story I'm working on but would like to talk to you about the origin of the data on your site.


Lisa Fletcher

Senior Investigative Reporter

ABC7 News, Washington DC


Apr 05, 2017 - 06:48 PM

Dear Lisa, contact me through bjorn@f-16.net

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.