Report: ATR-72 runway excursion accident following unstabilized approach (India)

January 13, 2011

Investigators from the Indian DGCA concluded that an ATR-72 runway excursion at Mumbai was caused by the failure of the crew to execute a go around during an unstabilized approach.

An ATR-72 passenger plane, operated by Kingfisher Airlines, was substantially damaged when it aquaplaned off the runway on landing at Mumbai-Chhatrapati Shivaji International Airport (BOM), India on November 10, 2009.

Flight IT4124 operated on a scheduled domestic flight from Bhavnagar Airport (BHU) to Mumbai. There were 36 passengers, 2 Infants and four crew members on board the aircraft.

Maintenance on runway runway 14/32 and runway 27 at Mumbai effected operations at the airport between certain times. There were several NOTAM’s in effect relating to runway 27:

GP RWY27 NOT AVBL DUE SHORTENED RWY27. BTN 0730-1130 ON EVERY TUE, 03 NOV 07:30 2009 UNTIL 23 MAR 11:30 2010
RWY27 CL LGT NOT AVBL. 27 OCT 12:30 2009 UNTIL 31 MAR 23:59 2010.
RWY27 TDZ LGT NOT AVBL. 27 OCT 12:30 2009 UNTIL 31 MAR 23:59 2010.
RWY27 SHALL BE USED FOR LDG AND TKOF FM A POINT 1262M FM THR OF RWY27
1.THE SHORTENED RWY SHALL BE DESIGNATED AS RWY 27A. RADAR VECTORED VISUAL APP WILL BE PROVIDED SUBJ TO VIS 2800M OR MORE.DECLARED DIST OF RWY27A-
RWY TORA TODA LDA ASDA
27A 1703M 1703M 1703M 1703M
2.THR MARKING PROVIDED ON BOTH SIDES OF RWY27A ON RWY SHOULDER AREA AT A DIST OF 180M
3.PAPI RWY27A PROVIDED
4.AIMING POINT MARKING PROVIDED ON SHOULDER OF RWY27A OPPOSITE PAPI
5.DIST INDICATION SIGN PROVIDED EV 300M FM RWY27A END.
6.TORA SIGN PROVIDED AT TWY Q HLDG POINT.
7.TEMP WING BAR LGT PROVIDED FOR THR.
8.RWY EDGE LGT,RWY CL AND RWY END LGT PROVIDED FOR RWY27A. BTN 0730-1130 UTC ON EV TUE ON [...],10,17,24 NOV 2009 [...]

Runway 27 thus was available only after runway intersection as runway 27A. To carry out operations on this reduced runway 27 a NOTAM was issued and designated runway 27A for visual approach only. 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 flight IC-164, an 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 the Kingfisher flight 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 ATR-72 approached 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 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 Taxiway N10, the aircraft rolled into an unpaved wet area. It rolled over drainage pipes and finally came to a stop near open drain. There was no fire.

PROBABLE CAUSE OF THE ACCIDENT:

The accident occurred due to unstabilized approach and decision of crew not to carry out a ‘Go-around’.

Contributory Factors:

  1. Water patches on the R/w 27A
  2. Inability of the ATCO to communicate the aircraft about aquaplaning of the previous aircraft
  3. Lack of input from the co-pilot.

More information:

VT-KAC final report


Report: poor runway friction and aquaplaning caused E135 excursion

May 11, 2010

The Embraer 135 came to rest across a road

The runway excursion accident involving an Airlink (South Africa) Embraer RJ135LR passenger jet in Decemer 2009 was caused by aquaplaning due to poor runway friction, according to the second interim report published by the South African Civil Aviation Authority (CAA).

SA Airlink flight SA 8625 departed Cape Town International Airport (CPT) on a domestic scheduled flight to George Airport (GRJ). The aircraft was cleared for an instrument landing system (ILS) approach runway 11. The prevailing weather conditions at the time were overcast in light rain. The aircraft touched down in the area of the fourth landing marker. At the end of the runway veered to the right and went past the ILS localizer. The aircraft collided with eleven approach lights before it burst through the aerodrome perimeter fence, with the aircraft coming to rest in a nose down attitude on a public road.
Runway 11 is a 2000 x 45 meters asphalt runway. At the time of this accident it was the first time that the George area had received a proper rain shower following the rehabilitation of the runway, which was concluded on 6 November 2009. It would appear that the application of the fog spray sealant extensively used during the runway rehabilitation works degraded the surface friction coefficient of the runway surface during wet conditions. This allowed the onset of aquaplaning and thereby inhibited the application of adequate braking pressure by the anti-skid system to stop the aircraft within the certificated distance.


Follow

Get every new post delivered to your Inbox.

Join 43 other followers

%d bloggers like this: