Indigo A320 at Bangalore on Sep 12th 2013, runway excursion
Last Update: November 30, 2015 / 16:13:12 GMT/Zulu time
Incident Facts
Date of incident
Sep 12, 2013
Classification
Incident
Cause
Runway excursion
Airline
Indigo Airlines
Flight number
6E-125
Departure
Delhi, India
Destination
Bangalore, India
Aircraft Registration
VT-IGV
Aircraft Type
Airbus A320
ICAO Type Designator
A320
Airport ICAO Code
VOBL
Bangalore Aviation reported the airport was closed for about 3 hours until the aircraft was moved off the runway protected zone.
The airline confirmed the aircraft touched down right of the runway center line, veered right and contacted five runway edge lights causing the deflation of the right hand main tyres. The aircraft was controlled and vacated the runway onto taxiway F. There were no injuries, the passengers disembarked via stairs and were taken to the terminal. The occurrence was reported to India's DGCA.
On Nov 30th 2015 India's DGCA released their final report concluding the probable cause of the incident was:
The PIC while landing in marginal visibility condition in heavy rain on a wet runway landed right of center line, veered further right and over ran runway shoulder edge lights before the aircraft was controlled directionally.
PIC not using wipers in heavy rain conditions with marginal visibility impaired his vision and is a contributory factor to the incident.
The DGCA reported that the aircraft performed an ILS approach to Bangalore's runway 27, tower warned the crew of heavy rain over the aerodrome with 1500 meters of visibility, the runway was wet. The crew requested a wind check on final approach, winds were reported at 6 knots from 320 degrees. Despite the heavy rain the captain (58, ATPL, 9,341 hours total, 4,411 hours on type), pilot flying, chose to use the rain repellent rather than the wipers, the first officer (24, CPL, 832 hours total, 290 hours on type), pilot monitoring, used the wipers. The captain kept the autopilot connected even after descending below decision height (203 feet AGL) and disconnected the autopilot at 91 feet AGL and flew the aircraft manually, however, drifted to the right. The aircraft touched down on the runway about 12 meters right of the center line, the first officer called (non standard) "Left! Left! Left!", after touchdown veered further to the right until the aircraft's right main gear went beyond the right runway edge destroying 5 runway edge lights in the process about 700 meters down the runway before a sharp left correction was applied by the captain, first officer now called out (again non-standard) "Right!", returning the aircraft onto the runway center line. The aircraft slowed and attempted to vacate the runway via high speed turnoff F 2346 meters from the runway threshold but came to a stop before crossing the hold short line and could not be moved despite increased engine thrust. The crew shut the aircraft down, requested a runway inspection suspecting they had hit runway lights and a tow truck. A tow truck was dispatched, however, the tow bar sheared. The runway inspection identified 5 runway edge lights had been damaged. Both right hand main gear tyres were found deflated damaged by impact with the runway edge lights. The runway had to be closed as the aircraft had not left the protected area of the runway. The passengers disembarked onto the runway and were bussed to the terminal. The tyres and brakes assemblies were replaced on site, then the aircraft was successfully towed to the apron and the runway re-opened 2:44 hours after landing.
No damage beyond the tyre damage occurred on the aircraft.
The DGCA analysed that the aircraft did not leave the paved portion of the runway surface at any time. The aircraft was fully serviceable and did not contribute to the occurrence.
The DGCA wrote in their analysis: "Both the cockpit crew stated that they saw the runway at decision altitude and hence continued for landing. Even though it was raining heavily, the PIC was using rain repellent and had not put on the wipers. However the first officer was using wipers. The aircraft landed right of center line and due prevailing heavy rain the visibility of the PIC was affected and before he could apply correction to bring the aircraft on center line, the aircraft veered further right and over ran 05 runway shoulder edge lights. From the foregoing, it is inferred that weather is a contributory factor to the incident since the PIC vision was impaired due heavy rain which eventually resulted in to the incident."
The DGCA subsequently analysed: "Though the rains were heavy the PIC preferred to use rain repellent only. As per standard practice it is always advisable to use wiper during heavy rains as it provide better visibility over rain repellant. The First officer was using the wiper. The pilot disconnected autopilot very late at around 91 feet AGL which is not as per the Company’s Standard Operating Procedures and thereafter he flew the aircraft manually. However during manually flying the aircraft deviated from the localizer and drifted toward the right. The 09/27 runway at Bengaluru is a CAT 1 runway and the center line is not illuminated. The PIC did a wind check on short final which was reported as 320 deg/06 Kts and winds were not very significant. The aircraft landed right of centerline. Since it was raining heavily and the PIC was not using wiper his vision was impaired. The first officer gave non-standard correction call-outs calling out ‘left left left’ and after a pause, ‘right’ instead of calling-out that they were right of center line. This possibly confused the PIC and delayed the corrective action. As a result the aircraft veered further right and overran the runway shoulder edge lights before the PIC gave correction and brought the aircraft on the center of the runway."
Metars:
VOBL 121700Z 26005KT 6000 -DZ SCT010 SCT015 FEW025CB BKN080 21/21 Q1014 NOSIG RMK CB S SE SW
VOBL 121500Z VRB07KT 0800 R27/P2000N TSRA BKN010 SCT015 FEW025CB OVC080 20/20 Q1014 BECMG 1500 RMK CB NE,E,N NW,OH
VOBL 121400Z 18004KT 8000 VCSH SCT015 SCT020 FEW025CB BKN080 24/23 Q1012 NOSIG RMK CB W
VOBL 121300Z VRB03KT 9999 SCT015 SCT020 FEW025CB BKN080 24/22 Q1011 REDZ NOSIG RMK CB W
VOBL 121200Z VRB03KT 9999 SCT015 SCT020 BKN080 25/21 Q1010 NOSIG
VOBL 121100Z VRB03KT 9999 SCT015 SCT020 BKN080 25/21 Q1010 REDZ NOSIG
VOBL 121030Z VRB03KT 9999 SCT015 SCT020 BKN080 25/22 Q1010 REDZ NOSIG
Incident Facts
Date of incident
Sep 12, 2013
Classification
Incident
Cause
Runway excursion
Airline
Indigo Airlines
Flight number
6E-125
Departure
Delhi, India
Destination
Bangalore, India
Aircraft Registration
VT-IGV
Aircraft Type
Airbus A320
ICAO Type Designator
A320
Airport ICAO Code
VOBL
This article is published under license from Avherald.com. © of text by Avherald.com.
Article source
You can read 2 more free articles without a subscription.
Subscribe now and continue reading without any limits!
Read unlimited articles and receive our daily update briefing. Gain better insights into what is happening in commercial aviation safety.
Send tip
Support AeroInside by sending a small tip amount.
Related articles
Indigo A320 enroute on Nov 11th 2017, laptop aims for Guinness book of records
An Indigo Airbus A320-200, registration VT-IGV performing flight 6E-445 from Thiruvananthapuram to Bangalore (India), was enroute when passengers…
Indigo A320 at Raipur on Sep 27th 2017, bird strike
An Indigo Airbus A320-200, registration VT-IGV performing flight 6E-811 from Raipur to Kolkata (India), was climbing out of Raipur's runway 06 when…
Indigo A20N at Delhi on Feb 11th 2024, runway excursion after landing
An Indigo Airbus A320-200N, registration VT-IZN performing flight 6E-2221 from Amritsar to Delhi (India), landed on Delhi's runway 28, slowed to taxi…
Indigo A21N at Delhi on Feb 9th 2024, momentary foul odour on board
An Indigo Airbus A321-200N, registration VT-IBN performing flight 6E-449 from Delhi to Mumbai (India), was climbing out of Delhi's runway 28 when the…
Indigo A320 at Patna on Jan 3rd 2023, could not retract nose gear
An Indigo Airbus A320-200, registration VT-IFN performing flight 6E-2074 from Patna to Delhi (India) with 187 people on board, was climbing out of…
Indigo A21N at Singapore on Oct 18th 2023, luggage was not unloaded from previous flight
An Indigo Airbus A321-200N, registration VT-IMC performing flight 6E-1006 from Singapore (Singapore) to Bangalore (India), was climbing out of…
Indigo A320 near Mumbai on Mar 21st 2022, uncleared descent causes loss of separation
An Indigo Airbus A320-200, registration VT-IAY performing flight 6E-6261 from Delhi to Mumbai (India), was nearing Mumbai at FL380 and had just…
Newest articles
Luxwing DH8D at Guernsey on Apr 23rd 2024, runway overrun on landing
A Luxwing de Havilland Dash 8-400 on behalf of Aurigny Air Services, registration 9H-LWB performing flight GR-609 from London Gatwick,EN to…
British Airways A388 at Singapore on Apr 22nd 2024, weather radar failure
A British Airways Airbus A380-800, registration G-XLED performing flight BA-12 from Singapore (Singapore) to London Heathrow,EN (UK), was climbing…
Subscribe today
Are you researching aviation incidents? Get access to AeroInside Insights, unlimited read access and receive the daily newsletter.
Pick your plan and subscribePartner
A new way to document and demonstrate airworthiness compliance and aircraft value. Find out more.
ELITE Simulation Solutions is a leading global provider of Flight Simulation Training Devices, IFR training software as well as flight controls and related services. Find out more.
Your regulation partner, specialists in aviation safety and compliance; providing training, auditing, and consultancy services. Find out more.
AeroInside Blog
Popular aircraft
Airbus A320Boeing 737-800
Boeing 737-800 MAX
Popular airlines
American AirlinesUnited
Delta
Air Canada
Lufthansa
British Airways