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 31-45 [Sorted by Date]
Date Status Local S/N Aircraft AF/Unit Version Info Details
25 Jul 1983 [w/o] 78113 78-0113 USAF 61 TFTS F-16B Block 5 Details
Ran out of gas and ended up in the water of the Gulf of Mexico, near McDill AFB, Florida.
08 Nov 1982 [w/o] 79298 79-0298 USAF 63 TFTS F-16A Block 10 Details
Crashed in Avon Park range, Florida during a night training mission killing Captain Francisco Pineiro, Jr. He was a flight instructor.
20 May 1982 [w/o] 79301 79-0301 USAF 421 TFS F-16A Block 10 Details
Hit the ground at Great Salt Lake, Utah killing Major Richard Olson. The F-16 suffered a controlled flight into terrain (CFIT) while in autopilot.
29 Jun 1981 [w/o] 79313 79-0313 USAF 388 TFW F-16A Block 10 Details
Went down in Great Salt Lake, Utah. An EPU problem was the cause of the mishap.
10 Apr 1984 [w/o] 79315 79-0315 USAF 157 TFS F-16A Block 10 Details
Crashed near McEntire ANGB, South Carolina killing the pilot, Lieutenant Colonel Yeadon D. Dorn.
10 Apr 1981 [w/o] 79316 79-0316 USAF 421 TFS F-16A Block 10 Details
At 1:09 local time the main generator warning light came on and the EPU started. The pilot Major John Cary who was part of a four ship flight advised of his emergency and tried to make it to Buckley ANGB. After flying in for five minutes on the EPU, that failed and flight controls were lost. Major Cary ejected at 1000 feet with a 90 degree nose down near Elizabeth, Colorado. Injuries were sore neck, chipped tooth and swollen eye which resulted in temporary blindness. This was caused by the high negative G's the aircraft pulled (-6G during a pitch down). The reason for the failure was due to an EPU overspeed which caused an over voltage to the flight control computer causing it to shut down.
27 Jan 1982 [w/o] 79318 79-0318 USAF 16 TFTS F-16A Block 10 Details
Crashed into an unpopulated area Southwest of Luke AFB, Arizona. Cause of crash was flight control failure, pilot ejected safely.
07 Feb 1985 [w/o] 79323 79-0323 USAF 157 TFS F-16A Block 10 Details
Hit the ground on the Townsend Bombing Range, Georgia
09 Sep 1988 [w/o] 79338 79-0338 USAF 72 TFTS F-16A Block 10 Details
Crashed off the coast of Sarasota, Florida into the Gulf of Mexico. The aircraft was recovered by the Navy and was stored in Hanger 5 for a few years being pretty much intact. The corrosion (caused by the salt water) was terrible. May have been marked 72nd TFTS at the time.
27 Dec 1982 [w/o] 79343 79-0343 USAF 428 TFS F-16A Block 10 Details
The crash occured somewhere over the Nevada desert.
18 Nov 1983 [w/o] 79350 79-0350 USAF 61 TFTS F-16A Block 10 Details
11 Mar 1986 [w/o] 79367 79-0367 USAF 474 TFW F-16A Block 10A Details
Destroyed after a mid-air collision.
30 Jul 1985 [w/o] 79372 79-0372 USAF 72 TFTS F-16A Block 10A Details
Crashed into the Gulf of Mexico killing the pilot, 2nd Lieutenant J. O'brien. Probable cause is believed to be black-out
20 May 1982 [w/o] 79374 79-0374 USAF 428 TFS F-16A Block 10A Details
Crashed on the Ugway range, Utah. During an exercises it suffered a main generator failure. After a sucessful airstart and while enroute to NAS China Lake for an emergency landing an intermittant flame was observed coming from the tailpipe. Upon hearing a loud bang and feeling a reduction of thrust, the pilot successfully ejected.
Unknown [act] 79377 79-0377 USAF 429 TFS F-16A Block 10A Details
This USAF F-16 crashed twice, but was repaired both times - hence it got named 'Twice as Nice'. It was later sold to Israel. The first crash was in 1984 - sometimes when aircraft systems designers integrate various components into an airframe, they forget to examine what happens if a component should fail. Such was the case in the original F-16 design. An electrical connector (cannon plug) came loose and unfortunately the wiring for critical components like brakes and arrestor hook all went through the same connector. The pilot attempted to land the aircraft and engage the arrestor wires. Both wires were missed and the aircraft went off the end of the runway. The pilot stayed with the aircraft and the rescue crews had to cut through the canopy to reach hime - the hole in the canopy can be seen in the photo. After this accident they changed the electrical schematic and wiring harness so that those features went through different connectors now. The second crash occurred a few years later. Cause of mishap was a stuck throttle cable at 70% power. The incident happened at MacDill and the pilot landed the aircraft then ejected when he couldn't stop it. It then went off the end of the runway.

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