Crash of a Swearingen SA226TC Metro II in Fort Wayne: 1 killed

Date & Time: Nov 9, 2000 at 0123 LT
Type of aircraft:
Operator:
Registration:
N731AC
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Fort Wayne – Milwaukee
MSN:
TC-255
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2870
Captain / Total hours on type:
75.00
Aircraft flight hours:
20885
Circumstances:
The airplane was destroyed on impact with trees and terrain after takeoff. A post-impact fire ensued. A courier stated that he put 14 cases and 5 bags into the airplane and that "everything took place as it normally does." A witness stated, "I heard a very low flying aircraft come directly over my house. ... It sounded very revved up like a chainsaw cutting through a tree at high speed." The accident airplane's radar returns, as depicted on a chart, exhibited a horseshoe shaped flight path. That chart showed that the airplane made a left climbing turn to a maximum altitude of 2,479 feet. That chart showed the airplane in a descending left turn after that maximum recorded altitude was attained. The operator reported the pilot had flown about 75 hours in the same make and model airplane and had flown about 190 hours in the last 90 days. The weather was: Wind 090 degrees at 7 knots; visibility 1 statute mile; present weather light rain, mist; sky condition overcast 200 feet; temperature 9 degrees C; dew point 9 degrees C. No pre-impact engine anomalies were found. NTSB's Materials Laboratory Division examined the annunciator panel and recovered light assemblies and stated, "Item '29' was a light assembly with an identification cover indicating that it was the '[Right-hand] AC BUS' light. Examination of the filaments in the two installed bulbs revealed that one had been stretched, deformed and fractured and the other had been stretched and deformed." The airplane manufacturer stated that the airplane's left-hand and right-hand attitude gyros are powered by the 115-volt alternating current essential bus. Two inverters are installed and one inverter is used at a time as selected by the inverter select switch. The inverter select switch is located on the right hand switch panel. The airplane was not equipped with a backup attitude gyro and was not required to be equipped with one. The airplane was certified with a minimum flight crew of one pilot. Subsequent to the accident, the operator transitioned "from the single pilot operation of our Fairchild Metroliner to the inclusion of a First Officer."
Probable cause:
The indicated failure of the right hand AC bus during takeoff with low ceiling. The factors were the low ceiling, night, and the excessive workload the pilot experienced on takeoff with an electrical failure without a second in command.
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.

Crash of an Antonov AN-32B in Luabo: 1 killed

Date & Time: Nov 7, 2000
Type of aircraft:
Operator:
Registration:
ER-AFA
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Luabo - Kinshasa
MSN:
3406
YOM:
1993
Location:
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
During the takeoff roll at Luabo Airport, at a speed of 180 km/h, the crew noted severe vibrations coming from the nose gear. Decision was taken to abort the takeoff procedure. Unable to stop within the remaining distance (the Luabo paved runway is 1,000 metres long), the aircraft overran, lost its nose gear and came to rest 500 metres further in a cemetery, bursting into flames. The copilot was killed while 10 other occupants escaped with minor injuries.
Probable cause:
It was determined that one of the tyres on the nose gear burst during the takeoff roll.

Crash of a Cessna 340A in Selma: 1 killed

Date & Time: Nov 6, 2000 at 0400 LT
Type of aircraft:
Operator:
Registration:
N12273
Flight Type:
Survivors:
Yes
Schedule:
Paso Robles – Selma
MSN:
340A-1536
YOM:
1982
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
19000
Captain / Total hours on type:
2000.00
Aircraft flight hours:
4915
Circumstances:
The airline transport rated pilot was returning an organ transplant nurse passenger to an uncontrolled, no facilities airport, with ground fog present about 0400 in the morning. The pilot had obtained two abbreviated preflight weather briefings while waiting for his passenger, and prior to departing at 0235. According to witnesses he attempted to land twice on runway 28, then he made an approach and attempted a landing on runway 10. Witnesses reported that the airport was engulfed in ground fog at the time of the approaches. They said that you could see straight up but not horizontally. The airplane collided with grape vineyard poles and canal/wash berms, about 250 feet short of the runway 10 displaced threshold. Approach charts for two airports with instrument approaches within 20 miles were found lying on the instrument panel glare shield. The passenger's car was parked at the uncontrolled airport.
Probable cause:
The pilot's improper decision to attempt a visual approach and landing in instrument meteorological conditions and his failure to follow instrument flight rules procedures.
Final Report:

Crash of a Boeing 747-2H7B in Paris

Date & Time: Nov 5, 2000 at 2157 LT
Type of aircraft:
Operator:
Registration:
TJ-CAB
Survivors:
Yes
Schedule:
Douala - Paris
MSN:
22378
YOM:
1981
Flight number:
UY070
Country:
Region:
Crew on board:
16
Crew fatalities:
Pax on board:
187
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
20250
Captain / Total hours on type:
12000.00
Copilot / Total flying hours:
14188
Copilot / Total hours on type:
9767
Aircraft flight hours:
48770
Aircraft flight cycles:
12872
Circumstances:
Following an uneventful flight from Douala, the crew started the descent to Paris-Roissy-CDG Airport by night and poor weather conditions. After touchdown on the wet runway 09R, the crew started the braking procedure when the aircraft went out of control, veered to the right off runway, crossed a grassy area, lost its nose gear and came to rest between both taxiways Z6 and Z7. All 203 occupants evacuated safely while the aircraft christened 'Mount Cameroon' was damaged beyond repair due to severe damages in the electronic bay because the nose landing gear penetrated the fuselage.
Probable cause:
The initial cause of the accident was the incomplete reduction of thrust on the left outer engine at the beginning of deceleration. This caused the de-activation of the automatic braking system and the non-extension of the n°1 thrust reverser. The inadvertent selection of full thrust on this engine after the landing created a high thrust asymmetry leading to the runway excursion. The lack of coordination and of joint control by the crew members, perhaps aggravated by the presence of third parties in the cockpit, contributed to the development of this situation.
Final Report:

Crash of an Antonov AN-24RV in Cheboksary

Date & Time: Nov 5, 2000
Type of aircraft:
Registration:
RA-46499
Flight Phase:
Survivors:
Yes
MSN:
2 73 083 02
YOM:
1972
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the takeoff roll at Cheboksary Airport, after V1 speed, the crew decided to abort. Unable to stop within the remaining distance, the aircraft overran, lost its nose gear and came to rest 270 metres further. All occupants escaped uninjured while the aircraft was damaged beyond repair. At the time of the accident, the visibility was reduced to 350 metres due to foggy conditions.

Crash of a Rockwell Grand Commander 690B in São Tomé

Date & Time: Nov 1, 2000 at 1745 LT
Operator:
Registration:
N6900K
Flight Type:
Survivors:
Yes
Schedule:
Luanda - São Tomé
MSN:
690-11441
YOM:
1978
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The pilot, sole on board, was completing a delivery flight from South Africa to the US via Luanda and São Tomé. Upon landing at São Tomé Airport, the left main gear collapsed. The aircraft slid on its belly for few dozen metres and came to rest. The pilot was uninjured.
Probable cause:
It was reported that the aircraft was unstable on final approach and not properly aligned with the runway centerline. This caused the aircraft to land hard in 'crab' configuration, causing the left main gear to collapse upon touchdown.

Crash of a Boeing 747-412 in Taipei: 83 killed

Date & Time: Oct 31, 2000 at 2318 LT
Type of aircraft:
Operator:
Registration:
9V-SPK
Flight Phase:
Survivors:
Yes
Schedule:
Singapore – Taipei – Los Angeles
MSN:
28023/1099
YOM:
1997
Flight number:
SQ006
Country:
Region:
Crew on board:
20
Crew fatalities:
Pax on board:
159
Pax fatalities:
Other fatalities:
Total fatalities:
83
Captain / Total flying hours:
11235
Captain / Total hours on type:
2017.00
Copilot / Total flying hours:
2442
Copilot / Total hours on type:
552
Aircraft flight hours:
18459
Aircraft flight cycles:
2274
Circumstances:
Singapore Airlines Flight 006 departed Singapore for a flight to Los Angeles via Taipei. Scheduled departure time at Taipei was 22:55. The flight left gate B-5 and taxied to taxiway NP, which ran parallel to runway 05L and 05R. The crew had been cleared for a runway 05L departure because runway 05R was closed because of construction work. CAA Taiwan had issued a NOTAM on Aug 31, 2000 indicating that part of runway 05R between Taxiway N4 and N5 was closed for construction between Sept. 13 to Nov. 22, 2000. Runway 05R was to have been converted and re-designated as Taxiway NC effective Nov. 1, 2000. After reaching the end of taxiway NP, SQ006 turned right into Taxiway N1 and immediately made a 180-degree turn to runway 05R. After approximately 6 second hold, SQ006 started its takeoff roll at 23:15:45. Weather conditions were very poor because of typhoon 'Xiang Sane' in the area. METAR at 23:20 included Wind 020 degrees at 36 knots gusting 56 knots, visibility - 600 meters, and heavy rainfall. On takeoff, 3.5 seconds after V1, the aircraft hit concrete barriers, excavators and other equipment on the runway. The plane crashed back onto the runway, breaking up and bursting into flames while sliding down the runway and crashing into other objects related to work being done on runway 05R. The aircraft wreckage was distributed along runway 05R beginning at about 4,080 feet from the runway threshold. The airplane broke into two main sections at about fuselage station 1560 and came to rest about 6,480 feet from the runway threshold.
Probable cause:
Findings related to probable causes:
- At the time of the accident, heavy rain and strong winds from typhoon "Xangsane" prevailed. At 2312:02 Taipei local time, the flight crewmembers of SQ006 received Runway Visual Range (RVR) 450 meters on Runway 05L from Automatic Terminal Information Service (ATIS) "Uniform". At 2315:22 Taipei local time, they received wind direction 020 degrees with a magnitude of 28 knots, gusting to 50 knots, together with the takeoff clearance issued by the local controller.
- On August 31, 2000, CAA of ROC issued a Notice to Airmen (NOTAM) A0606 indicating that a portion of the Runway 05R between Taxiway N4 and N5 was closed due to work in progress from September 13 to November 22, 2000. The flight crew of SQ006 was aware of the fact that a portion of Runway 05R was closed, and that Runway 05R was only available for taxi.
- The aircraft did not completely pass the Runway 05R threshold marking area and continue to taxi towards Runway 05L for the scheduled takeoff. Instead, it entered Runway 05R and CM-1 commenced the takeoff roll. CM-2 and CM-3 did not question CM-1's decision to take off.
- The flight crew did not review the taxi route in a manner sufficient to ensure they all understood that the route to Runway 05L included the need for the aircraft to pass Runway 05R, before taxiing onto Runway 05L.
- The flight crew had CKS Airport charts available when taxing from the parking bay to the departure runway; however, when the aircraft was turning from Taxiway NP to Taxiway NI and continued turning onto Runway 05R, none of the flight crewmembers verified the taxi route. As shown on the Jeppesen "20-9" CKS Airport chart, the taxi route to Runway 05L required that the aircraft make a 90-degree right turn from Taxiway NP and then taxi straight ahead on Taxiway NI, rather than making a continuous 180-degree turn onto Runway 05R. Further, none of the flight crewmembers confirmed orally which runway they had entered.
- CM-1's expectation that he was approaching the departure runway coupled with the saliency of the lights leading onto Runway 05R resulted in CM?1 allocating most of his attention to these centerline lights. He followed the green taxiway centerline lights and taxied onto Runway 05R.
- The moderate time pressure to take off before the inbound typhoon closed in around CKS Airport, and the condition of taking off in a strong crosswind, low visibility, and slippery runway subtly influenced the flight crew's decision?making ability and the ability to maintain situational awareness.
- On the night of the accident, the information available to the flight crew regarding the orientation of the aircraft on the airport was:
- CKS Airport navigation chart
- Aircraft heading references
- Runway and Taxiway signage and marking
- Taxiway NI centerline lights leading to Runway 05L
- Color of the centerline lights (green) on Runway 05R
- Runway 05R edge lights most likely not on
- Width difference between Runway 05L and Runway 05R
- Lighting configuration differences between Runway 05L and Runway 05R
- Para-Visual Display (PVD) showing aircraft not properly aligned with the Runway 05L localizer
- Primary Flight Display (PFD) information
The flight crew lost situational awareness and commenced takeoff from the wrong runway.
The Singapore Ministry of Transport (MOT) did not agree with the findings and released their own report. They conclude that the systems, procedures and facilities at the CKS Airport were seriously inadequate and that the accident could have been avoided if internationally-accepted precautionary measures had been in place at the Airport.
Final Report:

Crash of a Piper PA-60 Aerostar (Ted Smith 602P) in Coburg

Date & Time: Oct 30, 2000 at 1456 LT
Operator:
Registration:
D-IUAK
Flight Type:
Survivors:
Yes
MSN:
62-0920-8165044
YOM:
1981
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing on runway 12/30 which is 632 metres long, the twin engine aircraft was unable to stop within the remaining distance. It overran, lost its left wing and came to rest, bursting into flames. The pilot, sole on board, was slightly injured.

Crash of a Beechcraft 300 Super King Air in Concord

Date & Time: Oct 19, 2000 at 1538 LT
Registration:
N398DE
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Concord - San Jose
MSN:
FA-109
YOM:
1986
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
10868
Captain / Total hours on type:
35.00
Aircraft flight hours:
3801
Circumstances:
The twin turboprop airplane overran the runway, impacted two fences, and an occupied automobile after the airline transport pilot attempted to abort a takeoff. The pilot performed a rolling takeoff and was paying close attention to balancing the engine power and keeping runway centerline alignment. As the airplane accelerated, the pilot set the power above 80 percent and began an instrument scan. He then noted the airspeed indicator was reading zero with the needle resting on the peg. After a moment's hesitation, the pilot attempted to abort the takeoff by reducing the power levers to flight idle, and subsequently over the gate to ground fine. He reported to the FAA that he did not place the power controls into the reverse position. Air traffic controllers reported they observed the airplane with its nose wheel off of the ground approximately 3/4 of the way down the 4,602-foot long runway. The aircraft's left and right pitot/static systems were examined and tested after the accident, and no anomalies were noted. The pilot obtained verbal training on rejected/aborted takeoffs for the accident airplane. He obtained his type rating and 14 CFR 135 check-out in the accident airplane approximately 1 month prior to the accident. The pilot had accumulated a total of 10,867.5 hours of flight time, of which 34.7 hours were accumulated in the accident aircraft make and model. The pilot reported his total pilot-in-command flight time in the accident aircraft make and model as 20 hours, all of which were accumulated within the preceding 30 days of the accident. Examination of the airplane, the flight instruments and the pitot/static system found no explanation for the pilot reported lack of airspeed reading. The brakes were found to be fully functional. Review of the performance charts for the airplane disclosed that for the weight and ambient conditions of the takeoff, the airplane required 4,100 feet for an
accelerate-stop distance; the runway was 4,602 feet long.
Probable cause:
The pilot's delayed decision to abort the takeoff and his failure to utilize the propeller's reverse pitch function.
Final Report: