Ninety-two people are killed when Indian Airlines Flight 605 crashes in Bangalore, India.

Indian Airlines Flight 605: A Detailed Account of the 1990 Bangalore Airbus A320 Crash and Its Legacy

Indian Airlines Flight 605, a routine domestic passenger flight originating from Bombay (now known as Mumbai) and destined for Bangalore (now Bengaluru), tragically ended on 14 February 1990. The Airbus A320-231, registered as VT-EPN, crashed onto a local golf course while attempting its final approach and landing at Bengaluru's HAL Airport. This devastating accident resulted in the loss of 92 lives out of the 146 individuals on board, sending shockwaves through the nascent Indian aviation industry and highlighting critical challenges in new aircraft automation and crew training.

The Fateful Descent: A Critical Error in Mode Selection

The subsequent comprehensive investigation conducted by the Indian authorities revealed a series of operational missteps that directly led to the disaster. The probable cause was identified as a critical misjudgment by the pilots, who inadvertently selected the "Open descent/flight idle" control mode on the aircraft's Flight Control Unit (FCU) instead of the appropriate "Glideslope capture" mode required for a stabilized approach. This seemingly minor programming error had catastrophic consequences.

Sweeping Recommendations for Enhanced Aviation Safety

In the aftermath of the crash, the Indian investigation committee issued an extensive set of 62 recommendations to the Directorate General of Civil Aviation (DGCA), India's primary regulatory body for civil aviation. These recommendations aimed to address systemic issues and prevent similar incidents from recurring across the nation's aviation infrastructure.

The A320's Early Challenges: Pilot Concerns and Design Evolution

The Flight 605 accident also ignited a significant debate within the aviation community, drawing sharp criticism from the Indian Commercial Pilot Association (ICPA). The ICPA vehemently claimed that the newly introduced Airbus A320 possessed inherent design flaws, specifically asserting that the aircraft's advanced systems were overly complex and confusing for pilots transitioning from less automated aircraft. They contended that the crew of Flight 605 was grappling with these complexities in their desperate attempts to avert the crash.

This period marked a learning curve for the global aviation industry, grappling with the implications of highly automated "glass cockpits" and the shift from conventional manual controls to fly-by-wire systems. Pilots transitioning to the A320 often expressed concerns about the perceived "loss of feel" and the need for new paradigms in managing automation, which contributed to discussions around human-machine interface design and training methodologies.

A Catalyst for Global Safety Enhancements

The lessons learned from Indian Airlines Flight 605 unfortunately received further, tragic reinforcement less than two years later. Another Airbus A320 accident, Air Inter Flight 148, occurred in January 1992 under eerily similar circumstances, involving descent mode confusion and a controlled flight into terrain in France. These combined incidents proved to be a critical turning point for Airbus and the wider aviation industry.

In response to these twin tragedies, significant design improvements were implemented, particularly affecting the Flight Control Unit (FCU) of the Airbus A320. These enhancements aimed to make mode selection and annunciation clearer and more intuitive for pilots, thereby reducing the potential for mode confusion. Beyond physical design changes, the accidents led to a cascade of new safety recommendations globally, profoundly influencing pilot training protocols, emphasizing automation management, reinforcing the importance of maintaining robust situational awareness, and improving crew resource management (CRM) practices to prevent such errors from recurring.

Frequently Asked Questions (FAQs) about Indian Airlines Flight 605

What was the primary cause of the Indian Airlines Flight 605 crash?
The primary cause of the Indian Airlines Flight 605 crash was determined to be the flight crew's erroneous selection of the "Open descent/flight idle" control mode instead of "Glideslope capture" during the aircraft's approach to Bangalore. This critical programming error, coupled with a significant delay in recognizing the dangerous descent rate and taking corrective action, led to the aircraft descending far below its intended flight path and impacting the ground.
What is the difference between "Open descent/flight idle" and "Glideslope capture"?
"Open descent/flight idle" is a managed descent mode primarily used to descend efficiently to a pre-selected altitude, typically with the aircraft's engines at idle thrust. Conversely, "Glideslope capture" is an essential approach mode that precisely guides the aircraft along the Instrument Landing System (ILS) glideslope, providing the correct vertical path for a safe and controlled landing. The mistaken selection meant the aircraft was descending rapidly with minimal power, unguided by the necessary precision approach path.
How many fatalities occurred in the Indian Airlines Flight 605 crash?
The Indian Airlines Flight 605 crash resulted in the tragic loss of 92 lives out of the 146 passengers and crew members on board.
Did this crash lead to any significant changes in aviation safety or aircraft design?
Yes, the crash of Indian Airlines Flight 605, alongside a subsequent Airbus A320 accident (Air Inter Flight 148) that occurred under similar circumstances, acted as a catalyst for significant advancements in aviation safety. It led to 62 recommendations from the Indian investigative committee to the DGCA and prompted crucial design improvements, particularly to the Airbus A320's Flight Control Unit (FCU), aimed at making mode selection clearer. Furthermore, these incidents reinforced the need for enhanced pilot training in automation management, situational awareness, and crew resource management (CRM) across the global aviation industry.