Indian Airlines Flight 605

Last updated

Indian Airlines Flight 605
Indian Airlines Airbus A320 SDS-5.jpg
An Indian Airlines Airbus A320 similar to the one involved in the crash
Date14 February 1990 (1990-02-14)
Summary Controlled flight into terrain due to pilot error
SiteChallaghatta Valley, near Bangalore Hindustan Airport
12°56′53″N77°38′52″E / 12.9481°N 77.6478°E / 12.9481; 77.6478 Coordinates: 12°56′53″N77°38′52″E / 12.9481°N 77.6478°E / 12.9481; 77.6478
Aircraft type Airbus A320-231
Operator Indian Airlines
Registration VT-EPN
Flight origin Chhatrapati Shivaji International Airport, Bombay, India
Destination Hindustan Airport, Bangalore, India

Indian Airlines Flight 605 was a scheduled domestic passenger flight from Mumbai to Bengaluru. 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. [1]


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 of "Four hundred", "Three hundred" and "Two hundred" feet as the aircraft approached the ground. [1] 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. [1]

After the crash, the Indian investigation committee issued 62 recommendations to the Indian DGCA (Director General of Civil Aviation), including a time recording on the 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. [2]

The crash drew criticism among the Indian Commercial Pilot 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. [2]

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. [3]


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 an Airbus A320-231 registered in India as VT-EPN, 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. [2]

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. [2]


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 Club, approximately 2,800 ft 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 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. [2]

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 the emergency door on the airplane and began to evacuate the survivors. 92 people, consisting of 88 passengers and 4 crew, perished in the crash, while 54 survived, all with injuries. 2 people succumbed to their injuries after the accident. [2]

According to eyewitnesses, no fire service units reached the crash site as there was no RT communication facility between the tower and firefighting vehicles. A portable radio transmitter was available for communication between the tower and the aerodrome fire station, but was not serviceable on the day of the accident. [2]

Passengers and crews

Flight 605 carried 139 passengers and 7 crew members, consisting of 2 cockpit crew and 5 cabin crew. There were 4 infants aboard the flight. [2]

The pilot who controlled the flight was Indian national Captain Cyril Fernandez at 46 years old. He joined Indian Airlines in 1977 as a pilot and was promoted to the position of co-pilot. Eventually, he became Captain of a Hawker Siddeley HS 748. In 1983, Fernandez obtained a Boeing 737 co-pilot rating, followed by a Captain rating in 1984. Fernandez became the co-pilot of an Airbus A320 in 1989. Fernandez had a total flying experience of 9,307 hours, of which 68 hours were spent on the Airbus A320. [2]

According to the report, Captain Fernandez was under supervision as he was undergoing the first of 10 route checks required for qualification to Captain. During the flight, he was seated in the left seat. [2]

The pilot who supervised Captain Fernandez was Indian national Captain Satish Gopujkar at 44 years old. He joined Indian Airlines in 1969 and was employed as a co-pilot on a Hawker Siddeley HS 748 from 1971–1981, later flying the plane as a Captain. In 1981, he obtained a Boeing 737 co-pilot rating and later, a pilot in command rating in 1983. In 1989, he was promoted as a co-pilot on an Airbus A320. Captain Gopujkar had a total flying experience of 10,340 hours, of which 255 hours were on the Airbus A320. During the flight, he was carrying out the duties of both the co-pilot and the check pilot. [2]

Before Flight 605, Captain Gopujkar was involved in a taxiing incident in Cochin[ which? ], although he was not blamed for the incident. During Flight 605, he was seated in the right seat. [2]


92 people were killed in the crash, including Captain Gopujkar and Captain Fernandez. According to official reports: amongst the 54 injured people, at least 20 had suffered head injuries, 32 suffered lower limb injuries, while 7 sustained thoracic injuries. Details in the report revealed that most of the dead suffered major trauma during the crash. At least 81 victims were revealed to have suffered shock and burn injuries. [2]

The report then stated that several passengers may have been too injured to move, leaving them physically unable to escape from the burning wreckage. They may have survived the impact, but due to the injuries they suffered during the crash, they couldn't escape. The report stated that most people seated near the emergency exits and slides survived the crash. [2]

As most survivors and victims of the crash suffered head and leg injuries, the investigative team stated that those injuries might have occurred to the passengers (and some of the crew) onboard as a result of the inadequate leg room. In addition, during the crash, several seats were thrust forward, causing several passengers' head to slam into the back of the seat in front of them. [2]


The Indian Ministry of Civil Aviation ordered a full-scale investigation into the crash. The Indian AAIB and the Canadian TSB were involved in the investigation. On 19 February, investigators visited the crash site and inspected the wreckage of the aircraft. They noted that the front part of the aircraft was destroyed during its impact with the embankment. A subsequent fire led to the total destruction of the aircraft. [2]

Initial inspection

Investigators then inspected the flight controls of Flight 605, viz. the rudder, the ailerons, the trimmable horizontal stabilizer, the flaps and slats, and several other flight controls. However, they didn't find any abnormalities on these controls. Control failure was ruled out as a possible cause of the crash. According to investigators, they also ruled out terrorism as a cause of the crash, as there were no signs of an onboard explosion during the approach and there was no evidence of explosives on board. [2]

FDR and CVR analysis

After the discovery of the FDR and the CVR, investigators decoded and analyzed its contents. [2]

Investigators made an analysis based on both flight recorders as follows: Flight 605 was approaching Bangalore Airport in 'open descent' mode. In this mode, the aircraft engines are at the idle throttle. People would notice this since the engines seem to turn silent, and the plane appears to be sinking bit by bit. [2]

The crew of Flight 605 disengaged the autopilot when sighting the runway of Bangalore Airport. They later made contact with Bangalore Tower. At 01:40 pm local time, the aircraft display indicated that the plane’s altitude had been just under 5000 feet and its approach path was 600 ft higher than the normal glide path. [2]

Captain Fernandez noticed this and requested for a go-around. He would climb to 6000 ft, do another circle and come back better aligned to the normal glide path. The check pilot, Captain Gopujkar then responded to his request: “Do you want a go around? Or do you want vertical speed?” Captain Fernandez chose to proceed with the vertical speed option. If the pilots would have proceeded with the go-around, the emergency that was to follow could have been averted. [2]

Since the plane was a little higher than the normal glide path, Captain Fernandez asked for a higher descent rate of 1000 ft/min, instead of the normal rate of 700 ft/min. This faster descent increased the aircraft speed to 275 km/hr — higher than the recommended speed of 240 km/hr — but it helped the aircraft regain the normal glide path. The aircraft was also now in the vertical speed mode — the correct mode for landing. [2]

Captain Gopujkar then checked the landing checklist. After completing the checklist, he asked the cabin crew to be seated at their stations. Realizing that the aircraft had regained its normal glide path, Captain Gopujkar reported at 01:42 that he had now selected a “700 ft rate of descent”. However, instead of choosing the vertical speed knob, he accidentally chose the altitude knob. So, instead of inputting an order for a 700 ft rate of descent to the Airbus A320, he made an order to put the aircraft on an altitude of 700 ft. [2]

The cockpit of an Airbus A320. The ten control knobs are shown. Cockpit View PR-AVP A320-214 msn 4891 (6349154954).jpg
The cockpit of an Airbus A320. The ten control knobs are shown.

The vertical speed knob and the altitude knob are located next to each other and have a similar design. This might have led to the confusion. [2]

Because of Captain Gopujkar's action, the aircraft went back to the 'open descent' mode, causing the throttle to be in the idle position. The absence of engine power on the aircraft led to a decrease of the aircraft's speed. The plane was falling fast. Despite the impending disaster, the crew of Flight 605 seemed to not be aware of it. [2]

The plane's radio altimeter then sounded: "400 ft". This probably alerted Captain Gopujkar in some way because he suddenly observed: “You are descending on idle open descend eh, all this time!”. And as the altimeter called out “300 ft”, Captain Gopujkar asked: “You want flight directors off now?”. Captain Fernandez confirmed that his flight director had been put off, Captain Gopujkar's however, hadn't. If both the flight directors had been put off at that point, the plane would have gone to the speed mode, sensing that speed was dropping, and enough engine power could have been generated for a possible recovery even at that late stage. [2]

