Crash of a Cessna 208B Grand Caravan in Mundri

Date & Time: Oct 10, 2020
Type of aircraft:
Operator:
Registration:
5H-NWA
Flight Phase:
Survivors:
Yes
Schedule:
Mundri - Juba
MSN:
208B-0891
YOM:
2001
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single engine airplane suffered an accident while taking off from Mundri Airfield, causing the right main gear and the nose gear to be torn off. Also, both wings were severely damaged. There were no fire and no injuries. The aircraft was damaged beyond repair. It seems it was owned by Newton Air and leased to Zantas Air Services.

Crash of a Cessna 414 Chancellor in North Palm Beach

Date & Time: Oct 8, 2020 at 1115 LT
Type of aircraft:
Operator:
Registration:
N8132Q
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
North Palm Beach - Claxton
MSN:
414-0032
YOM:
1969
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1987
Captain / Total hours on type:
897.00
Copilot / Total flying hours:
149
Copilot / Total hours on type:
5
Aircraft flight hours:
6377
Circumstances:
The copilot, who was seated in the right seat, reported that after an uneventful run-up and taxi, the pilot, who was seated in the left seat, initiated the takeoff. The airplane remained on the runway past the point at which takeoff should have occurred and the copilot observed the pilot attempting to pull back on the control yoke but it would not move. The copilot then also attempted to pull back on the control yoke but was also unsuccessful. Observing that the end of the runway was nearing, the copilot aborted the takeoff by reducing the throttle to idle and applying maximum braking. The airplane overran the runway into rough and marshy terrain, where it came to rest partially submerged in water. Postaccident examination of the airplane and flight controls found no evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation. Specifically, examination of the elevator flight control rigging, in addition to functional checks of the elevator, confirmed continuity and normal function. Additionally, the flight control lock was found on the floor near the rudder pedals on the left side of the cockpit. Due to a head injury sustained during the accident, the pilot was unable to recall most of the events that transpired during the accident. The pilot did state that he typically removed the control lock during the preflight inspection and that he would place it in his flight bag. He thought that a shoulder injury may have led to the control lock missing the flight bag, and why it was found behind the rudder pedals after the accident. Review and analysis of a video that captured the airplane during its taxi to the runway showed that the elevator control position was similar to what it would be with the control lock installed. While the pilot and copilot reported that they did not observe the control lock installed during the takeoff, the position of the elevator observed on the video, the successful postaccident functional test of elevator, and the unsecured flight control lock being located behind the pilot’s rudder pedals after the accident suggest that the control anomaly experienced by the pilots may have been a result of the control lock remaining inadvertently installed and overlooked by both pilots prior to the takeoff. According to the airframe manufacturer’s preflight and before takeoff checklists, the flight control lock must be removed during preflight, prior to engine start and taxi, and the flight controls must be checked prior to takeoff. Regardless of why the elevator control would not move during the takeoff, a positive flight control check prior to the takeoff should have detected any such anomaly. It is likely that the pilot failed to conduct a flight control check prior to takeoff. Further, the pilot failed to abort the takeoff at the first indication that there was a problem. Although delayed, the copilot’s decision to take control of the airplane and abort the takeoff likely mitigated the potential for more severe injury to the occupants and damage to the airplane.
Probable cause:
The pilot’s inadequate preflight inspection during which he failed to detect a flight control abnormality, and his failure to expediently abort the takeoff, which resulted in the co-pilot performing a delayed aborted takeoff and the subsequent runway overrun.
Final Report:

Crash of a Piper PA-46R-350T Matrix in Vannes

