Crash of a Cessna 208 Caravan I on Mt Grüehorn: 1 killed

Date & Time: Mar 30, 2022 at 1223 LT
Type of aircraft:
Operator:
Registration:
D-FLIC
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Siegerland – Arezzo
MSN:
208-0274
YOM:
1998
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
6700
Captain / Total hours on type:
1800.00
Circumstances:
The pilot, sole on board, departed Siegerland Airport at 1100LT on a ferry flight to Arezzo, Tuscany. En route, while overflying Switzerland, he encountered marginal weather conditions. While cruising in IMC conditions, the single engine airplane impacted the slope of a rocky and snow covered face located west of Mt Grüehorn, in the south part of the canton of St Gallen. The wreckage was found later in the afternoon at an altitude of 1,700 metres. The aircraft was destroyed and the pilot was killed.
Probable cause:
The accident was the consequence of a controlled flight into terrain after the pilot continued under VFR mode in IMC conditions.
Final Report:

Crash of a Boeing 737-89P near Wuzhou: 132 killed

Date & Time: Mar 21, 2022 at 1422 LT
Type of aircraft:
Operator:
Registration:
B-1791
Flight Phase:
Survivors:
No
Site:
Schedule:
Kunming - Guangzhou
MSN:
41474/5433
YOM:
2015
Flight number:
MU5735
Location:
Country:
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
123
Pax fatalities:
Other fatalities:
Total fatalities:
132
Captain / Total flying hours:
6709
Copilot / Total flying hours:
31769
Aircraft flight hours:
18239
Aircraft flight cycles:
8986
Circumstances:
The airplane departed Kunming-Wujiaba Airport at 1315LT on a schedule service (flight MU5735) to Guangzhou, carrying 123 passengers and a crew of nine. At 1420LT, while cruising at an altitude of 29,100 feet, the aircraft entered an uncontrolled descent until 7,400 feet then climbed to 8,600 feet. It finally entered a steep descent and crashed almost two minutes later in a vertical attitude on hilly and wooded terrain located some 20 km southwest of Wuzhou. The airplane disintegrated on impact and all 132 occupants were killed. Two days after the accident, the CVR was found while the DFDR was found on March 27.

Crash of a Piper PA-46-500TP Malibu Meridian in Steamboat Springs: 1 killed

Date & Time: Dec 10, 2021 at 1809 LT
Operator:
Registration:
N744Z
Flight Type:
Survivors:
No
Site:
Schedule:
Cody – Steamboat Springs
MSN:
46-97134
YOM:
2002
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
581
Circumstances:
The pilot was conducting a solo night cross-country flight in low visibility through mountainous terrain. The pilot was then cleared by an air traffic controller to conduct a RNAV (GPS)-E instrument approach into the destination airport. After passing the final approach fix and before the missed approach point, the pilot, for an unknown reason, executed a left turn, consistent with the missed approach procedure. During the turn toward the holding waypoint, the airplane did not climb. Shortly thereafter, the airplane impacted steep rising terrain The local weather at the time of the accident indicated a cloud ceiling of 1,200 ft above ground level and 1 statute mile visibility, which was below the weather minimums for the approach. Data retrieved from the onboard avionics revealed that although the pilot flew the published route in accordance with the instrument approach procedure, the minimum required altitudes were not adhered to. A review of the ForeFlight weather briefing data indicated that a route weather briefing had been generated by the pilot with the filing of the instrument flight rules (IFR) flight plan. While no weather imagery was reviewed during the period, the pilot had checked METARs for the destination and another nearby airport before departure and viewed the RNAV (GPS)-E approach procedure at the destination airport. A review of the data that was presented to the pilot indicated that visual flight rules conditions prevailed at the destination with light snow in the vicinity at the time it was generated. Based on the preflight weather briefing the pilot obtained, he was likely unaware of the IFR conditions and below minimum weather conditions at the destination until he descended into the area and obtained the current local weather during the flight. It is probable that, based upon the weather and flight track information, as the pilot was on the instrument approach, he became aware of the below minimum weather conditions and elected to initiate the missed approach, as evident by the turn away from the airport similar to the missed approach procedure and the flaps and landing gear being in transition. This investigation was unable to determine why the missed approach procedure was prematurely initiated and why the airplane failed to climb. Additionally, there were no preimpact mechanical malfunctions or anomalies found during a postaccident examination that would have precluded normal operation.
Probable cause:
The pilot’s failure to adhere to the published instrument approach procedure, which resulted in controlled flight into terrain.
Final Report:

Crash of an Antonov AN-26KPA near Khabarovsk: 6 killed

Date & Time: Sep 22, 2021 at 1811 LT
Type of aircraft:
Operator:
Registration:
RA-26673
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Khabarovsk - Khabarovsk
MSN:
84 08
YOM:
1979
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
11990
Captain / Total hours on type:
3276.00
Copilot / Total flying hours:
530
Copilot / Total hours on type:
390
Aircraft flight hours:
36881
Circumstances:
The airplane was engaged in a calibration mission at Khabarovsk-Novy Airport, carrying six crew members. The goal of the flight was to caliber the ILS system of runway 05R. In the afternoon, the airplane departed Khabarovsk-Novy Airport and completed several circuits over the aerodrome and the area. The crew was instructed to climb away from the airport to an altitude of 600 metres and to turn to follow the reverse approach course. However, the minimum published altitude for that sector up to a distance of 46 km was fixed to 1,200 metres. The crew continued at an altitude of 600 metres with a heading of 220° for few minutes. While initiating a slight climb and while flying at an altitude of 742 metres in poor visibility due to marginal weather conditions, the airplane impacted trees and crashed on the wooded slope of Mt Khrebtovaya (793 metres high) located in the Bolchoï Khekhtsir Mountain Range, some 40 km southwest of Khabarovsk Airport. The aircraft was totally destroyed by impact forces and all six occupants were killed.
Probable cause:
The cause of the accident was that the airplane was flying over the radio beacons of runway 05R of Khabarovsk-Novy) Airport in instrumental meteorological conditions (IMC) at an altitude of 600 metres QFE, which was significantly lower than the established minimum safe altitude of 1,200 metres QFE in the sector where the accident occurred, which led to a collision with the mountain slope and resulted in a controlled flight into terrain (CFIT).

The following contributing factors were identified:
- Lack of current regulatory documents governing the conduct of flight inspections of ground-based flight support equipment, avionics, and civil aviation lighting equipment systems, including for airfields whose topographical features do not allow inspections to be conducted according to standard procedure;
- Unreasonable establishment of a continuous exclusion zone from 0 m to 6000 m by altitude within a radius of 99900 m from KTA for the function of signaling aircraft descent below the minimum safe altitude (MSAW), which excluded issuing a corresponding warning to a DPC dispatcher;
- Absence of the ATC Dispatcher's Work Procedure at the ATC and other documents of the ATC of EU ATS (Khabarovsk):
- procedure for ATC specialists when flying over the aerodrome's RMS;
- procedure for practical training of ATC specialist performing direct ATC under the control of ATC instructor, including their interaction and responsibility for ensuring flight safety.
- Making a decision to combine two sections of trainee navigator training without the necessary risk analysis and risk mitigation measures;
- Insufficient preliminary preparation of the crew for the overflight, including failure to take into account the terrain features (presence of zones with considerable elevation) and geographical features (proximity to the state border) of the airfield, as well as the presence in the crew of a trainee navigator not admitted to independent flights and to this particular type of work;
- Insufficient cooperation between the crew and ATC specialists when preparing and performing the overflight, including coordination by the crew and ATC specialists during the flight of the maneuver with violation of the established minimum safe altitude when performing a flight under instrumental weather conditions;
- Interference of the instructor navigator in the flight procedure (route change) without assessing the relevant risks in the absence of the pilot's control;
- Failure of the trainee navigator to comply with the operating procedures in terms of comprehensive use of aircraft equipment for precise piloting, maintenance of safe altitudes and timely informing the crew about turns, as well as lack of proper control over his actions on the part of the instructor navigator;
- Lack of control over the aircraft flight by the trainee controller and instructor controller at their minimum workload (controlling only the aircraft which had suffered a crash).
- The Operator's Flight Operations Manual lacked standard operating procedures for crew operation regarding the EGPWS Mark VIII system installed on board the aircraft. There were no warnings of this system during the flight. Probably, the system was not activated by the crew prior to the flight, maybe to avoid frequent activation during the flight. Due to the complete destruction of the system as a result of the crash, it was impossible to determine the cause of its failure. A proper use of this system may have prevent the accident.
Final Report:

Crash of a De Havilland DHC-6 Twin Otter 300 in Bilogai: 3 killed

Date & Time: Sep 15, 2021 at 0730 LT
Operator:
Registration:
PK-OTW
Flight Type:
Survivors:
No
Site:
Schedule:
Nabire – Bilogai
MSN:
493
YOM:
1976
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
13158
Captain / Total hours on type:
8051.00
Copilot / Total flying hours:
974
Copilot / Total hours on type:
807
Aircraft flight hours:
10333
Aircraft flight cycles:
1569
Circumstances:
On 15 September 2021, a DHC-6-300 (Twin Otter) aircraft registered PK-OTW was being operated for an unscheduled cargo flight from Douw Aturure Airport (WABI), Nabire, Papua to Bilorai Airport (WAYB), Intan Jaya, Papua. The aircraft was operated by two pilots accompanied by one engineer on board. The filed flight plan for the flight indicated that the aircraft would be operated under Visual Flight Rule (VFR) with fuel endurance of 2 hours 30 minutes. The estimate time departure for the flight was at 0640 LT. At 0610 LT, the pilot received weather observation report from the Bilorai aeronautical communication officer (ACO) that the visibility was 5 up to 7 kilometers, several clouds over the airport and all final areas were clear. About 7 minutes later, the ACO updated the observation report which indicated that the visibility changed to 7 up to 8 kilometers (km). After the cargo loading process and the flight preparation had completed, the aircraft taxied to Runway 16. At 0644 LT, the aircraft departed and climbed to the cruising altitude of 9,500 feet. Prior to the departure, there was no record or report of aircraft system malfunction. The Pilot in Command (PIC) acted as Pilot Monitoring (PM) while the Second in Command (SIC) acted as Pilot Flying (PF). At 0658 LT, the PK-OTW pilot reported to the Nabire air traffic control that the aircraft was at 25 Nm with altitude of 9,500 feet. At 0702 LT, the SIC asked the PIC to have the aircraft control as PF. During flight, the PK-OTW pilots monitored weather information provided by the pilots of two other aircraft that flew ahead of the PK-OTW to Bilorai. Both pilots monitored that the first aircraft (Cessna 208B EX) landed using Runway 27 while the second aircraft (Cessna 208B) would use Runway 09. At 0715 LT, the PIC advised the SIC to use the Runway 27 for landing. At 0719 LT, the SIC made initial contact with the ACO and advised that the aircraft was approaching Bilai at altitude of 9,500 feet and the estimate time arrival at Bilorai was 0726 LT. The ACO acknowledged the pilot report and provided current weather observation as follows “…wind westerly 3 until 5 knots, final 09 open with broken fog and final 27 open, visibility 5 until 7 km, blue sky overhead”. The SIC acknowledged the weather information and advised the ACO would report when the aircraft position was on left downwind Runway 27. At 0721 LT, the SIC read the descent checklist included the item of Landing Data/Approach Briefing and was replied by completed. The Cockpit Voice Recorder (CVR) did not record any pilot’s discussion regarding to the airport minimum safe altitude since the beginning of the recording. At 0723 LT, a pilot of DHC-6-400 aircraft registered PK-OTJ, asked the PK-OTW pilot of the weather condition in Bilorai. The PK-OTJ flew behind the PK-OTW with from Nabire to Bilorai. The SIC then responded that the PK-OTW was on descend and would fly through clouds about 5 Nm to Bilorai. Thereafter, the ACO provided traffic information to PK-OTW pilot that there was an aircraft (Cessna 208B aircraft) on final Runway 09. The PIC who acted as PF acknowledged the traffic information and advised to the ACO that the PK-OTW would join left downwind Runway 27 for the landing approach. At 0725 LT, the SIC advised to the ACO that the aircraft was on left downwind Runway 27. The ACO then advised the PK-OTW pilot to report when on final Runway 27. At 07:26:12 LT, a stall warning recorded in the Cockpit Voice Recorder (CVR) then the PIC asked to the SIC to check the aircraft speed. The SIC responded the aircraft speed was 65 knots. At 07:26:16 LT, the PIC asked to the SIC to advise the ACO that they were making a go around. The SIC then advised the ACO that the PK-OTW was making a go around and was responded to report when on final. The CVR did not record pilot’s discussion about the plan maneuver of the go around. At 07:26:45 LT, the PIC informed that they were making a go around to the PK-OTJ pilot. The PK-OTJ pilot responded that the aircraft was approaching Homeyo and would reduce the speed to make enough separation with the PK-OTW. The PIC then advised the PK-OTJ that the PK-OTW would attempt to land using Runway 09. Based on the data transmitted from the flight following system, at 07:27:57 LT, the aircraft was about 3 Nm outbound from Bilorai on direction of 238°. At 07:28:22 LT, the PK-OTJ pilot advised to the ACO that the aircraft was about 6 nm to Bilai and the pilot intended to make holding maneuver over Bilai to make enough separation with the PK-OTW. At 07:28:33 LT, the SIC advised the PIC that the aircraft was at 8,200 feet and was responded that the PIC initiated turning the aircraft. A few second later, the SIC advised to the PIC that the aircraft was turning, and the aircraft was at 3.2 Nm outbound from Bilorai. At 07:28:38 LT, the last data of the flight following system recorded that the aircraft was on direction of 110°. At 07:29:25 LT, the SIC advised the PIC to fly left. Thereafter, the SIC advised the PIC that the aircraft was passing 8,000 feet. At 07:29:35 LTC, the PIC asked to the SIC about the distance to Bilorai and was responded 2.5 Nm. The SIC, reminded the PIC to fly left as the aircraft flew too close to the terrain. At 07:29:49 LT, the CVR recorded the first impact sound and the CVR recording stopped at 07:29:55 LT. At 0730 LT, the ACO asked the PK-OTW pilot intention as the aircraft was not visible from the ACO working position, and the pilot did not respond the ACO. At about the same time, the ACO heard impact sound that was predicted coming from terrain area on west of Bilorai. The ACO then called the PK-OTW pilot several times without response. Several pilots also attempted to contact the PK-OTW with the same result. The PK-OTW was found on a ridge at elevation of 8,100 feet, about 2 Nm on bearing 260° from Bilorai.

Crash of a Beriev Be-200Chs near Kahramanmaraş: 8 killed

Date & Time: Aug 14, 2021
Type of aircraft:
Operator:
Registration:
RF-88450
Flight Phase:
Flight Type:
Survivors:
No
Site:
MSN:
64620090311
YOM:
2020
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
Owned and operated by the Russian Navy, the aircraft was dispatched in Turkey in July to help the Turkish government (General Directorate of Forestry) to fight raging forest fires in the southeast part of the country. On board were eight crew members, five Russian and three Turkish. After the aircraft drop water on fire, the crew elected to gain height when the aircraft impacted terrain and crashed on the slope of a mountain, bursting into flames. The aircraft was totally destroyed and all 8 occupants were killed.

Crash of a De Havilland DHC-2 Beaver near Ketchikan: 6 killed

Date & Time: Aug 5, 2021 at 1050 LT
Type of aircraft:
Operator:
Registration:
N1249K
Flight Phase:
Survivors:
No
Site:
Schedule:
Ketchikan - Ketchikan
MSN:
1594
YOM:
1965
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
15552
Captain / Total hours on type:
8000.00
Aircraft flight hours:
15028
Circumstances:
The accident flight was the pilot’s second passenger sightseeing flight of the day that overflew remote inland fjords, coastal waterways, and mountainous, tree-covered terrain in the Misty Fjords National Monument. Limited information was available about the airplane’s flight track due to radar limitations, and the flight tracking information from the airplane only provided data in 1-minute intervals. The data indicated that the airplane was on the return leg of the flight and in the final minutes of flight, the pilot was flying on the right side of a valley. The airplane impacted mountainous terrain at 1,750 ft mean sea level (msl), about 250 ft below the summit. Examination of the wreckage revealed no evidence of pre accident failures or malfunctions that would have precluded normal operation. Damage to the propeller indicated that it was rotating and under power at the time of the accident. The orientation and distribution of the wreckage indicated that the airplane impacted a tree in a left-wing-low attitude, likely as the pilot was attempting to maneuver away from terrain. Review of weather information for the day of the accident revealed a conditionally unstable environment below 6,000 ft msl, which led to rain organizing in bands of shower activity. Satellite imagery depicted that one of these bands was moving northeastward across the accident site at the accident time. Federal Aviation Administration (FAA) weather cameras and local weather observations also indicated that lower visibility and mountain obscuration conditions were progressing northward across the accident area with time. Based on photographs recovered from passenger cell phones along with FAA weather camera imagery, the accident flight encountered mountain obscuration conditions, rain shower activity, and reduced visibilities and cloud ceilings, resulting in instrument meteorological conditions (IMC) before the impact with terrain. The pilot reviewed weather conditions before the first flight of the day; however, there was no indication that he obtained updated weather conditions or additional weather information before departing on the accident flight. Based on interviews, the accident pilot landed following the first flight of the day in lowering visibility, ceiling, and precipitation, and departed on the accident flight in precipitation, based on passenger photos. Therefore, the pilot had knowledge of the weather conditions that he could have encountered along the route of flight before departure. The operator had adequate policies and procedures in place for pilots regarding inadvertent encounters with IMC; however, the pilot’s training records indicated that he was signed off for cue-based training that did not occur. Cue-based training is intended to help calibrate pilots’ weather assessment and foster an ability to accurately assess and respond appropriately to cues associated with deteriorating weather. Had the pilot completed the training, it might have helped improve his decision-making skills to either cancel the flight before departure or turn around earlier in the flight. The operator’s lack of safety management protocols resulted in the pilot not receiving the required cue-based training, allowed him to continue operating air tours with minimal remedial training following a previous accident, and allowed the accident airplane to operate without a valid FAA registration. The operator was signatory to a voluntary local air tour operator’s group letter of agreement that was developed to improve the overall safety of flight operations in the area of the Misty Fjords National Monument. Participation was voluntary and not regulated by the FAA, and the investigation noted multiple instances in which the LOA policies were ignored, including on the accident flight. For example, the accident flight did not follow the standard Misty Fjords route outlined in the LOA nor did it comply with the recommended altitudes for flights into and out of the Misty Fjords. FAA inspectors providing oversight for the area reported that, when they addressed operators about disregarding the LOA, the operators would respond that the LOA was voluntary and that they did not need to follow the guidance. The FAA’s reliance on voluntary compliance initiatives in the local air tour industry failed to produce compliance with safety initiatives or to reduce accidents in the Ketchikan region.
Probable cause:
The pilot’s decision to continue visual flight rules (VFR) flight into instrument meteorological conditions (IMC), which resulted in controlled flight into terrain. Contributing to the accident was the FAA’s reliance on voluntary compliance with the Ketchikan Operator’s Letter of Agreement.
Final Report:

Crash of a Beechcraft C90 King Air near Wikieup: 2 killed

Date & Time: Jul 10, 2021 at 1254 LT
Type of aircraft:
Operator:
Registration:
N3688P
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Marana - Wikieup
MSN:
LJ-915
YOM:
1980
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
10400
Aircraft flight hours:
17126
Circumstances:
On July 10, 2021, about 1254 mountain standard time, a Beech C-90, turbo prop airplane, N3688P, was destroyed when it was involved in an accident near Wikieup, Arizona. The pilot and Air Tactical Group supervisor were fatally injured. The airplane was operated as a public use firefighting aircraft in support of the Bureau of Land Management conducting aerial reconnaissance and supervision. The airplane was on station for about 45 minutes over the area of the Cedar Basin fire. The ADS-B data showed the airplane had accomplished multiple orbits over the area of the fire about 2,500 ft above ground level (agl). The last ADS-B data point showed the airplane’s airspeed as 151 knots, its altitude about 2,300 ft agl, and in a descent, about 805 ft east southeast of the accident site. No distress call from the airplane was overheard on the radio. According to a witness, the airplane was observed in a steep dive towards the ground. The airplane impacted the side of a ridgeline in mountainous desert terrain. The main wreckage was mostly consumed by a post-crash fire. Debris was scattered over an area of several acres. Another witness observed the left wing falling to the ground after the aircraft had impacted the terrain. The left wing had separated outboard of the nacelle and was located about 0.79 miles northeast of the main wreckage and did not sustain thermal damage.
Probable cause:
The failure and separation of the left wing’s outboard section due to a fatigue crack in the lower spar cap. Contributing to the accident was the operator’s decision to repair the wing spar instead of replacing it as recommended by the aircraft manufacturer. Also contributing to the accident was the failure of the Non-Destructive Testing inspector to detect the fatigue crack during inspection.
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 Piper PA-46-310P Malibu in Danville: 4 killed

Date & Time: Apr 23, 2021 at 1701 LT
Operator:
Registration:
N461DK
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Muskogee – Williston
MSN:
46-8508102
YOM:
1985
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
1431
Circumstances:
The pilot was conducting an instrument flight rules cross-country flight and climbing to a planned altitude of 23,000 ft mean sea level (msl). According to air traffic control data, as the airplane climbed through 18,600 ft msl, its groundspeed was 171 knots, and a gradual reduction in groundspeed began. After reaching an altitude of about 20,200 ft msl, the airplane began a descent on a southeast heading. Just before the descent began, the airplane’s groundspeed had decreased to 145 knots. About 2 minutes after the descent began, the airplane turned right to a northeast heading on which it continued for about 30 seconds. The flightpath then became erratic before the data ended. The pilot made no distress calls and did not respond to repeated calls from the controller. The main wreckage of the airplane was located in densely forested terrain at an elevation of about 930 ft about 1,000 ft south of the last radar return. The outboard portion of the right wing, right aileron, right horizontal stabilizer, and right elevator were not located with the main wreckage and, despite ground and aerial searches with a small unmanned aircraft system, were not found. Examination of the wreckage indicated that the missing wing and tail sections separated in flight due to overload. Examination of the recovered airframe and engine did not reveal evidence of any pre-existing mechanical malfunctions or anomalies that would have precluded normal operation. Weather forecasts indicated that the accident site was in an area where moderate icing conditions up to 25,000 ft msl, embedded thunderstorms, and 2-inch hail were forecasted. Review of preflight weather information received by the pilot indicated that he was aware of the conditions forecast on the route of flight before initiating the flight. Meteorological data revealed that the airplane likely entered icing conditions that ranged from light to heavy as it climbed through 14,000 ft msl about 23 minutes after takeoff and remained in icing conditions for the remaining 16-minute duration of the flight. Freezing drizzle conditions were likely present along the flightpath. Although the airplane was equipped for flight in icing conditions, the pilot’s operating handbook contained a warning about flight into severe icing conditions, which stated that flight in freezing drizzle could result in ice build-up on protected surfaces exceeding the capability of the ice protection system. The airplane’s gradual loss of groundspeed as it climbed was consistent with ice accumulating on the airplane. It is likely that during the 16 minutes the airplane was operating in icing conditions, the capability of the ice protection system was exceeded, which resulted in a degradation of aircraft performance and subsequent aerodynamic stall. During the ensuing uncontrolled descent, the structural capability of the airplane was exceeded, which resulted in an inflight break up. A review of the pilot’s records revealed multiple certificate application failures for reasons that included inadequate knowledge of cross-country flight planning, aircraft performance, and stalls. Review of the pilot’s airman knowledge written tests found areas answered incorrectly over multiple exams included meteorology, aircraft performance, aeronautical decision-making, and stalls. The ethanol identified in the pilot’s cavity blood was most likely the result of postmortem production. Therefore, effects from ethanol did not play any role in this accident. The cargo was documented as it was removed from the airplane and remained secure until after it was weighed. Based upon the weight of the cargo, passengers, airplane, and fuel from the filed flight plan, at the time of departure, the airplane would have been about 361 lbs over maximum gross weight. According to the FAA Pilot’s Handbook of Aeronautical Knowledge, an overloaded airplane “may exhibit unexpected and unusually poor flight characteristics,” which include reduced maneuverability and an increased stall speed.
Probable cause:
The pilot’s improper decision to continue flight in an area of moderate-to-heavy icing conditions, which resulted in exceedance of the airplane’s anti-icing system capabilities, a degradation of aircraft performance, and subsequent aerodynamic stall.
Final Report: