Country
Operator Image

Crash of a Fokker F27 Friendship 200 in Agartala

Date & Time: Jun 7, 1970 at 1839 LT
Type of aircraft:
Operator:
Registration:
VT-DVG
Survivors:
Yes
MSN:
10309
YOM:
1966
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
35
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
7273
Aircraft flight cycles:
6429
Circumstances:
Following a wrong approach configuration, the aircraft landed at a too high speed and too far down the runway, some 2,775 feet past the runway threshold. After touchdown, the airplane was unable to stop within the remaining distance, overran, lost its undercarriage and came to rest. All 39 occupants were evacuated safely while the aircraft was damaged beyond repair.
Probable cause:
Wrong approach configuration on part of the flying crew who continued the approach at a too high speed and landed too far down the runway, reducing the landing distance available.

Crash of a Fokker F27 Friendship 200 in Khulna: 44 killed

Date & Time: Apr 21, 1969 at 2030 LT
Type of aircraft:
Operator:
Registration:
VT-DOJ
Survivors:
No
Schedule:
Silchar – Agartala – Calcutta
MSN:
10214
YOM:
1962
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
40
Pax fatalities:
Other fatalities:
Total fatalities:
44
Aircraft flight hours:
14221
Aircraft flight cycles:
12017
Circumstances:
While descending to Calcutta-Dum Dum Airport, the crew encountered poor weather conditions over the border with Bangladesh when control was lost. The airplane crashed in an open field located in Khulna, some 55 km southeast of Dum Dum Airport and was destroyed upon impact. All 44 occupants were killed.
Probable cause:
Loss of control caused by turbulences and severe downdrafts while flying in thunderstorm activity.

Crash of a Douglas DC-3 in Jaipur

Date & Time: Feb 18, 1969
Type of aircraft:
Operator:
Registration:
VT-CJH
Flight Phase:
Survivors:
Yes
MSN:
12477
YOM:
1944
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
26
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the takeoff roll at Jaipur-Sanganeer Airport, the airplane was continuously deviating from the centerline to the left. The captain decided to expedite the rotation. At liftoff, the airplane banked left, causing the left wing to struck the ground. The aircraft then crashed and came to rest in the grassy area. While all 30 occupants escaped uninjured, the aircraft was considered as damaged beyond repair.
Probable cause:
It was reported that the aircraft was overloaded. The total weight of the aircraft was above the MTOW and the CofG was out of enveloppe.

Crash of a Sud-Aviation SE-210 Caravelle VI-N in Bombay: 4 killed

Date & Time: Sep 4, 1966
Operator:
Registration:
VT-DSB
Flight Type:
Survivors:
No
Schedule:
Bombay - Bombay
MSN:
134
YOM:
1964
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
The crew was completing a local training flight at Bombay-Santa Cruz Airport. On final approach, while at an altitude of 800 feet, the crew voluntarily shut down an engine to simulate a failure when the airplane struck a hill and crashed. All four crew members were killed.

Crash of a Douglas C-47A-1-DK in Nagpur

Date & Time: Apr 25, 1966
Operator:
Registration:
VT-DDR
Flight Type:
Survivors:
Yes
MSN:
12070
YOM:
1943
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a positioning flight to Nagpur when he encountered poor weather conditions upon arrival. After touchdown, the aircraft went out of control, veered off runway, struck obstacles and came to rest. All three crew members were uninjured while the aircraft was damaged beyond repair.
Probable cause:
The accident is attributable to a sudden and strong cross wind gust in heavy rain experienced during the landing.

Crash of a Sud Aviation SE-210 Caravelle VI-N in New Delhi: 2 killed

Date & Time: Feb 15, 1966
Operator:
Registration:
VT-DPP
Survivors:
Yes
Schedule:
Calcutta – New Delhi
MSN:
130
YOM:
1964
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
74
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
18378
Captain / Total hours on type:
484.00
Copilot / Total flying hours:
14887
Copilot / Total hours on type:
178
Aircraft flight hours:
5411
Circumstances:
Indian Airlines Corporation, Caravelle, VT-DPP, while on scheduled domestic passenger service from Calcutta Airport to Palam Airport on 15 February 1966, undershot the runway while attempting to land under conditions of poor visibility due to fog at Palam, with the result that it struck a cement pillar and subsequently several other obstructions until it came to rest on its belly near the threshold of the runway in use. Fortunately, all crew and passengers were able to get out before the aircraft was consumed by the fire which had broken out as a result of the earlier impact with obstructions. Some of the passengers received injuries and burns of varying degrees. Unfortunately, two passengers succumbed to their injuries subsequently. The aircraft was completely destroyed.
Probable cause:
The Government of India has accepted that the aircraft undershot and crashed as a result of the abandonment of the ILS approach at too early a stage during an attempt to land under conditions of poor visibility in fog.
Contributory causes were:
(i) Lack of information with the pilot regarding the true conditions of- surface visibility, which was in fact below thi minimum prescribed for a night landing by Caravelle aircraft on runway 28 at Palam.
(ii) Lack of proper monitoring and possibly incorrect setting of altimeter(s) during the approach to land.
(iii) The use of landing lights which resulted in glare during the final stages of the approach in foggy conditions.
Final Report:

Crash of a Fokker F27 Friendship 200 near Banihal: 37 killed

Date & Time: Feb 7, 1966 at 1155 LT
Type of aircraft:
Operator:
Registration:
PH-SAB
Flight Phase:
Survivors:
No
Site:
Schedule:
Srinagar – Jammu – Amritsar – New Delhi
MSN:
10271
YOM:
1965
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
33
Pax fatalities:
Other fatalities:
Total fatalities:
37
Captain / Total flying hours:
17312
Copilot / Total flying hours:
7729
Aircraft flight hours:
1930
Aircraft flight cycles:
1280
Circumstances:
A Fokker F-27, Series 200, aircraft, PH-SAB, owned by the Schreiner Airways of Holland, and operated by the Indian Airlines Corporation on a charter contract, met with an accident shortly before noon on 7 February 1966. The aircraft was on a scheduled flight from Srinagar to Delhi with intermediate stops at Jammu and Amritsar. It crashed on a hilltop in the Pir Panjal range at a spot 12 miles west of its proper course which lay over the Banihal Pass 33'30'' N, 75'14" E (altitude 9 290 ft). All members of the crew and all the 33 passengers on board were killed and the aircraft was totally destroyed.
Probable cause:
The cause of the accident was undoubtedly a navigational error. The Court was at first tempted to accept the hypothesis that the error was committed deliberately by Capt. Duggal because he wanted to take a short cut over the hill to Udampur, instead of going first to Banihal and then turning slightly right to the prescribed route to Udampur. Some support was lent to this hypothesis by the general assessment of Capt. Duggal's character as being hasty and casual and disinclined to pay heed to detail. But after giving greater consideration, it seems to the Court that this hypothesis cannot be accepted and that the navigational error was not intentional. The configuration of the hill at a spot 12 miles west of the Banihal Pass does not snow that the aircraft would have had a clear passage at an altitude of 12,000 feet because there are hills which are 14,000 feet high as shown by the contour lines on the map. Also Duggal did reply to the call 0610 hours GMT when he said that he would be crossing Banihal in two or three minted. It seems to the Court, therefore, that when flying through clouds at an altitude insufficient to ensure safety, Duggal found himself at a spot which resembled in its appearance the Banihal Pass. He must have steered an incorrect heading on leaving the airfield. Changes in cloud formation and decreasing visibility did not permit a full and clear view of the mountain range which lay across the route. So, when he was near the point where it crashed, he thought that he was going to cross Banihal and sent this message to the airport. In point of fact, he was 12 miles off his track and crashed at a point 12,364ft above sea level. A more careful and cautious pilot would, in the circumstances, have made sure of his direction and position by a reference to the Srinagar Airport where, in addition to the VOR, an Automatic Direction Finding facility is available.
Final Report:

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 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:

Crash of a Douglas C-54A-15-DC Skymaster in Haveri

Date & Time: May 7, 1962 at 1655 LT
Type of aircraft:
Operator:
Registration:
VT-DIC
Flight Phase:
Survivors:
Yes
Schedule:
Bangalore – Bombay
MSN:
10376
YOM:
1944
Flight number:
IC106
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
30
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
12777
Captain / Total hours on type:
1806.00
Copilot / Total flying hours:
13499
Copilot / Total hours on type:
2896
Circumstances:
Flight 106 departed from HAL Airport, Bangalore for Bombay at 1555LT on a scheduled domestic flight with 6 crew and 30 passengers on board. After a normal takeoff and climb, the aircraft was cruising at flight level 85 with the engines operating at 29" manifold pressure and 2050 rpm. BMEP gauges were not fitted. At 16:30 hours the flight reported its position 100 miles out from Bangalore and estimated Bombay FIR boundary at 17:00. The flight was uneventful up to about 16:50 when the pilot heard a loud "thud" which he believed to be an engine misfiring. This was followed by the aircraft losing height rapidly. The auto pilot was disengaged and the aircraft was trimmed for manual flight. In order to maintain height the pilot applied climb power, and then METO power by moving the pitch and throttle controls forward, and although the manifold pressure increased first to 35" and then to 40", the engine speed remained constant at 2050 rpm and the aircraft continued to lose height at a descent rate of 1500 feet per minute. Cylinder head temperatures were not apparently noted. The pilot eventually made a wheels-up landing in a ploughed field at an elevation of 1900 feet. All 36 occupants were evacuated safely while the aircraft was damaged beyond repair.
Probable cause:
The accident was attributed to the failure of the crew to diagnose complete loss of power caused by an inadvertent movement of the master ignition switch to the "off" position during flight.
Final Report: