F-16 Aircraft Database

F-16 Accident Reports for 1998




Found 27 aircraft, displaying privacy.html-14 [Sorted by Date]
Date Status Local S/N Aircraft AF/Unit Version Info Details
07 Jan 1998 [w/o] 88449 88-0449 USAF 421 FS F-16C Block 40C News Article Details
Had a mid-air collision at about 13:30 hours over Utah Test and Training Range, 105 miles from base. They were in six ship tactical intercept training sortie from Hill AFB. The lead aircraft collided with the wingman of the aggressor formation (#88-0537). The trailing wingman’s aircraft lost 40% of its right wing resulting in an uncontrollable spin. The aircraft crashed within the boundaries of the range. The pilot of this aircraft, Captain Paul Hertzberg, ejected with minor injuries. The other aircraft, an F-16C, suffered a gash in the wing and a lost missile and its rack. The pilot was Captain Scott Hufford, who was able to nurse the aircraft into Michael Army Air Field, Utah.
07 Jan 1998 [act] 88537 88-0537 USAF 4 FS F-16C Block 40D AIB Report Details
Collided with F-16 (#88-0449) who suffered a gash in the wing and a lost missile and its rack. The pilot was Captain Scott Hufford, who was able to nurse the aircraft into Michael Army Air Field, Utah.
08 Jan 1998 [w/o] 89131 89-2131 USAF 34 FS F-16C Block 40G News Article Details
Crashed while on a bombing run at the Test and Training Range, 100 miles west from home base, Hill near Salt Lake City. The pilot, Lieutenant Colonel Judd Kelley, ejected safely. A US Army HH-60 Black Hawk rescued him. The 388th Fighter Wing cancelled all flying for two days. The cause of the crash was due to a missing combustion diffuser pressure seal in the engine. Lack of parts forced the rebuild of the engine to take seven months. Proper daily maintenance logs were not kept to show what work had been preformed. The overheated engine caused it to seize, and no chance for a restart. The aircraft had flown for almost eighteen months without the seal before the crash.
20 Mar 1998 [w/o] 6828 93-0849 RoCAF 21 TFS F-16B Block 20 News Article Details
Crashed in the Taiwan Strait about 55 kilometres west of Huayu islet at Ma-Kung. The accident happened at 14:30 hours while conducting tactical manoeuvre training. Ships and helicopters were used to find the crew, Major Chin-Sung Wen and a student Captain Chia-Cheng Chan. But the search was hampered by strong winds and waves and was in vain. The loss was Taiwan's first with the F-16. Hence all Taiwan F-16's were grounded. F-16B's started flying again on March 25 while F-16A's flew again on March 26.
23 Mar 1998 [act] 89067 89-2067 USAF 4 FS F-16C Block 40F News Article Details
Veered off Hill AFB’s runway returning from a night surface attack at 20:20 hours. The pilot, Lt. Col. John Burgess, Jr, ejected with minor injuries. Cause of the crash was pilot error. On his approach for landing he failed to use proper decent control due to a step late left turn to line up with the runway.
25 Mar 1998 [w/o] 90792 90-0792 USAF 36 FS F-16D Block 40J News Article Details
Crashed into the Yellow Sea 100 kilometres west of Osan AB, South Korea at 20:52 hours. The aircraft was part of a four-ship formation on a combat training mission. Eleven hours after the mishap, the body of Captain Keith A. Sands was found. United States Air Force, Navy and Korean Air Force helped in the search. Korean Navy minesweepers found the wreckage, but the USS Salvor (ARS-52) salvaged 300 pieces to the aircraft, but lacked one large portion. This mishap was caused by a combination of the pilot unintentionally maneuvering his aircraft in excess of briefed parameters, and personal injuries and equipment damage sustained during the subsequent ejection. The pilot did eject safely, but sustained injuries which let him to pass away while in the water.
22 Apr 1998 [w/o] 88473 88-0473 USAF 188 FS F-16C Block 40C News Article Details
Crashed 70 miles southeast of Albuquerque, New Mexico at White Sands Missile Range while on a training mission. The pilot, 2nd Lt. Patrick J. 'Sherman' Potter, was killed in the mishap flying into terrain without ejecting.
13 May 1998 [w/o] 85550 85-1550 USAF 174 FS F-16C Block 30B News Article Details
Crashed at 10:30 hours seven miles south of Ainsworth, Nebraska near Johnston. The aircraft was on a two ship training mission from its home base Sioux City, Iowa. Cause of the crash was due to the F-16 flying through a flock of birds. A minimum of five American White Pelicans struck the aircraft. Damage to the structure, windscreen and ingestion into the engine brought the aircraft down onto hilly grasslands. The pilot, Lt. Col. Lundquist, ejected but was injured hitting the birds during the ejection.
21 May 1998 [scr] J-140 85-0140 F-16A Block 15X Details
While on a low-level flight from Goose Bay, Newfoundland, the aircraft hit trees. The aircraft was able to fly back to base safely. Damage was extensive with the loss of its nose cone and one of its underwing tanks. An inspection of the aircraft deemed it unrepairable.
19 Jun 1998 [w/o] 90798 90-0798 USAF 68 FS F-16D Block 40K Details
Skidded off the runway and burned out during take-off on a post maintenance test flight. The AOA probe was installed backwards. As soon as the aircraft broke ground the aircraft porpoised up and down the runway. Faulty instrument readings gave the wrong angle of attack to the computer. Air data inputs are used to automatically schedule the leading edge flaps and the AOA limiting is in effect. The pilot, Captain Bryan Nordhelm, managed to eject safely. The pilot attempted to correct the bad data but the computer would not respond. The mishap occurred at Hill AFB, but the aircraft is normally operated by the 347th Wing at Moody AFB, Georgia. It was being worked on for NIVIS lighting upgrade before the CCIP package had been released.
23 Jun 1998 [con] FA-120 88-0045 F-16A Block 15AE OCU Details
Landinggear collapse during landing at Kleine-Brogel AB. Aircraft suffered only minor damage
Jul 1998 [i/a] 750 79-0347 F-16A Block 10 Details
Seriously damaged in a ground fire at Hatzor AFB
22 Jul 1998 [w/o] 91397 91-0397 USAF 78 FS F-16C Block 50D News Article Details
Crashed 19 kilometres off the coast of Myrtle Beach, South Carolina. The F-16 was in a simulated air-to-air combat training exercise from Shaw AFB. The pilot, Captain James Sevick, ejected safely and was subsequently rescued by a Coast Guard helicopter. In August the wreckage of the aircraft was recovered from a depth of fifty feet. Cause of the crash was a faulty bearing in the engine which controls airflow. The result was low thrust and inability to retain altitude. Wreckage kept at Shaw AFB.
24 Jul 1998 [w/o] 90804 90-0804 USAF 14 FS F-16C Block 50 News Article Details
Unable to become airborne at 09:05 hours, the aircraft ran into the localiser antenna array at the east end of Misawa AB's runway. The pilot, First Lieutenant Brice Simpson ejected, but landed in the flaming wreckage of the air plane, suffering serious burns. On September 17, the pilot died due to his injuries at Brooke Army Medical Center in San Antonio, Texas. The aircraft was based in Japan. The pilot aborted takeoff, but was unaware of the SAFE-BAR system which could have been deployed and caught by an aircraft's dropped tail hook. It was never known why the pilot aborted the takeoff.
05 Aug 1998 [act] J-640 80-3640 RNlAF 306 sqn F-16A Block 15H Details
Damaged.

12 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



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.