FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Birgenair Flight 301

6 Feb 1996 · Atlantic Ocean, 26 km NE of Gregorio Luperón International Airport, Puerto Plata, Dominican Republic

Alas Nacionales on behalf of Birgenair Boeing 757-225 · Stalled and crashed after takeoff due to pitot tube blockage and pilot error

From Gregorio Luperon International Airport (POP) to Frankfurt Main Airport (FRA)

Report a problem

Event

NTSB case
DCA96RA030
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Unknown · led by another country; figures from NTSB notifications
Event fatalities
189 · all aircraft and ground
Ground fatalities
Unknown
Occupants
189
Survivors
0
InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
0 serious · 0 minor (NTSB)
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Not recorded

Boeing 757-225

Flight
KT301
Aircraft type
Boeing 757
Category
Airplane · from aircraft type
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
TC-GEN
Onboard fatalities
189
Route
From Gregorio Luperon International Airport (POP)To Frankfurt Main Airport (FRA)
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 129: Foreign
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Not recorded
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Not recorded
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Not recorded

Cause areas

  • Aircraft › Aircraft systems
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

From the investigation findings the Wikipedia article reports, sorted into the NTSB's cause areas with AI assistance.

Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.

From the Wikipedia article

Birgenair Flight 301 was a chartered flight 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 operating the route crashed shortly after take-off from Puerto Plata's Gregorio Luperón International Airport, killing all 189 people on board. 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 two days preceding the crash.

Flight 301 is tied with American Airlines Flight 77 as the deadliest aviation incident involving a Boeing 757, having a total of 189 fatalities. Furthermore, Flight 301 is the deadliest aviation accident ever to have occurred in the Dominican Republic.

Accident

During takeoff roll at 23:42 AST (03:42 UTC), the captain found that his airspeed indicator (ASI) was malfunctioning but he chose not to abort the takeoff. The first officer's ASI was functional, though subsequent warning indicators caused 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 2500 ft, the flight switched to main air traffic control and was instructed to climb to flight level 280 (28,000 ft). 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 kn and increasing, and the first officer's ASI, which was correct, was showing 220 kn and decreasing.

Then, the captain assumed that both ASI were wrong and decided to check the 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 kn and increasing. Then the second circuit breaker was pulled to silence the warning. As the plane was climbing through 4700 ft, the captain's ASI read 350 kn. 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 kn and was still decreasing. With all contradictory warnings given by the plane, the confused captain decided to reduce thrust of the plane, believing it was flying too fast.

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 close to a 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, "Stand by". The 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. 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. There were no survivors.

Investigation and cause

Investigation and final report

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

Investigations later showed that the plane was actually travelling at 220 kn at the time of the accident. 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 a black and yellow mud dauber (Sceliphron sp.), 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 there was evidently enough time to allow the wasps the opportunity to construct nests in the tubes. 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.

The investigation noted a number of other factors and suggested changes. 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.

Text from the Wikipedia article “Birgenair Flight 301” (revision 1374846865, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article

Sources

Wikipedia article: Birgenair Flight 301
Article
Birgenair Flight 301
Revision
1374846865 · 2026-09-14 · retrieved 2026-09-18
Wikidata
Q435223
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA96RA030
Event ID
20001208X05235
Case number
DCA96RA030
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Where each value comes from
Record
Wikipedia article "Birgenair Flight 301" (page 6049533, revision 1374846865); merged with NTSB case DCA96RA030 (events / aircraft)
Date
Wikipedia infobox: date
Place and country
Wikipedia infobox: site
Map position
Wikipedia: Wikipedia article coordinates
Aircraft, operator and route
Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports); gaps and aircraft details from NTSB record DCA96RA030
Operation
airline flight number in the infobox
Fatalities
Wikipedia: Wikipedia infobox: aircraft fatalities
Ground fatalities
Wikipedia: not stated in the Wikipedia infobox
Summary
Wikipedia infobox: summary
Source notes (2)
  • One occurrence in two sources, merged: the Wikipedia article "Birgenair Flight 301" and NTSB case DCA96RA030, matched by the same aircraft registration and date. For this event outside the United States Wikipedia's values are used where the two differ; each value names its source.
  • Filled from the NTSB case API where the bulk record had no value: local date. Values present in the bulk record are kept.