Landing (descent or approach)

On final approach to Charallave-Óscar Machado Zuloaga Airport in marginal weather conditions, the twin engine airplane crashed in unknown circumstances about 8 km from the runway threshold. The aircraft was destroyed and all nine occupants were killed.

On 09 December 2019, a private Piper Aerostar PA-60-602P aircraft (registration C-FQYW, serial number 60-8265020), departed Cabo San Lucas International Airport (MMSL), Baja California Sur, Mexico, with 3 people on board, for a 2-day trip to Nanaimo Airport (CYCD), British Columbia (BC). As planned the aircraft stopped for an overnight rest at Chino Airport (KCNO), California, U.S. At 1142, on 10 December 2019, the aircraft departed KCNO on a visual flight rules (VFR) flight plan to Bishop Airport (KBIH), California, U.S., for a planned fuel stop. The aircraft departed KBIH at approximately 1425 on an instrument flight rules (IFR) flight plan to CYCD. On 10 December 2019, night started at 1654. At 1741, the Vancouver area control centre air traffic controller advised the pilot that an aerodrome special meteorological report (SPECI) had been issued for CYCD at 1731. The SPECI reported visibility as 2 ½ statute miles (SM) in light drizzle and mist, with an overcast ceiling of 400 feet above ground level (AGL). The pilot informed the controller that he would be conducting an instrument landing system (ILS) approach for Runway 16. At 1749, when the aircraft was approximately 32 nautical miles (NM) south of CYCD, the pilot contacted the controller to inquire about the weather conditions at Victoria International Airport (CYYJ), BC. The controller informed the pilot that a SPECI was issued for CYYJ at 1709 and it reported the visibility as 5 SM in mist, a broken ceiling at 600 feet AGL, and an overcast layer at 1200 feet AGL. The controller provided the occurrence flight with pilot observations from another aircraft that had landed at CYCD approximately 15 minutes before. That crew had reported being able to see the Runway 16 approach lights at minimums, i.e., at 373 feet AGL. Between 1753 and 1802, the controller provided vectors to the pilot in order to intercept the ILS localizer. At 1803, the controller observed that the aircraft had not intercepted the localizer for Runway 16. The aircraft had continued to the southwest, past the localizer, at an altitude of 2100 feet above sea level (ASL) and a ground speed of 140 knots. The controller queried the pilot to confirm that he was still planning to intercept the ILS for Runway 16. The pilot confirmed that he would be intercepting the ILS as planned. The aircraft made a heading correction and momentarily lined up with the localizer before beginning a turn to the west. At 1804:03, the pilot requested vectors from the controller and informed him that he “just had a fail.” The controller responded with instructions to “turn left heading zero nine zero, tight left turn.” The pilot asked the controller to repeat the heading. The controller responded with instructions to “…turn right heading three six zero.” The pilot acknowledged the heading; however, the aircraft continued turning right beyond the assigned heading while climbing to 2500 feet ASL and slowing to a ground speed of 80 knots. The aircraft then began to descend, picking up speed as it was losing altitude. At 1804:33, the aircraft descended to 1800 feet ASL and reached a ground speed of 160 knots. At 1804:40, the pilot informed the air traffic controller that the aircraft had lost its attitude indicator.Footnote6 At the same time, the aircraft was climbing into a 2nd right turn. At 1804:44, the air traffic controller asked the pilot what he needed from him; the pilot replied he needed a heading. The controller provided the pilot with a heading of three six zero. At 1804:47, the aircraft reached an altitude of 2700 feet ASL and a ground speed of 60 knots. The aircraft continued its right turn and began to lose altitude. The controller instructed the pilot to gain altitude if he was able to; however, the pilot did not acknowledge the instruction. The last encoded radar return for the aircraft was at 1805:26, when the aircraft was at 300 feet ASL and travelling at a ground speed of 120 knotsControl of the aircraft was lost. The aircraft collided with a power pole and trees in a wooded park area on Gabriola Island, BC, and then impacted the ground. The aircraft broke into pieces and caught fire. The 3 occupants on board received fatal injuries. As a result of being damaged in the accident, the emergency locator transmitter (Artex ME406, serial number 188-00293) did not activate.

The airplane was engaged in an illegal flight and its crew attempted to land in a bush area located in San Andrés Villa Seca. No one was found on site and the aircraft was damaged beyond repair. It is unclear if the registration is illegal or the original one.

The twin engine aircraft crashed in unknown circumstances in a pasture located near Saint Jean, Haiti. There were no casualties while the aircraft was damaged beyond repair. It was engaged in an illegal flight (contraband) and the registration XB-PYB is false. Local authorities were looking for both Mexican pilots and a local involved in the illegal mission.

On November 21, 2019, a regular THY2UT flight en-route Istanbul – Odesa at B737-800 aircraft, nationality and registration mark TC-JGZ of the Turkish Airlines, was performed by the aircraft crew consisting of the Pilot-in-Command (PIC), co-pilot and four flight attendants of the aircraft. In fact, the departure from Istanbul Airport was performed at 17:33. The actual aircraft landing took place at 18:55. According to the flight plan, the alternate aerodromes were Istanbul and Chișinău. There were 136 passengers and 2793 kg of luggage on board the aircraft. The PIC was a Pilot Flying, and the co-pilot was a Pilot Monitoring of the aircraft. The pre-flight briefing of the crew, according to its explanations, was carried out before departure from the Istanbul Airport, after which the PIC took the decision to perform the flight. The climb and level flight were performed in the normal mode. The landing approach was performed to the Runway16 with ILS system at a significant crosswind component of variable directions. At the final stage of approaching with ILS to Runway 16, the ATC controller of the aerodrome control tower (ATC Tower) gave the aircraft crew a clearance for landing. The aircraft crew confirmed the controller’s clearance and continued the landing approach. Subsequently, from a height of about 50 meters, the aircraft performed a go-around due to the aircraft non-stabilization before landing. Following the go-around, the aircraft headed to the holding area to wait for favorable values of wind force and direction. At 18:45, the PIC took the decision to carry out a repeated landing approach, reported of that to the ATC controller, who provided ATS in the Odesa Terminal Maneuvering Area (TMA.) At 18:51, the crew re-contacted the Tower controller and received the clearance to land. At 18:55, after touchdown, during the runway run, the aircraft began to deviate to the left and veered off of the runway to the left onto the cleared and graded area. After 550 m run on the soil, the aircraft returned to the runway with its right main landing gear and nose part (while moving on the soil, the nose landing gear collapsed) and came to rest at the distance of 1612 m from the runway entrance threshold. The crew performed an emergency evacuation of passengers from the aircraft. As a result of the accident, the aircraft suffered a significant damage to the nose part of the fuselage and left engine. None of the passengers or crew members was injured.

The aircraft took off from the Comandante Rolim Adolfo Amaro Aerodrome (SBJD), Jundiaí - SP, to the Barra Grande Aerodrome (SIRI), Maraú - BA, at about 1458 (UTC), in order to carry out a private flight, with two pilots and eight passengers on board. Upon arriving at the destination Aerodrome, at 1717 (UTC), the aircraft made an undershoot landing on runway 11, causing the main and auxiliary landing gear to burst. The airplane moved along the runway, dragging the lower fuselage and the lower wing, leaving the runway by its left side, and stopping with the heading lagged, approximately, 210º in relation to the landing trajectory. Afterwards, there was a fire that consumed most of the aircraft. The aircraft was destroyed. One crewmember and four passengers suffered fatal injuries and the other crewmember and four passengers suffered serious injuries.

The pilot was conducting a GPS circling instrument approach in instrument meteorological conditions to an airport with which he was familiar. During the final minute of the flight, the airplane descended to and leveled off near the minimum descent altitude (MDA) of about 600 ft mean sea level (msl). During this time, the airplane’s groundspeed slowed from about 90 knots to a low of 65 knots. In the few seconds after reaching 65 knots groundspeed, the flight track abruptly turned left off course and the airplane rapidly descended. The final radar point was recorded at 200 ft msl less than 1/10 mile from the accident site. Two home surveillance cameras captured the final few seconds of the flight. The first showed the airplane in a shallow left bank that rapidly increased until the airplane descended in a steep left bank out of camera view below a line of trees. The second video captured the final 4 seconds of the flight; the airplane entered the camera view already in a steep left bank near treetop level, and continued to roll to the left, descending out of view. Both videos showed the airplane flying below an overcast cloud ceiling, and engine noise was audible until the sound of impact. Postaccident examination of the airplane revealed no evidence of preimpact mechanical malfunctions that would have precluded normal operation. The propeller signatures, witness impact marks, audio recordings, and witness statements were all consistent with the engines producing power at the time of impact. The pilot likely encountered restricted visibility of about 2 statute miles with mist and ceilings about 700 ft msl. When the airplane deviated from the final approach course and descended below the MDA, the destination airport remained 3.5 statute miles to the northeast. Although the airplane was observed to be flying below the overcast cloud layer, given the restricted visibility, it is likely that the pilot was unable to visually identify the airport or runway environment at any point during the approach. According to airplane flight manual supplements, the stall speed likely varied from 76 to 67 knots indicated airspeed. The exact weight and balance and configuration of the airplane could not be determined. Based upon surveillance video, witness accounts, and automatic dependent surveillance-broadcast data, it is likely that, as the pilot leveled off the airplane near the MDA, the airspeed decayed below the aerodynamic stall speed, and the airplane entered an aerodynamic stall and spin from which the pilot was unable to recover. Based on a readout of the pilot’s cardiac monitoring device and autopsy findings, while the pilot had a remote history of arrhythmia, sudden incapacitation was not a factor in this accident. Autopsy findings suggested that the pilot’s traumatic injuries were not immediately fatal; soot material in both the upper and lower airways provided evidence that the pilot inhaled smoke. This autopsy evidence supports that the pilot’s elevated carboxyhemoglobin level was from smoke inhalation during the postcrash fire. In addition, there were no distress calls received from the pilot and there was no evidence found that would indicate there was an in-flight fire. Thus, carbon monoxide exposure, as determined by the carboxyhemoglobin level, was not a contributing factor to the accident.

At approximately 0745 Central Daylight Time on 26 October 2019, the Blue Water Aviation float-equipped deHavillandDHC-3 Otteraircraft (registration C-GBTU, serial number 209) departed Bissett Water Aerodrome, Manitoba, with the pilot, 2 passengers, and approximately 800 pounds of freight on board. The destination was Little Grand Rapids, Manitoba, on the eastern shore of Family Lake. At approximately 0845, while on approach to Family Lake, the aircraft’s right wing separated from the fuselage. The aircraft then entered a nose-down attitudeand struck the water surface of the lake. The pilot and the 2 passengers were fatally injured. The aircraft was destroyed by impact forces. The emergency locator transmitter activated momentarily.

On the 18th October 2019, at approximately 4:30 PM local time, a Douglas DC-3C aircraft, registration N437GB crashed in the ocean; at coordinates 25°05.55N 077°30.29W, approximately 2.87miles from Runway 14 at the Lynden Pindling International Airport (MYNN) Nassau, Bahamas. There were 2 souls on board. The pilot reported that the left engine failed approximately 25-30 nautical miles from MYNN. The pilot further stated that during single engine operation, the aircraft performance was not optimal so the decision was made to land the aircraft in the ocean. The Air Traffic Control tower was notified by the crew of N437GB, that they will be performing a control water landing. The Royal Bahamas Defense Force was notified. Rescue efforts were then put into place. No injuries were received by the occupants of the aircraft. Aircraft could not be located for physical analysis to be carried out. The weather at the time of the accident was visual meteorological conditions and not a factor in this accident. A limited scope investigation was conducted, no safety message or recommendations were issued.

On October 17, 2019, a Saab SA-2000 airplane, operated by Peninsula Aviation Services Inc. d.b.a. PenAir flight 3296, overran the end of runway 13 at Unalaska Airport (DUT), Unalaska, Alaska. The flight crew executed a go-around during the first approach to runway 13; the airplane then entered the traffic pattern for a second landing attempt on the same runway. Shortly before landing, the flight crew learned that the wind at midfield was from 300° at 24 knots, indicating that a significant tailwind would be present during the landing. Because an airplane requires more runway length to decelerate and stop when a tailwind is present during landing, a landing in the opposite direction (on runway 31) would have favored the wind at the time. However, the flight crew continued with the plan to land on runway 13. Our postaccident calculations showed that, when the airplane touched down on the runway, the tailwind was 15 knots. The captain reported after the accident that the initial braking action after touchdown was normal but that, as the airplane traveled down the runway, the airplane had “zero braking” despite the application of maximum brakes. The airplane subsequently overran the end of the runway and the adjacent 300-ft runway safety area (RSA), which was designed to reduce airplane damage during an overrun, and came to rest beyond the airport property. The airplane was substantially damaged during the runway overrun; as a result, of the 3 crewmembers and 39 passengers aboard, 1 passenger sustained fatal injuries, and 1 passenger sustained serious injuries. Eight passengers sustained minor injuries, most of which occurred during the evacuation. The crewmembers and 29 passengers were not injured.