Crash of a Dassault Falcon 100 in Samedan: 2 killed

Date & Time: Feb 12, 2009 at 1612 LT
Type of aircraft:
Operator:
Registration:
VP-BAF
Flight Type:
Survivors:
Yes
Schedule:
Vienna - Samedan
MSN:
210
YOM:
1987
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
17269
Captain / Total hours on type:
739.00
Copilot / Total flying hours:
2591
Copilot / Total hours on type:
119
Aircraft flight hours:
6386
Circumstances:
On 12 February 2009, the Marcel Dassault/Bréguet Aviation Falcon 10 aircraft, registration VP-BAF, took off at 14:06 UTC from Vienna (LOWW) on a private flight under instrument flight rules (IFR) and an ATC flight plan Y, to Samedan (LSZS). Two crew members and one passenger were on board. After an uneventful flight, the IFR flight plan was cancelled at 14:56:32 UTC and the flight continued under visual flight rules (VFR). Over Samedan the crew were informed by the Samedan airport flight information service officer (FISO) that snow clearance work would be taking place on the runway and that they should expect a ten-minute delay. After approximately 15 minutes the crew initiated the approach. On landing, the aircraft made first contact with the ground by scraping the right wing on the left half of the runway and subsequently touched down with the right, and then the left main landing gear. It then drifted to the left and the left wing tip scraped a bank of snow running parallel to the runway. As a result it rotated anti-clockwise around its vertical axis and crashed into a frozen bank of snow about four metres high. The aircraft broke into two pieces as a result of the force of the impact. The two pilots suffered fatal injuries on the impact. The passenger was seriously injured. The aircraft was destroyed. Fire did not break out.
Probable cause:
The accident is attributable to the fact that the crew wanted to make a landing with inadequate visual references from an unfavorable initial position and as a result, after touchdown the aircraft collided with a snowbank running along the runway.
The following factors contributed to the accident:
• The rapidly changing weather conditions on the mountain aerodrome of Samedan were misjudged by the crew.
• A coordinated crew working method in terms of crew resource manage-ment was missing.
• The deactivation of the EGPWS, which meant that acoustic messages con-cerning the aircraft’s height above ground and bank angle were no longer available in the final phase of the approach up to the first contact with the runway.
• A snowbank up to four metres high ran along the edge of the runway.
Final Report:

Crash of an Antonov AN-2 in Pskov

Date & Time: Feb 11, 2009 at 1030 LT
Type of aircraft:
Operator:
Registration:
10 yellow
Flight Phase:
Survivors:
Yes
Schedule:
Pskov - Pskov
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after take off from Pskov Airport, while climbing to a height of about 50-70 metres, the crew encountered engine problems and elected to make an emergency landing. The aircraft lost height and crashed in a snow covered field located near the airport and came to rest. All 13 occupants escaped uninjured while the aircraft was damaged beyond repair. All passengers were skydivers (paratroopers) from the Marine Corps.
Probable cause:
Engine failure for unknown reasons.

Crash of a Cessna 208B Grand Caravan in Boma

Date & Time: Feb 11, 2009
Type of aircraft:
Operator:
Registration:
5Y-BUQ
Flight Type:
Survivors:
Yes
Schedule:
Juba – Boma
MSN:
208B-0366
YOM:
1993
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single engine aircraft was completing a humanitarian flight from Juba to Boma on behalf of the World Food Program, carrying one passenger and two pilots. Upon landing at Boma Airstrip, one of the landing gear collapsed. The aircraft slid for few dozen metres before coming to rest, bursting into flames. All three occupants escaped uninjured while the aircraft was destroyed by fire.

Crash of a De Havilland DHC-6 Twin Otter 100 in La Ronge

Date & Time: Feb 4, 2009 at 0915 LT
Operator:
Registration:
C-FCCE
Flight Phase:
Survivors:
Yes
Schedule:
La Ronge – Deschambeault Lake
MSN:
8
YOM:
1966
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
14000
Captain / Total hours on type:
11000.00
Copilot / Total flying hours:
625
Copilot / Total hours on type:
425
Circumstances:
The aircraft was taking off from a ski strip east of and parallel to Runway 36 at La Ronge. After the nose ski cleared the snow, the left wing rose and the aircraft veered to the right and the captain, who was the pilot flying, continued the take-off. The right ski, however, was still in contact with the snow. The aircraft became airborne briefly as it cleared a deep gully to the right of the runway. The aircraft remained in a steep right bank and the right wing contacted the snow-covered ground. The aircraft flew through a chain link fence and crashed into trees surrounding the airport. The five passengers and two crewmembers evacuated the aircraft with minor injuries. There was a small fire near the right engine exhaust that was immediately extinguished by the crew.
Probable cause:
Findings as to Causes and Contributing Factors:
1. Contamination on the wings of the aircraft was not fully removed before take-off. It is likely that asymmetric contamination of the wings created a lift differential and a loss of lateral control.
2. Although the operator was not authorized for short take-off and landing (STOL) take-off on this aircraft, the crew conducted a STOL take-off, which reduced the aircraft’s safety margin relative to its stalling speed and minimum control speed.
3. As a result of the loss of lateral control, the slow STOL take-off speed, and the manipulation of the flaps, the aircraft did not remain airborne and veered right, colliding with obstacles beside the ski strip.
Findings as to Risk:
1. The out of phase task requirements regarding the engine vibration isolator assembly, as listed in the operator’s maintenance schedule approval, results in a less than thorough inspection requirement, increasing the likelihood of fatigue cracks remaining undetected.
2. The right engine inboard and top engine mounts had pre-existing fatigue cracks, increasing the risk of catastrophic failure.
Other Findings:
1. The cockpit voice recorder (CVR) contained audio of a previous flight and was not in operation during the occurrence flight. Minimum equipment list (MEL) procedures for logbook entries and placarding were not followed.
2. The Transwest Air Limited safety management system (SMS) did not identify deviations from standard operating procedures.
Final Report:

Crash of an AMI Turbo DC-3-65TP in Mojave

Date & Time: Feb 4, 2009 at 0852 LT
Type of aircraft:
Operator:
Registration:
N834TP
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Mojave - Mojave
MSN:
12590
YOM:
1947
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
18000
Captain / Total hours on type:
1326.00
Aircraft flight hours:
17277
Circumstances:
During the takeoff roll, the airplane began to drift to the right. Despite the certified flight instructor's and student's attempts, they were unable to stop the yaw and drift. As the airplane was about to depart the runway, the pilots did not reduce the throttles or apply brakes as they felt that it would be safer to attempt to get airborne. After departing the runway surface, the airplane collided with a series of berms, which sheared off the left landing gear and left engine. The right landing gear collapsed, and the airplane came to rest in a nose down attitude. Post accident e examination revealed that the student pilot had inadvertently set the rudder trim to the full right position when he adjusted the rudder pedals during the prestart checks. The rudder trim was in the full right position for the takeoff, and found in the same position upon post accident inspection.
Probable cause:
The student pilot failed to follow the checklist and set the takeoff trim properly prior to takeoff resulting in a loss of directional control. Contributing to the accident were the certified flight instructor's inadequate supervision and delayed remedial action.
Final Report:

Crash of an ATR42-320 in Lubbock

Date & Time: Jan 27, 2009 at 0437 LT
Type of aircraft:
Operator:
Registration:
N902FX
Flight Type:
Survivors:
Yes
Schedule:
Fort Worth - Lubbock
MSN:
175
YOM:
1990
Flight number:
FX8284
Location:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13935
Captain / Total hours on type:
2052.00
Copilot / Total flying hours:
2109
Copilot / Total hours on type:
130
Aircraft flight hours:
28768
Aircraft flight cycles:
32379
Circumstances:
Aircraft was on an instrument approach when it crashed short of the runway at Lubbock Preston Smith International Airport, Lubbock, Texas. The captain sustained serious injuries, and the first officer sustained minor injuries. The airplane was substantially damaged. The airplane was registered to FedEx Corporation and operated by Empire Airlines, Inc., as a 14 Code of Federal Regulations Part 121 supplemental cargo flight. The flight departed from Fort Worth Alliance Airport, Fort Worth, Texas, about 0313. Instrument meteorological conditions prevailed, and an instrument flight rules flight plan was filed.
Probable cause:
The National Transportation Safety Board determines that the probable cause of this accident was the flight crew’s failure to monitor and maintain a minimum safe airspeed while executing an instrument approach in icing conditions, which resulted in an aerodynamic stall at low altitude.
Contributing to the accident were:
-the flight crew’s failure to follow published standard operating procedures in response to a flap anomaly,
-the captain’s decision to continue with the unstabilized approach
-the flight crew’s poor crew resource management,
-fatigue due to the time of day in which the accident occurred and a cumulative sleep debt which likely impaired the captain’s performance.
Final Report:

Crash of a Beechcraft F90-1 King Air in Mamuno

Date & Time: Jan 21, 2009
Type of aircraft:
Operator:
Registration:
A2-AHV
Survivors:
Yes
MSN:
LA-212
YOM:
1983
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On approach to Mamuno Airstrip, the pilot decided to initiate a go-around procedure. After the undercarriage were raised, the twin engine aircraft continued to descent and hit the runway surface. It slid for few dozen metres then veered off runway to the left and came to rest in a grassy area. The high engine temperature set the grass on fire and the aircraft was destroyed by fire. There were no injuries among the occupants.

Crash of a Fokker 100 in Tehran

Date & Time: Jan 19, 2009 at 1701 LT
Type of aircraft:
Operator:
Registration:
EP-CFN
Survivors:
Yes
Schedule:
Ardabil - Tehran
MSN:
11423
YOM:
1993
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
106
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing on runway 29L at Tehran-Mehrabad Airport, the right main gear collapsed. The aircraft veered off runway to the right and came to rest. All 114 occupants were uninjured and the aircraft was damaged beyond repair.
Probable cause:
Failure of the right main gear upon landing for unknown reasons.

Crash of a Beechcraft 100 King Air in Island Lake

Date & Time: Jan 16, 2009 at 2110 LT
Type of aircraft:
Operator:
Registration:
C-GNAA
Flight Type:
Survivors:
Yes
Schedule:
Thompson - Island Lake
MSN:
B-24
YOM:
1969
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3200
Captain / Total hours on type:
500.00
Copilot / Total flying hours:
1200
Copilot / Total hours on type:
620
Circumstances:
The crew was on a re-positioning flight from Thompson to Island Lake, Manitoba. On arrival in the Island Lake area, the crew commenced an instrument approach to Runway 12. On the final approach segment, the aircraft descended below the minimum descent altitude and the crew initiated a missed approach. During the missed approach, the aircraft struck trees. The crew was able to return for a landing on Runway 12 at Island Lake without further incident. The two crew members were not injured; the aircraft sustained damage to its right wing and landing gear doors. The accident occurred during hours of darkness at approximately 2110 Central Standard Time.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The crew conducted an Area Navigation (RNAV) approach for which they were not trained, with an aircraft that was not properly equipped nor approved for such purpose.
2. The aircraft descended 300 feet below the minimum descent altitude (MDA) as a result of a number of lapses, errors and adaptations which, when combined, resulted in the mismanaged approach.
3. The aural warning on the aircraft’s altitude alerter had been silenced prior to the approach, which precluded it from alerting the crew when the aircraft descended below minimum descent altitude.
4. The SkyNorth standard operating procedures for conducting a non-precision approach were not followed, which resulted in the aircraft descending below the minimum descent altitude. During the ensuing missed approach, the aircraft struck trees.
Findings as to Risk:
1. The lack of a more-structured training environment and the type of supervisory flying provided increased the risk that deviations from standard operating procedures (SOPs) would not be identified.
2. There are several instrument approach procedures in Canada that contain step-down fixes that are not displayed on global positioning system (GPS) units. This may increase the risk of collision with obstacles during step-downs on approaches.
Final Report:

Crash of a Gulfstream G200 in Oradea

Date & Time: Jan 16, 2009 at 1535 LT
Type of aircraft:
Operator:
Registration:
YR-TIG
Survivors:
Yes
Schedule:
Bucharest - Oradea
MSN:
012
YOM:
1999
Flight number:
TIH101
Location:
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13000
Captain / Total hours on type:
2000.00
Copilot / Total flying hours:
1600
Copilot / Total hours on type:
465
Circumstances:
Following an uneventful flight from Bucharest-Otopeni Airport, the crew started the approach to Oradea Airport in marginal weather conditions. On final approach, the pilot-in-command established a visual contact with the runway 19 and continued the descent. The aircraft landed 761 metres past the runway threshold. After touchdown, it was unable to stop within the remaining distance, overran and came to rest in a drainage ditch located 420 metres short of runway 01 threshold. All 13 occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
The contrast between the area covered with snow and the snow-cleared area (the runway) induced the pilots visual sensation about the runway threshold. This caused the crew to miscalculate the touchdown point, causing the aircraft to land too far down the runway.
Final Report: