Engine Stall and Runway Excursion During Go-Around at Bengaluru

Casualties unknown • BENGALURU AIRPORT, IN

An Airbus A320 operated by Go-Air experienced an engine stall and touched an unpaved surface during a missed approach at Bengaluru due to low visibility and pilot error.

What happened

On November 11, 2019, at 01:52 UTC, a Go-Air Airbus A320, registration VT-WGR, was performing a landing approach at Bengaluru Airport under deteriorating weather conditions. As the aircraft approached Runway 09, visibility and Runway Visual Range (RVR) were rapidly decreasing due to dense fog.

During the final stages of the approach, the pilot-in-command disconnected the autopilot at 220 feet radio altitude to perform a manual landing. While attempting to align the aircraft, the pilot mistakenly identified left runway edge lights as centerline lights and maneuvered the aircraft to the left. Two seconds before touchdown, the First Officer called for a "Go Around." During the subsequent missed approach maneuver, the aircraft's main undercarriage contacted an unpaved, grassy surface adjacent to the runway. This contact caused the ingestion of debris into the number 1 engine, resulting in an engine stall. The crew subsequently diverted the flight to Hyderabad, where the aircraft landed safely.

The investigation

The AAIB India investigation examined the flight data, cockpit voice recordings, and air traffic control communications. Investigators reviewed the meteorological conditions, noting that visibility had dropped significantly below the anticipated levels. The inquiry also scrutinized the aircraft's maintenance records and the operational procedures of the airline.

Findings

  • The primary cause of the incident was the loss of visual reference after crossing the approach lights, which led to the aircraft drifting from the runway centerline.
  • The pilot-in-command's attempt to regain visual alignment led to the aircraft being positioned over the unpaved surface during the go-around.
  • Air traffic controllers failed to provide the flight crew with updated, real-time RVR and visibility information as conditions worsened.
  • There was a lack of effective crew coordination, as the pilot-in-command did not take over flying duties at an appropriate stage of the landing phase.
  • The aircraft's left engine suffered a stall due to the ingestion of foreign objects from the unpaved ground during the excursion.

Safety action

  • The investigation recommended that airline operators enhance simulator training regarding crew assessment of visibility during approaches.
  • It suggested that operators evaluate the safety benefits of utilizing manufacturer-provided auto-land capabilities in CAT I conditions.
  • Recommendations were made for air traffic control infrastructure, specifically regarding the visibility of RVR monitoring software and the implementation of automated alerts for sudden visibility drops.

Probable cause

The incident was caused by the pilot's loss of visual reference in low visibility, leading to an improper alignment with the runway centerline. This was compounded by the failure of ATC to communicate rapidly deteriorating visibility and a lack of timely go-around initiation by the crew.

Frequently asked questions

What happened in the 2019-11-11 GO-AIR AIRBUS A320 accident near BENGALURU AIRPORT, IN?

An Airbus A320 operated by Go-Air experienced an engine stall and touched an unpaved surface during a missed approach at Bengaluru due to low visibility and pilot error.

What aircraft was involved and where did it happen?

The accident on 2019-11-11 involved a GO-AIR AIRBUS A320, registration VT-WGR, at BENGALURU AIRPORT, IN.

What was the probable cause of the accident?

The incident was caused by the pilot's loss of visual reference in low visibility, leading to an improper alignment with the runway centerline. This was compounded by the failure of ATC to communicate rapidly deteriorating visibility and a lack of timely go-around initiation by the crew.

Loading the flight search…