Crash of an IAI Arava 201 in Palacios

Date & Time: Jan 9, 2001
Type of aircraft:
Operator:
Registration:
316
Flight Type:
Survivors:
Yes
MSN:
31
YOM:
1976
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew completed the approach with a 13 knots tailwind component and landed too far down the runway, about half runway down. Unable to stop within the remaining distance, the aircraft overran and came to rest few dozen metres further. Both pilots escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Britten-Norman BN-2A-2 Islander in Mahdia: 3 killed

Date & Time: Jan 6, 2001
Type of aircraft:
Operator:
Registration:
8R-GFN
Flight Type:
Survivors:
No
Site:
Schedule:
Kato - Mahdia
MSN:
289
YOM:
1971
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The aircraft was completing a flight from Kato to Mahdia, carrying two pilots and one passenger on behalf of a public work company. On approach, the crew encountered marginal weather conditions when the twin engine aircraft struck the slope of Mt Ebini located 9 km short of runway and crashed in a wooded area. All three occupants were killed.

Crash of a Boeing 727-46F in Dundo: 1 killed

Date & Time: Jan 5, 2001
Type of aircraft:
Operator:
Registration:
S9-BAI
Flight Type:
Survivors:
Yes
Schedule:
Luanda – Dundo
MSN:
20078
YOM:
1968
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
1
Aircraft flight hours:
40300
Aircraft flight cycles:
30800
Circumstances:
On final approach to Dundo Airport, on the last segment, the pilot-in-command reduced both engines power when the aircraft lost height and landed hard. Upon impact, the right main gear collapsed. The aircraft slid for few dozen metres, veered off runway to the right and came to rest near houses. All 10 people on board the aircraft escaped uninjured while one people on the ground was killed. The aircraft was written off.

Crash of a Shaanxi Y-8 at Zhengzhou AFB: 14 killed

Date & Time: Jan 4, 2001
Type of aircraft:
Operator:
Registration:
31243
Flight Type:
Survivors:
No
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
14
Circumstances:
While approaching Zhengzhou AFB, the aircraft collided with a second China Air Force Shaanxi Y-8 registered 31242 and also carrying a crew of eight. One of the aircraft crashed short of runway while the second crashed onto a house. All 16 occupants in both aircraft were killed as well as six people in the house. The exact circumstances of the collision remains unknown.

Crash of a Shaanxi Y-8 at Zhengzhou AFB: 8 killed

Date & Time: Jan 4, 2001
Type of aircraft:
Operator:
Registration:
31242
Flight Type:
Survivors:
No
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
While approaching Zhengzhou AFB, the aircraft collided with a second China Air Force Shaanxi Y-8 registered 31243 and also carrying a crew of eight. One of the aircraft crashed short of runway while the second crashed onto a house. All 16 occupants in both aircraft were killed as well as six people in the house. The exact circumstances of the collision remains unknown.

Crash of a BAe 4101 Jetstream 41 in Charlottesville

Date & Time: Dec 29, 2000 at 2234 LT
Type of aircraft:
Operator:
Registration:
N323UE
Survivors:
Yes
Schedule:
Washington DC – Charlottesville
MSN:
41059
YOM:
1995
Flight number:
UA331
Crew on board:
3
Crew fatalities:
Pax on board:
15
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4050
Captain / Total hours on type:
1425.00
Copilot / Total flying hours:
4818
Copilot / Total hours on type:
68
Aircraft flight hours:
14456
Circumstances:
The twin-engine turboprop airplane touched down about 1,900 feet beyond the approach end of the 6,000-foot runway. During the rollout, the pilot reduced power by pulling the power levers aft, to the flight idle stop. He then depressed the latch levers, and pulled the power levers further aft, beyond the flight idle stop, through the beta range, into the reverse range. During the power reduction, the pilot noticed, and responded to a red beta light indication. Guidance from both the manufacturer and the operator prohibited the use of reverse thrust on the ground with a red beta light illuminated. The pilot pushed the power levers forward of the reverse range, and inadvertently continued through the beta range, where aerodynamic braking was optimum. The power levers continued beyond the flight idle gate into flight idle, a positive thrust setting. The airplane continued to the departure end of the runway in a skid, and departed the runway and taxiway in a skidding turn. The airplane dropped over a 60-foot embankment, and came to rest at the bottom. The computed landing distance for the airplane over a 50-foot obstacle was 3,900 feet, with braking and ground idle (beta) only; no reverse thrust applied. Ground-taxi testing after the accident revealed that the airplane could reach ground speeds upwards of 85 knots with the power levers at idle, and the condition levers in the flight position. Simulator testing, based on FDR data, consistently resulted in runway overruns. Examination of the airplane and component testing revealed no mechanical anomalies. Review of the beta light indicating system revealed that illumination of the red beta light on the ground was not an emergency situation, but only indicated a switch malfunction. In addition, a loss of the reverse capability would have had little effect on computed stopping distance, and none at all in the United States, where performance credit for reverse thrust was not permitted.
Probable cause:
The captain's improper application of power after responding to a beta warning light during landing rollout, which resulted in an excessive rollout speed and an inability to stop the airplane before it reached the end of the runway.
Final Report:

Crash of a Beechcraft B200 Super King Air in Rangeley: 2 killed

Date & Time: Dec 22, 2000 at 1716 LT
Registration:
N30EM
Survivors:
No
Site:
Schedule:
Rangeley – Boston – Portland – Rangeley
MSN:
BB-958
YOM:
1982
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
15500
Aircraft flight hours:
8845
Circumstances:
The pilot and passenger departed on a night IFR flight. Weather en route was a mixture of instrument and visual meteorological conditions. When the airplane was 17 miles southwest of its destination, the pilot was cleared for an instrument approach. At 9 miles, the pilot reported the airport in sight, and canceled his IFR clearance. The airplane continued to descend towards the airport on a modified left base until radar contact was lost at 3,300 feet msl. The pilot was in radio contact with his wife just prior to the accident. He advised her that he was on base for runway 32. Neither the pilot's wife, nor ATC received a distress call from the pilot. The airplane was located the next morning about 100 feet below the top of a mountain. The accident site was 7.9 miles from the airport, and approximately 1,200 feet above the airport elevation. Ground based weather radar recorded light snow showers, in the general vicinity of the accident site about the time of the accident, and satellite imagery showed that the airplane was operating under a solid overcast. A level path was cut through the trees that preceded the main wreckage. Examination of both engines and the airframe revealed no pre impact failures or malfunctions.
Probable cause:
The pilot-in-command's failure to maintain sufficient altitude while maneuvering to land, which resulted in a collision with terrain. Factors in the accident were the dark night, mountainous terrain, snow showers, clouds, and the pilot's decision to cancel his IFR clearance.
Final Report:

Crash of a BAe 125-700A in Jackson Hole

Date & Time: Dec 20, 2000 at 0126 LT
Type of aircraft:
Operator:
Registration:
N236BN
Survivors:
Yes
Schedule:
Austin – Jackson Hole
MSN:
257051
YOM:
1979
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
18120
Captain / Total hours on type:
1540.00
Copilot / Total flying hours:
3600
Copilot / Total hours on type:
1078
Aircraft flight hours:
8348
Circumstances:
The airplane was flying a full instrument landing system (ILS) approach to runway 18 at a high altitude airport (elevation 6,445 feet), in a mountainous area, at night. The control tower was closed for the night. The airport was located in a national park, and, therefore, the runway lights were not left on during the night. During non-tower operation hours, the procedure for turning on the runway lights called for the pilot to key the microphone multiple times on the Common Traffic Advisory Frequency (CTAF), which was the tower frequency. The copilot of the accident airplane made multiple attempts to turn on the runway lights using the UNICOM frequency, which had been the CTAF until about 6 months before the accident. The captain continued his landing approach below approach minimums without the runway lights being on. While in the landing flare, the captain reported that strong cross-winds and blowing snow created a "white-out" weather condition. The airplane touched down 195 feet left of the runway centerline in snow covered terrain between the runway and taxiway. Two ILS Runway 18 approach plates were found in the airplane. One was out of date and showed the UNICOM frequency as the CTAF. The other was current and showed the tower frequency as the CTAF. All four occupants escaped uninjured, among them the actress Sandra Bullock and the musician Bob Schneider.
Probable cause:
The pilot's failure to follow IFR approach procedures and perform a missed approach when the runway was not in sight below approach minimums. Contributing factors were the copilot's failure to follow current ILS approach procedures and use the correct frequency to turn on the runway lights, the snowy whiteout conditions near the ground, and the dark night light conditions.
Final Report:

Crash of a PZL-Mielec AN-2 in Anápolis

Date & Time: Dec 19, 2000 at 1200 LT
Type of aircraft:
Registration:
SP-FLU
Flight Type:
Survivors:
Yes
Schedule:
Canarana – Anápolis
MSN:
1G237-33
YOM:
1989
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total hours on type:
250.00
Circumstances:
After being ferried from Alta Floresta following maintenance, the pilot was completing a flight from Canarana to Anápolis with two passengers on board. Upon touchdown on runway 07, he encountered crosswinds from the left and lost control of the airplane that veered off runway to the right. It flew over a ravine, struck irregularities in the terrain and came to rest. All three occupants escaped with minor injuries and the aircraft was damaged beyond repair. The aircraft was still operated under a Polish registration SP-FLU while this was already cancelled. The owner was in the process of applying for a Brazilian certificate of registration.
Probable cause:
The following findings were identified:
- It was not possible to determine the contribution of the physiological aspect because the pilot was not found and his license had expired.
- At the critical moment of landing, a state of indecision was triggered in the pilot regarding the procedure to be adopted (landing or going around), impairing its decision-making capacity and causing delay in decision making.
- The pilot did not act adequately on the aircraft controls in order to counteract the action of the crosswind, allowing the aircraft to stand to the right of the approach axis and touch the right side of the runway. Subsequently, he was unable to prevent the left wings from climbing, causing the lower right wing to touch the ground and exit the runway.
- The pilot's decision not to go around immediately when he noticed the first signs of the aircraft's turning tendency, forced by the wind effect and, consequently, having lost full control of the aircraft, contributed to the worsening of the subsequent facts. The pilot acted belatedly when he decided to go around.
- The owner of the aircraft no longer verified that the technical qualification and the Certificate of Physical Capacity of the pilot were up to date for the performance of the air activity, as well as the certificates necessary for the operation of the aircraft. It also went against what prescribes the CTA certification, which establishes two pilots as the minimum crew for the aircraft.
- The left cross wind, associated with the inadequacy of the pilot's controls to counteract it, resulted in the right wing touching the ground, with consequent loss of control of the aircraft.
- The pilot failed to carry out a readaptation flight in the aircraft with a qualified instructor, being for more than three years without flying in the equipment.
Final Report:

Crash of a Casa 212 Aviocar 300 in Mokhotlong

Date & Time: Dec 16, 2000 at 0620 LT
Type of aircraft:
Operator:
Registration:
LDF-48
Flight Type:
Survivors:
Yes
Schedule:
Maseru - Mokhotlong
MSN:
390
YOM:
1989
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Maseru, the crew initiated the approach to Mokhotlong Airport. The left main gear touchdown 200 metres past the runway threshold. The right main gear landed few metres further. The gravel runway at Mokhotlong is 700 metres long. Unable to stop within the remaining distance, the aircraft overran and came to rest against a house about 100 metres past the runway end. All 13 occupants escaped uninjured while the aircraft was destroyed.
Probable cause:
Poor flight preparation on part of the crew who failed to check the wind component at Mokhotlong Airport. The crew though the wind was calm while locals confirmed the wind was relatively strong with gusts. Following a wrong approach configuration, the aircraft was too high and landed too far down the runway, reducing the landing distance available.