Crash of a Pilatus PC-12/47 in Big Timber: 2 killed

Date & Time: Jun 24, 2006 at 1420 LT
Type of aircraft:
Operator:
Registration:
N768H
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Big Timber - Big Timber
MSN:
716
YOM:
2006
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
3200
Aircraft flight hours:
41
Circumstances:
The private pilot receiving instruction and his flight instructor departed on runway 06 with a headwind of 17 knots gusting to 23 knots. Witnesses said that the pilot had transmitted on Common Traffic Advisor Frequency the intention of practicing a loss of engine power after takeoff, and turning 180 degrees to return to the airport. Another witness said that the airplane pitched up 30 degrees while simultaneously banking hard to the right in an uncoordinated manner. He said that as the airplane rolled to the right, the nose of the airplane yawed down to nearly 45 degrees below the horizon. Subsequently, the airplane's wings rolled level, but the aircraft was still pitched nose down. He said the airplane appeared to be recovering from its dive. A witness said that the airplane appeared to be in a landing flare when he observed dirt and grass flying up behind the aircraft. He said the airplane's right wing tip and engine impacted terrain, and a fire ensued that consumed the airplane. Examination of the accident site revealed that the airplane's right wingtip hit a 10 inch in diameter rock and immediately impacted a wire fence 10 inches above the ground. Approximately 120 feet of triple wire fence continued with the airplane to the point of rest. No preimpact engine or airframe anomalies which might have affected the airplane's performance were identified. The weight and balance was computed for the accident airplane at the time of the accident and the center of gravity was determined to be approximately one inch forward of the forward limit.
Probable cause:
The flight instructor's failure to maintain an adequate airspeed while maneuvering, which led to an inadvertent stall.
Final Report:

Crash of an Excel Jet Sport Jet I in Colorado Springs

Date & Time: Jun 22, 2006 at 0953 LT
Type of aircraft:
Operator:
Registration:
N350SJ
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Colorado Springs - Colorado Springs
MSN:
001
YOM:
2006
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5307
Captain / Total hours on type:
11.00
Aircraft flight hours:
24
Circumstances:
According to the pilot, passenger, and several witnesses, during takeoff the light jet became airborne momentarily, and then banked aggressively to the left. It impacted the runway in a left wing low attitude and cartwheeled down the runway. An examination of the airplane's systems revealed no anomalies. Approximately 1.5 minutes before the airplane was cleared for takeoff, a De Havilland Dash 8 (DH-8) airplane departed. A wake turbulence study conducted by an NTSB aircraft performance engineer concluded that even slight movement in the atmosphere would have caused the circulation of the vortices near the accident site to decay to zero within two minutes, that is, before the time accident jet would have encountered the wake from the DH-8. The study states, in part: "Given the time of day of the accident, consistent reports of easterly surface wind speeds on the order of 6 to 7 knots, higher wind speeds aloft, and the mountainous terrain near Colorado Springs, it is unlikely that the atmosphere was quiescent enough to allow the wake vortices near the Sport-Jet to retain any significant circulation after two minutes. Furthermore, easterly surface winds would have blown the wake vortices well to the west of the runway by the time of the accident. Consequently, while in smooth air the wake vortices from the DH-8 that preceded Sport-Jet off of the runway may have retained enough circulation after two minutes to produce rolling moments on Sport-Jet on the order of the rolling moment available from the Sport-Jet's ailerons, it is most likely that the wake vortices were neither strong enough nor close enough to the Sport-Jet to cause the violent roll to the left reported by the pilot and witnesses to the accident."
Probable cause:
A loss of control for an undetermined reason during takeoff-initial climb that resulted in an in-flight collision with terrain.
Final Report:

Crash of a Boeing 747-200 in Medellin

Date & Time: Jun 7, 2006 at 0702 LT
Type of aircraft:
Operator:
Registration:
N922FT
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Medellín - Miami
MSN:
22768
YOM:
1982
Flight number:
TDX444
Country:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8000
Captain / Total hours on type:
830.00
Copilot / Total flying hours:
13000
Copilot / Total hours on type:
152
Aircraft flight hours:
78767
Circumstances:
The takeoff from Medellín-José María Córdova Airport runway 36 was initiated in rain falls. During the takeoff roll, the Engine Gas Temperature warning light came on, informing the crew about EGT problems on engines n°1 and 4. In the same time, the engine n°1 encountered technical problems. The captain decided to abort the takeoff procedure and started an emergency braking manoeuvre despite the aircraft' speed was 12 knots above the V1 speed. Unable to stop within the remaining distance, the aircraft overran, lost its nose gear and came to rest about 150 metres further. All five crew members evacuated safely while the aircraft was damaged beyond repair.
Probable cause:
The decision of the crew to abandon the takeoff procedure at a speed that was 12 knots above the V1 speed on a wet runway surface, following an EGT warning on engines n°1 and 4. The following contributing factors were identified:
- Failure of the crew to take into consideration the wet runway factor in the takeoff performances calculation,
- Absence of a flight dispatcher properly certified and qualified for the equipment,
- Failure of the engine number n°1 for undetermined reasons.
Final Report:

Crash of a Dornier DO328Jet in Manassas

Date & Time: Jun 3, 2006 at 0719 LT
Type of aircraft:
Operator:
Registration:
N328PD
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Manassas - Myrtle Beach
MSN:
3105
YOM:
2000
Crew on board:
3
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
15615
Captain / Total hours on type:
2523.00
Copilot / Total flying hours:
819
Copilot / Total hours on type:
141
Aircraft flight hours:
2830
Circumstances:
Prior to departure on the maintenance repositioning flight, the captain discussed with the first officer an uneven fuel balance that they could "fix" once airborne, and a 25,000 feet msl restriction because of an inoperative air conditioning/pressurization pack. The captain also commented about the right pack "misbehaving", and a bleed valve failure warning. The captain also commented about aborting below 80 knots for everything, except for the bleed shutoff valve. During the takeoff roll, a single chime was heard, and the first officer reported a bleed valve fail message. The captain responded, "ignore it." Another chime was heard, and the first officer reported "lateral mode fail, pusher fail." The captain asked about airspeed and was advised of an "indicated airspeed miscompare." The captain initiated the aborted takeoff approximately 13 seconds after the second chime was heard. The crew was unable to stop the airplane, and it went off the end of the runway, and impacted obstructions and terrain. According to the flight data recorder, peak groundspeed was 152 knots and the time the aborted takeoff was initiated, and indicated airspeed was 78.5 knots. The captain and the airplane owner's director of maintenance were aware of several mechanical discrepancies prior to the flight, and the captain had advised the first officer that the flight was for "routine maintenance," but that the airplane was airworthy. Prior to the flight the first officer found "reddish clay" in one of the pitot tubes and removed it. A mechanic and the captain examined the pitot tube, and determined the tube was not obstructed. The captain's pitot tube was later found to be partially blocked with an insect nest. A postaccident examination of the airplane and aircraft maintenance log revealed that no discrepancies were entered in the log, and no placards or "inoperative" decals were affixed in the cockpit.
Probable cause:
The partially blocked pitot system, which resulted in an inaccurate airspeed indicator display, and an overrun during an aborted takeoff. A factor associated with the accident was the pilot-in-command's delayed decision to abort the takeoff.
Final Report:

Crash of a PZL-Mielec AN-2R in Krępsko

Date & Time: May 24, 2006 at 1921 LT
Type of aircraft:
Operator:
Registration:
SP-FLY
Flight Phase:
Survivors:
Yes
Schedule:
Krępsko - Krępsko
MSN:
1G170-45
YOM:
1977
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4253
Captain / Total hours on type:
1334.00
Copilot / Total flying hours:
13640
Copilot / Total hours on type:
4000
Aircraft flight hours:
4282
Circumstances:
The single engine aircraft departed Krępsko Aerodrome at 1850LT on a local spraying mission part of a beetle control program. About 10 minutes after takeoff, a leak in the atomizer system forced the crew to return. Repairs were completed and the crew again took off 20 minutes later. Shortly after rotation, at a height of about 50-60 metres, the engine surged and suffered vibrations. The crew decided to return when the aircraft impacted birch trees and crashed in a wooded area, bursting into flames. Both pilots were uninjured while the aircraft was totally destroyed by a post crash fire.
Probable cause:
The likely cause of the accident was a leak in the fuel system within the engine compartment, resulting in the fuel supply to the carburetor to be cut off and causing the engine to stop. After the fuel leaked in the engine compartment, it ignited while contacting high temperature components, causing a major fire that destructed the aircraft.
Final Report:

Crash of a De Havilland DHC-2 Beaver in Hallo Bay

Date & Time: May 22, 2006 at 1300 LT
Type of aircraft:
Operator:
Registration:
N1543
Flight Phase:
Survivors:
Yes
Schedule:
Hallo Bay-Kodiak
MSN:
1687
YOM:
1967
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7460
Captain / Total hours on type:
40.00
Aircraft flight hours:
16360
Circumstances:
The commercial certificated pilot was departing a remote bay with five passengers in an amphibious float-equipped airplane on the return portion of a Title 14, CFR Part 135 sightseeing flight. The pilot began the takeoff run toward the north, with the wind from the north between 15 to 20 knots, and 4 to 6 foot sea swells. When the airplane had climbed to about 10 to 15 feet, the pilot said a windshear was encountered, which pushed the airplane down. The airplane's floats struck a wave, missed about 4 to 5 swells, and then struck another wave, which produced a loud "bang." The company guide, seated in the right front seat, told the pilot that the right float assembly was broken and displaced upward. The airplane cleared a few additional swells, and then collided with the water. Both float assemblies were crushed upward, and the left float began flooding. The guide exited the airplane onto the right float, and made a distress call via a satellite telephone. All occupants donned a life preserver as the airplane began sinking. The pilot said that after about 15 minutes, the rising water level in the airplane necessitated an evacuation, and all occupants exited into the water, and held onto the right float as the airplane rolled left. The airplane remained floating from the right float, and was being moved away from shore by wind and wave action. The pilot said that one passenger was washed away from the float within about 5 minutes, and two more passengers followed shortly thereafter. Within about 5 minutes after entering the water, the pilot said he lost his grip on the float, and does not remember anything further until regaining consciousness in a hospital. He was told by medical staff that he had been severely hypothermic. U.S. Coast Guard aircraft were already airborne on a training mission, and diverted to rescue the occupants. About 1320, a C-130 flew overhead, and began dropping inflatable rafts. The company guide was the only one able to climb into a raft. When the helicopters arrived, they completed the rescue using a hoist and a rescue swimmer. The passengers reported that they also were unable to hold onto the airplane after entering the water, became unconscious, and were severely hypothermic upon reaching a hospital. The airplane was not equipped with a life raft, and was not required to be so equipped.
Probable cause:
The pilot's inadequate evaluation of the weather conditions, and his selection of unsuitable terrain (rough water) for takeoff, which resulted in a collision with ocean swells during takeoff initial climb, and a hard emergency landing and a roll over. Factors contributing to the accident were a windshear, rough water, and buckling of the float assemblies when the airplane struck the waves.
Final Report:

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 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 De Havilland DHC-3 Otter in Lagopede Lake

Date & Time: Apr 19, 2006 at 1115 LT
Type of aircraft:
Operator:
Registration:
C-FKLC
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
255
YOM:
1958
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The Otter registered C-FKLC was on the frozen Lagopede Lake, ready for takeoff, when another Otter operated by Air Saguenay and registered C-FODT landed on the same lake. Upon touchdown, the pilot lost control of the aircraft that collided with the Otter waiting for departure. While the Otter registered C-FODT was slightly damaged, the Otter registered C-FKLC was damaged beyond repair after its right wing was torn off. The pilot, sole on board, was uninjured.

Crash of a Beechcraft B60 Duke in Gainesville: 3 killed

Date & Time: Apr 16, 2006 at 1153 LT
Type of aircraft:
Operator:
Registration:
N999DE
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Gainesville - Gainesville
MSN:
P-447
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
1500
Aircraft flight hours:
2901
Circumstances:
The airplane crashed into the terminal building following a loss of control on takeoff initial climb from runway 25. Witnesses reported that shortly after takeoff, the airplane banked sharply to the left, then it seemed to momentarily stabilize and commence a climb before beginning to roll to the left again. The airplane rolled to an inverted position, entered a dive, collided with the airport terminal building and exploded on impact. The entire airplane sustained severe fire and impact damage. Examination of the engines and propellers revealed no evidence of any discrepancies that would preclude normal operation. All the propeller blades displayed signatures indicative of high rotational energy at the time of impact, indicating that both propellers were rotating, not feathered, and the engines were operating at high power at the time of impact. Components of the autopilot system, specifically the pitch servo assembly and a portion of the roll servo assembly, were identified in the wreckage. The portion of the roll servo assembly found remained attached to a piece of skin torn from the airframe and consisted of the mounting bracket for the roll servo with the capstan bolted to the bracket, clearly indicating that this component had been reinstalled and strongly suggesting that the pilot reinstalled/reactivated all of the removed autopilot components the day before the accident. Maintenance personnel started an annual inspection on the airplane the month prior to the accident and found an autopilot installed in the airplane without the proper paperwork. The pilot explained to them that he designed and built the autopilot and was in the process of getting the proper paperwork for the installation of the system in his airplane. During the inspection, a mechanic found the aileron cable rubbing on the autopilot's roll servo capstan so the mechanic removed the roll servo along with the capstan. Additionally, mechanics disabled the autopilot's pitch servo and removed the autopilot control head. They were in the process of completing the inspection when the pilot asked for the airplane stating that he needed it for a trip. The pilot also asked that the airplane be returned to him without the interior installed. Two days before the accident, the airplane was returned to the pilot with the annual inspection incomplete. The autopilot control head, roll servo and capstan were returned to the pilot in a cardboard box on this date. A friend of the pilot reported that the day before the accident, the pilot completed reinstalling the seats and "other things" in order to fly the airplane the next day. It is possible that improper installation or malfunction of the autopilot resulted in the loss of control; however, the extent of damage and fragmentation of the entire airplane wreckage precluded detailed examination of the flight control and autopilot systems and hence a conclusive determination of the reason for the loss of control.
Probable cause:
The loss of control for an undetermined reason.
Final Report: