Region
Asia

Crash of a Hindustan Aeronautics HAL-748-219-2 in Dubagunta: 22 killed

Date & Time: Dec 24, 1996 at 1540 LT
Type of aircraft:
Hindustan Aeronautics HAL-748
Operator:
Registration:
H1032
Flight Phase:
Flight
Flight Type:
Military
Survivors:
No
Site:
Plain, Valley
Schedule:
Tambaram – Hyderabad
MSN:
528
YOM:
1971
Location:
Dubagunta
Andhra Pradesh
Country:
India
Region:
Asia
Crew on board:
5
Crew fatalities:
Pax on board:
17
Pax fatalities:
Other fatalities:
Total fatalities:
22
Circumstances:
En route from Tambaram to Hyderabad, while in cruising altitude, the captain declared an emergency and informed ATC about the failure of an engine. Shortly later, the aircraft entered an uncontrolled descent and crashed near Dubagunta, killing all 22 occupants.
Probable cause:
It was determined that an engine failed in flight and later detached, causing the separation of a wing. The failure of the high compressor disk was the consequence of fatigue cracks that were not detected during the last maintenance inspection.

Crash of an Ilyushin II-76TD in Charkhi Dadri: 37 killed

Date & Time: Nov 12, 1996 at 1840 LT
Type of aircraft:
Ilyushin II-76
Operator:
Registration:
UN-76435
Flight Phase:
Flight
Flight Type:
Scheduled Revenue Flight
Survivors:
No
Site:
Plain, Valley
Schedule:
Shymkent - New Delhi
MSN:
10234 13428
YOM:
1992
Flight number:
KZA1907
Location:
Charkhi Dadri
Haryana
Country:
India
Region:
Asia
Crew on board:
10
Crew fatalities:
Pax on board:
27
Pax fatalities:
Other fatalities:
Total fatalities:
37
Captain / Total flying hours:
9229
Captain / Total hours on type:
1488.00
Copilot / Total flying hours:
6822
Copilot / Total hours on type:
409
Aircraft flight hours:
2643
Circumstances:
The Ilyushin II-76TD departed Shymkent Airport on a regular schedule service (flight KZA1907) to New Delhi-Indira Gandhi, carrying 27 passengers and 10 crew members. Following an uneventful flight, the crew was cleared to start the descent to New Delhi via route G452 and was instructed to maintain FL150. At 1833LT, a Boeing 747-168B operated by Saudi Arabian Airlines (Saudia) departed New Delhi-Indira Gandhi Airport on a flight to Jeddah (flight SV763) with an intermediate stop in Dhahran, carrying 289 passengers and 23 crew members. After takeoff, its crew was instructed to climb to FL140 via the same route G452. For unknown reasons, the Kazair crew continued the descent below FL150 until both aircraft faced each other and collided at 1840LT at FL140, seven minutes after the B747 takeoff. After the collision, both aircraft entered an uncontrolled descent and crashed in an open field located about 3 km Charkhi Dadri, some 80 km west of New Delhi-Indira Gandhi Airport. Both aircraft were destroyed by impact forces and a post crash fire and all 349 occupants in both aircraft were killed.
Probable cause:
It was determined that the collision was the consequence of the failure of the Kazair crew to follow the assigned altitude of 15,000 feet while approaching New Delhi. The crew of the Kazair II-76 was instructed by ATC to continue the descent to Indira Gandhi Airport via the same route G452 but at an altitude of 15,000 feet (14,000 feet for the Saudia B747). For unknown reasons, the Kazair crew continued the descent below FL150 without clearance until both aircraft faced each other and collided. During the minutes preceding the accident, both Kazair and Saudia crew have been informed by ATC about other traffic.
Final Report:

Crash of a Boeing 747-168B in Charkhi Dadri: 312 killed

