Birgenair Flight 301
TC-GEN, the aircraft involved in the accident
Accident
Date6 February 1996
SummaryPilot error, Stalled and crashed into the sea due to flight instrument malfunction from pitot tube blockage
Site26 km (16 mi; 14 nmi) NE of Gregorio Luperón International Airport
Puerto Plata, Dominican Republic
19°54′50″N 70°24′20″W / 19.91389°N 70.40556°W / 19.91389; -70.40556
Aircraft
Aircraft typeBoeing 757-225
OperatorBirgenair
ICAO flight No.ALW301
Call signALPHA LIMA WHISKY 301
RegistrationTC-GEN
Flight originGregorio Luperón International Airport
Puerto Plata, Dominican Republic
1st stopoverGander International Airport
Gander, Newfoundland and Labrador, Canada
2nd stopoverBerlin Schönefeld Airport
Berlin, Germany
DestinationFrankfurt Airport
Frankfurt, Germany
Occupants189
Passengers176
Crew13
Fatalities189
Survivors0

Birgenair Flight 301 was a flight chartered by Turkish-managed Birgenair partner Alas Nacionales from Puerto Plata in the Dominican Republic to Frankfurt, Germany, via Gander, Canada, and Berlin, Germany. On 6 February 1996, the Boeing 757-200 operating the route crashed shortly after take-off from Puerto Plata's Gregorio Luperón International Airport.[1][2] All 189 people on board died.[3] The cause was pilot error after receiving incorrect airspeed information from one of the pitot tubes, which investigators believe was blocked by a wasp nest built inside it. The aircraft had been sitting unused for 20 days, and without pitot tube covers in place for the preceding 2 days before the crash.

Flight 301 is the deadliest aviation incident involving a Boeing 757 (followed by American Airlines Flight 965) having a total of 189 fatalities. Furthermore, Flight 301 is the deadliest aviation accident ever to have occurred in the Dominican Republic.[4]

Aircraft and crew

The aircraft was a 11-year-old Boeing 757-225 originally delivered to Eastern Air Lines in February 1985 and registered as N516EA. It was powered by two Rolls-Royce RB211-535E4 engines. After Eastern Air Lines' bankruptcy and subsequent liquidation in 1991, the aircraft was stored at the Mojave Air and Space Port for more than a year. It was purchased by Aeronautics Leasing in April 1992, and then leased to Canadian airline Nationair in May 1992, and stayed with the airline until its demise the following year. It was leased again by the same lessor in July 1993 to Birgenair and then sub-leased to International Caribbean Airways in December 1994, and Birgenair operated the airliner until it crashed.[5][6]

The crew consisted of 11 Turks and 2 Dominicans. The captain was Ahmet Erdem (61), with 24,750 flight hours of experience (including 1,875 hours on the Boeing 757). The first officer was Aykut Gergin (34). He had 3,500 hours of flying experience, though only 71 hours were on the Boeing 757. The relief pilot was Muhlis Evrenesoğlu (51). He had 15,000 flight hours of experience (with 121 of them on the Boeing 757).[7]: 4–8 

Passengers

The passengers consisted mainly of Germans, along with nine Poles including two Members of the Parliament, Zbigniew Gorzelańczyk of the Democratic Left Alliance, and Marek Wielgus of the Nonpartisan Bloc for Support of Reforms (BBWR).[2][8] Most of the passengers had booked Caribbean package holidays with Öger Tours; Birgenair held 10% of Öger Tours.[9]

Nationality Passengers Crew Total
 Germany 167-167
 Poland 9-9
 Turkey -1111
 Dominican Republic -22
Total17613189

Accident

During takeoff roll at 23:42 AST (03:42 UTC),[7]: 1  the captain found that his airspeed indicator (ASI) was malfunctioning but he chose not to abort the takeoff.[10] The first officer's ASI was functional, though subsequent warning indicators would cause the aircrew to question its veracity as well. The aircraft took off normally at 23:42 AST, for the first leg of the flight. At 2,500 feet (760 m), the flight switched to main air traffic control and was instructed to climb to flight level 280 (28,000 ft or 8,500 m). The autopilot was engaged 1 minute and 30 seconds into the flight.

Approximately 10 seconds later, two warnings: rudder ratio and Mach airspeed trim appeared. The crew was at that point becoming increasingly confused, because the captain's ASI showed over 300 knots (560 km/h; 350 mph) and was increasing and the first officer's ASI, which was correct, was showing 220 knots (410 km/h; 250 mph) and decreasing.

Then, the captain assumed that both ASI are wrong, and decided to check circuit breakers. When the first circuit breaker was checked, the overspeed warning appeared, as the captain’s ASI, the primary source of the information about airspeed for autopilot, was showing airspeed near 350 knots (650 km/h; 400 mph) and increasing. Then, the second circuit breaker was pulled to silence the warning. As the plane was climbing through 4,700 feet (1,400 m), the captain's ASI read 350 knots (650 km/h; 400 mph). The autopilot, which was taking its airspeed information from the same equipment that was providing faulty readings to the captain's ASI, increased the pitch-up attitude and reduced power in order to lower the plane's airspeed. The first officer's ASI was giving a correct reading of 200 knots (370 km/h; 230 mph) and was still decreasing.[7]: 16  With all contradictory warnings given by the plane, the confused captain decided to reduce thrust of the plane, believing it was flying too fast.[7]: 18 

This action immediately triggered the 757's stick-shaker stall alert, warning the confused pilots that the aircraft was flying dangerously slow. Also, the autopilot disengaged. As the plane was closing to stall, its path became unstable and it started descending. Meanwhile, the controller, still unaware of any problems, called the flight, but, as the crew struggled with problems, the first officer said "Standby". First officer and relief pilot, aware of the scale of the problem, were suggesting various methods to recover from the stall, but the confused captain ignored all of them. About 20 seconds before crash, the captain finally attempted to recover from the stall by increasing the plane's thrust to full, but as the aircraft was still in a nose up attitude, the engines were prevented from receiving adequate airflow required to match the increase in thrust. The left engine flamed out, causing the right engine, which was still at full power, to throw the aircraft into a spin. Moments later, the plane inverted.[11] At 23:47 AST, the Ground Proximity Warning System (GPWS) sounded an audible warning, and eight seconds later the plane crashed into the Atlantic Ocean. All 176 passengers and 13 crew members died on impact.

Investigation and final report

The Dominican Republic government's General Directorate of Civil Aviation (Spanish: Dirección General de Aeronáutica Civil) (DGAC) investigated the accident and determined the probable cause to be:[12]

The crew's failure to recognize the activation of the stick shaker as a warning of imminent entrance to the stall, and the failure of the crew to execute the procedures for recovery from the onset of loss of control.

Investigations later showed that the plane was actually travelling at 220 knots (410 km/h; 250 mph) at the time of the accident.[7] The investigation concluded that one of the three pitot tubes, used to measure airspeed, was blocked.

None of the pitot tubes were recovered so investigators were unable to determine for certain what caused the blockage. Investigators believe that the most likely culprit was the black and yellow mud dauber (Sceliphron caementarium), a type of solitary sphecid wasp well known to Dominican pilots, which makes a cylindrical nest out of mud and tends to establish a nest in artificial, cylindrical structures. According to the final report, section 2.3 – "Aircraft maintenance factors", the aircraft had not flown in 20 days, however, this was not the duration for which pitots remained uncovered, but was evidently enough time to allow the wasps the opportunity to construct nests in the tubes.[7]: 20 [13][14] According to Cetin Birgen, president and CEO of Birgenair, the pitot covers were removed two days before the accident in order to conduct an engine test run.[7]: 20 [15]

The investigation noted a number of other factors and suggested changes.[10] They reconfirmed that the pilots should have followed existing procedures and aborted the takeoff when they found that their airspeed indicators were already in significant disagreement as the plane accelerated down the runway. Results from a number of simulations with experienced pilots found that the combination of the overspeed warning horn and underspeed stick shaker while in flight was an overly confusing contradictory set of messages for many pilots; the FAA issued a directive that pilot training would now include a blocked pitot tube scenario. The FAA research had also revealed that the situation also led to multiple other contradictory warning sounds and warning lights that increased the demands on the pilot to fly the plane. The FAA asked Boeing to change some of those warnings, as well as add a new warning to tell both pilots that their instruments disagree, add the ability for the pilots to silence troublesome alarms, and to modify the system so that the pilots can choose which pitot tube the autopilot uses for airspeed readings.[10]

Memorial for the victims of Birgenair Flight 301 in Puerto Plata
Memorial for the victims of Birgenair Flight 301 in Frankfurt's main cemetery

Aftermath

Shortly after the crash of flight 301, the airline's overall image and profits became heavily damaged, and some of its planes were grounded at the same time. Birgenair went bankrupt in October of the same year as there were concerns about safety after the accident, causing a decline in passenger numbers. The crash and ensuing negative publicity both contributed to Birgenair's bankruptcy.[16]

  • The events of Flight 301 were featured in "Mixed Signals", a Season 5 (2007) episode of the Canadian TV series Mayday[10] (called Air Emergency and Air Disasters in the U.S. and Air Crash Investigation in the UK and elsewhere around the world). The dramatization was broadcast with the title "The Plane That Wouldn't Talk" in the United Kingdom, Australia and Asia.
  • The British television series Survival in the Sky featured the crash in its first episode, titled "Blaming the Pilot" (1996).
  • Berlin – Schicksalsjahre einer Stadt (Berlin - Fateful Years of the City: Series 4, Episode 6) interviewed the Berlin parents of one of 167 German passengers who died in the flight crash.

See also

Similar events

  • Later the same year (1996), Aeroperú Flight 603, also operated with a Boeing 757-200, suffered a similar but far more difficult situation (static ports blocked by tape, rendering all airspeed indicators and pressure altimeters unusable) and crashed in the ocean off Peru, killing all 70 people aboard.
  • On June 1, 2009, Air France Flight 447 stalled and crashed over the Atlantic Ocean after pilots mishandled procedures when managing to deal with pitot tubes jammed by ice, causing them to stall the aircraft.
  • On 29 October 2018, Lion Air Flight 610 suffered an incorrect airspeed data due to an MCAS design flaw, pilot error, and incorrect maintenance shortly after taking off, crashing into the Java Sea near Jakarta, killing all 189 onboard.

References

  1. ↑ Pope, Hugh (10 February 1996). "Crash plane may not have been serviced". The Independent. Retrieved 19 November 2009.
  2. 1 2 "Rescuers call off search in plane crash". CNN. 8 February 1996. Archived from the original on 13 April 2005. Retrieved 19 November 2009.
  3. ↑ Wald, Matthew L. (8 February 1996). "German Tourist Plane Crashes; 189 Feared Dead". The New York Times. ISSN 0362-4331. Retrieved 26 January 2021.
  4. ↑ Accident description at the Aviation Safety Network. Retrieved on 21 July 2006.
  5. ↑ "TC-GEN Birgenair Boeing 757-200". www.planespotters.net. Retrieved 26 January 2021.
  6. ↑ "Birgenair TC-GEN (Boeing 757 - MSN 22206) (Ex 8P-GUL C-FNXN N516EA N7079S)". www.airfleets.net. Airfleets aviation. Retrieved 26 January 2021.
  7. 1 2 3 4 5 6 7 "Reporte Final Accidente Aereo Birgenair, Vuelo ALW-301, Febrero 06,1996" [Final Report of the Birgenair Air Crash, Flight ALW-301, 6 February 1996] (PDF) (in Spanish). DGAC. 25 October 1996. Archived (PDF) from the original on 3 March 2016. Retrieved 27 August 2014.
  8. ↑ Clary, Mike (8 February 1996). "Dominican Jet Crashes in Sea; 189 Feared Dead". Los Angeles Times. Retrieved 25 February 2018.
  9. ↑ Karacs, Imre (9 February 1996). "Bonn grounds 757 as crash mystery grows". The Independent. Retrieved 19 November 2009.
  10. 1 2 3 4 "Mixed Signals". Mayday. Season 5. Episode 8. 2007. Discovery Channel Canada / National Geographic Channel.
  11. ↑ Beveren, Tim van (1996). Runter kommen sie immer: die verschwiegenen Risiken des Flugverkehrs [They always come down: the hidden risks of air traffic] (in German). Campus-Verlag. pp. 258–271. ISBN 978-3-593-35254-1.
  12. ↑ Walters, James M.; Sumwalt III, Robert L. (16 February 2000). Aircraft Accident Analysis: Final Reports. McGraw Hill Professional. p. 98. ISBN 978-0-07-137984-7. Retrieved 11 May 2011 – via Google Books. Souffront, Emmanuel T., Presidente, Junta Investigadora de Accidentes Aéreos (JIAA) of the Director General of Civil Aviation (DGAC) of the Dominican Republic. 1996. Aircraft accident information. Dominican Republic Press Release—Factual Information, 1 & 18 March 1996.
  13. ↑ "Erroneous airspeed indications cited in Boeing 757 control loss" (PDF). Flight Safety Foundation. October 1999. p. 2. Retrieved 27 August 2014. It had not been flown for 20 days before the accident...Investigators believe that the engine [covers] and pitot covers were not installed before or after the engine ground test.
  14. ↑ DGAC final report 1996, p. 20, section 2.3"Durante el tiempo que duró en tierra, dicho avión no fue volado en veinte (20) dias. Durante este periodo se ejecutó una inspección de motores que requirió una prueba en tierra del motor antes del despegue. Los investigadores creen que las cubiertas de los motores y cubiertas de los pitot no fueron instaladas antes ó después de la prueba en tierra de los motores. [English: During the time that the aircraft was on the ground, it is believed that the plane had not flown for twenty (20) days. During this period, an engine inspection was performed that required an engine ground test before the next takeoff. Investigators believe that the engine and pitot covers were not installed before or after the engine ground test.]"
  15. ↑ Birgenair comments 1996, pp. 16–17"the aircraft was not on the ground for 20 days, but only for 12 days prior to the ill-fated flight. The pitot-tubes were covered prior to an engine test run which took place 2 days prior to the ill-fated flight. It was known by the BIRGENAIR mechanics that the airplane should be returned to Turkey in a ferry flight within the next 3 days. If therefore the pitot-tubes had not been covered after the engine test run for 2 days, according to the BOEING procedures, set forth in the BOEING Maintenance Manual, this might be justified." ... "Despite these irritating and even conflicting procedures set forth in BOEING's 757 Maintenance Manual and the Maintenance Planning Document, a blockage of the pitot-tube might occur even within any period of stay on the ground and [installation of pitot-covers] should therefore be clearly required for all periods of stay on the ground."
  16. ↑ Roelen, Alfred Lambertus Cornelis (2008). Causal Risk Models of Air Transport: Comparison of User Needs and Model Capabilities. IOS Press. p. 39. ISBN 978-1-58603-933-2.

"Reporte Final Accidente Aereo Birgenair, Vuelo ALW-301, Febrero 06,1996" [Final Report of the Birgenair Air Crash, Flight ALW-301, 6 February 1996] (PDF) (in Spanish). DGAC. 25 October 1996. Archived (PDF) from the original on 3 March 2016. Retrieved 27 August 2014.

"Birgenair Comments" (PDF). Birgenair. June 1997. pp. 67–68 of PDF (item 19). Archived from the original (PDF) on 3 March 2016. Retrieved 27 August 2014.

External image
image icon Pre-crash photos of the 757 carrying Flight 301 on Airliners.Net

Birgenair Flight 301 Monument Puerto Plata

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.