Crash of a Beechcraft C90A King Air in Mumbai: 5 killed

Date & Time: Jun 28, 2018 at 1315 LT
Type of aircraft:
Operator:
Registration:
VT-UPZ
Flight Type:
Survivors:
No
Site:
Schedule:
Juhu - Juhu
MSN:
LJ-1400
YOM:
1995
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
Following technical maintenance, a test flight was scheduled with two engineers and two pilots. The twin engine airplane departed Mumbai-Juhu Airport and the crew completed several manoeuvres over the city before returning. On approach in heavy rain falls, the aircraft went out of control and crashed in flames at the bottom of a building under construction located in the Ghatkopar West district, some 3 km east from Mumbai Intl Airport. The aircraft was completely destroyed by impact forces and a post crash fire and all four occupants were killed as well as one person on the ground.

Crash of an ATR72-212 in Mumbai

Date & Time: Nov 10, 2009 at 1640 LT
Type of aircraft:
Operator:
Registration:
VT-KAC
Survivors:
Yes
Schedule:
Bhavnagar - Mumbai
MSN:
729
YOM:
2006
Flight number:
IT4124
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
38
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7160
Captain / Total hours on type:
2241.00
Copilot / Total flying hours:
973
Copilot / Total hours on type:
613
Aircraft flight hours:
9318
Circumstances:
As per the NOTAM, Runway 14/32 was under permanent maintenance on every Tuesdays since 10/11/2009 runway 27 was available only after runway intersection as runway 27A. To carry out operations on this reduced runway 27 a NOTAM ‘G’ No. G 0128/08 was issued by AAI on the same day of accident i.e. 10-11-2009 and designated as runway 27A for visual approach only. As per the NOTAM Landing Distance Available (LDA)/take off Distance available (TODA) was 1703 m. The weather conditions prevailing at the time of accident was winds 070/07 knots visibility 2800 m with feeble rain. Prior to Kingfisher aircraft, Air India aircraft IC-164, Airbus 319 had landed and reported to ATC that it had aquaplaned and broken two runway edge lights. The ATC acknowledged it and sent runway inspection vehicle to inspect the runway. The ATC person was not familiar with the terminology of ‘aquaplaning’ and not realizing the seriousness of it, cleared kingfisher aircraft for landing. At the time of accident there were water patches on the runway. ATC also did not transmit to the Kingfisher aircraft the information regarding aquaplaning reported by the previous aircraft. The DFDR readout revealed that kingfisher aircraft was not on profile as per localizer procedure laid down in NOTAM ‘G’ and was high and fast. The aircraft landed late on the runway and the runway length available was around 1000 m from the touchdown point. In the prevailing weather conditions this runway length was just sufficient to stop the aircraft on the runway. During landing the kingfisher aircraft aquaplaned and did not decelerate even though reversers and full manual braking was applied by both the cockpit crew. The aircraft started skidding toward the left of center line. On nearing the runway end, the pilot initiated a 45 ° right turn, after crossing ‘N 10’ Taxi track, the aircraft rolled into unpaved wet area. Aircraft rolled over drainage pipes & finally came to a stop near open drain. There was no fire. All the passenger safely deplaned after the accident.
Probable cause:
The accident occurred due to an unstabilized approach and decision of crew not to carry out a ‘Go-around’.
Contributory Factors:
i) Water patches on the runway 27
ii) Inability of the ATCO to communicate the aircraft about aquaplaning of the previous aircraft
iii) Lack of input from the copilot.
Final Report:

Crash of a Boeing 737-400 in Mumbai

Date & Time: Oct 9, 2005 at 1920 LT
Type of aircraft:
Operator:
Registration:
VT-SID
Survivors:
Yes
Schedule:
Calcutta-Bombay
MSN:
24705
YOM:
1990
Flight number:
RSH117
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
111
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
While landing on runway 27, the aircraft did not decelerate as expected. It overran and came to rest few dozen metres further on. Nobody was injured while the aircraft was damaged beyond repair.

Crash of a Boeing 737-200 in Aurangabad: 55 killed

Date & Time: Apr 26, 1993 at 1306 LT
Type of aircraft:
Operator:
Registration:
VT-ECQ
Flight Phase:
Survivors:
Yes
Schedule:
New Delhi-Jaipur-Udaipur-Aurangabad-Bombay
MSN:
20961
YOM:
1974
Flight number:
IC491
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
112
Pax fatalities:
Other fatalities:
Total fatalities:
55
Aircraft flight hours:
43886

Crash of an Airbus A320 in Bangalore: 92 killed

Date & Time: Feb 14, 1990 at 1303 LT
Type of aircraft:
Operator:
Registration:
VT-EPN
Survivors:
Yes
Schedule:
Bombay-Bangalore
MSN:
0079
YOM:
1989
Flight number:
IC605
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
139
Pax fatalities:
Other fatalities:
Total fatalities:
92
Captain / Total flying hours:
10339
Captain / Total hours on type:
212.00
Copilot / Total flying hours:
9307
Copilot / Total hours on type:
68

Crash of a Boeing 737-200 in Ahmedabad: 124 killed

Date & Time: Oct 19, 1988 at 0630 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:
5
Crew fatalities:
Pax on board:
124
Pax fatalities:
Other fatalities:
Total fatalities:
124
Aircraft flight hours:
42750
Aircraft flight cycles:
47520

Crash of a Lockheed L-1049G Super Constellation in Bombay

Date & Time: Jan 12, 1983
Operator:
Registration:
IN316
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
4666
YOM:
1956
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The undercarriage retracted for unknown reasons while the aircraft was taxiing at Bombay Airport. There were no injuries but the aircraft was written off.

Crash of a Hindustan Aeronautics HAL-748-224-2A near Mumbai: 45 killed

Date & Time: Aug 4, 1979 at 2016 LT
Operator:
Registration:
VT-DXJ
Survivors:
No
Site:
Schedule:
Pune - Bombay
MSN:
515
YOM:
1968
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
40
Pax fatalities:
Other fatalities:
Total fatalities:
45
Circumstances:
While approaching Bombay Airport from the southeast by night, the crew encountered technical problems when the airplane struck the slope of Mt Kisoli located 30 km southeast from Bombay Airport. SAR operations were hampered by lack of visibility and heavy rain falls. The wreckage was found few hours later and all 45 occupants were killed.
Probable cause:
The accident was the consequence of the combination of the following factors:
- Momentary/intermittent loss of electrical contact in G/S system of aircraft which gave the pilot an erroneous impression of the interception of the glide slope,
- Failure of the pilot to discharge his obligations under DOC 4444 by failing to use the glidepath facility only after the Outer Marker and also in descending below 2910 feet without first cross-checking over the Outer Marker,
- Failure of the radar controller to discharge his obligations under DOC 4444 of giving position information to the aircraft from time to time, use of incorrect and/or non-standard phraseology and also failure to inform the aircraft about the loss of radar contact.