Found
211 aircraft, displaying
46-
60
[Sorted by
Date]
Date |
Status |
Local S/N |
Aircraft |
AF/Unit |
Version |
Info |
Details |
24 Apr 1965 |
[
w/o] |
57-475 |
57-
0475
|
USAF 815 TCS |
C-130A
|
|
Details
|
|
|
Aircraft was low on fuel in bad weather with a heavy load, lost two engines and went down on a mountain side after a go-around at Korat RTAFB, Thailand. Six crew were killed in this first loss to a C-130 in the Vietnam conflict.
|
|
Apr 1959 |
[
act] |
57-490 |
57-
0490
|
USAF 61 TCS |
C-130D
|
|
Details
|
|
|
Nose gear collapsed during a landing on Arctic ice at DYEIII causing some major damage to the nose gear assemble and forward cargo compartment. The aircraft struck a ice ridge formed from wind.
|
|
Unknown |
[
act] |
57-490 |
57-
0490
|
USAF 17 TCS |
C-130D
|
|
Details
|
|
|
Lost prop on engine one and belly landed. Was repaired by April quickly.
|
|
22 Oct 1968 |
[
act] |
57-492 |
57-
0492
|
USAF 17 TAS |
C-130D
|
Pilot Interview
|
Details
|
|
|
Wrecked on landing at on touchdown at Greenland, Dye 3 when the left gear/ski landed in a deep hole in the snow. The gear became detached and on its rearward travel damaged the left para door and the left tailplane. The wing down attitude led to the No 1 propeller striking the snow, which in turn led to serious engine damage and a fire, which was quickly put out. Flew out six weeks later after five weeks of repair. Flew with a few stops to Hayes Aircraft at Birmingham, Alabama for permanent repairs.
|
|
05 Jun 1972 |
[
w/o] |
57-495 |
57-
0495
|
USAF 17 TAS |
C-130D
|
|
Details
|
|
|
Crashed due to rudder stall during flat side-slipping turn.
|
|
06 Oct 1969 |
[
w/o] |
58-718 |
58-
0718
|
USAF 774 TAS |
C-130B
|
|
Details
|
|
|
Mid-air explosion near Chu Lai, South Vietnam.
|
|
11 Jan 1965 |
[
w/o] |
58-719 |
58-
0719
|
USAF 313 TCW |
JC-130B
|
|
Details
|
|
|
Jumped one of two main wheel chocks during engine run-up, with one main gear still anchored, ground looped and ran across ramp and crashed into C-130B #58-0730 destroying both aircraft in the ensuing fire at Forbes AFB, Kansas.
|
|
16 Jul 1979 |
[
act] |
58-720 |
58-
0720
|
USAF 187 TAS |
C-130B
|
|
Details
|
01 Feb 1975 |
[
w/o] |
58-721 |
58-
0721
|
USAF 706 TAS |
C-130B
|
|
Details
|
|
|
Crash on take-off when number one engine failed at New Orleans, Louisiana.
|
|
16 Apr 1967 |
[
w/o] |
58-722 |
58-
0722
|
USAF 29 TCS |
C-130B
|
|
Details
|
|
|
Crash after ammunition load exploded on go-around at Bao Loc, South Vietnam.
|
|
11 Jan 1965 |
[
w/o] |
58-730 |
58-
0730
|
USAF 313 TCW |
C-130B
|
|
Details
|
|
|
Destroyed in a fire after C-130B #58-0719 jumped chocks during an engine run-up and crashed into it at Forbes AFB, Kansas. Both aircraft were written-off.
|
|
06 Feb 1992 |
[
w/o] |
58-732 |
58-
0732
|
USAF 165 TAS |
C-130B
|
|
Details
|
|
|
Stalled on take-off during a simulated engine failure and crashed one mile south of Evansville, Indiana killing all 5 on board as well as 11 on the ground.
|
|
Unknown |
[
con] |
58-733 |
58-
0733
|
USAF 772 TAS |
C-130B
|
|
Details
|
|
|
Damaged in 1968 in South Vietnam but was repaired and rebuilt as a WC-130B.
|
|
09 Jun 1967 |
[
w/o] |
58-737 |
58-
0737
|
USAF 29 TCS |
C-130B
|
|
Details
|
|
|
Crash after structural failure possibly shot down 20 kilometers east of Tan Son Nhut AB, South Vietnam killing 10 on board.
|
|
24 Aug 1992 |
[
w/o] |
58-740 |
58-
0740
|
|
C-130B
|
|
Details
|
|
|
Ground instructional aircraft destroyed in Hurricane Andrew at Homestead AFB.
|
|
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.