Crash of a Convair C-131B Samaritan off Miami: 1 killed

Date & Time: Feb 8, 2019 at 1216 LT
Type of aircraft:
Operator:
Registration:
N145GT
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Nassau - Miami
MSN:
256
YOM:
1955
Flight number:
QAI504
Location:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
23000
Captain / Total hours on type:
725.00
Copilot / Total flying hours:
650
Copilot / Total hours on type:
305
Aircraft flight hours:
12701
Circumstances:
According to the first officer, during the first cargo flight of the day, the left engine propeller control was not working properly and the captain indicated that they would shut down the airplane and contact maintenance if the left engine propeller control could not be reset before the return flight. For the return flight, the engines started normally, and both propellers were cycled. The captain and the first officer were able to reset the left propeller control, so the airplane departed with the first officer as the pilot flying. The takeoff and initial climb were normal; however, as the airplane climbed through 4,000 ft, the left engine propeller control stopped working and the power was stuck at 2,400 rpm. The captain tried to adjust the propeller control and inadvertently increased power to 2,700 rpm. The captain then took control of the airplane and tried to stabilize the power on both engines. He leveled the airplane at 4,500 ft, canceled the instrument flight rules flight plan, and flew via visual flight rules direct toward the destination airport. The first officer suggested that they return to the departure airport, but the captain elected to continue as planned (The destination airport was located about 160 nautical miles from the departure airport). The first officer's postaccident statements indicated that he did not challenge the captain's decision. When the flight began the descent to 1,500 ft, the right engine began to surge and lose power. The captain and the first officer performed the engine failure checklist, and the captain feathered the propeller and shut down the engine. Shortly afterward, the left engine began to surge and lose power. The captain told the first officer to declare an emergency. The airplane continued to descend, and the airplane impacted the water "violently," about 32 miles east of the destination airport. The captain was unresponsive after the impact and the first officer was unable to lift the captain from his seat. Because the cockpit was filling rapidly with water, the first officer grabbed the life raft and exited the airplane from where the tail section had separated from the empennage. The first officer did not know what caused both engines to lose power. The airplane was not recovered from the ocean, so examination and testing to determine the cause of the engine failures could not be performed. According to the operator, the flight crew should have landed as soon as practical after the first sign of a mechanical issue. Thus, the crew should have diverted to the closest airport when the left engine propeller control stopped working and not continued the flight toward the destination airport.
Probable cause:
The captain's decision to continue with the flight with a malfunctioning left engine propeller control and the subsequent loss of engine power on both engines for undetermined reasons, which resulted in ditching into the ocean. Contributing to the accident was the first officer's failure to challenge the captain's decision to continue with the flight.
Final Report:

Crash of a Cessna 207 Stationair 7 in Cayenne

Date & Time: Jan 25, 2019 at 1435 LT
Operator:
Registration:
F-OSIA
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Cayenne – Maripasoula
MSN:
207-0042
YOM:
1969
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3620
Circumstances:
The single engine airplane departed Cayenne-Rochambeau-Félix Eboué Airport on a cargo flight to Maripasoula, carrying a load of foods on behalf of a restaurant. The pilot was sole on board. Shortly after takeoff, while in initial climb, the engine lost power. The pilot reduced his altitude and attempted an emergency landing on a known open area located near the airport. But on short final, the aircraft struck a embankment and came to rest upside down. The pilot was seriously injured and the aircraft was destroyed.
Probable cause:
The flight was undertaken with an airplane whose center of gravity was beyond the rear center of gravity limits and a mass greater than the maximum take-off mass. The load was not secured. As a result, the performance of the aircraft was degraded and piloting made more difficult. The BEA investigation did not reveal any major failure that could explain a loss of power. Engine performance may have been lower than the manufacturer's standards, due in particular to improper adjustment of the mechanical fuel pump, probably resulting from unsuitable maintenance. This defect was most likely already present on previous flights. It is likely that the power required for the initial climb was greater than what the engine could deliver. This brought the aircraft into a situation where the speed gradually decreased. When the pilot turned, the stall warning sounded and the pilot sensed the engine was losing power.
Final Report:

Crash of a Boeing 707-3J9C in Fath: 15 killed

Date & Time: Jan 14, 2019 at 0830 LT
Type of aircraft:
Operator:
Registration:
EP-CPP
Flight Type:
Survivors:
Yes
Site:
Schedule:
Bishkek - Payam
MSN:
21128/917
YOM:
1976
Country:
Region:
Crew on board:
16
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
15
Circumstances:
The airplane, owned by the Islamic Republic of Iran Air Force (IRIAF) was completing a cargo flight from Bishkek, Kyrgyzstan, on behalf of Saha Airlines, and was supposed to land at Payam Airport located southwest of Karaj, carrying a load of meat. On approach, the crew encountered marginal weather conditions and the pilot mistakenly landed on runway 31L at Fath Airport instead of runway 30 at Payam Airport which is located 10 km northwest. After touchdown, control was lost and the airplane was unable to stop within the remaining distance (runway 31L is 1,140 meters long), overran and crashed in flames into several houses located past the runway end. The aircraft was destroyed by fire as well as few houses. The flight engineer was evacuated while 15 other occupants were killed.

Crash of an Antonov AN-26B in Kinshasa: 7 killed

Date & Time: Dec 20, 2018 at 1000 LT
Type of aircraft:
Operator:
Registration:
9S-AGB
Flight Type:
Survivors:
No
Schedule:
Tshikapa – Kinshasa
MSN:
13402
YOM:
1984
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
The crew was returning to Kinshasa after delivering election equipments and materials in Tshikapa on behalf of the Independent National Election Commission. The crew was cleared to descend to 5,000 feet on approach to runway 06 at Kinshasa-N'Djili Airport but encountered poor weather conditions with rain falls. In limited visibility, the airplane crashed on a hilly terrain located about 35 km west of the airport. The wreckage was found few hours later and all seven occupants were killed.

Crash of a Boeing 747-412F in Halifax

Date & Time: Nov 7, 2018 at 0506 LT
Type of aircraft:
Operator:
Registration:
N908AR
Flight Type:
Survivors:
Yes
Schedule:
Chicago – Halifax
MSN:
28026/1105
YOM:
1997
Flight number:
KYE4854
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
21134
Captain / Total hours on type:
166.00
Copilot / Total flying hours:
7404
Copilot / Total hours on type:
1239
Aircraft flight hours:
92471
Aircraft flight cycles:
16948
Circumstances:
The Sky Lease Cargo Boeing 747-412F aircraft (U.S. registration N908AR, serial number 28026) was conducting flight 4854 (KYE4854) from Chicago/O’Hare International Airport, Illinois, U.S., to Halifax/Stanfield International Airport, Nova Scotia, with 3 crew members, 1 passenger, and no cargo on board. The crew conducted the Runway 14 instrument landing system approach. When the aircraft was 1 minute and 21 seconds from the threshold, the crew realized that there was a tailwind; however, they did not recalculate the performance data to confirm that the landing distance available was still acceptable, likely because of the limited amount of time available before landing. The unexpected tailwind resulted in a greater landing distance required, but this distance did not exceed the length of the runway. The aircraft touched down firmly at approximately 0506 Atlantic Standard Time, during the hours of darkness. After the firm touchdown, for undetermined reasons, the engine No. 1 thrust lever was moved forward of the idle position, causing the speed brakes to retract and the autobrake system to disengage, increasing the distance required to bring the aircraft to a stop. In addition, the right crab angle (4.5°) on initial touchdown, combined with the crosswind component and asymmetric reverser selection, caused the aircraft to deviate to the right of the runway centreline. During the landing roll, the pilot monitoring’s attention was focused on the lateral drift and, as a result, the required callouts regarding the position of the deceleration devices were not made. Although manual brake application began 8 seconds after touchdown, maximum braking effort did not occur until 15 seconds later, when the aircraft was 800 feet from the end of the runway. At this position, it was not possible for the aircraft to stop on the runway and, 5 seconds later, the aircraft departed the end of the runway at a speed of 77 knots and came to a stop 270 m (885 feet) past the end. The aircraft struck the approach light stanchions and the localizer antenna array. The No. 2 engine detached from its pylon during the impact sequence and came to rest under the left horizontal stabilizer, causing a fire in the tail section following the impact. The emergency locator transmitter activated. Aircraft rescue and firefighting personnel responded. All 3 crew members received minor injuries and were taken to the hospital. The passenger was not injured. During the overrun, the aircraft crossed a significant drop of 2.8 m (9 feet) approximately 166 m (544 feet) past the end of the runway and was damaged beyond repair.
Probable cause:
Findings as to causes and contributing factors:
These are conditions, acts or safety deficiencies that were found to have caused or contributed to this occurrence.
1. The ineffective presentation style and sequence of the NOTAMs available to the crew and flight dispatch led them to interpret that Runway 23 was not available for landing at Halifax/Stanfield International Airport.
2. The crew was unaware that the aircraft did not meet the pre-departure landing weight requirements using flaps 25 for Runway 14.
3. Due to the timing of the flight during the nighttime circadian trough and because the crew had had insufficient restorative sleep in the previous 24 hours, the crew was experiencing sleep-related fatigue that degraded their performance and cognitive functioning during the approach and landing.
4. Using unfactored (actual) landing distance charts may have given the crew the impression that landing on Runway 14 would have had a considerable runway safety margin, influencing their decision to continue the landing in the presence of a tailwind.
5. When planning the approach, the crew calculated a faster approach speed of reference speed + 10 knots instead of the recommended reference speed + 5 knots, because they misinterpreted that a wind additive was required for the existing conditions.
6. New information regarding a change of active runway was not communicated by air traffic control directly to the crew, although it was contained within the automatic terminal information service broadcast; as a result, the crew continued to believe that the approach and landing to Runway 14 was the only option available.
7. For the approach, the crew selected the typical flap setting of flaps 25 rather than flaps 30, because they believed they had a sufficient safety margin. This setting increased the landing distance required by 494 feet.
8. The crew were operating in a cognitive context of fatigue and biases that encouraged anchoring to and confirming information that aligned with continuing the initial plan, increasing the likelihood that they would continue the approach.
9. The crew recognized the presence of a tailwind on approach 1 minute and 21 seconds from the threshold; likely due to this limited amount of time, the crew did not recalculate the performance data to confirm that the runway safety margin was still acceptable.
10. An elevated level of stress and workload on short final approach likely exacerbated the performance-impairing effects of fatigue to limit the crew’s ability to determine the effect of the tailwind, influencing their decision to continue the approach.
11. The higher aircraft approach speed, the presence of a tailwind component, and the slight deviation above the glideslope increased the landing distance required to a distance greater than the runway length available.
12. After the firm touchdown, for undetermined reasons, the engine No. 1 thrust lever was moved forward of the idle position, causing the speed brakes to retract and the autobrake system to disengage, increasing the distance required to bring the aircraft to a stop.
13. The right crab angle (4.5°) on initial touchdown, combined with the crosswind component and asymmetric reverser selection, caused the aircraft to deviate to the right of the runway centreline.
14. During the landing roll, the pilot monitoring’s attention was focused on the lateral drift and, as a result, the required callouts regarding the position of the deceleration devices were not made.
15. The pilot flying focused on controlling the lateral deviation and, without the benefit of the landing rollout callouts, did not recognize that all of the deceleration devices were not fully deployed and that the autobrake was disengaged.
16. Although manual brake application began 8 seconds after touchdown, maximum braking effort did not occur until 15 seconds later, when the aircraft was 800 feet from the end of the runway. At this position, it was not possible for the aircraft to stop on the runway and, 5 seconds later, the aircraft departed the end of the runway at a speed of 77 knots and came to a stop 270 m (885 feet) past the end of the runway.
17. During the overrun, the aircraft crossed a significant drop of 2.8 m (9 feet) approximately 166 m (544 feet) past the end of the runway and was damaged beyond repair. While this uneven terrain was beyond the 150 m (492 feet) runway end safety area proposed by Transport Canada, it was within the recommended International Civil Aviation Organization runway end safety area of 300 m (984 feet).

Findings as to risk:
These are conditions, unsafe acts or safety deficiencies that were found not to be a factor in this occurrence but could have adverse consequences in future occurrences.
1. If the pilot monitoring does not call out approach conditions or approach speed increases, the pilot flying might not make corrections, increasing the risk of a runway overrun.

Other findings:
These items could enhance safety, resolve an issue of controversy, or provide a data point for future safety studies.
1. The investigation concluded that there was no reverted rubber hydroplaning and almost certainly no dynamic hydroplaning during this occurrence.
2. Although viscous hydroplaning can be expected on all wet runways, the investigation found that when maximum braking effort was applied, the aircraft braking was consistent with the expected braking on Runway 14 under the existing wet runway conditions.
Final Report:

Crash of a Dassault Falcon 20D in San Luis Potosí

Date & Time: Aug 7, 2018 at 0110 LT
Type of aircraft:
Operator:
Registration:
N961AA
Flight Type:
Survivors:
Yes
Schedule:
Santiago de Querétaro - Laredo
MSN:
205
YOM:
1969
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed Santiago de Querétaro Airport on a night cargo flight to Laredo, Texas, carrying two pilots and a load consisting of automotive parts. En route, the crew encountered engine problems and was clearted to divert to San Luis Potosí-Ponciano Arriaga Airport for an emergency landing. On approach, the crew realized he could not make it and decided to attempt an forced landing. The airplane struck the ground, lost its undercarriage and came to rest in an agricultural area located in Peñasco, about 6 km northeast of runway 14 threshold. The left wing was bent and partially torn off. Both crew members escaped with minor injuries and the aircraft was damaged beyond repair.

Crash of a Curtiss C-46F-1-CU Commando in Manley Hot Springs

Date & Time: Jul 16, 2018 at 0925 LT
Type of aircraft:
Operator:
Registration:
N1822M
Flight Type:
Survivors:
Yes
Schedule:
Fairbanks – Kenai
MSN:
22521
YOM:
1945
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6500
Captain / Total hours on type:
3500.00
Copilot / Total flying hours:
300
Copilot / Total hours on type:
135
Aircraft flight hours:
37049
Circumstances:
The pilot reported that, following a precautionary shutdown of the No. 2 engine, he diverted to an alternate airport that was closer than the original destination. During the landing in tailwind conditions, the airplane touched down "a little fast." The pilot added that, as the brakes faded from continuous use, the airplane was unable to stop, and it overran the end of the runway, which resulted in substantial damage to the fuselage. The pilot reported that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause:
The pilot's failure to attain the proper touchdown speed and his decision to land with a tailwind without ensuring that there was adequate runway length for the touchdown.
Final Report:

Crash of a Cessna 207 Skywagon in the Susitna River: 1 killed

Date & Time: Jun 13, 2018 at 1205 LT
Operator:
Registration:
N91038
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Anchorage - Tyonek
MSN:
207-0027
YOM:
1969
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1442
Captain / Total hours on type:
514.00
Aircraft flight hours:
31711
Circumstances:
Two wheel-equipped, high-wing airplanes, a Cessna 207 and a Cessna 175, collided midair while in cruise flight in day visual meteorological conditions. Both airplanes were operating under visual flight rules, and neither airplane was in communication with an air traffic control facility. The Cessna 175 pilot stated that he was making position reports during cruise flight about 1,000ft above mean sea level when he established contact with the pilot of another airplane, which was passing in the opposite direction. As he watched that airplane pass well below him, he noticed the shadow of a second airplane converging with the shadow of his airplane from the opposite direction. He looked forward and saw the spinner of the converging airplane in his windscreen and immediately pulled aft on the control yoke; the airplanes subsequently collided. The Cessna 207 descended uncontrolled into the river. Although damaged, the Cessna 175 continued to fly, and the pilot proceeded to an airport and landed safely. An examination of both airplanes revealed impact signatures consistent with the two airplanes colliding nearly head-on. About 4 years before the accident, following a series of midair collisions in the Matanuska Susitna (MatSu) Valley (the area where the accident occurred), the FAA made significant changes to the common traffic advisory frequencies (CTAF) assigned north and west of Anchorage, Alaska. The FAA established geographic CTAF areas based, in part, on flight patterns, traffic flow, private and public airports, and off-airport landing sites. The CTAF for the area where the accident occurred was at a frequency changeover point with westbound Cook Inlet traffic communicating on 122.70 and eastbound traffic on 122.90 Mhz. The pilot of the Cessna 175, which was traveling on an eastbound heading at the time of the accident, reported that he had a primary active radio frequency of 122.90 Mhz, and a nonactive secondary frequency 135.25 Mhz in his transceiver at the time of the collision. The transceivers from the other airplane were not recovered, and it could not be determined whether the pilot of the Cessna 207 was monitoring the CTAF or making position reports.
Probable cause:
The failure of both pilots to see and avoid the other airplane while in level cruise flight, which resulted in a midair collision.
Final Report:

Crash of a Cessna 208B Grand Caravan near Simikot: 2 killed

Date & Time: May 16, 2018 at 0645 LT
Type of aircraft:
Operator:
Registration:
9N-AJU
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Surkhet – Simikot
MSN:
208B-0770
YOM:
1999
Location:
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total hours on type:
414.00
Copilot / Total hours on type:
461
Aircraft flight hours:
15757
Aircraft flight cycles:
31540
Circumstances:
The single engine aircraft departed Surkhet Airport at 0612LT on a cargo flight to Simikot. At 0627LT, the crew made his last radio transmission with Nepalgunj Tower. About 18 minutes later, while cruising by night at an altitude of 12,800 feet, the airplane struck the slope of a mountain located near the Simikot Pass, some 12 km from Simikot Airport. The airplane disintegrated on impact and both crew members were killed.
Probable cause:
The Commission determines the most probable cause of this accident was to continue the flight despite unfavorable weather conditions resulting inadvertent flight into instrument
meteorological conditions and there by deviating from the normal track due to loss of situational awareness that aggravated the spatial disorientation leading to CFIT accident. The following contributing factors were reported:
- Possible effect of hypoxia due to flight for prolonged period in high altitude without oxygen supplement,
- Ineffective safety management of the company which prevented the organization from identifying and correcting latent deficiencies in risk management and inadequacies in pilot training.
Final Report:

Crash of a Beechcraft C99 Airliner in Hastings

Date & Time: Mar 16, 2018 at 0750 LT
Type of aircraft:
Operator:
Registration:
N213AV
Flight Type:
Survivors:
Yes
Schedule:
Omaha – Hastings
MSN:
U-213
YOM:
1983
Flight number:
AMF1696
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6500
Captain / Total hours on type:
1145.00
Copilot / Total flying hours:
853
Copilot / Total hours on type:
21
Aircraft flight hours:
17228
Circumstances:
According to the operator's director of safety, during landing in gusty crosswind conditions, the multi-engine, turbine-powered airplane bounced. The airplane then touched down a second time left of the runway centerline. "Recognizing their position was too far left," the flight crew attempted a go-around. However, both engines were almost at idle and "took time to spool back up." Without the appropriate airspeed, the airplane continued to veer to the left. A gust under the right wing "drove" the left wing into the ground. The airplane continued across a grass field, the nose landing gear collapsed, and the airplane slid to a stop. The airplane sustained substantial damage to the fuselage and left wing. The director of safety reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The automated weather observation system located at the accident airport reported that, about the time of the accident, the wind was from 110° at 21 knots, gusting to 35 knots. The pilot landed on runway 04. The Beechcraft airplane flight manual states the max demonstrated crosswind is 25 knots. Based on the stated wind conditions, the calculated crosswind component was 19 to 33 knots.
Probable cause:
The pilot's decision to land in a gusty crosswind that exceeded the airplane's maximum demonstrated crosswind and resulted in a runway excursion.
Final Report: