Found
29 aircraft, displaying
16-
29
[Sorted by
Date]
Date |
Status |
Local S/N |
Aircraft |
AF/Unit |
Version |
Info |
Details |
12 Jun 1994 |
[
w/o] |
82934 |
82-
0934
|
USAF 169 FS |
F-16A
Block
15
K
ADF
|
|
Details
|
|
|
Written-off in a crash while making a fuel stop at Buckley ANGB, Colorado. When the aircraft lifted off the runway it veered off to the right with the pilot ejecting immediately and landing safe. Cause was determined as non proper trim settings applied for take-off.
|
|
01 Jul 1994 |
[
w/o] |
83173 |
83-
1173
|
USAF 182 FS |
F-16B
Block
15
S
|
|
Details
|
|
|
Crashed at about 10:20 hours some 100 miles from Kelly AFB, Texas at the Crystal Military Operating Area after a bird strike. The incident was during a training mission. Both crew ejected safely and where treated for minor injuries.
|
|
14 Jul 1994 |
[
w/o] |
9852 |
93-
0514
|
EAF 272 TFW |
F-16D
Block
40
N
|
|
Details
|
21 Jul 1994 |
[
w/o] |
508 |
90-
0852
|
IDFAF 101 sqn |
F-16C
Block
40
H
|
|
Details
|
|
|
Crashed after an engine failure.
|
|
Aug 1994 |
[
act] |
777 |
80-
0534
|
|
F-16A
Block
10
D
|
|
Details
|
|
|
Suffered a major oil leak on transit to Israel while at Lakenheath AB where it was repaired and continued on.
|
|
20 Sep 1994 |
[
w/o] |
88488 |
88-
0488
|
USAF 421 FS |
F-16C
Block
40
C
|
|
Details
|
|
|
Crashed at about 11:00 hours in a cornfield 12 miles away from Hill AFB, Utah. The aircraft was on a training mission on the Utah Test and Training Range. The pilot, Capt. Michael D. Goldfein, safely ejected and landed in the Great Salt Lake. He was rescued by a UH-1 from Hill’s 545th Test Group and released from hospital after examination. A faulty fan blade in the engine was the cause of the crash
|
|
04 Oct 1994 |
[
w/o] |
9917 |
90-
0913
|
EAF 262 TFB |
F-16C
Block
40
K
|
|
Details
|
05 Oct 1994 |
[
w/o] |
621 |
90-
0882
|
IDFAF 105 sqn |
F-16D
Block
40
J
|
|
Details
|
18 Oct 1994 |
[
act] |
89058 |
89-
2058
|
USAF 68 FS |
F-16C
Block
40
F
|
AIB Report
|
Details
|
|
|
The aircraft suffered from a B system hydraulic failure with the landing gear failing. The pilot, Lt. Col. Tom Ardern, made a belly landing.
|
|
22 Oct 1994 |
[
w/o] |
82701 |
81-
0899
|
PAF 11 sqn |
F-16A
Block
15
E
|
|
Details
|
|
|
Crashed near Sargodha AB after suffering a birdhit. The pilot ejected safely.
|
|
25 Oct 1994 |
[
w/o] |
90814 |
90-
0814
|
USAF 4 FS |
F-16C
Block
50
B
|
|
Details
|
|
|
Captain Miguel F. Torrealday ejected safely near Wendover, Utah at 9:59 hours after suffering an engine flame-out at low altitude.
|
|
25 Oct 1994 |
[
act] |
J-870 |
81-
0870
|
RNlAF 323 sqn |
F-16A
Block
15
R
|
|
Details
|
|
|
22 Nov 1994 |
[
w/o] |
90-0003 |
90-
0003
|
TuAF 192 Filo |
F-16C
Block
40
D
|
|
Details
|
|
|
Flew into the water of Lake Manjas, Turkey killing the pilot, Captain Oktay Gungordu.
|
|
05 Dec 1994 |
[
w/o] |
163573 |
86-
1691
|
USNavy VF-45 |
F-16N
Block
30
D
|
|
Details
|
|
|
Settled back down on the runway while the undercarriage was being retracted during takeoff. It was departing NAS Key West, Florida. The pilot did eject safely. The wreckage remained at the base for about three months. The pilot was performing touch and goes after a training mission. He was rolling on the main wheels and put the gear handle up prior to advancing the throttle (this can be done prior to weight-on-wheels). As the gear retracted the pilot ejected but before ejecting, he selected augmentor and as he was decending in his parachute, the aircraft was assending and actually got airborn and flew for some several thousand feet before crashing into a salt pond.
|
|
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 |
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.