Crash of a Douglas DC-3C in Puerto Gaitán

Date & Time: Apr 6, 2016 at 0625 LT
Type of aircraft:
Operator:
Registration:
HK-2663
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Puerto Gaitán – Villavicencio
MSN:
10210
YOM:
1945
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4058
Copilot / Total flying hours:
7934
Aircraft flight hours:
23291
Circumstances:
Shortly after takeoff from Puerto Gaitán Airport Runway 04, while on a cargo flight to Villavicencio, the left engine exploded and caught fire. As the aircraft was losing speed and height, the crew attempted an emergency landing when the aircraft crash landed in an open field located 2,6 km southwest from the airport, bursting into flames. All three crew members escaped with minor injuries and the aircraft was destroyed by a post crash fire.
Probable cause:
Failure of the left engine following the detachment of the head of a cylinder shortly after takeoff. Deficiencies in maintenance processes contributed to this situation. The crew failed to follow the emergency procedures when the left engine caught fire and exploded, reducing the power on the right engine. In such conditions, the aircraft was unable to maintain a safe altitude and the crew was forced to attempt an emergency landing.
Final Report:

Crash of a Piper PA-42-720 Cheyenne IIIA off Tel Aviv

Date & Time: Apr 3, 2016 at 1700 LT
Type of aircraft:
Operator:
Registration:
4X-CMD
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
42-5501040
YOM:
1989
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Tel Aviv-Sde Dov Airport, while climbing, the pilot encountered technical problems and declared an emergency. He elected to return to the airport but eventually ditched the airplane few dozen metres offshore. Both occupants were rescued and the aircraft was damaged beyond repair.

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

Date & Time: Apr 3, 2016 at 0732 LT
Type of aircraft:
Operator:
Registration:
RA-54828
Flight Phase:
Survivors:
Yes
Schedule:
Aksarino - Aksarino
MSN:
1G184-35
YOM:
16
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6095
Aircraft flight hours:
6782
Circumstances:
The pilot, sole on board, was engaged in a crop spraying mission over plantation located near Aksarino, Republic of Tatarstan, and the aircraft was carrying a load of 1,200 kilos of fertilizers. Shortly after takeoff, while climbing, the engine encountered technical problems. The pilot elected to make an emergency landing when the aircraft crash landed in a field and came to rest. The aircraft was damaged beyond repair and the pilot was uninjured.
Probable cause:
Most probably the accident with An-2 RA-54828 aircraft after its takeoff in order to perform crop dusting was caused by inadvertent engine cut-off due to water ingestion into fuel flow system. Most probably water ingestion into engine fuel flow system was due to violation of refueling procedure by the crew. The aircraft sustained significant damage during the emergency landing on slush soft surface.
Final Report:

Ground fire of an Antonov AN-26RT in Rostov-on-Don

Date & Time: Mar 29, 2016
Type of aircraft:
Operator:
Registration:
09 blue
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
122 02
YOM:
1982
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the takeoff roll, the right engine caught fire. The crew aborted the takeoff procedure and was able to stop the aircraft on the runway. Unfortunately, he was unable to extinguish the fire that destroyed the right engine. All occupants evacuated safely and the aircraft was partially destroyed by fire.
Probable cause:
The right engine caught fire during takeoff for unknown reasons.

Crash of a Comp Air CA-9 in Campo de Marte: 7 killed

Date & Time: Mar 19, 2016 at 1523 LT
Type of aircraft:
Operator:
Registration:
PR-ZRA
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Campo de Marte – Rio de Janeiro
MSN:
0420109T01
YOM:
2012
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
7
Captain / Total flying hours:
215
Circumstances:
Shortly after takeoff from Campo de Marte Airport runway 30, the single engine airplane entered a right turn without gaining altitude. Less than one minute after liftoff, the aircraft impacted a building located in the Frei Machado Street, some 370 metres from runway 12 threshold. The aircraft was totally destroyed by impact forces and a post crash fire and all seven occupants were killed. One people on the ground was slightly injured. Owned by the Brazilian businessman Roger Agnelli, the aircraft was on its way to Santos Dumont Airport in Rio de Janeiro. Among the victims was Roger Agnelli, his wife Andrea, his both children John and Anna Carolina, the pilot and two other friends. They were enroute to Rio to take part to the wedding of the nephew of Mr. Agnelli.
Probable cause:
Contributing factors
- Pilot judgment - undetermined
The absence of manuals and performance charts to guide the operation and actions based only on empirical knowledge about the aircraft may have taken to an inadequate evaluation of certain parameters related to its operation. In this case, the performance of the aircraft under conditions of weight, altitude and high temperatures may have provided its conduction with reduced margins of safety during takeoff that resulted in the on-screen accident.
- Flight planning - undetermined
The informality present in the field of experimental aviation, associated with the absence of support systems, may have resulted in an inadequacy in the work of flight preparation, particularly with regard to performance degradation in the face of adverse conditions (high weight, altitude and temperature), compromising the quality of the planning carried out, thus contributing to it being carried out a takeoff under marginal conditions.
- Project - undetermined
During the PR-ZRA assembly process, changes were incorporated into the Kit's original design that directly affected the airplane's take-off performance. Since the submission of documentation related to in-flight testing or performance graphics was not required by applicable law, it is possible that the experimental nature of the project has enabled the operation of the aircraft based on
empirical parameters and inadequate to their real capabilities.
- Support systems - undetermined
The absence of a support system, in the form of publications that allowed obtaining equipment performance data in order to carry out proper planning, added risk to operations and may have led to an attempt to take off under unsafe conditions.
Final Report:

Crash of a Cessna 340A in Tampa: 2 killed

Date & Time: Mar 18, 2016 at 1130 LT
Type of aircraft:
Operator:
Registration:
N6239X
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Tampa – Pensacola
MSN:
340A-0436
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
5195
Aircraft flight hours:
3963
Circumstances:
The airline transport pilot and pilot-rated passenger were departing on an instrument flight rules (IFR) cross country flight from runway 4 in a Cessna 340A about the same time that a private pilot and pilot rated passenger were departing on a visual flight rules repositioning flight from runway 36 in a Cessna 172M. Visual meteorological conditions prevailed at the airport. The runways at the nontowered airport converged and intersected near their departure ends. According to a witness, both airplanes had announced their takeoff intentions on the airport's common traffic advisory frequency (CTAF), which was not recorded; the Cessna 340A pilot's transmission occurred about 10 to 15 seconds before the Cessna 172M pilot's transmission. However, the witness stated that the Cessna 172M pilot's transmission was not clear, but he was distracted at the time. Both occupants of the Cessna 172M later reported that they were constantly monitoring the CTAF but did not hear the transmission from the Cessna 340A pilot nor did they see any inbound or outbound aircraft. Airport video that captured the takeoffs revealed that the Cessna 172M had just lifted off and was over runway 36 approaching the intersection with runway 4, when the Cessna 340A was just above runway 4 in a wings level attitude with the landing gear extended and approaching the intersection with runway 36. Almost immediately, the Cessna 340A then began a climbing left turn with an increasing bank angle while the Cessna 172M continued straight ahead. The Cessna 340A then rolled inverted and impacted the ground in a nose-low and left-wing-low attitude. The Cessna 172M, which was not damaged, continued to its destination and landed uneventfully. The Cessna 340A was likely being flown at the published takeoff and climb speed of 93 knots indicated airspeed (KIAS). The published stall speed for the airplane in a 40° bank was 93 KIAS, and, when the airplane reached that bank angle, it likely exceeded the critical angle of attack and entered an aerodynamic stall. Examination of the Cessna 340A wreckage did not reveal any preimpact mechanical malfunctions that would have precluded normal operation. Because of a postcrash fire, no determination could be made as to how the radios and audio panel were configured for transmitting and receiving or what frequencies were selected. There were no reported discrepancies with the radios of the Cessna 172M, and there were no reported difficulties with the communication between the Cessna 340A and the Federal Aviation Administration facility that issued the airplane's IFR clearance. Additionally, there were no known issues related to the CTAF at the airport. Toxicological testing detected unquantified amounts of atorvastatin, diphenhydramine, and naproxen in the Cessna 340A pilot's liver. The Cessna 340A pilot's use of atorvastatin or naproxen would not have impaired his ability to hear the radio announcements, see the other airplane taking off on the converging runway, or affected his performance once the threat had been detected. Without an available blood level of diphenhydramine, it could not be determined whether the drug was impairing or contributed to the circumstances of the accident.
Probable cause:
The intentional low altitude maneuvering during takeoff in response to a near-miss with an airplane departing from a converging runway, which resulted in an exceedance of the airplane's critical angle of attack and a subsequent aerodynamic stall.
Final Report:

Crash of a Beechcraft 1900D in Karachi

Date & Time: Mar 18, 2016 at 0820 LT
Type of aircraft:
Operator:
Registration:
AP-BII
Flight Phase:
Survivors:
Yes
Schedule:
Karachi – Sui
MSN:
UE-45
YOM:
1993
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
18
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2885
Captain / Total hours on type:
717.00
Copilot / Total flying hours:
3614
Copilot / Total hours on type:
245
Aircraft flight hours:
19574
Aircraft flight cycles:
30623
Circumstances:
The Aircraft Sales and Services (Private) Limited (ASSL) aircraft Beechcraft-1900D Registration No. AP-BII was scheduled for a chartered flight on 18th March, 2016 from Karachi to Sui. Just after takeoff from runway 25L at 0820 hrs local time, the crew observed power loss of right engine and made a gear up landing on the remaining runway on the right side of centreline. After touchdown, the aircraft went off the runway towards right side and then came back on the runway before coming to a final stop 1,050 feet short from the end of runway. The Captain and one passenger received serious injuries due to hard impact of the aircraft with ground. All other passengers and technician remained unhurt.
Probable cause:
The investigation therefore, concludes that:
- Some internal malfunction of the Propeller Governor Part No. 8210-410 Serial No. 2490719 was the cause of experienced uncommanded auto feather. However, exact cause of the occurrence could not be determined.
- Continuing take off below V1 speed (104kts) after encountering engine malfunction and after takeoff raising flaps below recommended height (400ft AGL) lead to decrease in lift and unsustainability of flight.
Final Report:

Crash of an Antonov AN-26B off Cox's Bazar: 3 killed

Date & Time: Mar 9, 2016 at 0905 LT
Type of aircraft:
Operator:
Registration:
S2-AGZ
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Cox’s Bazar – Jessore
MSN:
134 08
YOM:
1984
Flight number:
21
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
13315
Captain / Total hours on type:
6896.00
Copilot / Total flying hours:
1438
Copilot / Total hours on type:
1195
Aircraft flight hours:
16379
Aircraft flight cycles:
17299
Circumstances:
On March 9, 2016 one AN -26B aircraft belonging to True Aviation Ltd was operating a schedule cargo flight from a small domestic airport (Cox’s Bazar-VGCB) in southern Bangladesh to another domestic airport (Jessore -VGJR) in western Bangladesh, The cargo was Shrimp fries. As per the General Declaration the total cargo quantity was 802 boxes weighing 4800 kg. The airline had filled a flight plan keeping the ETD blank. The flight plan routing was CB W4 CTG W5 JSR at FL 100. All the documents except the load sheet were found properly signed and are in the possession of AAIT. According to ATC controller’s statement and recorded tape the aircraft requested for startup clearance at 0258z. As per the recordings with ATC the controller passed the visibility information of Jessore Airport as 3km. The aircraft started engines and requested for taxi. The aircraft was cleared to taxi to Runway 35 via taxiway S. The aircraft requested for takeoff clearance and was cleared for Take Off at 0305z. Immediately after airborne the pilot reported engine failure without mentioning initially which engine had failed but later confirming failure of the left engine and requested for immediate return back to Cox’s Bazar airport. He was advised by ATC to call left hand down wind. But the control tower spotted the aircraft making a right hand down wind at a very low altitude. All emergency services were made standby from the ATC. The aircraft called final and requested for landing clearance. For reasons so far unknown the aircraft made a low level Go Around. The controller in the tower saw the aircraft flying at about 400 to 500 feet. The surviving Flight Navigator also confirmed this in his statement. The ATC advised the captain to call left hand down wind. But there was no response from the crew. The ATC repeatedly kept calling the aircraft but there was no response from the crew and total communication was lost. At time 0332z the airport authority came to know through other means that the aircraft had crashed approximately 03km west of the airport.
Probable cause:
The accident was the consequence of the combination of the following factors:
a) Failure to initiate a rejected take off during take off roll following the indication of engine failure;
b) Failure to adhere to the company SOP following the detection of the engine failure during take off;
c) Considering the poor visibility at Cox’s Bazar Airport, diverting to the alternate airfield Chittagong Airport located only 50 nm away that has the provision for full ILS approach facility. This could have helped the crew in carrying out a proper one engine out precision approach landing;
d) The aircraft flew at a speed much lower than the clean configuration speed. The aircraft flew at 225 km/h in clean configuration whereas the minimum clean configuration speed is 290 km/hr.
e) As per the FDR data the aircraft stalled while making a turn towards the side of the failed engine at a very low altitude.
Final Report:

Crash of a Beechcraft 1900D in Naypyidaw: 5 killed

Date & Time: Feb 10, 2016 at 0940 LT
Type of aircraft:
Operator:
Registration:
4601
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Naypyidaw – Namhsan
MSN:
UE-177
YOM:
1995
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
Shortly after takeoff from Naypyidaw Airport, while climbing to an altitude of about 500 feet, the aircraft entered an uncontrolled descent and crashed in an open field located 600 metres past the runway end, bursting into flames. Four occupants were killed while a passenger was seriously injured and evacuated to a local hospital. He died from his injuries few hours later. Used for emergency flights, the airplane was carrying three officers to Namhsan, Shan State, to assist with the aftermath of a fire there. Those officers who were killed were Major Aung Kyaw Moe, Captain Aung Paing Soe and Captain Htin Kyaw Soe.

Crash of a Socata TBM-900 off Florianópolis: 2 killed

Date & Time: Feb 1, 2016 at 0519 LT
Type of aircraft:
Registration:
PP-LIG
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Florianópolis – Ji-Paraná
MSN:
1071
YOM:
2015
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1535
Captain / Total hours on type:
154.00
Aircraft flight hours:
195
Circumstances:
The single engine aircraft departed Florianópolis-Hercilio Luz Airport at 0515LT on a private flight to Ji-Paraná, carrying one passenger and one pilot. While climbing by night at an altitude of 3,600 feet, the pilot initiated a right turn. Then the aircraft completed a 360 turn and crashed in the sea off Campeche Island. Few debris were found the following morning floating on water and the main wreckage was found two weeks later. Both occupants were killed.
Probable cause:
Contributing factors:
- Application of commands – undetermined
Considering the hypothesis of spatial disorientation, of the disabling type, it is possible that the pilot has reached a situation of complete inability to operate correctly controls the aircraft in order to regain control of the flight.
- Attitude – undetermined
It is possible that the high subordination of the pilot to the requests of his boss has made it difficult for you to position yourself in relation to your limitation in flying at night and in instrument flight meteorological conditions.
- Disorientation – undetermined
Conditions favorable to disorientation, that is, the night flight over the sea, within clouds and manual operation, as well as the dynamics of the aircraft trajectory recorded by the radar, among other factors, make spatial disorientation the main hypothesis for the accident.
- Visual illusions – undetermined
It is also possible that the pilot suffered visual illusions when flying over the sea in night time. When not seeing the lighting on land, and being at night dark, with cloudiness, the pilot may have confused spatial references.
- Instruction – undetermined
It is possible that the lack of familiarity with the English language has made it difficult, in to some degree, knowledge of the resources, equipment and systems present in the aircraft, as well as in the instruction received in a flight simulator.
Final Report: