Found 33 aircraft, displaying 1-9
[Sorted by Date]
| Date |
Status |
Local S/N |
Aircraft |
AF/Unit |
Version |
Info |
Details |
| Unknown |
[act] |
J-200 |
83-1200
|
RNLAF 315 sqn |
F-16A
Block 15U
|
|
Details
|
|
|
|
|
This mishap happened somewhere in 1989. Pilot L. van Bruggen executed a touch-and-go but came back on the runway with a retracted gear.
|
|
| Unknown |
[act] |
301 |
86-1598
|
|
F-16C
Block 30
|
|
Details
|
|
|
|
|
Was damaged in a hard landing in the late 1980's. Main gear struts went through the inlet. Everything below the strake was replaced due to this mishap and was flown again.
|
|
| 04 Jan 1989 |
[w/o] |
83116 |
83-1116
|
USAF 308 TFS |
F-16A
Block 15S
|
News Article
|
Details
|
|
|
|
|
Impacted the ground by Lake Okeechobee near Avon Park range. The pilot, Lt. Mark Pugh ejected safely. It was being flown on a surface attack/tactics mission and he was number four in the formation. While egressing the target area at 515 knots his canopy struck an approximately 8-pound turkey buzzard directly in front of the HUD. The bird's remains penetrated the canopy (this was the first USAF penetration of an F-16 canopy) and hit Pugsly in the chest knocking his left hand onto the ejection handle and his right arm off the sidestick back against the bulkhead. He could only see a small gap near his left hand on the ejection handle which seemed like a good idea so he ejected. The airplane continued and crashed off-range killing a cow. Pugsly's injuries were confined to bruises and lacerations from the canopy plexiglass. He flew again in several weeks and continued as an F-16 LANTIRN and F-15E RTU Instructor Pilot.
|
|
| 05 Jan 1989 |
[w/o] |
84228 |
84-1228
|
USAF 19 TFS |
F-16C
Block 25C
|
|
Details
|
|
|
|
|
Damaged beyond repair in an aborted takeoff from Shaw AFB after multiple bird strike. The pilot was injured in the mishap. Eye witness account by Scott Gandy "I witnessed the mishap from in front of Hanger 1200. Aircraft had birdstrikes right after rotation, pilot then planted airplane on runway and attempted a departure-end barrier engagement. The cable bounced after being run over by the NLG wheel and struck the C/L tank, rupturing it. The spilling fuel was then ignited. The pilot ran the canopy up, over and down the radome he went. It seemed like the jet burned up in two minutes."
|
|
| 10 Jan 1989 |
[w/o] |
676 |
80-3676
|
RNOAF 331 skv |
F-16A
Block 15K
|
|
Details
|
|
|
|
|
Crashed near Andøya, Norway killing the pilot, Bjørn Gunnar Olsen.
|
|
| 29 Jan 1989 |
[w/o] |
86297 |
86-0297
|
USAF 35 TFS |
F-16C
Block 30D
|
|
Details
|
|
|
|
|
Crashed into the Yellow Sea just off South Korea. Pilot ejected and was rescued by a US Army Chinook. The wreck was salvaged by a US Navy vessel. Recovery from the sea took about a week. Photograph taken after recovery.
|
|
| 14 Feb 1989 |
[w/o] |
86274 |
86-0274
|
USAF 35 TFS |
F-16C
Block 30D
|
|
Details
|
|
|
|
|
Crashed in Crow Valley, Philippines with the pilot, 1st Lieutenant Josh Levin, not surviving the crash.
|
|
| 14 Mar 1989 |
[w/o] |
86311 |
86-0311
|
USAF 612 TFS |
F-16C
Block 30D
|
|
Details
|
|
|
|
|
Collided with F-16C (86-0312) over Spain. Both aircraft were lost. One pilot, 1st Lieutenant Danny Ralph Johnson, was killed while the other ejected safely.
|
|
| 14 Mar 1989 |
[w/o] |
86312 |
86-0312
|
USAF 612 TFS |
F-16C
Block 30D
|
|
Details
|
|
|
|
|
Collided with F-16C (86-0311) over Spain. Both aircraft were lost. One pilot, 1st Lieutenant Danny Ralph Johnson, was killed while the other ejected safely.
|
|
|
|
Abbreviations and symbols:
| [act] |
Active |
[msh] |
Involved in Mishap |
[w/o] |
Write-off |
| [cld] |
Cancelled Order |
[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 |
| [i/a] |
Instructional Airframe |
[sto] |
Stored (e.g. at AMARG) |
|
|
Errors and Omissions
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.
|
|