F-16 Reference

F-16 Aircraft Database

F-16 Accident Reports for 1997

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



Found 34 aircraft, displaying 16- 30 [Sorted by Date]
Date Status Local S/N Aircraft AF/Unit Version Info Details
12 May 1997 [ w/o] 89153 89- 2153 USAF 524 FS F-16C Block 40 H News Article Details
Crashed at Vaughn, New Mexico. Maintainance error caused a compressor blade to seperated from the engine. The pilot, 1st Lt. Paul J. Murray, ejected at around 400 feet without injuries.
20 Jun 1997 [ w/o] 84255 84- 1255 USAF 194 FS F-16C Block 25 D Details
California ANG F-16 crash near the Saline Valley, California. The pilot, Lt Steven R. Jennings, ejected but dislocated his elbow. A short time after the crash the pilot was picked up by a NAWC China Lake HH-1N. Pilot probably experienced a short G-LOC and regained conscienous just in time to eject before impacting the ground around 14:00 hours.
22 Jul 1997 [ con] FA-56 80- 3547 F-16A Block 15 B Details
Two flame-outs occured when flying over France. After two succesfull airstarts, the aircraft landed safely somewhere in France
25 Jul 1997 [ w/o] 91-0013 91- 0013 TuAF 162 Filo F-16C Block 40 H Details
Crashed near Eskisehir with the pilot ejecting safely.
03 Aug 1997 [ con] FA-89 80- 3580 F-16A Block 15 P Details
During final approach, the nose landinggear refused to exit. The pilot, Cdt. 'Mich' Kerkhofs made a succesfull landing. Damage to the aircraft was limited to the CARAPACE antenna under the intake
06 Aug 1997 [ w/o] 92-016 92- 4016 RoKAF 20 TFW F-16C Block 52 M Details
During a training flight the F-16 crashed into a field in Youju at around 13:56 hours. The pilot escaped unhurt just before the crash. The crash was caused by a failure in the fuel demand/supply system of the aircraft's engine which shut off the engine.
22 Aug 1997 [ w/o] 82037 82- 1037 USAF 39 FTS F-16B Block 15 L Details
Crashed into the Gulf of Mexico 7 miles south of Destin, Florida. The aircraft was based at Eglin. Both crew, Major Paul A. Krause and Captain Stephen E. Gurney ejected safely and were rescued by boat. The plane was returning to Eglin after flying as a chase plane in a mission with an Air Force F-15. Cause was that the 4th stage seperated at a speed past mach.
07 Sep 1997 [ w/o] 991 79- 0410 IDFAF 144 sqn F-16B Block 5 Details
The aircraft crashed in the Negev desert during an instruction flight. The crash was due to a bird ingestion. Both pilots ejected with the instructor being fine but the student being badly wounded.
11 Sep 1997 [ sto] J-228 78- 0228 RNlAF 312 sqn F-16A Block 5 Details
Ran into trees after failing to clear a ridge during a low-level training flight in the Churchill River valley , 55nm southwest of Goose Bay. Structural damage to the wings and fuselage was the result. The aircraft recovered safely at Goose Bay. It is supposed to return to the Netherlands for instructional use. This F-16 was scheduled for retirement anyway
16 Sep 1997 [ act] 84276 84- 1276 USAF 119 FS F-16C Block 25 D Details
Collided with F-16D (#84-1320). Damage was to the left wing, horizontal stabiliser, fuselage, canopy and engine. Estimated at 1.15 million in damage and was repaired.
16 Sep 1997 [ act] 84286 84- 1286 USAF 119 FS F-16C Block 25 D Details
Collided with F-16D (#84-1320), but made it home and was repaired
16 Sep 1997 [ w/o] 84320 84- 1320 USAF 119 FS F-16D Block 25 C News Article Details
Collided with an F-16C (84-1286) from the same squadron over the Atlantic just off the coast. The two aircraft were to rendezvous just after take-off. There destination was Whiskey-107, an ocean training area located 40 miles from Atlantic City. One crew member was rescued at 21:15 hours in good shape. The other crew member was picked up at 21:25 hours and was taken to a trauma center where his condition was stabilized. He had suffered a gash to his head. Damage to the F-16C was to its left wing, horizontal stabiliser, fuselage, canopy and the engine. Damage to this aircraft is estimated to be $1.15 million worth. The F-16D was recovered from the ocean but is a total write off. The aircraft was valued at $16.3 million at the time of the crash. The aircraft belonged to the New Jersey ANG. Surprisingly, blame for the accident was placed on both pilots. The F-16D pilot thought the other aircraft was miles ahead. By the time he spotted the other aircraft it was too late. Lack of communication between both pilots contributed to the accident, as well, both aircraft had their strobe lights turned off. Both pilots were grounded.
18 Sep 1997 [ w/o] 92-004 92- 4004 RoKAF 120 TFS F-16C Block 52 J Details
During a training mission in the Chungnam Province the F-16 slammed into a mountain side at about 14:05 hours. The pilot, Capt. Park Kun, ejected safely. The accident was caused by a crack in a terminal fuel pipe (designated PF4) causing supply shut down.
23 Sep 1997 [ w/o] 131 88- 0131 HAF 330 Mira F-16C Block 30 K News Article Details
Crashed into the eastern part of the Aegean Sea near Agios Efstratios Island. The aircraft was out on a routine training mission. The pilot was missing and assumed to be killed in the mishap
16 Oct 1997 [ act] FA-134 90- 0025 F-16A Block 15 AJ OCU Details
Caught fire during take-off from Villafranca AB, Italy. It was repaired only a week thereafter.

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