Crash of an Ilyushin II-38 in Dabolim: 11 killed

Date & Time: Oct 1, 2002 at 0945 LT
Type of aircraft:
Operator:
Registration:
IN304
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Dabolim - Dabolim
MSN:
0800 106 10
YOM:
1970
Location:
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
11
Circumstances:
Two Indian Navy Ilyushin II-38 were engaged in a demonstration flight at Dabolim Airport, celebrating the 25th anniversary of the 315th Squadron based at Dabolim. While approaching the airfield in formation at a height of about 100 metres, both aircraft registered IN302 and IN304 collided and crashed. All 12 occupants were killed (five on board IN302 and seven on board IN304) as well as four people on the ground.

Crash of an Ilyushin II-38 in Dabolim: 5 killed

Date & Time: Oct 1, 2002 at 0945 LT
Type of aircraft:
Operator:
Registration:
IN302
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Dabolim - Dabolim
MSN:
0810 110 09
YOM:
1971
Location:
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
Two Indian Navy Ilyushin II-38 were engaged in a demonstration flight at Dabolim Airport, celebrating the 25th anniversary of the 315th Squadron based at Dabolim. While approaching the airfield in formation at a height of about 100 metres, both aircraft registered IN302 and IN304 collided and crashed. All 12 occupants were killed (five on board IN302 and seven on board IN304) as well as four people on the ground.

Crash of a Dornier DO228-201 in Jaipur

Date & Time: Jun 9, 2002
Type of aircraft:
Operator:
Registration:
VT-EJN
Flight Type:
Survivors:
Yes
Schedule:
Jaipur - Jaipur
MSN:
8060
YOM:
1986
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a local training flight at Jaipur-Sanganer Airport. After touchdown, the twin engine aircraft skidded on runway, veered off runway and came to rest. Both pilots escaped uninjured while the aircraft was damaged beyond repair.

Ground accident of an Airbus A300B2-101 in New Delhi

Date & Time: Mar 8, 2002 at 0315 LT
Type of aircraft:
Operator:
Registration:
VT-EFW
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
111
YOM:
1980
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
A group of five technicians/engineers of the company was preparing the aircraft to be transferred to a hangar for maintenance. After engine startup, the power was reduced to idle after someone inadvertently pulled out the circuit breaker. The aircraft jumped the chocks and started to roll. Since the engine's power was in idle, the brakes and the nosewheel steering system were inoperative. The crew elected to reduce power on the left engine but mistakenly increased the power on the right engine by 90%. This caused the aircraft to rotate 80° when control was lost. The airplane rolled through a perimeter wall, causing the nose gear to collapse. All five occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Beechcraft C90 King Air near Mainpuri: 8 killed

Date & Time: Sep 30, 2001 at 1331 LT
Type of aircraft:
Registration:
VT-EFF
Flight Phase:
Survivors:
No
Schedule:
New Delhi - Kanpur
MSN:
LJ-705
YOM:
1977
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
8
Captain / Total flying hours:
1596
Captain / Total hours on type:
894.00
Copilot / Total flying hours:
271
Copilot / Total hours on type:
19
Aircraft flight hours:
8083
Aircraft flight cycles:
7008
Circumstances:
En route from New Delhi to Kanpur, the crew reported over Aligarh. Short of next reporting point Kadas, the aircraft was about 10 miles right of track for which the permission was obtained and the pilot requested for a direct routing to Kanpur. About 10 minutes later, at an altitude of 14,000 feet, while cruising in bad weather conditions, the twin engine aircraft entered an uncontrolled descent, partially disintegrated in the air and eventually crashed in an open field near Mainpuri. All eight occupants were killed.
Crew:
Vivek Kumar Gupta,
Ritu Malik.
Passengers:
Mr. Madhav Rao Scindia,
Mr. Rupinder Singh,
Mr. Ranjan Jha,
Mr. Gopal Singh Bisht,
Mrs. Anu Sharma,
Mr. Sanjiv Sinha.
Probable cause:
While in cruising altitude, the crew encountered severe updrafts while flying in thunderstorm activity. Following a possible abrupt and abnormal manoeuvre, the crew lost control of the airplane that entered a spiral dive, resulting in an in-flight break up due to aerodynamic overload, leading to a total loss of control followed with a heavy impact with the ground.
Final Report:

Crash of a Beechcraft B200C Super King near Kulu-Bhuntar: 5 killed

Date & Time: Jul 29, 2000 at 1332 LT
Registration:
VT-EIE
Flight Type:
Survivors:
No
Site:
Schedule:
New Delhi – Kulu-Bhuntar
MSN:
BL-63
YOM:
1983
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
8340
Captain / Total hours on type:
776.00
Copilot / Total flying hours:
526
Aircraft flight hours:
6243
Aircraft flight cycles:
5646
Circumstances:
The twin engine aircraft departed New Delhi-Indira Gandhi Airport on an ambulance flight to Kulu-Bhuntar, carrying three doctors and two pilots. While descending to Kulu-Bhuntar Airport in IMC conditions, the crew failed to realize his altitude was insufficient when the aircraft struck the slope of a mountain located 20 km from the destination airport. The aircraft was destroyed and all five occupants were killed.
Probable cause:
The pilot descended below minimum sector altitude in Instrument Meteorological Condition in hilly area.
Contributing factors were:
1. ATC Chandigarh contributed to the accident by permitting IFR flight to descend below minimum sector altitude.
2. Inadequate Supervision, Lack of Safety culture and poor pre-flight planning. Factor: Pilot: Non-adherence to standard operating procedure.
Final Report:

Crash of a Boeing 737-2A8 in Patna: 60 killed

Date & Time: Jul 17, 2000 at 0734 LT
Type of aircraft:
Operator:
Registration:
VT-EGD
Survivors:
Yes
Site:
Schedule:
Calcutta – Patna – Lucknow – New Delhi
MSN:
22280
YOM:
1980
Flight number:
CD7412
Location:
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
52
Pax fatalities:
Other fatalities:
Total fatalities:
60
Captain / Total flying hours:
4361
Captain / Total hours on type:
1778.00
Copilot / Total flying hours:
4085
Copilot / Total hours on type:
3605
Aircraft flight hours:
44087
Aircraft flight cycles:
51278
Circumstances:
Alliance Air Flight No. CD-7412 departed Netaji Subhash Chandra Bose International Airport, Kolkata at 0651 hrs. on 17th July, 2000 bound for Patna-Lucknow-Delhi. After normal departure from Runway 01R, the aircraft climbed to FL260 on track to Patna via route W52. The aircraft was under the control of Kolkata Radar from 0652 hrs. to 0659 hrs. It changed over to Kolkata Area Control Centre. The aircraft reported position SAREK at FL 260 at 0712 hrs. and changed over to Patna Control with information that there was no reported traffic for descent. The aircraft contacted Patna ATC at 0713 hrs. and gave it’s ETA at Patna as 0736 hrs. Patna ATC cleared the aircraft to PPT VOR ILS/DME ARC Approach for R/W 25. The ATC Officer communicated that Patna METAR originated at 0650 hrs. stated “Wind calm, Visibility 4000 metres, Weather Haze, Clouds Broken 25000 feet, temp 29ºC, Dew Point 27º, QNH 996 hPa, No Sig”. The aircraft was cleared to descend to 7500’ and report 25 DME from PPT VOR. The aircraft reported 25 DME at 0726 hrs. The aircraft then descended to 4000’ on QNH 996 hPa and was asked to report 13 DME for ILS/DME ARC Approach R/W 25. The aircraft reported commencing the ARC at 0728 hrs. The aircraft reported crossing lead radial 080 at 0731 hrs. and coming on to the Localizer. The aircraft was then asked to descend to 1700’ on QNH 997 hPa with instructions to call established on Localizer. The aircraft informed Patna ATC at 0732 hrs. that it would like to do a 360º turn due to being high on approach. Patna ATC sought confirmation from the aircraft whether it had the airfield in sight and on receiving an affirmative reply, asked the aircraft to report on finals for R/W 25 after carrying out a 360º turn. This was acknowledged by the aircraft at 0732 hrs. This was the last communication from the aircraft. Immediately thereafter, the aircraft was spotted by the Air Traffic Controller in normal descent aligned with the R/W 25. It, however, appeared to be high on approach. The aircraft then turned steeply to the left losing height all of a sudden and disappeared from sight behind a row of trees. The Air Traffic Controller observed a huge column of smoke rising from the Gardani Bagh area outside the airfield perimeter and initiated crash action. All six crew members and 49 passengers were killed as well as five people on the ground. Three passengers escaped with serious injuries.
Probable cause:
The cause of the accident was loss of control of the aircraft due Human Error (air crew). The crew had not followed the correct approach procedure, which resulted in the aircraft being high on approach. They had kept the engines at idle thrust and allowed the air speed to reduce to a lower than normally permissible value on approach. They then maneuvered the aircraft with high pitch attitude and executed rapid roll reversals. This resulted in actuation of the stick shaker stall warning indicating an approaching stall. At this stage, the crew initiated a Go Around procedure instead of Approach to Stall Recovery procedure resulting in an actual stall of the aircraft, loss of control and subsequent impact with the ground.
Final Report:

Crash of an Antonov AN-32 in Bangalore

Date & Time: Feb 23, 2000
Type of aircraft:
Operator:
Registration:
K2690
Flight Type:
Survivors:
Yes
Site:
MSN:
03 05
YOM:
1984
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft was approaching Bangalore-Hindustan Airport when it crashed in unknown circumstances in the district of Vijayanagar, about 13 km short of runway 09 threshold. There were no casualties.

Crash of a Breguet Bre.1150 Atlantic in the Rann of Kutch: 16 killed

Date & Time: Aug 10, 1999
Type of aircraft:
Operator:
Registration:
91
Flight Phase:
Survivors:
No
Schedule:
Mehran NAS - Mehran NAS
MSN:
33
Country:
Region:
Crew on board:
16
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
16
Circumstances:
The aircraft departed Mehran NAS in Karachi on a survey flight over Kashmir and the Pakistan/India border. On board were 16 crew members, six officers and 10 marines attached to the Pakistan Navy Corps based at Mehran NAS, Karachi. In flight, the aircraft was shot down by an air-air missile shot by the pilot of an Indian MiG-21 fighter. The Breguet entered a dive and crashed in the Rann of Kutch, Indian territory. The aircraft disintegrated on impact and all 16 occupants were killed.
Probable cause:
The aircraft was shot down by an air-air missile from an Indian MiG-21 fighter after it entered illegally the Indian airspace.

Crash of an Antonov AN-32 in New Delhi: 21 killed

Date & Time: Mar 7, 1999 at 0822 LT
Type of aircraft:
Operator:
Registration:
K2673
Flight Type:
Survivors:
No
Site:
Schedule:
Gwalior – New Delhi – Pokhran
MSN:
108
YOM:
1984
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
14
Pax fatalities:
Other fatalities:
Total fatalities:
21
Circumstances:
While descending to New Delhi-Indira Gandhi Airport runway 10, the crew encountered poor visibility due to thick fog and requested ATC assistance. On short final, the crew failed to realize his altitude was insufficient when the aircraft struck successively a concrete water tank and power cables then crashed in the Pappankalan district, about 2,4 km short of runway. The aircraft and a building were destroyed. All 18 occupants were killed as well as three people on the ground.
Probable cause:
The crew was completing the final approach below the minimum safe altitude in reduced visibility due to thick fog.