Crash of a Beechcraft 1900C-1 in Kinshasa

Date & Time: Apr 29, 2003 at 1930 LT
Type of aircraft:
Operator:
Registration:
TR-LFQ
Survivors:
Yes
Schedule:
Brazzaville - Kinshasa
MSN:
UC-80
YOM:
1989
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
13
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft departed Brazzaville on a charter flight to Kinshasa, carrying 13 passengers (all Air France crew members) and two pilots. On approach to Kinshasa, the crew encountered poor weather conditions with thunderstorm activity, heavy rain falls and strong crosswinds. After touchdown, the aircraft became unstable, deviated to the left and veered off runway. While contacting soft ground, the aircraft lost its undercarriage and slid for few dozen metres before coming to rest beside the runway. All 15 occupants escaped uninjured but the aircraft was damaged beyond repair.
Probable cause:
It is believed that the aircraft became unstable at touchdown due to strong crosswinds. A inappropriate reaction on part of the pilot-in-command, an overcorrection or a wrong configuration may have been a contributing factor.

Crash of a De Havilland DHC-6 Twin Otter 300 in Mulia

Date & Time: Apr 28, 2003 at 0730 LT
Operator:
Registration:
PK-WAR
Survivors:
Yes
Schedule:
Wamena - Mulia
MSN:
313
YOM:
1971
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Mulia Airport, the twin engine aircraft struck the ground and crashed few km short o runway. All four occupants were injured and the aircraft was damaged beyond repair.

Crash of a Yakovlev Yak-40 in Dnipropetrovsk

Date & Time: Apr 28, 2003
Type of aircraft:
Operator:
Registration:
UR-87918
Survivors:
Yes
MSN:
9 73 08 55
YOM:
1977
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
13
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On flare, the aircraft was unstable and rolled from right to left. When landing firmly on runway 09/27, the aircraft was not properly aligned and ran off runway to the right at a speed of 115 km/h. It eventually collided with a dike located 100 metres further. All 17 occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Vickers 836 Viscount in Democratic Republic of Congo

Date & Time: Apr 27, 2003
Type of aircraft:
Operator:
Registration:
9Q-CGL
Flight Phase:
Survivors:
Yes
MSN:
435
YOM:
1960
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The exact circumstances of this accident remains unknown. While landing on a 900 meters long gravel runway somewhere in DRC, one of the four engine was damaged. The crew later decided to takeoff on a three-engine configuration but a second engine failed during takeoff. The aircraft stalled and crashed near the runway end. There were no casualties.
Probable cause:

Crash of an Antonov AN-26 in Beni

Date & Time: Apr 25, 2003
Type of aircraft:
Operator:
Flight Type:
Survivors:
Yes
Schedule:
Kinshasa - Beni
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew attempted to land by night at Beni Airport which is not equipped for such operations. The aircraft landed too far down the runway, overran and collided with trees. All 10 occupants escaped with various injuries and the aircraft was damaged beyond repair.

Crash of a Socata TBM-700 in Mobile: 1 killed

Date & Time: Apr 24, 2003 at 2012 LT
Type of aircraft:
Operator:
Registration:
N705QD
Survivors:
No
Schedule:
Lawrenceville – Mobile
MSN:
231
YOM:
2002
Flight number:
LBQ850
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
10000
Captain / Total hours on type:
408.00
Aircraft flight hours:
1222
Circumstances:
A review of communications between Mobile Downtown Control Tower, and the pilot revealed that while on approach the pilot reported having a problem. The Ground Controller reported that he had the airplane in sight and cleared the flight to land on runway 18. The pilot stated that he had a "run away engine", and elected to shut down the engine and continued the approach. The Controller then cleared the pilot again to runway 18. The pilot then stated that he did not think that he was going to "make it." The airplane collided with a utility pole and the ground and burst into flames short of the runway. The post-accident examination of the engine found that the fuel control unit arm to the fuel control unit interconnect rod end connection was separated from the rod end swivel ball assembly. The swivel ball assembly was found improperly attached to the inboard side of the arm, with the bolt head facing inboard, instead of outboard, and the washer and nut attached to the arm's outboard side instead of the inboard side. The rod separation would resulted in a loss of power lever control. The published emergency procedures for "Power Lever Control Lose," states; If minimum power obtained is excessive: 1) reduce airspeed by setting airplane in nose-up attitude at IAS < 178 KIAS. 2) "inert Sep" switch--On. 3) if ITT >800 C "Inert Sep"--Off. 4) Landing Gear Control--Down. 5) Flaps--Takeoff. 6) Establish a long final or an ILS approach respecting IAS < 178 KIAS. 7) When runway is assured: Condition Lever to --Cut Off. 8) Propeller Governor Lever to-- Feather. 9) Flaps --Landing as required (at IAS <122 KIAS). 10) Land Normally without reverse. 11) Braking as required. The pilot stated to Mobile Downtown Control Tower, Ground Control that he had a "run away engine" and that he "had to shut down the engine". As a result of the pilot not following the published emergency procedures, the airplane was unable to reach the runway during the emergency.
Probable cause:
The improper installation of the power control linkage on the engine fuel control unit by maintenance personnel which resulted in a loss of power lever control, and the pilot's failure to follow emergency procedures and his intentional engine shutdown which resulted in a forced landing and subsequent inflight collision with a light pole.
Final Report:

Crash of a Swearingen SA226AC Metro II in Denver

Date & Time: Apr 15, 2003 at 2041 LT
Type of aircraft:
Operator:
Registration:
N229AM
Flight Type:
Survivors:
Yes
Schedule:
Gunnison - Denver
MSN:
TC-305
YOM:
1979
Flight number:
HKA1813
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4565
Captain / Total hours on type:
2179.00
Copilot / Total flying hours:
2517
Copilot / Total hours on type:
1400
Aircraft flight hours:
31643
Circumstances:
The flight was following a heavy jet on landing approach. The crew agreed to fly the approach at a slightly higher altitude than normal to avoid any possible wake turbulence. The first officer, who was flying the airplane, called for the landing gear to be lowered. When the captain placed the gear handle in the DOWN position, he noted red IN-TRANSIT lights. He recycled the landing gear, but got the same result. He consulted the emergency checklist and thought he had manually extended the landing gear because he "heard the normal 'clunk feel' and airspeed started to decay." In addition, when power was reduced to FLIGHT IDLE, the GEAR UNSAFE warning horn did not sound. The first officer agreed, noting 2,000 pounds of hydraulic pressure. The airplane landed wheels up. Propeller blade fragments penetrated the fuselage, breaching the pressure vessel. Postaccident examination revealed the nose gear had been partially extended but the main landing gear was retracted. The crew said the GEAR UNSAFE indication had been a recurring problem with the airplane. The problem had previously been attributed to a frozen squat switch in the wheel well.
Probable cause:
The failure of the landing gear system and the flight crew's failure to ascertain that the landing ear was down and locked. A contributing factor was the inadequate maintenance inspections performed by maintenance personnel.
Final Report:

Crash of a Grumman G-64 Albatross in Chetumal: 3 killed

Date & Time: Apr 14, 2003 at 1830 LT
Type of aircraft:
Registration:
N7026Y
Flight Type:
Survivors:
No
Schedule:
Tulum - Chetumal
MSN:
G-394
YOM:
1954
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The seaplane departed Tulum on a flight to Chetumal with three people on board. On approach to Chetumal Airport in good weather conditions, the pilot was cleared to land on runway 10 and initiated a left turn when control was slot. The aircraft rolled to the left, lost height and crashed 6 km short of the runway, bursting into flames. All three occupants were killed.

Crash of a Rockwell Shrike Commander 500S in Mount Pleasant

Date & Time: Apr 14, 2003 at 1140 LT
Operator:
Registration:
N19WL
Flight Phase:
Survivors:
Yes
Schedule:
Mount Pleasant - Mount Pleasant
MSN:
500-3160
YOM:
1973
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4578
Captain / Total hours on type:
280.00
Aircraft flight hours:
11617
Circumstances:
According to the pilot, he requested the refueler to top off his fuel tanks with "100 low lead fuel". After refueling, the pilot performed a preflight including taking fuel samples from under the wings, draining the rear fuel drain, and checking the fuel cap for security. The engine start, run-up, and taxi were uneventful. The airplane departed runway 17 and was in a positive rate of climb. At approximately 200 feet AGL the airplane began to lose power. Shortly after the pilot ensured that the throttle, propeller, and mixture controls were in the full forward position, the airplane lost power in both engines. The pilot executed an emergency off field landing. Examination of the wreckage revealed that the left wing had broken off and the aft cabin area was crushed. According to the refueler, he stated that he mistakenly used the Jet-A fuel truck instead of the AVGAS 100 low lead truck, and pumped 58 gallons of Jet-A into the airplane. Examination of the fuel samples taken from both engines revealed the left and right engine contained 70 percent of jet A fuel.
Probable cause:
The improper refueling of the airplane by airport personnel with the incorrect fuel grade that resulted in a total loss in engine power on both engines during initial climb. A factor was the inadequate preflight inspection by the pilot in command.
Final Report:

Crash of an Antonov AN-12BP in Sredny Island

Date & Time: Apr 11, 2003 at 2152 LT
Type of aircraft:
Registration:
RA-12981
Flight Type:
Survivors:
Yes
Schedule:
Moscow - Salekhard - Sredny Island
MSN:
00 347 104
YOM:
1970
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The four engine aircraft departed Moscow-Vnukovo on a cargo flight to Sredny Island with an intermediate stop in Salekhard, carrying six crew members, seven passengers and a load of 9,6 tons of various goods for the personnel of the drifting Polar Station "Severny Polyus 32" (North Pole 32). On final approach to the Sredny Ostrov Airfield, the crew encountered poor weather conditions and limited visibility. Too low, the aircraft struck the icy ground about 650 metres short of runway. It lost its undercarriage and slid for few dozen metres before coming to rest 165 metres to the right of the extended centerline. All 13 occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
The following findings were identified:
- Poor flight preparation,
- The crew did not receive a suitable weather briefing for the destination airport,
- Poor weather conditions at destination,
- The visibility was below minimums,
- The crew continued the approach without visual contact with the runway until the aircraft impacted ground,
- The crew failed to initiate a go-around procedure.