Bhavnagar - Mumbai
Flight / Schedule
Bhavnagar - Mumbai
Aircraft
ATR72-200Registration
VT-KAC
MSN
729
Year of Manufacture
2006
Operator
Kingfisher AirlinesDate
November 10, 2009 at 04:40 PM
Type
CRASHFlight Type
Scheduled Revenue Flight
Flight Phase
Landing (descent or approach)
Crash Site
Airport (less than 10 km from airport)
Crash Location
Mumbai-Chhatrapati Shivaji (Santa Cruz) Maharashtra
Region
Asia • India
Crash Cause
Human factor
Narrative Report
On November 10, 2009 at 04:40 PM, Bhavnagar - Mumbai experienced a crash involving ATR72-200, operated by Kingfisher Airlines, with the event recorded near Mumbai-Chhatrapati Shivaji (Santa Cruz) Maharashtra.
The flight was categorized as scheduled revenue flight and the reported phase was landing (descent or approach) at a airport (less than 10 km from airport) crash site.
42 people were known to be on board, 0 fatalities were recorded, 42 survivors were identified or estimated. This corresponds to an estimated fatality rate of 0.0%.
Crew on board: 4, crew fatalities: 0, passengers on board: 38, passenger fatalities: 0, other fatalities: 0.
The listed crash cause is human factor. 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.
Aircraft reference details include registration VT-KAC, MSN 729, year of manufacture 2006.
Fatalities
Total
0
Crew
0
Passengers
0
Other
0
Crash Summary
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.
Cause: Human factor
Occupants & Outcome
Crew On Board
4
Passengers On Board
38
Estimated Survivors
42
Fatality Rate
0.0%
Known people on board: 42
Operational Details
Schedule / Flight
Bhavnagar - Mumbai
Operator
Kingfisher AirlinesFlight Type
Scheduled Revenue Flight
Flight Phase
Landing (descent or approach)
Crash Site
Airport (less than 10 km from airport)
Region / Country
Asia • India
