Alliance Air Flight 7412

Alliance Air Flight 7412

An Alliance Air Boeing 737-2A8 similar to the one involved in the crash
Accident summary
Date 17 July 2000
Summary Pilot violating approach procedure which leads to loss of control
Site Patna, Bihar, India
Passengers 52
Crew 6
Injuries (non-fatal) 8 (5 on ground)
Fatalities 60 (5 on ground)
Survivors 3 (initially 7)
Aircraft type Boeing 737-2A8
Operator Alliance Air
Registration VT-EGD
Flight origin Netaji Subhash Chandra Bose International Airport, Kolkata, India
Stopover Lok Nayak Jayaprakash Airport, Patna, India
Last stopover Chaudhary Charan Singh International Airport, Lucknow, India
Destination Indira Gandhi International Airport, Delhi, India

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

The final report, investigated by the Indian AAIB (Aircraft Accident Investigation Bureau), concluded that the cause of the crash was due to pilot error.[1] Initially, the Bihar Air Traffic Controller was blamed as the cause of the accident. Even after the official final report was published, most residents live near the crash site and the relatives of those who perished on the flight believed that ATC error was the cause of the accident.[2]

The plane crash was the deadliest plane crash in year 2000 in India, and remained as the deadliest crash in India for nearly a decade until Air India Express Flight 812 which crashed in Mangalore on 12 May 2010, killing 158 people. Subsequently, it was the 26th worst accident involving a Boeing 737-200 and the 13th deadliest plane crash in India.[3]

Accident

Flight 7412 departed Calcutta (Kolkata) at 06:51 on July 17, 2000, for a flight to Delhi, with stops at Patna and Lucknow. Patna ATC asked the aircraft at 07:17 to report for descent and also to check descent traffic with Kolkata Area Control. The aircraft soon responded that Kolkata had reported negative traffic. Flight 7412 was then cleared for descent to FL75 and asked to report 25 NM and the same was reported by the aircraft at 07:26. Flight 7412 was cleared to descend to 4000 ft. and was asked to report for approach runway 25.[4]

At 07:28, Flight 7412 reported commencing the turn and at 07:31 reported crossing the airport area and coming up on the localiser. Flight 7412 was then asked to descend to 1700 ft.The crew had been cleared to land at runway 25 at Lok Nayak Jayaprakash Airport at Patna when the pilots requested a 360-degree orbit due to the flight being high on the approach. Permission was granted and a left turn was initiated. During the left turn, the aircraft stalled. The plane then grazed a few single-storied houses in a government residential housing estate and crashed in a government residential colony behind Gardani Bagh Girls School at Anishabad, which is located about 2 km southwest of the Patna Airport.[5] The aircraft broke into four pieces.

When the aircraft struck the residential quarters and the ground, the impact was severe. The intensity of post impact fire was also severe. Initially, seven passengers were extricated alive. Of them six were seriously injured. Miraculously, one of the passengers walked out of the wreckage without much injury, even though, he had minor concussion and was treated later. Of the six injured passengers, four died subsequently. Two passengers recovered completely after treatment.[6]

The airport ambulance had proceeded to the crash site along with the CFTs. Two injured passengers were transported to the PMCH in the first instance. Subsequently, the second ambulance from the airport was also pressed into service to transport the remaining injured passengers for medical aid. Shortly after the arrival of the airport ambulance, ambulances from other assisting agencies also arrived and helped in removing all the injured for medical aid.[6]

Failures in Rescue Services

The accident site was 5–6 km from the airport. The fire personnel reached the site in 5 to 6 minutes (local residents stated that the tenders reached only after 15–20 minutes). The first Crash Fire Tender (CFT) laid two hoses and began to fight the fire; however it failed in 3 minutes. After failing in their efforts to rectify the fault, the CFT crew had to call a mechanic from the airport and the CFT was put back into operation after an hour. However, after a few minutes of operation it went back to the airport to refill water. On the way it broke down twice.[7]

The second CFT after a few minutes of operation had to return to the airport to refill water. The crowd that collected within a short time was unmanageable and definitely hampered the rescue operations. According to witnesses, crowd tempers ran high and there was a general tendency to target anybody in uniform or position of authority with verbal abuse and physical violence. At times there were hundreds of people trying to climb on to the rescue vehicles to get a better view. It was only after the arrival of the Bihar military police jawans and the army contingent that some semblance of crowd control was achieved.[7]

Aircraft

The aircraft involved in the accident was a Boeing 737-200. Boeing 737-200 is a twin engine jet transport airplane manufactured by Boeing Commercial Airplane Company, USA. It is designed to operate over short to medium ranges at cruise speeds of approximately 950 Kilometers/hour (Kmph). Two P&W JT8D/17A engines power the aircraft, each developing approximately 16,000 Pounds (lbs) of thrust at sea level.[4]

The aircraft involved in the accident was registered in India as VT-EGD with a serial number of MSN22280. The aircraft was manufactured in 1980 and sold to Indian Airline. It was subsequently leased to Alliance Air in 1999.[4]

Investigation

The aircraft in question, VT-EGD, had been involved in an earlier accident. On January 15, 1986, the pilot of flight 529 attempted to land at Tiruchirapalli in conditions below weather minima (reported Wx was exactly the minima). During a go-around (wave-off, just before touch down) the wing contacted the runway due to an excessive bank angle (the delay in spool up times for both engines were more than 5 seconds apart with the right engine slow). The HIALS was not switched on at the time 529 was approaching and the ATC anemometer was unserviceable. The wing was substantially damaged, but there were no injuries among the 6 crew and 122 passengers. The pilot displayed great skill in manually flying the B737 at FL100 and diverted to Chennai and landed safely with flight controls in "manual reversion" on runway 07 [5] The aircraft was to be phased out by the end of the year per Indian government guidelines which do not allow aircraft over 20 years old to operate in Indian airspace.[8]

Investigators ruled out terrorism as the cause of the accident. They didn't find any signs of explosion nor a fire had occurred in flight. Both pilots were not intoxicated and fully aware at the time of the crash.[9]

The flight crew consisted of Captain Manjit Singh Sohanpal and co-pilot Arvind Singh Bagga. A criminal case, filed against them based on the statement of a surviving passenger, was later withdrawn.[10][11] Both Captain Sohanpal and co-pilot Bagga died in the accident.[12]

A TAESA Boeing 737 with the rudder visible. The rudder could be seen in the tail in yellow.

Investigators later conducted an observation with its Rudder Power Control Unit (PCU). The Main Power Control Unit (MPCU) of the rudder has been a subject of intense debate and discussions and has undergone mandatory modifications as a result of some previous accident investigations. The PCU has responsible for several high profile crashes, such as United Airlines Flight 585, USAir Flight 427, and Eastwind Airlines Flight 517. Flight 7412 nose-dived before the crash, as well as two previous crashes, Flight 585 and Flight 427. The rudder locked up in a particular direction, and reversal of rudder to that of the commanded position (anomalous rudder movements such as un-commanded movements). These have been attributed to the secondary slide jamming with the primary slide due to contamination or adverse buildup of tolerances during manufacture. However, investigators later dismissed it and ruled out the failure of the PCU as the cause, and concluded that it was serviceable and was in good condition.[9]

Animation of an accelerated stall. The aircraft is flying at constant speed (IAS or Indicated Air Speed) along a circular trajectory with decreasing turn radius (i.e. is turning and increasingly tightening the turn). In order to keep the trajectory, more and more lift is needed (since it must equal the sum of weight and centrifugal force), which can be achieved by increasing the Angle of Attack (that is pulling back on the stick). When the critical Angle of Attack is reached, any further increase results in a stall, even if the airspeed has not changed. Note that a stall would not occur if the aircraft was flying straight and level at the same speed, hence the term accelerated stall.

As both black boxes were found by search and rescue team, investigators teared both black boxes and analyze its content. The results shown that the engines were at idle thrust throughout the descent profile and the speed was continuously reducing. It was not clear why the engines were kept at idle thrust even after selecting Flaps 40. It was perhaps because the aircraft was higher than normal on approach. If the intention was to regain the correct glide path then classic flying technique would have required the Pilot to maintain speed by reducing the angle of attack by pushing the control column forward while allowing the aircraft to regain the correct glide path with an increased rate of descent.[9]

When it was realized that the aircraft was too high 10 effect a landing, a 360° orbit was requested. The speed at this time was 119 kts VREF that was the landing speed. The procedure to carry out a 360° turn was not an authorised procedure as per the Alliance Air Operations Manual and could have caused considerable confusion in the mind of First Officer Arvind. It was clear from the FDR recording that the aircraft was not following the ILS procedure but Patna ATC was being given the impression that the aircraft was doing so.

At any busy airport with some more traffic, this would have been unthinkable and would have created a conflict. However, there was no other traffic for miles around Patna and ATC gave the permission, only after confirming that the crew had the airfield in sight. Captain Manjit tried to resolve this issue without any discussion with Fist Officer Arvind . The atmosphere in the cockpit was relaxed and tension free till 15 secs before the crash. The first sign of anxiety became apparent only when Arvind called for raising the landing gear.[9]

Investigators conducted a simulation of the crash and found that at 16 seconds before the crash, the spooling up of the engine had reduced the rate of descent. However, eight seconds later when the Flap Lever was moved to 15, the rate of descent increased as seen by the steepening of the slope of the curve. This was caused by loss of lift due to the reduction in wing area as the flaps moved up from 40 to 15. Six seconds after the Flap Lever was moved to 15, the rate of descent increased even further indicating that the flaps were close to 15 position and the wing no longer generated enough lift to support the aircraft. This high rate of descent together with the high Nose Up pitch attitude held by the Pilot resulted in the aircraft attaining a very high Angle of Attack of the order of 26º. The aircraft had completely stalled by this time and even though thrust had been increased to the maximum possible on both engines, recovery was not possible.[9]

The final investigation noted pilot error as the cause of the plane crash.[13] According to the panel, the crew had not followed the correct approach procedure, which resulted in the aircraft being high on approach. The engines had been kept at idle thrust, which allowed the air speed to decline below the allowed minimum for approach and caused the aircraft to stall. The inquiry also pointed out that the airport had "several operational constraints, resulting in erosion of safety margins for operation of Airbus 320s and Boeing 737s."

Controversy

There were a number of aspersions cast on the maintenance of flights by Alliance Air, with the then civil aviation minister Sharad Yadav reportedly unhappy with the maintenance of the aircraft [14] and asking for replacement of a number of additional aircraft.[14] Some reports even claimed that one of the engines was on fire before the crash.[15] However, the investigation clearly said the aircraft was fully airworthy and was properly maintained.[16]

See also

References

  1. ↑ http://web.archive.org/web/20020802095528/http://civilaviation.nic.in/coi-fin/contents.htm
  2. ↑ Swaroop, Vijay (19 July 2001). "Memories of plane crash still haunt Patnaites". Times of India. Retrieved 3 April 2016.
  3. ↑ "Accident description".
  4. 1 2 3 http://web.archive.org/web/20020705084734/http://civilaviation.nic.in/coi-fin/report.htm#FACTUAL INFORMATION
  5. 1 2 Accident description at the Aviation Safety Network
  6. 1 2 http://web.archive.org/web/20020705084734/http://civilaviation.nic.in/coi-fin/report.htm#SURVIVAL ASPECTS
  7. 1 2 http://medind.nic.in/iab/t02/i1/iabt02i1p66o.pdf
  8. ↑ rediff.com: Alliance Air Boeing 737 crashes near Patna
  9. 1 2 3 4 5 http://web.archive.org/web/20020705084734/http://civilaviation.nic.in/coi-fin/report.htm#FLIGHT RECORDERS
  10. ↑ rediff.com: Alliance Air Boeing 737 crashes near Patna
  11. ↑ rediff.com: FIR against Alliance Air pilot, co-pilot withdrawn
  12. ↑ rediff.com: Alliance Air Boeing 737 crashes near Patna
  13. ↑ http://www.rediff.com/news/2001/mar/31crash.htm.
  14. 1 2 rediff.com:Minister unhappy with Alliance Air maintenance
  15. ↑ rediff.com: Alliance Air Boeing 737 crashes near Patna
  16. ↑ rediff.com: Patna crash blamed on pilot error

External links

Coordinates: 25°36′39″N 85°08′34″E / 25.61083°N 85.14278°E / 25.61083; 85.14278

This article is issued from Wikipedia - version of the Sunday, April 17, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.