F-16 Reference

F-16 Aircraft Database

F-16 Accident Reports for 1991

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

Found 44 aircraft, displaying 1- 15 [Sorted by Date]
Date Status Local S/N Aircraft AF/Unit Version Info Details
Unknown [ act] 88161 88- 0161 USAF 310 TFTS F-16D Block 42 A Details
Suffered from an electrical fire during start up in 1991. The EPU activated after primary and standby generators fell offline. Spark chasers had a fire in the main landing gear bay during electrical checks. Chafing discovered where the harnesses crossed from the left to the right MLG bays. Depot team from Hill ALC came down and assisted with rewiring from tail to aft seat clock. All power harnesses needed to be replaced. Code 1 on the first FCF flight after all maintenance was completed.
08 Jan 1991 [ w/o] 88483 88- 0483 USAF 4 TFS F-16C Block 40 C Details
The mishap occurred in the north-eastern part of Saudi Arabia at Night Camel West training area. Crashed killing the pilot, Captain Michael L. Chinburg, during a night training flight. It is believed to have been from spatial disorientation. Deployed for Desert Storm, but did not see any combat.
13 Jan 1991 [ w/o] 79400 79- 0400 USAF 138 TFS F-16A Block 10 B Details
Crashed 31 miles southwest of Al Kharj AB, Saudi Arabia. The pilot experienced smoke and fumes in the cockpit. The engine failed and also the EPU. The pilot, Lieutenant Scott Thompson, ejected safely.
15 Jan 1991 [ w/o] 83089 83- 1089 USAF 308 TFS F-16A Block 15 R Details
Crashed 19 miles off Homestead AFB, Florida at 15:00 hours. The aircraft was lost due to a burn-through in the engine and airframe. The pilot, Captain Charles Q. Brown, ejected when ATC personal saw a fire plume coming from the side of the aircraft. It was later determined that during a flame holder assembly change, a maintenance rag was left in the afterburner section causing a hot spot. The airforce F-16 units then began counting rags taken out on a daily basis. The aircraft was viewed with the vertical stabilizer above the water as it crashed in shallow water at the end of the runway.
17 Jan 1991 [ act] 88488 88- 0488 USAF 4 TFS F-16C Block 40 C Details
Sustained battle damage to the bottom of the intake. Repaired by SABCA and returned to the United States on January 22, 1992. The 4th TFS had already been changed to the 4th FS by this time.
18 Jan 1991 [ act] 79391 79- 0391 USAF 138 TFS F-16A Block 10 B Details
Shot up during Desert Storm by AAA on January 18, 1991. Damage was to the ECM pod and the the right wing. Spent a week in BDR before returning to flight a week later.
19 Jan 1991 [ w/o] 87228 87- 0228 USAF 614 TFS F-16C Block 30 F Details
Shot down in Desert Storm from an SA-6. Combat loss number 10 in Desert Storm. The pilot, Captain Harry 'Mike' Roberts, ejected safely, but was taken prisoner. Aircraft was on a mission to attack the Air Defense Headquarters Building in Baghdad. Aircraft had flown 4 combat missions before being lost.
19 Jan 1991 [ w/o] 87257 87- 0257 USAF 614 TFS F-16C Block 30 F Details
Pilot, Major Jeffrey Scott Tice ejected safely after travelling 150 miles inside Iraq, but became a POW as the ejection took place over Iraq. It was the 8th combat loss and the first daylight raid over Baghdad. The aircraft was struck by an SA-3 just south of Baghdad. Aircraft 86-0225 was brought in to replace this lost aircraft. Major Tice's aircraft aborted and 87-0257 was the spare for that day. Wreckage was later found by the US Marines who contacted the squadron to see what they wanted done with the aircraft as the aircraft was largely intact. Order was give to destroy the aircraft. Location of the crash site was in a section of Iraq that the US Marines had occupied. Most reports have the two losses of F-16's from this squadron switched on this date. Flew 4 missions before being written off.
21 Jan 1991 [ w/o] 87224 87- 0224 USAF 614 TFS F-16C Block 30 F Details
An Mk. 84 bomb exploded as it left the aircraft on a strike mission over Kuwait. Pilot, Colonel John Ball, was able to fly the aircraft over water before ejecting. The US Navy rescued John out of the Persian Gulf water. John Ball was the 614th Director of Operations.
24 Jan 1991 [ w/o] 78009 78- 0009 USAF 127 TFTS F-16A Block 1 Details
Collided with F-16A (80-0536), near Beaumont, Kansas. The pilot, Major Cary Carlin, was unfortunately killed.
24 Jan 1991 [ w/o] 80536 80- 0536 USAF 127 TFTS F-16A Block 10 D Details
Collided with F-16A (78-0009), near Beaumont, Kansas. One of the pilots, Major Cary Carlin, was killed.
26 Jan 1991 [ w/o] 81717 81- 0717 USAF 171 FIS F-16A Block 15 E ADF Details
Crashed near Fairhaven, Michigan after suffering an engine stall. The pilot ejected safely.
28 Jan 1991 [ w/o] 85423 85- 1423 USAF 422 TES F-16C Block 25 F Details
Crashed 75 miles north of Las Vegas, in the Nevada Desert. The pilot ejected safely. The crash was caused by an engine failure, specifically due to high time engine being installed in the jet to "get more hours out of it" before sending it to depot for major overhaul.
15 Feb 1991 [ w/o] 84379 84- 1379 USAF 17 TFS F-16C Block 25 E Details
Crashed killing the pilot, Capt. Dale Thomas Cormier. Pilot was attempting to land at Al Dhafra AB, United Arab Emirates. It was a non-combat loss. The pilot never ejected.
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.

123 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

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.