Crash of a Cessna 340A in Ponoka

Date & Time: Nov 13, 2018 at 1815 LT
Type of aircraft:
Operator:
Registration:
C-GMLS
Flight Type:
Survivors:
Yes
MSN:
340A-0771
YOM:
1979
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On approach to Ponoka-Labrie Field, the pilot encountered technical problems with the autopilot and decided to make a go-around. While in the circuit pattern, the autopilot failed to disconnect properly so the pilot attempted an emergency landing in a field. The airplane belly landed then contacted trees. Upon impact, the tail was torn off and the aircraft came to rest. The pilot was seriously injured.

Crash of a Lockheed C-130E Hercules at Chaklala-Nur Khan AFB

Date & Time: Nov 9, 2018 at 1438 LT
Type of aircraft:
Operator:
Registration:
4180
Flight Type:
Survivors:
Yes
Schedule:
Chaklala - Chaklala
MSN:
4180
YOM:
1966
Country:
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a training mission at Chaklala-Nur Khan AFB in Islamabad. Upon touchdown, a tyre burst. Control was lost and the airplane veered off runway to the right and collided with a concrete wall before coming to rest, burstin into flames. All nine occupants escaped uninjured while the aircraft was destroyed by a post crash fire. It is believed that the landing was hard.

Crash of a Boeing 757-23N in Georgetown: 1 killed

Date & Time: Nov 9, 2018 at 0253 LT
Type of aircraft:
Operator:
Registration:
N524AT
Survivors:
Yes
Schedule:
Georgetown – Toronto
MSN:
30233/895
YOM:
1999
Flight number:
OJ256
Country:
Crew on board:
8
Crew fatalities:
Pax on board:
120
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The airplane departed Georgetown-Cheddi Jagan Airport at 0209LT on an international schedule flight to Toronto-Lester Bowles Pearson Airport, carrying 120 passengers (118 adults and two children) and 8 crew members. At 0222LT, while climbing to 21,000 feet, the crew encountered technical problems with the hydraulic systems and was cleared to return. The captain made a 180 turn and followed a circuit and a holding pattern to burn fuel until he started the final approach to runway 06. After touchdown, the crew started the braking procedure but the airplane was apparently unable to stop within the remaining distance. Approaching the end of the runway, the aircraft veered to the right, lost its right main gear and came to rest in a sandy area with the right engine torn off and the right wing severely damaged. All 128 occupants evacuated, among them six were injured. One week later, on November 16, a 86 year old woman died from her injuries (fractured skull).

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 Piper PA-46-350P Malibu Mirage in Hurricane

Date & Time: Oct 21, 2018 at 1500 LT
Registration:
N413LL
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Hurricane - Salt Lake City
MSN:
46-36413
YOM:
2007
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7000
Captain / Total hours on type:
1500.00
Aircraft flight hours:
1088
Circumstances:
Shortly after takeoff, the pilot smelled smoke. As he began to turn the airplane back to the airport, the engine lost total power. He conducted a forced landing in a field just short of the airport, during which the airplane struck a metal fence and pipe. All occupants egressed, and the pilot then noticed that a fire had erupted under the airplane's engine cowling. Postaccident examination revealed that the airplane sustained fire damage to the roof and forward end of the baggage compartment along with the engine accessory area between the firewall and aft air baffles. Further examination revealed that one of the engine exhaust crossover pipe assemblies was misaligned at the slip joint. An engine manufacturer service bulletin (SB) called for inspections of the exhaust system slip and flange joints to identify misaligned exhaust components. The last maintenance event occurred about 7 1/2 flight hours before the accident, during which the SB was performed and resulted in the replacement of crossover pipes. The mechanic who had performed the most recent maintenance did not follow the correct procedures for reinstallation of the crossover pipe, and the inspector who reviewed his work did not examine the installation as it progressed but instead inspected the pipes after they were installed and essentially hidden from view by their protective heat shield. As a result of the misaligned engine exhaust crossover pipe, hot exhaust gases escaped into the engine compartment and started a fire, which compromised critical engine fuel and oil lines, and resulted in the loss of engine power.
Probable cause:
The mechanic's failure to properly align the engine exhaust crossover pipe during replacement, and his supervisor's failure to properly inspect the installation, which resulted in an in-flight fire and the loss of engine power.
Final Report:

Crash of a Sukhoi Superjet 100-95B in Yakutsk

Date & Time: Oct 10, 2018 at 0321 LT
Type of aircraft:
Operator:
Registration:
RA-89011
Survivors:
Yes
Schedule:
Ulan-Ude - Yakutsk
MSN:
95019
YOM:
2012
Flight number:
SYL414
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
87
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13125
Captain / Total hours on type:
1080.00
Copilot / Total flying hours:
3200
Copilot / Total hours on type:
1300
Aircraft flight hours:
8115
Aircraft flight cycles:
3320
Circumstances:
Following an uneventful flight from Ulan-Ude, the crew initiated the approach to Yakutsk-Platon Oyunsky Intl Airport Runway 23L. Due to work in progress, the runway 05R threshold was displaced by 1,150 metres, reducing the landing distance to 2,248 metres for the runway 23L on which the touchdown zone lighting system was unserviceable. On approach, the crew was informed by ATC that the friction coefficient was 0,45. The crew completed the landing on runway 23L with a slight tailwind component of 4 knots and started the braking procedure. Unable to stop within the remaining distance, the aircraft overran, entered the construction area and collided with the junction of a concrete section under reconstruction, causing both main landing gear to collapse (the left main gear was torn off). The aircraft slid for another 250 metres before coming to rest. All 92 occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
The cause of the aviation accident with the RRJ 95B RA-89011 aircraft when landing at night with one deactivated thrust reverser was the transfer to the crew of incorrect information about the value of the friction coefficient, which led to the landing on an icy runway, the average normative friction coefficient which was less than 0.3, which did not allow landing in accordance with current regulations. This led to a significant increase in landing distance, rolling the aircraft out of the runway and collision with the junction of the reconstructed section of the runway with a height of about 0.4 m, which led to the destruction of the main landing gear supports and damage to the engines with fuel leakage without causing a fire.
The contributing factors were the following:
- Absence of a connecting ramp (which was not envisaged by the reconstruction project) between the current and the part of the runway being reconstructed;
- inefficiency of the SMS of Yakutsk Airport JSC in terms of identification and control of risks associated with the possibility of ice formation at the runway, and insufficient control over the implementation of the SMS by aviation authorities;
- erroneous determination of the Xc value at the last measurement;
- inefficiency of ice removal procedure during runway cleaning due to lack of chemical reagents for ice removal and/or thermal machines at the airfield;
- lack of information from the RRJ-95LR-100 RA 89038 aircraft crew about actual rolling out of the runway, which was an aviation incident and was subject to investigation;
- failure by airport and ATC officials to take appropriate action after receiving the RRJ-95LR-100 RA-89038 low friction report from the aircraft crew.
Final Report:

Crash of an Antonov AN-32 in Khartoum

Date & Time: Oct 3, 2018
Type of aircraft:
Operator:
Flight Type:
Survivors:
Yes
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The airplane was engaged in an exercise with a second Sudanese Air Force Antonov AN-32. After touchdown on runway 18, the crew started the braking procedure when the airplane was struck by the AN-32 from behind. After collision, both airplanes went out of control and came to rest on the runway edge. There were no casualties while both aircraft were destroyed. It appears that the AN-32 landed shortly after the AN-26 and was unable to stop in a timely manner.

Crash of an Antonov AN-26 in Khartoum

Date & Time: Oct 3, 2018
Type of aircraft:
Operator:
Registration:
7706
Flight Type:
Survivors:
Yes
MSN:
104 04
YOM:
1980
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The airplane was engaged in an exercise with a second Sudanese Air Force Antonov AN-32. After touchdown on runway 18, the crew started the braking procedure when the airplane was struck by the AN-32 from behind. After collision, both airplanes went out of control and came to rest on the runway edge. There were no casualties while both aircraft were destroyed. It appears that the AN-32 landed shortly after the AN-26 and was unable to stop in a timely manner.

Crash of a Dassault Falcon 50 in Greenville: 2 killed

Date & Time: Sep 27, 2018 at 1346 LT
Type of aircraft:
Registration:
N114TD
Survivors:
Yes
Schedule:
St Petersburg - Greenville
MSN:
17
YOM:
1980
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
11650
Copilot / Total flying hours:
5500
Aircraft flight hours:
14002
Circumstances:
The flight crew was operating the business jet on an on-demand air taxi flight with passengers onboard. During landing at the destination airport, the cockpit voice recorder (CVR) recorded the sound of the airplane touching down followed by the pilot's and copilot's comments that the brakes were not operating. Air traffic controllers reported, and airport surveillance video confirmed, that the airplane touched down "normally" and the airplane's thrust reverser deployed but that the airplane continued down the runway without decelerating before overrunning the runway and impacting terrain. Postaccident examination of the airplane's brake system revealed discrepancies of the antiskid system that included a broken solder joint on the left-side inboard transducer and a reversal of the wiring on the right-side outboard transducer. It is likely that these discrepancies resulted in the normal braking system's failure to function during the landing. Before the accident flight, the airplane had been in long-term storage for several years and was in the process of undergoing maintenance to bring the airplane back to a serviceable condition, which in-part required the completion of several inspections, an overhaul of the landing gear, and the resolution of over 100 other unresolved discrepancies. The accident flight and four previous flights were all made with only a portion of this required maintenance having been completed and properly documented in the airplane's maintenance logs. A pilot, who had flown the airplane on four previous flights along with the accident pilot (who was acting as second-in-command during them), identified during those flights that the airplane's normal braking system was not operating when the airplane was traveling faster than 20 knots. He remedied the situation by configuring the airplane to use the emergency, rather than normal, braking system. That pilot reported this discrepancy to the operator's director of maintenance, and it is likely that maintenance personnel from the company subsequently added an "INOP" placard near the switch on the date of the accident. The label on the placard referenced the antiskid system, and the airplane's flight manual described that with the normal brake (or antiskid) system inoperative, the brake selector switch must be positioned to use the emergency braking system. Following the accident, the switch was found positioned with the normal braking system activated, and it is likely that the accident flight crew attempted to utilize the malfunctioning normal braking system during the landing. Additionally, the flight crew failed to properly recognize the failure and configure the airplane to utilize the emergency braking system, or utilize the parking brake, as described in the airplane's flight manual, in order to stop the airplane within the available runway.
Probable cause:
The operator's decision to allow a flight in an airplane with known, unresolved maintenance discrepancies, and the flight crew's failure to properly configure the airplane in a way that would have allowed the emergency or parking brake systems to stop the airplane during landing.
Final Report:

Crash of a Beechcraft 200 Super King Air in Oscoda: 1 killed

Date & Time: Sep 25, 2018 at 0613 LT
Operator:
Registration:
N241CK
Flight Type:
Survivors:
No
Schedule:
Detroit - Oscoda
MSN:
BB-272
YOM:
1977
Flight number:
K985
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
3806
Captain / Total hours on type:
201.00
Aircraft flight hours:
13933
Circumstances:
The airline transport pilot of the multiengine airplane was cleared for the VOR approach. The weather at the airport was reported as 400 ft overcast with 4 miles visibility in drizzle. When the airplane failed to arrive at the airport as scheduled, a search was initiated, and the wreckage was located soon thereafter. Radar data indicated that the pilot was provided vectors to intercept the final approach course. The last radar return indicated that the airplane was at 2,200 ft and 8.1 miles from the runway threshold. It impacted terrain 3.5 miles from the runway threshold and left of the final approach course. According to the published approach procedure, the minimum descent altitude was 1,100 feet, which was 466 ft above airport elevation. Examination of the wreckage revealed that the airplane had impacted the tops of trees and descended at a 45° angle to ground contact; the airplane was destroyed by a postcrash fire, thus limiting the examination; however, no anomalies were observed that would have precluded normal operation. The landing gear was extended, and approach flaps had been set. Impact and fire damage precluded an examination of the flight and navigation instruments. Autopsy and toxicology of the pilot were not performed; therefore, whether a physiological issue may have contributed to the accident could not be determined. The location of the wreckage indicates that the pilot descended below the minimum descent altitude (MDA) for the approach; however, the reason for the pilot's descent below MDA could not be determined based on the available information.
Probable cause:
The pilot's descent below minimum descent altitude during the non precision instrument approach for reasons that could not be determined based on the available information.
Final Report: