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

Date & Time: Nov 12, 1996 at 1840 LT
Type of aircraft:
Operator:
Registration:
UN-76435
Flight Phase:
Survivors:
No
Schedule:
Shymkent - New Delhi
MSN:
10234 13428
YOM:
1992
Flight number:
KZA1907
Country:
Region:
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:
Operator:
Registration:
HZ-AIH
Flight Phase:
Survivors:
No
Schedule:
New Delhi - Dhahran - Jeddah
MSN:
22748
YOM:
1982
Flight number:
SV763
Country:
Region:
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 Kanpur

Date & Time: May 18, 1996 at 0738 LT
Type of aircraft:
Operator:
Registration:
VT-ETB
Survivors:
Yes
Schedule:
New Delhi - Kanpur
MSN:
92 27 02
YOM:
1992
Country:
Region:
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:
Operator:
Registration:
VT-ECS
Survivors:
Yes
Schedule:
Bombay – Jaipur – New Delhi
MSN:
20963
YOM:
1974
Flight number:
IC492
Country:
Region:
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 Boeing 737-2R4C in New Delhi: 5 killed

Date & Time: Mar 8, 1994 at 1454 LT
Type of aircraft:
Operator:
Registration:
VT-SIA
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
New Delhi - New Delhi
MSN:
21763
YOM:
1979
Country:
Region:
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:
Operator:
Registration:
RA-86119
Flight Phase:
Survivors:
Yes
Schedule:
New Delhi - Tashkent - Moscow
MSN:
51483209087
YOM:
1985
Country:
Region:
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.

Crash of a Tupolev TU-154B-2 in New Delhi

Date & Time: Jan 9, 1993 at 0408 LT
Type of aircraft:
Operator:
Registration:
85533
Survivors:
Yes
Schedule:
Hyderabad - New Delhi
MSN:
82A533
YOM:
1982
Flight number:
IC840
Country:
Region:
Crew on board:
13
Crew fatalities:
Pax on board:
152
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
10245
Circumstances:
On 9th January, 1993 TU-154 aircraft No. 85533 wet leased by Indian Airlines from Uzbekistan Airways was operating flight IC-840 from Hyderabad to Delhi. The aircraft was being flown by Uzbeki operating crew and there were 165 persons on board including the crew. The aircraft touched down slightly outside the right edge of the runway, collided with some fixed installations on the ground, got airborne once again and finally touched down on kutcha ground on the right side of the runway. At this stage the right wing and the tail of the aircraft broke away and it came to rest in an inverted position. During the process, the aircraft caught fire and was destroyed. Most occupants of the aircraft escaped unhurt. Six persons suffered either limb fracture or other serious injuries while 45 persons suffered injuries of a minor nature.
Probable cause:
The probable cause of accident has been attributed to :
- The failure of the Pilot-in-Command to divert to Ahmedabad when he was informed that the RVR on runway 28 was below the minima applicable to his flight.
- The switching on of landing lights, on the instruction of the second Captain, at a height of only about ten metres, resulting in the loss of all visual references due to the blinding effect of
light reflections from fog.
- The failure of captain to carry out a missed approach when visual reference to the runway was lost.
Final Report:

Crash of a Beechcraft B200C Super King Air in New Delhi: 1 killed

Date & Time: Aug 27, 1992 at 1159 LT
Registration:
VT-EOA
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
New Delhi - New Delhi
MSN:
BL-129
YOM:
1987
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
13519
Captain / Total hours on type:
1099.00
Aircraft flight hours:
1347
Circumstances:
Border Security Force (BSF) Beechcraft B200 Super King Air VT-EOA was engaged in a local flying (circuits and landings) at IGI Airport, Delhi on 27.8.92. There were two persons on board the aircraft including the commander. After two circuits and landings, the commander asked for full stop landing. However, after landing the commander asked the ATC about one more circuit to which the controller gave the consent and asked him to line up on runway 28 for take off. At this stage, the copilot on board was disembarked. The aircraft took-off without ATC clearance and turned left for circuit. Thereafter, it was seen going down in a nose down attitude and impacted the ground. The aircraft impacted the ground, caught fire and was destroyed. The pilot, who was the sole occupant on board, received fatal injuries.
Probable cause:
The exact cause of the accident could be confirmed. However, on the basis of evidence on record, the probability of deliberate attempt to crash the aircraft by late Captain Dhaliwal could not be ruled out. The probability of incapacitation of Captain Dhaliwal during the last circuit has also not been ruled out.
Final Report:

Crash of a Boeing 747-237B in New Delhi

Date & Time: May 7, 1990 at 0917 LT
Type of aircraft:
Operator:
Registration:
VT-EBO
Survivors:
Yes
Schedule:
London - New Delhi - Bombay
MSN:
20558
YOM:
1972
Flight number:
AI132
Country:
Region:
Crew on board:
20
Crew fatalities:
Pax on board:
195
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8026
Circumstances:
After touchdown at New Delhi-Indira Gandhi Airport following an uneventful flight from London-Heathrow Airport, the crew started the braking procedure and activated the thrust reversers when the pylon of the engine n°1 failed. The engine partially detached, causing a fuel line to rupture and the fuel to ignite. The aircraft was stopped after a course of almost 3 km and all 215 occupants were evacuated safely. The fire was extinguished but the aircraft was damaged beyond repair.
Probable cause:
The accident was caused due to the migration of the improperly installed diagonal-brace aft fuse-pin of the No.1 engine from its fitting which substantially reduced the load carrying capability of the engine fittings resulting in failure of the upper-link forward fuse pin due to excessive loads on account of probably improper landing leading to a partial separation of engine and fire.

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.