Date & Time: Nov 12, 1996 at 1840 LT
Type of aircraft:
Boeing 747-100
Operator:
Registration:
HZ-AIH
Flight Phase:
Flight
Flight Type:
Scheduled Revenue Flight
Survivors:
No
Site:
Plain, Valley
Schedule:
New Delhi - Dhahran - Jeddah
MSN:
22748
YOM:
1982
Flight number:
SV763
Location:
Charkhi Dadri
Haryana
Country:
India
Region:
Asia
Crew on board:
23
Crew fatalities:
Pax on board:
289
Pax fatalities:
Other fatalities:
Total fatalities:
312
Captain / Total flying hours:
9837
Captain / Total hours on type:
104.00
Copilot / Total flying hours:
7779
Copilot / Total hours on type:
1952
Aircraft flight hours:
40035
Aircraft flight cycles:
14927
Circumstances:
The aircraft departed New Delhi-Indira Gandhi Airport at 1833LT on a flight to Jeddah with an intermediate stop in Dhahran, carrying 289 passengers and 23 crew members. After takeoff, the crew was instructed to climb to FL140 via route G452. Seven minutes after takeoff, while cruising at an altitude of 14,000 feet, the aircraft collided with a Kazakhstan Airlines (Kazair) Ilyushin II-76TD that was descending to New Delhi Airport. Registered UN-76435, it was completing flight KZA1907 from Shymkent with 27 passengers and 10 crew members on board. After the collision, both aircraft entered an uncontrolled descent and crashed in an open field located about 3 km Charkhi Dadri, some 80 km west of New Delhi-Indira Gandhi Airport. Both aircraft were destroyed by impact forces and a post crash fire and all 349 occupants in both aircraft were killed.
Probable cause:
It was determined that the collision was the consequence of the failure of the Kazair crew to follow the assigned altitude of 15,000 feet while approaching New Delhi. The crew of the Kazair II-76 was instructed by ATC to continue the descent to Indira Gandhi Airport via the same route G452 but at an altitude of 15,000 feet (14,000 feet for the Saudia B747). For unknown reasons, the Kazair crew continued the descent below FL150 without clearance until both aircraft faced each other and collided. During the minutes preceding the accident, both Kazair and Saudia crew have been informed by ATC about other traffic.
Final Report:

Crash of a Let L-410UVP-E9D in Kulu: 9 killed

Date & Time: Jul 11, 1996 at 0855 LT
Type of aircraft:
Let L-410
Operator:
Registration:
VT-ETC
Flight Phase:
Landing (descent or approach)
Flight Type:
Scheduled Revenue Flight
Survivors:
No
Site:
Airport (less than 10 km from airport)
Schedule:
New Delhi – Shimla – Kulu
MSN:
94 27 03
YOM:
1994
Location:
Kulu-Bhuntar
Himachal Pradesh
Country:
India
Region:
Asia
Crew on board:
3
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
9
Captain / Total flying hours:
8912
Captain / Total hours on type:
1705.00
Copilot / Total flying hours:
1789
Copilot / Total hours on type:
828
Aircraft flight hours:
3297
Aircraft flight cycles:
2556
Circumstances:
Following an uneventful flight from Shimla, the crew started the descent to Kulu-Bhuntar Airport in poor visibility due to thick fog. On approach, the aircraft struck trees and crashed in a wooded area located on Mt Bandi. The aircraft was destroyed and all nine occupants were killed.
Probable cause:
The was due to a complete lack of safety awareness, proper supervision and operational control in the organisation. The non compliance of safety requirements on part of the operator was a contributing factor.
Final Report:

Crash of a Let L-410UVP-E9D in Kanpur

Date & Time: May 18, 1996 at 0738 LT
Type of aircraft:
Let L-410
Operator:
Registration:
VT-ETB
Flight Phase:
Landing (descent or approach)
Flight Type:
Scheduled Revenue Flight
Survivors:
Yes
Site:
Airport (less than 10 km from airport)
Schedule:
New Delhi - Kanpur
MSN:
92 27 02
YOM:
1992
Location:
Kanpur
Uttar Pradesh
Country:
India
Region:
Asia
Crew on board:
3
Crew fatalities:
Pax on board:
16
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8237
Circumstances:
Archana Airways L-410 aircraft VT-ETB was operating a scheduled flight from Delhi to Kanpur civil aerodrome on 18.05.96. The flight from Delhi to Kanpur was uneventful. The aircraft took-off from Delhi with 19 persons including three flight crew. During landing, the aircraft touched down late and could not be stopped within the available runway length and went beyond the runway. The aircraft hit the boundary wall of the airport and came to halt. The aircraft sustained major damages. There was no fire and no injury to persons on board the aircraft.
Probable cause:
The accident was caused due to late touchdown at higher aircraft touchdown speed as a result of which the aircraft overshot the runway and suffered damage by impact with boundary wall.
The following contributing factors were reported:
- Wrong selection of runway,
- Overloading of aircraft,
- Non-deployment of spoilers,
- Lower visibility conditions than the required,
- Disregard of procedures, regulations and instructions on part of the pilot.
Final Report:

Crash of a Boeing 737-2A8 in New Delhi

Date & Time: Dec 2, 1995 at 1253 LT
Type of aircraft:
Boeing 737-200
Operator:
Registration:
VT-ECS
Flight Phase:
Landing (descent or approach)
Flight Type:
Scheduled Revenue Flight
Survivors:
Yes
Site:
Airport (less than 10 km from airport)
Schedule:
Bombay – Jaipur – New Delhi
MSN:
20963
YOM:
1974
Flight number:
IC492
Location:
New Delhi-Indira Gandhi
National Capital Territory of Delhi
Country:
India
Region:
Asia
Crew on board:
6
Crew fatalities:
Pax on board:
102
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6088
Circumstances:
Following a wrong approach configuration, the aircraft landed too far down the runway, about 600 metres from the runway end. Unable to stop within the remaining distance, the aircraft overran, struck a concrete wall (45 cm high) and came to rest 450 metres further. All 108 occupants were evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
The accident was the consequence of the combination of the following factors:
- The injudicious and imprudent decision of the Pilot-in-Command to hastily complete the flight in the inadequate time available before the notified closure of Delhi airport for a VVIP flight,
- The dangerously unstabilised approach made by the Pilot-in-Command, primarily due to his failure to decelerate the aircraft in time,
- The failure of the First Officer to call out significant deviations from the stipulated approach parameters,
- The failure of the Pilot-in-Command to carry out a missed approach in spite of his approach being grossly unstabilised,
- The inadvertent omission of the Pilot-in-Command to arm the speed brake before landing,
- Touch-down of the aircraft at excessive speed and too far down the runway,
- Failure of the First Officer and Pilot-in-Command to monitor the automatic deployment of the speed brake, and failure of the Pilot-in-Command to deploy it manually,
- Impact of the aircraft with an 18-inch high cement-concrete cable duct in the kutcha ground beyond the over-run area,
- The pilot disregard of procedures, regulations and instructions.
Final Report:

Crash of a Fokker F27 Friendship 500RF in Baroda

Date & Time: Jul 1, 1995 at 0840 LT
Type of aircraft:
Fokker F27 Friendship
Operator:
Registration:
VT-EWE
Flight Phase:
Landing (descent or approach)
Flight Type:
Training
Survivors:
Yes
Site:
Airport (less than 10 km from airport)
Schedule:
Baroda - Baroda
MSN:
10605
YOM:
1980
Location:
Baroda (Vadodara)
Gujarat
Country:
India
Region:
Asia
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9360
Circumstances:
The aircraft was engaged in a training flight at Baroda airport. It was under the command of an examiner pilot with the trainee pilot on right hand seat. The first touch and go exercise was uneventful. During the second exercise, immediately on touchdown the left main landing gear failed at its shock strut outer cylinder and the inner cylinder with the main wheel assembly attached to it got liberated. The aircraft continued moving forward with the remaining portion of left shock strut contacting the runway followed by the left engine propellers and fuselage bottom and finally came to rest on the runway left side strip. There was no fire and no injury to persons on board the aircraft.
Probable cause:
The accident occurred during aircraft touchdown due to liberation of the sliding piston along with the wheels of the left main landing gear as a result of failure of the locking arrangement on the piston top end. Non-compliance by the operator of the Service Bulletin issued by the Manufacturer and Mandatory Modifications issued by the DGCA regarding piston-adapter and dowel pin lock fitment, is the Contributory Factor in the accident.
Final Report:

Crash of a Beechcraft 200 Super King Air near Sundar Nagar: 11 killed

Date & Time: Jul 9, 1994 at 0905 LT
Type of aircraft:
Beechcraft 200 Super King Air
Operator:
Registration:
VT-EUJ
Flight Phase:
Flight
Flight Type:
Government
Survivors:
No
Site:
Mountains
Schedule:
Chandigarh – Kulu-Bhuntar
MSN:
BB-1456
YOM:
1993
Location:
Sundar Nagar
Himachal Pradesh
Country:
India
Region:
Asia
Crew on board:
3
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
11
Captain / Total flying hours:
7503
Captain / Total hours on type:
113.00
Copilot / Total flying hours:
6412
Copilot / Total hours on type:
46
Aircraft flight hours:
153
Aircraft flight cycles:
186
Circumstances:
The twin engine aircraft departed Chandigarh Airport at 0850LT on a flight to Kulu-Bhuntar, carrying eight passengers and three crew members, among them Surendra Nath, Governor of Punjab and Himachal Pradesh along with his family members. While in cruising altitude, the crew encountered limited visibility due to cumulus when the aircraft struck trees and rocks and crashed on the slope of a mountain located in the Kamrunag Mountain Range, about 18,5 km southeast of Sundar Nagar, some 50 km south of Kulu-Bhuntar Airport. The aircraft was destroyed and all 11 occupants were killed.
Probable cause:
The accident was caused due to serious errors on the part of the flight crew by not strictly adhering to the VFR conditions for flight to Bhuntar Airfield. As a result, the aircraft after encountering cumulus clouds enroute, deviated from the pre-determined route and collided with the hilltop covered with clouds.
The contributed factors to the accident were:
- Existence of bad weather enroute with cumulus clouds in layers covering the hill tops;
- Pilots not conversant with the topography of the mountains in the region;
- Failure on the part of the flight crew not to refer and follow the maps of the region;
- Mental pressure on the pilot-in-command to complete the flight in time with a view to meet the subsequent flight commitments;
- Failure on the part of the copilot to bring out flight deviations to the notice of the commander,
- Disregard of procedures, regulations and instructions on part of the pilot,
- Operational decision.
Final Report:

Crash of a Boeing 737-2R4C in New Delhi: 5 killed

Date & Time: Mar 8, 1994 at 1454 LT
Type of aircraft:
Boeing 737-200
Operator:
Registration:
VT-SIA
Flight Phase:
Takeoff (climb)
Flight Type:
Training
Survivors:
No
Site:
Airport (less than 10 km from airport)
Schedule:
New Delhi - New Delhi
MSN:
21763
YOM:
1979
Location:
New Delhi-Indira Gandhi
National Capital Territory of Delhi
Country:
India
Region:
Asia
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
7263
Captain / Total hours on type:
2821.00
Copilot / Total flying hours:
556
Copilot / Total hours on type:
166
Aircraft flight hours:
25947
Aircraft flight cycles:
2861
Circumstances:
The aircraft was engaged in a local training flight at New Delhi-Indira Gandhi Airport, carrying one instructor and three trainee pilots. Five circuits and landings were completed uneventfully and during the sixth touch-and-go exercice, after take off from runway 28, the aircraft took a left turn and crashed on the international apron. The aircraft collided with an Aeroflot Ilyushin II-86 registered RA-86119 that was parked on the apron, bay n°45. Both aircraft were destroyed by fire. All four crew members on board the Boeing 737 were killed as well as four people on board the II-86 and one on the ground.
Probable cause:
Loss of control after rotation due to application of wrong rudder by trainee pilot during engine failure exercice. The instructor did not guard/block the rudder control and give clear commands as instructor so as to obviate the application of wrong rudder control by the trainee pilot.
Final Report:

Crash of an Ilyushin II-86 in New Delhi: 4 killed

Date & Time: Mar 8, 1994 at 1200 LT
Type of aircraft:
Ilyushin II-86
Operator:
Registration:
RA-86119
Flight Phase:
Parking
Flight Type:
Scheduled Revenue Flight
Survivors:
Yes
Site:
Airport (less than 10 km from airport)
Schedule:
New Delhi - Tashkent - Moscow
MSN:
51483209087
YOM:
1985
Location:
New Delhi-Indira Gandhi
National Capital Territory of Delhi
Country:
India
Region:
Asia
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
An Air Sahara (Sahara Airlines) boeing 737-2R4C registered VT-SIA was engaged in a local training flight at New Delhi-Indira Gandhi Airport, carrying one instructor and three trainee pilots. Five circuits and landings were completed uneventfully and during the sixth touch-and-go exercice, after take off from runway 28, the aircraft took a left turn and crashed on the international apron. The aircraft collided with an Aeroflot Ilyushin II-86 registered RA-86119 that was parked on the apron, bay n°45. Both aircraft were destroyed by fire. All four crew members on board the Boeing 737 were killed as well as four people on board the II-86 and one on the ground.
Probable cause:
Loss of control after rotation due to application of wrong rudder by trainee pilot during engine failure exercice. The instructor did not guard/block the rudder control and give clear commands as instructor so as to obviate the application of wrong rudder control by the trainee pilot.
Subscribe to India