Crash of an Embraer ERJ-190AR in the Bwabwata National Park: 33 killed

Date & Time: Nov 29, 2013 at 1230 LT
Type of aircraft:
Operator:
Registration:
C9-EMC
Flight Phase:
Survivors:
No
Schedule:
Maputo - Luanda
MSN:
190-00581
YOM:
2012
Flight number:
LAM470
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
27
Pax fatalities:
Other fatalities:
Total fatalities:
33
Captain / Total flying hours:
9052
Captain / Total hours on type:
2519.00
Copilot / Total flying hours:
1183
Copilot / Total hours on type:
101
Aircraft flight hours:
2905
Aircraft flight cycles:
1877
Circumstances:
Aircraft left Maputo Airport at 1126LT on flight LAM470 to Luanda, Angola. En route, while overflying Botswana and Namibia, aircraft encountered bad weather conditions with CB's at high altitude and turbulence. In unknown circumstances, aircraft went out of control and disappeared from radar screens at 1230LT, most probably after diving into the ground. As the aircraft did not arrive at Luanda, SAR commenced but were suspended by night due to low visibility and bad weather conditions (heavy rain falls). The day after, on 30NOV, Namibia Police forces announced they located the wreckage in the Bwabwata National Park, near Divundu. Aircraft was completely destroyed by impact forces and post impact fire. All 33 occupants were killed, among them 16 Mozambicans, 9 Angolans, 5 Portuguese, one French, one Brazilian and one Chinese. The aircraft crashed in a dense wooded and isolated area, sot SAR are difficult. No distress call was sent by the crew.
Probable cause:
A press conference provided by the Mozambican authorities on 21DEC2013 reported that CVR analysis revealed that the captain was alone in the cockpit which was locked. The copilot tried to enter without success and was knocking on the door several times, without answer or any reaction on part of the captain who engaged the aircraft in a descent rate of 6,000 feet per minute until impact with the ground. Several warning sounds and alarms were not responded to. On April 15, 2016, the Directorate of Aircraft Accident Investigations (DAAI) of Namibia confirmed in its final report that the accident was caused by the inputs to the auto flight systems by the person believed to be the Captain, who remained alone on the flight deck when the person believed to be the co-pilot requested to go to the lavatory, caused the aircraft to departure from cruise flight to a sustained controlled descent and subsequent collision with the terrain. Investigations revealed that the captain suffered personal events during the past year, such as a divorce, the death of his son in a car crash and one of his daughter that underwent heart surgery.
Final Report:

Crash of a Boeing 737-53A in Kazan: 50 killed

Date & Time: Nov 17, 2013 at 1924 LT
Type of aircraft:
Operator:
Registration:
VQ-BBN
Survivors:
No
Schedule:
Moscow - Kazan
MSN:
24785/1882
YOM:
1990
Flight number:
TAK363
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
44
Pax fatalities:
Other fatalities:
Total fatalities:
50
Captain / Total flying hours:
2783
Captain / Total hours on type:
2509.00
Copilot / Total flying hours:
2093
Copilot / Total hours on type:
1943
Aircraft flight hours:
51547
Aircraft flight cycles:
36596
Circumstances:
On final approach to Kazan from Domodedovo in marginal weather conditions, crew was forced to make a go around as the aircraft was not correctly aligned with the runway centerline. While climbing to a height of 700 meters, the aircraft went out of control, nosed down and hit the ground. The aircraft disintegrated on impact and all 50 occupants were killed. MAK reported in a first statement that the crew did not follow the standard approach profile and the approach was unstable. TOGA mode was selected, autopilot deactivated and flaps raised from 30 to 15 degrees. As gear were retracted, the aircraft pitched up to about 25 degrees nose up and the indicated airspeed decreased from 150 to 125 knots. Crew countered the nose up by control inputs and the climb was stopped. Aircraft reached a maximum height of 2,300 feet and began to rapidly descend until it impacted the ground with a near vertical angle of 75 degrees at a speed of 242 knots, some 20 seconds after reaching the height of 2,300 feet. The crash was no survivable.
Probable cause:
Systemic weaknesses in identifying and controlling the levels of risk, non-functional safety management system in the airline and lack of control over the level of crew training by aviation authorities at all levels (Tatarstan Civil Aviation Authority, Russian Civil Aviation Authority), that resulted in an unqualified crew being assigned to the flight.
During the go-around the crew did not recognize that the autopilot had disconnected resulting in the aircraft impacting ground in a complex spatial position (nose up upset). The captain, pilot flying, lacked the skills to recover the aircraft from the complex spatial upset (lack of Upset Recovery), that led to significant negative G-forces, loss of spatial orientation sending the aircraft into a steep drive (75 degrees nose down) until impact with ground.
The go around was required because the aircraft on its final approach arrived in a position from which landing was impossible as result of a map shift by about 4000 meters (aircraft systems determining the position of the aircraft in error), the inability of the crew in those circumstances to combine aircraft control and navigation with needed precision, and the lack of active support by air traffic control during prolonged observation of significant deviation from the approach procedure.
The following factors were considered as contributory:
The captain not having had primary flight training,
The flight crew members being allowed to upgrade to Boeing 737 without satisfying the required qualifications including the English language,
Methodical shortcomings in retraining as well as verification of results and quality of training,
Insufficient level of organisation of flight operations at the airline, which resulted in failure to detect and correct shortcomings in working with the navigation equipment, pilot technique and crew interaction, including missed approaches,
Systematic violation of crew work and rest hours, a large debt of holidays, which could have resulted in accumulation of fatigue adversely affecting crew performance, Simulator training that lacked a missed approach with intermediate height and all engines operating,
Increased emotional stress to the flight crew before deciding to go around because they could not establish the position of their aircraft with the necessary precision to accomplish a successful landing,
Violation of the principle "Aviate, Navigate, Communicate" by both flight crew and air traffic control, which resulted in the flight crew not following standard operating procedures at the time of initiating the go around because the pilot monitoring was diverted from his duties for a prolonged period and did not monitor the flight parameters,
The fact that the crew did not recognize the autopilot had disconnected and delayed intervention by the crew, that resulted in the aircraft entering a complex spatial position (nose up upset),
Imperfection of simulator training programs for Upset Recovery Procedures as well as lack of criteria for assessing the quality of training, which resulted in the crew being unable to recover the aircraft from the upset,
The possible impact of somatogravic illusions,
The non-addressing of prior accident investigation recommendations, geared towards elimination of risks and establishing risk level management, had prevented the prevention of this accident,
Lack of proper supervision of issuance of pilot certificates in accordance with achieving specified requirements and qualifications,
Failure of safety management system (SMS) in the airline, lack of guidelines for SMS development and approval, lack of a formal approach to approve/agree on SMS and pilot training by the related authorities,
Deficiencies in aviation training centers' performance and absence of verification of training quality,
Lack of requirements for flight crew to be proficient in English Language for retraining on foreign aircraft types and lack of formal approach to verify language proficiency,
lack of formal approach to conduct periodic verification of flight crew qualification,
systematic violation of crew work and rest times,
lack of training of flight crew on go around from intermediate heights in manual control potentially leading to complex spatial position (e.g. nose high upset),
The map shifts in aircraft without GPS without training of crew to operate in such conditions,
Lack of active assistance by air traffic control when the approach procedure was deviated from over a prolonged period of time,
Breach of principle "Aviate, Navigate, Communicate".
Translation via www.avherald.com
Final Report:

Crash of a Swearingen SA227AC Metro III in Red Lake: 5 killed

Date & Time: Nov 10, 2013 at 1829 LT
Type of aircraft:
Operator:
Registration:
C-FFZN
Survivors:
Yes
Schedule:
Sioux Lookout - Red Lake
MSN:
AC-785B
YOM:
1991
Flight number:
BLS311
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
5150
Captain / Total hours on type:
3550.00
Copilot / Total flying hours:
2200
Copilot / Total hours on type:
1060
Aircraft flight hours:
35474
Circumstances:
Flight from Sioux Lookout was uneventful till the final descent to Red Lake completed by night and in light snow with a ceiling at 2,000 feet and visibility 8 SM. On final approach to runway 26, crew reported south of the airport and declared an emergency. Shortly after this mayday message, aircraft hit power cables and crashed in flames in a dense wooded area located 800 meters south of the airport. Two passengers seating in the rear were seriously injured while all five other occupants including both pilots were killed.
Probable cause:
A first-stage turbine wheel blade in the left engine failed due to a combination of metallurgical issues and stator vane burn-through. As a result of the blade failure, the left engine continued to operate but experienced a near-total loss of power at approximately 500 feet above ground level, on final approach to Runway 26 at the Red Lake Airport. The crew were unable to identify the nature of the engine malfunction, which prevented them from taking timely and appropriate action to control the aircraft. The nature of the engine malfunction resulted in the left propeller being at a very low blade angle, which, together with the landing configuration of the aircraft, resulted in the aircraft being in an increasingly high drag and asymmetric state. When the aircraft’s speed reduced below minimum control speed (VMC), the crew lost control at an altitude from which a recovery was not possible.
Final Report:

Crash of a Swearingen SA227AC Metro III in Riberalta: 8 killed

Date & Time: Nov 3, 2013 at 1556 LT
Type of aircraft:
Operator:
Registration:
CP-2754
Survivors:
Yes
Schedule:
Trinidad - Riberalta
MSN:
AC-721B
YOM:
1989
Flight number:
AEK025
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
16
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
Following an uneventful flight from Trinidad, the crew started the descent to Riberalta Airport in poor weather conditions with a visibility reduced to 3 km due to rain falls. After touchdown on wet runway 14, the aircraft was unable to stop within the remaining distance. It overran, collided with obstacles and came to rest upside down, bursting into flames, some 300 metres short of runway 32 threshold. Ten people were rescued while eight passengers were killed. The aircraft was totally destroyed. The exact circumstances of the accident remains unclear.

Crash of an ATR72-600 off Pakse: 49 killed

Date & Time: Oct 16, 2013 at 1555 LT
Type of aircraft:
Operator:
Registration:
RDPL-34233
Survivors:
No
Schedule:
Vientiane - Pakse
MSN:
1071
YOM:
2013
Flight number:
LAO301
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
44
Pax fatalities:
Other fatalities:
Total fatalities:
49
Captain / Total flying hours:
5600
Captain / Total hours on type:
3200.00
Copilot / Total flying hours:
400
Aircraft flight hours:
758
Circumstances:
A first approach procedure to runway 15 was aborted by the crew due to insufficient visibility. On the circuit to complete a second approach in bad weather conditions, the ATR72-600 crashed some 8 km short of runway and was completely submerged in the Mekong River. None of the 49 occupants (44 pax and 5 crew) survived, among them 7 French citizens and 6 Australians. Aircraft left Vientiane at 1445LT and should arrive in Pakse one hour later. Aircraft was built and delivered to Lao Airlines in March this year. First crash involving an ATR72-600 series. Up to date, worst accident in Laos.
The Laotian Authorities released the following key sentences of analysis:
"Under IMC conditions, with no reference to the ground, the SOPs lead to conducting an instrument approach. In Pakse the VOR DME approach procedure is in force. There is no radar service. The flight crew has to fly to the initial approach fix or the intermediate fix at an altitude above 4600ft, then start the descent to 2300ft until final approach fix. Finally the flight crew descends to the minima (990ft), if visual references with the ground are available and sufficient the flight crew may continue until touchdown. If ground visual references are not available or not sufficient, the flight crew may level off up to the missed approach point and then must start the missed approach procedure. From the FOR data, the flight crew set 600 ft as the minima. This is contrary to the published minima of 990 ft. Even if the flight crew had used the incorrect height as published in the JEPPESEN Chart at that time the minima should have been set to 645 ft or above. The choice of minima lower than the published minima considerably reduces the safety margins. Following the chart would lead the flight crew to fly on a parallel path 345 ft lower than the desired indicated altitude. The recordings show that the flight crew initiated a right turn according to the lateral missed approach trajectory without succeeding in reaching the vertical trajectory. Specifically, the flight crew didn't follow the vertical profile of missed approach as the missed approach altitude was set at 600 ft and the aircraft system went into altitude capture mode. When the flight crew realized that the altitude was too close to the ground, the PF over-reacted, which led to a high pitch attitude of 33°. The aircraft was mostly flying in the clouds during the last part of flight."
Probable cause:
The probable cause of this accident were the sudden change of weather condition and the flight crew's failure to properly execute the published instrument approach, including the published missed approach procedure, which resulted in the aircraft impacting the terrain.
The following factors may have contributed to the accident:
- The flight crew's decision to continue the approach below the published minima
- The flight crew's selection of an altitude in the ALT SEL window below the minima, which led to misleading FD horizontal bar readings during the go-around
- Possible Somatogravic illusions suffered by the PF
- The automatic reappearance of the FD crossbars consistent with the operating logic of the aeroplane systems, but inappropriate for the go-around
- The inadequate monitoring of primary flight parameters during the go-around, which may have been worsened by the PM's attention all tunneling on the management of the aircraft flap configuration
- The flight crew's limited coordination that led to a mismatch of action plans between the PF and the PM during the final approach.
Final Report:

Crash of a Cessna 208B Grand Caravan near Loreto: 14 killed

Date & Time: Oct 14, 2013 at 0907 LT
Type of aircraft:
Operator:
Registration:
XA-TXM
Flight Phase:
Survivors:
No
Site:
Schedule:
Los Mochis – Loreto – Ciudad Constitución
MSN:
208B-0947
YOM:
2002
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
13
Pax fatalities:
Other fatalities:
Total fatalities:
14
Captain / Total flying hours:
2308
Aircraft flight hours:
11840
Aircraft flight cycles:
12184
Circumstances:
The single engine aircraft departed Loreto Airport at 0901LT on a flight to Ciudad Constitución, carrying 13 passengers and one pilot. Weather conditions were poor with limited visibility and heavy rain falls due to the presence of the tropical storm 'Octave'. Six minutes after takeoff, while cruising at an altitude of 3,900 feet, the airplane impacted the slope of a rocky mountain located in the Sierra de La Giganta. The wreckage was found two days later some 26 km west of Loreto. The aircraft disintegrated on impact and all 14 occupants were killed.
Probable cause:
Controlled flight into terrain after the pilot suffered a spatial disorientation while cruising in unfavorable weather conditions due to the presence of the tropical storm 'Octave'.
Final Report:

Crash of a De Havilland DHC-6 Twin Otter 310 in Kudat: 2 killed

Date & Time: Oct 10, 2013 at 1450 LT
Operator:
Registration:
9M-MDM
Survivors:
Yes
Schedule:
Kota Kinabalu - Kudat
MSN:
804
YOM:
1983
Flight number:
MWG3002
Location:
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
14
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
4700
Aircraft flight hours:
56828
Aircraft flight cycles:
108882
Circumstances:
A de Havilland Canada DHC-6 Twin Otter 310, operated by MASwings, sustained substantial damage in an accident at Kudat Airport (KUD), Malaysia. The copilot and one passenger died, four others were injured. MASwings flight MH3002 operated on a domestic flight from Kota Kinabalu Airport (BKI) to Kudat. The captain was the pilot flying for this sector and the first officer was pilot monitoring. As the aircraft was approaching Kudat Airfield, Kudat Tower reported the weather conditions to be: wind at 270 degrees at 17 kts gusting 31 kts. The aircraft continued the approach on runway 04 and leveled off at 500 feet with flaps set at 10°. At this point the crew noticed that the approach for runway 04 had a strong tail wind. This was evident from the indicated airspeed observed by the crew which indicated 100 kts where the airspeed for flaps 10° should be 65kts. The windsock also indicated a tail wind. Noticing the approach for runway 04 was a tail wind condition, the crew decided to go around at a height of 500ft. Maintaining runway heading, the crew initiated a go around climbing to 1,000ft making a left tear drop and reposition for runway 22. On the approach for runway 22 the captain informed the first officer that if they could not land they would return to Kota Kinabalu. The aircraft was aligned with the centerline of runway 22 and 20° flaps was set. The aircraft continued to descend to 300ft. At this point the wind appeared to be calm as the aircraft did not experience any turbulence and the captain told the first officer that he was committed to land. Upon reaching 200ft the captain called for the flaps to be lowered to full down. As they were about to flare the aircraft to land, approximately 20ft above the runway, the aircraft was suddenly hit by a gust of wind which caused the aircraft to veer to the right with the right wing low and left wing high and the nose was pointing 45° to the right of runway 22. The crew decided to go around by applying maximum power; however the aircraft did not manage to climb successfully. The flaps were not raised and were still in the full flaps down position as the crew thought the aircraft was still low hence the flaps were not raised. The aircraft continued to veer to the right with right wing low and managed to only climb at a shallow rate. The aircraft failed to clear the approaching trees ahead and was unable to continue its climb because the airspeed was reducing. The presence of a full flaps configuration made it more difficult for the aircraft to climb. As the aircraft was on full power on both the engines, it continued to fly almost perpendicularly in relation to the runway and at a low height above the ground. The aircraft hit a tree top at the airfield perimeter fencing, disappeared behind the row of trees, hit another tree behind a house. It hit the right rear roof of the house, ploughed through the roof top of the kitchen, toilet and dining area, hit the solid concrete pillars of the car garage and finally hit the lamp post just outside the house fence. It swung back onto the direction of the runway and came to rest on the ground with its left engine still running. A woman and her 11-year old son who were in the living room at the time escaped unhurt.
Probable cause:
Based on the information from the recorded statements of witnesses and Captain of the aircraft, it clearly indicates that the aircraft was attempting to land on Runway 04 with a tail-wind blowing at 270° 15kts gusting up to 25kts on the first approach, contrary to what was reported by the Captain to the investigators. The demonstrated cross wind landing on the DHC6-310 is 25kts and tailwind landing is 10kts. The aircraft was unsettled and unstable until it passed abeam the terminal building which was not the normal touch down point under normal landing condition. The flap setting on the first approach with the tail-wind condition was at 10°, which is not in accordance with company’s procedures. A tail wind landing condition that will satisfy the criteria for the DHC6-310 is not more than 10kts tail-wind and a flap setting of not more than 20°. One of the stabilized approach criterias for visual conditions (VMC) into Kudat is landing configuration must be completed by 500ft Above Ground Level (AGL) for the DHC6-310 where else if the above conditions could not be met, a go-around should be initiated. Hence, the Crew should have initiated a go-around earlier before the aircraft reached 500ft AGL on the first approach. The aircraft should be in the correct landing configuration at or below the stabilized approach altitude of 500ft AGL, since the aircraft was not stable due to the tail wind and gusting weather. The procedure carried out on the approach for Runway 04 was not consistent with MASwings’ Standard Operating Procedure (SOP) for a tailwind condition. Nonetheless, the first approach for Runway 04 though was uneventful. On the second approach from Runway 22, the wind condition was still not favorable for landing, and gusting. The aircraft was believed to be slightly low on the initial approach and was still unstable. The flap setting for the second approach for Runway 22 was at full flap (37°). As the wind was gusting, a flap setting to full-down should be avoided for the landing as stated in company’s DHC6-310 SOP. With the full-flap configuration, the aircraft had difficulty to settle down on the runway thus dragging the aircraft until abeam the tower which is way beyond the normal touch down zone.
At the point where the aircraft was approaching to land it was reported that the aircraft was hit by a sudden gust, several factors, including the following, have been looked into:
a) Why was the aircraft unable to climb after initiating the go-around?
The full flap setting would require a zero degree pitch attitude to ensure the aircraft speed is maintained. With go-around power set, the zero degree pitch would ensure a climb without speed loss. A pitch above zero degree can cause the aircraft speed to decrease and induce a stall condition resulting in the aircraft being unable to climb.
b) Was the go-around technique executed correctly, taking into consideration that the wind was blowing from 270° and gusting?
The Captain had said that "I applied maximum power and expected the aircraft to climb. At this point, the aircraft was still in left-wing high situation. I noticed the aircraft did make a climb but it was a shallow climb. I did not retract the flaps to 20°, as at that time, in my mind, the aircraft was still low."
c) Under normal conditions, the rule of thumb for initiating a go-around procedure is to apply maximum power, set attitude to climb, confirm airspeed increasing and reduce the flap setting. This procedure was found not to be properly synchronized between MASwings Manuals and DHC6-310 Series 300 SOP.
d) Were the pilots in control of the aircraft?
Based on the Captain’s statement and other associated factors, the pilots were not in total control of the aircraft.

Crash of a Saab 340B in Udon Thani

Date & Time: Oct 6, 2013 at 0845 LT
Type of aircraft:
Operator:
Registration:
HS-GBG
Flight Phase:
Survivors:
Yes
Schedule:
Chiang Mai - Udon Thani
MSN:
453
YOM:
1998
Flight number:
DD8610
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
25
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Chiang Mai, the crew completed the landing on runway 30 at Udon Thani Airport. The aircraft vacated runway and was taxiing when control was lost. The airplane veered to the right, entered a soft grassy area, lost its nose gear and came to rest. All 28 occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
Failure of the hydraulic system, causing the malfunction of the nosewheel steering system and the brakes.

Crash of a PZL-Mielec AN-2R in Kamako

Date & Time: Sep 13, 2013 at 1150 LT
Type of aircraft:
Operator:
Registration:
9Q-CFT
Survivors:
Yes
Schedule:
Tshikapa - Kamako
MSN:
1G223-14
YOM:
1987
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
16798
Captain / Total hours on type:
16000.00
Aircraft flight hours:
6981
Circumstances:
Following an uneventful flight from Tshikapa, the pilot initiated the approach to Kamako Airfield in relative good conditions. On final, the wind component suddenly changed. The aircraft lost height and impacted ground 16 metres short of runway 12. Upon impact, the undercarriage were partially torn off and the aircraft slid before coming to rest 37 metres past the runway threshold. All six occupants, one pilot and five passengers, escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
It was determined that the loss of control that occurred on short final was the result of the combination of a human error and weather component. The pilot was surprised by the abrupt change in weather conditions on short final to Kamako runway 12. He elected to initiate a go-around procedure and increased engine power but unfortunately, low level windshear caused the aircraft to lose height and to struck the ground as its speed was insufficient. In consequence, the increase power was too low to allow the pilot to maintain the approach profile. The torsion of the blades confirmed that the engine was at full power for a go-around procedure at impact. The absence of a windsock at Kamako Airfield was considered as a contributing factor as this would help the pilot to recognize the wind component and to decide to land or to go-around in due time.
Final Report:

Crash of an Airbus A330-321 in Bangkok

Date & Time: Sep 8, 2013 at 2326 LT
Type of aircraft:
Operator:
Registration:
HS-TEF
Survivors:
Yes
Schedule:
Guangzhou – Bangkok
MSN:
066
YOM:
1995
Flight number:
TG679
Country:
Region:
Crew on board:
14
Crew fatalities:
Pax on board:
288
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful night schedule service from Guangzhou, the crew was cleared for an ILS approach to runway 19L at Bangkok-Suvarnabhumi Airport. Following a smooth landing, the crew started the braking procedure when, after a course of about 1,000 metres, the aircraft deviated to the right then veered off runway. While contacting soft ground, the nose gear collapsed, the aircraft sank in earth and came to rest with both engines in flames. All 302 occupants were rescued, among them 14 passengers were injured. The aircraft was damaged beyond repair.
Probable cause:
Loss of control after landing after the right hand bogie beam broke due to fatigue cracks.