India | Bureau of Aircraft Accidents Archives

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:

Dornier DO228

Operator:

Registration:

VT-EJT

Flight Phase:

Landing (descent or approach)

Flight Type:

Scheduled Revenue Flight

Survivors:

Yes

Site:

Airport (less than 10 km from airport)

Schedule:

Nagpur – Aurangabad

MSN:

8064

YOM:

1986

Location:

Country:

Region:

Crew on board:

Crew fatalities:

Pax on board:

Pax fatalities:

Other fatalities:

Total fatalities:

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:

Boeing 737-200

Operator:

Registration:

VT-EAI

Flight Phase:

Landing (descent or approach)

Flight Type:

Scheduled Revenue Flight

Survivors:

Yes

Site:

Airport (less than 10 km from airport)

Schedule:

Srinagar – Jammu – Chandigarh – New Delhi

MSN:

20482/272

YOM:

1970

Flight number:

IC422

Location:

New Delhi-Indira Gandhi

National Capital Territory of Delhi

Country:

India

Region:

Asia

Crew on board:

Crew fatalities:

Pax on board:

128

Pax fatalities:

Other fatalities:

Total fatalities:

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:

Antonov AN-12

Operator:

Registration:

L2174

Flight Phase:

Flight Type:

Survivors:

Site:

MSN:

6 3 438 06

YOM:

1965

Location:

Charbatia AFB (Cuttack)

Odisha (Orissa)

Country:

India

Region:

Asia

Crew on board:

Crew fatalities:

Pax on board:

Pax fatalities:

Other fatalities:

Total fatalities:

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:

Britten-Norman Islander

Operator:

Registration:

IN132

Flight Phase:

Flight

Flight Type:

Survey / Patrol / Reconnaissance

Survivors:

Yes

Site:

Lake, Sea, Ocean, River

Schedule:

Cochin - Cochin

MSN:

875

YOM:

1974

Location:

Country:

Region:

Crew on board:

Crew fatalities:

Pax on board:

Pax fatalities:

Other fatalities:

Total fatalities:

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:

Douglas DC-3

Operator:

Registration:

VT-DFM

Flight Phase:

Takeoff (climb)

Flight Type:

Charter/Taxi (Non Scheduled Revenue Flight)

Survivors:

Yes

Site:

Airport (less than 10 km from airport)

Schedule:

Jaisalmer – Baroda

MSN:

20269

YOM:

1944

Location:

Country:

Region:

Crew on board:

Crew fatalities:

Pax on board:

Pax fatalities:

Other fatalities:

Total fatalities:

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:

Douglas DC-3

Operator:

Registration:

VT-DFM

Flight Phase:

Takeoff (climb)

Flight Type:

Charter/Taxi (Non Scheduled Revenue Flight)

Survivors:

Yes

Site:

Airport (less than 10 km from airport)

Schedule:

Jaisalmer – Baroda

MSN:

20269

YOM:

1944

Location:

Country:

Region:

Crew on board:

Crew fatalities:

Pax on board:

Pax fatalities:

Other fatalities:

Total fatalities:

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:

Final Report:

Crash of an Airbus A300B2-1C in Madras

Date & Time: Sep 29, 1986 at 0719 LT

Type of aircraft:

Airbus A300

Operator:

Registration:

VT-ELV

Flight Phase:

Takeoff (climb)

Flight Type:

Scheduled Revenue Flight

Survivors:

Yes

Site:

Airport (less than 10 km from airport)

Schedule:

Madras - Bombay

MSN:

YOM:

1976

Flight number:

IC571

Location:

Country:

Region:

Crew on board:

Crew fatalities:

Pax on board:

185

Pax fatalities:

Other fatalities:

Total fatalities:

Captain / Total flying hours:

20865

Circumstances:

During taxiing for takeoff, the commander gave controls to copilot for takeoff. During takeoff roll, the commander and the copilot sighted a large bird towards the right hand side and the commander told the copilot to continue with takeoff. The copilot reportedly saw another large bird on the runway centreline when the aircraft speed was around 150 knots. The copilot rotated the aircraft and when the aircraft attained 5 to 8° nose up attitude, a loud noise was heard from the right side followed by severe vibration. The commande took over the controls from the copilot at this stage and initiated action to abort the takeoff. Reverse thrust and wheel brakes were applied but the aircraft could not be stopped on the runway and rolled over to kutcha ground. There was no fire but the aircraft was damaged beyond repair. All 196 occupants were evacuated, among them 14 were slightly injured.

Probable cause:

Wrong decision of the commander to reject the take-off after the aircraft had been rotated for a lift-off, following a loud sound and severe vibrations from right engine due to bird hit.