Crash of a Cessna 207 Skywagon in Carrefour: 6 killed

Date & Time: Apr 20, 2022 at 1600 LT
Registration:
HH-FAH
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Port-au-Prince – Jacmel
MSN:
207-0352
YOM:
1976
Location:
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
6
Circumstances:
The single engine airplane departed Port-au-Prince-Toussaint Louverture Airport on a private flight to Jacmel, some 45 km southwest of the capital city. On board were four passengers and one pilot. During climbout, the pilot encountered problems and the airplane lost height until it collided with a truck and crashed on a road located in Carrefour, some 12 km southwest of Port-au-Prince Airport. A passenger was seriously injured while four other occupants as well as the truck driver were killed. The aircraft was destroyed. The only survivor died from his injuries few hours later.

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

Date & Time: Feb 13, 2022 at 1020 LT
Registration:
N2445F
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Olathe - Albuquerque
MSN:
46-97480
YOM:
2012
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
354
Aircraft flight hours:
2170
Circumstances:
The airplane had recently undergone an annual inspection, and the pilot planned to fly the airplane back to his home base. After receiving clearance from air traffic control, the pilot proceeded to take off. The airplane accelerated and reached a peak groundspeed of 81 kts about 2,075 ft down the 4,097-ft runway. Once airborne, the airplane drifted slightly to the right and the pilot radioed an urgent need to return to the airport. The controller cleared the airplane to land and no further transmissions were received from the accident airplane. The airplane’s flight path showed that it slowed before turning back toward the left and the airplane’s speed continued to decrease throughout the remainder of the data. The final data point recorded the airplane at a groundspeed of 45 kts. The groundspeed would equate to 60 kts airspeed when considering the 15-kt headwind. The stall speed chart for the airplane listed the minimum stall speed for any configuration as 64 kts. Postaccident examinations of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. External and internal engine damage indicated that the engine was producing power at the time of impact, but the amount of power output could not be determined. Based on the available information, the pilot perceived an urgent need to return the airplane to the airport; however, due to the amount of damage from the impact and postimpact fire, the reason that the pilot was returning to the airport could not be determined. Stall speed information for the airplane, the recorded winds, and flight track data, indicated that the airplane encountered an aerodynamic stall before impacting the ground near the departure end of the runway. Since the airplane stalled and impacted the ground before reaching the perimeter of the airport, the pilot may not have had sufficient altitude to execute a forced landing to the empty field off the departure end of the runway.
Probable cause:
The unknown emergency that warranted a return to the airport and the airspeed decay which resulted in an aerodynamic stall.
Final Report:

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

Date & Time: Feb 11, 2022 at 1230 LT
Type of aircraft:
Registration:
RA-33599
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Koryaki - Tymlat
MSN:
1G230-41
YOM:
1988
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
17136
Captain / Total hours on type:
2388.00
Copilot / Total flying hours:
376
Copilot / Total hours on type:
7
Aircraft flight hours:
3712
Circumstances:
The single engine airplane departed Koryaki on a cargo flight to Tymlat, carrying two pilots and a load of potatoes and roof tiles. Shortly after takeoff, while in initial climb, the airplane reached a critical angle of attack then entered a stall and crashed in a wooded area, bursting into flames. The wreckage was found about one km from the village. The airplane was totally destroyed by a post crash fire and both occupants were killed.
Probable cause:
The accident probably occurred as a result of its entry into subcritical angles of attack and stall mode after a takeoff with the maximum permissible weight and reduced power of the propulsion system. Most likely, the reduced power was due to the installation of a magneto switch prior to the PM-1 magneto switch to position “1” instead of position “1+2” as required in the flight manual.
The following contributing factors were identified:
- Long flight interruptions of both crew members before the emergency flight,
- Deficiencies in the training and interaction of crew members,
- Insufficient level of flight training, which resulted in a loss of control of the flight speed.
Final Report:

Crash of a Cessna T207A Stationair 8 in Nazca: 7 killed

Date & Time: Feb 4, 2022 at 1214 LT
Operator:
Registration:
OB-2179
Flight Phase:
Survivors:
No
Schedule:
Nazca - Nazca
MSN:
207-0428
YOM:
1978
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
7
Captain / Total flying hours:
1429
Captain / Total hours on type:
400.00
Copilot / Total flying hours:
291
Copilot / Total hours on type:
45
Aircraft flight hours:
26888
Circumstances:
The single engine airplane departed Nazca-María Reiche Neuman Airport on a local sightseeing flight, carrying five passengers and two crew members. During the rotation phase, the aircraft presented mechanical failures evidenced by unusual noises and a progressive decrease in engine power. The crew continued the takeoff without reaching the necessary speed and altitude for a safe climb. The pilot reported he was returning to the airport when the aircraft entered into a loss of aerodynamic lift, violently impacting the ground. The strong impact caused multiple serious injuries to the occupants and triggered a fire that destroyed a large part of the aircraft. All seven occupants were killed.
Probable cause:
Progressive loss of engine power due to the malfunction of the combustion system from the beginning of the takeoff, which significantly compromised the aircraft's performance in flight, as it was unable to maintain the proper speed and altitude to return to the airport, entering into a sudden loss of lift and the subsequent collision with ground.
Final Report:

Crash of a Cessna 207 Skywagon off Marathon

Date & Time: Dec 29, 2021 at 1622 LT
Operator:
Registration:
N1596U
Flight Phase:
Survivors:
Yes
Schedule:
Marathon - Naples
MSN:
207-0196
YOM:
1971
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1463
Captain / Total hours on type:
176.00
Aircraft flight hours:
13496
Circumstances:
Shortly after departure, the engine lost total power and the pilot was forced to ditch in open water; the occupants egressed and were subsequently rescued by a recreational vessel. Examination of the engine revealed a fracture hole near the n°2 cylinder, which was likely the result of the n°2 cylinder connecting rod fracturing in fatigue as a result of high heat and high stress associated with failure of the n°2 bearing. The fatigue fracture displayed multiple origins consistent with relatively high cyclic stress, which likely occurred as excessive clearances developed between the bearing and the crankshaft journal. The n°2 connecting rod bearing may have failed due to a material defect in the bearing itself or due to a disruption in the oil lubrication supply to the bearing/journal interface. Either situation can cause similar damage patterns to develop, including excessive heating and subsequent bearing failure.
Probable cause:
A total loss of engine power due to the failure of the No. 2 bearing, which resulted in the n°2 connecting rod failing due to fatigue, high heat, and stress.
Final Report:

Crash of a Piper PA-31-350 Navajo Chiefain in Medford: 1 killed

Date & Time: Dec 5, 2021 at 1652 LT
Registration:
N64BR
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Medford - Fallon
MSN:
31-7752124
YOM:
1977
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2167
Captain / Total hours on type:
1520.00
Aircraft flight hours:
8809
Circumstances:
The airplane was departing into instrument meteorological conditions using a standard instrument departure. The takeoff instructions consisted of making a climbing right turn direct to a nondirectional beacon. After departing, the pilot made a radio communication to an air traffic controller asking if he will tell him when to turn. The controller replied that he would not be calling his turn and that the pilot should fly the departure as published making a climbing right turn to overfly the approach end of the runway. The pilot acknowledged the communication, which was his last transmission. The airplane made a 360° turn and descended below the cloud layer. The airplane then climbed back into the cloud layer and made an inverted loop, descending into the ground in a near-vertical attitude. A postaccident examination of the airplane revealed no evidence of preimpact mechanical malfunctions or failures. Recorded audio of the airplane before the accident was consistent with the engines operating. The signatures on both propellers were consistent with one another and consistent with the engines operating at a similar rpm. The pilot was qualified and recently underwent recurrent training. The reasons the pilot became spatially disoriented could not definitely determined. The pilot left the anti-collision lights on while in the clouds, which may have resulted in him having flicker vertigo.
Probable cause:
The pilot’s failure to maintain aircraft control during the initial climb into clouds due to spatial disorientation, which resulted in an uncontrolled descent and collision with terrain.
Final Report:

Crash of an Antonov AN-26 in Juba: 5 killed

Date & Time: Nov 2, 2021 at 1237 LT
Type of aircraft:
Operator:
Registration:
TR-NGT
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Juba - Maban
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
The airplane departed Juba Airport Runway 13 at 1233LT on a cargo flight to Maban, carrying five crew members and a load consisting of 28 drums of diesel. Three minutes after takeoff, while climbing, the crew declared an emergency. One minute later, the entered an uncontrolled descent and crashed less than 2 km past the runway end, bursting into flames. The aircraft was destroyed and all five occupants were killed. Registration and MSN to be confirmed. It is believed that the aircraft was operated on behalf of Euro Airlines.

Crash of a McDonnell Douglas MD-87 in Houston

Date & Time: Oct 19, 2021 at 1000 LT
Type of aircraft:
Registration:
N987AK
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Houston - Bedford
MSN:
49404/1430
YOM:
1987
Crew on board:
4
Crew fatalities:
Pax on board:
19
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
22000
Captain / Total hours on type:
4000.00
Copilot / Total flying hours:
10000
Copilot / Total hours on type:
700
Aircraft flight hours:
49566
Circumstances:
The captain (who was the pilot flying) initiated the takeoff roll, and the airplane accelerated normally. According to the cockpit voice recorder (CVR) transcript, the first officer made the “V1” and then “rotate” callouts. According to the captain (in a postaccident interview), when he pulled back on the control column to rotate the airplane, “nothing happened,” and the control column felt like it “was in concrete” and “frozen.” The CVR captured that the first officer subsequently made the “V2” callout, then the captain said “come on” in a strained voice. Both pilots recalled in postaccident interviews that they both attempted to pull back on the controls, but the airplane did not rotate. The CVR captured that the first officer called out “abort.” The first officer pulled the thrust levers to idle and applied the brakes, and the captain deployed the thrust reversers. (See “Execution of Rejected Takeoff” for more information.) The airplane overran the departure end of the runway and continued through the airport perimeter fence and across a road, striking electrical distribution lines and trees before coming to rest in a pasture, where a postcrash fire ensued. The pilots, two additional crewmembers, and all passengers evacuated the airplane. Two passengers received serious injuries, and one received a minor injury. The airplane was totally destroyed by a post crash fire.
Probable cause:
The jammed condition of both elevators, which resulted from exposure to localized, dynamic high wind while the airplane was parked and prevented the airplane from rotating during the takeoff roll. Also causal was the failure of Everts Air Cargo, the pilots’ primary employer, to maintain awareness of Boeing-issued, required updates for its manuals, which resulted in the pilots not receiving the procedures and training that addressed the requirement to visually verify during the preflight checks that the elevators are not jammed.
Final Report:

Crash of a Cessna 401 in Tapachula: 1 killed

Date & Time: Oct 19, 2021 at 0716 LT
Type of aircraft:
Operator:
Registration:
XB-RQE
Flight Phase:
Survivors:
No
Schedule:
Tapachula – Tapachula
MSN:
401-0268
YOM:
1969
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1647
Captain / Total hours on type:
1397.00
Aircraft flight hours:
5237
Circumstances:
The pilot, sole on board, departed Tapachula Airport on a local flight to release Mediterranean flies. A flight plan of four hours was filed, with an altitude of 9,500 feet. The flies should be released in an area corresponding to 60 - 100 NM around the Tapachula VOR. Shortly after takeoff from Tapachula Airport Runway 05, while climbing to an altitude of 1,000 feet, the pilot reported engine problems. The aircraft turned to the right then entered an uncontrolled descent until it crashed in a mango plantation. The airplane was destroyed and the pilot was killed.
Probable cause:
Impact of the aircraft against the ground during a tight turn towards the side of the right engine, which showed inadequate performance.
The following contributing factors were identified:
- Continuing the flight despite intermittent failures in the fuel flow of engine number 2,
- Failure to adhere to the abnormal engine failure procedure during takeoff,
- Fatigue fracture of the fuel pump shaft of engine number 2.
Final Report:

Crash of a PZL-Mielec AN-2T in Alta Mesa

Date & Time: Oct 14, 2021 at 1600 LT
Type of aircraft:
Operator:
Registration:
N857PF
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Alta Mesa – Reno
MSN:
1G108-57
YOM:
1969
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9811
Captain / Total hours on type:
70.00
Aircraft flight hours:
3500
Circumstances:
The pilot stated that the departure started normally but that, after becoming airborne, the airplane controls were not responding to his inputs as expected. The airplane continued to pitch up in a nose-high attitude and he was unable to push the control yoke forward, which he described as feeling like he was “stretching” cables with forward pressure. With the airplane’s pitch uncontrollable, he elected to make a rapid maneuver toward an unpopulated area. The airplane descended into trees; after coming to a stop, a fire erupted. A postaccident examination of the flight control system revealed no definitive evidence of preimpact mechanical malfunctions or failures. Because the elevator system was extensively damaged and was partially consumed by fire, the investigation was not able to determine the cause of the pitch control anomaly. The airplane’s weight and center of gravity (CG) could not be confirmed. The burned remains of items found in the airplane could not be identified and the location of those items at impact could not be confirmed.
Probable cause:
The pilot’s inability to control the airplane’s pitch during departure for reasons that could not be determined because of the extensive fragmentation and thermal damage the airplane sustained in the accident sequence.
Final Report: