Crash of a Fokker F27 Friendship 100 in Guwahati: 34 killed

Date & Time: Oct 19, 1988 at 0856 LT
Type of aircraft:
Operator:
Registration:
VT-DMC
Survivors:
No
Schedule:
Silchar - Guwahati
MSN:
10173
YOM:
1961
Flight number:
PF703
Location:
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
31
Pax fatalities:
Other fatalities:
Total fatalities:
34
Captain / Total flying hours:
5673
Circumstances:
Vayudoot F27 aircraft VT-DMC was operating scheduled flight VDT703 Silchar - Guwahati on 19-10-1988. There were 34 persons on board including 3 crew members. The aircraft took off from Silchar at around 0810LT from runway 06. The weather report at that time was visibility 3 km with rain. After takeoff, the aircraft gave estimate time to Silchar tower of its passing the Point Hotel at 0820LT and the estimated time of arrival at Guwahati was at 0850LT. At 0823LT the flight reported over Point Hotel at FL105 and thereafter the aircraft was in contact with Guwahati control when the flight was cleared to change over to Guwahati control tower. At 0839LT the aircraft reported ATC that they are passing through FL55 for 40 and will call over VOR for ILS let down at out bound. At 0846LT the aircraft commenced procedure turn. At 0847LT the aircraft reported ATC that they are not getting glide path. At 0848:15LT the aircraft reported turning inbound after completing procedure turn. At 0848:45LT the aircraft reported outer marker inbond. The aircraft lost contact with ATC at 0853:30LT. The aircraft was destroyed due impact with a hill and post impact fire at a distance of more than 10 nautical miles from Guwahati Airport. All persons on board received fatal injuries.
Probable cause:
An error on the part of the pilot-in-command in obeying the localiser bar on the outbound leg when it is supposed to be disobeyed and which has resulted in disorientation of the pilot resultant effect of which is total non-adherence of the ILS let down procedure at Guwahati viz. failure to monitor the middle and outer locators, allowing the aircraft to descend below 2750 feet without intercepting the localiser and glide slope. The wrong clearance by ATC in asking the aircraft to report outer marker inbound when Captain-in-command reported non-availability of the Glide slope has misled the captain and as such has contributed to the accident. The possibility of sabotage or the aircraft outliving its age has been ruled out. The pilot failed to follow approved procedures, directives, instructions, etc.

Crash of a Boeing 737-2A8 in Ahmedabad: 133 killed

Date & Time: Oct 19, 1988 at 0653 LT
Type of aircraft:
Operator:
Registration:
VT-EAH
Survivors:
Yes
Schedule:
Bombay - Ahmedabad
MSN:
20481
YOM:
1970
Flight number:
IC113
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
129
Pax fatalities:
Other fatalities:
Total fatalities:
133
Captain / Total flying hours:
5985
Aircraft flight hours:
42750
Aircraft flight cycles:
47520
Circumstances:
Indian Airlines B-737 aircraft VT-EAH was operating scheduled flight IC113 (Bombay - Ahmedabad sector) on 19-10-1988. There were 135 occupants on board including 6 crew members. Aircraft contacted Ahmedabad Approach Control at 0620LT. Ahmedabad weather as per Metar of 0540LT was passed to the aircraft and again at 0625LT (speci) of 0610LT was passed to the aircraft and then visibility has been reduced from 6 km to 3 km. Clearance to descend to FL150 was given at 0632LT and the aircraft was further cleared to FL55, 25 DME at 0636LT. At 0641LT, the aircraft was advised to report over Ahmedabad VOR and 'Speci' of 0640LT was also transmitted to the aircraft as per the same the winds were calm, visibility 2 km in haze and was 1010. QNH was correctly read back by the aircraft. The pilot decided to carry localiser-DME approach for runway 23 and reported overhead Ahmedabad. The aircraft went outbound and reported turning inbound. This was the last transmission from the aircraft and thereafter contact with the ATC was lost at 0650:53. The aircraft was found crashed at a distance of 2,540 meters from the beginning of runway 23 on the extended centre line of the runway in a paddy field at about 0653LT. Out of 135 persons on board, 133 received fatal injuries. The remaining two were seriously injured. The aircraft was destroyed due to post impact fire.
Probable cause:
The cause of the accident is attributed to error on part of the pilot-in-command as well as copilot due to non adherence to laid down procedures under poor visibility conditions. Both pilot and copilot failed to follow approved procedures, directives, instructions, etc. Weather was considered as a contributing factor.

Ground accident of a Fokker F27 Friendship 100 in Calcutta

Date & Time: Sep 23, 1988 at 1145 LT
Type of aircraft:
Operator:
Registration:
VT-DMB
Flight Phase:
Survivors:
Yes
Schedule:
Calcutta - Biratnagar
MSN:
10172
YOM:
1961
Flight number:
PF701
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
39
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
53680
Aircraft flight cycles:
51890
Circumstances:
While taxiing at Calcutta-Dum Dum in poor visibility, the aircraft collided with a catering truck. On impact, a part of the left wing was torn off and the aircraft came to rest. All 43 occupants were evacuated safely and the aircraft was damaged beyond repair. All three people on board the catering truck were seriously injured.
Probable cause:
It was determined that the driver of the catering truck failed to observe the ground markings and was unaware he was rolling on a taxiway. The lack of visibility was a contributory factor as the crew of the F27 was unable to see and avoid the truck.

Crash of a Dornier DO228-201 in Aurangabad

Date & Time: Sep 22, 1988 at 1758 LT
Type of aircraft:
Operator:
Registration:
VT-EJT
Survivors:
Yes
Schedule:
Nagpur – Aurangabad
MSN:
8064
YOM:
1986
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
18676
Circumstances:
While nearing Aurangabad, the weather was deteriorating. ATC Aurangabad kept the pilot apprised about the prevailing surface wind and rain. The pilot too had similar observations of adverse weather and deteriorated visibility. The commander sighted the runway quite late and the aircraft was descended very fast triggering the Ground Proximity Warning System and aural warning. After coming close to the runway the pilot attempted to open power on the engines. However, he found himself unable to move the power lever forward. The aircraft continued to sink fast and crashed over undershoot area of the runway 27. The aircraft sustained substantial damage. No person on board sustained serious injury. There was no fire.
Probable cause:
The cause of the accident has been attributed as the commander while landing during bad weather had descended at a very fast rate and subsequently could not arrest the sink rate while approaching close to the runway due to improper handling of engine controls. Non-availability of deteriorating visibility conditions to the flight crew at the time of landing is a contributory factor.

Crash of a Boeing 737-2A8 in New Delhi

Date & Time: Jun 19, 1988 at 1726 LT
Type of aircraft:
Operator:
Registration:
VT-EAI
Survivors:
Yes
Schedule:
Srinagar – Jammu – Chandigarh – New Delhi
MSN:
20482/272
YOM:
1970
Flight number:
IC422
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
128
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9000
Circumstances:
Indian Airlines flight IC422 was a domestic service from Srinagar to Delhi via Jammu and Chandigarh, India. The aircraft, a Boeing 737-200, landed gear up on runway 10 at Delhi-Indira Gandhi International Airport. The left engine then caught fire due to a fuel leak from ruptured fuel lines and a broken fuel control unit. The fire was quickly put out by fire services. All 134 occupants evacuated safely.
Probable cause:
The accident occurred because of commander's negligent flying contrary to laid down procedures and failure to ensure that the landing gears were down and locked before landing. The co-pilot's failure to bring to the notice of the commander the deviations from the laid down procedures and to verify and cross-check that the gears were down, was a contributory factor to the accident.

Crash of an Antonov AN-12B near Charbatia AFB: 17 killed

Date & Time: Mar 8, 1988
Type of aircraft:
Operator:
Registration:
L2174
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
MSN:
6 3 438 06
YOM:
1965
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
17
Circumstances:
After takeoff from Charbatia AFB, while in initial climb, the crew declared an emergency after an engine caught fire. After being cleared to return, the captain initiated a turn while the fire spread to the nacelle and the wing. The aircraft entered an uncontrolled descent and crashed in the district of Paikarapur. The aircraft and few houses were totally destroyed. All nine occupants as well as eight people on the ground were killed. 10 other people on the ground were injured.
Probable cause:
The exact cause of the engine fire could not be determined with certainty. However, it was reported that the fire extinguishing systems were inoperative.

Crash of a Britten-Norman BN-2A-21 Defender off Cochin

Date & Time: Dec 9, 1987
Type of aircraft:
Operator:
Registration:
IN132
Flight Phase:
Survivors:
Yes
Schedule:
Cochin - Cochin
MSN:
875
YOM:
1974
Location:
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 maritime patrol flight when an engine lost power in flight. The pilot ditched the aircraft few km off Cochin. All three occupants were evacuated safely while the aircraft sank and was lost.
Probable cause:
Loss of engine power for unknown reasons.

Crash of a Douglas DC-3C in Jaisalmer

Date & Time: Apr 13, 1987 at 0850 LT
Type of aircraft:
Operator:
Registration:
VT-DFM
Flight Phase:
Survivors:
Yes
Schedule:
Jaisalmer – Baroda
MSN:
20269
YOM:
1944
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
28
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
12500
Circumstances:
The aircraft was engaged in a charter flight on behalf of the Oil & Natural Gas Corporation. During the takeoff roll from Jaisalmer Airfield, the commander experienced yaw to the left which could not be corrected by him. When the aircraft was about to leave the paved surface, the commander prematurely attempted liftoff. The aircraft momentarily became airborne and unable to sustain flight due to low flying speed impacted the kutcha side strip on the left side of the runway. The aircraft got destroyed due to impact force and post impact fire. During the process of evacuation 19 passengers and four crew members received minor injuries.
Probable cause:
The cause of the accident has been attributed to commander attempting takeoff after experiencing uncommanded and uncontrollable yaw to the left during takeoff roll and executed premature liftoff to avoid aircraft rolling onto kutcha surface resulting in the aircraft to crash onto the ground. Loss of directional control was probably due to deflection of left wheel which was a contributory factor to the accident.
Final Report:

Crash of a Douglas DC-3C in Jaisalmer

Date & Time: Apr 13, 1987 at 0850 LT
Type of aircraft:
Operator:
Registration:
VT-DFM
Flight Phase:
Survivors:
Yes
Schedule:
Jaisalmer – Baroda
MSN:
20269
YOM:
1944
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
28
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
12500
Circumstances:
During the takeoff roll from Jaisalmer Airfield, the commander experienced yaw to the left which could not be corrected by him. When the aircraft was about to leave the paved surface, the commander prematurely attempted liftoff. The aircraft momentarily became airborne and unable to sustain flight due to low flying speed impacted the kutcha side strip on the left side of the runway. The aircraft got destroyed due to impact force and post impact fire. During the process of evacuation 19 passengers and four crew members received minor injuries.
Probable cause:
The cause of the accident has been attributed to commander attempting takeoff after experiencing uncommanded and uncontrollable yaw to the left during takeoff roll and executed premature liftoff to avoid aircraft rolling onto kutcha surface resulting in the aircraft to crash onto the ground. Loss of directional control was probably due to deflection of left wheel which was a contributory factor to the accident.
Final Report: