Crash of a Cessna 404 Titan in Lockhart River: 5 killed

Date & Time: Mar 11, 2020 at 0919 LT
Type of aircraft:
Registration:
VH-OZO
Survivors:
No
Schedule:
Cairns – Lockhart River
MSN:
404-0653
YOM:
1980
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
3220
Captain / Total hours on type:
399.00
Circumstances:
On 11 March 2020, a Cessna 404 aircraft, registered VH-OZO, was being operated by Air Connect Australia to conduct a passenger charter flight from Cairns to Lockhart River, Queensland. On board were the pilot and 4 passengers, and the flight was being conducted under the instrument flight rules (IFR). Consistent with the forecast, there were areas of cloud and rain that significantly reduced visibility at Lockhart River Airport. On descent, the pilot obtained the latest weather information from the airport’s automated weather information system (AWIS) and soon after commenced an area navigation (RNAV) global satellite system (GNSS) instrument approach to runway 30. The pilot conducted the first approach consistent with the recommended (3°) constant descent profile, and the aircraft kept descending through the minimum descent altitude (MDA) of 730 ft and passed the missed approach point (MAPt). At about 400 ft, the pilot commenced a missed approach. After conducting the missed approach, the pilot immediately commenced a second RNAV GNSS approach to runway 30. During this approach, the pilot commenced descent from 3,500 ft about 2.7 NM prior to the intermediate fix (or 12.7 NM prior to the MAPt). The descent was flown at about a normal 3° flight path, although about 1,000 ft below the recommended descent profile. While continuing on this descent profile, the aircraft descended below the MDA. It then kept descending until it collided with terrain 6.4 km (3.5 NM) short of the runway. The pilot and 4 passengers were fatally injured, and the aircraft was destroyed.
Probable cause:
The accident was the consequence of a controlled flight into terrain.
The following contributing factors were identified:
• While the pilot was operating in the vicinity of Lockhart River Airport, there were areas of cloud and rain that significantly reduced visibility and increased the risk of controlled flight into terrain.
In particular, the aircraft probably entered areas of significantly reduced visibility during the second approach.
• After an area navigation (RNAV) global satellite system (GNSS) approach to runway 30 and missed approach, the pilot immediately conducted another approach to the same runway that was on a similar gradient to the recommended descent profile but displaced about 1,000 ft below that profile. While continuing on this descent profile, the aircraft descended below a segment minimum safe altitude and the minimum descent altitude, then kept descending until the collision with terrain about 6 km before the runway threshold.
• Although the exact reasons for the aircraft being significantly below the recommended descent profile and the continued descent below the minimum descent altitude could not be determined, it was evident that the pilot did not effectively monitor the aircraft’s altitude and descent rate for an extended period.
• When passing the final approach fix (FAF), the aircraft’s lateral position was at about full-scale deflection on the course deviation indicator (CDI), and it then exceeded full-scale deflection for
an extended period. In accordance with the operator’s stabilized approach procedures, a missed approach should have been conducted if the aircraft exceeded half full-scale deflection at the FAF, however a missed approach was not conducted.
• The pilot was probably experiencing a very high workload during periods of the second approach. In addition to the normal high workload associated with a single pilot hand flying an approach in instrument meteorological conditions, the pilot’s workload was elevated due to conducting an immediate entry into the second approach, conducting the approach in a different manner to their normal method, the need to correct lateral tracking deviations throughout the approach, and higher than appropriate speeds in the final approach segment.
• The aircraft was not fitted with a terrain avoidance and warning system (TAWS). Such a system would have provided visual and aural alerts to the pilot of the approaching terrain for an extended period, reducing the risk of controlled flight into terrain.
• Although the aircraft was fitted with a GPS/navigational system suitable for an area navigation (RNAV) global satellite system (GNSS) approach and other non-precision approaches, it was not fitted with a system that provided vertical guidance information, which would have explicitly indicated that the aircraft was well below the recommended descent profile. Although the operator had specified a flight profile for a straight-in approaches and stabilized approach criteria in its operations manual, and encouraged the use of stabilized approaches, there were limitations with the design of these procedures. In addition, there were limitations with other risk controls for minimizing the risk of controlled flight into terrain (CFIT), including no procedures or guidance for the use of the terrain awareness function on the aircraft’s GNS 430W GPS/navigational units and limited monitoring of the conduct of line operations.

Other factors that increased risk:
• Although an applicable height of 1,000 ft for stabilized approach criteria in instrument meteorological conditions has been widely recommended by organizations such as the International Civil Aviation Organization for over 20 years, the Civil Aviation Safety Authority had not provided formal guidance information to Australian operators regarding the content of stabilized approach criteria. (Safety issue)
• The Australian requirements for installing a terrain avoidance and warning system (TAWS) were less than those of other comparable countries for some types of small aeroplanes conducting air transport operations, and the requirements were not consistent with International Civil Aviation Organization (ICAO) standards and recommended practices. More specifically, although there was a TAWS requirement in Australia for turbine-engine aeroplanes carrying 10 or more passengers under the instrument flight rules:
- There was no requirement for piston-engine aeroplanes to be fitted with a TAWS, even though this was an ICAO standard for such aeroplanes authorized to carry 10 or more passengers, and this standard had been adopted as a requirement in many comparable countries.
- There was no requirement for turbine-engine aeroplanes authorized to carry 6–9 passengers to be fitted with a TAWS, even though this had been an ICAO recommended practice since 2007, and this recommended practice had been adopted as a requirement in many comparable countries. (Safety Issue)

Other findings:
• The forecast weather at Lockhart River for the time of the aircraft’s arrival required the pilot to plan for 60 minutes holding or diversion to an alternate aerodrome. The aircraft had sufficient fuel for that purpose; and the aircraft had sufficient fuel to conduct the flight from Cairns to Lockhart River and return, with additional fuel for holding on both sectors if required.
• There was no evidence of any organizational or commercial pressure to conduct the flight to Lockhart River or to complete the flight once to commenced.
• Based on the available evidence, it is very unlikely that the pilot was incapacitated or impaired during the flight.
• There was no evidence of any aircraft system or mechanical anomalies that would have directly influenced the accident. However, as a consequence of extensive aircraft damage, it was not possible to be conclusive about the aircraft’s serviceability.
• The aircraft was fitted with Garmin GNS 430W GPS/navigational units that could be configured to provide visual (but not aural) terrain alerts. However, it could not be determined whether the
terrain awareness function was selected on during the accident flight.
Final Report:

Crash of a Cessna 208B Super Cargomaster in Rhinelander

Date & Time: Mar 5, 2020 at 0815 LT
Type of aircraft:
Operator:
Registration:
N706FX
Flight Type:
Survivors:
Yes
Schedule:
Milwaukee – Rhinelander
MSN:
208B-0426
YOM:
1995
Flight number:
FDX8312
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7245
Captain / Total hours on type:
3684.00
Aircraft flight hours:
11458
Circumstances:
The pilot reported that, upon reaching the decision altitude on a GPS instrument approach, he saw the runway end identifier lights and continued the approach. Shortly after, the lights disappeared and then reappeared. He continued the approach and landing thinking the airplane was lined up with the runway by using the runway edge lights for reference. Upon touching down about 225 ft left of the runway, the airplane dug into snow and flipped over, which resulted in substantial damage to the wings and tail. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause:
The pilot's improper decision to continue an instrument approach to landing following a loss of visual reference with the runway, which resulted in the airplane touching down left of the runway in snow and flipping over.
Final Report:

Crash of a PZL-Mielec AN-2P in Ust-Kamenogorsk

Date & Time: Feb 26, 2020 at 1226 LT
Type of aircraft:
Operator:
Registration:
UP-A0001
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Ust-Kamenogorsk - Aksuat
MSN:
1G140-49
YOM:
1972
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single engine airplane departed Ust-Kamenogorsk Airport on an ambulance flight to Aksuat. After takeoff, while in initial climb, the crew encountered engine problems. They elected to make an emergency in a snow covered field. The airplane came to rest upside down, bursting into flames. All five occupants escaped with minor injuries while the aircraft was destroyed.

Crash of a Learjet 55 Longhorn in Monmouth

Date & Time: Feb 25, 2020 at 2356 LT
Type of aircraft:
Registration:
N135LR
Survivors:
Yes
Schedule:
Richmond – Monmouth
MSN:
55-068
YOM:
1982
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
18288
Captain / Total hours on type:
2909.00
Copilot / Total flying hours:
14759
Copilot / Total hours on type:
1978
Aircraft flight hours:
12792
Circumstances:
The pilot reported that he and the copilot were conducting an instrument approach to the runway in a business jet. He noted that the weather conditions included fog and mist. After touching down about 1,500 ft down the 7,300-ft-long runway, he engaged the thrust reversers and applied the brakes gradually because the runway was "slippery." As the airplane approached the end of the runway, he applied full braking, but the airplane departed the end of the runway and impacted a ditch, which resulted in the forward landing gear breaking and the airplane nosing down. The copilot corroborated the pilot's statement. The fuselage was substantially damaged. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause:
The flight crew's failure to stop the airplane on the available runway, which was wet and resulted in the airplane impacting a ditch.
Final Report:

Crash of a Piper PA-60 Aerostar (Ted Smith 602P) in Pamplona: 1 killed

Date & Time: Feb 20, 2020 at 1819 LT
Operator:
Registration:
EC-HRJ
Flight Type:
Survivors:
No
Schedule:
Sabadell - Pamplona
MSN:
62P-0897-8165027
YOM:
1981
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Aircraft flight hours:
3049
Circumstances:
On Thursday, 20 February 2020, the Piper PA-60-602P aircraft, with registration EC-HRJ, took off from Sabadell Airport (LELL) bound for Pamplona Airport (LEPP). At 17:51:43 hours local time, when the aircraft was in the vicinity of the SURCO waypoint, a sudden change in course from 300º to 317º was observed on the aircraft's radar trace. Moments later, at 17:53:12, the pilot of the aircraft contacted the Madrid air control units to report problems with one of his engines, adding verbatim: “I’m not sure if I’ve lost the turbo”. In a subsequent communication with the same air traffic controller, at 17:57:22 h, the pilot stated: "I’ve lost an engine”. At 17:57:58 h, the pilot contacted the controller of the Pamplona control tower. The controller asked him if he required any assistance, and the pilot replied that he did not. At 18:16:15 h, the pilot told the control tower controller that he was on right base for runway 33. The controller cleared him to land and asked him to notify him when he was on final. At 18:19:40 h, the control tower controller alerted the airport Fire Extinguishing Service (SEI) when he saw the aircraft crash and a column of smoke coming from the wreckage area. The aircraft had impacted the ground during the final approach manoeuvre. As it fell, it hit and severed a power line. The pilot, who was the sole occupant of the aircraft, was killed during the accident. The impact and subsequent fire completely destroyed the aircraft.
Probable cause:
The investigation concluded the probable cause of the accident was that the aircraft lost control on final approach to runway 33 as a result of flying with asymmetrical power.
Final Report:

Crash of a Cessna 510 Citation Mustang in Daytona Beach

Date & Time: Feb 20, 2020 at 1245 LT
Operator:
Registration:
N163TC
Flight Type:
Survivors:
Yes
Schedule:
Daytona Beach - Daytona Beach
MSN:
510-0039
YOM:
2007
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2533
Captain / Total hours on type:
90.00
Copilot / Total flying hours:
7500
Aircraft flight hours:
2380
Circumstances:
The pilot was receiving a checkride from a designated pilot examiner for his single-pilot type rating in a turbine airplane. After a series of maneuvers, emergencies, and landings, the examiner asked the pilot to complete a no-flap landing. The pilot reported that he performed the Before Landing checklist with no flaps and believed that he had put the gear down. During touchdown, the pilot felt a "thump" and thought a tire had blown; however, he saw that the landing gear handle was in the "up" position, and he noted that the landing gear warning horn did not sound because he had performed a no-flaps landing. The examiner confirmed that the landing gear handle was in the "up" position. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. A Federal Aviation Administration inspector who examined the airplane reported that the landing gear handle was in the "up" position and that the fuselage had sustained substantial damage. The landing gear was lowered and locked into place without issue after the airplane was lifted from the runway.
Probable cause:
The pilot's failure to lower the landing gear before landing. Contributing to the accident was the examiner's failure to check that the landing gear was extended.
Final Report:

Crash of a PZL-Mielec AN-2R in Magadan

Date & Time: Feb 20, 2020 at 1032 LT
Type of aircraft:
Operator:
Registration:
RA-40642
Flight Phase:
Survivors:
Yes
Schedule:
Magadan – Seymchan
MSN:
1G213-49
YOM:
1985
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
12
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8750
Captain / Total hours on type:
4543.00
Copilot / Total flying hours:
3865
Copilot / Total hours on type:
3865
Aircraft flight hours:
14822
Circumstances:
The single engine airplane, operated by T-Cement, was engaged in a charter flight from Magadan to Seymchan, carrying 12 pilots and 12 mining employees of the company and their 445 kilos of luggages and personal stuffs. After takeoff from the snowy runway 01, while climbing to a height of 10 metres, the aircraft entered a nose-up attitude while its speed dropped. At a height of about 30 metres, the angle of attack increased to 24° and the speed dropped to 65 km/h, causing the aircraft to stall and to crash in a snow covered field, some 240 metres past the runway end. All 14 occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
The aircraft stalled during initial climb because its total weight was above the MTOW and the CofG was well beyond the aft limit. The crew failed to prepare the flight according to procedure and, failed to proceed with a mass and balance calculation and the passengers and lugages were incorrectly placed in the cabin according to the CofG.
Final Report:

Crash of a Piper PA-31-310 Navajo in Bogotá: 4 killed

Date & Time: Feb 12, 2020 at 1544 LT
Type of aircraft:
Operator:
Registration:
HK-4686
Flight Phase:
Survivors:
No
Schedule:
Bogotá – Villagarzón
MSN:
31-344
YOM:
1968
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
1890
Captain / Total hours on type:
250.00
Copilot / Total flying hours:
646
Aircraft flight hours:
10251
Circumstances:
Shortly after takeoff from Bogotá-Guaymaral Airport, while in initial climb, the crew informed ATC about the failure of the right engine. He was cleared to return for an emergency and completed a circuit to land on ruwnay 11. On final, the airplane lost height and crashed in a wooded area located about 800 metres short of runway, bursting into flames. The aircraft was destroyed by a post crash fire and all four occupants were killed.
Probable cause:
The investigation determined that the accident was caused by the following probable cause(s):
- Loss of in-flight control as a result of slowing below Minimum Control Speed and drag, generated by the failure of the right engine (No. 2).
- Failure of engine No. 2, due to lack of lubrication, possibly caused by oil leakage through an 11.5 mm fracture, found in one of the sides of cylinder No. 2 at the height of the intake valves.
- Inappropriate application by the crew of the emergency procedure for landing with an inoperative engine, by not declaring the emergency, not feathering the propeller of the inoperative engine and configuring the aircraft early for landing (with landing gear and flaps) without having a safe runway, making it difficult to control the aircraft and placing it in a condition of loss of lift and control.

Contributing Factors:
- Failure of the operator to emphasize in the crew training program the techniques and procedures to be followed in the event of engine failure, among others, the declaration of emergency to ATC, the flagging of the propeller of the inoperative engine, the care in the application of power to the good engine so as not to increase yaw and not to configure the aircraft until landing has been assured.
- Lack of emergency calls by the crew, which denotes deficiencies in the Operator's Safety Management System, and which prevented the early warning of the aerodrome support services and deprived the crew of possible assistance from other aircraft or from the same operator.
Final Report:

Crash of a Boeing 737-524 in Usinsk

Date & Time: Feb 9, 2020 at 1227 LT
Type of aircraft:
Operator:
Registration:
VQ-BPS
Survivors:
Yes
Schedule:
Moscow - Usinsk
MSN:
28909/2960
YOM:
1997
Flight number:
UT595
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
94
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
17852
Captain / Total hours on type:
7672.00
Copilot / Total flying hours:
6595
Copilot / Total hours on type:
4989
Aircraft flight hours:
57410
Aircraft flight cycles:
29162
Circumstances:
Following an uneventful flight from Moscow-Vnukovo Airport, the crew initiated the descent to Usinsk Airport Runway 13. On short final, the aircraft hit a snow bank (1,1 metre high) located 32 metres short of runway threshold, still on the concrete zone. Upon impact, both main gears were torn off and the airplane belly landed and slid for few hundred metres before coming to rest. All 100 occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
The accident with the Boeing 737-500 VQ-BPS aircraft occurred during the landing as a result of a collision of the aircraft with a snow parapet 1.1 m high at a distance of 32 m to the runway threshold (within the paved section of the runway), which resulted in damage to the main landing gear and their subsequent "folding" in the process of moving along the runway.
The accident was caused by a combination of the following factors:
- the presence of contradictions in the Federal Aviation Rules for flights in the airspace of the Russian Federation, the airline's radio control system and the aircraft operational documentation regarding the need and procedure for introducing temperature corrections to the readings of barometric altimeters at low ambient temperatures;
- Failure by the operator of the Usinsk aerodrome to comply with the FAP-262 requirements for the maintenance of the aerodrome, which resulted in the presence of snow parapets on the paved section of the landing strip;
- the operator of the Usinsk aerodrome did not eliminate the shortcomings in the winter maintenance of the aerodrome, noted based on the results of the inspection by the Rosaviatsia commission on January 22, 2020;
- lack of risk assessment in the airline associated with the execution of approaches in the baro-VNAV mode in the presence of factors that impede such approaches (low ambient temperatures, snow-covered underlying surface, drifting snow (snowstorm), significant changes in the relief in front of the runway end, lack of PAPI-type lights), as well as appropriate recommendations to the crews on the specifics of such approaches, including after the transition to visual flight, and crew training;
- insufficient assessment by the crew during the preparation of the existing threats (hazard factors) and making an insufficiently substantiated decision to perform an RNAV (GNSS) approach (under the control of the autopilot in LNAV/VNAV mode) without introducing a correction for low outside air temperature in altitude overflying waypoints, which led to a flight below the established glide path;
- performing a flight along the "extended glide path" after turning off the autopilot and switching to manual piloting without attempting to enter the set glide path;
- the PIC may have had a visual illusion of a "high glide path" due to a snow-covered underlying surface, a snowstorm and the presence of a ravine directly in front of the runway end in the absence of PAPI type lights, which led to an incorrect assessment of the aircraft's flight altitude after switching to manual piloting, lack of reaction to timely and correct warnings of the co-pilot and exit to the runway end at a height significantly less than the established one.
Final Report:

Crash of a Being 737-86J in Istanbul: 3 killed

Date & Time: Feb 5, 2020 at 1820 LT
Type of aircraft:
Operator:
Registration:
TC-IZK
Survivors:
Yes
Schedule:
Izmir - Istanbul
MSN:
37742
YOM:
2009
Flight number:
PC2193
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
177
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
Following an uneventful flight from Izmir-Adnan Menderes Airport, the crew initiated the approach to Istanbul-Sabiha Gökçen Airport runway 06. Weather conditions were poor with thunderstorm activity, rain, CB's and a wind from 290 gusting to 37 knots. After touchdown on a wet runway, the airplane was unable to stop within the remaining distance. It overran, turned slightly to the left then went down an embankment (25 meters high) and came to rest, broken in three. Three passengers were killed while all 180 other occupants were evacuated to local hospitals. It is understood that the airplane apparently landed 1,500 meters past the runway threshold (runway 06 is 3,000 meters long) with a non negligible tailwind component that must be confirmed.