C-130 Reference

C-130 Aircraft Database

C-130 Accident Reports for 1968

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



Found 26 aircraft, displaying 1- 15 [Sorted by Date]
Date Status Local S/N Aircraft AF/Unit Version Info Details
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.
10 Feb 1968 [ w/o] 149813 USMC VMGR-152 KC-130F Details
Crash landed on runway after ground fire set fuel bladder on fire at Khe Sanh, South Vietnam. A bullet also struck the cockpit and one of the engines caught fire. A camera caught the action as it happened and the aircraft blew on touchdown. Of the eleven on board, only 3 survived.
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.
28 Feb 1968 [ w/o] 64-522 64- 0522 USAF 776 TAS C-130E Details
Crash landed and burned after being hit by hit by ground fire on take-off from Song Ba, South Vietnam. Five crew and the five passengers all escaped.
Mar 1968 [ con] 55-023 55- 0023 USAF 374 TCW C-130A Details
Damaged by enemy action in Vietnam but was repaired to become the NC-130A.
02 Mar 1968 [ w/o] 56-549 56- 0549 USAF 21 TAS C-130A Details
Crash during night landing at Phu Bai AB, South Vietnam.
03 Mar 1968 [ w/o] 62-814 62- 1814 USAF 50 TAS C-130E Details
Wrecked after electrical fire in cockpit at Cam Ranh Bay AB, South Vietnam.
11 Apr 1968 [ w/o] 9J-RBZ L100 Details
Destroyed in ground collision when brakes failed and collided with L-100 (c/n 4137) 9J-RCY at Ndola, Zambia. Both L-100's were written-off.
11 Apr 1968 [ w/o] 9J-RCY L100 Details
Destroyed in ground collision when hit by L-100 (c/n 4109) 9J-RBZ when it's brakes failed at Ndola, Angola. Four crew were fine. Both L100's were written-off.
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.
16 Apr 1968 [ w/o] 56-480 56- 0480 USAF 35 TAS C-130A Details
Crash landed at Camp Bunard some 80 kms north of Bien Hoa, South Vietnam. The wreckage was later blown up.
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.
30 Apr 1968 [ w/o] 64145 PAF 6 sqn L100 Details
Wing failed in turbulence near Chaklala, Pakistan causing the aircraft to crash.
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.
12 May 1968 [ w/o] 56-548 56- 0548 USAF 21 TAS C-130A Details
Crash landed on runway after being damaged by small arms fire at Kham Duc, South Vietnam.

12 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.