Crash of a Cessna 340 in Covington: 2 killed

Date & Time: Apr 21, 2022 at 1844 LT
Type of aircraft:
Operator:
Registration:
N84GR
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Covington - Covington
MSN:
340-0178
YOM:
1973
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
0
Captain / Total hours on type:
0.00
Copilot / Total flying hours:
3148
Copilot / Total hours on type:
0
Aircraft flight hours:
7581
Circumstances:
The student pilot, who was the new owner of the multi-engine airplane, and a private pilot flew commercially to Lubbock, Texas, utilized a ride-hailing service to drive to Portales, New Mexico; they met with the former owner of the airplane to finalize the purchase of the airplane and flew it back to Georgia the same day. The next day, the student pilot commenced flight training with the private pilot who offered to provide flight instruction to the student pilot in the student pilot’s newly acquired multi-engine airplane, even though he did not possess a flight instructor’s rating or a multi-engine airplane rating. Radar data showed that the track of the accident airplane's route consisted of their departure airport, a midway stop, and the third leg of the flight, where it crashed during the approach to their destination airport. Witnesses observed a sharp right turn before the airplane’s spiraling descent and impact with terrain and unoccupied semi-trailers. Surveillance footage from a parking lot security camera captured the airplane in a right spiral turn just before the accident. The airplane was destroyed by impact forces and the postimpact fire. The postaccident examination of the airframe, engines, and propellers revealed no anomalies that would preclude normal engine and airplane performance. Additionally, a review of the maintenance logbook revealed that the airplane was overdue for its annual maintenance inspection; no special flight permit (ferry permit) was obtained from the Federal Aviation Administration (FAA) for its return flight to Georgia. Toxicological testing of the student pilot revealed the presence amphetamine, a prescription Schedule II controlled substance that may result in cognitive deficits that pose a risk to aviation safety; however, its effect, if any on the accident flight could not be determined. It is likely that the private pilot’s failure to maintain aircraft control was exacerbated by his lack of a multi-engine airplane rating, his lack of a flight instructor rating, and his poor decision making.
Probable cause:
The private pilot’s loss of control in flight, which resulted in a collision with terrain. Contributing to the accident was the student pilot’s decision to obtain flight instruction from the private pilot and the private pilot's insufficient qualifications to fly or to provide flight instruction in a multi-engine airplane.
Final Report:

Crash of a Britten-Norman BN-2A-9 Islander in Culebra

Date & Time: Feb 15, 2022 at 0955 LT
Type of aircraft:
Operator:
Registration:
N821RR
Flight Type:
Survivors:
Yes
Schedule:
San Juan - Culebra
MSN:
338
YOM:
1973
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
16550
Captain / Total hours on type:
0.00
Copilot / Total flying hours:
6000
Copilot / Total hours on type:
5000
Aircraft flight hours:
2864
Circumstances:
The pilot was receiving flight training as a new hire, and the accident occurred during his first flight in the airplane and the first landing. The pilot stated the approach was flown at the upper end of the allowable approach speed, and about 100 ft above the normal glidepath. During the landing, all three of the airplane’s landing gear touched down at the same time, the airplane immediately veered right, and continued off the right side of the runway. The airplane sustained substantial damage to the right-wing structure. The flight instructor chose an airport with a challenging approach that required a special training program prior to the first landing. The approach procedure requires a left 40° turn then rolling wings level just before touchdown. It is likely that the airplane’s descent rate during landing exceeded the airplane’s capability, which resulted in a hard landing and failure of the right-wing structure.
Probable cause:
The flight crew’s failure to arrest the descent rate during the non-standard approach, which resulted in a hard landing and failure of the right-wing structure. Contributing was the flight instructor’s selection of a challenging approach for initial training.
Final Report:

Crash of a Douglas DC-3C near Restrepo: 3 killed

Date & Time: Jul 8, 2021 at 0709 LT
Type of aircraft:
Operator:
Registration:
HK-2820
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Villavicencio - Villavicencio
MSN:
20171
YOM:
1944
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
16923
Captain / Total hours on type:
16680.00
Copilot / Total flying hours:
9387
Copilot / Total hours on type:
8170
Aircraft flight hours:
18472
Circumstances:
The twin engine airplane departed Villavicencio-La Vanguardia Airport Runway 05 at 0659LT on a training flight consisting with a proficiency check of the captain. On board were one instructor, one captain and one mechanic. About 10 minutes into the flight, while cruising at an altitude of 6,000 feet over mountainous terrain in Instrument Meteorological Conditions, the airplane impacted trees and crashed on the slope of a hilly terrain located in the region of Restrepo. The wreckage was found three days later. All three crew members were killed.
Probable cause:
Probable causes:
- Controlled flight into terrain during the execution of the IFR departure procedure VVC2A, during which the crew mistakenly turned left, contrary to the procedure, heading towards the mountainous area at the foothills of the eastern range, where the impact occurred.
- Loss of situational awareness by the crew, which, for reasons that could not be determined, apparently made a controlled left turn, contrary to the indications of the VVC2A departure procedure, even though it was an experienced crew familiar with the operating area.

The following contributing factors were identified:
- Lack of operator standards, as there was no detailed, organized, and sequential instructional plan and syllabus for the crew to follow during each maneuver, such as the VVC2A instrument departure.
- Lack of operator standards, as there was no specific syllabus for the planning and execution of the Recurrent Check, taking into account, among other aspects, the composition of the aircraft crew, consisting of two instructor pilots, one of whom was conducting the check on the other.
- Inadequate planning and supervision of the training flight by the operator, as they did not conduct a specific risk analysis of the flight, did not monitor its preparation and execution, did not provide details in a flight order or other document, considering especially the composition of the aircraft crew, consisting of two instructor pilots, one of whom was conducting the check on the other.
- Deficient planning and preparation of the flight by the crew, as they informally changed the VFR Flight Plan to IFR, apparently did not conduct a complete and adequate briefing, were unaware of or did not consider the VVC2A SID for the start of the IFR flight, and omitted several IFR flight procedures.
- Crew's neglect of the following IFR flight procedures:
- Not specifying a route and an IFR departure procedure in the IFR Flight Plan.
- Not requesting complete authorization from ATC to initiate an IFR flight. At no time did they mention the VVC2A departure, which was key to the verbally proposed plan before takeoff.
- Not defining or requesting from ATS which standard departure procedure or other they would use to initiate the IFR flight, in which they would encounter IMC shortly after takeoff.
- Not requiring ATC to assign a transponder code before takeoff or at any other phase of the flight, or selecting code 2000 as they did not receive instructions from ATS to activate the transponder.
- Likely not activating the transponder before takeoff and/or not verifying its correct operation before takeoff or immediately once the aircraft was in the air.
- Inaccurate use of phraseology with non-standard terminology in their transmissions with ATC.
- Insufficient experience and training in IFR flights by the crew, despite their extensive experience with the equipment. Much of this experience had been gained in the eastern region of the country, where the majority of DC3 flights are conducted in VMC and under VFR, with no opportunity for the practical execution of IFR procedures.
- Overconfidence of the crew, influenced by factors such as the high flight experience and DC3 equipment experience of the two pilots in the crew, their status as instructor pilots, the relatively low operational demand of the flight mission, and the knowledge, familiarity, and confidence of both crew members with the aerodrome's characteristics, the surrounding area, and especially the peculiarities and risks of the terrain to the west of the takeoff path.
- Non-observance by air traffic control of the following IFR flight procedures initiated by HK2820:
- Failure to issue complete authorization to the aircraft for the IFR flight before initiating the flight or at any other time.
- Failure to issue a standardized instrument departure, SID, or any other safe departure procedure to the aircraft. At no time did ATC mention the VVC2A departure, which was crucial for carrying out the plan verbally proposed by the crew.
- Failure to provide the aircraft with a transponder code before takeoff or at another appropriate time, or to verify its response. This process started only 03:11 minutes after the aircraft took off, so positive radar contact verification was only achieved 04:58 minutes after takeoff, delaying radar presentation and limiting positive flight control.
- Late transfer of aircraft control from the Control Tower to Approach Control (03:35 minutes after takeoff), not immediately after the aircraft was airborne as it should have been, considering prevailing IMC flight conditions in the vicinity of the aerodrome.
- Operating with an incomplete radar display configuration in Approach Control, with insufficient symbology, depriving control of references and judgment elements for an accurate location of the aircraft and its left turn from the path.
- Failure to observe radar surveillance techniques and procedures.
- Inaccurate use of phraseology with non-standard terminology in their transmissions with the aircraft.
- Lack of situational awareness by both the crew and ATC during a flight that, perhaps because it seemed routine, led both parties to omit elementary IFR flight procedures, disregarding the inherent risks of an operation in IMC conditions, with strict IFR procedures that needed to be followed, considering, among other things, the aerodrome's proximity to a mountainous area.
Final Report:

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

Date & Time: May 14, 2021 at 1140 LT
Operator:
Registration:
I-HSKC
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Ravenna - Ravenna
MSN:
779
YOM:
1977
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
The crew departed Ravenna-La Spreta Airport in the morning on a local training flight consisting of a licence renewal for one of the pilots. En route, in unclear circumstances, the single engine aircraft went out of control and crashed at the bottom of a building located about 1,400 metres south of the airfield. The aircraft was totally destroyed by impact forces and a post crash fire and both occupants were killed.

Crash of a Piper PA-60 Aerostar (Ted Smith 600) in LaBelle: 1 killed

Date & Time: May 6, 2021 at 1520 LT
Registration:
C-FAAZ
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
LaBelle - LaBelle
MSN:
60-0148-065
YOM:
1973
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
10000
Captain / Total hours on type:
65.00
Aircraft flight hours:
5252
Circumstances:
The pilot, who was the owner of the airplane, and the pilot-rated passenger, whose maintenance facility had recently completed work on the airplane, departed on the second of two local flights on the day of the accident as requested by the pilot, since he had not flown the airplane recently. Flight track and engine monitor data indicated that, about 15 minutes after takeoff, fuel flow and engine exhaust gas temperature (EGT) values were consistent with a total loss of left engine power at an altitude about 2,500 ft. Engine power was fully restored about 4 minutes later. Between the time of the power loss and subsequent restoration, the airplane directly overflew an airport and was in the vicinity of a larger airport. It is likely that the left engine was intentionally shut down to practice one engine inoperative (OEI) procedures. Had the loss of power been unanticipated, the pilot would likely have initiated a landing at one of these airports in accordance with the airplane’s published emergency procedure, which was to land as soon as possible if engine power could not be restored; however, data indicated that engine power was restored, and the flight continued back to the departure airport. About 7.5 minutes later, about 6 nautical miles from the departure airport, engine data indicated a total loss of right engine power, followed almost immediately by a total loss of left engine power, at an altitude about 3,500 ft. A battery voltage perturbation consistent with starter engagement was recorded about 1 minute later, followed by a slight increase in left engine fuel flow; however, the data did not indicate that left engine power was fully restored during the remainder of the flight. The airplane continued in the direction of the departure airport as it descended and ultimately impacted a tree and terrain and came to rest upright. A witness saw the airplane flying toward her with the landing gear extended and stated that it appeared as though neither of the two propellers was turning. A doorbell security camera near the accident site captured the airplane as it passed overhead at low altitude. Sound spectrum analysis of the footage indicated that one engine was likely operating about 1,600 rpm while the other was operating at less than 1,000 rpm. The right propeller was found feathered at the accident site. An examination and test run of the right engine revealed no anomalies that would have precluded normal operation. The left propeller blades exhibited bending, twisting, and chordwise polishing consistent with the engine producing some power at the time of impact. Examination of the left engine and engine-driven fuel pump did not reveal any anomalies. Based on the available information, it is likely that the pilots were conducting practice OEI procedures and intentionally shut down the right engine. The loss of left engine power immediately after was likely the result of the pilot’s failure to properly identify and verify the “failed” engine before securing it, which resulted in an inadvertent shutdown of the left engine. Although partial left engine power was restored before the accident (as indicated by fuel flow values, damage to the left propeller, and sound spectrum analysis of security camera video), the left engine power available was inadequate to maintain altitude for reasons that could not be determined, and it is likely that the pilot was performing a forced landing when the accident occurred. It is also likely that the pilot’s decision to conduct intentional OEI flight at low altitude resulted in reduced time and altitude available for troubleshooting and restoration of engine power following the inadvertent shutdown of the left engine. The 67-year-old pilot was a Canadian national and had never applied for a Federal Aviation Administration medical certificate. According to the Transportation Safety Board of Canada, the pilot was issued a category 1 license with knowledge of a previous condition and knowledge of currently taking Xarelto (rivaroxabam). No acute or historical cardiovascular event was found on autopsy. Toxicology testing detected the sedating antihistamine cetirizine just below therapeutic levels in the pilot’s blood. A very low concentration of the narcotic pain medication codeine was detected in the pilot’s blood and urine; codeine’s metabolite morphine was also detected in his urine. The mood stabilizing medication lamotrigine was detected but not quantified in the pilot’s blood and urine. Thus, the pilot was taking some impairing medications and likely had a psychiatric condition that could impact decision-making and performance; however, given the circumstances of the accident, including the presence of the pilot-rated passenger to operate the airplane, the effects from the pilot’s use of cetirizine, codeine, and lamotrigine were not likely factors in this accident.
Probable cause:
The pilot's inadvertent shutdown of the left engine following an intentional shutdown of the right engine while practicing one engine inoperative (OEI) procedures. Contributing to the accident was the pilot’s decision to conduct OEI training at low altitude.
Final Report:

Crash of a Swearingen SA226T Merlin IIIB in Winslow: 2 killed

Date & Time: Apr 23, 2021 at 1519 LT
Operator:
Registration:
N59EZ
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Scottsdale - Winslow
MSN:
T-394
YOM:
1981
Location:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Aircraft flight hours:
5959
Circumstances:
The pilot was conducting a personal flight and was descending the airplane to the destination airport. Automatic dependent surveillance-broadcast (ADS-B) data showed that the airplane accomplished several turning maneuvers near the airport. These turns occurred from an elevation of 6,000 to 4,950 ft mean sea level, at which time the data ended. The airplane was 80 ft above ground level at the time. Witnesses reported seeing a low-flying airplane perform a turn and then veer toward the ground. The airplane came to rest about 4 miles east of the destination airport and 70 ft from the last data target. A postcrash fire ensued. Postaccident examination of the airframe and engines found no mechanical anomalies that would have precluded normal operation. Examination of the left engine revealed that the engine was likely producing power. The right engine examination revealed damage consistent with low or no rotation at the time of the accident, including distinct, localized contact marks on the rotating propeller shaft. In addition, no metal spray was found in the turbine section, and no dirt was found within the combustor section. The examination of the right propeller blades showed chordwise scoring with the blades bent aft and twisted toward a low-pitch setting. Examination of the fuel system noted no anomalies. The airplane was equipped with a single redline (SRL) autostart computer. Examination of the right (R) SRL-OFF annunciator panel light bulb showed signatures of hot filament stretch, which was consistent with illumination of the light at the time of the accident. The SRL light normally extinguishes above an engine speed of 80% rpm. Given the low rotational signatures on the right engine and the illuminated “R SRL-OFF” warning light, it is likely that the right engine lost engine power during the flight for reasons that could not be determined.
Probable cause:
The loss of engine power to the right engine for reasons that could not be determined. Contributing to the accident was the pilot’s failure to maintain control of the airplane.
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 Piper PA-46-350P Malibu Mirage in Jacksonville

