Private

On final approach to Los Ángeles-María Dolores Airport, the airplane crashed in a wooded area located about 412 metres short of runway 18, bursting into flames. The aircraft was destroyed by impact forces and a post crash fire and the pilot, sole on board, was killed. The accident occurred 19 minutes after sunset.

En route from Vancouver to Pender Harbour, the pilot encountered engine problems and elected to ditch the aircraft about three miles off Sechelt. All three occupants were able to evacuate the cabin before the aircraft sank and was lost. All three occupants were rescued.

The pilot was in cruise flight at an altitude of 19,000 feet mean sea level (msl) for about 1 hour and 10 minutes on an easterly heading when he requested a diversion from his filed destination to an airport along his route of flight to utilize a restroom. Two miles west of his amended destination at 12,000 ft msl, the pilot advised the controller that he had a “fuel emergency light" and wanted to expedite the approach. The controller acknowledged the low fuel warning and cleared the airplane to descend from its assigned altitude. Instead of conducting the descent over the airport, the airplane continued its easterly heading past the airport for nearly 8 miles before reversing course. After reversing course, instead of assuming a direct heading back to the airport, the pilot assumed a parallel reciprocal track and didn’t turn for the airport until the airplane intercepted the extended centerline of the landing runway. The pilot informed the controller that he was unable to make it to the airport and performed a forced landing less than 1 mile from the landing runway. Both fuel tanks were breached during the accident sequence, and detailed postaccident inspections of the airplane’s fuel system revealed no leaks in either the supply or return sides of the system. A computer tomography scan and flow-testing of the engine-driven fuel pump revealed no leaks or evidence of fuel leakage. The engine ran successfully in a test cell. Data recovered from an engine and fuel monitoring system revealed that, during the two flights before the accident flight, the reduction in fuel quantity was consistent with the fuel consumption rates depicted at the respective power settings (climb, cruise, etc). During the accident flight, the reduction in fuel quantity was consistent with the indicated fuel flow throughout the climb; however, the fuel quantity continued to reduce at a rate consistent with a climb power setting even after engine power was reduced, and the fuel flow indicated a rate consistent with a cruise engine power setting. The data also showed that the indicated fuel quantity in the left and right tanks reached 0 gallons within about 10 minutes of each other, and shortly before the accident. Given this information, it is likely that the engine lost power due to an exhaustion of the available fuel supply; however, based on available data and findings of the fuel system and component examinations, the disparate rates of indicated fuel flow and fuel quantity reduction could not be explained.

While approaching class B airspace, the airline transport pilot was in communication with a controller who later stated that the pilot's speech was slurred, and the controller repeatedly asked if the oxygen system on the airplane was working properly. As the airplane approached a nearby airport, about 85 miles from his destination airport, the pilot stated he had the airport in sight and repeatedly requested a visual approach. The controller instructed the pilot to continue his flight to his destination, in a southwest direction. As the controller attempted to maintain communications, the pilot dropped off radar shortly after passing the nearby airport and subsequently landed at the nearby airport, which was not his destination airport. According to a surveillance video and impact marks on the runway, the airplane landed hard about halfway down the runway and slid to a stop on the left side of the runway. The airplane fuselage and wings were mostly consumed by postimpact fire. After authorities arrived onsite, the pilot was arrested for operating an aircraft under the influence of alcohol. The pilot was found to have a blood alcohol level of .288, which likely contributed to the pilot landing at the incorrect airport and his subsequent loss of airplane control during landing.

At approximately 1000LT on 12 July 2019, a private de Havilland DHC-2 Mk. 1 Beaver floatplane (registration C‑GRHF, serial number 1123) took off from the St-Mathias Water Aerodrome (CSV9), Quebec, with only the pilot on board, for a series of visual flight rules (VFR) flights. The aircraft landed at approximately 1130 on Désert Lake in La Minerve, Quebec, and came alongside a private dock where 3 individuals were waiting to board and fly to a fishing lodge. Once the baggage was stowed on the aircraft, the pilot provided a safety briefing to the passengers, who were all wearing a personal flotation device. The aircraft took off from Désert Lake at approximately 1215, bound for the Barrage Gouin Water Aerodrome (CTP3), Quebec, where the aircraft was scheduled to be refuelled. The aircraft landed at approximately 1430. Once the refuelling was complete, the aircraft took off once again around 1528, headed northwest to Weakwaten Lake, Quebec, where the fishing lodge was located. After approximately 48 minutes of flight, at around 1616, the aircraft collided with trees and struck the ground. There was no post-impact fire. The emergency locator transmitter was activated by the force of impact, and began transmitting a signal on frequency 121.5 MHz. This signal was detected by the flight crew of a commercial airliner at 1705 and reported to air traffic services. At 1850, the Joint Rescue Coordination Centre in Trenton dispatched a CC130 Hercules aircraft to try to locate the distress signal. The occurrence aircraft was found in a densely wooded area at 2032. Two search and rescue technicians were parachuted to rescue the aircraft occupants. Three of the 4 occupants received fatal injuries. The survivor was evacuated and transported to the hospital in Chibougamau, Quebec.

The pilot, co-pilot, and eight passengers departed on a cross-country flight in the twin-engine airplane. One witness located on the ramp at the airport reported that the airplane sounded underpowered immediately after takeoff “like it was at a reduced power setting.” Another witness stated that the airplane sounded like it did not have sufficient power to takeoff. A third witness described the rotation as “steep,” and other witnesses reported thinking that the airplane was performing aerobatics. Digital video from multiple cameras both on and off the airport showed the airplane roll to its left before reaching a maximum altitude of 100 ft above ground level; it then descended and impacted an airport hangar in an inverted attitude about 17 seconds after takeoff and an explosion immediately followed. After breaching a closed roll-up garage door, the airplane came to rest on its right side outside of the hangar and was immediately involved in a postimpact fire. Sound spectrum analysis of data from the airplane’s cockpit voice recorder (CVR) estimated that the propeller speeds were at takeoff power (1,714 to 1,728 rpm) at liftoff. About 7 seconds later, the propeller speeds diverged, with the left propeller speed decreasing to about 1,688 rpm and the right propeller speed decreasing to 1,707 rpm. Based on the airplane’s estimated calibrated airspeed of about 110 knots and the propeller rpm when the speeds diverged, the estimated thrust in the left engine decreased to near 0 while the right engine continued operating at slightly less than maximum takeoff power. Analysis of available data estimated that, 2 seconds after the propeller speed deviation, the airplane’s sideslip angle was nearly 20°. During the first 5 seconds after the propeller speed deviation, the airplane’s roll rate was about 5° per second to the left; its roll rate then rapidly increased to more than 60° per second before the airplane rolled inverted. Witness marks on the left engine and propeller, the reduction in propeller speed, and the airplane’s roll to the left suggest that the airplane most likely experienced a loss of thrust in the left engine shortly after takeoff. The airplane manufacturer’s engine-out procedure during takeoff instructed that the landing gear should be retracted once a positive rate of climb is established, and the propeller of the inoperative engine should be feathered. Right rudder should also be applied to balance the yawing moment imparted by a thrust reduction in the left engine. Examination of the wreckage found both main landing gear in a position consistent with being extended and the left propeller was unfeathered. The condition of the wreckage precluded determining whether the autofeather system was armed or activated during the accident flight. Thus, the pilot failed to properly configure the airplane once the left engine thrust was reduced. Calculations based on the airplane’s sideslip angle shortly after the propeller speed deviation determined that the thrust asymmetry alone was insufficient to produce the sideslip angle. Based on an evaluation of thrust estimates provided by the propeller manufacturer and performance data provided by the airplane manufacturer, it is likely that the pilot applied left rudder, the opposite input needed to maintain lateral control, before applying right rudder seconds later. However, by then, the airplane’s roll rate was increasing too rapidly, and its altitude was too low to recover. The data support that it would have been possible to maintain directional and lateral control of the airplane after the thrust reduction in the left engine if the pilot had commanded right rudder initially rather than left rudder. The pilot’s confused reaction to the airplane’s performance shortly after takeoff supports the possibility that he was startled by the stall warning that followed the propeller speed divergence, which may have prompted his initial, improper rudder input. In addition, the NTSB’s investigation estimated that rotation occurred before the airplane had attained Vr (rotation speed), which decreased the margin to the minimum controllable airspeed and likely lessened the amount of time available for the pilot to properly react to the reduction in thrust and maintain airplane control. Although the airplane was slightly over its maximum takeoff weight at departure, its rate of climb was near what would be expected at maximum weight in the weather conditions on the day of the accident (even with the extended landing gear adding drag); therefore, the weight exceedance likely was not a factor in the accident. Engine and propeller examinations and functional evaluations of the engine and propeller controls found no condition that would have prevented normal operation; evidence of operation in both engines at impact was found. Absent evidence of an engine malfunction, the investigation considered whether the left engine’s thrust reduction was caused by other means, such as uncommanded throttle movement due to an insufficient friction setting of the airplane’s power lever friction locks. Given the lack of callouts for checklists on the CVR and the pilot’s consistently reported history of not using checklists, it is possible that he did not check or adjust the setting of the power lever friction locks before the accident flight, which led to uncommanded movement of the throttle. Although the co-pilot reportedly had flown with the pilot many times previously and was familiar with the B-300, he was not type rated in the airplane and was not allowed by the pilot to operate the flight controls when passengers were on board. Therefore, the co-pilot may not have checked or adjusted the friction setting before the flight’s departure. Although the investigation considered inadequate friction setting the most likely cause of the thrust reduction in the left engine, other circumstances, such as a malfunction within the throttle control system, could also result in loss of engine thrust. However, heavy fire and impact damage to the throttle control system components, including the power quadrant and cockpit control lever friction components, precluded determining the position of the throttle levers at the time of the loss of thrust or the friction setting during the accident flight. Thus, the reason for the reduction in thrust could not be determined definitively. In addition to a lack of callouts for checklists on the CVR, the pilots did not discuss any emergency procedures. As a result, they did not have a shared understanding of how to respond to the emergency of losing thrust in an engine during takeoff. Although the co-pilot verbally identified the loss of the left engine in response to the pilot’s confused reaction to the airplane’s performance shortly after takeoff, it is likely the co-pilot did not initiate any corrective flight control inputs, possibly due to the pilot’s established practice of being the sole operator of flight controls when passengers were on board. The investigation considered whether fatigue from inadequately treated obstructive sleep apnea contributed to the pilot’s response to the emergency; however, the extent of any fatigue could not be determined from the available evidence. In addition, no evidence indicates that the pilot’s medical conditions or their treatment were factors in the accident. In summary, the available evidence indicates that the pilot improperly responded to the loss of thrust in the left engine by initially commanding a left rudder input and did not retract the landing gear or feather the left propeller, which was not consistent with the airplane manufacturer’s engine out procedure during takeoff. It would have been possible to maintain directional and lateral control of the airplane after the thrust reduction in the left engine if right rudder had been commanded initially rather than left rudder. It is possible that the pilot’s reported habit of not using checklists resulted in his not checking or adjusting the power lever friction locks as specified in the airplane manufacturer’s checklists. However, fire and impact damage precluded determining the position of the power levers or friction setting during the flight.

During a cross-country flight, the pilot initiated a descent to his intended destination. During the descent, the pilot informed air traffic control (ATC) that he could not retard power on the right engine. Later in the descent, the pilot decided to shut down the right engine. The pilot communicated his desire to land at the nearest airport to ATC, and ATC provided the pilot with the clearance to divert. Radar data showed the airplane in a steady descent toward the airport. When the airplane was at an altitude of about 2,500 ft mean sea level, the pilot contacted ATC and stated that he was trying to get the airplane under control; radar data showed the airplane in a 360° right turn at the time. The pilot contacted ATC again and stated that he was going to land on a highway. No further transmissions were received from the pilot. After the right turn, the airplane continued in a descent through 1,300 ft mean sea level, at which point radar contact was lost. A witness saw the airplane and stated that the airplane was low and slow but appeared to be in stable flight with both propellers spinning. She did not see any smoke coming from the airplane. She saw the airplane flying northeast to southwest when it suddenly descended nose first into the ground. The airplane impacted a gravel road adjacent to a 100-fttall grain silo about 1 mile from the highway and about 3.3 miles from the airport.

The pilot departed on the cross-country flight with the airplane about 730 lbs over its maximum gross weight. While in cruise altitude at 27,000 ft mean sea level (msl), the pilot reported to air traffic control that he observed weather on his radar along his route and ahead of his position. The areas of weather included thunderstorms with cloud tops up to 43,000 ft msl. The controller acknowledged the weather; however, she did not provide specifics to the pilot, including the size and strength of the area of precipitation or cloud tops information, nor did she solicit or disseminate any pilot reports related to the conditions, as required. The airplane entered an area of heavy to extreme precipitation, likely a thunderstorm updraft, while in instrument meteorological conditions. Tracking information indicated that the airplane climbed about 300 ft, then entered a right, descending spiral and broke up in flight at high altitude. The recovered wreckage was found scattered along a path about 2.6 miles in length. Both wings separated, and most of the empennage was not located. The airplane was likely about 148 lbs over the maximum allowable gross weight at the time of the accident. Examination of the wreckage revealed no evidence of a pre accident malfunction or failure that would have prevented normal operation. The pilot, who owned the airplane, did not possess an instrument rating. The pilot-rated passenger in the right seat was instrument-rated but did not meet resency of experience requirements to act as pilot-in-command. Toxicology testing detected a small amount of ethanol in the pilot’s liver but not in muscle. After absorption, ethanol is uniformly distributed throughout all tissues and body fluids; therefore, the finding in one tissue but not another is most consistent with post-mortem production. Hazardous weather avoidance is ultimately the pilot’s responsibility, and, in this case, the airplane was sufficiently equipped to provide a qualified pilot with the information necessary to navigate hazardous weather; however, the controller’s failure to provide the pilot with adequate and timely weather information as required by Federal Aviation Administration Order JO 7110.65X contributed to the pilot’s inability to safely navigate the hazardous weather along his route of flight, resulting in the penetration of a thunderstorm and the resulting loss of airplane control and inflight breakup.

The pilot was conducting a personal cross-country flight in a turbofan-powered airplane. Shortly after departure, the airplane entered a witness-estimated 90° left bank with the nose parallel to the horizon; as the airplane began to roll out of the turn, the nose remained at or below the horizon before it dropped and the airplane impacted the ground. Flight track data revealed that, shortly after departure, the airplane's ground speed immediately began decreasing from its maximum of 141 knots during takeoff and continued decreasing until the last recorded data point, which showed that the airplane had a ground speed of 100 knots. The surface wind reported about 10 minutes before the accident was from 170° at 9 knots, gusting to 14 knots, which resulted in a 1- to 2-knot tailwind component. Given this information and the airplane's configuration at the time of the accident, the airplane's indicated airspeed (IAS) would have been between about 86 and 93 knots. The airplane's stall speed was calculated to be 100 knots IAS (KIAS) with a bank angle of 45° and 118 KIAS with a bank angle of 60°. Thus, the pilot failed to maintain airspeed or accelerate after departure, which resulted in an aerodynamic stall A pilot who had flown with the accident pilot twice before the accident reported that, during these flights, the pilot had flown at reduced power settings and slower-than-normal airspeeds. During the flight 1 year before the accident, he reached over and pushed the power levers forward himself. He also stated that every time he had flown with the pilot, he was "very behind the airplane." Postaccident examination of the engines revealed no signs of preimpact mechanical failures or malfunctions that would have precluded normal operation, and both engines exhibited circumferential rub marks on all rotating stages, blade tip bending opposite the direction of rotation, and debris ingestion through the gas path, indicating that the engine had power at impact. Further, the right engine full authority digital electronic control (FADEC) nonvolatile memory recorded no faults. (The left engine FADEC could not be downloaded due to damage.) The Airplane Flight Manual stated that the pilot must, in part, advance the throttle lever to the maximum takeoff detent for the FADEC's nonvolatile memory to record a logic trend snapshot 2 seconds after takeoff. The lack of a FADEC logic trend snapshot is consistent with the pilot not fully advancing the throttles during the takeoff and initial climb and is likely why he did not attain or maintain sufficient airspeed. The flight track data, pilot witness account, and airplane damage are consistent with the pilot failing to fully advance the power levers while maneuvering shortly after takeoff, which led to his failure to maintain sufficient airspeed and resulted in the exceedance of the airplane's critical angle of attack and a subsequent aerodynamic stall.

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.