Country
code

Dhaka

Crash of an ATR72-500 in Dhaka

Date & Time: Apr 30, 2012 at 0851 LT
Type of aircraft:
Operator:
Registration:
60314
Flight Type:
Survivors:
Yes
Schedule:
Bangkok - Dhaka
MSN:
881
YOM:
2009
Flight number:
KAT304
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing at Dhaka-Hazrat Shahjalal Airport, the twin engine aircraft deviated to the right and veered off runway. It collided with an embankment, lost its undercarriage and came to rest against a concrete wall. All 15 occupants were rescued, among them two passengers were slightly injured.

Ground fire of a Boeing 747-357 in Dhaka

Date & Time: Mar 25, 2008 at 0827 LT
Type of aircraft:
Operator:
Registration:
TF-ARS
Survivors:
Yes
Schedule:
Madinah - Dhaka
MSN:
22996/586
YOM:
1983
Flight number:
SV810
Country:
Region:
Crew on board:
19
Crew fatalities:
Pax on board:
307
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
18137
Captain / Total hours on type:
5637.00
Copilot / Total flying hours:
7161
Copilot / Total hours on type:
261
Aircraft flight hours:
99327
Aircraft flight cycles:
18779
Circumstances:
TF-ARS (B747-300) was on a scheduled flight from Medina (Saudi Arabia) to Dhaka (Bangladesh), flight number SVA810. The flight crew consisted of a commander, copilot and a flight engineer. The cabin crew consisted of 15 crew members including one senior cabin attendant. Additionally to the cabin crew, one “off duty” cabin crew member was in the cabin. According to the commander, the flight from Medina and the landing at Dhaka was uneventful. During the landing roll, approximately 50 seconds after touchdown, the flight crew received a call from the tower controller where the tower controller inquired whether the aircraft was under control. The flight crew responded to the call by stating that the aircraft was completely under control and asked what the problem seemed to be. The controller then informed the flight crew that fire was observed at the right wing area. At this point the Aerodrome Fire Operator had already activated the fire fighters as well as the rescue team. As soon as the controller had informed the flight crew about the fire, the flight crew received a No. 3 engine fire alarm. The co-pilot immediately discharged the first engine fire bottle and the flight crew requested firefighter assistance and shut down all engines. The co-pilot waited 20 seconds until the second fire bottle was discharged. At this time the commander called the senior cabin attendant to the flight deck using the public address system (PA). This command was followed by a command to the cabin crew to remain seated. The commander informed the senior cabin attendant of the situation and instructed him to evaluate the situation and to evacuate the passengers if necessary. The senior cabin attendant went back down to the main deck and saw the smoke and the fire through the windows. He then commanded the cabin crew as well as passengers, by using a megaphone, to evacuate the aircraft. The cabin attendant at location L2 (see figure 6-7, page 21) had already operated the emergency exit and started evacuating the passengers. Cabin attendants at locations L1 and R2 (see figure 6-7, page 21) also operated their respective emergency exits. After realizing that smoke and fire were at the right hand side, the emergency exit at R2 was blocked by one of the cabin attendants. All passengers managed to evacuate without serious injuries and the fire department at Zia International Airport managed to extinguish the fire successfully. The damage to the aircraft was later evaluated as beyond economical repair.
Probable cause:
When TF-ARS was decelerating after landing on runway 14 at Zia International Airport, fuel leak at engine No. 3 resulted in a fire within the strut. The cause of the fire was that fuel was leaking through the flexible half coupling to the hot surface of the engine. The fuel leak was because the O-ring and retaining rings were not properly assembled within the coupling and one retaining ring was missing. The IAAIB considers unclear instructions in the aircraft maintenance manual (AMM) to be a contributing factor of the incorrect installation. Another incorrect installation was also found at the flexible half coupling at the front spar for engine No. 1. However there were no signs of a fuel leak in that area, most likely due to the fact that both the retaining rings and the O-ring were within the coupling even though they were incorrectly placed. During the investigation, it was not possible to determine the quantity of the fuel leak. However it is likely that the draining system within the strut of engine No. 3 could not manage the fuel leak. According to the manufacturer, the intention of the draining system is to drain drips or small running leaks. Furthermore the drain was clogged by debris, but IAAIB believes that this was a result of the fire. Two out of six suitable emergency exits on the left side were used (L1 and L2) to evacuate most of the passengers during the emergency evacuation. The reason for not opening doors at location L3, L4 and L5 initially was most likely due to the fact that the commander ordered the cabin crew to remain seated prior to the emergency evacuation. The cabin crew members at locations L3 to L5 most likely did not hear the emergency evacuation command from the senior cabin crew member as he was only using a megaphone. Furthermore these exits were not opened later since the passengers moved aggressively to the opened exits, L1 and L2. The reason for not opening emergency exit UDL at the upper deck was evaluated by the crew to be too risky for the passengers. The flight crew discharged both fire bottles for engine No. 3 without managing to extinguish the fire. The flight crew did not discharge fire bottles on other engines. According to the passenger evacuation checklist (see Appendix 2), the crew should discharge all fire bottles before evacuation.
Findings as to causes and contributing factors:
- Incorrect assembly of the flexible half coupling at the front spar of engine No. 3.
- Retaining ring missing in flexible half coupling at the front spar engine No. 3.
- Lock wire fastened in such a way that the coupling nut might rotate slightly.
Findings as to risk:
- Unclear command made to the cabin crew to start emergency evacuation.
- Cabin crew did not open all suitable emergency exits.
- Flight crew did not follow company’s procedure regarding evacuation.
Other findings:
- Retaining rings and O-ring incorrectly inserted in the flexible half coupling on engine No. 1.
- Pliers used to tighten or loosen the coupling nuts, even though maintenance manual instructs to only hand tight the nuts.
Final Report:

Crash of a Boeing 707-3J6C in Dhaka

Date & Time: Jul 11, 2003 at 0638 LT
Type of aircraft:
Operator:
Registration:
5X-AMW
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Dhaka - Amman
MSN:
20723
YOM:
1974
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the takeoff roll from runway 14 at Dhaka-Zia Ul-Haq Airport, the crew encountered an unexpected situation and the captain decided to abandon the takeoff procedure. Unable to stop within the remaining distance (runway 14 is 3,200 metres long), the aircraft overran, lost its undercarriage and came to rest 450 metres further. All five crew members escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Let L-410UVP-E in Dhaka

Date & Time: Jun 27, 1998
Type of aircraft:
Operator:
Registration:
S2-ADD
Survivors:
Yes
Schedule:
Ishwardi - Dhaka
MSN:
91 26 18
YOM:
1991
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
While approaching Dhaka-Tejgaon Airport at an altitude of 4,000 feet, the crew encountered technical problems with the right engine they shut down. Few seconds later, the crew was able to restart the right engine but as the temperature of the turbine increased, he shut down the engine again. This time, he was unable to feather the propeller. Due to excessive drag, the aircraft lost height and the captain attempted an emergency landing in an open field. On landing, the aircraft lost its undercarriage and came to rest. All seven occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Failure of the right engine for unknown reasons. Failure of the automatic propeller pitch control mechanism was a contributing factor.

Crash of a Fokker F27 Friendship 600 in Dhaka: 49 killed

Date & Time: Aug 5, 1984
Type of aircraft:
Operator:
Registration:
S2-ABJ
Survivors:
No
Schedule:
Chittagong - Dhaka
MSN:
10453
YOM:
1971
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
44
Pax fatalities:
Other fatalities:
Total fatalities:
49
Aircraft flight hours:
15595
Aircraft flight cycles:
24085
Circumstances:
On approach to Dhaka-Zia Ul-Haq Airport runway 32, the crew encountered poor weather conditions with limited visibility due to heavy rain falls. The captain abandoned the approach and initiated a go-around maneuver. Few minutes later, he attempted a second approach to runway 14 but again was forced to make a go-around. During a third attempt to land on runway 14, the crew descended below the MDA until the aircraft struck the ground and crashed in a swampy area located about 550 meters short of runway. The aircraft was totally destroyed upon impact and all 49 occupants were killed.
Probable cause:
Controlled flight into terrain after the crew decided to continue the approach below the MDA without any visual contact with the ground/runway.

Crash of a Fokker F27 Friendship 200 in Sabhar

Date & Time: Nov 18, 1979
Type of aircraft:
Operator:
Registration:
S2-ABG
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Dhaka - Dhaka
MSN:
10308
YOM:
1966
Location:
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
19210
Aircraft flight cycles:
24081
Circumstances:
The crew departed Dhaka Airport for a local training flight. While cruising at an altitude of 8,000 feet, the crew initiated a stall test program when both engines flamed out. Several attempts to restart the engines failed so the instructor regained control and attempted an emergency landing in Sabhar, about 15 km west of Dhaka Airport. On touchdown, the airplane struck an embankment, lost its undercarriage and came to rest. While all four crew members escaped with minor injuries, the aircraft was damaged beyond repair.
Probable cause:
Engine flameout for unknown reasons.

Crash of a Douglas DC-3 in Dhaka: 5 killed

Date & Time: Feb 10, 1972
Type of aircraft:
Operator:
Flight Type:
Survivors:
No
Schedule:
Dhaka - Dhaka
Location:
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
On final approach to Dhaka Airport, the airplane crashed in unknown circumstances, killing all five crew members who were completing a local training flight.

Crash of a Canadair CL-44J in Dhaka: 8 killed

Date & Time: Dec 2, 1970 at 1600 LT
Type of aircraft:
Operator:
Registration:
TF-LLG
Flight Type:
Survivors:
No
Site:
Schedule:
Hamburg – Tehran - Dhaka
MSN:
36
YOM:
1964
Location:
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
The aircraft was completing a humanitarian flight from Hamburg to Dhaka with an intermediate stop in Tehran, carrying a crew of four and 27,5 tons of foods on behalf of the International Red Cross Comity. On final approach to Dhaka-Tejgaon Airport, the airplane went out of control and crashed onto several houses located in a district 10 km northwest of the airport. All four crew members were killed as well as four people on the ground.
Probable cause:
It appeared that the hydraulic gust lock system activated in flight, causing the controls to lock. It is believed the rudder was blocked in neutral position and the ailerons in a upper position. Also, it is believed that hydraulic back pressure had built up because of a malfunctioning switch valve when hydraulics where armed on descent. The aircraft already suffered a major hydraulic contamination during a previous flight in the Azores Islands. On takeoff, both hydraulic pumps failed, causing a total hydraulic loss and forcing the crew to fly gear down to Madrid.

Crash of a Fokker F27 Friendship 200 in Dhaka

Date & Time: Jun 25, 1964
Type of aircraft:
Operator:
Registration:
AP-ALO
Survivors:
Yes
Schedule:
Karachi – Hyderabad – Dhaka
MSN:
10165
YOM:
1961
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
22
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
7016
Aircraft flight cycles:
8325
Circumstances:
The crew started the approach to Tejgaon AFB in marginal weather conditions. During the last segment, the airplane lost height and struck the runway surface. At impact, both wings were partially sheared off and the airplane came to rest. Five occupants were injured while all other occupants were unhurt. At the time of the accident, a squall line was passing over the airport with turbulences and heavy rain falls.
Probable cause:
It is believed the loss of control on short final was caused by strong downdrafts and/or windshear.