Date & Time: Oct 5, 2020 at 1415 LT
Registration:
N898BB
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Vannes - La Môle
MSN:
46-92057
YOM:
2008
Location:
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
845
Captain / Total hours on type:
565.00
Circumstances:
On the morning of the day of the accident, the pilot, accompanied by a passenger, flew under IFR flight mode from La Môle (83) to Quiberon (56). The flight took 3 hours and 40 minutes and the return was scheduled in the afternoon. After landing in Quiberon, the pilot learned that there was no possibility to refuel with AVGAS, information that was not specified by NOTAM. The pilot then decided to refuel at Vannes-Meucon Airport before leaving to St Tropez-La Môle. He said he was upset by this situation and by the bad weather conditions in the area. During the pre-flight visit to Quiberon, the pilot added oil. He indicates that he also carried out a pre-flight inspection before takeoff from Vannes. During the takeoff roll from runway 22 at Vannes-Meucon Airport, the rotation took place in the first third of the runway. Just after liftoff, he saw the engine cowling open. He immediately thaught he forgot to tighten the dipstick and decided to abort the takeoff and landed on the remaining runway. The runway being long, he believed he can stop before the runway end. He put the power levers in the "full, reduced and choke" position and tried to land the plane quickly. As the aircraft already reached a high speed, it landed 200 metres short of runway end and deviated longitudinally and crossed the runway end safety area, known as RESA. It came to a stop a 100 metres further on an embankment. The left wing was partially torn off and the aircraft was damaged beyond repair. There was no fire. Both occupants escaped uninjured.
Final Report:

Crash of a Piper PA-46-500TP Malibu Meridian in Lake Elmo

Date & Time: Oct 2, 2020 at 1512 LT
Registration:
N62ZM
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Lake Elmo - Mesquite
MSN:
46-97087
YOM:
2001
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3828
Captain / Total hours on type:
42.00
Aircraft flight hours:
2850
Circumstances:
On October 2, 2020, about 1512 central daylight time (CDT), a Piper PA-46-500TP, N62ZM, was substantially damaged when it was involved in an accident near Lake Elmo, Minnesota. The airline transport pilot sustained serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight. The pilot reported that shortly after takeoff from runway 32 at the Lake Elmo airport (21D) and following landing gear retraction, he noticed a “hiccup” in the engine power and immediately started a turn back towards the airport. During the turn, all engine power was lost and the pilot executed a forced landing into a field of standing corn. The airplane impacted the terrain, bounced, and came to rest upright in the corn about ½ mile northwest of the departure end of runway 32. The airplane sustained substantial damage to the right wing as a result of the impact and post-crash fire. The airplane was equipped with a Pratt & Whitney PT6A turboprop engine.
Probable cause:
A total loss of engine power for reasons that could not be determined.
Final Report:

Crash of a Cessna 208B Grand Caravan in Guaymaral

Date & Time: Sep 22, 2020 at 0655 LT
Type of aircraft:
Registration:
HK-4669G
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Guaymaral – Flandes
MSN:
208B-0968
YOM:
2002
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13220
Captain / Total hours on type:
1506.00
Aircraft flight hours:
2830
Circumstances:
After takeoff from Guaymaral-Flaminio Suárez Camacho Airport runway 29, while climbing to a height of 200 feet, the engine suffered and explosion and lost power. The airplane started to descend, impacted a brick wall and lost its undercarriage. It then crash landed in a prairie and slid for few dozen metres before coming to rest. All five occupants escaped uninjured. The accident occurred three minutes after takeoff.
Probable cause:
The investigation determined that the accident was caused by the following probable causes:
- Emergency landing of the aircraft on an unprepared field, as a result of a decrease in power, generated by engine failure.
- An engine failure caused by the fracture of three (3) blades of the rotor disk of the high pressure compressor, which caused severe backwards damage to the hot and power section.
Contributing Factors:
- Non-compliance in the engine maintenance process, of what was ordered in AD. No. 2014-17-08R1 FAA (year 2014), which establishes the replacement of the engine blades high pressure compressor in anticipation of material failures in these components.
- Deficient maintenance processes by the provider of this service to the aircraft HK4669G, by not detecting the condition of the high-pressure rotor blades in the boroscopic inspections of the high pressure during routine boroscopic inspections.
- Deficient verification of the Operator's contracted maintenance processes, by not verifying the quality and compliance the quality and full compliance of these processes by the maintenance service provider.
Final Report:

Crash of an Antonov AN-26 in Juba: 7 killed

Date & Time: Aug 22, 2020 at 0840 LT
Type of aircraft:
Operator:
Registration:
EX-126
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Juba - Wau - Aweil
MSN:
11508
YOM:
1981
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
Shortly after takeoff from Juba Airport runway 31, while climbing, the aircraft lost height and crashed in a prairie located near Referendom, about 4 km northwest of Juba Airport, bursting into flames. The aircraft was destroyed by impact forces and a post crash fire. A passenger was seriously injured while seven other occupants were killed. The aircraft was on its way to Aweil with an intermediate stop in Wau, carrying a load of foods and money for wages on behalf of the World Food Programme (WFP). It was reported that the aircraft was loaded with 8 tons of cargo while the maximum allowable would be 5,5 tons.

