14 Feb 1990: Airbus A320-231 — Indian Airlines

92 fatalities • 0,7 km W of Bangalore-Hindustan Airport (BLR)

Accident narrative

Indian Airlines Flight 605 was a scheduled domestic passenger flight from Bombay to Bangalore. On 14 February 1990, an Airbus A320-231 registered as VT-EPN, crashed onto a golf course while attempting to land at Bangalore, killing 92 of 146 people on board. The Indian investigative team ruled that the probable cause was the pilots selecting the "Open descent/flight idle" control mode rather than "Glideslope capture", allowing the aircraft to sink far below the correct flight path. They further failed to advance the throttles or pull up even after the radio altitude call-outs, as the aircraft approached landing. The report stated that the crew of Flight 605 weren't aware of the situation and the danger they were facing at the time, resulting in delayed reaction during the descent. After the crash, the Indian investigation committee issued 62 recommendations to the Indian Directorate General of Civil Aviation (DGCA), including a time recording on the air traffic control (ATC) tapes and the formation of several investigative committees specializing in several aviation operational issues. Included in the recommendation was the addition of a crash siren in Bangalore, evaluation of the evacuation doors and slides in Airbus airplanes, and a design change on their instrument knob. The report also urged the government to evaluate every airport in India to prevent similar incidents from occurring. The crash drew criticism among the Indian Commercial Pilots' Association (ICPA) which claimed that the Airbus A320 had severe flaws. They claimed that the aircraft's systems were too confusing and that the crew of Flight 605 was struggling to avert the crash. Another A320 accident less than two years later (which occurred under similar circumstances) led to design improvements to the flight control unit and numerous safety recommendations.

== Aircraft == The aircraft involved was an Airbus A320-231, registered as VT-EPN, serial number 79 and was around 5 months old. The aircraft had logged around 370 flight hours over 302 flights and was equipped with two IAE V2500-A1 engines.

== Flight ==

=== Take-off and approach === Flight 605 took off from Bombay Airport at 11:58 local time after an hour delay. Prior to this, the aircraft was used for two other flights on the day of the accident, operating as Flight 669 and Flight 670, flying from Bombay to Goa and back. The aircraft was carrying 139 passengers and 7 crew members, including 4 infants. The aircraft's assigned route was on route W17 from Bombay to Belgaum via Karad and W56 from Belgaum to Bangalore. The take-off phase and en route phase proceeded normally. At 12:53 local time, Flight 605's radar plot appeared on Bangalore's radar. Flight 605 was asked by Bangalore Radar to turn right and make a visual approach to Runway 09. The crew disengaged the autopilot and later changed to the Bangalore Tower after being transferred by Bangalore Radar.

=== Crash === While Flight 605 was attempting to land, the pilots flew far below the glideslope, and the landing gear touched down on the grounds of the Karnataka Golf Association, approximately 2,800 ft (850 m) from the airport. Most people on the aircraft, including some crew members, thought that the aircraft had touched down on the runway as it was similar to its normal landing. Flight 605 then bounced and shortly later impacted the ground for the second time. The impact caused several people's seat belts to fail, leading people to be thrown from their seats and hit the aircraft's floor. Flight 605 later struck a 12 ft (3.7 m) embankment. Both the engines and landing gear detached from the aircraft. The aircraft then flew over a road and crashed into a grassy, rocky area near the airport.

=== Search and rescue === After the crash, a post-impact fire started and the survivors began to escape from the burning wreckage. Several people managed to get out of the plane from an opening in the aircraft's fuselage. The surviving cabin crew opened…

Contributing factors

  • [object Object]

Investigation report by Wikidata contributors. Original record: https://www.wikidata.org/wiki/Q6019809. This page is a structured re-presentation; facts and quotes are in the CC0 (Wikidata).

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 40,000+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.