Crash of a Let L-410UVP-E9 in Ngerende: 4 killed

Date & Time: Aug 22, 2012 at 1220 LT
Type of aircraft:
Operator:
Registration:
5Y-UVP
Flight Phase:
Survivors:
Yes
Schedule:
Amboseli – Ngerende – Mara North – Ukunda – Mombasa
MSN:
91 26 27
YOM:
1991
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
11
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
7480
Captain / Total hours on type:
1150.00
Copilot / Total flying hours:
312
Circumstances:
This was a commercial non scheduled flight which was being operated for air transport for local flights. The operator is based in Mombasa and mostly executes passenger flights to the Masai Mara and other game parks and reserves within the Republic of Kenya. On 22nd Aug 2012, the aircraft was scheduled to carry out a flight to the Masai Mara, do several sectors to pick and drop passengers and return to Moi international Airport via Ukunda Airport. The call sign was 5Y-UVP. The last point of departure was Ngerende Airstrip in the Masai Mara at 0917 with intention of onward flight to Mara North airstrip in the Masai Mara. The flight had earlier left Amboseli Airstrip with two crew, and 17 passengers for Ngerende Airstrip. 6 passengers had disembarked at Ngerende and the remaining 11 passengers were continuing to other destinations. No additional passengers or cargo was picked up from Ngerende airstrip. No refueling was done at the airstrip. The airfield is an unmanned airfield, with crew executing unmanned airfield communication procedures to execute approach and landings and also during takeoff. There is however a ground time keeper and a fueling bay at the airfield. Due to terrain and prevailing winds at the time of the flight, Runway 28 was in use. The crew was using unmanned airfield procedures and after the drop-off of 6 passengers, the aircraft lined up runway 28 and proceeded with the take off run. Ground staff at the airstrip reported a normal takeoff run and rotation. During the initial climb, the ground staff still had the aircraft in sight and reported to have seen the aircraft veer sharply to the left and then disappear behind terrain. Shortly afterwards, a loud sound was heard followed by dust in the air. Emergency SAR was initiated with the airport and hotel staff rushing to the accident site. The location of the accident was about 310 meters from the threshold of Runway 10, offset 30° to the left of the extended center line Runway 28. GPS coordinates (figure 1.2) 01.084189° S, 35.1781127° E, Ngerende airstrip. The accident occurred at 0917 UTC on 22nd Aug 2012, during daytime.
Probable cause:
The following findings were identified:
- The left engine was most probably not developing power at the time of impact,
- The left engine propeller was most probably in feather at the time of impact,
- Both CVR and FDR were unserviceable at the time of the accident,
- AAID was unable to determine origin of contaminant found in the left engine Fuel Control Unit,
- Sufficient oversight was not exercised over the Operator,
- High turnover of the Operator’s staff.
Final Report:

Crash of a Piper PA-46R-350T Matrix off Jacarepaguá: 2 killed

Date & Time: Aug 21, 2012 at 1935 LT
Registration:
PT-FEM
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Jacarepaguá – Campo de Marte
MSN:
46-92158
YOM:
2010
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
Shortly after a night takeoff from Jacarepaguá Airport, the single engine aircraft entered an uncontrolled descent and crashed in the sea. Few debris were found several days later. The pilot's body was found on September 4 on a beach in Barra de Tijuca. The wreckage and the copilot's body were never found. It was reported that the crew did not activate the transponder after takeoff and did not contact ATC for unknown reasons.

Crash of a Beechcraft B60 Duke in Sedona: 3 killed

Date & Time: Jul 26, 2012 at 0830 LT
Type of aircraft:
Registration:
N880LY
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Sedona – Albuquerque
MSN:
P-524
YOM:
1980
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
663
Captain / Total hours on type:
94.00
Aircraft flight hours:
3924
Circumstances:
Several witnesses observed the airplane before and during its takeoff roll on the morning of the accident. One witness observed the airplane for the entire event and stated that the run-up of the engines sounded normal. During the takeoff roll, the acceleration of the airplane appeared a little slower but the engines continued to sound normal. Directional control was maintained, and at midfield, the airplane had still not rotated. As the airplane continued down the 5,132-foot-long runway, it did not appear to be accelerating, and, about 100 yards from the end of the runway, it appeared that it was not going to stop. The airplane maintained contact with the runway and turned slightly right before it overran the end of the runway. The airplane was subsequently destroyed by impact forces and a postaccident fire. The wreckage was located at the bottom of a deep gully off the end of the runway. Postaccident examination of the area at the end of the runway revealed two distinct tire tracks, both of which crossed the asphalt and dirt overrun of 175 feet. A review of the airplane's weight and balance and performance data revealed that it was within its maximum gross takeoff weight and center of gravity limits. At the time of the accident, the density altitude was calculated to be 7,100 feet; the airport's elevation is 4,830 feet. For the weight of the airplane and density altitude at the time of the accident, it should have lifted off 2,805 feet down the runway; the distance to accelerate to takeoff speed and then to safely abort the takeoff and stop the airplane was calculated to be 4,900 feet. It is unknown whether the pilot completed performance calculations accounting for the density altitude. All flight control components were accounted for at the accident site. Although three witnesses indicated that the engines did not sound right at some point during the runup or takeoff, examination of the engine and airframe revealed no evidence of any preexisting mechanical malfunctions or failures that would have precluded normal operation. Propeller signatures were consistent with rotational forces being applied at the time of impact. No conclusive evidence was found to explain why the airplane did not rotate or why the pilot did not abort the takeoff once reaching the point to safely stop the airplane.
Probable cause:
The airplane's failure to rotate and the pilot's failure to reject the takeoff, which resulted in a runway overrun for reasons that could not be undetermined because postaccident examination of the airplane and engines did not reveal any malfunctions or failures that would have precluded normal operation.
Final Report:

Crash of a Harbin Yunsunji Y-12-II in Nouakchott: 7 killed

Date & Time: Jul 12, 2012 at 0745 LT
Type of aircraft:
Operator:
Registration:
5T-MAE
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Nouakchott - Tasiast
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
The twin engine aircraft was engaged in a special flight to the Tasiast Airstrip deserving the Gold Mine of Tasiast on behalf of the Kinross Gold Corporation. Shortly after take off from Nouakchott, while in initial climb, the aircraft stalled and crashed in a desert area located past the runway end, bursting into flames. All seven occupants were killed and aircraft was destroyed by impact forces and a post crash fire. Both pilots were Mauritanian Customs Officers while among the passengers were three Security Officers of the Kinross Gold Corporation who were in charge to transfer a load of gold back to Nouakchott.

Crash of a Technoavia SM-92G Turbo Finist in Bollullos de la Mitación

Date & Time: Jul 1, 2012 at 1045 LT
Registration:
HA-NAH
Flight Phase:
Survivors:
Yes
Schedule:
Bollullos de la Mitación - Bollullos de la Mitación
MSN:
003
YOM:
1994
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
340
Captain / Total hours on type:
24.00
Aircraft flight hours:
2575
Circumstances:
The aircraft started taking off from runway 27 threshold. Upon reaching a speed deemed proper by the pilot for rotation, the pilot noticed that the aircraft was not taking off, so he decided to abort the takeoff. While trying to stop the aircraft, it exited via the left side of the runway near the end, breaking through the fence that surrounds the aerodrome before coming to rest in trees. While all ten occupants were uninjured, the aircraft was damaged beyond repair with both wings sheared off.
Probable cause:
Whenever this aircraft is doing a short-field takeoff with a high weight, it is recommended that the flaps be set to their takeoff position of 20°. The evidence indicates that the pilot was attempting to take off on runway 27 and forgot to place the flaps in the takeoff position (20°).
Final Report:

Crash of a Piper PA-31P-425 Navajo in Dalton: 1 killed

Date & Time: Jun 30, 2012 at 1620 LT
Type of aircraft:
Registration:
N33CG
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Dalton - Dalton
MSN:
31-7300157
YOM:
1973
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1685
Circumstances:
According to a friend of the pilot, the pilot was taking the airplane to have an annual inspection completed. The friend assisted the pilot before departure and watched as the airplane departed. He did not notice any anomalies with the airplane during the takeoff or the climbout. According to a witness in the vicinity of the accident site, he heard the airplane coming toward him, and it was flying very low. He looked up and saw the airplane approximately 200 feet over his house and descending toward the trees. As he watched the airplane, he noticed that the right propeller was not turning, and the right engine was not running. He stated that the left engine sounded as if it was running at full power. The airplane pitched up to avoid a power line and rolled to the right, descending below the tree line. A plume of smoke and an explosion followed. Examination of the right propeller assembly revealed evidence of significant frontal impact. The blades were bent but did not have indications of rotational scoring; thus they likely were not rotating at impact. One preload plate impact mark indicated that the blades were at an approximate 23-degree angle; blades that are feathered are about 86 degrees. Due to fire and impact damage of the right engine and related system components, the reason for the loss of power could not be determined. An examination of the airframe and left engine revealed no mechanical malfunctions or failures that would have precluded normal operation. A review of the airplane maintenance logbooks revealed that the annual inspection was 12 days overdue. According to Lycoming Service Instruction No. 1009AS, the recommended time between engine overhaul is 1,200 hours or 12 years, whichever occurs first. A review of the right engine maintenance logbook revealed that the engine had accumulated 1,435 hours since major overhaul and that neither engine had been overhauled within the preceding 12 years. Although the propeller manufacturer recommends that the propeller be feathered before the engine rpm drops below 1,000 rpm, a review of the latest revision of the pilot operating handbook (POH) revealed that the feathering procedure for engine failure did not specify this. It is likely that the pilot did not feather the right propeller before the engine reached the critical 1,000 rpm, which prevented the propeller from engaging in the feathered position
Probable cause:
The pilot’s failure to maintain airplane control following loss of power in the right engine for reasons that could not be determined because of fire and impact damage. Contributing to the accident was the pilot’s delayed feathering of the right propeller following the loss of engine power and the lack of specific emergency procedures in the pilot operating handbook indicating the need to feather the propellers before engine rpm falls below 1,000 rpm.
Final Report:

Crash of a Cessna 207 Skywagon in Clinceni

Date & Time: Jun 23, 2012 at 1110 LT
Registration:
D-EBBG
Flight Phase:
Survivors:
Yes
Schedule:
Clinceni - Clinceni
MSN:
207-0108
YOM:
1969
Location:
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3656
Captain / Total hours on type:
182.00
Aircraft flight hours:
9019
Circumstances:
The single engine aircraft was engaged in skydiving flights at Clinceni Airport. Shortly after takeoff, while climbing to a height of about 200 feet, the engine failed. The pilot attempted an emergency landing when the aircraft crash landed in a field located 300 meters past the runway end. A skydiver was slightly injured while three other occupants were unhurt. The aircraft was damaged beyond repair.
Probable cause:
The connecting rod in the second cylinder failed during initial climb, causing the engine to stop. The authorization to operate skydiving flights was canceled 21 April 2012.
Final Report:

Crash of a Swearingen SA227AC Metro III off Montevideo: 2 killed

Date & Time: Jun 6, 2012 at 1955 LT
Type of aircraft:
Operator:
Registration:
CX-LAS
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Montevideo - Buenos Aires
MSN:
AC-482
YOM:
1982
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
16177
Copilot / Total flying hours:
406
Aircraft flight hours:
26158
Circumstances:
The crew was performing a cargo flight from Montevideo to Buenos Aires on behalf of DHL. The aircraft departed runway 24 at Montevideo-Carrasco Airport at 1945LT and the crew was cleared to climb to FL080. While reaching a height of 4,500 feet, the aircraft entered an uncontrolled descent and crashed in the sea at a speed of 570 knots which caused its disintegration off Flores Island. Few debris were found the following day floating on water but the main wreckage was localized two weeks later about one NM south of Flores Island. The CVR was found on 02AUG2012 but was unreadable as the content was concerning the last 30 minutes of the precedent flight. On 11FEB2013, fishermen found the cargo door in their fishnet. No trace of the cargo nor the crew was ever found.
Probable cause:
Investigations determined that both engines were running normally at impact, that no propeller blades were lost during descent, that fuel was not contaminated and that no problems occurred on the on electrical system. Meteorological Office confirmed that severe icing conditions prevailed at the time of the accident between FL010 and FL150. The loss of control was the consequence of erroneous indications of the flight instruments, associated with the possible formation of crystalline ice on the aircraft' structure, causing a loss of situational awareness of the crew.
Final Report:

Crash of a Piper PA-42-720 Cheyenne III off Grand Case: 4 killed

Date & Time: May 5, 2012 at 0240 LT
Type of aircraft:
Registration:
F-GXES
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Grand Case - Fort-de-France
MSN:
42-8001043
YOM:
1980
Flight number:
TIF520
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
3950
Captain / Total hours on type:
513.00
Aircraft flight hours:
7593
Aircraft flight cycles:
7830
Circumstances:
The twin engine aircraft was engaged in an ambulance flight between Grand Case and Fort-de-France and was carrying a pilot, a nurse, a doctor and a patient, a Greek citizen in honeymoon in Saint Martin who suffered a heart attack. He normally should be transferred to Fort-de-France from Saint Martin-Princess Juliana Airport with another Operator but the aircraft suffered technical problem prior to departure and the patient was transferred to Grand Case Airport. Piper PA-42 left Grand Case-L'Espérance runway 12 at 02H39. One minute later, during initial climb, it lost height and crashed into the Caribbean Sea, some three NM off the airport, off Tintamarre Island. Around 1000LT in the morning, a wheel and some others debris were found floating in water and no trace of the four occupants was found. They were later considered as deceased.
Probable cause:
The French BEA said in its final report that no technical anomaly to affect significantly the performance of the airplane or its pitch control could be demonstrated. It appears that the pilot had consumed alcohol before the flight and was awake since 0630LT and did not sleep over 20 hours, which could affect his capabilities. In conclusion, the investigation did not determine the cause of the accident, but the following factors may have contributed:
- aircraft's operation with one pilot only,
- absence of regulation does not allow the Civil Aviation Authority to ensure the adequacy of the operational objectives of an operator and its capacity to maintain its activity. This failure could not ensure that the pilot was able to conduct the flight.
- the presence of a flight recorder would probably help to understand the circumstances of the accident with more precision. Important data failed to the investigation, which was not able to identify all possible measures to avoid a similar accident in the future.
Final Report:

Crash of a Un PZL-Mielec AN-2R in Knyazhichi

Date & Time: Apr 23, 2012 at 1335 LT
Type of aircraft:
Operator:
Registration:
UR-81515
Flight Phase:
Survivors:
Yes
Schedule:
Knyazhichi - Knyazhichi
MSN:
1G208-15
YOM:
1984
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was engaged in a spraying mission in the region of Knyazhichi, Sumy Oblast, Ukraine. Following 15 successful sorties that day, the crew was ready for the 16th and started the takeoff procedure from the third of the runway which is 768 metres long. After a course of 577 metres, the single engine aircraft failed to get airborne and overran. The crew decided to abort but this was too late. The aircraft sank in muddy field and rolled for about 56 metres before coming to rest upside down. Both occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
The following factors were identified:
- The crew did not use the entire runway length for the takeoff procedure (577 metres instead of the 768 metres available),
- The decision of the crew to reject takeoff was taken too late,
- The wind direction changed during the takeoff procedure and became a tailwind component.