Crash of a Beechcraft 200 Super King Air in Rockford: 1 killed

Date & Time: Aug 20, 2020 at 1542 LT
Operator:
Registration:
N198DM
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Rockford - DuPage
MSN:
BB-1198
YOM:
1984
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
3650
Aircraft flight hours:
8018
Circumstances:
On August 20, 2020, about 1542 central daylight time, a Beech B200 airplane (marketed as a King Air 200), N198DM, was destroyed when it was involved in an accident near Rockford, Illinois. The private pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 positioning flight. The purpose of the flight was to relocate the airplane to the pilot's home base at the DuPage Airport (DPA), West Chicago, Illinois. The airplane had been at Chronos Aviation, LLC (a 14 CFR Part 145 repair station), at the Rockford International Airport (RFD), Rockford, Illinois, for maintenance work. Multiple airport-based cameras recorded the accident sequence. The videos showed the airplane taking off from runway 19. Shortly after liftoff, the airplane started turning left, and the airplane developed a large left bank angle as it was turning. The airplane departed the runway to the left and impacted the ground. During the impact sequence, an explosion occurred, and there was a postimpact fire. A video study estimated the airplane’s maximum groundspeed during the takeoff as 105.5 knots (kts). Data recovered from an Appareo Stratus device onboard the airplane showed that about 1538, the airplane began taxing to runway 19. At 1540:34, the airplane crossed the hold short line for runway 19. At 1541:19, the airplane began a takeoff roll on runway 19. At 1541:42, the airplane began to depart the runway centerline to the left of the runway. Subsequent tracklog points showed the airplane gaining some altitude, and the tracklog terminated adjacent to a taxiway in a grassy area. The Appareo Stratus data showed the airplane began to increase groundspeed on a true heading of roughly 185° about 1541. Airplane pitch began to increase at 1541:41 as the groundspeed reached about 104 kts. The groundspeed increased to 107 kts within the next 2 seconds, and the pitch angle reached around 4° nose-up at this time. In the next few seconds, pitch lowered to around 0° as the groundspeed decayed to around 98 kts. The pitch then became 15° nose-up as the groundspeed continued to decay to about 95 kts. A right roll occurred of about 13° and changed to a rapidly increasing left roll over the next 5 seconds. The left roll reached a maximum of about 86° left as the pitch angle increasingly became negative (the airplane nosed down). The pitch angle reached a maximum nose down condition of -73°. The data became invalid after 1541:53.4. An airplane performance study based on the Appareo Stratus data showed that during the takeoff from runway 19, the airplane accelerated to a groundspeed of 98 kts and an airspeed of 105 kts before rotating and lifting off. The airplane pitched up, climbed, and gained height above the ground. Then, 4 seconds after rotation, the airplane began descending and slowing, consistent with a loss of power. A nose-left sideslip, a left side force, and a left roll were recorded, consistent with the loss or reduction in thrust of the left engine. The sideslip was reduced, likely due to opposite rudder input, and the airplane briefly rolled right. The airplane pitched up and was able to begin climbing again; however, it continued to lose speed. The sideslip then reversed, and the airplane rolled left again and impacted the ground. One witness reported that he observed the accident sequence. He did not hear any abnormal engine noises, nor did he see any smoke or flames emit from the airplane before impact. The airplane came to rest on a flat grass field to the east of runway 19 on airport property. The airplane sustained fire damage and was fragmented from impacting terrain.
Probable cause:
The pilot’s failure to maintain airplane control following a reduction of thrust in the left engine during takeoff. The reason for the reduction in thrust could not be determined based on the available evidence.
Final Report:

Crash of a Cessna 208B Grand Caravan in Fangak

Date & Time: Aug 16, 2020
Type of aircraft:
Operator:
Registration:
5Y-SAV
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
208B-0312
YOM:
1992
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single engine aircraft completed a humanitarian flight from Juba to Fangak on behalf of the NGO 'Nile Hope'. On board were five passengers and two pilots. During the takeoff roll on a muddy airstrip, the aircraft went out of control, veered off runway and collided with a tree. The right wing was torn off and the aircraft came to rest upside down. Two passengers were slightly injured.

