F-16 Reference

F-16 Aircraft Database

F-16 Accident Reports for 2014

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

Found 11 aircraft, displaying 1- 11 [Sorted by Date]
Date Status Local S/N Aircraft AF/Unit Version Info Details
Unknown [ w/o] 157 88- 0045 RJAF 1 sqn F-16A Block 20 MLU Details
Suffered a mishap at an unknown date.
02 Jan 2014 [ sto] 285 78- 0285 RNoAF FLO F-16A Block 20 MLU Details
Nosewheel broke down during touch-and-goes at Bodø AB.
04 Feb 2014 [ sto] 84277 84- 1277 USAF 62 FS F-16C Block 25 D Details
Aircrew was practicing low approaches and impacted landing approach lights. Suffered some damage to the landing gear, the leading edge flaps, right stabiliser and centerline tank. Thought to be repairable, the aircraft failed a canopy sill longeron Inspection which oddly enough was not related to the mishap event. Both the left and right canopy sill longerons were cracked severely the aircraft was shipped it to AMARG.
Jun 2014 [ i/a] 85439 85- 1439 USAF 62 FS F-16C Block 25 F Details
Experienced B system hydraulic failure resulting in alternate gear extension. The nose gear did not fully extend and collapsed on landing. The aircraft scraped the nose the length of the runway, and when it reached to arresting cable on the departure end, the cable went over the jet and came to rest at the dorsal and vertical tail. Although significantly damaged, was deemed repairable.
07 Jul 2014 [ sto] 680 80- 3680 RNoAF FLO F-16A Block 20 MLU News Article Details
Flew into high-voltage power lines in the Grong, near Nord-Trøndelag on July 7th. The jet landed safely after declaring an emergency. A released photograph shows damage to the right wing and drop tank.
20 Oct 2014 [ w/o] 89019 89- 2019 USAF 125 FS F-16C Block 42 E News Article Details
Lost in a crash in a field in Moline, Kansas around 14:00 local after a mid-air collision with F-16C 89-2034 which landed safely while the pilot of the crashed aircraft ejected with injuries.
20 Oct 2014 [ act] 89034 89- 2034 USAF 125 FS F-16C Block 42 E AIB Report Details
This aircraft collided with F-16C 89-2019 causing it to crash. This aircraft managed to land safely after flying 100 miles with a large portion of right wing removed.
07 Nov 2014 [ w/o] 85502 85- 1502 USAF 82 ATRS F-16C Block 30 B News Article Details
Aircraft had not completed modifications to QF-16. The aircraft hit the water of the Gulf of Mexico roughly 74 miles south of Tyndall AFB at 8:34 local time during a routine missions. The pilot, Lt.Col. Matthew J. LaCourse, was unfortunately killed in the mishap. The cause was determined at spatial disorientation suffered by the pilot.
01 Dec 2014 [ w/o] 87-0017 87- 0017 TuAF 152 Filo F-16C Block 30 B News Article Details
The F-16 crashed around 10:50hrs local time during a training flight at 36 kilometers away from the Merzifon district center. The pilot ejected safely.
01 Dec 2014 [ w/o] 91375 91- 0375 USAF 77 FS F-16C Block 50 D News Article Details
Crashed at around 23:00 local right after take off from a fighter base in Jordan (probably Azraq AB) killing the pilot, Capt. William H. “Pyro” Dubois.
04 Dec 2014 [ w/o] 614 99- 1548 HAF 343 Mira F-16D Block 52 News Article Details
The F-16 crashed during a training flight at 13:42h local time, 14 nautical miles north of the island of Gavdos. Both crew members ejected.

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

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.