Crash of a PZL-Mielec AN-2R in Urimán

Date & Time: May 8, 2019
Type of aircraft:
Operator:
Registration:
YV2354
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
La Paragua – Urimán
MSN:
1G211-43
YOM:
1985
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
While descending to Urimán Airport following an uneventful flight from La Paragua, the crew encountered an unexpected situation and attempted an emergency landing when the aircraft impacted ground and came to rest against a group of palm trees located 13 km from Urimán. Both pilots were injured and the aircraft was damaged beyond repair.

Crash of a Canadair CL-601-3A Challenger near La Rosita: 13 killed

Date & Time: May 5, 2019 at 1740 LT
Type of aircraft:
Registration:
N601VH
Flight Phase:
Survivors:
No
Site:
Schedule:
Las Vegas - Monterrey
MSN:
5043
YOM:
1989
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
11
Pax fatalities:
Other fatalities:
Total fatalities:
13
Captain / Total flying hours:
3337
Captain / Total hours on type:
329.00
Copilot / Total flying hours:
1541
Copilot / Total hours on type:
147
Aircraft flight hours:
7637
Aircraft flight cycles:
4122
Circumstances:
The airplane departed Las Vegas-McCarran Airport at 1452LT on a charter flight to Monterrey, carrying two pilots and 11 passengers who were returning to Mexico after taking part to a boxing match in Las Vegas. The flight was completed at FL370 until the crew was cleared to climb to FL390 for five minutes then to FL410. Suddenly, the airplane entered an uncontrolled descent and eventually crashed in an almost flat attitude in a desert area located near La Rosita, Coahuila. The aircraft was destroyed by impact forces and a post crash fire and all 13 occupants were killed. The wreckage was found the following day.
Probable cause:
A loss of control at high altitude after the airplane encountered severe atmospheric turbulences coming from an unstable weather area. The crew were unable to detect the presence of this atmospheric phenomenon due to the malfunction of the onboard weather radar system for reasons that could not be determined.
Final Report:

Crash of a Piper PA-46-350P Malibu near Makkovik: 1 killed

Date & Time: May 1, 2019 at 0816 LT
Operator:
Registration:
N757NY
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Goose Bay - Narsarsuaq
MSN:
46-36657
YOM:
2015
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
3500
Captain / Total hours on type:
20.00
Copilot / Total flying hours:
1300
Copilot / Total hours on type:
0
Circumstances:
On 01 May 2019 at 0723, the aircraft departed CYYR on a VFR flight plan direct to BGBW. The ferry pilot, who was the pilot-in-command, occupied the left seat while the co-owner occupied the right seat. The aircraft climbed to 2000 feet ASL and proceeded on a direct track to destination. The altitude and heading did not change significantly along the route, therefore it is likely that the autopilot was engaged. At 0816, the aircraft collided with a snow-covered hill 2250 feet in elevation, located 35 nautical miles (NM) southeast of Makkovik Airport (CYFT), Newfoundland and Labrador. The impact happened approximately 200 feet below the top of the hill. The aircraft came to rest in deep snow on steep sloping terrain. The aircraft sustained significant damage to the propeller, nose gear, both wings, and fuselage. Although the cabin was crush-damaged, occupiable space remained. There was no post-impact fire. The ferry pilot was seriously injured and the co-owner was fatally injured. The Joint Rescue Coordination Centre (JRCC) in Halifax received an emergency locator transmitter (ELT) signal from the aircraft at 0823. The ferry pilot carried a personal satellite tracking device, a personal locator beacon (PLB) and a handheld very high frequency (VHF) radio, which allowed communication with search and rescue (SAR). Air SAR were dispatched to the area; however, by that time, the weather had deteriorated to blizzard conditions and aerial rescue was not possible. Ground SAR then deployed from the coastal community of Makkovik and arrived at the accident site approximately 4 hours later because of poor weather conditions and near zero visibility. The ferry pilot and the body of the co-owner were transported to Makkovik by snowmobile. The following day, they were airlifted to CYYR.
Probable cause:
Controlled flight into terrain.
Final Report:

Crash of a Rockwell Sabreliner 65 near New Albany: 3 killed

Date & Time: Apr 13, 2019 at 1514 LT
Type of aircraft:
Registration:
N265DS
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Broomfield - Oxford - Hamilton
MSN:
465-45
YOM:
1980
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
22200
Copilot / Total flying hours:
2250
Aircraft flight hours:
10754
Circumstances:
Two instrument-rated commercial pilots and one passenger were conducting a cross-country flight in instrument meteorological conditions when they began discussing an electrical malfunction; they then reported the electrical problem to air traffic control. The airplane subsequently made a descending right turn and impacted wooded terrain at a high speed. Most components of the airplane were highly fragmented, impact damaged, and unidentifiable. Based on the limited discussion of the electrical problem on the cockpit voice recorder and the damage to the airplane, it was not possible to determine the specific nature of the electrical malfunction the airplane may have experienced. While it was not possible to determine which systems were impacted by the electrical malfunction, it is possible the flight instruments were affected. The airplane's descending, turning, flight path before impact is consistent with a system malfunction that either directly or indirectly (through a diversion of attention) led to the pilot's loss of awareness of the airplane's performance in instrument meteorological conditions and subsequent loss of control of the airplane.
Probable cause:
An unidentified electrical system malfunction that led to the pilots losing awareness of the airplane's performance in instrument meteorological conditions and resulted in a loss of control of the airplane.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Sayaxché: 2 killed

Date & Time: Apr 13, 2019
Operator:
Registration:
N2613
Flight Phase:
Flight Type:
Survivors:
No
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
In the morning, the Guatemala Army Forces were informed by ATC that a PA-31 entered the Guatemala Airspace without prior permission. The twin engine airplane crashed in a wooded area located near the farm of Sepens located in the region of Sayaxché, Petén. The aircraft was partially destroyed by impact forces and both occupants were killed. A sticker was set on the fuselage with the registration N2613 which is wrong.

Crash of a Piper PA-31-350 Navajo Chieftain near San Rafael de Yuma

Date & Time: Apr 5, 2019 at 2228 LT
Operator:
Registration:
YV312
Flight Phase:
Flight Type:
Survivors:
Yes
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine airplane departed Venezuela in the evening on a probable drug smuggling flight with an unknown destination. At 2226LT, after it entered the Dominican Airspace, a crew of the Dominican Air Force was dispatched with an Embraer EMB-314 Super Tucano but the PA-31 disappeared from radar screens at 2228LT after crashing in a sugar cane field located in the region of San Rafael de Yuma, between La Romana and Punta Cana. Due to limited visibility caused by night and poor weather conditions, SAR operations were suspended shortly after midnight. The wreckage was found in the next early morning. Nobody was found on site and the aircraft is probably written off. The registration YV312 may be a wrong one.

Crash of a Beechcraft B200 Super King Air in Matsieng: 1 killed

Date & Time: Mar 23, 2019 at 2020 LT
Operator:
Registration:
A2-MBM
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Gaborone - Matsieng
MSN:
BB-1489
YOM:
1994
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
Earlier in the afternoon the pilot was an uninvited guest at a private function that was held at the Matsieng Flying Club facility at Matsieng Aerodrome. In a statement, the Matsieng Flying Club reported that it was rumored that the pilot was involved in a domestic dispute earlier in the afternoon. At 2015LT the aircraft approached Matsieng Aerodrome from the direction of Sir Seretse Khama Airport and made a number of low level fly passes from different directions past the Club facilities next to the Air Traffic Control tower. An immediate evacuation of the club premises was ordered. The final extreme low level run by the aircraft along runway 36 resulted in an impact with the Matsieng Flying Club facility at ground level. The Club facility and Matsieng ATC tower was destroyed on impact. The post impact fire destroyed 13 parked vehicles. The emergency services of the Kgatleng District Council were on the scene within minutes to attend to the post-impact fire and distress. These response actions are to be commended. It is believed that the pilot had no permission to fly the aircraft involved. Sole on board, he was killed.
Probable cause:
Pilot suicide suspected.

Crash of a Piper PA-31-350 Navajo Chieftain in Madeira: 1 killed

Date & Time: Mar 12, 2019 at 1516 LT
Operator:
Registration:
N400JM
Flight Phase:
Survivors:
No
Site:
Schedule:
Cincinnati - Cincinnati
MSN:
31-8152002
YOM:
1981
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
6421
Captain / Total hours on type:
1364.00
Aircraft flight hours:
19094
Circumstances:
The commercial pilot was conducting an aerial observation (surveying) flight in a piston engineequipped multiengine airplane. Several hours into the flight, the pilot advised air traffic control (ATC) that the airplane had a fuel problem and that he needed to return to the departure airport. When the airplane was 8 miles from the airport, and after passing several other airports, the pilot informed ATC that he was unsure if the airplane could reach the airport. The final minutes of radar data depicted the airplane in a descent and tracking toward a golf fairway as the airplane's groundspeed decreased to a speed near the single engine minimum control airspeed. According to witnesses, they heard an engine sputter before making two loud "back-fire" sounds. One witness reported that, after the engine sputtered, the airplane "was on its left side flying crooked." Additional witnesses reported that the airplane turned to the left before it "nose-dived" into a neighborhood, impacting a tree and private residence before coming to rest in the backyard of the residence. A witness approached the wreckage immediately after the accident and observed a small flame rising from the area of the left engine. Video recorded on the witness' mobile phone several minutes later showed the airplane engulfed in flames. Examination of the wreckage revealed no evidence of any preimpact mechanical malfunctions or failures of either engine. The fuel systems feeding both engines were damaged by impact forces but the examined components generally displayed that only trace amounts of fuel remained; with the exception of the left engine nacelle fuel tank. Given the extent of the fire damage to this area of the wreckage, and the witness report that the post impact fire originated in this area, it is likely that this tank contained fuel. By design, this fuel in this tank was not able to supply fuel directly to either engine, but instead relied on an electric pump to transfer fuel into the left main fuel tank. Fire damage precluded a detailed postaccident examination or functional testing of the left nacelle fuel transfer pump. Other pilots who flew similar airplanes for the operator, along with a review of maintenance records for those airplanes, revealed at least three instances of these pumps failing in the months surrounding the accident. The other pilots also reported varying methods of utilizing fuel and monitoring fuel transfers of fuel from the nacelle fuel tanks, since there was no direct indication of the quantity of fuel available in the tank. These methods were not standardized between pilots within the company and relied on their monitoring the quantity of fuel in the main fuel tanks in order to ensure that the fuel transfer was occurring. Had the pilot not activated this pump, or had this pump failed during the flight, it would have rendered the fuel in the tank inaccessible. Given this information it is likely that the fuel supply available to the airplane's left engine was exhausted, and that the engine subsequently lost power due to fuel starvation. The accident pilot, along with another company pilot, identified fuel leaking from the airplane's left wing, about a week before the accident. Maintenance records showed no actions had been completed to the address the fuel leak. Due to damage sustained during the accident, the origin of the fuel leak could not be determined, nor could it be determined whether the fuel leak contributed to the fuel starvation and eventual inflight loss of power to the left engine. Because the left engine stopped producing power, the pilot would have needed to configure the airplane for single-engine flight; however, examination of the left engine's propeller found that it was not feathered. With the propeller in this state, the pilot's ability to maintain control the airplane would have been reduced, and it is likely that the pilot allowed the airplane's airspeed to decrease below the singleengine minimum controllable airspeed, which resulted in a loss of control and led to the airplane's roll to the left and rapid descent toward the terrain. Toxicology results revealed that the pilot had taken doxylamine, an over-the-counter antihistamine that can decrease alertness and impair performance of potentially hazardous tasks. Although the toxicology results indicated that the amount of doxylamine in the pilot's cavity blood was within the lower therapeutic range, review of ATC records revealed that the pilot was alert and that he was making necessary decisions and following instructions. Thus, the pilot's use of doxylamine was not likely a factor in the accident.
Probable cause:
Fuel starvation to the left engine and the resulting loss of engine power to that engine, and a loss of airplane control due to the pilot's failure to maintain the minimum controllable airspeed.
Final Report:

Crash of a BAe 125-600A in San Pedro de Peralta: 1 killed

Date & Time: Mar 10, 2019
Type of aircraft:
Operator:
Registration:
N18BA
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
256046
YOM:
1974
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The aircraft was engaged in an illegal flight, carrying two pilots and a load of 200 kg of cocaine. En route, the crew apparently encountered an unexpected situation and was forced to attempt an emergency landing when the airplane crashed in a wooded area located near San Pedro de Peralta. A pilot was killed while the second was seriously injured. Originally registered N299GS, the aircraft was cancelled from the US registered on 15 February 2018 and exported to Mexico. The registration N18BA is false.

Crash of a Douglas DC-3 in Finca La Bendición: 14 killed

Date & Time: Mar 9, 2019 at 1036 LT
Type of aircraft:
Operator:
Registration:
HK-2494
Flight Phase:
Survivors:
No
Schedule:
San Jose del Guaviare – Villavicencio
MSN:
33105/16357
YOM:
1945
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
11
Pax fatalities:
Other fatalities:
Total fatalities:
14
Captain / Total flying hours:
12710
Captain / Total hours on type:
7044.00
Copilot / Total flying hours:
12710
Copilot / Total hours on type:
7044
Aircraft flight hours:
23000
Circumstances:
The twin engine airplane departed San José del Guaviare on a charter flight to Villavicencio, carrying 11 passengers and three crew members. While cruising at an altitude of 8,500 feet in good weather conditions, the left engine failed due to an important fuel leak. The crew elected to secure the engine but was unable to feather the propeller. The airplane lost speed and height, and while attempting an emergency landing, the crew lost control of the airplane that stalled and crashed in a palm plantation, bursting into flames. The aircraft was totally destroyed by a post crash fire and all 14 occupants were killed.
Probable cause:
The investigation determined that the accident was caused by the following probable causes:
- Loss of control in-flight as a consequence of the decrease in minimum in-flight control speed and drag generated by the impossibility of performing the No. 1 engine propeller feathering in the face of engine failure.
- Malfunction of the lubrication system of engine No. 1, evident in the abundant oil leakage from the engine, in flight, and in the governor of the left propeller; although discrepancies were found in the maintenance of the propeller feathering pressure line, it was not possible to determine the origin of the oil leakage.
- Weaknesses in the aircraft Operator's operational procedures, lacking a standard that would facilitate a crew's decision making to act in the event of critical failures, in matters such as making an emergency landing on unprepared field or the selection of an alternate airfield.

Contributing Factors:
- Deficiencies in standard maintenance practices during repairs performed on the No. 1 engine's propeller propeller feathering oil pressure line.
- Non-compliance with an effective and reliable maintenance program, which did not verify the operating conditions of the aircraft components; it was not possible to determine compliance with the last 50-hour service, Phase A, to engine No. 1 according to the company's maintenance program, since there are no records of that service in the Flight Log.
- Inefficient safety management system of the Operator for not detecting errors in the maintenance processes and in the conduct and control of operations.
Final Report: