Crash of a Piper PA-31-325 Navajo in Belvidere: 1 killed

Date & Time: Dec 14, 2000 at 1303 LT
Type of aircraft:
Registration:
N120JB
Flight Type:
Survivors:
No
Schedule:
Vero Beach - Edenton
MSN:
31-7612050
YOM:
1976
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
647
Captain / Total hours on type:
336.00
Aircraft flight hours:
4903
Circumstances:
The flight was maneuvering in instrument meteorological conditions and was observed on radar making climbing and descending turns prior to making a final descending turn and being lost from radar. Examination of the crash site showed the airplane had impacted the terrain in a about a 90-degree nose down attitude. The crash site was about .09 miles from the last radar contact, when the airplane was 2,000 feet above ground level. Post crash examination of the airplane structure, flight controls, engines, propellers, and airplane systems showed no evidence of pre-crash failure or malfunction.
Probable cause:
The pilot's failure to maintain airplane control due to spatial disorientation while maneuvering in instrument meteorological conditions resulting in the airplane entering a descending turn and crashing into terrain.
Final Report:

Crash of a Cessna 421B Golden Eagle II in Norman: 2 killed

Date & Time: Dec 10, 2000 at 0448 LT
Registration:
N52KL
Flight Type:
Survivors:
No
Schedule:
Altus - Norman
MSN:
421B-0254
YOM:
1972
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
10000
Aircraft flight hours:
5315
Circumstances:
According to air traffic control communication and radar data, the flight was VFR over the top, approximately 7,900 feet, and requested an IFR clearance to the destination airport. The flight was issued an IFR clearance and, subsequently, was cleared for the localizer runway 03 approach. Radar data indicates that the airplane intercepted the localizer and began tracking inbound. Once the airplane reached the final approach fix, the airplane entered a shallow descent, but did not reach the MDA until after passing the missed approach point (MAP). The airplane flew past the MAP, continued to descend and over flew the runway. The final radar return was captured at 1,200 feet and one mile northeast of the airport, where the airplane was later located. The weather observation facility located at the airport reported that, 11 minutes before the accident, the winds were from 140 degrees at 6 knots, ceiling 200 feet overcast, visibility 1/4 miles in fog, temperature 45 degrees Fahrenheit and dew point 45 degrees Fahrenheit. A person who was at the airport at the time of the accident reported that the "clouds were low and visibility was poor." Toxicological testing performed on the pilot by the FAA's Civil Aeromedical Institute, Oklahoma City, Oklahoma, revealed the following: 0.121 (ug/ml, ug/g) amphetamine detected in blood, 0.419 (ug/ml, ug/g) amphetamine detected in liver, amphetamine detected in kidney, 4.595 (ug/ml, ug/g) methamphetamine detected in blood, 5.34 (ug/ml, ug/g) methamphetamine detected in liver, 3.715 (ug/ml, ug/g) methamphetamine detected in kidney, pseudoephedrine present in blood, and pseudoephedrine present in liver. The airframe and engines were examined and no anomalies were discovered that would have affected operation of the flight.
Probable cause:
The pilot's failure to follow the instrument approach procedure and his continued descent below the prescribed minimum descent altitude (MDA). Contributory factors were the pilot's physical impairment from drugs, the low ceiling, fog, and dark night light conditions.
Final Report:

Crash of a Casa 212 Aviocar 300 in Tres Esquinas

Date & Time: Dec 5, 2000
Type of aircraft:
Operator:
Registration:
FAC-1251
Flight Type:
Survivors:
Yes
Schedule:
Bogotá – Tres Esquinas
MSN:
450
YOM:
1991
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed Bogotá on a flight to Tres Esquinas, carrying a team of engineers who were involved in the refurbishment of the runway at Tres Esquinas Airport. On final approach, the crew encountered technical problems and attempted an emergency landing when the aircraft crashed in a wooded area located 3 km short of runway. Two occupants were injured.

Ground fire of a Douglas DC-9-32 in Atlanta

Date & Time: Nov 29, 2000 at 1550 LT
Type of aircraft:
Operator:
Registration:
N826AT
Survivors:
Yes
Schedule:
Atlanta - Akron
MSN:
47359/495
YOM:
1969
Flight number:
FL956
Crew on board:
5
Crew fatalities:
Pax on board:
92
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
12000
Captain / Total hours on type:
6000.00
Copilot / Total flying hours:
3100
Copilot / Total hours on type:
0
Aircraft flight hours:
78255
Aircraft flight cycles:
88367
Circumstances:
Shortly after takeoff, the airplane experienced electrical problems, including numerous tripped circuit breakers. The flight crew requested a return to airport. During the landing rollout, the lead flight attendant and air traffic control personnel reported to the flight crew that smoke was coming from the left side of the airplane; subsequently, the flight crew initiated an emergency evacuation on one of the taxiways. Examination of the airplane revealed fire damage to the left, forward areas of the fuselage, cabin, and forward cargo compartment. The greatest amount of fire damage was found just aft of the electrical disconnect panel located at fuselage station 237. There was no evidence that the drip shield normally installed over the disconnect panel was present at the time of the accident. Bluish stains caused by lavatory rinse fluid were observed on surfaces near the disconnect panel on the accident airplane and in the same areas on another of AirTran's DC-9 airplanes. Examination of one of the connectors from the disconnect panel on the accident airplane revealed light-blue and turquoise-green deposits on its internal surfaces and evidence of shorting between the connector pins. It could not be determined when the drip shield over the disconnect panel was removed; however, this likely contributed to the lavatory fluid contamination of the connectors. Following the accident, AirTran revised its lavatory servicing procedures to emphasize the importance of completely draining the waste tank to avoid overflows. Boeing issued an alert service bulletin recommending that operators of DC-9 airplanes visually inspect the connectors at the FS 237 disconnect panel for evidence of lavatory rinse fluid contamination and that they install a drip shield over the disconnect panel. Boeing also issued a service letter to operators to stress the importance of properly sealing floor panels and adhering to lavatory servicing procedures specified in its DC-9 Maintenance Manual. The Safety Board is aware of two incidents involving the military equivalent of the DC-9 that involved circumstances similar to the accident involving N826AT. Drip shields were installed above the FS 237 disconnect panels on both airplanes.
Probable cause:
The leakage of lavatory fluid from the airplane's forward lavatory onto electrical connectors, which caused shorting that led to a fire. Contributing to the accident were the inadequate servicing of the lavatory and the failure of maintenance to ensure reinstallation of the shield over the fuselage station 237 disconnect panel.
Final Report:

Crash of a Swearingen SA227AC Metro III in Trujillo

Date & Time: Nov 28, 2000 at 0625 LT
Type of aircraft:
Operator:
Registration:
N3107P
Flight Type:
Survivors:
Yes
Schedule:
Lima - Trujillo
MSN:
AC-496
YOM:
1981
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On November 28, 2000, at 0625 eastern standard time, a Fairchild SA227AC transport category airplane, N3107P, was substantially damaged while landing with an unsafe gear indication on the right main landing gear at the Trujillo International Airport, near Trujillo, Peru. The two commercial pilots aboard the cargo flight were not injured. The airplane was owned by Joda LLC, of Town and Country, Missouri, and was being operated as a cargo freighter by Aero Condor S.A., of Lima, Peru. Visual meteorological conditions prevailed for the cargo flight for which a VFR flight plan was filed. The scheduled cargo flight originated from the Lima International Airport, near Lima, Peru, approximately 0530. The operator reported that the flight crew had reported a complete loss of hydraulic power prior to initiating the approach. The flight crew was not able to extend the right main landing gear due to a leak in a hydraulic line in the right landing gear well. The runway was foamed and the crew performed an emergency landing with the other two landing gears extended. Examination of the airplane by the operator revealed structural damage to the right wing and the underside section of the tail section of the airplane. The right engine and the 4-propeller blades for the right engine were also damaged. Both pilots were uninjured.

Crash of an Aérospatiale SN.601 Corvette in Córdoba: 1 killed

Date & Time: Nov 25, 2000 at 0604 LT
Registration:
EC-DQG
Flight Type:
Survivors:
Yes
Schedule:
Málaga - Córdoba
MSN:
27
YOM:
1976
Flight number:
MYO611
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
6232
Captain / Total hours on type:
3251.00
Copilot / Total flying hours:
1875
Copilot / Total hours on type:
22
Aircraft flight hours:
5743
Circumstances:
The aircraft departed Málaga-Pablo Ruiz Picasso Airport at 0543LT on a positioning flight to Córdoba. On board were two pilots who were flying to Córdoba to pick up a medical team for a transplantation mission. Fifteen minutes after takeoff, the crew started the descent but encountered poor visibility due to the night and foggy conditions. At that moment, the horizontal visibility was 300 metres and the vertical visibility about 500 feet. As Córdoba Airport was not equipped with an ILS system, the crew decided to attempt an approach via a GPS system. On final approach, the aircraft was too low, struck a utility pole then crashed onto a uninhabited house located 1,500 metres short of runway 21. The aircraft was destroyed, one pilot was killed and the second was seriously injured.
Probable cause:
The accident occurred when the aircraft crew carried out an approach maneuver to Córdoba Airport in conditions of very reduced visibility in fog, based exclusively on the GPS receiver of the communications navigation system installed in the aircraft and without reliably monitoring the ground separation. It is likely that the decision to carry out this maneuver was influenced by a pressure to complete the mission, self-generated by the crew members, or self-generated by the pilot-in-command, and induced or not by him and the copilot, as a consequence of an urgent humanitarian operation that entrusted about the confidence of the pilot-in-command and his experience, the navigation system that equipped the aircraft and the knowledge of the destination airport.
Final Report:

Crash of a Douglas DC-9-51 in Conakry

Date & Time: Nov 13, 2000 at 1813 LT
Type of aircraft:
Operator:
Registration:
9G-ADY
Survivors:
Yes
Schedule:
Accra – Abidjan – Monrovia – Freetown – Conakry
MSN:
47679
YOM:
1975
Flight number:
GH530
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
42
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
45600
Aircraft flight cycles:
64300
Circumstances:
While descending to Conakry-Gbessia Airport, the crew encountered technical problems with the undercarriage that could not be lowered. Several attempts were made to lower the gear manually but this was unsuccessful. The crew decided to complete a belly landing. After touchdown, the aircraft slid for few dozen metres and came to rest on the runway. All 50 occupants evacuated safely and the aircraft was damaged beyond repair.

Crash of a Beechcraft E90 King Air in Reims: 2 killed

Date & Time: Nov 13, 2000 at 1338 LT
Type of aircraft:
Operator:
Registration:
F-GIML
Flight Type:
Survivors:
No
Schedule:
Paris - Reims
MSN:
LW-180
YOM:
1976
Flight number:
CPH030
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
6568
Captain / Total hours on type:
2000.00
Copilot / Total flying hours:
1006
Copilot / Total hours on type:
670
Aircraft flight hours:
8772
Aircraft flight cycles:
8441
Circumstances:
The twin engine aircraft departed Paris-Le Bourget Airport at 1309LT on a flight to Reims-Champagne with two pilots on board, one instructor and one pilot that should complete a transition program. While descending at an altitude of 2,000 to Reims-Prunay Airport, the crew informed ATC that he would perform an exercise consisting of a go-around procedure with the simulation of an engine failure. On a left downwind approach to runway 25, the crew started the exercise when the aircraft rolled to the left, lost height and crashed in an open field, bursting into flames. The wreckage was found 425 metres short of runway 25 and both pilots were killed.
Probable cause:
The accident resulted from the performance of a single-engine go-around exercise at low height, in an unfavorable configuration.
Final Report:

Crash of a Cessna 425 Conquest I in Idaho Falls: 2 killed

Date & Time: Nov 10, 2000 at 1215 LT
Type of aircraft:
Registration:
N41054
Flight Type:
Survivors:
No
Schedule:
Idaho Falls - Idaho Falls
MSN:
425-0172
YOM:
1983
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
8000
Aircraft flight hours:
4027
Circumstances:
The accident aircraft had recently had maintenance work performed on its autofeather system pressure sensing switches, due to reports of the left engine not autofeathering properly in flight. The purpose of the accident flight was to verify proper inflight operation of the autofeather system following the maintenance work on the autofeather pressure sensing switches and a successful ground check of the autofeather system. Air traffic control (ATC) communications recordings disclosed that the pilot called ready for takeoff from runway 2 approximately 1207, and requested to orbit above the airport at 8,000 feet (note: the airport elevation is 4,740 feet.) The pilot subsequently reported established in a hold above the airport at 8,000 feet approximately 1213, and was instructed by ATC to report leaving the hold. Approximately 1215, an abbreviated radio transmission, "zero five four," was recorded. The Idaho Falls tower controller responded to this call but never got a response in return from the accident aircraft, despite repeated efforts to contact the aircraft. Witnesses reported that the aircraft banked to the left, or to the west, and that it entered a spiral from this bank and crashed (one witness reported the aircraft was flying at 200 to 300 feet above ground level when it entered this bank, and that it performed a "skidding" or "sliding" motion part way through the bank, about 1 second before entering the spiral.) The aircraft crashed about 2 miles north of the airport. On-site examination disclosed wreckage and impact signatures consistent with an uncontrolled, relatively low-speed, moderate to steep (i.e. greater than 22 degrees) angle, left-wing-low impact on an easterly flight path. No evidence of flight control system malfunction was found, and a large quantity of jet fuel was noted to be aboard the aircraft. Post-accident examination of the aircraft's engines indicated that the left engine was most likely operating in a low power range and the right engine was most likely operating in a mid to high power range at impact, but no indications of any anomalies or distress that would have precluded normal operation of the engines prior to impact was found. Post-accident examination of the aircraft's propellers disclosed indications that 1) both propellers were rotating at impact, 2) neither propeller was at or near the feather position at impact, 3) both propellers were being operated with power at impact (exact amount unknown), 4) both propellers were operating at approximately 14º to 20º blade angle at impact, and 5) there were no propeller failures prior to impact. Post-accident examination of the autofeather pressure sensing switches disclosed evidence of alterations, tampering, or modifications made in the field on all but one switch (a replacement switch, which had been installed just before the accident flight during maintenance) installed on the aircraft at the time of the accident. All switches except for the replacement switch operated outside their design pressure specifications; the replacement switch operated within design pressure specifications. Examination of the switches indicated that all switches were installed in the correct positions relative to high- or low-pressure switch installations. Engineering analyses of expected autofeather system performance with the switches operating at their "as-found" pressure settings (vice at design pressure specifications) did not indicate a likelihood of any anomalous or abnormal autofeather system operation with the autofeather switches at their "as-found" pressure settings. Also, cockpit light and switch evidence indicated that the autofeather system was not activated at the time of impact. The combination of probable engine power and propeller pitch on the left engine (as per the post-accident engine and propeller teardown results) was noted to be generally consistent with the "zero-thrust" engine torque and propeller RPM settings specified for simulated single-engine practice in the aircraft Information Manual.
Probable cause:
The pilot-in-command's failure to maintain adequate airspeed with an asymmetric thrust condition, resulting in a loss of aircraft control. A factor was an asymmetric engine thrust condition, which was present for undetermined reasons.
Final Report:

Crash of a Basler BT-67 in Chilanga

Date & Time: Nov 9, 2000
Type of aircraft:
Operator:
Registration:
FAS119
Flight Type:
Survivors:
Yes
MSN:
6204
YOM:
1943
Country:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing at Chilanga-Los Comandos Airport, the crew encountered technical problems with the brakes. The aircraft veered off runway and collided with trees. There were no casualties but the aircraft was damaged beyond repair.
Probable cause:
Loss of control after touchdown due to technical problems with the brakes.