Crash of an Antonov AN-26B-100 in Mykhailivka: 1 killed

Date & Time: Apr 22, 2022 at 0900 LT
Type of aircraft:
Operator:
Registration:
UR-UZB
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Zaporozhie - Zaporozhie
MSN:
113 05
YOM:
1981
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The crew departed Zaporozhie Airport on a local test flight according to local authorities, carrying three crew members. While flying at low height, the airplane collided with power line and crashed in an open field located in Mykhailivka, some 11 km northwest of the airport. A crew member was killed and two others were injured. The aircraft was destroyed.

Crash of an Ilyushin II-112V in Kubinka: 3 killed

Date & Time: Aug 17, 2021 at 1118 LT
Type of aircraft:
Operator:
Registration:
RF-41400
Flight Type:
Survivors:
No
Schedule:
Kubinka - Kubinka
MSN:
01-01
YOM:
2008
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
On August 13, the aircraft (first prototype of this new model) departed the aviation plant at Voronezh Airport on a flight to Moscow-Zhukovsky, preparing for a demonstration flight at the 7th Military Technical Forum. On August 17, the crew departed Zhukovsky for a test flight to Kubinka Airport where the aircraft landed at 1109LT. Four minutes after takeoff at 1114LT, while flying at low altitude in a flat attitude, the right engine caught fire. 35 seconds later, while the crew elected to reach the airport, the aircraft rolled to the right, got inverted and crashed in a wooded area located 2,5 km short of runway 22. The aircraft was totally destroyed and all three crew members were killed. This first exemple was dedicated to the Russian Aerospace Forces (Vozdushno-kosmicheskiye sily) and was also registered 01 yellow.
Crew:
Nikolay Dmitrievich Kuimov, test pilot,
Dmitry Komarov, test pilot,
Nikolai Khludeyev, flight engineer.

Crash of a Piper PA-46-350P Malibu Mirage in Cranfield

Date & Time: Apr 29, 2021 at 1528 LT
Operator:
Registration:
G-HYZA
Flight Type:
Survivors:
Yes
Schedule:
Cranfield - Cranfield
MSN:
46-36130
YOM:
1997
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a local test flight at Cranfield Airport on this aircraft equipped with a hydrogen engine. On approach, the aircraft crashed in unknown circumstances in an open field near the airfield. Both occupants evacuated uninjured while the aircraft was severely damaged.

Crash of a Learjet 35A in Belo Horizonte: 1 killed

Date & Time: Apr 20, 2021 at 1430 LT
Type of aircraft:
Registration:
PR-MLA
Flight Type:
Survivors:
Yes
Schedule:
Belo Horizonte - Belo Horizonte
MSN:
35-072
YOM:
1976
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The crew departed Belo Horizonte-Pampulha Airport for a local test flight. After landing on runway 13, the crew encountered difficulties and the aircraft was unable to stop within the remaining distance. It overran, went through the perimeter fence (striking concrete poles) and came to rest against trees, broken in two. The copilot aged 76 was killed while both other occupants were injured.

Crash of a Cessna 340A in Tatum: 1 killed

Date & Time: Apr 19, 2021 at 1346 LT
Type of aircraft:
Registration:
N801EC
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Henderson - Henderson
MSN:
340A-0312
YOM:
1977
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
On April 19, 2021, about 1346 central daylight time, a Cessna 340A airplane, N801EC, was destroyed when it was involved in an accident near Tatum, Texas. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 flight test. According to information provided by a Fixed Base Operator (FBO) at the East Texas Regional Airport (GGG), the intention of the flight was to do a functional test of a newly upgraded autopilot system. Automatic Dependent Surveillance – Broadcast (ADS-B) data showed that the airplane took off from runway 13 at GGG about 1340. According to preliminary Air Traffic Control (ATC) information provided by the Federal Aviation Administration (FAA), the controller cleared the pilot to operate under Visual Flight Rules (VFR) to the east of the airport and to remain in class C airspace. Communications between ground control, tower control, and the pilot were normal during the ground taxi, takeoff, and climb-out. Six minutes after takeoff, radio and radar communications were lost and controllers initiated ALNOT procedures. There were no radio distress calls heard from the pilot. After takeoff, ADS-B data showed the airplane in a steady climb to the east of GGG. The airplane climbed to an altitude of 2,750 ft mean sea level (msl) and then descended to 2,675 ft msl. There were no other data points recorded. The accident site was located directly east, about ¾ mile from the last recorded data point. Groundspeeds and headings were consistent throughout the climb, with no abrupt deviations. There were no eyewitnesses to the accident; however, a local resident located about 1 mile from the accident site reported that he was inside his residence when he heard and felt a “boom” that shook the windows. He immediately saw black smoke rise, found the wreckage, and called 911. The accident site was located at an elevation of 361 ft msl. The airplane impacted the vegetated terrain in a nose-down, vertical flight attitude. The fuselage and cabin were embedded into the ground and were mostly consumed from a post-impact fire. The empennage was folded forward over the cabin area. Both left and right wings showed leading edge crushing along their respective spans. Portions of both wings were fire damaged. Both left and right engine nacelles were separated from the wings and the engine and propeller assemblies were embedded in 3-foot-deep craters.

Crash of a Cessna 750 Citation X at La Carlota AFB

Date & Time: Aug 21, 2019 at 1100 LT
Type of aircraft:
Operator:
Registration:
1060
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
La Carlota - La Carlota
MSN:
750-0134
YOM:
2000
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was engaged in a local test flight at La Carlota-General Francisco de Miranda AFB in Caracas. During the takeoff roll, a tire burst on the right main gear that collapsed and was torn off. The airplane veered off runway to the left then the left main gear collapsed as well and the airplane came to rest on its belly with the nose gear still extended. There were no injuries among the crew.

Crash of a Piper PA-61 Aerostar (Ted Smith 601) in Baton Rouge

Date & Time: Jul 20, 2018 at 1430 LT
Registration:
N327BK
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Baton Rouge - Baton Rouge
MSN:
61-0145-076
YOM:
1973
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
28829
Captain / Total hours on type:
600.00
Aircraft flight hours:
1912
Circumstances:
The mechanic who maintained the airplane reported that, on the morning of the accident, the right engine would not start due to water contamination in the fuel system. The commercial pilot and mechanic purged the fuel tanks, flushed the fuel system, and cleaned the left engine fuel injector nozzles. After the maintenance work, they completed engine ground runs for each engine with no anomalies noted. Subsequently, the pilot ordered new fuel from the local fixed-based operator to complete a maintenance test flight. The pilot stated that he completed a preflight inspection, followed by engine run-ups for each engine with no anomalies noted and then departed with one passenger onboard. Immediately after takeoff, the right engine stopped producing full power, and the airplane would not maintain altitude. No remaining runway was left to land, so the pilot conducted a forced landing to a field about 1 mile from the runway; the airplane landed hard and came to rest upright. Postaccident examination revealed no water contamination in the engines. Examination of the airplane revealed numerous instances of improper and inadequate maintenance of the engines and fuel system. The fuel system contained corrosion debris, and minimal fuel was found in the lines to the fuel servo. Although maintenance was conducted on the airplane on the morning of the accident, the right engine fuel injectors nozzles were not removed during the maintenance procedures; therefore, it is likely that the fuel flow volume was not measured. It is likely that the corrosion debris in the fuel system resulted when the water was recently purged from the fuel system. The contaminants were likely knocked loose during the subsequent engine runs and attempted takeoff, which subsequently blocked the fuel lines and starved the right engine of available fuel.
Probable cause:
The loss of right engine power due to fuel starvation, which resulted from corrosion debris in the fuel lines. Contributing to the accident was the mechanic's and pilot's inadequate maintenance of the airplane before the flight.
Final Report:

Crash of a Beechcraft C90A King Air in Mumbai: 5 killed

Date & Time: Jun 28, 2018 at 1315 LT
Type of aircraft:
Operator:
Registration:
VT-UPZ
Flight Type:
Survivors:
No
Site:
Schedule:
Juhu - Juhu
MSN:
LJ-1400
YOM:
1995
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
Following a technical maintenance, a test flight was scheduled with two engineers and two pilots. The twin engine airplane departed Mumbai-Juhu Airport and the crew completed several manoeuvres over the city before returning. On approach in heavy rain falls, the aircraft went out of control and crashed at the bottom of a building under construction located in the Ghatkopar West district, some 3 km east from Mumbai Intl Airport, bursting into flames. The aircraft was destroyed by impact forces and a post crash fire and all four occupants were killed as well as one people on the ground.

Crash of a GippsAero GA10 Airvan near Mojave

Date & Time: Jun 4, 2018 at 1152 LT
Type of aircraft:
Operator:
Registration:
VH-XMH
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Mojave - Mojave
MSN:
GA10-TP450-16-101
YOM:
2016
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9767
Captain / Total hours on type:
46.00
Copilot / Total flying hours:
10980
Copilot / Total hours on type:
287
Aircraft flight hours:
113
Circumstances:
The airplane manufacturer was conducting spin flight testing for the installation of a cargo pod when the airplane exhibited aberrant behavior and the testing was halted. The chief design engineer (CDE) was consulted, and, to provide a margin of safety for further flights, a forward center of gravity position was authorized for flaps up and flaps takeoff entries to gain more insight into the airplane's behavior on the previous flight. At the final briefing, before the next flight, the flight crew added spins with flaps in the landing configuration (flaps landing) into the test plan without the CDE's consultation or authorization. According to the pilot flying, after two wings-level, power on, flaps landing spins with left rudder and right aileron, a third spin entry was flown in the same configuration except that the entry was from a 30° left-bank turn. The airplane entered a normal spin, and, at one turn, flight controls were inputted for a normal recovery; however, the airplane settled into a fully developed spin. When recovery attempts failed, the decision was made to deploy the anti-spin parachute. After repeated unsuccessful attempts to deploy the anti-spin parachute, and when the airplane's altitude reached about 500 ft above the briefed minimum bailout altitude, both pilots called for and executed a bailout. The airplane impacted the ground and was destroyed. A postaccident examination of the anti-spin parachute system revealed that half of the connector hook had opened, which allowed the activation pin lanyard for the anti-spin parachute to become disengaged. Based on the airplane's previous aberrant behavior and the conservative parameters that the CDE had previously set, it is not likely that the CDE would have authorized abused spin entries without a prior testing buildup to those entries. Thus, the flight crew made an inappropriate decision to introduce flaps landing entry spin testing, and the failure of the anti-spin parachute contributed to the accident.
Probable cause:
The flight crew's inappropriate decision, without authorization or consultation from the manufacturer's chief design engineer, to introduce flaps in the landing configuration into the entry spin testing, which resulted in an unrecoverable spin and impact with the ground. Contributing to the accident was the failure of the anti-spin parachute.
Final Report:

Crash of an Embraer KC-390 in Gavião Peixoto

Date & Time: May 5, 2018 at 1110 LT
Type of aircraft:
Operator:
Registration:
PT-ZNF
Flight Type:
Survivors:
Yes
Schedule:
Gavião Peixoto - Gavião Peixoto
MSN:
390-00001
YOM:
2015
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a local test flight at Gavião Peixoto-Embraer Unidade Airport on this first prototype built in 2015 and flying under the Brazilian Air Force colour scheme. Following several circuits, the crew landed on runway 20. After touchdown, the airplane was unable to stop within the remaining distance and overran. While contacting soft ground, it lost its undercarriage and came to rest few dozen metres further. All three crew members escaped uninjured while the aircraft was considered as damaged beyond repair.
Probable cause:
Despite the fact that the aircraft sustained significant damage, CENIPA classified the event as an 'Incident' and on August 5, 2018, reported that closed the investigation with no final report being issued.