Ground fire of an Airbus A330-343 in Beijing

Date & Time: Aug 27, 2019 at 1648 LT
Type of aircraft:
Operator:
Registration:
B-5958
Flight Phase:
Survivors:
Yes
Schedule:
Beijing - Tokyo
MSN:
1587
YOM:
2014
Flight number:
CA183
Country:
Region:
Crew on board:
14
Crew fatalities:
Pax on board:
147
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
19007
Aircraft flight cycles:
4596
Circumstances:
The airplane was parked at gate 530 (Terminal 3) at Beijing Capital and being prepared for flight CA183 to Tokyo-Haneda. 14 crew members were on board as well as 147 passengers when an abnormal sound was heard coming from the L2 door connected to the jetbridge. The cargo smoke alarm came on in the cockpit while smoke spread in the cabin. The pilot declared an emergency and decision was taken to evacuate all 161 occupants and no one was injured while the aircraft was partially destroyed by fire. The origin of the fire is still under investigation.

Crash of a De Havilland DHC-8-202 in Kichwa Tembo

Date & Time: Aug 16, 2019 at 1100 LT
Operator:
Registration:
5Y-SLM
Survivors:
Yes
Schedule:
Nairobi – Kichwa Tembo
MSN:
506
YOM:
1997
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Nairobi-Wilson Airport, the crew landed on a gravel runway at Kichwa Tembo Airport. After touchdown, the aircraft collided with two wildebeests. Upon impact, the left main gear was torn off and the aircraft veered off runway to the left and came to rest. All occupants evacuated safely and the aircraft was damaged beyond repair. Both wildebeests were killed.
Probable cause:
Loss of control upon landing following a ground collision with two wildebeests.

Crash of an Airbus A321-211 in Moscow

Date & Time: Aug 15, 2019 at 0615 LT
Type of aircraft:
Operator:
Registration:
VQ-BOZ
Flight Phase:
Survivors:
Yes
Schedule:
Moscow - Simferopol
MSN:
2117
YOM:
2003
Flight number:
U6178
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
226
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Moscow-Zukhovski Airport runway 12, while climbing to an altitude of 750 feet in excellent weather conditions, the airplane collided with a flock of birds (sea gulls). Some of them were ingested by both engines that lost power. It was later reported by the crew that the left engine stopped almost immediately while the right engine lost power and run irregularly. Unable to maintain a positive rate of climb, the captain decided to attempt an emergency landing in a cornfield. The airplane belly landed approximately 3,5 km past the runway end and slid for dozen meters before coming to rest with its both engines partially torn off. All 233 occupants were able to evacuate the cabin and it is reported that 23 people were slightly injured.

Crash of a Cessna 208B Grand Caravan in Kilindoni

Date & Time: Aug 6, 2019
Type of aircraft:
Operator:
Registration:
5H-NOW
Flight Phase:
Survivors:
Yes
Schedule:
Kilindoni - Dar es Salaam
MSN:
208B-2209
YOM:
2010
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Kilindoni Airport, the single engine airplane crashed in flames. All nine occupants were able to evacuate the cabin and six of them were injured and transported to local hospital. The aircraft was completely destroyed by fire.

Crash of a Boeing 737-36N in Lagos

Date & Time: Jul 23, 2019 at 1128 LT
Type of aircraft:
Operator:
Registration:
5N-BQO
Survivors:
Yes
Schedule:
Port Harcourt - Lagos
MSN:
28571/3022
YOM:
1998
Flight number:
P47191
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
133
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
45452
Aircraft flight cycles:
31643
Circumstances:
Following an uneventful flight from Port Harcourt, the crew initiated the approach to Lagos-Murtala Muhammed Airport in poor weather conditions with heavy rain falls due to CB's at 1,900 feet. On final, he was cleared to land on runway 18R and informed about a wet runway surface. Both main landing gears touched down normally and when the nose gear landed as well, both wheels apparently separated. The nose gear leg ripped the ground and the airplane rolled for few dozen metres before coming to rest. All 139 occupants evacuated safely and the airplane was later considered as damaged beyond repair.

Crash of an ATR42-500 in Gilgit

Date & Time: Jul 20, 2019 at 0815 LT
Type of aircraft:
Operator:
Registration:
AP-BHP
Survivors:
Yes
Schedule:
Islamabad – Gilgit
MSN:
665
YOM:
2007
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
48
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Islamabad, the crew was cleared to land on runway 25 at Gilgit Airport. After touchdown, the crew initiated the braking procedure but the aircraft was unable to stop within the remaining distance. It overran, lost its right main gear and came to rest 12 metres further in a grassy area. All 53 occupants evacuated safely and the aircraft was damaged beyond repair.

Crash of a Cessna 404 Titan II in Moroni

Date & Time: Jul 18, 2019
Type of aircraft:
Operator:
Registration:
D6-FAT
Flight Phase:
Survivors:
Yes
Schedule:
Moroni - Mohéli
MSN:
404-0216
YOM:
1978
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Moroni-Prince Saïd Ibrahim-Hahaya Airport, while climbing, the pilot encountered an unexpected situation and apparently attempted an emergency landing when the twin engine airplane struck the ground past the runway end and came to rest inverted. All 11 occupants were evacuated, a passenger and the pilot were injured. The aircraft was partially destroyed by a post crash fire.

Crash of a Cessna 208B Grand Caravan in Bethel

Date & Time: Jul 8, 2019 at 1505 LT
Type of aircraft:
Operator:
Registration:
N9448B
Survivors:
Yes
Schedule:
Newtok – Bethel
MSN:
208B-0121
YOM:
1988
Flight number:
GV262
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2258
Captain / Total hours on type:
787.00
Aircraft flight hours:
21206
Circumstances:
The commercial pilot was conducting a visual flight rules scheduled passenger flight with five passengers. During the return leg to the company’s base airport, the pilot requested, and was given clearance to, a short gravel runway of 1,858 ft that terminated at parallel cross-runways and had inbound airplanes. The wind was reported as variable at 3 knots, and the outside air temperature was 88°F which was 25° warmer than usual. The pilot stated that he conducted a steeper than normal approach and performed a normal 30° flap landing flare; however, the airplane floated halfway down the runway. He initiated a go-around by advancing the throttle to takeoff power and retracting the flaps to 20° as the main landing gear briefly touched down. Automatic dependent surveillance-broadcast (ADS-B) data indicated that the airplane arrived 0.1 mile from the runway threshold at 149 ft above ground level (agl) and 110 knots of ground speed, which was 32 knots faster than the short field landing approach speed listed in the pilot operating handbook. A witness in the air traffic control tower (the ground controller) stated that the airplane “bled off a lot of airspeed,” during the landing attempt and climbed out in a very flat profile. The tower local controller stated that after liftoff, the airplane’s right wing dropped and the airplane appeared to be turning right into conflicting landing traffic, so he twice instructed the airplane to “left turn out immediately.” The pilot stated that he attempted to comply with the tower controller’s instruction, but when he applied left aileron, the airplane appeared to stall, rolled rapidly right, and descended in a right-wing-low attitude. It subsequently impacted the surface between runways. A postimpact fire ensued, and the pilot helped the passengers egress. The airplane was destroyed by postimpact fire. Given the evidence, it is likely that the pilot decided to land on the short runway to expedite the arrival and did not perform an appropriate short field landing approach, which resulted in excessive airspeed and altitude over the runway threshold, a long landing flare, rapid deceleration, and a self-initiated go-around from a slow airspeed. Had the pilot initiated the go-around as he approached the runway with indications of an unstable visual approach, the airspeed would have been well above stall speed, which would have allowed for the desired positive climb out on runway heading. The pilot likely attempted to comply with the tower local controller’s urgent commands to turn while the airplane was near the limit of performance (the temperature was about 25 degrees warmer than average, which would have resulted in a higher density altitude than the pilot was accustomed to and degraded aircraft and engine performance). The pilot’s maneuvering resulted in the exceedance of the critical angle-of-attack of the high wing (right wing) during the left turn, and an aerodynamic stall.
Probable cause:
The pilot’s failure to maintain adequate airspeed while maneuvering during an attempted go around, which resulted in an exceedance of the airplane's critical angle of attack and an aerodynamic stall at low altitude. Contributing to the accident, was the pilot’s decision to perform an approach to a short runway at an excessive airspeed and his late decision to perform a go-around, which resulted in a slow climb at a reduced safe margin above stall airspeed.
Final Report:

Crash of a Boeing 737-85R in Mumbai

