Region

Crash of an Antonov AN-26B off Cox's Bazar: 3 killed

Date & Time: Mar 9, 2016 at 0905 LT
Type of aircraft:
Operator:
Registration:
S2-AGZ
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Cox’s Bazar – Jessore
MSN:
134 08
YOM:
1984
Flight number:
21
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
13315
Captain / Total hours on type:
6896.00
Copilot / Total flying hours:
1438
Copilot / Total hours on type:
1195
Aircraft flight hours:
16379
Aircraft flight cycles:
17299
Circumstances:
On March 9, 2016 one AN -26B aircraft belonging to True Aviation Ltd was operating a schedule cargo flight from a small domestic airport (Cox’s Bazar-VGCB) in southern Bangladesh to another domestic airport (Jessore -VGJR) in western Bangladesh, The cargo was Shrimp fries. As per the General Declaration the total cargo quantity was 802 boxes weighing 4800 kg. The airline had filled a flight plan keeping the ETD blank. The flight plan routing was CB W4 CTG W5 JSR at FL 100. All the documents except the load sheet were found properly signed and are in the possession of AAIT. According to ATC controller’s statement and recorded tape the aircraft requested for startup clearance at 0258z. As per the recordings with ATC the controller passed the visibility information of Jessore Airport as 3km. The aircraft started engines and requested for taxi. The aircraft was cleared to taxi to Runway 35 via taxiway S. The aircraft requested for takeoff clearance and was cleared for Take Off at 0305z. Immediately after airborne the pilot reported engine failure without mentioning initially which engine had failed but later confirming failure of the left engine and requested for immediate return back to Cox’s Bazar airport. He was advised by ATC to call left hand down wind. But the control tower spotted the aircraft making a right hand down wind at a very low altitude. All emergency services were made standby from the ATC. The aircraft called final and requested for landing clearance. For reasons so far unknown the aircraft made a low level Go Around. The controller in the tower saw the aircraft flying at about 400 to 500 feet. The surviving Flight Navigator also confirmed this in his statement. The ATC advised the captain to call left hand down wind. But there was no response from the crew. The ATC repeatedly kept calling the aircraft but there was no response from the crew and total communication was lost. At time 0332z the airport authority came to know through other means that the aircraft had crashed approximately 03km west of the airport.
Probable cause:
The accident was the consequence of the combination of the following factors:
a) Failure to initiate a rejected take off during take off roll following the indication of engine failure;
b) Failure to adhere to the company SOP following the detection of the engine failure during take off;
c) Considering the poor visibility at Cox’s Bazar Airport, diverting to the alternate airfield Chittagong Airport located only 50 nm away that has the provision for full ILS approach facility. This could have helped the crew in carrying out a proper one engine out precision approach landing;
d) The aircraft flew at a speed much lower than the clean configuration speed. The aircraft flew at 225 km/h in clean configuration whereas the minimum clean configuration speed is 290 km/hr.
e) As per the FDR data the aircraft stalled while making a turn towards the side of the failed engine at a very low altitude.
Final Report:

Crash of an ATR72-212 in Cox's Bazar

Date & Time: Jul 20, 2014 at 1745 LT
Type of aircraft:
Operator:
Registration:
S2-AFN
Survivors:
Yes
Schedule:
Dhaka - Cox's Bazar
MSN:
379
YOM:
1993
Flight number:
4H501
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
43
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Dhaka, the crew initiated the approach to Cox's Bazar in poor weather conditions due to heavy rain falls. After touchdown, the nose gear collapsed. The airplane slid on its nose for few dozen metres before coming to rest in the middle of the runway that was blocked for almost 22 hours. All 48 occupants evacuated safely while the aircraft was damaged beyond repair.

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 Douglas DC-10-30ER in Chittagong

Date & Time: Jul 1, 2005 at 0853 LT
Type of aircraft:
Operator:
Registration:
S2-ADN
Survivors:
Yes
Schedule:
Dubai - Chittagong - Dhaka
MSN:
46542
YOM:
1979
Flight number:
BG048
Country:
Region:
Crew on board:
15
Crew fatalities:
Pax on board:
201
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed Dubai on a flight to Dhaka with an intermediate stop in Chittagong, carrying 201 passengers and a crew of 15. Weather conditions at Chittagong Airport were poor with a visibility of 1,800 metres in rain, 5-7 oktas cloud at 700 feet, 3-4 oktas cloud at 1,300 feet, 0-2 oktas cloud at 2,600 feet, overcast at 8,000 feet with CB's, temporary visibility of 2 km and wind from 180 at 6 knots. On final approach, the aircraft was unstable but the captain decided to continue the descent. After touchdown on runway 23, the aircraft deviated from the centerline to the right, causing the right main gear to veer off runway. While contacting soft ground, it was torn off, causing the engine n°3 to be partially sheared off. The aircraft slid for few dozen metres before coming to rest in a grassy area along the runway. All 216 occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
Wrong approach configuration on part of the crew who failed to follow the SOP's and his failure to initiate a go-around while the aircraft was unstable on short final.

Crash of a Fokker F28 Fellowship 4000 in Sylhet

Date & Time: Oct 8, 2004 at 0915 LT
Type of aircraft:
Operator:
Registration:
S2-ACH
Survivors:
Yes
Schedule:
Dhaka - Sylhet
MSN:
11172
YOM:
1981
Flight number:
BG601
Location:
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
79
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The flight from Dhaka to Sylhet was delayed for few hours due to poor weather conditions at destination with limited visibility, heavy rain falls, low ceiling and strong winds. Following an uneventful flight, the aircraft landed too far down a wet runway. Unable to stop within the remaining distance, it overran and came to rest in a drainage ditch. 30 passengers were slightly injured while all other occupants escaped unhurt. Both pilots were seriously injured as the cockpit was trapped against an earth wall.
Probable cause:
It was determined that the crew failed to refer to the PAPI's and following a wrong approach configuration, the aircraft landed too far down the runway, reducing the landing distance available. The following contributing factors were reported:
- The ILS system was not properly calibrated, causing the aircraft to land about 900 feet past the runway threshold,
- The aircraft was too high on approach,
- The aircraft' speed at touchdown was 20 knots above the reference speed,
- The braking action was considered as low because the runway surface was wet,
- Aquaplaning,
- The crew failed to initiate a go-around procedure.

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 F28 Fellowship 4000 in Sylhet

Date & Time: Dec 22, 1997 at 2236 LT
Type of aircraft:
Operator:
Registration:
S2-ACJ
Survivors:
Yes
Schedule:
Dhaka - Sylhet
MSN:
11180
YOM:
1981
Flight number:
BG609
Location:
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
85
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On approach to Sylhet Airport, the crew encountered foggy conditions. Due to poor visibility, the crew was unable to establish a visual contact with the approach and runway lights so the decision was taken to initiate a go-around procedure. Few minutes later, a second attempt to land was abandoned for the same reason. The captain insisted and elected to make another approach. On final, the aircraft descended below the MDA and struck the ground 3 km short of runway threshold. On impact, the undercarriage were torn off and the aircraft came to rest in a waterlogged area, broken in two. All 89 occupants were rescued, among them 50 were slightly injured.
Probable cause:
Controlled flight into terrain after the crew continued the descent below MDA without visual contact with the ground until the aircraft impacted terrain.

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.