F-16 Aircraft Database

F-16 Accident Reports for 1998

Found 27 aircraft, displaying 16-27 [Sorted by Date]
Date Status Local S/N Aircraft AF/Unit Version Info Details
09 Aug 1998 [w/o] 368 87-1674 IDFAF 110 sqn F-16C Block 30B Details
Lost power after take-off from Ramat David AB, and crashed into the Jezre'el Valley. Power was lost due to an engine fire which occurred at only 800 feet. The pilot attempted to return to base but ejected just short of the airfield. The ejection caused injuries to the pilot, but turned out to be minor.
24 Aug 1998 [w/o] 88519 88-0519 USAF 36 FS F-16C Block 40D Details
Crashed into the sea at 18:15 hours about one mile off the coast from Kangnung, South Korea. The aircraft was on a routine training flight. Pilot, Captain David W. Murphy, ejected safely. The aircraft suffered an engine burn through.
01 Sep 1998 [w/o] 86324 86-0324 USAF 523 FS F-16C Block 30E News Article Details
Crashed at 9:13 hours, 30 miles southwest of Fort Sumner in the eastern portion of New Mexico. The pilot, Major Kevin Frisbie, was severely injured in the ejection. He was treated at the University Hospital, Albuquerque. Cause of the crash was the pilot having gravity-induced loss of consciousness after preforming a high-g manoeuvre of 6.4 g’s. Frisbie was unconscious for about ten seconds. When he woke he was 70 degrees nose down 5,000 feet altitude and at a speed of 575 knots (1,065 km/h). He attempted to pull out of the dive, but at 300 feet ejected. The pilot knew about the g-suit malfunction prior to flight during his checks. He was cleared to take it as is with a g-limit restriction. His parachute also did not open fully before he impacted the ground causing multiple breaks to both hips and legs. It was over 4 to 6 months until he was around on crutches.
12 Sep 1998 [w/o] 86040 86-0040 USAF 302 FS F-16D Block 32C News Article Details
Crashed onto the Avon Park Range about 50 miles south of Orlando, Florida. The aircraft was in a four ship formation on a gunnery training mission from Homestead Air Reserve Station. The pilot, Capt. Thomas M. Carr, was killed in the mishap, and no one was in the backseat. Cause of the crash was human error, with improper distance with the other aircraft in the formation. Aircraft was on loan to the 93rd FS at the time of loss.
22 Oct 1998 [w/o] 88414 88-0414 USAF 310 FS F-16C Block 42B Details
Crashed at about 13:00 hours, ten miles north of Luke AFB. The pilot, Lt.Col. James Bright, was on a routine air-to-air training mission and ejected safely. The crash was the result of a mid-air collision in which the other aircraft, F-16D #90-0730, landed safely. Cause of the mishap was error due to improper rejoin procedure.
22 Oct 1998 [act] 90730 90-0730 USAF 310 FS F-16C Block 42H Details
Landed safely after a midair collision with F-16C #88-0414. The other aircraft crashed after the pilot had safely ejected. Cause of the mishap was error due to improper rejoin procedure.
09 Nov 1998 [w/o] 88450 88-0450 USAF 421 FS F-16C Block 40C News Article Details
Lost at 15:00 hours in the northern part of the Utah Test and Training Range, about 65 miles west of Hill AFB. The mishap occurred when the aircraft was performing basic fighter manoeuvres. Bad weather slowed search efforts, but is most likely not a factor as it would have been above the weather. The pilot, Major Gregory C. Martineac, did not eject, and was killed. The aircraft was found laying in four feet of mud. Crash probably caused by G-induced loss of consiousness.
17 Nov 1998 [w/o] 85489 85-1489 USAF 113 FS F-16C Block 30B News Article Details
Crashed 70 miles southeast of Indianapolis, Indiana on the north side of the Jefferson Proving Grounds. The aircraft was from the Indiana Air National Guard at Terre Haute. First Lieutenant Chris Snyder was able to eject safely. The mishap occurred at about 14:40 hours. Cause was found to be engine failure.
19 Nov 1998 [w/o] 93538 93-0538 USAF 55 FS F-16C Block 50Q News Article Details
Commander of the 55th Fighter Squadron ejected from this F-16 at Shaw AFB, South Carolina. Lieutenant Colonel Robert Harvey survived the ejection which occurred about 15:00 hours. The pilot ejected under a minute after takeoff. Cause of the crash was due to engine fuel control problems from a faulty AC generator which gave wrong signals to the Digital Engine Control (DEC). Just after the pilot left the aircraft, the engine regained power and flew for an additional thirty seconds before impacting the ground two miles from the end of the runway.
04 Dec 1998 [w/o] 87389 87-0389 USAF 522 FS F-16D Block 30J News Article Details
Crashed 30 miles south of Fort Summer, New Mexico. The pilot, Lieutenant Colonel Randel Meyer, and the passenger, Senior Airman Hugo Serrano-Molina, both ejected safely, but with Hugo breaking his ankle. The aircraft was on an incentive flight as a reward for Hugo. The aircraft was based at Cannon AFB, New Mexico. Cause of the crash was engine failure. This F-16 had been involved in a collision on the runway on January 26th, 1994 at Wright Patterson AFB.
15 Dec 1998 [w/o] 84314 84-1314 USAF 61 FS F-16C Block 25E Details
Major Will Sparrow ejected at 15:30 hours over the Barry M. Goldwater range about 40 miles west of Gila Bend, Arizona. The pilot, who was on a training mission, ejected safely.
29 Dec 1998 [w/o] 9969 93-0503 EAF 272 TFW F-16C Block 40R Details

First Previous 12

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

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