Crash of a Harbin Yunsunji Y-12-II in Dhobley

Date & Time: Aug 4, 2020
Type of aircraft:
Operator:
Registration:
KAF128
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Dhobley - Nairobi
MSN:
0097
YOM:
1997
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft was returning to Nairobi-Eastleigh (Moi Air Base) after various supplies were delivered at Dhobley Airport on behalf of the Amisom, the African Union Mission in Somalia. Upon takeoff from Dhobley Airstrip, the aircraft crashed in unclear circumstances. All 10 occupants were injured while the aircraft was damaged beyond repair.

Crash of a Cessna 402C in Papa Lealea

Date & Time: Jul 26, 2020 at 1246 LT
Type of aircraft:
Operator:
Registration:
VH-TSI
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Papa Lealea - Mareeba
MSN:
402C-0492
YOM:
1981
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On 26 July 2020, at 12:46 local time (02:46 UTC), a Cessna 402C aircraft, registered VH-TSI collided with trees during an aborted take-off at an uncommissioned field near Papa-Lealea, about 16 nm North-West of Port Moresby, Papua New Guinea. The pilot, during interview with the AIC, stated that he departed at 09:30 that day from Mareeba Airport, Queensland Australia and tracked towards the North North-East with a planned track set slightly left of Jacksons International Airport, Port Moresby, National Capital District, Papua New Guinea. As the aircraft neared the Southern shoreline (within the Caution Bay area), he diverted left and began tracking towards the North West along the coast in order to avoid flying over villages in the area. He subsequently crossed over land before turning back to approach the intended landing field. As the aircraft approached to land, the outboard section of the left wing was clipped by a tree and separated from the aircraft. According to the pilot, he continued on with the approach and landed on the field at about 12:20. The pilot reported that he had flown to and within Papua New Guinea in the past and was familiar with the area and airspace. He confirmed that after departing Mareeba, he switched off the transponder. After shutting down the aircraft, the aircraft was refuelled with jerrycans full of fuel (AvGas) and loaded with cargo by persons waiting on the ground. The pilot reported that he estimated that a distance of 800 m would be required for the take-off. According to the pilot, at about 12:40, he lined up and commenced his take-off roll from the Southern end of the field. As the aircraft lifted off, he noticed that the airspeed indicator (ASI) was not working. He also observed that the aircraft was not achieving a positive rate of climb. He subsequently pulled the throttles back and manoeuvred the aircraft back towards the ground. The aircraft touched down with a speed that the pilot described as higher than normal, with about 400 m of usable field remaining. The aircraft continued off the end of the field and into the bushes clipping trees along the way until it came to rest. The pilot informed the AIC that he was the sole occupant of the aircraft, and sustained minor injuries as a result of the occurrence. The aircraft was substantially damaged. The investigation confirmed that the fire to the left wing and engine was a post-accident event and was deliberate. The pilot was later arrested and a load of 500 kilos of cocaine distributed in 28 bales was found at the scene.
Probable cause:
The investigation determined that the separation of the outboard section of the left wing, clipped by a tree during the approach to land phase, affected the ability of the left wing to produce lift. The investigation could not conclusively determine the actual weight and balance of the aircraft as it was not possible to determine the quantity and quality of fuel on board, nor the weight and distribution of the cargo that was on board. The evidence gathered during the investigation did not allow the AIC to discard overweight, balance or centre of gravity issues due to improper loading or restrain of the cargo as factors contributing to the inability of the aircraft to obtain a positive rate of climb during take-off. The evidence of tire marks found by the investigators on the uncommissioned field indicated that the aircraft touched down about 400 m before the end of the field, distance that was not enough for the aircraft to come to a stop, continuing its landing roll into the bushes and impacting trees until it got to its final position. The investigation determined that the aircraft was not airworthy at the time of the accident and was unserviceable for the conduct of the flight. The investigation also determined that there was no proper document control to conduct timely scheduled maintenance and that there was no record of a certificate of airworthiness (CoA) at the time of the accident.
Final Report: