Crash of a Embraer EMB-500 Phenom 100 in São Pedro

Date & Time: Oct 30, 2020 at 1750 LT
Type of aircraft:
Operator:
Registration:
PR-LMP
Survivors:
Yes
Schedule:
São Paulo – São Pedro
MSN:
500-00094
YOM:
2009
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7300
Captain / Total hours on type:
2350.00
Copilot / Total flying hours:
676
Copilot / Total hours on type:
409
Circumstances:
After touchdown on runway 29 at São Pedro Airport, the crew initiated the breaking procedure but the airplane failed to stop within the remaining distance. It overran, collided with various obstacles, went down an embankment of 10 metres and eventually came to rest 130 metres further, bursting into flames. All four occupants evacuated safely and the airplane was destroyed by a post crash fire.
Probable cause:
Studies and research showed that the low deceleration of the aircraft and the limitation of the hydraulic pressure provided by the brake system were compatible with a slippery runway scenario. Thus, one inferred that the runway was contaminated, a condition that would reduce its coefficient of friction and impair the aircraft's braking performance, making it impossible to stop within the runway limits. On account of the mirroring condition of the runway in SSDK, it is possible that the crew had some difficulty perceiving, analyzing, choosing alternatives, and acting appropriately, given a possible inadequate judgment of the aircraft's landing performance on contaminated runways.
Final Report:

Crash of an Antonov AN-32A in Iquitos

Date & Time: Oct 14, 2020 at 1321 LT
Type of aircraft:
Operator:
Registration:
OB-2120-P
Flight Type:
Survivors:
Yes
Schedule:
Lima - iquitos
MSN:
18 05
YOM:
1989
Country:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After touchdown on runway 06 at Iquitos-Coronel Francisco Secada Vignetta Airport, the aircraft went out of control and veered off runway to the left. It contacted small trees and bushes, lost its right wing and came to rest 100 metres to the left of the runway, broken in two. A fire erupted but was quickly extinguished. All four crew members were slightly injured and the aircraft was destroyed.

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 an Antonov AN-26Sh at Chuhuiv AFB: 26 killed

Date & Time: Sep 25, 2020 at 2050 LT
Type of aircraft:
Operator:
Registration:
76 yellow
Flight Type:
Survivors:
Yes
Schedule:
Chuhuiv AFB - Chuhuiv AFB
MSN:
56 08
YOM:
1977
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
20
Pax fatalities:
Other fatalities:
Total fatalities:
26
Circumstances:
The aircraft was engaged in a local training flight at Chuhuiv AFB, carrying 7 crew members and 20 cadets. On approach to runway 16, the crew apparently encountered engine problems when the aircraft lost height and crashed 2 km short of runway threshold near motorway E40, bursting into flames. Two passengers were seriously injured while 25 other occupants were killed. Few hours later, one of the survivors died from his injuries.

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 a Piper PA-46-310P Malibu in Hilltop Lakes: 4 killed

Date & Time: Sep 20, 2020 at 1050 LT
Operator:
Registration:
N236KM
Flight Type:
Survivors:
No
Schedule:
Horseshoe Bay – Natchitoches
MSN:
46-8508014
YOM:
1985
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
1107
Circumstances:
While in cruise flight at 19,000 ft mean sea level (msl), the pilot declared an emergency to air traffic control and stated that the airplane had lost engine power and that he needed to divert. The pilot elected to divert to an airport that was about 5 miles south of his position. Archived automatic dependent surveillance-broadcast data and commercially available flight track data showed that a descent was initiated from 19,000 ft and the airplane proceeded directly to, and circled around, the airport one time while descending. The last data point showed the airplane at 1,250 ft msl (about 750 ft above ground level) and about 1 mile north of the approach end of the runway. From the cruise altitude of 19,000ft until the last data point, about 12 minutes and 45 seconds had elapsed, which equated to an average descent rate of about 1,392ft per minute. Witnesses located about 1/4 mile south of the end of the runway on a miniature golf course noticed the propeller on the airplane was not turning. They stated that they saw the airplane in a “really hard” left bank; the nose of the airplane dropped, and it impacted the ground in a near vertical attitude. The airplane came to rest along a road about 200 ft south of the airport property. The airplane impacted the terrain in a nose low, near vertical attitude and sustained substantial damage to fuselage and both wings. It is likely that, based on the location of the runway, relative to the miniature golf course, the pilot initiated the left bank to avoid bystanders on the ground and inadvertently exceeded the wing’s critical angle of attack, which resulted in an aerodynamic stall. The airplane was equipped with an engine trend monitor (ETM), which captured various events concerning the accident flight, including engine start, operating limit exceedances, and power checks. The ETM captured a power check while the airplane was at 19,100 ft. About 3 minutes 32 seconds later, an engine off event was recorded. The ETM further captured a logon message, which was consistent with the power being cycled, at an altitude of 3,542 ft, 9 minutes, 52 seconds later. The ETM did not record any start attempts between the logged engine off event and when power was lost to the unit. A postaccident examination of the airframe, engine, and accessories did not reveal any mechanical malfunctions or anomalies that would have precluded normal operation. Although it cannot be determined whether a restart attempt would have been successful, the data were consistent with a restart not being attempted. Both the engine failure and power off landing checklists contained instructions for the pilot to establish the airspeed at 90 knots; however, when the winds aloft were applied to the reported groundspeeds, it was evident this did not occur. Furthermore, the power off landing checklist instructed the pilot to be about 1,500 ft above the airport on the downwind leg; however, data indicate that the airplane was about 5,000 ft above the airport on the downwind leg. The rapid descent from 5,000 ft on the downwind leg to about 750 ft above ground level on the final leg resulted in an unstabilized approach.
Probable cause:
The loss of engine power for reasons that could not be determined and the pilot’s failure to maintain control of the airplane which resulted in an aerodynamic stall and spin. Contributing to the accident was the pilot’s failure to establish and maintain a proper glidepath.
Final Report:

Crash of a Pilatus PC-6/B2-H4 Turbo Porter in Livrasco: 2 killed

Date & Time: Sep 20, 2020 at 0949 LT
Operator:
Registration:
T7-SKY
Survivors:
Yes
Schedule:
Cremona - Cremona
MSN:
902
YOM:
1993
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
4400
Captain / Total hours on type:
2500.00
Aircraft flight hours:
4920
Circumstances:
The single engine airplane departed Cremona-Migliaro Airport in the morning on a local skydiving flight, carrying eight skydivers and one pilot. This was the second sortie of the day. Once the altitude of 4,000 metres was reached, all eight skydivers successfully jumped out and the pilot started the descent to return to the airport. While descending to runway 11, the airplane collided with the eighth skydivers that hit the left wing and the vertical stabilizer. A large section of the left wing separated, causing the airplane to enter an uncontrolled descent and to crash in a cornfield located in Livrasco, about two km north of the airport. The pilot and the skydiver were killed. The airplane was totally destroyed.
Probable cause:
The cause of the accident was an in-flight collision between the Pilatus PC-6 descending and a free-falling track-suit parachutist. This collision resulted in a loss of control of the aircraft in flight and the destruction of the left wing of the aircraft, which fell to the ground uncontrolled.
The following factors contributed to the accident:
- Inadequate coordination between pilot and parachutist in relation to their respective descent and drift paths,
- The meteorological conditions at the time of the parachutist's exit from the aircraft, which took place in cloud and in the absence of visual contact with the ground, in a situation, therefore, incompatible with VFR flight rules and ENAC regulations for parachuting,
- The absence of codified procedures at the Italian level, integrating the procedures for jumps with those of aircraft operators used for parachute jumps, including deconfliction between descending aircraft and parachutists performing drift or wingsuit jumps.
The inadequate coordination between the pilot and parachutist in relation to their respective descent and drift paths could also be attributable to the absence of a responsible person to ensure that the above mentioned coordination was in place. In addition to the above mentioned criticalities, the ANSV investigation activity revealed, also in the present case, a general lack of rules and controls regarding parachuting activities carried out outside of training activities, which reasonably contributed to the occurrence of the investigated aircraft accidents.
Final Report: