F-16 Reference

F-16 Aircraft Database

F-16 Accident Reports for 1999

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



Found 29 aircraft, displaying 16- 29 [Sorted by Date]
Date Status Local S/N Aircraft AF/Unit Version Info Details
18 Jun 1999 [ w/o] 87396 87- 0396 USAF 152 FS F-16D Block 42 A Details
A mechanical failure caused the crash of this Arizona ANG jet. The pilot, Timothy English, ejected south of Gila Bend, Arizona. The mishap occurred at about 9:20 hours.
01 Jul 1999 [ w/o] 84268 84- 1268 USAF 93 FS F-16C Block 25 D News Article Details
Major Samuel D'Angelo was killed when his F-16 impacted the ground near Sebring, Florida on the outskirts of the Avon Park Bombing Range. The aircraft was on a low-level training mission. The accident occurred at 11:36 hours. It is believed based on evidence that cause was a bird strike to the canopy and pilot.
09 Jul 1999 [ act] FA-104 87- 0048 F-16A Block 20 MLU Details
Emergency landing at Brüggen AB, Germany after a mission during Allied Force. Cause unknown.
12 Jul 1999 [ w/o] 86284 86- 0284 USAF 523 FS F-16C Block 30 D News Article Details
Crashed during a night training mission at about 8:45 hours. The aircraft crashed eight miles north of Hobbs, New Mexico. The pilot (callsign BamBam) ejected safely only twenty seconds before impact. Cause of the crash was an engine failure, when two blades broke loose due to fatigue. The pilot had attempted two re-lights of engine before ejecting. The aircraft skidded nearly intact partly across a highway. The pilot landed a few hundred yards from the aircraft at which point he picked up the back of his seat (which is quite heavy) carried it to the aircraft and leaned it up against the side of the jet before walking to a farmhouse nearby and calling ops.
26 Jul 1999 [ act] J-636 80- 3636 RNlAF 306 sqn F-16A Block 15 H Details
Damaged and repaired
11 Aug 1999 [ act] 86266 86- 0266 USAF 35 FS F-16C Block 30 D Details
Collided with F-16C (88-0403) and crashed at Kunsan AFB, South Korea. After the pilot, Major Mark Moore, ejected, the aircraft slided down on the runway with the gear torn off but was thought to have been a complete write-off. The aircraft received a landing clearance, while the other was taking off at the same time. The pilot of 88-0403 was able to land his plane with some damage to the left leading edge flap of the wing between stations no. 1 & 2 .
11 Aug 1999 [ w/o] 88403 88- 0403 USAF 35 FS F-16C Block 30 K Details
Collided with another F-16C (86-0266) which crashed. It was about 18:15 hours when the collision occurred and the aircraft were returning from a live weapons training mission. The aircraft that was destroyed impacted near the southern end of Kunsan's runway. The pilot, Major Mark Moore, had ejected safely. Two five hundred pound mk.82 bombs were recovered, however a CBU-87 went missing. It is believed to have been just off shore from the wreckage. The aircraft which landed safely caused the accident by ignoring the calls from the other aircraft in the formation due to focusing too much on flying the aircraft. The aircraft was cleared to land, while the other had a take-off clearance. Damage to this aircraft was in the starboard wing and horizontal stabilizer.
18 Aug 1999 [ w/o] 6680 93- 0781 RoCAF 26 TFS F-16A Block 20 News Article Details
This aircraft was part of a four ship formation which was practising air combat. They had just taken off when aircraft numbered 6689 (not the aircraft which crashed) could not retract its landing gear. The aircraft was ordered back to Chiayi AB, Taiwan with F-16 this aircraft to escort. To burn off extra fuel the aircraft made several passes on the base. At 8:56 hours 6680 began to loose thrust. The pilot, Major Geng-Sheng Lin dropped the external tanks in an effort to lighten the aircraft and come around for landing. But when he reached an altitude of only 150 feet and an airspeed of 132 knots he ejected. The aircraft landed on the ground and did not break-up. Damage was largely limited to the nose. Major Geng-Sheng Lin fractured both legs after ejecting. All Taiwan F-16's were grounded as a result
26 Aug 1999 [ w/o] 92-0009 92- 0009 TuAF 182 Filo F-16C Block 40 L News Article Details
Crashed during landing with the pilot, Lt. Ozcan Kete, ejecting safely.
20 Sep 1999 [ w/o] 83179 83- 1179 USAF 61 FS F-16D Block 25 A Details
Crashed through the fence at the end of the runway at Luke AFB, Arizona. Overshot the runway after touchdown. Sheared the nose and undercarriage off. The aircraft landed without battery power, so the tail hook nor the brakes operated. The pilot, Major Sharon J. Preszler, ejected safely.
23 Sep 1999 [ w/o] J-361 84- 1361 RNlAF 312 sqn F-16A Block 15 W News Article Details
Crashed into the North Sea
17 Nov 1999 [ w/o] 87240 87- 0240 USAF 170 FS F-16C Block 30 F Details
Collided with F-16C (86-0263), near the town of Vermont, Illinois about eighty kilometres north of their base. One pilot landed the aircraft while the other was forced to eject. Cause is believed to have been from one of the pilots losing situational awareness. The mishap occurred as the upgrading pilot performed an air-to-air intercept on the instructor who was acting as a target and flying slow speed with lights out. A high to low intercept was flown by the upgrading pilot and he did not achieve sufficient lateral displacement for his Vc (overtaking velocity). He rolled out behind the target at 500 feet and 180 knots of overtake. An evasive maneuver was initiated at 200 feet and less than 1 second prior to impact. The right wing impacted and severed the target aircraft's left horizontal tail and severely damaged the corresponding hydraulic integrated servoacuator. The aircraft then experienced total hydraulic failure and went out of control. The instructor pilot ejected safely and the upgrading pilot flew his damaged aircraft to base.
17 Nov 1999 [ act] 86263 86- 0263 USAF 170 FS F-16C Block 30 D AIB Report Details
Collided with F-16C (87-0240), near the town of Vermont, Illinois about eighty kilometres north of their base. One pilot landed the aircraft while the other was forced to eject. Cause is believed to have been from one of the pilots losing situational awareness. The mishap occurred as the upgrading pilot performed an air-to-air intercept on the instructor who was acting as a target and flying slow speed with lights out. A high to low intercept was flown by the upgrading pilot and he did not achieve sufficient lateral displacement for his Vc (overtaking velocity). He rolled out behind the target at 500 feet and 180 knots of overtake. An evasive maneuver was initiated at 200 feet and less than 1 second prior to impact. The right wing impacted and severed the target aircraft's left horizontal tail and severely damaged the corresponding hydraulic integrated servoacuator. The aircraft then experienced total hydraulic failure and went out of control. The instructor pilot ejected safely and the upgrading pilot flew his damaged aircraft to base.
22 Dec 1999 [ w/o] J-059 86- 0059 RNlAF 315 sqn F-16A Block 20 MLU Details
Collided in mid-air with a civilian PA-28-140 Cherokee (PH-BLY) close to Hoeven, Netherlands. Both the instructor and student in the Cherokee were killed. A female pilot in the F-16, Lieutenant Lonneke Maes, ejected with minor burns due to the collision. It was the first loss of a Dutch MLU F-16

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




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.