Crash of a Let L-410UVP in Juba

Date & Time: Jan 27, 2023
Type of aircraft:
Registration:
EY-473
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Juba - Lankien
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Juba Airport runway 31, while climbing, the crew encountered an unexpected situation and was forced to attempt an emergency landing. The airplane crash landed in an area located in the Hai Referendum district about 3 km northwest of the airport. All five occupants escaped with minor injuries while the airplane was severely damaged.

Crash of a Swearingen SA227AT Expediter in Waukesha

Date & Time: Nov 15, 2022 at 1500 LT
Operator:
Registration:
N247DH
Flight Type:
Survivors:
Yes
Schedule:
New Orleans – Waukesha
MSN:
AT-626B
YOM:
1985
Flight number:
AMF7141
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2848
Captain / Total hours on type:
1316.00
Copilot / Total flying hours:
1320
Copilot / Total hours on type:
537
Aircraft flight hours:
29256
Circumstances:
The flight crew reported that while on an instrument landing system (ILS) approach with the autopilot system engaged in approach mode, they noticed that the airplane flight director indicated a climbing right turn but the airplane was still tracking the localizer and glideslope. The airplane’s ice protection was on, and no visible ice had accumulated. They reported that they disconnected the autopilot, and the airplane suddenly rolled to the right. They attempted to regain control by increasing engine power and applying counteractive control inputs, but the airplane impacted the ground in a near-wings-level attitude. Examination of the airplane’s primary flight control system and engines after the accident did not reveal any defects. The rudder trim was neutral, and the pitch trim was airplane nose up. Aileron trim could not be determined. Examination of the airplane’s autopilot components revealed deficiencies in the yaw damper system that rendered it inoperative; however, on the accident airplane the yaw damper system was an optional component and was not necessary for airplane operation. Testing of the remaining autopilot components revealed some deficiencies that could have degraded performance but would not have resulted in a complete failure of the automatic flight control system. A performance study based on ADS-B data showed that the airplane intercepted the localizer and glideslope for the ILS approach and was descending in a level attitude. While maintaining the ILS approach guidance, the airplane slowed below the 130 knots (kts) airspeed that the crew stated was the desired approach speed. The airspeed continued to slow to about 102 kts when the ADS-B data indicated that the airplane rolled slightly to the right, likely corresponding to the flight crew’s description of events after they disconnected the autopilot. The airplane continued to slow below 100 kts and the airplane was at a bank angle of 27° right wing down. Subsequently, the descent rate increased to over 4,000 ft/min and airspeed increased while ground speed remained between 80 and 90 kts. The airplane rolled sharply to the left. The sudden roll and loss of altitude after reaching a low airspeed was consistent with an aerodynamic stall. Based on the available evidence, the airplane entered an inadvertent aerodynamic stall due to exceedance of the critical angle of attack after the flight crew allowed the airspeed to decay during the instrument approach. Although an unknown anomaly in the flight director system could have resulted in the crew becoming fixated on an errant flight director indication at the expense of airspeed control, the postaccident component examination was not able to explain the errant flight director indication that the flight crew described.
Probable cause:
The flight crew’s failure to maintain adequate airspeed and their exceedance of the airplane’s critical angle of attack during the instrument approach, which resulted in an aerodynamic stall. Contributing to the accident was an undetermined anomaly in the airplane flight director system which resulted in the flight crew likely becoming fixated on the anomaly at the expense of airspeed control.
Final Report:

Crash of a Let L-410UVP-E20 in South Kivu: 3 killed

Date & Time: Nov 3, 2022 at 1432 LT
Type of aircraft:
Operator:
Registration:
9S-GPK
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Kasese – Goma
MSN:
86 17 02
YOM:
1986
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
15750
Aircraft flight hours:
9468
Circumstances:
The airplane departed Kasese Airport at 1500LT on a cargo flight to Goma, carrying two pilots, one passenger and a load of various goods for a total weight of one ton. En route, weather conditions deteriorated with low clouds and heavy rain falls. As the airplane failed to arrive at destination, SAR operations were initiated and the wreckage was found two days later in a dense wooded area located in South Kivu, about 139 km southwest of Goma. The airplane was destroyed by a post impact fire and all three occupants were killed.
Crew:
Peter Sabo +1.
Probable cause:
Investigations were unable to determine the exact cause of the accident. Nevertheless, it may be the consequence of an insufficient consideration of weather conditions during flight preparation or during the flight itself, to a system or component failure, or to human error (error of judgment and decision-making).
Final Report:

Crash of a Swearingen SA227AC Metro III in Saltillo

Date & Time: Sep 15, 2022 at 1635 LT
Type of aircraft:
Operator:
Registration:
XA-UMW
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Saltillo - Laredo
MSN:
AC-717
YOM:
1988
Flight number:
VTM717
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After takeoff from runway 35 at Saltillo-Plan de Guadalupe Airport, while climbing to an altitude of 800 feet, the crew encountered technical issues with the right engine that lost power and started to vibrate. The crew reduced his altitude and attempted an emergency landing when the aircraft crashed in bushes about 4,5 km northwest of the airport and came to rest. Both pilots were uninjured and the aircraft was damaged beyond repair.

Crash of a PZL-Mielec AN-28 in Kasese: 3 killed

Date & Time: Sep 10, 2022 at 1230 LT
Type of aircraft:
Operator:
Registration:
9S-GAX
Flight Type:
Survivors:
No
Schedule:
Bukavu – Kasese
MSN:
1AJ002-08
YOM:
1986
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The airplane departed Bukavu-Kavumu Airport at 1150LT on a cargo flight to Kasese with three crew members on board. As the airplane failed to arrive at destination, SAR operations were initiated and the wreckage was found two days later in a wooded and hilly terrain near Kasese. All three occupants were killed.

Crash of an Antonov AN-12BK near Eleftheroupolis: 8 killed

Date & Time: Jul 16, 2022 at 2247 LT
Type of aircraft:
Operator:
Registration:
UR-CIC
Flight Type:
Survivors:
No
Schedule:
Niš – Amman – Riyadh – Ahmedabad – Dhaka
MSN:
01 34 77 01
YOM:
1971
Flight number:
MEM3032
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
The four engine airplane departed Niš at 2036LT on a cargo flight to Amman, carrying eight crew members and a load of 12 tons of various goods. Bound to the southeast over the Aegean Sea, the crew was cruising at FL210 when they reported technical problems. Cleared to divert to Kavala Airport, the pilot made a 180 turn and started the descent. On approach to Kavala Airport at night with engine n°4 on fire, the aircraft entered an uncontrolled descent and crashed at a speed of 202 knots in an agricultural zone located just out of the village of Eleftheroupolis, bursting into flames. The aircraft disintegrated on impact and all eight occupants were killed. The wreckage was found 12 km west of Kavala Airport. According to the Serbian Defense Minister Nebojsa Stefanovic, the plane was carrying a load of 11-12 tons of armaments, including flare mortar mines, bound for Bangladesh.

Crash of an Antonov AN-30M near Olenyok

Date & Time: Jun 22, 2022
Type of aircraft:
Operator:
Registration:
RA-30001
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Yakutsk - Olenek
MSN:
14 02
YOM:
1978
Flight number:
9424
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine airplane departed Yakutsk Airport on a cargo flight to Olenyok, carrying seven crew members and a load of 6,3 tons of food. En route, the airplane suffered a double engine failure. The crew reduced his altitude and attempted an emergency landing. The airplane crash landed in a wooded area located 70 km from Olenyok and came to rest. All seven crew members evacuated the cabin, among them three were slightly injured. The aircraft was damaged beyond repair.
Probable cause:
It is believed that the double engine failure is the consequence of a fuel exhaustion.

Crash of a PZL-Mielec AN-2R near Sebyan-Kyuyol: 2 killed

Date & Time: Jun 21, 2022 at 0830 LT
Type of aircraft:
Operator:
Registration:
RA-17742
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Us-Khatyn – Vertikal’nyy
MSN:
1G203-03
YOM:
1983
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
10700
Captain / Total hours on type:
10700.00
Copilot / Total flying hours:
1965
Copilot / Total hours on type:
1600
Circumstances:
The single engine airplane departed Us-Khatyn on a cargo flight to Vertikal'nyy, carrying one passenger and two pilots. En route, weather conditions worsened and the visibility was reduced due to fog. The airplane impacted tree tops and crashed on the slope of a wooded terrain located about 46 km southeast of the village of Sebyan-Kyuyol. As the airplane failed to arrive at destination (the flight was supposed to be 2 hours and 30 minutes), SAR operations were initiated. The wreckage was found 10 days later, on July 1st, in an uninhabited area. Both pilots were killed and the passenger was found alive after he found refuge in a fishing house where he could find food.
Probable cause:
Controlled flight into terrain after the crew continued to fly under VFR mode in IMC conditions.
The following contributing factors were identified:
- Unreasonable flight decision taken by the flight crew,
- The forecasted weather on the declared route did not ensure compliance with ATC,
- Failure of the pilot-in-command to take timely measures to return to the departure airfield or to take other actions to change the flight plan.
Final Report:

Crash of an Embraer EMB-110P1 Bandeirante in Eldorado do Sul

Date & Time: May 20, 2022
Operator:
Registration:
PT-SHN
Flight Type:
Survivors:
Yes
Schedule:
Jundiaí – Eldorado do Sul
MSN:
110-460
YOM:
1985
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The airplane departed Jundiaí on a cargo flight to Eldorado do Sul, carrying two pilots and a load of automotive parts. On final approach, the airplane crash landed in a rice paddy field and came to rest with its left wing detached. Both pilots were slightly injured.

Crash of a Cessna 208B Grand Caravan in Heyburn: 1 killed

Date & Time: Apr 13, 2022 at 0832 LT
Type of aircraft:
Operator:
Registration:
N928JP
Flight Type:
Survivors:
No
Site:
Schedule:
Salt Lake City – Burley
MSN:
208B-2428
YOM:
2013
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1380
Captain / Total hours on type:
193.00
Aircraft flight hours:
5116
Circumstances:
The pilot flew two RNAV (GPS) runway 20 instrument approaches at the Burley Municipal Airport, Burley, Idaho in instrument meteorological conditions (IMC). The accident occurred during the second approach. For the first instrument approach, the pilot configured the airplane with flaps up and flew the final approach segment at speeds above the operator’s training standard of 120 knots indicated airspeed (KIAS).The pilot flew a low pass over the runway, most likely to assess the landing conditions in accordance with company policy, determined the conditions were acceptable, initiated the missed approach and requested to return flying the same approach. The pilot elected to not use flaps during the second approach but slowed the approach speed during the final approach leg. Reported weather had improved and visibility had increased to about 2.5 miles. During this approach, the airplane intercepted and remained on the glide path to the stepdown fix. The last automatic dependent surveillance - broadcast (ADS-B) equipment plot recorded the airplane about a mile past this fix, or about 0.6 nautical miles (nm) from the displaced threshold, on the glide path, and at an estimated 85 knots calibrated airspeed (KCAS), which was slower than the airplane’s 95-knot minimum speed for flaps up in icing conditions. Shortly afterward, the airplane descended about 130 ft below the glide path, striking an agglomerate stack atop a potato processing plant, fatally injuring the pilot and substantially damaging the airplane. A witness reported seeing the airplane come out of the clouds and immediately enter a steam cloud coming from six other stacks before striking the accident stack. A security camera at the processing plant captured the last moments of the airplane’s flight as it came into view in a wings-level, flaps-up, nose-high descent and just before it impacted the stack. While snow and visible moisture were present, the agglomerate stack was always in clear view during the Page 2 of 24 WPR22FA151 video, with only partial sections obscured. The witness’s account of hearing the engine noise increase and then the nose lift-up may have been the pilot’s attempt to avoid the obstacle. The Federal Aviation Administration’s (FAA) Aeronautical Information Manual advises pilots to avoid overflight of exhaust stacks; however, the accident stack was directly underneath the instrument approach course and overflight would be expected. Postaccident examination of the airplane, conducted hours after the accident, revealed no structural icing on the wings and empennage. Examination of the airframe and powerplant revealed no mechanical malfunctions or failures that would have precluded normal operation. The flaps were up, and a review of the manifest revealed the airplane was loaded within the specifications of the manifest and within the center of gravity limits. Between 2016 and 2017, the FAA conducted two aeronautical studies regarding the stack structures. In the first study, the FAA determined that many of the stack structures were a hazard to air navigation that required mitigation by the processing plant. As an interim measure, the FAA placed the runway 20 visual approach slope indicator (VASI) out of service because the stacks penetrated the obstruction clearance surface and were deemed hazardous to aviation. After determining that they needed to increase the height of the stacks, the plant then modified their proposal; the proposed height increase necessitated a second study. The second study determined the agglomerate stack and the row-of-six stacks exceeded the Code of Federal Regulations (CFR) section 77 standards and provided mitigating actions that included painting the stacks with high visibility white and aviation orange paint and equipping the stacks with red flashing warning lights. The control measures also included the permanent removal of the VASI. On the day of the accident, the agglomerate stack and row-of-six stacks had not been painted to the standard required by the FAA. The warning lights had been installed, and five of the row-of-six stacks were equipped with flashing red lights. The agglomerate stack warning light was stolen following the accident, so an accurate determination of its operating status could not be made. The existing paint scheme and the visible moisture emitted by the stacks provided a low contrast to the environmental background. This low contrast and the lack of a visual glide slope indicator may have caused difficulty for the pilot in maintaining a safe altitude during the visual portion of the approach to the runway. A white and aviation orange paint scheme, as identified in the regulations, may have offered a higher contrast and thus an adequate warning once the pilot transitioned to visual conditions.
Probable cause:
The pilot’s failure to maintain altitude during an instrument approach, which resulted in a descent below the approach path and impact with a vent stack. Also causal was the failure of the processing plant to correctly paint the vent stacks, which had been determined by the FAA to be a hazard to navigation due to their proximity to the landing approach path. Contributing to the accident was the likely distraction/illusion/obscuration created by steam from the processing plant, which intermittently obscured the runway.
Final Report: