Crash of an Airbus A310-304F in Mbuji-Mayi: 8 killed

Date & Time: Dec 24, 2015 at 1630 LT
Type of aircraft:
Operator:
Registration:
9Q-CVH
Flight Type:
Survivors:
Yes
Schedule:
Lubumbashi – Mbuji-Mayi
MSN:
413
YOM:
1986
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
The crew completed the approach and landing on runway 17 in poor weather conditions with heavy rain falls. After touchdown on a wet runway surface, the aircraft was unable to stop within the remaining distance (runway 17 is 2,000 metres long). It overran and collided with several houses before coming to rest 300 metres further. All five crew members evacuated safely while eight people on the ground were killed.

Crash of an Eclipse EA500 near Swellendam: 1 killed

Date & Time: Dec 7, 2015 at 1057 LT
Type of aircraft:
Registration:
ZS-DKS
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Lanseria - Cape Town
MSN:
142
YOM:
2008
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2977
Captain / Total hours on type:
506.00
Aircraft flight hours:
714
Circumstances:
The aircraft had taken off on a private flight with the pilot being the sole occupant on board. The pilot had filed an IFR flight plan and had informed air traffic control (ATC) at FALA that the aircraft had a fuel endurance of 4 hours and his estimated flying time to FACT was approximately 2 hours and 30 minutes. After take-off the aircraft climbed to its cruising altitude of 36 000 feet (FL360) as was seen on the radar recordings. The pilot maintained communication with ATC until overhead Kimberley. Shortly thereafter the aircraft was observed to change course, turning slightly left before the town of Douglas. The aircraft remained at FL360 and was observed to fly south towards the waypoint OKTED, which was a substantial distance to the east of FACT. FACT could not get communication with the aircraft and the aeronautical rescue co-ordination centre (ARCC) was advised of the situation. The aircraft was kept under constant radar surveillance. The ARCC requested assistance from the South African Air Force (SAAF) and a Gripen (military jet) from Air Force Base Overberg (FAOB) was dispatched to intercept the aircraft. The pilot of the Gripen intercepted the aircraft approximately 3 minutes before it impacted the terrain. The Gripen pilot was unable to get close enough to the aircraft as it was flying very erratically, and he could therefore not see whether the pilot was conscious or not. The aircraft was observed entering a left spiral and continue spiraling down until it impacted the ground. The pilot was fatally injured and the aircraft was destroyed during the impact sequence.
Probable cause:
The investigation revealed no anomalies on the part of the aircraft and all damage was attributed to the impact with the ground. The fatal injuries sustained by the pilot made it impossible to determine if the pilot was incapacitated or not. It was observed that the aircraft performed a series of unexplainable as well as erratic flying manoeuvres, which resulted in a loss of control and the aircraft to enter into a spiral dive, which was observed by the Gripen pilot before colliding with the ground.
Final Report:

Crash of a Hawker-Siddeley HS.780 Andover C.1 in Malakal

Date & Time: Nov 10, 2015
Operator:
Registration:
TL-AEW
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Malakal – Wau
MSN:
Set13
YOM:
1966
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was performing a flight from Malakal to Wau on behalf of the World Food Program. Shortly after takeoff, during initial climb, an unexpected situation forced the captain to attempt an emergency landing. The aircraft crash landed in a field past the runway end, slid for few dozen metres and came to rest, bursting into flames. All four crew members evacuated safely and the aircraft was totally destroyed by a post crash fire.

Crash of an Antonov AN-12BK in Juba: 41 killed

Date & Time: Nov 4, 2015 at 0900 LT
Type of aircraft:
Operator:
Registration:
EY-406
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Juba – Paloich
MSN:
01 34 77 04
YOM:
1971
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
37
Pax fatalities:
Other fatalities:
Total fatalities:
41
Circumstances:
After takeoff from Juba Airport Runway 13, the four engine aircraft encountered difficulties to gain height. After a distance of some 800 metres, the aircraft impacted a hill and crashed on the shore of the White Nile. Two passengers were seriously injured while 41 other occupants were killed, among them all six crew members. Weather conditions at the time of the accident were marginal with rain showers. South Sudan Authorities reported the aircraft was unable to climb because it was overloaded, and the captain reported to ATC prior to departure he was carrying 12 passengers. According to Antonov, the aircraft was not airworthy at the time of the accident because its owner, Tajik Asia Airways, was not compliant with published procedures.

Crash of a Fokker F27 Friendship 400M near Koussané

Date & Time: Nov 2, 2015
Type of aircraft:
Operator:
Registration:
6W-STF
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
10591
YOM:
1979
Location:
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Enroute from Nioro, the crew encountered technical problems and attempted an emergency landing. The aircraft crash landed in a field located 2 km from Koussané. It skidded for few dozen metres, lost its undercarriage, hit a tree with its left wing that was partially torn and came to rest. All 10 occupants were rescued, among them two were injured. The aircraft was damaged beyond repair.

Crash of a Grumman G-159 Gulfstream I in Kinshasa

Date & Time: Nov 1, 2015
Type of aircraft:
Operator:
Registration:
9Q-CNP
Survivors:
Yes
MSN:
164
YOM:
1965
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
22
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After takeoff from Kinshasa-Ndolo Airport, the crew reported technical problems with the undercarriage and was cleared to divert to Kinshasa-N'Djili Airport. A belly landing was completed on runway 24 and the aircraft slid for few dozen metres then veered off runway to the right and came to rest in a grassy area. All 26 occupants evacuated safely and the aircraft was damaged beyond repair. It is believed that the left main gear was torn off upon takeoff from Kinshasa-Ndolo Airport for unknown reasons.

Crash of an Airbus A321-231 near Hasna: 224 killed

Date & Time: Oct 31, 2015 at 0613 LT
Type of aircraft:
Operator:
Registration:
EI-ETJ
Flight Phase:
Survivors:
No
Site:
Schedule:
Sharm el-Sheikh - Saint Petersburg
MSN:
663
YOM:
1997
Flight number:
KGL9268
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
217
Pax fatalities:
Other fatalities:
Total fatalities:
224
Captain / Total flying hours:
12000
Captain / Total hours on type:
3800.00
Aircraft flight hours:
55772
Aircraft flight cycles:
21175
Circumstances:
The aircraft departed Sharm el-Sheikh at 0549LT bound for Saint Petersburg-Pulkovo Airport and was cleared to climb to FL350. On board were 217 passengers and a crew of seven. Some 23 minutes after takeoff, the aircraft entered a steep descent and reached a descent rate of 6,000 feet per minute with a simultaneous reduction of speed before all radar and radio contact were lost at 0613LT. The aircraft crashed in a desert area located about 50 km southeast of Hasna, in the Sinai. None of the 224 occupants survived the accident. It appears the aircraft crashed in a slightly flat attitude and was destroyed by impact forces and a post crash fire (the central part of the fuselage and wings). Based on the debris scattered on a zone of 16 km2, it is now understood that the engines and the tail have been found few hundred metres from the main wreckage. It is believed the aircraft partially disintegrated in the air but probably during the last phase of the descent and not at high altitude.
Probable cause:
On November 17, 2015, Alexander Bortnikov, Chief of the Russian Secret Services, confirmed to Vladimir Putin that the crash was caused by the detonation of a small 'home made' bomb equivalent to one kilo of TNT that was placed on board the airplane in a beverage can. This was confirmed by the Egyptian Presidency on 24 February 2016.

Crash of a Boeing 737-4L7 in Johannesburg

Date & Time: Oct 26, 2015 at 1206 LT
Type of aircraft:
Operator:
Registration:
ZS-OAA
Survivors:
Yes
Schedule:
Port Elizabeth - Johannesburg
MSN:
26960/2483
YOM:
1993
Flight number:
BA6234
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
94
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9186
Captain / Total hours on type:
2899.00
Copilot / Total flying hours:
5817
Copilot / Total hours on type:
480
Aircraft flight hours:
57543
Circumstances:
The aircraft Boeing 737-400, operated by Comair, flight number BA6234, was on a scheduled domestic flight operated under the provisions of Part 121 of the Civil Aviation Regulations (CARs). The aircraft was on the third leg for the day, after it had performed two uneventful legs. According to their recorded flight plan, the first leg departed from King Shaka International Airport (FALE) to O.R. Tambo International Airport (FAOR), the second leg was from FAOR to Port Elizabeth International Airport (FAPE) on the same day, during which the Captain was flying. During this third leg, the aircraft departed from FAPE at 0820Z on an instrument flight plan rule for FAOR. On board were six (6) crew members, ninety four (94) passengers and two (2) live animals. The departure from FAPE was uneventful, whereby the first officer (FO) was the flying pilot (FP) for this leg. During the approach to FAOR, the aircraft was cleared for landing on runway 03R. The accident occurred at approximately 1 km past the threshold. The crew stated that a few seconds after a successful touchdown, they felt the aircraft vibrating, during which they applied brakes and deployed the reverse thrust. The vibration was followed by the aircraft rolling slightly low to the left. It later came to a full stop slightly left of the runway centre line, resting on its right main landing gear and the number one engine, with the nose landing gear in the air. The crash alarm was activated by the FAOR Air Traffic Controller (ATC). The Airport Rescue and Fire Fighting (ARFF) personnel responded swiftly to the scene of the accident. The accident site was then secured with all relevant procedures put in place. The aircraft sustained substantial damage as the number one engine scraped along the runway surface when the landing gear detached from the fuselage. ARFF personnel had to prevent an engine fire in which they saw smoke as a result of runway contact. The occupants were allowed to disembark from the aircraft via the left aft door due to the attitude in which the aircraft came to rest. The accident occurred during daylight meteorological conditions on Runway 03R at O.R. Tambo International Airport (FAOR) located at GPS reading as: S 26°08’01.30” E 028°14’32.34” and the field elevation 5558 ft.
Probable cause:
Unstable approach whereby the aircraft was flared too high with high forward speed resulting with a low sink rate in which during touch down the left landing gear
experienced excessive vibration and failed due to shimmy events.
The following findings were identified:
- According to the FDR recordings, the aircraft flare was initiated earlier at 65ft than at 20ft as recommended by aircraft manufacture, which contributed to the low sink rate.
- The shimmy damper failed the post-accident lab-test and fluid was found in the thermal relief valve, which could have contributed to the shimmy damper failure.
- According to the lab results, significant wear was found on the upper torsion link bushing and flange, which could have contributed to undamped vibration
continuation.
- The aircraft had a tailwind component during landing, which could have prolonged the landing distance.
Final Report:

Crash of an Airbus A300B4-203F in Afgooye

Date & Time: Oct 12, 2015 at 1930 LT
Type of aircraft:
Operator:
Registration:
SU-BMZ
Flight Type:
Survivors:
Yes
Schedule:
Oostend – Cairo – Mogadishu
MSN:
129
YOM:
1980
Flight number:
TSY810
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was performing a cargo flight from Ostend to Mogadishu with an intermediate stop in Cairo with perishable goods on board on behalf of the AMISOM, the African Mission in Somalia. The final approach to Mogadishu-Aden Abdulle International Airport was performed by night. As the crew was unable to localize the runway, he abandoned the approach and initiated a go-around procedure. A second attempt was also interrupted and the crew initiated a new go-around then continued towards the north of the capital city. Eventually, the captain decided to attempt an emergency belly landing near Afgooye, about 25 km northwest of Mogadishu. Upon landing, the aircraft lost its both engines and came to rest in the bush. Two crew members were taken to hospital while four others were uninjured. The aircraft was damaged beyond repair. According to Somalian Authorities, the International Airport of Mogadishu is open to traffic from 0600LT till 1800LT. For undetermined reason, the crew started the descent while the airport was already closed to all traffic (sunset at 1747LT). Also, an emergency landing was unavoidable, probably due to a fuel exhaustion. It is unknown why the crew did not divert to the alternate airport.
Probable cause:
When the controller received the estimated time of arrival for TSY810 from the Flight Information Center (FIC) Nairobi he advised FIC Nairobi (Kenya) that Mogadishu Airport was closed at the estimated time of arrival and advised the crew should divert to their alternate aerodrome but received no feedback. At 14:45Z the tower received first communication from the crew advising they would be overhead the aerodrome at 15:02Z, the controller advised again that the aerodrome would already be closed by then, the crew insisted however that they would land. Tower provided the necessary landing information like weather and active runway. At 15:02Z there was no sight of the aircraft, tower queried with the crew who reported still being 54nm out and revised their estimated time of arrival. At 15:27Z the aircraft turned final for runway 05, tower advised the crew to land at own discretion as tower's "instructions were only advisory and not clearance". The controller added that the approach was aborted and all subsequent approaches were unsuccessful too. "At one point the pilot mistook street parallel to the runway lighted by flood lights with intention of landing but was alerted the runway was on his right and the approach was discontinued. The crew has been warned numerous times that Mogadishu Airport closed at 1800LT (1500Z) and there is no adequate runway lights as the airport is not prepared to receive flights during night time hours. Thus, the pilot has intentionally tried to land at the airport while the visibility was limited to few metres due to darkness.
Final Report:

Crash of a BAe 146-300 in Tamale

Date & Time: Oct 6, 2015 at 0831 LT
Type of aircraft:
Operator:
Registration:
9G-SBB
Survivors:
Yes
Schedule:
Accra – Tamale
MSN:
E.3123
YOM:
1989
Flight number:
IKM110
Location:
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
71
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing on runway 23 at Tamale Airport, the four engine aircraft failed to stop within the remaining distance. It went through a fence that was delimiting a work area as the runway was subject to an extension. Upon impact, the nose gear was torn off and the aircraft slid for few dozen metres before coming to rest. All 76 occupants escaped uninjured but the aircraft was damaged beyond repair. It was specified in a NOTAM that the runway 23 length was reduced to 1,860 meters and that works were in progress to extend runway 23, with the presence of men and equipment. So, caution was advised during landing and takeoff procedures.