Country
code

Maharashtra

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 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 a 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 at the bottom of a building under construction located in the Ghatkopar West district, some 3 km east from Mumbai Intl Airport, bursting into flames. The aircraft was destroyed by impact forces and a post crash fire and all four occupants were killed as well as one people on the ground.

Crash of a Beechcraft King Air 90 in Lohegaon

Date & Time: Sep 7, 2012 at 2000 LT
Type of aircraft:
Operator:
Registration:
VT-KPC
Flight Type:
Survivors:
Yes
Schedule:
Lohegaon - Lohegaon
MSN:
LJ-1696
YOM:
2005
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a local training mission at Lohegaon Airport. On final approach to runway 28, the aircraft impacted ground, teared off several runway lights and came to rest. All three occupants escaped uninjured while the aircraft was damaged beyond repair.

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 a Dornier DO228-201 near Indapur: 11 killed

Date & Time: Sep 23, 1989 at 1953 LT
Type of aircraft:
Operator:
Registration:
VT-EJF
Flight Phase:
Survivors:
No
Schedule:
Pune - Hyderabad
MSN:
8052
YOM:
1985
Flight number:
PF624
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
11
Captain / Total flying hours:
4459
Circumstances:
The aircraft took off from Pune at 1928 hrs. The flight was uneventful up to 1943 hrs. Soon thereafter, the aircraft started losing height rapidly with increasing speed. The pilot attempted recover the aircraft from the dive but the aircraft continued to lose height till it impacted the backwaters Ujjaini Dam near Indapur village, 129 ms east-southeast of Pune. The aircraft disintegrated into multiple pieces, killing all persons on board the aircraft. The accident occurred during night conditions.
Probable cause:
Entry of the aircraft into severe turbulent conditions while passing through clouds, leading to rapid loss of height of the aircraft because of inappropriate action by the pilots. As a result, the aircraft entered a spiral. This was not recognised by the pilots, resulting in initiation of incorrect recovery action by pulling back on the control column instead of first levelling the wings. The possibility of jamming of the elevator of the aircraft cannot be ruled out as one of the probable cause of the accident. Disorientation; unpreparedness of the pilots and their failure to recognise in time, a serious situation and take appropriate corrective action; long breaks in night flying in the case of the captain and temporary malfunction or sluggishness of ADI are the contributory causes.