The plane continued to hurtle downwards. When the plane was only 135 ft from the ground, Captain Fernandez suddenly realized the gravity of the situation and exclaimed: “Hey, we’re going down!”. Captain Gopujkar, himself stunned now, could only respond with “Oh, shit!” Those were his last recorded words. Captain Fernandez then ordered an immediate TOGA (Take-off Go-around). However, this action was too late. The aircraft did lift from the ground, however, it failed to clear a 12-ft embankment, which its engines and landing gear sub sequentially struck, and the aircraft crashed. Investigators stated that if this action had been taken 2 seconds earlier, the disaster could have been averted. [2]

Court's findings

The High Court of Karnataka reported that the accident was caused by the pilots failing to realize the gravity of the situation and failing to respond by immediately advancing the throttles, even after the radio altitude callouts of “Four Hundred,” “Three Hundred” and “Two Hundred” feet, despite knowing that the plane was in idle/open descent mode. [2]


India's investigative team concluded that pilot error was the cause of the accident, which was supported by Airbus Industrie. However, the India Commercial Pilot Association (ICPA) disputed the report, claiming that a design flaw on the Airbus A320 was the cause of the crash. [4]

The ICPA stated that the senior Captain of the flight, Captain Gopujkar, wouldn't have made the series of mistakes and stated that there was no proof that he made the faulty setting since the flight data recorder didn't record such mistakes. The association also believes that the engines went into idle power because of a major system defect. Even when Gopujkar tried to shut his director off, it didn't respond. They also claimed that the time lag of 0.5 seconds for the auto-thrust controls to act proved to be disastrous. [4]

At the time, the Airbus A320 was relatively new, having just been launched in 1988. Its main difference from other aircraft was that it used fly-by-wire (FBW) technology. In a conventional aircraft the pilot was in direct contact with the actuator; so if the pilot opened the throttle more, the actuator immediately gave the pilot more power. In the A320 however, the pilot’s command is first directed to an onboard computer — and the actuator responds only when the computer determines that it is okay to do so. [4]

Before the crash of Flight 605, an Airbus A320 had been involved in another crash, Air France Flight 296. Official investigations determined that the cause of the crash was pilot error. However, the pilot blamed the plane's fly-by-wire system for the crash. This claim caused a major controversy about the Airbus A320. [5]


Less than two years after the crash of Flight 605, the A320 suffered another fatal accident when Air Inter Flight 148 crashed in France killing 87 people. The cause was also a CFIT like 605. The investigation of Flight 148 harshly criticized the Airbus A320's cockpit design. In response, changes were made to the Flight Control Unit panel display; the French aviation safety authority issued 34 recommendations. [3]

See also

Related Research Articles

Japan Airlines Flight 350 Deliberate crash of a Douglas DC-8 on February 9, 1982

Japan Airlines Flight 350 was a McDonnell Douglas DC-8-61, registered JA8061, on a domestic scheduled passenger flight from Fukuoka, Japan, to Tokyo. The airplane crashed 9 February 1982 on approach to Haneda Airport in Tokyo Bay, resulting in 24 fatalities. Flight 350 was Japan Airlines' first crash of the 1980s. The investigation traced the cause of the crash to the deliberate actions of the captain.

Pilot error decision, action or inaction by a pilot of an aircraft

Historically, the term pilot error has been used to describe an accident in which an action or decision made by the pilot was the cause or a contributing factor that led to the accident, but also includes the pilot's failure to make a correct decision or take proper action. Errors are intentional actions that fail to achieve their intended outcomes. Chicago Convention defines accident as "An occurrence associated with the operation of an aircraft [...] in which [...] a person is fatally or seriously injured [...] except when the injuries are [...] inflicted by other persons." Hence the definition of the "pilot error" does not include deliberate crash.

Air France Flight 296 aviation accident at Habsheim air show

Air France Flight 296 was a chartered flight of a new Airbus A320-111 operated by Air France for Air Charter. On 26 June 1988, it crashed while making a low pass over Mulhouse–Habsheim Airport as part of the Habsheim Air Show. Most of the crash sequence, which occurred in front of several thousand spectators, was caught on video. The cause of the crash has been the source of major controversy.

China Airlines Flight 140 April 1994 aviation accident in Nagoya, Japan

China Airlines Flight 140 was a regularly scheduled passenger flight from Chiang Kai-shek International Airport serving Taipei, Taiwan, to Nagoya Airport in Nagoya, Japan.