Date & Time: Sep 16, 2020 at 1340 LT
Operator:
Registration:
N972DD
Flight Type:
Survivors:
Yes
Schedule:
Jacksonville - Jacksonville
MSN:
46-36637
YOM:
2014
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total hours on type:
1141.00
Copilot / Total flying hours:
534
Copilot / Total hours on type:
9
Aircraft flight hours:
629
Circumstances:
The instructor pilot reported that while practicing an engine-out landing in the traffic pattern, the pilot-rated student overshot the turn from base leg to final rolling out to the right of the runway centerline. The student pilot attempted to turn back toward the runway and then saw that the airplane’s airspeed was rapidly decreasing. The instructor reported that when he realized the severity of the situation it was too late to do anything. The student attempted to add power for a go-around but was unable to recover. The airplane stalled about 10 ft above the ground, impacted the ground right of the runway, and skidded onto the runway where it came to rest. Both wings and the forward fuselage were substantially damaged. Both pilots stated there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Probable cause:
The student pilot’s failure to maintain control of the airplane during the landing approach and the exceedance of the airplane’s critical angle of attack at low altitude resulting in an aerodynamic stall. Contributing was the instructor pilot’s failure to adequately monitor the student pilot’s actions during the approach.
Final Report:

Crash of a Gulfstream G200 in Belo Horizonte

Date & Time: Sep 7, 2020 at 1845 LT
Type of aircraft:
Operator:
Registration:
PR-AUR
Flight Type:
Survivors:
Yes
Schedule:
Belo Horizonte - Belo Horizonte
MSN:
140
YOM:
2006
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7000
Captain / Total hours on type:
200.00
Copilot / Total flying hours:
225
Copilot / Total hours on type:
67
Circumstances:
At approximately 1835LT, the aircraft took off from SBBH (Pampulha - Carlos Drummond de Andrade - Aerodrome, Belo Horizonte, State of Minas Gerais) on a local instrument training flight with touch and goes, with 03 POB (two pilots and an extra crew member). The flight proceeded uneventfully until the first approach. During the run after touching down, the aircraft overran the departure end of the runway in a direction slightly to the right of the longitudinal axis, and collided with a nearby protective fence located past the departure end of runway 13. The airplane came to a stop at a distance of 95 m from the runway limits. The aircraft sustained substantial damage. The PIC suffered minor injuries. The SIC and the extra crew member were not injured.
Probable cause:
The following contributing factors were identified:

Attitude – a contributor.
The contribution of the pilots’ attitude to the outcome of this occurrence can be found in two distinct moments: when the go-around procedures were improvised, and when the approach was continued under marginal safety conditions, reflecting difficulties in the way the crew thought and acted.

Communication – a contributor.
One considered that the lack of clear and assertive communication between the pilots at the time of the decision to abort the takeoff, and the lack of definition as to which pilot had the aircraft controls in that moment contributed to the aircraft exceeding the departure end of the runway.

Crew Resource Management – a contributor.
The lack of adequate management of the tasks performed by the pilots during the transition to the takeoff run after the touch-down, a critical moment of the flight, combined with the lack of clear communication between them contributed to the inadequate handling of the aircraft on the ground and its consequent runway excursion.

Handling of aircraft flight controls – a contributor.
The ineffective control inputs during the final approach and during the attempt to stop the aircraft after touchdown, as well as the application of the elevator trim to the opposite side after the touchdown on the runway, indicated inadequacies in the handling of the controls that contributed to the airplane's runway excursion.

Piloting judgment – a contributor.
An inadequate assessment of the parameters related to the aircraft's operation was observed when there was an attempt to abort the takeoff after the airplane had reached 147 knots, without evaluating the remaining runway length to ensure full stop of the aircraft within the runway limits.

Flight planning – a contributor.
One concluded that the flight preparation was not adequately executed, as the planning did not allocate enough time for the pilots to prepare the aircraft for the return and carry-out of the descent procedure, resulting in an unstable approach.
Final Report:

Crash of a Grumman E-2C Hawkeye in Wallops Island

Date & Time: Aug 31, 2020 at 1550 LT
Type of aircraft:
Operator:
Registration:
166503
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Norfolk-Chambers Field - Norfolk-Chambers Field
MSN:
AA3
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft, assigned to Airborne Command & Control Squadron (VAW) 120 Fleet Replacement Squadron, departed Norfolk-Chambers Field NAS on a training flight. In the afternoon, the crew encountered an unexpected situation, abandoned the aircraft and bailed out. Out of control, the aircraft entered a dive and crashed in a field located near Wallops Island. All four occupants parachuted to safety while the aircraft was totally destroyed by impact forces and a post crash fire.