Crash of a Rockwell 500S Shrike Commander in Pembroke Park: 2 killed

Date & Time: Aug 28, 2020 at 0902 LT
Operator:
Registration:
N900DT
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Pompano Beach – Opa Locka
MSN:
500-3056
YOM:
1969
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
27780
Captain / Total hours on type:
300.00
Copilot / Total flying hours:
8029
Aircraft flight hours:
10300
Circumstances:
The pilot-in-command seated in the right seat was providing familiarization in the multiengine airplane to the left seat pilot during a flight to a nearby airport for fuel. Shortly after takeoff, one of the pilots reported an engine problem and advised that they were diverting to a nearby airport. A witness along the route of flight reported hearing the engines accelerating and decelerating and then popping sounds; several witnesses near the accident site reported hearing no engine sounds. The airplane impacted a building and terrain about 10 minutes after takeoff. Very minimal fuel leakage on the ground was noted and only 23 ounces of aviation fuel were collected from the airplane’s five fuel tanks. No evidence of preimpact failure or malfunction was noted for either engine or propeller; the damage to both propellers was consistent with low-to-no power at impact. Since the pilot could not have visually verified the fuel level in the center fuel tank because of the low quantity of fuel prior to the flight, he would have had to rely on fuel consumption calculations since fueling based on flight time and the airplane’s fuel quantity indicating system. Although the fuel quantity indications at engine start and impact could not be determined postaccident from the available evidence, if the fuel quantity reading at the start of the flight was accurate based on the amount of fuel required for engine start, taxi, run-up, takeoff, and then only to fly the accident flight duration of 10 minutes, it would have been reading between 8 and 10 gallons. It is unlikely that the pilot, who was a chief pilot of a cargo operation and tasked with familiarizing company pilots in the airplane, would have knowingly initiated the flight with an insufficient fuel load for the intended flight or with the fuel gauge accurately registering the actual fuel load that was on-board. Examination of the tank unit, or fuel quantity transmitter, revealed that the resistance between pins A and B, which were the ends of the resistor element inside the housing, fell within specification. When monitoring the potentiometer pin C, there was no resistance, indicating an open circuit between the wiper and the resistor element. X-ray imaging revealed that the conductor of electrical wire was fractured between the end of the lugs at the wiper and for pin C. Bypassing the fractured conductor, the resistive readings followed the position of the float arm consistent with normal operation. Visual examination of the wire insulation revealed no evidence of shorting, burning or damage. Examination of the fractured electrical conductor by the NTSB Materials Laboratory revealed that many of the individual wires exhibited intergranular fracture surface features with fatigue striations in various directions on some individual grains. It is likely that the many fatigue fractured conductor strands of the electrical wire inside the accident tank unit or fuel transmitter resulted in the fuel gauge indicating that the tanks contained more fuel than the amount that was actually on board, which resulted in inadequate fuel for the intended flight and a subsequent total loss of engine power due to fuel exhaustion. The inaccurate fuel indication would also be consistent with the pilot’s decision to decline additional fuel before departing on the accident flight. While the estimated fuel remaining since fueling (between 15 and 51 gallons) was substantially more than the actual amount on board at the start of the accident flight (between 8 and 10 gallons), the difference could have been caused by either not allowing the fuel to settle during fueling, and/or the operational use of the airplane. Ultimately, the fuel supply was likely completely exhausted during the flight, which resulted in the subsequent loss of power to both engines. Given the circumstances of the accident, the effects from the right seat pilot’s use of cetirizine and the identified ethanol in the left seat pilot, which was likely from sources other than ingestion, did not contribute to this accident.
Probable cause:
A total loss of engine power due to fuel exhaustion. Contributing to the fuel exhaustion was the fatigue fracture of an electrical wire in the tank unit or fuel transmitter, which likely resulted in an inaccurate fuel quantity indication.
Final Report:

Crash of a Rockwell Sabreliner 75A near Punto Fijo: 2 killed

Date & Time: Aug 10, 2020
Type of aircraft:
Operator:
Registration:
N400RS
Flight Phase:
Flight Type:
Survivors:
No
MSN:
380-25
YOM:
1978
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
The aircraft entered the Venezuelan airspace without flight plan and authorisation. While flying over the Paraguaña Peninsula at low altitude, the crew was forced to land when control was lost. The aircraft crashed in shallow water few meters offshore, lost its tail and both wings. Both pilots were killed.

Crash of a Canadair CL-215-1A10 near Lobios: 1 killed

Date & Time: Aug 8, 2020 at 1220 LT
Type of aircraft:
Operator:
Registration:
EC-HET
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Castelo Branco - Castelo Branco
MSN:
1034
YOM:
1974
Location:
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2500
Captain / Total hours on type:
1120.00
Copilot / Total flying hours:
15150
Copilot / Total hours on type:
600
Aircraft flight hours:
12003
Aircraft flight cycles:
5645
Circumstances:
Operated by Babcock Spain, the aircraft was stationed at Castelo Branco Airport in Portugal on behalf of the Civil Security of Portugal (Autoridade Nacional de Emergência e Proteção Civil).. The airplane departed Castelo Branco Airfield at 0815LT with a second CL-215 and was dispatched over the region of Lindoso, at the border with Spain, to fight a fire. While approaching the area to treat, the airplane was too low and impacted ground, causing the tail to detach. The aircraft crashed on a rocky area located near Lobios, on Spanish territory. The cockpit was destroyed upon impact and the Portuguese copilot aged 66 was killed while the Spanish captain aged 39 was seriously injured and transferred to an hospital in Alto Minho.
Probable cause:
The accident was the consequence of an erroneous assessment of the aircraft's ability to climb over the mountain.
Final Report:

Crash of a Piper PA-31-325 Navajo C/R in Sumter

Date & Time: Aug 1, 2020 at 1000 LT
Type of aircraft:
Operator:
Registration:
C-GXKS
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Manning - Manning
MSN:
31-7512038
YOM:
1975
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1625
Captain / Total hours on type:
550.00
Aircraft flight hours:
12038
Circumstances:
According to the pilot, he and the copilot were flying low-level mapping flights in the twin-engine airplane. Although the copilot was not multi-engine rated, he and the pilot regularly switched control of the airplane during the mapping flights. On the accident flight, the pilot was seated in the right seat; the copilot was seated in the left seat; and they were flying the airplane at an altitude of about 300 ft above ground level. According to the pilot, they flew for about 2 hours before he, who was the pilot flying at the time, switched fuel tanks from the inboard tanks to the outboard tanks. The pilot did not tell the copilot he had switched fuel tanks. About 1.5 hours later, while the copilot was the pilot flying, the left engine started to surge and lose power. The pilot began the steps of the emergency procedure for an engine failure in cruise flight starting with moving the fuel selectors to the inboard tanks. Power was not restored; the airplane immediately began losing altitude; and the pilot took over control of the airplane. The copilot stated that at the time the pilot took over control, he looked at the fuel tank quantity gauges, and they both displayed zero. The pilot reported that the airplane stalled just above the ground during the emergency landing in a field. The right wing struck first, and within a couple of seconds, the right outboard fuel tank exploded. The pilot and copilot egressed out the rear door. Examination of the wreckage revealed that neither engine exhibited evidence of power at impact. The left outboard fuel tank was found completely full of fuel, and the left inboard fuel tank was empty. Both right wing tanks were fire damaged, and the fuel quantity in the tanks at impact could not be determined. Further examination revealed that the fuel crossfeed valve was in the “crossfeed/open” position. No fuel was observed in the valve or attached fuel lines during disassembly. The left fuel selector valve was found in the “OFF” position, and no fuel was observed within the fuel line between the valve and gascolator. The right fuel selector valve was damaged by fire, and its position at impact could not be determined. No other anomalies were noted in the engines or airframe. According to the pilot, all fuel tanks were full before the flight. According to the pilot’s operating manual, the airplane likely consumed about 33.1 gallons of fuel per hour or a total of about 115 gallons of fuel during the 3.5-hour flight. Given that the inboard fuel cells held 56 gallons each (112 gallons total), that the left inboard tank was found empty, and that the copilot noticed that the fuel gauges were reading zero just before impact, it is likely that each engine was drawing fuel from its respective inboard tank throughout the flight until those tanks were empty. The left engine lost power first, and the right engine likely lost power just before impact. The postaccident positions of the crossfeed valve (on) and the left fuel selector (off) did not correspond to the pilot’s statements regarding his positioning of the fuel selector valves during the flight. The fuel panel was located between and behind the pilots’ seats and required the pilots to look down and back in order to see the panel when making changes to the panel; therefore, it is likely the pilot misconfigured the valves when he switched tanks 2 hours into the flight, when he switched tanks after the left engine lost power, or on both occasions. It is unlikely the copilot would have been able to see an incorrect switch selection on the fuel panel due to the location of the panel, and he would have been unlikely to look at the 2-hour point as the pilot did not verbalize that a change to the panel had been made.
Probable cause:
The pilot’s fuel mismanagement during flight, which resulted in a total loss of engine power from both engines due to fuel starvation.
Final Report:

Crash of a Cessna 401A in the Lake Maracaibo

Date & Time: Aug 1, 2020
Type of aircraft:
Registration:
N17JE
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Puerto Plata – Santa Cruz de Barahona
MSN:
401A-0082
YOM:
1969
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft departed Puerto Plata-Gregorio Luperón Airport at 1718LT on a flight to Santa Cruz de Barahona. En route, the pilot was informed that this airport is closed to all traffic after 1700LT and decided to return to Puerto Plata. A last radio communication was recorded with ATC when the aircraft disappeared from radar screens eight minutes later. Dominican authorities thought the aircraft may have crashed in the septentrional mountain range and SAR operations were initiated. Few hours later, the wreckage was found in a marshy area of the Lake Maracaibo, more than 1,000 km south of Puerto Plata. All three occupants were found alive and arrested while the aircraft was damaged beyond repair. Venezuelan authorities reported the aircraft and its occupants were engaged in an illegal narcotic flight.

Crash of a De Havilland DHC-2 Beaver in Soldotna: 6 killed

Date & Time: Jul 31, 2020 at 0827 LT
Type of aircraft:
Operator:
Registration:
N4982U
Flight Phase:
Survivors:
No
MSN:
904
YOM:
1956
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
19530
Captain / Total hours on type:
13480.00
Aircraft flight hours:
23595
Circumstances:
On July 31, 2020, about 0827 Alaska daylight time, a de Havilland DHC-2 (Beaver) airplane, N4982U, and a Piper PA-12 airplane, N2587M, sustained substantial damage when they were involved in an accident near Soldotna, Alaska. The pilot of the PA-12 and the pilot and the five passengers on the DHC-2 were fatally injured. The DHC-2 was operated as a Title 14 Code of Federal Regulations (CFR) Part 135 on-demand charter flight. The PA-12 was operated as a Title 14 CFR Part 91 personal flight. The float-equipped DHC-2, operated by High Adventure Charter, departed Longmere Lake, near Soldotna, about 0824 bound for a remote lake on the west side of Cook Inlet. The purpose of the flight was to transport the passengers to a remote fishing location. The PA-12, operated by a private individual, departed Soldotna Airport, Soldotna, Alaska, (PASX) about 0824 bound for Fairbanks, Alaska. Flight track data revealed that the DHC-2 was traveling northwest about 78 knots (kts) groundspeed and gradually climbing through about 1,175 ft mean sea level (msl) when it crossed the Sterling Highway. The PA-12 was traveling northeast about 1,175 ft msl and about 71 kts north of, and parallel to, the Sterling Highway. The airplanes collided about 2.5 miles northeast of the Soldotna airport at an altitude of about 1,175 ft msl. A witness located near the accident site observed the DHC-2 traveling in a westerly direction and the PA-12 traveling in a northerly direction. He stated that the PA-12 impacted the DHC-2 on the left side of the fuselage toward the back of the airplane. After the collision, he observed what he believed to be the DHC-2's left wing separate, and the airplane entered an uncontrolled, descending counterclockwise spiral before it disappeared from view. He did not observe the PA-12 following the collision.
Probable cause:
The failure of both pilots to see and avoid the other airplane.
Contributing to the accident were:
1) the PA-12 pilot’s decision to fly with a known severe vision deficiency that had resulted in denial of his most recent application for medical certification and
2) the Federal Aviation Administration’s absence of a requirement for airborne traffic advisory systems with aural alerting among operators who carry passengers for hire.
Final Report:

Crash of a PZL-Mielec AN-2R near Kagarkhay: 6 killed

Date & Time: Jul 19, 2020 at 2026 LT
Type of aircraft:
Operator:
Registration:
RA-71276
Flight Phase:
Survivors:
No
Site:
Schedule:
Kyren - Kyren
MSN:
1G207-47
YOM:
1984
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
4280
Captain / Total hours on type:
4236.00
Copilot / Total flying hours:
8363
Copilot / Total hours on type:
8363
Aircraft flight hours:
7382
Circumstances:
The single engine airplane departed Kyren Airport in the afternoon with four employees of the company and two pilots. The purpose of the flight was to familiarize them with the area of ​​the planned aviation chemical works for the processing of the silkworm. As the airplane failed to return to Kyren in the evening, SAR operations were initiated, but abandoned few days later as no trace of the aircraft was found. More than a year later, on July 24, 2021, a group of tourist discovered the burnt wreckage near the Baikonur Pass, in a rocky area, at an altitude of 2,780 metres. The airplane was destroyed by a post crash fire and all six occupants were killed.
Probable cause:
The accident with the An-2 RA-71276 aircraft occurred as a result of a collision with a mountain at an altitude of 2,780 metres above sea level perpendicular to the direction of the ridge with its minimum height of 2,960 metres conditions of limited visibility and the closure of mountain tops by clouds.
The following contributing factors were identified:
- The crew took the decision to perform a flight over a mountainous area with predicted closure of the mountains by clouds and unfavorable wind conditions,
- The crew took the decision to return to the landing site through the mountain range along an unexplored and previously unused route,
- Operational fatigue of the crew due to the significant duration of working hours on the day of the accident (more than 12 hours),
- The airplane falling under the influence of descending air currents on the leeward side of a mountain slope.
Final Report:

Crash of a Beechcraft 350i Super King Air on Mt Artos: 7 killed

Date & Time: Jul 15, 2020 at 2245 LT
Operator:
Registration:
EM-809
Flight Phase:
Survivors:
No
Site:
Schedule:
Van - Van
MSN:
FL-896
YOM:
2015
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
The twin engine aircraft departed Van-Ferit Melen Airport at 1834LT on a survey/reconnaissance mission over the province of Hakkari and Van, carrying five passengers and two pilots. At 2232LT, the crew informed ATC about his position vertical to Başkale on approach to Van-Ferit Melen Airport. Thirteen minutes later, the aircraft struck the slope of Mt Artos located 30 km southwest of runway 03 threshold. The aircraft was destroyed upon impact and all seven occupants were killed.

Crash of a PZL-Mielec AN-2R in Kistenovo: 2 killed

Date & Time: Jul 13, 2020 at 0337 LT
Type of aircraft:
Operator:
Registration:
RA-40851
Flight Phase:
Survivors:
No
Schedule:
Bol’shoye Boldino - Bol’shoye Boldino
MSN:
1G174-47
YOM:
1977
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
5036
Copilot / Total flying hours:
2000
Copilot / Total hours on type:
1400
Circumstances:
The crew was completing a spraying mission near the village of Kistenovo, about six km north of Bol'shoye Boldino Airfield. While flying at a low height against sunrise, the crew failed to see and avoid power cables. The single engine airplane collided with cables and a concrete post before crashing in a cornfield, bursting into flames. The copilot was killed and the captain was seriously injured. He died two days later from his injuries. The aircraft was destroyed by a post crash fire.
Probable cause:
The cause of the accident with the An-2 RA-40851 aircraft was the collision of the aircraft with a reinforced concrete support and power transmission lines in a controlled flight while performing the aerial application at an extremely low altitude.
The contributing factors most likely were:
- Field processing when the sun is less than 15° above the horizon and the sun's heading angle is less than 30°,
- Insufficient prudence of the PIC when performing a VFR flight for aerial application,
- Failure of the pilot to take into account the presence of artificial obstacles in the flight area,
- Lack of marking of power lines.
Final Report:

Crash of a De Havilland DHC-2 Beaver in Lake Coeur d'Alene: 6 killed

Date & Time: Jul 5, 2020 at 1422 LT
Type of aircraft:
Operator:
Registration:
N2106K
Flight Phase:
Survivors:
No
Schedule:
Coeur d'Alene - Coeur d'Alene
MSN:
1131
YOM:
1957
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
21173
Captain / Total hours on type:
217.00
Aircraft flight hours:
6171
Circumstances:
The float-equipped De Havilland DHC-2 was on a tour flight, and the Cessna 206 was on a personal flight. The airplanes collided in midair over a lake during day visual meteorological conditions. No radar or automatic dependent surveillance-broadcast data were available for either airplane. Witnesses reported that the airplanes were flying directly toward each other before they collided about 700 to 800 ft above the water. Other witnesses reported that the Cessna was at a lower altitude and had initiated a climb before the collision. Review of 2 seconds of video captured as part of a witness’ “live” photo showed that both airplanes appeared to be in level flight before the collision. No evidence of any preexisting mechanical malfunction was observed with either airplane. Recovered wreckage and impact signatures were consistent with the upper fuselage of the Cessna colliding with the floats and the lower fuselage of the De Havilland. The impact angle could not be determined due to the lack of available evidence, including unrecovered wreckage. The available evidence was consistent with both pilots’ failure to see and avoid the other airplane.
Probable cause:
The failure of the pilots of both airplanes to see and avoid the other airplane.
Final Report: