Crash of a Cessna 560 Citation V in Atlanta: 4 killed

Date & Time: Dec 20, 2018 at 1210 LT
Type of aircraft:
Operator:
Registration:
N188CW
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Atlanta - Millington
MSN:
560-0148
YOM:
1991
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
2300
Captain / Total hours on type:
110.00
Aircraft flight hours:
6854
Circumstances:
The pilot departed on an instrument flight rules flight into instrument meteorological conditions (IMC). Radar data indicated that the airplane entered a left turn after takeoff, consistent with the pilot's instrument clearance. As the airplane climbed to an altitude about 2,410 ft above ground level, its rate of climb increased from about 3,500 ft per minute to 9,600 ft per minute, the stick shaker activated, and the airplane decelerated to about 75 knots. The airplane then entered a descending right turn and rolled inverted before impacting terrain about 1 mile from the airport. All major components of the airplane were located at the accident site, and examination of the wreckage revealed no anomalies with the airplane that would have precluded normal operation. The weather conditions about the time of the accident included an overcast cloud ceiling about 600 ft above ground level. It is likely that the pilot became spatially disoriented after entering the cloud layer, which resulted in the airplane's high rate of climb, rapid loss of airspeed, and a likely aerodynamic stall. The steep descending right turn, the airplane's roll to an inverted attitude, and the high-energy impact are also consistent with a loss of control due to spatial disorientation.
Probable cause:
The pilot's loss of airplane control due to spatial disorientation during initial climb in instrument meteorological conditions.
Final Report:

Crash of a Piper PA-46-350P Malibu off Mayport: 2 killed

Date & Time: Dec 20, 2018 at 0904 LT
Registration:
N307JM
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Kissimmee - Princeton
MSN:
46-36253
YOM:
2000
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
390
Captain / Total hours on type:
30.00
Aircraft flight hours:
3785
Circumstances:
The aircraft impacted the Atlantic Ocean near Mayport, Florida. The private pilot and pilot-rated passenger were fatally injured. The airplane was destroyed. The airplane was privately owned and operated under the provisions of Title 14 Code of Federal Regulations Part 91. Instrument meteorological conditions prevailed at the time and the flight was operating on an instrument flight rules (IFR) flight plan. The personal flight originated from Kissimmee Gateway Airport, Orlando, Florida, about 0821, and was destined for Princeton Airport, Princeton/Rocky Hill, NJ. According to preliminary air traffic control radar and voice data provided by the Federal Aviation Administration (FAA), at 0859:02, one of the airplane's occupants contacted the Jacksonville Air Route Traffic Control Center (ZJX ARTCC) R-73 sector controller and reported passing through Flight Level (FL) 220 for FL230. The controller advised the pilot there were moderate and some heavy precipitation along the route of flight extending for 200 nautical miles. The occupant acknowledged the controller and advised they would be watching the weather. FAA radar data indicated at 0900:22 the flight reached FL227. Preliminary review of weather data revealed that this altitude was above the freezing level, and at that time the flight entered an area of weather radar returns with intensities between 10 to 30 dBZ (which equated to light to moderate precipitation). While in the weather radar-indicated precipitation, the flight climbed to FL230. At 0902:14, while at the edge of the precipitation, the airplane started a slight left turn before entering a right turn at 0902:28 at FL226. The turn had not been directed by the controller or announced by either occupant. Between 0902:28 and 0903:10, the airplane descended from FL226 to FL202. At 0903:10, the airplane was descending through FL202 when the controller attempted to contact the flight, but there was no reply. The controller attempted to communicate with the flight several more times, and at 0903:27 in response to one attempt, while at 14,500 feet mean sea level (msl), an occupant advised, "were not ok we need help." The controller asked the pilot if he was declaring an emergency and "whats going on." At 0903:35, while at 12,600 feet msl an occupant stated, "I'm not sure whats happening", followed by, "I have anti-ice and everything." At 0903:40 the controller asked the flight if it could maintain altitude, an occupant responded that they could not maintain altitude. The controller provided vectors to a nearby airport west of their position, but the flight did not reply to that transmission or a subsequent query. At about 0904:32 (which was the last communication from the airplane), while at 3,300 feet msl, an occupant advised the controller that the airplane was inverted and asked for assistance. The last radar recorded position with altitude read-out of the flight was at 0904:40, at an altitude of 1,700 feet msl, and 30.40069° north latitude and -81.3844° west longitude. The U.S. Coast Guard initiated a search for the missing airplane, but the wreckage was not located and the search was suspended on December 22, 2018. A privately-funded search for the airplane was initiated and the wreckage was located and recovered on February 6, 2019. The recovered wreckage was retained for further investigation.
Probable cause:
An in-flight loss of control following an encounter with supercooled large droplet icing conditions, which ultimately resulted in an uncontrolled descent and subsequent inflight breakup. Also causal was the pilot’s failure to maintain an appropriate airspeed for flight in icing conditions.
Final Report:

Crash of a Cessna 550 Citation II in Fargo

Date & Time: Nov 30, 2018 at 1353 LT
Type of aircraft:
Operator:
Registration:
N941JM
Flight Type:
Survivors:
Yes
Schedule:
Williston - Fargo
MSN:
550-0146
YOM:
1980
Crew on board:
1
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1513
Captain / Total hours on type:
253.00
Aircraft flight hours:
7180
Circumstances:
The commercial pilot was conducting a cross-country, business flight with 10 passengers onboard the 8-passenger airplane. He reported that air traffic control cleared the flight for an instrument landing system (ILS) approach to the runway. While descending, the airplane entered instrument meteorological conditions (IMC) at 3,100 ft mean sea level (msl), and ice started to accumulate on the wing's leading edges, empennage, and windshield. The pilot activated the pneumatic deice boots multiple times during the approach and slowed the airplane to 120 knots. The airplane then exited the clouds about 400 ft above ground level (agl), and the pilot maintained 120 knots as the airplane flew over the airport fence; all indications for landing were normal. About 100 ft agl, the airplane started to pull right. He applied left correction inputs, but the airplane continued to pull right. He applied engine power to conduct a goaround, but the airplane landed in grass right of the runway, sustaining damage to the wings and landing gear. Witnesses and passengers reported that the airplane stalled. During examination of the airplane immediately after the accident, about 1/2 to 1 inch of mixed ice was found on the right wing's leading edge, the vertical and horizontal stabilizers, and the angle of attack probe. Ice was also observed on the windshield. The flaps were found in the "up" position. Flight control continuity was established. Although the airplane was originally certificated for two-pilot operation, the pilot was flying the airplane under a single-pilot exemption. The pilot received a logbook endorsement indicating that he had received single-pilot training and was properly qualified under the single-pilot exemption. However, he
had not met the turbine flight time qualifications (1,000 hours) to be properly authorized to conduct the flight under the single-pilot exemption because he only had 500 hours. A review of cockpit voice recorder information indicated that, although the pilot verbalized that the landing gear was "all green," followed by stating "check, check, check," he did not verbalize all the approach or landing checklist items nor did he make any audible comments about activating the pneumatic deice boots or windshield anti-ice. A review of radar data for the flight indicated that, during the last 2 minutes of flight, while the airplane was on final approach to the runway, the indicated airspeed got as low as 99 knots. The last recorded radar return indicated that the airplane had an airspeed of 104 knots at 900 ft msl. The pilot's lack of minimum flight experience required to fly the airplane without a copilot likely led to task saturation as he flew the airplane entered IMC and icing conditions while on an ILS approach. He subsequently failed to lower the flaps during the approach, which resulted in a no-flap approach instead of a full-flap landing. The ice on the leading edges of the wings, the no-flap approach, and the low airspeed likely led to the exceedance of the airplane's critical angle of attack, which resulted in an aerodynamic stall.
Probable cause:
The pilot's failure to lower the flaps during the approach and maintain sufficient airspeed while flying in instrument meteorological and icing conditions and the accumulation of ice on the wings' leading edges, which resulted in the exceedance of the airplane's critical angle of attack and subsequent aerodynamic stall. Contributing to the accident was the pilot's lack of proper qualification to operate the airplane under a single-pilot exemption due to his lack of total turbine time, which led to task saturation and his failure to properly configure the flaps for landing.
Final Report:

Crash of a Cessna 525 CitationJet Cj2+ in Memphis: 3 killed

Date & Time: Nov 30, 2018 at 1028 LT
Type of aircraft:
Operator:
Registration:
N525EG
Flight Phase:
Survivors:
No
Schedule:
Jeffersonville – Chicago
MSN:
525-0449
YOM:
2009
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
3500
Aircraft flight hours:
3306
Circumstances:
On November 30, 2018, about 1028 central standard time, a Cessna 525A (Citation) airplane, N525EG, was destroyed when it was involved in an accident near Memphis, Indiana. The pilot and two passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 business flight. The cross-country flight originated from Clark Regional Airport (JVY), Jeffersonville, Indiana, and was en route to Chicago Midway International Airport (MDW), Chicago, Illinois. The airplane was equipped with automatic dependent surveillance–broadcast (ADS-B), which recorded latitude and longitude from GPS, pressure and geometric altitude, and selected altitude and heading. The airplane was also equipped with a cockpit voice recorder (CVR), which recorded the accident flight and annunciations from the enhanced ground proximity warning system (EGPWS). It was not equipped with a flight data recorder (FDR) nor was it required to be. Review of the CVR transcript showed that the pilot operated as a single pilot but verbalized his actions as he configured the airplane before departure. He referenced items from the Before Taxi checklist and included in his crew briefing that in the event of a problem after takeoff decision speed, he would handle it as an in-flight emergency and “fly the airplane, address the problem, get the autopilot on, talk on the radios, divert over to Stanford.” The air traffic controller provided initial clearance for the pilot to fly direct to the STREP intersection and to climb and maintain 3,000 ft mean sea level. Before the departure from JVY, the pilot announced on the common traffic advisory frequency that he was departing runway 36 and verbalized in the cockpit “this is three six” before he advanced the throttles. The flight departed JVY about 1024:36 into instrument meteorological conditions. The CVR recorded the pilot state that he set power to maximum cruise thrust, switched the engine sync on, and turned on the yaw dampers. The pilot also verbalized his interaction with the autopilot, including navigation mode, direct STREP, and vertical speed climb up to 3,000 ft. According to the National Transportation Safety Board’s (NTSB) airplane performance study, the airplane climbed to about 1,400 ft msl before it turned left onto a course of 330° and continued to climb. The CVR recorded the pilot state he was turning on the autopilot at 1025:22. At 1025:39, the pilot was cleared up to 10,000 ft and asked to “ident,” and the airplane was subsequently identified on radar. The pilot verbalized setting the autopilot for 10,000 ft and read items on the After Takeoff/Climb checklist. The performance study indicated that the airplane passed 3,000 ft about 1026, with an airspeed between 230 and 240 kts, and continued to climb steadily. At 1026:29, while the pilot was conducting the checklist, the controller instructed him to contact the Indianapolis Air Route Traffic Control Center; the pilot acknowledged. At 1026:38, the pilot resumed the checklist and stated, “uhhh lets seeee. Pressurization pressurizing anti ice de-ice systems are not required at this time.” The performance study indicated that, at 1026:45, the airplane began to bank to the left at a rate of about 5° per second and that after the onset of the roll, the airplane maintained airspeed while it continued to climb for 12 seconds, consistent with engine power not being reduced in response to the roll onset. At 1026:48, the CVR recorded the airplane’s autopilot disconnect annunciation, “autopilot.” The performance study indicated that about this time, the airplane was in about a 30° left bank. About 1 second later, the pilot stated, “whooooaaaaah.” Over the next 8 seconds, the airplane’s EGPWS annunciated six “bank angle” alerts. At 1026:57, the airplane reached its maximum altitude of about 6,100 ft msl and then began to descend rapidly, in excess of 11,000 ft per minute. At 1026:58, the bank angle was about 70° left wing down, and by 1027:05, the airplane was near 90° left wing down. At 1027:04, the CVR recorded a sound similar to an overspeed warning alert, which continued to the end of the flight. The performance study indicated that about the time of the overspeed warning, the airplane passed about 250 kts calibrated airspeed at an altitude of about 5,600 ft. After the overspeed warning, the pilot shouted three expletives, and the bank angle alert sounded two more times. According to the performance study, at 1027:18, the final ADS-B data point, the airplane was about 1,000 ft msl, with the airspeed about 380 kts and in a 53° left bank. At 1027:11, the CVR recorded the pilot shouting a radio transmission, “mayday mayday mayday citation five two five echo golf is in an emergency descent unable to gain control of the aircraft.” At 1027:16, the CVR recorded the EGPWS annunciating “terrain terrain.” The sound of impact was recorded about 1027:20. The total time from the beginning of the left roll until ground impact was about 35 seconds. The accident site was located about 8.5 miles northwest of JVY.
Probable cause:
The asymmetric deployment of the left wing load alleviation system for undetermined reasons, which resulted in an in-flight upset from which the pilot was not able to recover.
Final Report:

Crash of a Cessna 441 Conquest II in Harmon: 3 killed

Date & Time: Nov 18, 2018 at 2240 LT
Type of aircraft:
Operator:
Registration:
N441CX
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Bismarck - Williston
MSN:
441-0305
YOM:
1982
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
4685
Captain / Total hours on type:
70.00
Circumstances:
The pilot and two medical crewmembers were repositioning the airplane to pick up a patient for aeromedical transport. Dark night instrument meteorological conditions prevailed for the flight. Radar data showed the airplane climb to 14,000 ft mean sea level after departure and proceed direct toward the destination airport before beginning a right descending turn. The airplane subsequently broke up inflight and impacted terrain. No distress calls were received from the pilot before the accident. Although weather conditions were conducive for inflight icing, no evidence of structural icing was identified at the scene. The debris field was 2,500 ft long and the disbursement of the wreckage confirmed that both wings, the horizontal stabilizer, both elevators, and both engines separated from the airplane before impacting the ground. Examination of the wreckage revealed that the initiating failure was the failure of the wing where it passed through the center of the airplane. The three wing spars exhibited S-bending deformation, indicative of positive overload producing compressive buckling and fracture. Further, impact signatures as black paint transfers and gouged aluminum, were consistent with the left outboard wing separating when it was struck by the right engine after the wing spars failed. There was no evidence of any pre-exiting conditions that would have degraded the strength of the airplane structure at the fracture locations. Flight control continuity was confirmed. An examination of the engines, propellers, and available systems showed no mechanical malfunctions or failure that could have contributed to the accident. The descending right turn was inconsistent with the intended flight track and ATC-provided clearance. However, there was insufficient information to determine how it was initiated and when the pilot became aware of the airplane's state in the dark night IMC conditions. Yet, the
absence of a distress call or communication with ATC about the airplane's deviation suggests that the pilot was not initially aware of the change in state. The structural failure signatures on the airplane were indicative of the wings failing in positive overload, which was consistent with the pilot initiating a pullup maneuver that exceeded the airplane spars' structural integrity during an attempted recovery from the spiral dive.
Probable cause:
The pilot's failure to maintain control of the airplane in dark night conditions that resulted in an in-flight positive overload failure of the wings and the subsequent in-flight breakup of the airplane.
Final Report:

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 Gulfstream 690C Jetprop 840 off Myrtle Beach

Date & Time: Nov 12, 2018 at 1415 LT
Operator:
Registration:
N840JC
Flight Type:
Survivors:
Yes
Schedule:
Greater Cumberland - Myrtle Beach
MSN:
690-11676
YOM:
1981
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
22335
Aircraft flight hours:
8441
Circumstances:
The airplane sustained substantial damage when it collided with terrain during an approach to landing at the Myrtle Beach International Airport (MYR), Myrtle Beach, South Carolina. The commercial pilot was seriously injured. The airplane was privately owned and operated under the provisions of Title 14 Code of Federal Regulations Part 91 as a personal flight. Instrument meteorological conditions prevailed, and an instrument flight rules flight plan was filed for the flight that departed Greater Cumberland Regional Airport (CBE), Cumberland, Maryland. According to the pilot, he was following radar vectors for the downwind leg of the traffic pattern to runway 36 at MYR. He turned for final approach and was inside the outer marker, when he encountered heavy turbulence. As he continued the approach, he described what he believed to be a microburst and the airplane started to descend rapidly. The pilot added full power in an attempt to climb, but the airplane continued to descend until it collided with the Atlantic Ocean 1 mile from the approach end of runway 36. A review of pictures of the wreckage provided by a Federal Aviation Administration inspector revealed the cockpit section of the airplane was broken away from the fuselage during the impact sequence. At 1456, the weather recorded at MYR, included broken clouds at 6,000 ft, few clouds at 3,500 ft and wind from 010° at 8 knots. The temperature was 14°C, and the dew point was 9°C. The altimeter setting was 30.27 inches of mercury. The airplane was retained for further examination.
Probable cause:
An encounter with low-level windshear and turbulence during the landing approach, which resulted in a loss of airplane control.
Final Report:

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 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: