Crash of a Douglas C-47A-25-DK in Calcutta

Date & Time: Apr 2, 1964
Operator:
Registration:
VT-COU
Flight Type:
Survivors:
Yes
MSN:
13570
YOM:
1944
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Calcutta-Dum Dum Airport, the right engine stopped. The copilot-in-command lost control of the airplane that stalled and crashed short of runway threshold. Both occupants were uninjured while the aircraft was damaged beyond repair.
Probable cause:
The accident is attributed to the pilot's action in simulating failure of the starboard engine during the final approach by feathering the propeller without the prior knowledge of the copilot who was handling the aircraft. The copilot was unable to control the aircraft which stalled and crashed. The captain was not authorized to check the capability of the copilot.

Crash of a Fairchild C-119 Flying Boxcar in Barrackpore: 22 killed

Date & Time: Mar 4, 1964
Operator:
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Barrackpore – Bagdogra
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
17
Pax fatalities:
Other fatalities:
Total fatalities:
22
Circumstances:
Shortly after takeoff from Barrackpore Airport, while climbing, the airplane exploded and crashed into the Hooghly River. All 22 occupants were killed.

Crash of an Ilyushin II-14 near Banihal Pass: 13 killed

Date & Time: Feb 18, 1964 at 1540 LT
Type of aircraft:
Operator:
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Srinagar – Udhampur
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
13
Circumstances:
On a flight from Srinagar to Udhampur, the crew encountered poor weather conditions when the airplane struck the slope of a mountain located near the Banihal Pass. SAR operations were conducted but eventually suspended few days later as no trace of the aircraft nor the 13 occupants was found. Mountaineers found the debris in an isolated area in May 1964.

Crash of a Vickers 768D Viscount near Agra: 18 killed

Date & Time: Sep 11, 1963 at 0400 LT
Type of aircraft:
Operator:
Registration:
VT-DIO
Flight Phase:
Survivors:
No
Schedule:
Madras – Nagpur – New Delhi
MSN:
192
YOM:
1957
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
13
Pax fatalities:
Other fatalities:
Total fatalities:
18
Circumstances:
On 10 September 1963, Viscount aircraft VT-DIO was on a scheduled domestic flight, operating the Night Air Mail Service on the route Madras - Nagpur - New Delhi. It took off from Madras at 2240 hours Indian standard time and the flight to Nagpur was uneventful. The aircraft took off from Nagpur with another crew at 0237 hours on 11 September. Communications difficulties were encountered commencing at 0258 hours; the last message known to be sent by the aircraft was at 0336 hours; at that time VT-DIO was flying normally at an altitude of 16 500 ft, the sky was clear and the estimated time of arrival to the Delhi Control boundary was given as 0405. There was enough fuel in the aircraft to maintain flight until 0950 hours. At approximately 0400 hours, the aircraft crashed in a field near village Patti, 15 miles from Agra. The impact resulted in immediate explosion and fire, all aboard being killed.
Probable cause:
The cause of the accident could not be established. Although there is little substantial evidence to support the assumption, it is possible that a sudden malfunctioning of the auto-pilot and/or a sudden failure of the electrical power may have created conditions which made it impossible for the crew to retain control of the aircraft, thus causing it to lose height rapidly and crash to the ground.
Final Report:

Crash of a De Havilland DH.106 Comet 4C off Mumbai: 63 killed

Date & Time: Jul 28, 1963 at 0150 LT
Type of aircraft:
Operator:
Registration:
SU-ALD
Survivors:
No
Schedule:
Tokyo – Hong Kong – Bangkok – Bombay – Bahreïn – Cairo
MSN:
6441
YOM:
1960
Flight number:
MS869
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
55
Pax fatalities:
Other fatalities:
Total fatalities:
63
Captain / Total flying hours:
14841
Captain / Total hours on type:
1473.00
Copilot / Total flying hours:
5463
Copilot / Total hours on type:
475
Circumstances:
Flight 869 was a scheduled international flight from Tokyo, Japan to Cairo, United Arab Republic via Hong Kong, Bangkok, Bombay and Bahrain. A crew change was effected at Bangkok. Based on the tape recordings of messages exchanged between the aircraft and Santa Cruz approach and radar control, the flight was reconstructed. It was uneventful until 2016 hours GMT when it reported arriving over the Santa Cruz VOR at 7 000 ft. It was cleared to descend to 4 000 ft over the VOR and was requested to report what type of approach would be carried out for landing on runway 09. The aircraft reported it would follow the ILS back beam procedure. It was advised by Santa Cruz approach that the back beam of the ILS was not flyable but that it could home on the 270° radial of the VOR. The aircraft agreed to do a VOR letdown for runway 09, and shortly thereafter reported it was leaving 7 000 ft outbound over the sea on the 272° radial of the VOR. At 2018 Santa Cruz radar, which was monitoring the flight, warned it that if it flew more than 6 or 7 miles west of the field it would run into very heavy turbulence. Shortly thereafter the flight requested permission to make a left-hand procedure turn instead of the normal right-hand turn. This was granted. At 2019 the flight commenced the procedure turn inbound. Santa Cruz radar advised the flight that it was then 6 miles west-northwest of the field. Flight 869 acknowledged this message and was not heard from again. During the turn in severe turbulence and heavy rain the pilot lost control of the aircraft. It was found later on that the air- craft had crashed into the sea 9 NM west of Madh Island at approximately 2020 hours.
Probable cause:
The committee was faced with difficulties during the course of the investigation due to the fact that neither the exact location of the wreckage could be fixed no the wreckage salvaged. Moreover, the accident occurred suddenly with no airborne emergency reported and late at night over the sea in limited visibility. There were no eyewitnesses. However, in the presence of the facts available, it can be concluded that the accident was probably due to loss of control while turning in severe turbulence and heavy rain.
Final Report:

Crash of an Antonov AN-12A in New Delhi: 2 killed

Date & Time: Jul 16, 1963
Type of aircraft:
Operator:
Registration:
BL734
Flight Type:
Survivors:
No
MSN:
2 4 013 06
YOM:
1962
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
Crash landed at Palam Airport. At least two crew members were killed.

Crash of a Douglas DC-3 near Pathankot: 29 killed

Date & Time: Jun 3, 1963 at 1130 LT
Type of aircraft:
Operator:
Registration:
VT-AUL
Flight Phase:
Survivors:
No
Schedule:
Amritsar – Srinagar
MSN:
20265
YOM:
1944
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
25
Pax fatalities:
Other fatalities:
Total fatalities:
29
Captain / Total hours on type:
2700.00
Copilot / Total hours on type:
4000
Circumstances:
The aircraft was on a scheduled domestic flight from Amritsar to Srinagar. It took off at 1115LT with 29 persons on board and 7 minutes later it reported its position 25 miles from Amritsar. No further communication was received from the aircraft. Shortly after 1200 hours a report was received by telephone at Amritsar, stating that the aircraft had crashed in a field near the Sarna railway station, about five miles west from Pathankot. The crash took place at a point where the aircraft had to make a left turn of 70° to proceed on its normal course to Srinagar. Eyewitness evidence indicates that the aircraft made a left turn, went out of control and lost height rapidly. It then attained a climbing attitude, broke up and crashed to the ground, catching fire on impact. All 29 occupants were killed.
Probable cause:
The accident was caused by structural failure of the aircraft in the air following overstressing as a result of loss of control. The loss of control was caused by improper rigging of the rudder bungee system which helps to prevent the marked tendency of the rudder of the Hiper Dakota to reverse or lock under conditions of yawed turn and/or encountering a severe side gust. It is equally likely that malfunctioning or improper operation of the autopilot may have initiated a yaw and accentuated the tendency of the rudder to lock.
Final Report: