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 166- 180 [Sorted by Date]
Date Status Local S/N Aircraft AF/Unit Version Info Details
11 Apr 2006 [ w/o] 83164 83- 1164 USAF 62 FS F-16C Block 25 B 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 15 Q 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 15 S Details
Crashed at about 10:20 hours some 100 miles from Kelly AFB, Texas at the Crystal Military Operating Area after a bird strike. 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 25 A 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. The pilot, Major Sharon J. Preszler, ejected safely.
16 Jan 2004 [ act] 83184 83- 1184 USAF 62 FS F-16D Block 25 B News Article Details
Canopy inadvertently jettisoned. Damage was repairable.
10 Feb 1995 [ act] 83185 83- 1185 USAF 309 FS F-16D Block 25 B AIB Report Details
Collided with F-16C (88-0478) at Luke AFB, Arizona. Aircraft only lost its nosecone and was repaired.
Unknown [ i/a] 84213 84- 1213 USAF 61 FS F-16C Block 25 C Details
Damaged in a fire involving the JFS. Need to confirm exact date of loss which was in 2007 or 2008.
25 Oct 2001 [ i/a] 84217 84- 1217 USAF 62 FS F-16C Block 25 C AIB Report Details
Major Yarema Sos ejected while the landing gear collapsed on touch-down at Luke AFB. The aircraft came down three quarters of the way down the runway. The F-16 was caught in the turbulence of the aircraft before him and hit the ground well over the structural design limit of the aircrafts landing gear system resulting in a collapse.
17 Feb 1991 [ w/o] 84218 84- 1218 USAF 17 TFS F-16C Block 25 C Details
Had an engine fire coming off a target over Iraq. The pilot, Capt. Scott 'Spike' Thomas, ejected and was rescued.
02 Aug 1988 [ w/o] 84221 84- 1221 USAF 19 TFS F-16C Block 25 C Details
Shortly after the pilot, Capt. Robert F. Weiland Jr. ejected the aircraft impacted an 803 foot radio tower. The F-16 hit the tower about 500 feet above the ground. Possibly the Shaw AFB jet that crashed causing injuries to two people on the ground. Aircraft was on a training mission.
11 Feb 1986 [ w/o] 84224 84- 1224 USAF 19 TFS F-16C Block 25 C Details
Flew into the Gulf of Mexico.
05 Jan 1989 [ w/o] 84228 84- 1228 USAF 19 TFS F-16C Block 25 C Details
Damaged beyond repair in an aborted takeoff from Shaw AFB after multiple bird strike. The pilot was injured in the mishap. Eye witness account by Scott Gandy "I witnessed the mishap from in front of Hanger 1200. Aircraft had birdstrikes right after rotation, pilot then planted airplane on runway and attempted a departure-end barrier engagement. The cable bounced after being run over by the NLG wheel and struck the C/L tank, rupturing it. The spilling fuel was then ignited. The pilot ran the canopy up, over and down the radome he went. It seemed like the jet burned up in two minutes."
25 Jul 1988 [ w/o] 84232 84- 1232 USAF 19 TFS F-16C Block 25 C Details
Crashed and sank to the bottom of the Atlantic Ocean near Georgetown, South Carolina. Captain Paul Stone ejected safely and was released from the hospital the same night. Aircraft was participating in a combat exercise at the time.
12 Nov 1986 [ w/o] 84233 84- 1233 USAF 33 TFS F-16C Block 25 C Details
Crashed near Shaw AFB, South Carolina. The pilot, Lieutenant Colonel Eric Oliver, didn't survive the crash.
23 Sep 2003 [ act] 84240 84- 1240 USAF 309 FS F-16C Block 25 C Details
Left main gear collapsed while landing at night at Luke AFB, Arizona.The center line tank and pod mounted on the left wing sustained the most damage but was repaired. Aircraft was temporarily on loan to the 61st FS at the time of the crash but still owned by the 309th FS.

First Previous 1234567891011121314151617181920212223242526272829303132333435 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.