Crash of a Cessna 525C CitationJet CJ4 in Howell

Date & Time: Jan 16, 2017 at 1159 LT
Type of aircraft:
Registration:
N525PZ
Flight Type:
Survivors:
Yes
Schedule:
Batavia – Howell
MSN:
525C-0196
YOM:
2015
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5800
Captain / Total hours on type:
320.00
Aircraft flight hours:
320
Circumstances:
After exiting the clouds during the landing approach at the uncontrolled airport, the private pilot of the small jet canceled his instrument flight plan with air traffic control. He stated that, although there was no precipitation when he exited the clouds, he suspected the runway may be icy due to the weather conditions. The pilot saw an airplane holding short on the taxiway at the end of the runway and assumed it was preparing to takeoff, which he stated led him to believe that the runway condition was good. Although the pilot announced his location and intentions on the airport's common traffic advisory frequency (CTAF), he did not inquire about the runway condition via CTAF/UNICOM. Witnesses reported that the approach looked normal. After touchdown, the pilot applied brakes and realized he had no braking action. He subsequently retracted the speed brakes, spoilers, and flaps, and added takeoff power. The airplane yawed to the left and the pilot reduced engine power to idle while applying rudder to correct the airplane's track. The airplane continued off the runway, where it traveled through a fence and across a road before coming to rest inverted. The pilot and mechanic seated in the airplane that was holding short of the runway during the landing reported that they were only taxiing to a maintenance facility and did not intend to take off. They reported that the taxiways were icy. A witness who assisted the pilot following the accident reported that the roads at the time were covered in ice and "very slick." Recorded data from the airplane showed that the pilot flew a stabilized approach and that the airplane touched down near the approach end of the runway; however, given the icy runway conditions, the airplane's landing distance required exceeded the available runway by more than 8,000 ft. Airport personnel had not issued a NOTAM regarding the icy runway conditions. The airport manager stated he was not at the airport at the time of the accident, and that he was still trying to learn the new digital NOTAM manager system. The employee who was at the airport was authorized to issue NOTAMs, but had not yet been trained on the new system.
Probable cause:
The pilot's attempted landing on the ice-covered runway, which resulted in a runway excursion and impact with terrain. Contributing to the accident was airport personnel's lack of training regarding issuance of NOTAMs
Final Report:

Crash of a Let L-410UVP in Shabunda

Date & Time: Jan 2, 2017 at 1220 LT
Type of aircraft:
Operator:
Registration:
9Q-CZR
Flight Type:
Survivors:
Yes
Schedule:
Bukavu – Shabunda
MSN:
85 13 36
YOM:
1985
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew, one Russian and one Congolese, was performing a cargo flight from Bukavu to Shabunda, carrying various goods for a total weight of 1,300 kilos. After touchdown, after a course of about 300 metres, it is believed that the tire on the right main gear burst. The aircraft veered off runway and eventually collided with banana trees. Both pilots were uninjured while the aircraft was damaged beyond repair.

Crash of a Reims/Cessna F406 Caravan II in Sasakwa

Date & Time: Jan 2, 2017
Type of aircraft:
Operator:
Registration:
5H-WOW
Flight Phase:
Survivors:
Yes
MSN:
406-0060
YOM:
1991
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
While taking off from runway 12/30 at Sasakwa Airfield, the twin engine aircraft went out of control and crashed, bursting into flames. All six occupants were injured, some seriously, and the aircraft burnt out.

Crash of a Piper PA-46-350P Malibu Mirage in Nashville

Date & Time: Dec 29, 2016 at 1345 LT
Operator:
Registration:
N301BK
Flight Type:
Survivors:
Yes
Schedule:
Memphis – Nashville
MSN:
46-36407
YOM:
2007
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1550
Captain / Total hours on type:
1092.00
Aircraft flight hours:
1332
Circumstances:
According to the pilot, during the landing roll, the airplane "began to drift sharply to the left." The pilot reported that, although there were no wind gusts reported, he felt as though a wind gust was pushing the airplane to the left. He attempted to maintain directional control with rudder pedal application, and he applied full right aileron. The airplane continued to drift to the left, and the pilot attempted to abort the landing by applying full throttle and 25° of flaps. He reported that the airplane continued to drift to the left and that he was not able to achieve sufficient airspeed to rotate. The airplane exited the runway, the pilot pulled the throttle to idle, and he applied the brakes to avoid obstacles. However, the airplane impacted the runway and taxiway signage and came to rest in a drainage culvert. The airplane sustained substantial damage to both wings. The published METAR for the accident airport reported that the wind was from 290° at 15 knots, and wind gusts exceeded 22 knots 1 hour before and 1 hour after the accident. The pilot landed the airplane on runway 20. The maximum demonstrated crosswind component for the airplane was 17 knots. 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 loss of directional control during the aborted landing in gusting crosswind conditions, which resulted in a runway excursion.
Final Report:

Crash of an ATR72-600 in Semarang

Date & Time: Dec 25, 2016 at 1824 LT
Type of aircraft:
Operator:
Registration:
PK-WGW
Survivors:
Yes
Schedule:
Bandung – Semarang
MSN:
1234
YOM:
2015
Flight number:
IW1896
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
68
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4065
Captain / Total hours on type:
3805.00
Copilot / Total flying hours:
3300
Copilot / Total hours on type:
3200
Aircraft flight hours:
3485
Aircraft flight cycles:
4104
Circumstances:
On 25 December 2016, an ATR 72-600 aircraft registered PK-WGW was being operated by PT. Wings Abadi Airlines (Wings Air) as a scheduled passenger flight from Husein Sastranegara International Airport (WICC), Bandung to Ahmad Yani International Airport (WAHS), Semarang with flight number WON 1896. On board the aircraft were two pilots, two flight attendants and 68 passengers. There was no report or record of aircraft system malfunction prior to the departure. The aircraft departed from Bandung at 1734 LT (1034 UTC). The Pilot in Command (PIC) acted as Pilot Flying (PF) and the Second in Command (SIC) acted as Pilot Monitoring (PM). The flight from departure until commenced for landing approach was uneventful. At 1112 UTC, at night condition, the air traffic controller of Semarang Approach unit (approach controller) informed to all traffic that the rain was falling over the airport and the pilot confirmed whether the rain was heavy and was replied that it was slight rain. At 1115 UTC, the flight held over waypoint KENDA for separation with another aircraft and maintained altitude of 4,000 feet. Two minutes later, the flight was approved to descend to altitude of 3,000 feet. At 1118 UTC, the approach controller issued clearance for RNAV approach to runway 13 and advised the pilot to report when leaving waypoint KENDA. One minute later, the pilot reported leaving waypoint KENDA and the approach controller instructed to continue approach and to contact to the air traffic controller of Semarang Tower unit (tower controller). At 1120 UTC, the pilot advised to the tower controller that the aircraft was on final and the runway was in sight. The tower controller instructed to continue the landing approach and advised that the surface wind direction was 190° with velocity of 15 knots, altimeter setting 1,008 mbs and the runway was wet. At 1121 UTC, the tower controller had visual contact to the aircraft and issued landing clearance, the pilot read back the clearance and requested to reduce the approach light intensity. The tower controller reduced the light intensity and confirmed whether the intensity was appropriate then the pilot affirmed. At 1124 UTC, the aircraft touched down and bounced. After the third bounce, the pilot attempted to go around and the aircraft touched the runway. The tower controller noticed that the red light on the right wing was lower than the green light on the left wing. The aircraft moved to the right from the runway centerline and stopped near taxiway D. The tower controller realized that the aircraft was not in normal condition and pressed the crass bell then informed the Airport Rescue and Fire Fighting (ARFF) personnel by phone that there was aircraft accident near the taxiway D. At 1126 UTC, the pilot advised the tower controller that the aircraft stopped on the runway and requested assistance. The tower controller acknowledged the message and advised the pilot to wait for the assistance. While waiting the assistance, the pilot kept the engines run to provide lighting in the cabin. At 1129 UTC, the tower controller advised the pilot to shut down the engines since the ARFF personnel had arrived near the aircraft to assist the evacuation. Passenger evacuation completed at approximately 10 minutes after the aircraft stopped.
Probable cause:
Contributing Factors:
- The visual illusion of aircraft higher than the real altitude resulted in late flare out which made the aircraft bounced.
- The unrecovered bounce resulted in abnormal landing attitude with vertical acceleration up to 6 g and collapsed the right main landing gear.
Final Report:

Crash of a Beechcraft B200T Super King Air at Butterworth AFB: 1 killed

Date & Time: Dec 21, 2016 at 1718 LT
Operator:
Registration:
M41-03
Flight Type:
Survivors:
Yes
Schedule:
Kuala Lumpur – Butterworth
MSN:
BT-37
YOM:
1993
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The crew was completing a training flight from Kuala Lumpur-Subang Airport when on final approach to Butterworth Airbase, the twin engine aircraft went out of control and crashed, coming to rest against the perimeter fence. The aircraft was partially destroyed by impact forces and one crew member was killed while three other occupants were injured. Weather conditions were considered as good at the time of the accident.

Crash of a Boeing 727-2J0F in Puerto Carreño: 5 killed

Date & Time: Dec 20, 2016 at 1722 LT
Type of aircraft:
Operator:
Registration:
HK-4544
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Puerto Carreño - Bogotá
MSN:
21105/1158
YOM:
1975
Flight number:
KRE157
Country:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
8708
Captain / Total hours on type:
6822.00
Copilot / Total flying hours:
3285
Copilot / Total hours on type:
3285
Aircraft flight hours:
60199
Circumstances:
The crew started the takeoff procedure at 1718LT from Puerto Carreño-Germán Olano Airport Runway 07 which is 1,800 metres long. Following a long takeoff roll, the pilot-in-command initiated the rotation when the aircraft overran then rolled for about 95 metres. It collided with two perimeter fences, passed through a road then lifted off. During initial climb, the right main gear was torn off after it collided with a tree and the engine n°3 failed. The airplane continued to climb to an altitude of 790 feet then entered a right turn and eventually crashed in an open field located 7,5 km from the airport, bursting into flames. The flight engineer was seriously injured while five other occupants were killed.
Probable cause:
The following findings were identified:
- Inadequate flight planning by the operator of the aircraft, and by the crew, by failure to properly perform dispatch procedures, takeoff performance calculations and verification of limitations imposed by operational conditions of the aerodrome according to the configuration of the aircraft.
- Wrong crew decision making by not considering a key aspect affecting aircraft performance, such as the prevailing tailwind at takeoff.
- Erroneous selection of takeoff speeds V1/VR and V2, by the crew, corresponding to an aircraft without modification in its flap system, which led to rotate the aircraft with five more knots of speed, increasing the takeoff run.
- Erroneous rotation technique applied by the Pilot, delayed maneuver that extended the long takeoff run even more.
- Loss of components (landing gear, trailing inboard flap right) and damage to functional systems (loss of engine power n°3 and hydraulic system) necessary to control the aircraft in flight.
- Loss of control in flight generated by asymmetries of lift, power and emptying of the main hydraulic systems that exceeded the capacity of the crew and made it impossible to maintain adequate directional control and stability of the aircraft.
Contributing Factors:
- Non-compliance with the Aeronautical Regulations by the operating company of the aircraft, operating to an aerodrome unsuitable for the operation of B727-200 equipment, which, in addition, was not authorized for that type of aircraft in the company's Operating Specifications, approved by the Aeronautical Authority.
- Lack of standardization and supervision of the operating company of the aircraft, allowing the operation of the B727-200 equipment, to which a modification had been applied to the flap system, with the reference tables of speeds corresponding to the aircraft without modification.
- Execution of take-off with a weight that exceeded the maximum value established in the aircraft performance charts for the conditions prevailing at the Germán Olano airport.
- Omission of the crew by not activating the Standby hydraulic system, which might have allowed emergency hydraulic pressure, to regain control of the aircraft.
- Lack of supervision by the Aeronautical Authority, which allowed for several years the operation of equipment B727-200 of the company operating the aircraft at the Germán Olano aerodrome in Puerto Carreño, when the characteristics of the aerodrome did not allow it and without the operator being authorized to operate equipment B727-200 in that aerodrome.
Final Report:

Crash of a Cessna (DMI) Falcon 402 in Lanseria

Date & Time: Dec 13, 2016 at 1530 LT
Type of aircraft:
Registration:
ZU-TVB
Flight Type:
Survivors:
Yes
Schedule:
Lanseria - Bazaruto Island
MSN:
402B-1008
YOM:
1975
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Lanseria Airport Runway 07, en route to Bazaruto Island in Mozambique, the pilot encountered engine problems. He contacted ATC and was cleared for an immediate return and landing on runway 25. On short final, the single engine airplane hit the perimeter fence and crashed near the runway threshold, bursting into flames. All three occupants were injured and the aircraft was destroyed by a post crash fire. Built in 1975, this Cessna 402B was equipped with a new turbo engine and redesigned as a single engine Cessna (DMI) Falcon 402 (the C402 is usually a twin engine aircraft).

Crash of a Beechcraft B200 Super King Air in Moomba

Date & Time: Dec 13, 2016 at 1251 LT
Operator:
Registration:
VH-MVL
Flight Type:
Survivors:
Yes
Schedule:
Innamincka – Moomba
MSN:
BB-1333
YOM:
1989
Flight number:
FD209
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On 13 December 2016, a Beech Aircraft Corporation B200, registered VH-MVL, conducted a medical services flight from Innamincka, South Australia (SA) to Moomba, SA. On board the aircraft were the pilot and two passengers. On arrival at Moomba at about 1250 Central Daylight-saving Time (CDT), the pilot configured the aircraft to join the circuit with flaps set to the approach setting and the propeller speed set at 1900 RPM. They positioned the aircraft at 150–160 kt airspeed to join the downwind leg of the circuit for runway 30, which is a right circuit. The pilot lowered the landing gear on the downwind circuit leg. They reduced power (set 600-700 foot-pounds torque on both engines) to start the final descent on late downwind abeam the runway 30 threshold, in accordance with their standard operating procedures. At about the turn point for the base leg of the circuit, the pilot observed the left engine fire warning activate. The pilot held the aircraft in the right base turn, but paused before conducting the engine fire checklist immediate actions in consideration of the fact that they were only a few minutes from landing and there were no secondary indications of an engine fire. After a momentary pause, the pilot decided to conduct the immediate actions. They retarded the left engine condition lever to the fuel shut-off position, paused again to consider if there was any other evidence of fire, then closed the firewall shutoff valve, activated the fire extinguisher and doubled the right engine power (about 1,400 foot-pounds torque). The pilot continued to fly the aircraft in a continuous turn for the base leg towards the final approach path, but noticed it was getting increasingly difficult to maintain the right turn. They checked the engine instruments and confirmed the left engine was shut down. They adjusted the aileron and rudder trim to assist controlling the aircraft in the right turn. The aircraft became more difficult to control as the right turn and descent continued and the pilot focused on maintaining bank angle, airspeed (fluctuating 100–115 kt) and rate of descent. Due to the pilot’s position in the left seat, they were initially unable to sight the runway when they started the right turn. The aircraft had flown through the extended runway centreline when the pilot sighted the runway to the right of the aircraft. The aircraft was low on the approach and the pilot realised that a sand dune between the aircraft and the runway was a potential obstacle. They increased the right engine power to climb power (2,230 foot-pounds torque) raised the landing gear and retracted the flap to reduce the rate of descent. The aircraft cleared the sand dune and the pilot lowered the landing gear and continued the approach to the runway from a position to the left of the runway centreline. The aircraft landed in the sand to the left of the runway threshold and after a short ground roll spun to the left and came to rest. There were no injuries and the aircraft was substantially damaged.
Probable cause:
From the evidence available, the following findings are made with respect to the collision with terrain involving Beech Aircraft Corporation B200, registered VH-MVL that occurred at Moomba Airport, South Australia on 13 December 2016. These findings should not be read as apportioning blame or liability to any particular organisation or individual.
Contributing factors:
- The operator did not modify the aircraft to include a more reliable engine fire detection system in accordance with the manufacturer’s service bulletin, and as subsequently recommended by the Civil Aviation Safety Authority’s airworthiness bulletin. The incorporation of the manufacturer’s modification would have reduced the risk of a false engine fire warning.
- During the approach phase of flight, the pilot shutdown the left engine in response to observing a fire warning, but omitted to feather the propeller. The additional drag caused by the windmilling propeller, combined with the aircraft configuration set for landing while in a right turn, required more thrust than available for the approach.

Other factors that increased risk:
- The advice from the Civil Aviation Safety Authority to the operator, that differences training was acceptable, resulted in the pilot not receiving the operator’s published B200 syllabus of training. The omission of basic handling training on a new aircraft type could result in a pilot not developing the required skilled behaviour to handle the aircraft either near to or in a loss of control situation.

Other findings:
- The pilot met the standard required by the operator in their cyclic training and proficiency program and no knowledge deficiencies associated with handling engine fire warnings were identified.
Final Report:

Crash of a Beechcraft A100 King Air in Saint-Frédéric

Date & Time: Dec 12, 2016 at 0730 LT
Type of aircraft:
Operator:
Registration:
C-FONY
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Saint-Frédéric - Quebec
MSN:
B-154
YOM:
1973
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the takeoff roll from runway 05 at Saint-Frédéric Airport, the twin engine deviated to the left. The pilot-in-command elected to correct the deviation and to maintain the airplane on the runway centerline but it veered off runway to the left and came to rest in the snow. Both pilots evacuated safely and the aircraft was damaged beyond repair.