Crash of a Hawker 800XP in Carson City

Date & Time: Aug 28, 2006 at 1506 LT
Type of aircraft:
Operator:
Registration:
N879QS
Survivors:
Yes
Schedule:
Carlsbad – Reno
MSN:
258379
YOM:
1998
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6134
Captain / Total hours on type:
1564.00
Copilot / Total flying hours:
3848
Copilot / Total hours on type:
548
Aircraft flight hours:
6727
Circumstances:
The Hawker and the glider collided in flight at an altitude of about 16,000 feet above mean sea level about 42 nautical miles south-southeast of the Reno/Tahoe International Airport (RNO), Reno, Nevada, which was the Hawker's destination. The collision occurred in visual meteorological conditions in an area that is frequently traversed by air carrier and other turbojet airplanes inbound to RNO and that is also popular for glider operations because of the thermal and mountain wave gliding opportunities there. Before the collision, the Hawker had been descending toward RNO on a stable northwest heading for several miles, and the glider was in a 30-degree, left-banked, spiraling climb. According to statements from the Hawker's captain and the glider pilot, they each saw the other aircraft only about 1 second or less before the collision and were unable to maneuver to avoid the collision in time. Damage sustained by the Hawker disabled one engine and other systems; however, the flight crew was able to land the airplane. The damaged glider was uncontrollable, and the glider pilot bailed out and parachuted to the ground. Because of the lack of radar data for the glider's flight, it was not possible to determine at which points each aircraft may have been within the other's available field of view. Although Federal Aviation Regulations (FARs) require all pilots to maintain vigilance to see and avoid other aircraft (this includes pilots of flights operated under instrument flight rules, when visibility permits), a number of factors that can diminish the effectiveness of the see-and-avoid principle were evident in this accident. For example, the high closure rate of the Hawker as it approached the glider would have given the glider pilot only limited time to see and avoid the jet. Likewise, the closure rate would have limited the time that the Hawker crew had to detect the glider, and the slim design of the glider would have made it difficult for the Hawker crew to see it. Although the demands of cockpit tasks, such as preparing for an approach, have been shown to adversely affect scan vigilance, both the Hawker captain, who was the flying pilot, and the first officer reported that they were looking out the window before the collision. However, the captain saw the glider only a moment before it filled the windshield, and the first officer never saw it at all.
Probable cause:
The failure of the glider pilot to utilize his transponder and the high closure rate of the two aircraft, which limited each pilot's opportunity to see and avoid the other aircraft.
Final Report:

Crash of a Cessna 207A Skywagon in Caño Negro: 2 killed

Date & Time: Aug 11, 2006 at 1700 LT
Registration:
YV-492C
Flight Phase:
Survivors:
No
Schedule:
Caño Negro – Puerto Ayacucho
MSN:
207-0260
YOM:
1974
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
Shortly after takeoff from Caño Negro Airport, while climbing, the single engine aircraft entered an uncontrolled descent and crashed. Both occupants were killed.

Crash of a PZL-Mielec AN-28 in Bukavu: 17 killed

Date & Time: Aug 3, 2006
Type of aircraft:
Operator:
Registration:
9Q-COM
Survivors:
No
Site:
Schedule:
Lugushwa - Bukavu
MSN:
1AJ008-21
YOM:
1990
Location:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
14
Pax fatalities:
Other fatalities:
Total fatalities:
17
Circumstances:
While descending to Bukavu-Kamembe Airport, the crew encountered stormy weather with limited visibility due to rain falls. Too low, the twin engine aircraft impacted trees and crashed on hilly and wooded terrain located about 15 km from Bukavu Airport. The aircraft was destroyed and all 17 occupants were killed.
Probable cause:
Controlled flight into terrain.

Crash of a De Havilland DHC-2 Beaver in Hamburg: 5 killed

Date & Time: Jul 2, 2006 at 1038 LT
Type of aircraft:
Operator:
Registration:
D-FVIP
Flight Phase:
Survivors:
Yes
Site:
Schedule:
Hamburg - Hamburg
MSN:
1512
YOM:
1962
Location:
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
5
Aircraft flight hours:
17729
Circumstances:
The aircraft, owned by the German operator Himmelsschreiber Azur GmbH, was planned to make a sightseeing tour over Hamburg. This was a present from a father for his son aged 12. Less than 2 minutes after takeoff from the Hamburg-Norderelbe Seaplane Base, in the city center, the engine lost power and caught fire. The pilot elected to make an emergency landing when the aircraft lost height, collided with a wagon and crashed on a railway road located in a marshalling yard about 2 km south from the departure point, bursting into flames. The aircraft was totally destroyed by a post crash fire. Four passengers were killed while the pilot and a fifth passenger were seriously injured. The pilot died the following day.
Probable cause:
A technical problem occurred on a fuel supply line shortly after takeoff, at an altitude below 800 feet, resulting in the immediate failure of the engine that caught fire shortly later. There were no suitable terrain available for an emergency landing in the vicinity, which was considered as a contributing factor.
Final Report:

Crash of a Cessna 208B Grand Caravan in Vilanculos: 1 killed

Date & Time: Jun 30, 2006 at 1900 LT
Type of aircraft:
Operator:
Registration:
ZS-POG
Survivors:
Yes
Schedule:
Polokwane – Vilanculos
MSN:
208B-0396
YOM:
1994
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The single engine aircraft departed Polokwane on a charter flight to Madagascar with an intermediate stop in Vilanculos, carrying one passenger and two pilots. On final approach to Vilanculos Airport by night, the airplane collided with two palms and crashed 2 km short of runway. All three occupants were seriously injured and the aircraft was destroyed. Few hours after the crash, one of the pilots died from his injuries.

Crash of a Learjet 35A off Groton: 2 killed

Date & Time: Jun 2, 2006 at 1440 LT
Type of aircraft:
Operator:
Registration:
N182K
Survivors:
Yes
Schedule:
Atlantic City - Groton
MSN:
35-293
YOM:
1980
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
18750
Captain / Total hours on type:
7500.00
Copilot / Total flying hours:
3275
Copilot / Total hours on type:
289
Aircraft flight hours:
11704
Circumstances:
The crew briefed the Instrument Landing System approach, including the missed approach procedures. Weather at the time included a 100-foot broken cloud layer, and at the airport, 2 miles visibility. The approach was flown over water, and at the accident location, there was dense fog. Two smaller airplanes had successfully completed the approach prior to the accident airplane. The captain flew the approach and the first officer made 100-foot callouts during the final descent, until 200 feet above the decision height. At that point, the captain asked the first officer if he saw anything. The first officer reported "ground contact," then noted "decision height." The captain immediately reported "I got the lights" which the first officer confirmed. The captain reduced the power to flight idle. Approximately 4 seconds later, the captain attempted to increase power. However, the engines did not have time to respond before the airplane descended into the water and impacted a series of approach light stanchions, commencing about 2,000 feet from the runway. Neither crew member continued to call out altitudes after seeing the approach lights, and the captain descended the airplane below the decision height before having the requisite descent criteria. The absence of ground references could have been conducive to a featureless terrain illusion in which the captain would have believed that the airplane was at a higher altitude than it actually was. There were
no mechanical anomalies which would have precluded normal airplane operation.
Probable cause:
The crew's failure to properly monitor the airplane's altitude, which resulted in the captain's inadvertent descent of the airplane into water. Contributing to the accident were the foggy weather conditions, and the captain's decision to descend below the decision height without sufficient visual cues.
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 PZL-Mielec AN-2P in Göktepe

Date & Time: May 6, 2006 at 2000 LT
Type of aircraft:
Operator:
Registration:
ER-35538
Flight Phase:
Survivors:
Yes
Site:
Schedule:
Izmir – Adana
MSN:
1G114-50
YOM:
1970
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single engine aircraft was leased by a regional Turkish operator to perform a flight from Izmir to Adana with 4 pilots and 2 engineers from the Moldovan Company. En route, the crew encountered bad weather conditions with limited visibility due to heavy rain falls, and elected to make an emergency landing. The aircraft crash landed in a hilly terrain located near Göktepe. All 6 occupants were slightly injured while the aircraft was damaged beyond repair.

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 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: