C-130 Reference

C-130 Aircraft Database

C-130 Accidents & Mishaps for the United States Air Force

[Back to C-130 Aircraft Database menu | Missing Photos | Hall of Fame]



Found 211 aircraft, displaying 61- 75 [Sorted by Date]
Date Status Local S/N Aircraft AF/Unit Version Info Details
18 Feb 1968 [ w/o] 58-743 58- 0743 USAF 772 TAS C-130B Details
Destroyed in 122mm rocket attack at Tan Son Nhut AB, South Vietnam. A lucky shot put the mortar down the top hatch. A fuel truck was just ready to make the connection at the time of the explosion. Because of the intense heat and lack of access to the cockpit, the fire was almost impossible to fight. The largest tow-tug on base was used to repeatedly hit the nose of the plane from the side until the heat-stressed aluminum gave way. This opened up the aircraft forward of the wing allowing access to extinguish the fire.
Oct 1961 [ w/o] 58-745 58- 0745 USAF 317 TCW C-130B Details
Damaged by fire at Evreux AB, France. Exact date of occurrence has not been determined. Some sources state while refueling while others states it was during maintenance. Years later the wreckage was moved to Spangdahlem AB, Germany to repair C-130 #58-0734 (c/n 3530) in October 1969.
16 Jul 1979 [ act] 59-533 59- 1533 USAF 187 TAS C-130B Details
Damage by a tornado that swept through Cheyenne, Wyoming. Was repaired.
27 May 1961 [ w/o] 59-534 59- 1534 USAF 773 TCS C-130B Details
During landing with an engine failure, ran off runway at Ramstein AB, Germany.
17 Jun 1967 [ w/o] 60-293 60- 0293 USAF 773 TCS C-130B Details
Overran the runway on aborted take-off at An Khe, South Vietnam.
12 May 1968 [ w/o] 60-297 60- 0297 USAF 773 TAS C-130B Details
Shot down on take-off from Kham Duc, South Vietnam killing the 6 crew and 149 passengers on board.
26 Apr 1968 [ w/o] 60-298 60- 0298 USAF 29 MAS C-130B Details
Crashed after being hit by enemy fire while dropping load at A Loui, South Vietnam (crew from 772nd Tactical Airlift Squadron). All 8 crewmembers were killed.
17 Feb 1967 [ w/o] 60-307 60- 0307 USAF 773 TCS C-130B Details
Crash in rice paddy during emergency landing after split flap problem following take-off from Tay Ninh, South Vietnam.
20 Nov 1978 [ act] 60-310 60- 0310 USAF 68 TAS C-130B Details
Extensive damage due to in-flight fire. Eventually repaired and returned to service with the 68th TAS.
29 Mar 1966 [ w/o] 61-953 61- 0953 USAF 29 TCS C-130B Details
Crash short of the runway during night landing at Pleiku AB, South Vietnam.
25 Oct 1966 [ w/o] 61-955 61- 0955 USAF 48 TCS C-130B Details
Ran off runway during landing after hitting wake turbulence at Fort Campbell, Kentucky and written-off
23 Jun 1969 [ w/o] 61-965 61- 0965 USAF 773 TAS C-130B Details
Stalled and entered a spin after being hit on approach to Katum, South Vietnam.
13 Apr 1968 [ w/o] 61-967 61- 0967 USAF 774 TAS C-130B Details
Burned after sliding off runway on landing following engine failure at Khe Sanh, South Vietnam.
09 Jan 1966 [ w/o] 61-970 61- 0970 C-130B Details
Crash on landing after running off runway when all four engines were reversed at 50 feet above the runway and into a ditch at An Khe, South Vietnam. The five crew survived.
06 Jan 1966 [ w/o] 61-972 61- 0972 C-130B Details
Shot down west of Pleiku AB, South Vietnam.

First Previous 123456789101112131415 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 C-130 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.