Crash of a Gavilán 358 in Nueva Antioquia: 3 killed

Date & Time: May 24, 2006
Type of aircraft:
Operator:
Registration:
ARC-416
Flight Type:
Survivors:
No
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
On final approach to Nueva Antioquia Airport, the single engine aircraft went out of control and crashed, killing all three occupants, two pilots and one passenger.

Crash of a Short 330-200 in Myrtle Beach

Date & Time: May 18, 2006 at 0745 LT
Type of aircraft:
Operator:
Registration:
N937MA
Flight Type:
Survivors:
Yes
Schedule:
Greensboro – Myrtle Beach
MSN:
3040
YOM:
1980
Flight number:
SNC1340
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
21095
Circumstances:
Following an uneventful cargo flight from Greensboro, NC, the aircraft made a wheels-up landing on runway 18 at Myrtle Beach Airport, SC. The aircraft slid on its belly for few dozen metres before coming to rest on the main runway. Both pilots escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
NTSB did not conduct any investigation on this event.

Crash of a Convair CV-580 in La Ronge: 1 killed

Date & Time: May 14, 2006 at 1245 LT
Type of aircraft:
Registration:
C-GSKJ
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
La Ronge - La Ronge
MSN:
202
YOM:
1954
Flight number:
TKR472
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
9500
Captain / Total hours on type:
750.00
Copilot / Total flying hours:
13000
Copilot / Total hours on type:
25
Circumstances:
The aircraft was conducting stop-and-go landings on Runway 36 at the airport in La Ronge, Saskatchewan. On short final approach for the third landing, the aircraft developed a high sink rate, nearly striking the ground short of the runway. As the crew applied power to arrest the descent, the autofeather system feathered the left propeller and shut down the left engine. On touchdown, the aircraft bounced, the landing was rejected, and a go-around was attempted, but the aircraft did not attain the airspeed required to climb or maintain directional control. The aircraft subsequently entered a descending left-hand turn and crashed into a wooded area approximately one mile northwest of the airport. The first officer was killed and two other crew members sustained serious injuries. The aircraft sustained substantial damage. The accident occurred during daylight hours at 1245 central standard time.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The flight crew attempted a low-energy go-around after briefly touching down on the runway. The aircraft’s low-energy state contributed to its inability to accelerate to the airspeed required to accomplish a successful go-around procedure.
2. The rapid power lever advancement caused an inadvertent shutdown of the left engine, which exacerbated the aircraft’s low-energy status and contributed to the eventual loss of control.
3. The inadvertent activation of the autofeather system contributed to the crew’s loss of situational awareness, which adversely influenced the decision to go around, at a time when it may have been possible for the aircraft to safely stop and remain on the runway.
4. The shortage and ambiguity of information available on rejected landings contributed to confusion between the pilots, which resulted in a delayed retraction of the flaps. This departure from procedure prevented the aircraft from accelerating adequately.
5. Retarding the power levers after the first officer had exceeded maximum power setting resulted in an inadequate power setting on the right engine and contributed to a breakdown of crew coordination. This prevented the crew from effectively identifying and responding to the emergencies they encountered.
Findings as to Risk:
1. The design of the autofeather system is such that, when armed, the risk of an inadvertent engine shutdown is increased.
2. Rapid power movement may increase the risk of inadvertent activation of the negative torque sensing system during critical flight regimes.
Other Findings:
1. There were inconsistencies between sections of the Conair aircraft operating manual (AOM), the standard operating procedures (SOPs), and the copied AOM that the operator possessed. These inconsistencies likely created confusion between the training captain and the operator’s pilots.
2. The operator’s CV-580A checklists do not contain a specified section for circuit training. The lack of such checklist information likely increased pilot workload.
Final Report:

Crash of a Cessna 421B Golden Eagle II in Marathon

Date & Time: May 8, 2006 at 0800 LT
Operator:
Registration:
N988GM
Flight Type:
Survivors:
Yes
Schedule:
Pompano Beach - Marathon
MSN:
421B-0535
YOM:
1973
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1450
Aircraft flight hours:
5307
Circumstances:
The commercial certificated pilot was positioning the multi-engine, retractable landing gear airplane for a corporate passenger flight under Title 14, CFR Part 91, when the accident occurred. Upon landing at the destination, the pilot aborted the landing, and after climbing to about 100 feet agl descended, impacting in a canal. A witness who was not looking towards the runway, reported hearing the sound of a twin engine airplane approaching with the engines at reduced power, and then heard a scraping noise similar to the recent gear-up landing he had witnessed. Looking toward the runway, he said the airplane was midfield, left of the runway centerline, about 20 feet in the air with the landing gear retracted, and that he saw a cloud of dust, and heard what he thought was full engine power being applied. He said the airplane climbed to about 100 feet agl, and disappeared from view. Another witness with a portable VHF radio tuned to the unicom frequency, reported hearing the pilot say he was "doing an emergency go-around." The airplane descended striking utility poles, and impacted in a saltwater canal. An examination of the airport runway revealed a set of parallel propeller strike marks. The left and right sets of marks were 109 and 113 feet long, and the mark's center-to-center measurement is consistent with the engine centerline-to-centerline measurement for the accident airplane. No landing gear marks were observed. The airplane's six propeller blades had extensive torsional twisting and bending, as-well-as extensive chord wise scratching and abrasion. Several of the blades had fractured or missing tips. An examination of the cockpit showed the landing gear retraction/extension handle was in the up/retracted position, and the landing gear extension warning horn circuit breaker was in the pulled/tripped position. The landing gear emergency extension handle was in the stowed position. The nose landing gear was damaged during final impact, and was not functional. During the postimpact examination, both the left and right main landing gear were stowed in the up and locked/retracted position. The landing gear were released/unlocked and operated appropriately using the emergency extension handle. An examination of the left and right main landing gear showed no damage to the wheel doors, leg doors, wheels, or tires. All linkages and locking devices were undamaged, and appeared to function normally.
Probable cause:
The pilot's failure to extend the landing gear prior to landing, which resulted in the propellers striking the runway, an aborted landing, and an in-flight collision with terrain.
Final Report:

Crash of a Rockwell Shrike Commander 500S in Natal

Date & Time: May 5, 2006 at 0710 LT
Operator:
Registration:
PT-IGL
Flight Type:
Survivors:
Yes
Schedule:
Recife - Natal
MSN:
500-3129
YOM:
1972
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3000
Captain / Total hours on type:
500.00
Circumstances:
The twin engine aircraft departed Recife-Guararapes Airport at 0609LT on a flight to Natal, carrying one passenger, one pilot and a load consisting of bags containing bank documents. On approach to Natal-Augusto Severo Airport runway 16L, the left engine failed. Shortly later, at a height of about 600 feet, the right engine failed as well. Aware that he will not be able to reach the airport, the pilot attempted an emergency landing in an open field. On touchdown, the undercarriage collapsed and the aircraft slid for about 200 metres before coming to rest in a muddy field. Both occupants escaped with minor injuries and the aircraft was damaged beyond repair.
Probable cause:
Double engine failure on approach caused by a fuel exhaustion. The following findings were identified:
- Poor flight preparation on part of the pilot,
- Miscalculation of fuel consumption for the flying distance (about an hour),
- The day prior to the accident, tanks were filled with a quantity of 130 liters of fuel, barely 13 liters more than the quantity theoretically necessary for the flight in the conditions existing at the time of the accident,
- No technical anomalies were found on the airplane and its equipment,
- Poor organizational culture within the operator regarding fuel policy,
- Qualitative deficiency in the instruction given to the pilot who had not acquired the basic knowledge for fuel management,
- Failure to observe the actual quantity of fuel in the tanks prior to departure,
- Shortcomings in the operator's organizational processes,
- Inadequate supervision of flight planning activities by the operator who failed to identify any flaws in the fuel management procedures by the pilots.
Final Report:

Crash of a Partenavia P.68 in Panda Ranch

Date & Time: Apr 30, 2006 at 2000 LT
Type of aircraft:
Registration:
N4574C
Flight Phase:
Survivors:
Yes
Schedule:
Panda Ranch - Honolulu
MSN:
310
YOM:
1983
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2100
Captain / Total hours on type:
110.00
Aircraft flight hours:
1900
Circumstances:
The airplane descended into terrain during the takeoff initial climb from a private airstrip in dark night conditions. The four passengers had been flown to the departure airport earlier in the day. After several hours at the destination, the pilot and passengers boarded the airplane and waited for two other airplanes to depart. During the initial climb, the pilot banked the airplane to the right, due to the upsloping terrain in the opposite direction (left) and noise abatement concerns; this maneuver was a standard departure procedure. The airplane collided with the gradually upsloping terrain, coming to rest upright. The pilot did not believe that he had experienced a loss of power. The accident occurred in dark night conditions, about 1 hour after sunset. In his written report, the pilot said he only had 10 hours of total night flying experience.
Probable cause:
The pilot's failure to attain a proper climb rate and to maintain adequate clearance from the terrain during the initial climb in dark night conditions, which resulted in an in-flight collision with terrain.
Final Report:

Crash of a Convair CV-580F in Amisi: 8 killed

Date & Time: Apr 27, 2006 at 1100 LT
Type of aircraft:
Registration:
ZS-SKH
Flight Type:
Survivors:
No
Schedule:
Goma – Amisi
MSN:
147
YOM:
1954
Location:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
The aircraft departed Goma at 0930LT on a cargo flight to Amisi, carrying five passengers, three crew members and a load consisting of telecommunication equipments. On approach to Amisi Airport, the aircraft crashed in unknown circumstances, killing all eight occupants.

Crash of an Antonov AN-32B in Lashkar Gah: 5 killed

Date & Time: Apr 24, 2006 at 1145 LT
Type of aircraft:
Registration:
ZS-PDV
Flight Type:
Survivors:
Yes
Schedule:
Kandahar – Lashkar Gah
MSN:
30 03
YOM:
1992
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
12
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
The aircraft was dispatched in Afghanistan on behalf of the US Department of State, carrying members of the Bureau of International Narcotics and Law Enforcement Affairs. Following an uneventful flight from Kandahar, the crew landed at Lashkar Gah Airport. After touchdown, a truck crossed the active runway so the pilot-in-command initiated a turn to avoid the collision. Doing so, the aircraft veered off runway and collided with nearby houses. Both pilots as well as three people on the ground were killed. All other occupants were injured, some seriously.

Crash of a Cessna 402C in Freeport

Date & Time: Apr 21, 2006 at 0023 LT
Type of aircraft:
Registration:
C6-KEV
Survivors:
Yes
Schedule:
Fort Lauderdale – Freeport
MSN:
402C-0051
YOM:
1979
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3033
Circumstances:
At approximately 0423UTC on April 21, 2006 the pilot reported that approximately 20 miles out of Freeport, both hydraulic pressure lights illuminated on the annunciator panel. He extended the gear and noticed only the right gear safe light illuminated. The pilot obtained the assistance of a passenger, who retrieved the aircraft pilot operating handbook and read the appropriate procedures as the pilot followed the instructions for emergency gear extension. The pilot stated that he landed the aircraft on the right main gear, hoping this action would release the left main and nose gear. After realizing that this manoeuvre was not successful, he decided to initiate a go-around. Before he could get the aircraft airborne the left propeller made contact with the ground. The aircraft touched down approximately 9,000 feet from the threshold of runway 06; which has a total length of 11,000 feet. The aircraft travelled approximately 1,500 feet on its right main wheel before it veered off the left shoulder of the runway, struck several trees and finally came to rest pointing in a northwesterly direction. The approximate final position was measured to be 180 feet from the side of the runway. The aircraft left wing burst into flames. The left wing and left side of the fuselage was substantially damaged by fire. The four occupants escaped with only minor injuries.
Probable cause:
The investigation determines that the probable causes of this accident to be the following;
• Substandard maintenance that was performed. (Due to the improper flange on the hydraulic line, the hydraulic line came loose from its housing and depleted the fluid from the hydraulic
reservoir).
• Failure of the back up emergency blow down bottle system. It has been determined from inspection that the cable that connects the emergency blow down bottle system in the nose well of the aircraft to the T-handle in the cockpit, exhibited excessive play. Therefore even though the cable was pulled all the way to its fullest extent, it did not allow movement of the pin that would have provided activation of the system. Annual inspection report completed in December 2005 revealed that the portion of the Annual Inspection that required inspection of the emergency blow down bottle was not signed off by the mechanic as having been accomplished. However, the aircraft was returned to service with this discrepancy outstanding.
• Pilot’s lack of qualification and unfamiliarity with this aircraft, its systems and emergency procedures. ( Evidence of falsification of qualification and time requirement exists in pilot’s logbook).
• Pilot’s poor decision making and impaired judgement. (Possibility of impaired judgement due to pilot fatigue).
• Pilot’s failure in assessing the severity of his situation.
• Pilot’s failure to notify ATC of his problem. (Problem was discovered 20 miles prior to the accident).
• Pilot’s failure to properly assess the conditions for landing and maintain vigilant situational awareness while manoeuvring the aircraft after landing. (From post accident inspection, it was noted that the flaps were not extended for the landing. Had it been extended the aircraft glide path as well as the distance required for roll out after landing may have been greatly decreased).
• Pilot’s failure to take immediate action once he realized his predicament. (Pilot stated that after the propeller made contact with the ground, he decided to apply power and go around, but it was too late. Failure to act also can be attributed to possible pilot fatigue as (pilot was out all day shopping and then decided to leave at such a late hour) well as pilot’s unfamiliarity with aircraft systems and performance capabilities).
• Pilot’s failure to request Emergency Service Assistance. Had this service been requested in a timely manner, preparations could have been made to prevent the fire from spreading to the degree in which it did.
Final Report:

Crash of a Rockwell Sabreliner 75A in Alexandria

Date & Time: Apr 20, 2006 at 1505 LT
Type of aircraft:
Operator:
Registration:
JY-JAS
Flight Type:
Survivors:
Yes
Schedule:
Amman - Alexandria
MSN:
380-64
YOM:
1978
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew departed Amman-Marka Airport on a positioning flight to Alexandria, Egypt. On final approach, the aircraft was too high on the glide but the captain decided to continue. During the last segment, after the speed brakes were deactivated, the aircraft floated and landed too far down the runway. Unable to stop within the remaining distance, it overran and came to rest. While all three crew members escaped uninjured, the aircraft was damaged beyond repair.
Probable cause:
Wrong approach configuration on part of the captain who decided to landed while the aircraft was too high on the glide. Failure of the captain to initiate a go-around procedure after the copilot warned him three times about that.