Home | Forum | RSS | Submit News | Upload photos | Contact Us | Search
F-16 Accidents & Mishaps for the United States Air Force

F-16 Aircraft Database

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



Found 449 aircraft, displaying 421-435 [Sorted by Date]
Date Status Local S/N Aircraft AF/Unit Version Info Details
14 Sep 2006 [w/o] 91337 91-0337 USAF 22 FS F-16C Block 50B News Article Details
The aircraft suffered a landing gear failure near Spangdahlem AB after hitting an antenna during a landing attempt. It ran out of fuel before the problem could be fixed and the pilot, 1st Lieutenant Trevor Merrell, executed a controlled bailout. The accident was caused by a visual illusion at Spangdahlem AB. The runway has an upslope, making the pilot think he is coming in too high, forcing him to take a lower approach, with all consequences.
08 Oct 1993 [w/o] 91350 91-0350 USAF 23 FS F-16C Block 50C Details
The aircraft crashed at 1830 hours on a delivery flight at Remsen, near Griffiss AFB, New York. Air Force investigators have concluded that night fog and a blown fuse in instruments that receive landing information were the cause of the crash. Pilot ejected safely. The F-16 cut a 1,000-foot swath through the trees off Joslyn Road before coming to rest in a fiery heap 500 feet from the home of Nick and Diane Polce. The aircraft was being delivered from Fort Worth, Texas to the 23rd FS in Spangdahlem AB, Germany.
11 Jul 1996 [w/o] 91354 91-0354 USAF 77 FS F-16C Block 50C Details
Crashed about 15:30 hours into a house in Pensacola, Florida, following an engine failure 20 miles north of Pensacola while on route from Shaw AFB to Eglin AFB to avoid hurricane Bertha. The pilot was forced to eject two miles short of the runway. A child in the house was killed. A man and woman in the house suffered burns. The pilot ejected safely. The accident investigation showed foreign object damage to a fan blade caused a crack seven thousands of an inch (too small to visually spot). The blade was ingested into the engine. The engine had failed three times during the flight with two relighting's. With the third engine failure the pilot ditched the aircraft into what he hoped was an unpopulated area, and ejected at only 200 feet.
15 Aug 2009 [act] 91364 91-0364 USAF 77 FS F-16C Block 50D News Article Details
During a night training sortie #91-0364 collided with #91-0365 over the Atlantic Ocean approx 126 nautical miles southeast of Shaw AFB. The aircraft suffered moderate damage to flight control surfaces and external stores. The jet recovered to Charleston AFB. #91-0365 crashed after the impact and was destroyed.
15 Oct 2009 [w/o] 91365 91-0365 USAF 77 FS F-16C Block 50D News Article Details
During a night training sortie #91-0365 collided with #91-0364 over the Atlantic Ocean approximately 126 nautical miles southeast of Shaw AFB. The pilot did not survive the collision
Jun 2005 [act] 91374 91-0374 USAF 422 TES F-16C Block 52D Details
Chalks wash out on F-16C #90-0809 during storm and the aircraft rolled into F-16C #91-0374 causing wing tip missile to puncture 374 right under nose. Unknown if the aircraft was marked 53 TEG at the time or not.
Jan 2002 [act] 91377 91-0377 USAF 77 FS F-16C Block 50D Details

Struck by lightning during a sand storm while deployed for OSW. Was the lead aircraft of a two ship formation at an altitude of 35,000 to 40,000 feet when the wall of sand surrounded the aircraft and there was nowhere to go but through the storm. When the lightning strike occurred, the airspeed dropped to zero and the aircraft fell into a flat spint in the orange sand sky. Fortunately the pilot recovered but bottomed out at an altitude of only 500 feet.

Chris, the Crew Chief of #377 describes the experience: "We got the squacks saying my jet was code three for a lightning strike and the other was code one. That was strange to me because there really wasn't too much lightning out there and I had never seen a jet get struck by lightning. Anyway when the jet came in 15-20 minutes later, I noticed immediately something wrong, the ECM pod nose cone was gone! I hooked up the comm cord and said to the pilot like I always do "How are you doing Sir' did you have a good flight?" The only words out of his mouth were "I almost died, your jet saved me, if you could get me out as fast as you can." So as normal I shut him down, and it wasn't till I got a closer look that I noticed all kinds of things wrong; all of the leading edge tape was gone, the static dischargers broke off, the electronic nose cones of the cluster bombs he was carrying were gone and because it was our squadron jet, all the probes that I had polished were sandblasted… After that we had nothing but problems, a standby generator problem which ended up being the harness through the 341 bulkhead, a FLCS problem which was a harness in the right strake and a few flights later tension strut bushing problems that are still going on to this day."
12 Mar 2007 [w/o] 91386 91-0386 USAF 16 WS F-16C Block 52D News Article Details
The aircraft crashed at 20:50 hours local near the end of the runway, while on approach to the Tonopah Test Range Airfield, approximately 20 miles southeast of Tonopah. The aircraft was flying a night training mission over the restricted Nevada Test and Training Range when his AB was stuck. The pilot tried to make an emergency landing but the lights at the airfield didn't come on, so he tried it with his NVG's. Right before he came in, the runway lights came on and he was blinded. He then saw he was short and after he took off the NVG's he ejected safely.
22 Jul 1998 [w/o] 91397 91-0397 USAF 78 FS F-16C Block 50D News Article Details
Crashed 19 kilometres off the coast of Myrtle Beach, South Carolina. The F-16 was in a simulated air-to-air combat training exercise from Shaw AFB. The pilot, Captain James Sevick, ejected safely and was subsequently rescued by a Coast Guard helicopter. In August the wreckage of the aircraft was recovered from a depth of fifty feet. Cause of the crash was a faulty bearing in the engine which controls airflow. The result was low thrust and inability to retain altitude. Wreckage kept at Shaw AFB.
09 Mar 2004 [act] 91398 91-0398 USAF 79 FS F-16C Block 50D AIB Report Details
Suffered a mid-air with F-16C (#97-0109) at approximately 14:40 hours, 35 miles southeast of Myrtle Beach, South Carolina. Both aircraft landed safely
12 Aug 2004 [act] 91405 91-0405 USAF 23 FS F-16C Block 50D Details
The pilot switched to battery power during a recovery operation and EPU fired.
20 Mar 2002 [w/o] 91415 91-0415 USAF 23 FS F-16C Block 50D News Article Details
Crashed while performing a PAR approach at night at Spangdahlem AB near Lancheid, Germany. Pilot, Captain Luke Johnson, was killed in the crash
18 Apr 2005 [w/o] 91469 91-0469 USAF 55 FS F-16D Block 50D Details
Crashed into a marshland area next to Ashley River near Charleston, South Carolina at about 5 pm local time. The aircraft was from the 55th FS but the crew were from the 77th FS. Both of them ejected safely and walked away but were examined at hospital as a precaution. The aircraft was on a routine training mission when it lost engine power.
08 Sep 2011 [i/a] 91470 91-0470 USAF 16 WS F-16D Block 52D Details
A storm hit Nellis AFB, Nevada on September 8, 2011 at just after 5pm causing a row of aircraft sunshelters to fall striking aircraft and injuring airman. In total eleven F-16s including this one and two A-10s were damaged.
17 Nov 2006 [act] 91471 91-0471 USAF 13 FS F-16D Block 50D News Article Details
Smoke filled the cockpit forcing the pilot to make an emergancy landing at Hakodate Airport at around 9:56 hours local. Pilot and aircraft are ok. The cause is still unknown.

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 – Next – Last



Abbreviations and symbols:
[act] Active [msh] Involved in Mishap [w/o] Write-off
[cld] Cancelled Order [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
[i/a] Instructional Airframe [sto] Stored (e.g. at AMARG)



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
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.


RSS | Legal Terms | Privacy Policy | Advertise
Copyright © 2012 Lieven Dewitte and Stefaan Vanhastel
Site F-16 Section AircraftDB