Date & Time: Jul 1, 2019 at 2351 LT
Type of aircraft:
Operator:
Registration:
VT-SYK
Survivors:
Yes
Schedule:
Jaipur - Mumbai
MSN:
30410/1228
YOM:
2002
Flight number:
SG6237
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
160
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5355
Captain / Total hours on type:
5113.00
Copilot / Total flying hours:
4826
Copilot / Total hours on type:
4625
Circumstances:
On 01.07.2019, B737-800 aircraft was involved in an accident (runway excursion) at Mumbai airport while landing in moderate to heavy rain. The aircraft was under the command of an ATPL holder (PF) with a CPL holder as First Officer (PM). There were 160 passengers and 7 crew members on board. There was no injury to any of the passengers or crew members. The aircraft suffered substantial damage. The subject flight was fifth of the day for the aircraft and second for the flight crew. The flight crew had earlier operated Mumbai-Jaipur sector and the incident flight was from Jaipur to Mumbai. There were no technical issues reported by the flight crew either during Mumbai Jaipur sector or on the return leg (Jaipur- Mumbai) till descent into Mumbai. The pilots had carried out briefing amongst themselves for the approach including the weather and Go Around actions, if required. The aircraft commenced descent into Mumbai in the late evening hours. As per the reported weather at the time of approach visibility was 2100 metres in rain making it dark. Reported winds were 090/12 Knots. Runway was wet and the trend provided was ³temporary reduction in visibility to 1500 metres with thunder/ showers of rain´. During descend at approximately 7000' Pressure Altitude, the crew observed an indication for IAS disagree, indicating a discrepancy of airspeed between the instrument sources for the flight crew. Although this indication was momentary, the 'Non-Normal Checklist' was carried out. The indication discrepancy did not recur for the remainder of the flight. The aircraft was radar vectored for an ILS approach for Runway 27 at Mumbai. The approach was stabilized by 3800' Pressure Altitude with landing gear down, flaps 30 and auto brake selected at 3. The autopilot was engaged throughout the descent phase and during approach, the second autopilot was also coupled for the ILS approach. At 100', the autopilot and the auto-throttle were disengaged by the PF. The flare manoeuvre consumed approximately 5807' of the runway length prior to the aircraft touchdown with 3881' of runway remaining. After touchdown, the speed brakes deployed automatically and maximum reverse thrust and wheel brakes were applied. The aircraft exited the paved surface at 65 Knots and came to rest at a distance of 615' beyond the end of the runway. Once the aircraft came to rest, the flight crew advised cabin crew to be at their stations. The pilots were unable to contact ATC through VHF communication. The PF contacted his airline personnel using mobile phone and informed that the aircraft had overrun the runway and requested for step ladders. The ATC activated fire services and the runway was closed for operation. The Cabin crew carried out check on the passengers in the cabin. The fire services reached the aircraft location and verbal communication was established with the flight crew once the cockpit window was opened. Two Fire Services personnel boarded the aircraft from the L1 door using a fire ladder. An assessment of the aircraft structure and occupants was made and the fire services personnel informed the cabin crew that deplaning was to be carried out using fire ladders. There were no injuries during evacuation or otherwise.
Probable cause:
The runway excursion occurred because of combination of:
- Disconnection of auto pilot at an altitude 118' RA with the nose up trim bias without adequate compensation.
- Disconnection of auto throttle at 118' RA at a higher thrust setting for that phase of flight.
- Late touchdown of the aircraft on the runway.
- Reduced visual cues due to heavy rain impacting depth perception and ascertaining of actual touchdown position.
- Tailwind conditions at the time of landing resulting In increasing the distance covered during the extended flare (float).
- Approach with lower flaps (30) than recommended (40).
Final Report:

Crash of an Antonov AN-24RV in Nizhneangarsk: 2 killed

Date & Time: Jun 27, 2019 at 1024 LT
Type of aircraft:
Operator:
Registration:
RA-47366
Survivors:
Yes
Schedule:
Ulan-Ude - Nizhneangarsk
MSN:
7 73 108 04
YOM:
1977
Flight number:
AGU200
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
43
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
15167
Captain / Total hours on type:
10667.00
Copilot / Total flying hours:
6012
Copilot / Total hours on type:
1325
Aircraft flight hours:
38014
Aircraft flight cycles:
18584
Circumstances:
On a flight from Ulan-Ude to Nizhneangarsk, while descending to an altitude of 3,050 metres about 30 km from the destination airport, the crew contacted ATC and reported the failure of the left engine. The approach was continued to runway 22. After touchdown, the crew started the braking procedure when the airplane deviated to the right then veered off runway. It rolled in a grassy area, cwent through the perimeter fence and eventually impacted the building of a sewage treatment plant located 380 metres to the right of the runway centerline. The captain and the flight engineer were killed and the copilot was seriously injured. 10 other occupants were injured. The aircraft was destroyed by a post crash fire.