TAROM Flight 371 Aviation accident

TAROM Flight 371 (RO371/ROT371) was a scheduled international passenger flight, with an Airbus A310 from Otopeni International Airport in Romania's capital Bucharest to Brussels Airport in Brussels, Belgium. The flight was operated by TAROM, the flag carrier of Romania. On 31 March 1995 the Airbus A310-324, registered as YR-LCC, entered a nose-down dive after take off and crashed near Balotești in Romania. All 60 people aboard were killed in the crash.

Gulf Air Flight 072 aviation accident in Bahrain on 23 Aug. 2000

Gulf Air Flight 072 (GF072/GFA072) was a scheduled international passenger flight from Cairo International Airport in Egypt to Bahrain International Airport in Bahrain, operated by Gulf Air. On 23 August 2000 at 19:30 Arabia Standard Time (UTC+3), the Airbus A320 crashed minutes after executing a go-around upon failed attempt to land on Runway 12. The flight crew suffered from spatial disorientation during the go-around and crashed into the shallow waters of the Persian Gulf 5 km from the airport. All 143 people on board the aircraft were killed.

Armavia Flight 967 3 May 2006 air crash in Sochi, Russia

Armavia Flight 967 was a scheduled international passenger flight operated by Armavia from Zvartnots International Airport, Zvarnots in Armenia to Sochi, a Black Sea coastal resort city in Russia. On 3 May 2006, the aircraft operating the route, an Airbus A320-200, crashed into the sea while attempting to go-around following its first approach to Sochi airport, killing all 113 aboard.

2003 Baghdad DHL attempted shootdown incident Attempted shootdown of DHL cargo airliner near Baghdad International Airport

On 22 November 2003, shortly after takeoff from Baghdad, Iraq, an Airbus A300B4-200F cargo plane, registered OO-DLL and owned by European Air Transport was struck on the left wing by a surface-to-air missile while on a scheduled flight to Muharraq, Bahrain. Severe wing damage resulted in a fire and complete loss of hydraulic flight control systems. Because outboard left wing fuel tank 1A was full at takeoff, there was no fuel-air vapour explosion. Liquid jet fuel dropped away as 1A disintegrated. Inboard fuel tank 1 was pierced and leaking.

S7 Airlines Flight 778 aviation accident

S7 Airlines Flight 778(RU778/SBI778) was an Airbus A310-300 on a scheduled domestic passenger flight, flying from Moscow Domodedovo to Irkutsk, when it crashed upon landing at Irkutsk International Airport at 07:44 local time on 9 July 2006. The plane overshot the runway, sliding over several hundred metres of wet runway and grass. It crashed through a concrete barricade, hit a group of private garages and burst into flames. Television pictures showed smoking ruins of the Airbus with only the tail section intact. It took two hours for local firefighters from five different fire stations to extinguish the blaze.

Airbus Industrie Flight 129 1994 Aviation accident

Airbus Industrie Flight 129 was an Airbus Industrie A330-321 test flight that ended in a crash on 30 June 1994 at Toulouse-Blagnac Airport, killing all seven people aboard. The last test flown was to certify the plane's takeoff capability with a single engine failure. It was the first fatal accident involving an Airbus A330 as well as the first hull loss of the type. It remained the only fatal accident involving an A330 until the crash of Air France Flight 447 on 1 June 2009.

Alliance Air Flight 7412 Aviation accident

Alliance Air Flight 7412 was a scheduled domestic passenger flight operated by Alliance Air, a subsidiary of the airline Indian, from Kolkata's Netaji Subhas Chandra Bose International Airport to Indira Gandhi International Airport in Delhi. On 17 July 2000, while on approach to its first stopover in Patna, the Boeing 737-2A8 operating the route nose-dived and crashed into a residential area in Patna, killing 60 people including 5 on the ground.

TAM Airlines Flight 3054 aviation accident

TAM Airlines Flight 3054 (JJ3054/TAM3054) was a regularly scheduled domestic passenger flight from Porto Alegre to São Paulo, Brazil. On the evening of July 17, 2007, the Airbus A320-233 executing the flight overran runway 35L at São Paulo during moderate rain and crashed into a nearby TAM Express warehouse adjacent to a Shell filling station. The plane exploded on impact, killing all 187 passengers and crew on board and 12 people on the ground. The crash surpassed Gol Transportes Aéreos Flight 1907 as the deadliest aviation accident in South American history, and remains the deadliest aviation accident involving the A320 proper worldwide, and the second-deadliest air disaster involving the A320 family, surpassed by the bombing of Metrojet Flight 9268, an A321-231, which crashed in Egypt in October 2015 with 224 fatalities.

Air Inter Flight 148 plane crash in France

Air Inter Flight 148 was a scheduled passenger flight from Lyon–Saint-Exupéry Airport to Strasbourg Airport in France. On 20 January 1992, the aircraft operating the flight, an Airbus A320, crashed in the Vosges Mountains, France, near Mont Sainte-Odile, while circling to land at Strasbourg Airport. 87 of the 96 people on board were killed, while the remaining nine were all injured.

KLM Cityhopper Flight 433 1994 airplane crash

KLM Cityhopper Flight 433 was a Saab 340B, registered as PH-KSH, which crashed during an emergency landing in 1994. Flight 433 was a routine scheduled flight from Amsterdam, the Netherlands, to Cardiff, Wales.

XL Airways Germany Flight 888T Aviation accident

XL Airways Germany Flight 888T (GXL888T) was an Airbus A320 which crashed into the Mediterranean Sea, 7 kilometres off Canet-en-Roussillon on the French coast, close to the Spanish border, on 27 November 2008, killing all seven people on board.

Airblue Flight 202 2010 crash of an Airblue A321-231 near Islamabad, Pakistan, killing 152

Airblue Flight 202 was a scheduled Airblue domestic passenger flight from Karachi's Jinnah International Airport to Islamabad's Benazir Bhutto International Airport. On 28 July 2010, the Airbus A321-231 narrow-body jet airliner serving the flight crashed near Islamabad, the capital of Pakistan, killing all 146 passengers and six crew on board. It is the deadliest air accident to occur in Pakistan to date. The aircraft crashed in the Margalla Hills north of Islamabad after air traffic controllers lost contact with the flight crew during their attempt to land in dense fog and heavy monsoon rain.

Northwest Airlink Flight 2268

Northwest Airlink Flight 2268 was a commuter flight between Cleveland-Hopkins International Airport in Cleveland, Ohio, and Detroit Metropolitan Wayne County Airport in Romulus, Michigan, just outside Detroit. The flight was operated by Fischer Brothers Aviation, doing business as Northwest Airlink, and was operated by a CASA C-212 aircraft. On March 4, 1987, the plane crashed while attempting to land. Nine of the 19 passengers and crew on board were killed in the accident.

Asiana Airlines Flight 214 Transpacific flight that crashed on July 6, 2013

Asiana Airlines Flight 214 was a scheduled transpacific passenger flight from Incheon International Airport near Seoul, South Korea, to San Francisco International Airport in the United States. On the morning of July 6, 2013, the Boeing 777-200ER crashed on final approach into San Francisco International Airport. Of the 307 people on board, three died; another 187 were injured, 49 of them seriously. Among the injured were four flight attendants who were thrown onto the runway while still strapped in their seats when the tail section broke off after striking the seawall short of the runway. It was the first fatal crash of a Boeing 777 since that aircraft type entered service in 1995.

Air Canada Flight 624 2015 crash landing of an Air Canada A320-211 at Halifax International Airport

Air Canada Flight 624 was a scheduled Canadian domestic passenger flight from Toronto Pearson International Airport to Halifax Stanfield International Airport in Halifax, Nova Scotia. During heavy snow and poor visibility, at 00:43 ADT on March 29, 2015, the Airbus A320-211 landed short of the runway and was severely damaged. Twenty-six people were injured.


  1. 1 2 3 Accident description at the Aviation Safety Network
  2. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 "Final report" (PDF). Archived from the original (PDF) on 22 December 2016. Retrieved 29 September 2016.
  3. 1 2 Ranter, Harro. "ASN Aircraft accident Airbus A320-111 F-GGED Strasbourg-Entzheim Airport (SXB)". Retrieved 1 July 2019.
  4. 1 2 3 "Dispute over findings". India Today. Retrieved 27 January 2017.
  5. "Air France Flight 296". ASN.