Fatal accident · Dominican Republic
Birgenair Boeing 757 crash off Puerto Plata, Dominican Republic
Birgenair Flight 301, a Boeing 757-225 (TC-GEN) flying a charter for Alas Nacionales, crashed into the Atlantic Ocean about 14 nautical miles northeast of Puerto Plata, Dominican Republic, on 6 February 1996. All 189 people on board died. The Dominican Republic's JIAA investigated, with NTSB participation, and published a final report.
This is one of 1 Alas Nacionales, leased from Birgen Air fatal accidents on record. See also all plane crashes in 1996.
A climb that ended in the Atlantic five minutes after takeoff
Birgenair Flight 301 took off from General Gregorio Luperón International Airport at Puerto Plata at about 23:42 local time on 6 February 1996. The Boeing 757-225, registration TC-GEN, was bound for Frankfurt with a planned fuel stop in Canada.
During the climb the crew received unreliable airspeed indications and conflicting warnings. Flight recorder data showed thrust and pitch changes, then the autopilot disconnected and control was lost.
The aircraft reached about 7,300 feet and then descended in a steep nose-down attitude. It struck the ocean roughly 14 nautical miles northeast of Puerto Plata at about 23:47 local time. The aircraft was destroyed. There were no survivors and no deaths on the ground were reported.
A Turkish carrier's 757 flying a charter for Alas Nacionales
The Boeing 757-225 was operated by Birgenair on a charter for Alas Nacionales, and the FAA identifies the flight as ALW-301. A verified manufacture date for TC-GEN was not found in the sources reviewed, so the age of the aircraft is not stated here.
Aboard were 176 passengers and 13 crew, 189 people in all. All 189 died. For wider context on how types and operators compare, see accident history by aircraft model.
What the Dominican investigation found
The Dominican Republic's Junta Investigadora de Accidentes Aéreos (JIAA) led the investigation of the Birgenair 757 crash. The U.S. National Transportation Safety Board took part under Annex 13, the international rules for accident investigation, because the aircraft was a U.S.-built type.
The JIAA gave two probable causes:
- The flight crew did not recognize that the stick shaker activation was a warning of an imminent aerodynamic stall.
- The crew did not carry out the proper procedures to recover from the loss of control.
It listed crew confusion, caused by erroneous airspeed indications and an associated overspeed warning, as a contributing factor. For how such findings are worded, see what probable cause means.
The blocked pitot system behind the false airspeed
Investigators associated the airspeed anomaly on TC-GEN with a blocked pitot system. The FAA's summary says they concluded that pitot covers had not been properly used while the aircraft was out of service for about 20 days.
A popular explanation holds that insects built a nest in the probe. The official summaries reviewed do not state that as a definitive finding, so it is not treated as one here.
The crash is a documented case of loss of control in flight following faulty instrument data, and it also sits among mechanical failure crashes in the sense that the faulty indications began with a blocked sensor.
TC-GEN was built in 1985 and had an earlier tail strike
Birgenair Flight 301 was flown by TC-GEN, a Boeing 757-225 that the JIAA report dates to 1985. The aircraft was about 10 years and 10 months old at the time of the crash. It had logged approximately 29,000 flight hours and 4,000 cycles.
The report records that TC-GEN had earlier suffered tail-strike damage and had undergone structural repair. It also notes earlier maintenance on the left captain's pitot-static and airspeed system. The report does not say the earlier damage caused the accident.
The three pilots had very different amounts of time on the type. The figures come from the crew biographies in the JIAA report:
- Captain Ahmet Erdem: 24,750 total hours, 1,875 of them on the Boeing 757.
- First officer Aykut Gergin: 3,500 total hours, 71 on the 757.
- Relief pilot Muhlis Evrenesoğlu: 15,000 total hours, 121 on the 757.
All three held the medical authorizations required for their duties. The report also concluded that the captain's left pitot tube was blocked, most probably by an insect nest or similar contamination, but it did not settle the exact mechanism with certainty.
A bad airspeed reading on the takeoff roll, and 350 knots that was really 220
On the Birgenair Flight 301 takeoff from Puerto Plata runway 08, the problem started before the 757 left the ground. The JIAA report's cockpit voice recorder shows the captain saying his airspeed indicator was not working properly during the roll. The other airspeed indications did not show the same fault, and the crew did not reject the takeoff.
The aircraft climbed normally at first. Then the captain's indicator began to read high while the real speed fell. The autopilot and autothrottle stayed engaged and acted on that false figure. Pitch and thrust moved the aircraft toward a low-energy condition.
Around 23:46 the crew began comparing the conflicting indications. Passing about 4,700 feet, the captain's indicator showed roughly 350 knots. The actual airspeed was about 220 knots.
Shortly before 23:47 the stick shaker activated. The crew did not carry out the prescribed stall recovery. They disconnected the autopilot and autothrottle and applied thrust, but control was already lost. The ground-proximity warning sounded "Whoop whoop, pull up" at 23:47:17. The aircraft hit the sea about eight seconds later.
Some published timelines are given in UTC, which puts them four hours off the local times above. One summary says the crash came about eight minutes after takeoff. This page keeps the report's local times, which give about five.
Night search off Puerto Plata found no one alive
After Birgenair Flight 301 went into the sea off Puerto Plata, Dominican naval and other local emergency units were sent out once contact was lost and the crash was reported. The JIAA report describes difficult night conditions for a marine search. Rescue craft and divers reached the crash area only after a substantial interval. No one was recovered alive.
The conditions at the time were night visual meteorological conditions. The report records no severe weather, thunderstorm or significant turbulence in the area, and the investigation treated weather as not causal. The dark sky did take away outside visual references while the crew was dealing with the failure.
The report's manifests list occupants from several countries. The 13 crew were 11 Turkish nationals and 2 Dominican nationals, according to Wikipedia's summary of the manifest. The passengers included Dominican, German, Polish and Turkish nationals, among others listed individually in the report. The report's seating and recovery material shows where victims were found, but with no survivors there is no survivor seating pattern to analyze.
Popular accounts often round the rescue times or merge the first response with the later recovery work. The JIAA report is the source for the sequence.
Birgenair rejected the finding that the crew was at fault
The Dominican report on Birgenair Flight 301 did not go unchallenged. Birgenair objected to the Dominican authority's control of the investigation. It asked for evidence and records to be handed over for review under Turkish authority. It also argued that blaming the crew for not understanding the stick shaker was not justified. Turkey, as the state of registry, took part or sought access. The report is generally dated 25 October 1996.
Nobody disputed that the pitot system gave false readings. The argument was over where responsibility lay. The JIAA put the crew's failure to diagnose and recover from the stall as the probable cause and the blocked pitot tube as a contributing factor. Birgenair said the report gave too much weight to crew performance and too little to the unreliable indications and the warning design. The sources reviewed do not show any Turkish or Boeing finding that replaced the JIAA report. They also do not show a reopened inquiry. For how causes are decided, see how investigators determine the cause.
The recommendations went to Boeing 757 and 767 operations. They covered:
- a flight manual note that simultaneous MACH/SPD TRIM and RUDDER RATIO warnings can mean an airspeed discrepancy
- a caution alert for erroneous airspeed
- a detailed procedure for identifying and eliminating a bad airspeed indication
- simulator training on blocked pitot and unreliable airspeed, including on takeoff
- crew resource management training and operator-specific training manuals
The sources document these recommendations more clearly than any single rule that followed from them. Final legal outcomes and any official memorial are not documented in the sources reviewed.
Status of the investigation
The investigation into the Birgenair Flight 301 crash is complete. The JIAA issued a final report, and the NTSB took part but was not the state-of-occurrence authority. The NTSB also issued recommendations that the FAA has published. To understand the stages of such work, see preliminary vs final accident report.
A full weather observation for the time of the crash was not found in the sources reviewed, and weather is not part of the stated probable cause.
Questions people ask about this accident
What happened to Birgenair Flight 301?
Birgenair Flight 301, a Boeing 757-225, crashed into the Atlantic Ocean about 14 nautical miles northeast of Puerto Plata, Dominican Republic, on 6 February 1996 after unreliable airspeed indications led to a loss of control.
How many people died in the Birgenair Flight 301 crash?
All 189 people on board died: 176 passengers and 13 crew. No deaths on the ground were reported.
Where did Birgenair Flight 301 crash?
The Boeing 757 crashed in the Atlantic Ocean roughly 14 nautical miles northeast of Puerto Plata, shortly after departing Gregorio Luperón International Airport.
What caused the Birgenair Flight 301 crash?
The Dominican JIAA found the crew did not recognize the stick shaker as a stall warning and did not carry out recovery procedures. Erroneous airspeed indications from a blocked pitot system were a contributing factor.
Was Birgenair Flight 301 an Alas Nacionales flight?
Yes. Birgenair operated the Boeing 757 on a charter for Alas Nacionales, and the FAA identifies the flight as ALW-301.
Where was Birgenair Flight 301 going?
The Boeing 757 was flying from Puerto Plata to Frankfurt, Germany, with a scheduled refueling stop in Canada.
Who investigated the Birgenair Flight 301 crash?
The Dominican Republic's Junta Investigadora de Accidentes Aéreos (JIAA) investigated, with participation from the U.S. NTSB. A final report has been issued.
Did wasps cause the Birgenair 757 crash?
The official summaries reviewed do not state that as a definitive finding. They say a blocked pitot system was associated with the false airspeed, and that pitot covers had not been properly used during about 20 days out of service.
Related accidents
- 102 killed
9 killed
No fatalities
4 killed
1 killed
Correct this page or send a photo
Spotted a wrong date, registration or number? Have a photo of the aircraft or the site that you took yourself? Send it here. Nothing is published until an editor has checked it.