Crash of a Learjet 45 in Mumbai

Date & Time: Sep 14, 2023 at 1705 LT
Type of aircraft:
Operator:
Registration:
VT-DBL
Survivors:
Yes
Schedule:
Visakhapatnam – Mumbai
MSN:
45-404
YOM:
2009
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The approach to Mumbai-Chhatrapati Shivaji Airport was completed in poor weather conditions with reduced visibility due to heavy rain falls. On short final, the airplane was in a nose down attitude and rolling to the right when it impacted the runway surface. It went out of control, veered off runway and came to rest in a grassy area, broken in two. A small fire was quickly extinguished. All eight occupants were injured.

Crash of a Boeing 737-85R in Mumbai

Date & Time: Jul 1, 2019 at 2351 LT
Type of aircraft:
Operator:
Registration:
VT-SYK
Survivors:
Yes
Schedule:
Jaipur - Mumbai
MSN:
30410/1228
YOM:
2002
Flight number:
SG6237
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
160
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5355
Captain / Total hours on type:
5113.00
Copilot / Total flying hours:
4826
Copilot / Total hours on type:
4625
Circumstances:
On 01.07.2019, B737-800 aircraft was involved in an accident (runway excursion) at Mumbai airport while landing in moderate to heavy rain. The aircraft was under the command of an ATPL holder (PF) with a CPL holder as First Officer (PM). There were 160 passengers and 7 crew members on board. There was no injury to any of the passengers or crew members. The aircraft suffered substantial damage. The subject flight was fifth of the day for the aircraft and second for the flight crew. The flight crew had earlier operated Mumbai-Jaipur sector and the incident flight was from Jaipur to Mumbai. There were no technical issues reported by the flight crew either during Mumbai Jaipur sector or on the return leg (Jaipur- Mumbai) till descent into Mumbai. The pilots had carried out briefing amongst themselves for the approach including the weather and Go Around actions, if required. The aircraft commenced descent into Mumbai in the late evening hours. As per the reported weather at the time of approach visibility was 2100 metres in rain making it dark. Reported winds were 090/12 Knots. Runway was wet and the trend provided was ³temporary reduction in visibility to 1500 metres with thunder/ showers of rain´. During descend at approximately 7000' Pressure Altitude, the crew observed an indication for IAS disagree, indicating a discrepancy of airspeed between the instrument sources for the flight crew. Although this indication was momentary, the 'Non-Normal Checklist' was carried out. The indication discrepancy did not recur for the remainder of the flight. The aircraft was radar vectored for an ILS approach for Runway 27 at Mumbai. The approach was stabilized by 3800' Pressure Altitude with landing gear down, flaps 30 and auto brake selected at 3. The autopilot was engaged throughout the descent phase and during approach, the second autopilot was also coupled for the ILS approach. At 100', the autopilot and the auto-throttle were disengaged by the PF. The flare manoeuvre consumed approximately 5807' of the runway length prior to the aircraft touchdown with 3881' of runway remaining. After touchdown, the speed brakes deployed automatically and maximum reverse thrust and wheel brakes were applied. The aircraft exited the paved surface at 65 Knots and came to rest at a distance of 615' beyond the end of the runway. Once the aircraft came to rest, the flight crew advised cabin crew to be at their stations. The pilots were unable to contact ATC through VHF communication. The PF contacted his airline personnel using mobile phone and informed that the aircraft had overrun the runway and requested for step ladders. The ATC activated fire services and the runway was closed for operation. The Cabin crew carried out check on the passengers in the cabin. The fire services reached the aircraft location and verbal communication was established with the flight crew once the cockpit window was opened. Two Fire Services personnel boarded the aircraft from the L1 door using a fire ladder. An assessment of the aircraft structure and occupants was made and the fire services personnel informed the cabin crew that deplaning was to be carried out using fire ladders. There were no injuries during evacuation or otherwise.
Probable cause:
The runway excursion occurred because of combination of:
- Disconnection of auto pilot at an altitude 118' RA with the nose up trim bias without adequate compensation.
- Disconnection of auto throttle at 118' RA at a higher thrust setting for that phase of flight.
- Late touchdown of the aircraft on the runway.
- Reduced visual cues due to heavy rain impacting depth perception and ascertaining of actual touchdown position.
- Tailwind conditions at the time of landing resulting In increasing the distance covered during the extended flare (float).
- Approach with lower flaps (30) than recommended (40).
Final Report:

Crash of a De Havilland DHC-8-402Q in Jabalpur

Date & Time: Dec 4, 2015 at 1922 LT
Operator:
Registration:
VT-SUC
Survivors:
Yes
Schedule:
Mumbai – Jabalpur
MSN:
4377
YOM:
2011
Flight number:
SG2458
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
49
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7748
Captain / Total hours on type:
2148.00
Copilot / Total flying hours:
7804
Copilot / Total hours on type:
137
Aircraft flight hours:
11928
Aircraft flight cycles:
11214
Circumstances:
Bombardier Q-400 aircraft VT-SUC belonging to M/s Spice jet Ltd. was involved in wild life strike accident during landing roll at Jabalpur while operating scheduled flight SG2458 from Mumbai to Jabalpur on 04.12.2015. The aircraft was under the command of pilot holding ATPL & duly qualified on type with First Officer also an ATPL holder and qualified on type. There were 49 passengers and 02 cabin crew on board the aircraft. The aircraft VT-SUC took-off from Mumbai for Jabalpur at around 1200 UTC. The enroute flight was uneventful. The aircraft came in contact with ATC Jabalpur at around 1323 UTC. The ATC reported prevailing weather at Jabalpur as surface winds calm, visibility 5000 meters, weather Haze, nonsignificant clouds, and temp 24° C. At 1342 UTC the pilot requested ATC for visual approach runway 06. The ATC cleared VT-SUC for visual approach runway 06 and asked to confirm when runway in sight. At 1347 UTC the pilot confirmed the runway in sight and requested for landing clearance and the same was acknowledged by ATC. The aircraft landed on runway 06 and about 05 to 06 seconds after touch down at around 1350 UTC the aircraft hit wild boars on the runway. The pilot stated that as it was dawn they did not see the wild boars on runway during approach, and saw the wild boars only after touch down and when they were very close to them, also they did not had adequate time to react so as to take any evasive action. Hence, one of the wild boars on runway impacted with LH main landing gear due which the LH Main landing gear got collapsed and the aircraft started drifting towards left. Thereafter LH engine propeller blades came in contact with ground and got sheared off. The aircraft dragged on its belly for around 182 feet and in the process the nose landing gear also collapsed. The aircraft then veered to the left of the center line and subsequently exited the runway onto the left side and came to final halt position in Soft Ground. The pilot then confirmed with first officer about fire and once getting assured that there was no fire gave evacuation call outs. The pilot then contacted ATC for assistance and informed that there were 10 to 11 pigs on the runway and the aircraft had hit the pig and gone off the runway. The Crash Fire Tender (CFT) team along with operational jeep reached the accident site. The pilot shut down the engines. All the passengers were then evacuated safely from the RH side. There was no injury to any of the occupants on board the aircraft and there was no fire.
Probable cause:
The aircraft during its landing roll had a wild life (Wild Boars) strike on the runway, resulting in collapse of left main landing gear and subsequently the aircraft veered to the left of the runway.
Contributory factor:
The presence of wild life in the operational area and the runway was due to several breaches in the boundary wall.
Final Report:

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-4Q8 in Mumbai

Date & Time: Oct 9, 2005 at 1920 LT
Type of aircraft:
Operator:
Registration:
VT-SID
Survivors:
Yes
Schedule:
Calcutta - Mumbai
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:
Following an uneventful flight from Calcutta, the aircraft landed at Mumbai-Chhatrapati Shivaji Airport runway 27. Unable to stop within the remaining distance, the aircraft overran and came to rest few dozen metres further. All 117 occupants evacuated safely while the aircraft was damaged beyond repair.

Crash of a Fokker F27 Friendship off Mumbai: 2 killed

Date & Time: Jul 3, 1997 at 0349 LT
Type of aircraft:
Operator:
Registration:
VT-SSA
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Mumbai - Bangalore
MSN:
10670
YOM:
1984
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
9322
Captain / Total hours on type:
4585.00
Copilot / Total flying hours:
812
Copilot / Total hours on type:
545
Aircraft flight hours:
10619
Circumstances:
The aircraft took-off from runway 27 of Mumbai Airport at 2216 UTC of 2.7.97 (0346 IST of 3.7.97). After take off the pilot reported to Tower, "VSA is turning left Sir, thousand two hundred, we are entering weather otherwise", to which tower acknowledged and asked VT-SSA to contact Radar. The aircraft contacted Radar and was asked to establish radial 146 and report passing FL080, climb level 170 for which aircraft acknowledged, "Roger, call you establish 146 passing 70 and reaching 170 SA." This was the last transmission from the aircraft. The aircraft crashed into the Arabian Sea off Mumbai coast at about 2219 UTC. The aircraft got destroyed after impact with sea and both occupants on board died in the accident. There was no evidence of fire.
Probable cause:
The pilot possibly lost control when encountered severe weather conditions soon after take off and crashed into the sea. Non-availability of latest weather to the pilot was the contributory factor.
Final Report:

Crash of a Beechcraft 300 Super King Air in Taloja: 4 killed

Date & Time: Jul 15, 1993 at 1155 LT
Operator:
Registration:
VT-EQM
Flight Type:
Survivors:
No
Schedule:
Ahmedabad - Mumbai
MSN:
FA-128
YOM:
1987
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
1505
Captain / Total hours on type:
28.00
Aircraft flight hours:
270
Circumstances:
The aircraft, belonging to National Remote Sensing Agency, Hyderabad, was operating a ferry flight from Ahmedabad to Bombay. There were four persons on board the aircraft including pilot-in-command. During approach to land at Bombay, contact with ATC was lost after the aircraft had reported its flight level 4,000 feet. The aircraft was found crashed on top of the hills at Taloja village located about 11 NM East of Bombay airports. All the four persons on board received fatal injuries. The aircraft was completely destroyed.
Probable cause:
The probable cause of accident has been attributed to:
- The commander of the aircraft having meager flying experience on type and limited instrument flying hours encountering instrument meteorological conditions descended below the ATC cleared height of 3,700 feet without intercepting the glide slope.
- The radar controller by not effectively monitoring the aircraft position after he had advised it to intercept the localizer contributed to the cause of the accident.
- The pilot failed to follow procedures, regulations and instructions.
Final Report:

Crash of a Boeing 737-2A8 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
Captain / Total flying hours:
4963
Captain / Total hours on type:
1720.00
Copilot / Total flying hours:
1172
Copilot / Total hours on type:
921
Aircraft flight hours:
43886
Circumstances:
Indian Airlines Boeing 737 aircraft VT-ECQ was operating scheduled flight IC491 from Delhi to Jaipur, Udaipur, Aurangabad and Bombay. The flight from Delhi to Aurangabad was uneventful. The aircraft took-off from Aurangabad with 118 persons on board. Aircraft lifted up almost at the end of runway and impacted heavily with a lorry carrying pressed cotton bales running from North to South on a highway at a distance of about 410 feet from the end of runway. The aircraft left main landing gear, left engine bottom cowling and thrust reverser impacted the left side of the truck at a height of nearly seven feet from the level of the road. Thereafter the aircraft hit the high tension electric wires nearly 3 kms North-East of the runway and hit the ground. In all 55 persons received fatal injuries. The aircraft was destroyed due to post impact fire.
Probable cause:
The probable cause of accident has been attributed to :
- Pilots' error in initiating late rotation and following wrong rotation technique, and
- Failure of the NAA to regulate the mobile traffic on the Beed road during the flight hours.
Final Report:

Crash of an Airbus A320-231 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:
79
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
Aircraft flight hours:
370
Aircraft flight cycles:
302
Circumstances:
Indian Airlines Flight 605 took off from Mumbai, India, at 11:58 for a domestic flight to Bangalore. At 12:25 Bangalore approach was contacted and prevailing weather was passed on to the crew (wind variable 5 knots, visibility 10 km, clouds 2 octa 2,000 feet, temperature 27° C, QNH 1018). At 12:44 the aircraft was cleared to descend to FL110. Reaching FL110, vectors were given for a visual runway 09 approach. On final approach, the aircraft descended well below the normal approach profile and kept descending until it struck the boundaries of the Karnataka Golf Club (2,300 feet short of the runway and 200 feet right of the extended centerline. The aircraft rolled for 80 feet and lifted off again for about 230 feet and came down again on the 17th green of the golf course. The landing gear wheels dug into the ground and the aircraft impacted a 12 feet high embankment, causing the gears and engines to be sheared off. The aircraft continued over the embankment and came to rest in a grassy, marshy and rocky area.
Probable cause:
Failure of the pilots to realize the gravity of the situation and respond immediately towards proper action of moving the throttles, even after the radio altitude call-outs of "Four hundred", "Three hundred" and "Two hundred" feet, in spite of knowing that the plane was in idle/open descent mode. However, identification of the cause for the engagement of idle/open descent mode in short final approach during the crucial period of the flight is not possible.
Final Report:

Crash of a Boeing 737-2A8 in Ahmedabad: 133 killed

Date & Time: Oct 19, 1988 at 0653 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:
6
Crew fatalities:
Pax on board:
129
Pax fatalities:
Other fatalities:
Total fatalities:
133
Captain / Total flying hours:
5985
Aircraft flight hours:
42750
Aircraft flight cycles:
47520
Circumstances:
Indian Airlines B-737 aircraft VT-EAH was operating scheduled flight IC113 (Bombay - Ahmedabad sector) on 19-10-1988. There were 135 occupants on board including 6 crew members. Aircraft contacted Ahmedabad Approach Control at 0620LT. Ahmedabad weather as per Metar of 0540LT was passed to the aircraft and again at 0625LT (speci) of 0610LT was passed to the aircraft and then visibility has been reduced from 6 km to 3 km. Clearance to descend to FL150 was given at 0632LT and the aircraft was further cleared to FL55, 25 DME at 0636LT. At 0641LT, the aircraft was advised to report over Ahmedabad VOR and 'Speci' of 0640LT was also transmitted to the aircraft as per the same the winds were calm, visibility 2 km in haze and was 1010. QNH was correctly read back by the aircraft. The pilot decided to carry localiser-DME approach for runway 23 and reported overhead Ahmedabad. The aircraft went outbound and reported turning inbound. This was the last transmission from the aircraft and thereafter contact with the ATC was lost at 0650:53. The aircraft was found crashed at a distance of 2,540 meters from the beginning of runway 23 on the extended centre line of the runway in a paddy field at about 0653LT. Out of 135 persons on board, 133 received fatal injuries. The remaining two were seriously injured. The aircraft was destroyed due to post impact fire.
Probable cause:
The cause of the accident is attributed to error on part of the pilot-in-command as well as copilot due to non adherence to laid down procedures under poor visibility conditions. Both pilot and copilot failed to follow approved procedures, directives, instructions, etc. Weather was considered as a contributing factor.