Crash of an Antonov AN-26B in Ndjolé: 7 killed

Date & Time: Jan 17, 2003
Type of aircraft:
Operator:
Registration:
ER-AFT
Flight Type:
Survivors:
No
Schedule:
Brazzaville - Douala
MSN:
134 03
YOM:
1984
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
The aircraft departed Brazzaville on a delivery flight to Douala. While cruising by night over Gabon, the crew informed ATC about technical problems, declared an emergency and elected to divert to the nearest airport which was Ndjolé. This airfield was not equipped with any runway or approach lights nor any navigation aids. The crew completed several circuits over the city then people parked their cars along the airstrip so the crew was able to land. After four unsuccessful attempts, the crew tried to land but the aircraft flew over the runway without landing, passed over the Ogooué River and eventually crashed in a wooded and swampy area. The crew of two helicopters from the Gabonese Air Force found the wreckage the following day. The aircraft was destroyed and all seven occupants were killed. Until few days prior to the accident, the aircraft was operated by Pont Aviation which bankrupted, so it was transferred to another operator in Cameroon.
Probable cause:
It is believe that the crew was forced to make an emergency landing following a general failure of the navigation instruments in flight.

Crash of a Britten-Norman BN-2A-26 Islander in Pattaya

Date & Time: Jan 14, 2003 at 1300 LT
Type of aircraft:
Registration:
HS-RON
Flight Phase:
Survivors:
Yes
Schedule:
Pattaya - Pattaya
MSN:
156
YOM:
1970
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft departed Pattaya Airpark runway 10 for a local flight with 6 skydivers and one pilot on board. During initial climb, at a height of about 200-300 feet, the aircraft stalled and crashed in a cassava field located 1,500 metres from the runway end, near the village of Chak Ngaeo. All seven occupants were injured and the aircraft was damaged beyond repair.
Probable cause:
It is believed that the aircraft stalled following an engine failure while the flaps were still in the full down position.

Crash of an Avro RJ100 in Diyarbakir: 75 killed

Date & Time: Jan 8, 2003 at 2019 LT
Type of aircraft:
Operator:
Registration:
TC-THG
Survivors:
Yes
Schedule:
Istanbul – Diyarbakir
MSN:
E3241
YOM:
1994
Flight number:
TK634
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
75
Pax fatalities:
Other fatalities:
Total fatalities:
75
Captain / Total flying hours:
6309
Captain / Total hours on type:
473.00
Copilot / Total flying hours:
2052
Copilot / Total hours on type:
1802
Aircraft flight hours:
19289
Aircraft flight cycles:
16659
Circumstances:
On final approach to Diyarbakir Airport by night, the crew encountered marginal weather conditions with local patches of fog and limited visibility. On short final, in a slight nose down attitude, the aircraft struck the ground and crashed 900 metres short of runway 34, bursting into flames. Five passengers were seriously injured while 75 other occupants were killed. At the time of the accident, the crew was completing a VOR/DME approach to runway 34 that was not equipped with an ILS.
Probable cause:
It was determined that the crew established a visual contact with the runway lights when, on short final, due to the presence of local patches of fog, the pilot-in-command lost visual contact with the ground for few seconds. This caused the aircraft to descend below the MDA until it impacted the ground 900 metres short of runway threshold. Poor weather conditions were considered as a contributing factor.
Final Report:

Crash of a Raytheon 390 Premier I in Santo Domingo

Date & Time: Jan 8, 2003 at 1824 LT
Type of aircraft:
Registration:
N390RB
Survivors:
Yes
Schedule:
Santo Domingo - Santo Domingo
MSN:
RB-26
YOM:
2002
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft overran the runway and came to rest in a parking lot, while landing at Herrera International Airport, Santo Domingo, Dominican Republic, while on a 14 CFR Part 91 positioning flight. Visual meteorological conditions prevailed at the time and a visual flight rules flight plan was filed. The airplane received substantial damage and the airline transport-rated pilot, copilot, and two passengers received minor injuries. The flight originated from Las Americas International Airport, Santo Domingo, Dominican Republic, the same day, about 1810. The pilot stated they made a normal approach and landing on runway 19 at Herrera International Airport. Once on the ground they activated lift dump spoilers, but the system failed. They were unable to stop the airplane on the remaining runway. The airplane came to a stop, inverted beyond a street that is at the end of the runway.

Crash of a Beechcraft 1900D in Charlotte: 21 killed

Date & Time: Jan 8, 2003 at 0849 LT
Type of aircraft:
Operator:
Registration:
N233YV
Flight Phase:
Survivors:
No
Schedule:
Charlotte - Greenville
MSN:
UE-233
YOM:
1996
Flight number:
US5481
Crew on board:
2
Crew fatalities:
Pax on board:
19
Pax fatalities:
Other fatalities:
Total fatalities:
21
Captain / Total flying hours:
2790
Captain / Total hours on type:
1100.00
Copilot / Total flying hours:
706
Copilot / Total hours on type:
706
Aircraft flight hours:
15003
Aircraft flight cycles:
21332
Circumstances:
On January 8, 2003, about 0847:28 eastern standard time, Air Midwest (doing business as US Airways Express) flight 5481, a Raytheon (Beechcraft) 1900D, N233YV, crashed shortly after takeoff from runway 18R at Charlotte-Douglas International Airport, Charlotte, North Carolina. The 2 flight crewmembers and 19 passengers aboard the airplane were killed, 1 person on the ground received minor injuries, and the airplane was destroyed by impact forces and a post crash fire. Flight 5481 was a regularly scheduled passenger flight to Greenville-Spartanburg International Airport, Greer, South Carolina, and was operating under the provisions of 14 Code of Federal Regulations Part 121 on an instrument flight rules flight plan. Visual meteorological conditions prevailed at the time of the accident.
Probable cause:
The airplane’s loss of pitch control during takeoff. The loss of pitch control resulted from the incorrect rigging of the elevator control system compounded by the airplane’s aft center of gravity, which was substantially aft of the certified aft limit.
Contributing to the cause of the accident was:
1) Air Midwest’s lack of oversight of the work being performed at the Huntington, West Virginia, maintenance station,
2) Air Midwest’s maintenance procedures and documentation,
3) Air Midwest’s weight and balance program at the time of the accident,
4) the Raytheon Aerospace quality assurance inspector’s failure to detect the incorrect rigging of the elevator system,
5) the FAA’s average weight assumptions in its weight and balance program guidance at the time of the accident, and
6) the FAA’s lack of oversight of Air Midwest’s maintenance program and its weight and balance program.
Final Report:

Crash of a Piper PA-46-500TP Malibu Meridian in Dunkeswell

Date & Time: Dec 31, 2002 at 1749 LT
Registration:
N961JM
Survivors:
Yes
Schedule:
Chambéry – Dunkeswell
MSN:
46-97122
YOM:
2002
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8899
Captain / Total hours on type:
2095.00
Circumstances:
The pilot was carrying out an IFR flight from Chambery in France to Dunkeswell Aerodrome using Exeter Airport as his diversion. Before departure from Chambery he had checked the weather conditions at Exeter and other airfields in its vicinity from the available TAFs and METARs covering the period of the flight and he was satisfied that conditions were suitable. He had also contacted a friend who was also a commercial pilot at about 1530 hrs. This friend lived near Dunkeswell Aerodrome and had estimated the cloud base to be approximately 1,500 feet. The aircraft departed Chambery at 1605 hrs and, apart from some airframe icing on departure, it had an uneventful transit at FL270. Approaching the south coast of England, the aircraft was descended to FL60 and it left controlled airspace at Southampton in good VMC with the lights along the south coast clearly visible. The weather at Exeter at 1720 hrs was: surface wind 130°/08 kt, varying between 110° and 170°; visibility 6,000 metres; cloud SCT 005, BKN 012; temperature +9° C; dew point +8° C and QNH 1011 mb. With approximately 50 miles to run to his destination, the pilot attempted to contact Dunkeswell Radio but received no reply so he assumed the airfield had closed for the night. The lights of Dunkeswell village and the industrial site at the north-eastern edge of the aerodrome were visible but they had a milky appearance as if shining through scattered mist pockets. The aircraft was descended to 2,600 feet on the Exeter QNH and the main altimeter was set to the Dunkeswell QFE by subtracting 31 mb from the Exeter QNH to allow for the Dunkeswell elevation of 850 feet. The pilot was utilising two GPS navigation systems programmed to provide him with centreline information for Runway 23 on a CDI (Course Deviation Indicator) scale of 0.3 nm for full deflection. Whilst there was no runway lighting at Dunkeswell, the pilot had placed white reflective panels on the right edge of Runway 23. When illuminated by the aircraft landing light, these panels would show the right hand edge of the runway and also indicate the touchdown zone of the runway. The panels measured 18 cm by 9.5 cm and were mounted vertically on low, black plastic supports. The threshold for Runway 23 is displaced 290 metres from the road which runs along the northern aerodrome boundary and the first reflector was 220 metres beyond the displaced threshold. The reflectors had been positioned over a distance of 460 metres with the distances between them varying between 15 and 49 metres. The white centreline markings would also have been visible in the landing light once the aircraft was low enough. The end of the 46 metre wide runway was 280 metres from the last reflector. The pilot had carried out night approaches and landings to Runway 23 at Dunkeswell using similar visual references on many previous occasions. The pilot identified the lights of the industrial site earlier than he expected at six miles whilst maintaining 2,600 feet on the Exeter QNH. He cancelled his radar service from Exeter, which had also provided him with ranges and bearings from Dunkeswell, and made blind transmissions regarding his position and intentions on the Dunkeswell Radio frequency. Having commenced his final approach, the pilot noticed there was scattered cloud in the vicinity of the approach path. At about 2.5 nm from the runway threshold and approximately 800 feet agl, the pilot noticed a mist pocket ahead of the aircraft and so he decided to initiate a go-around and divert to Exeter. At that point the aircraft was configured with the second stage of flap lowered, the landing gear down and the airspeed reducing through 135 kt with all three aircraft landing lights selected ON. The pilot increased power and commenced a climb but he became visual with the runway once more and so he reduced power and resumed the approach. A high rate of descent developed and the radio altimeters automatic 50 feet audio warning sounded. The pilot started to increase engine power but he was too late to prevent the severe impact with terrain that followed almost immediately. The aircrafts wings were torn off as it passed between two trees and the fuselage continued across a grass field, remaining upright until it came to a stop. The passenger vacated the aircraft immediately through the normal exit in the passenger cabin and then returned to assist the pilot. Having turned off the aircraft's electrical and fuel systems the pilot also left the aircraft through the normal exit. There was a leak from the oxygen system, which had been disrupted in the accident and the pilot was unable to remove the fire extinguisher from its stowage due to the deformation of the airframe. He contacted Exeter ATC using his mobile telephone to inform them of the accident and they initiated the response of the emergency services.
Probable cause:
The investigation concluded that the accident had occurred due to an attempt to land at night in fog, at an airfield with no runway lighting and only limited cultural lighting to provide visual
orientation; these visual references were lost when the fog was entered. The aircraft impacted the treeline at the top of the valley 1,600 metres short of the displaced threshold and 200 metres to the right of the centreline.
Final Report:

Crash of an Antonov AN-12A in Nzagi

Date & Time: Dec 31, 2002
Type of aircraft:
Operator:
Registration:
D2-FBV
Flight Type:
Survivors:
Yes
MSN:
2 34 06 04
YOM:
1962
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Crashed in unknown circumstances at Nzagi Airport during the year 2002, date exact unknown.

Crash of an Embraer EMB-110P1 Bandeirante in Freetown

Date & Time: Dec 31, 2002
Registration:
9L-LBR
Survivors:
Yes
Schedule:
Freetown - Freetown
MSN:
110-411
YOM:
1982
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
14
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft was performing a flight from Freetown-Lungi Airport to Freetown-Hastings located southeast of the capital city. During the night, rebels sabotaged the runway with concrete and steel projectiles. After landing, the right main gear struck several obstructions and was torn off. The aircraft came to rest and was damaged beyond repair while all 16 occupants escaped uninjured. The exact date of the mishap remains unknown, somewhere in 2002.

Crash of a De Havilland DHC-3 Otter in Nikolai

Date & Time: Dec 28, 2002 at 1230 LT
Type of aircraft:
Registration:
N3904
Flight Type:
Survivors:
Yes
Schedule:
Nikolai – Wasilla
MSN:
54
YOM:
1954
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4000
Captain / Total hours on type:
400.00
Aircraft flight hours:
16437
Circumstances:
The commercial certificated pilot reported that just after takeoff in a wheel/ski equipped airplane, he heard a very loud bang, followed by a loud rattling noise. As he turned towards the departure airstrip, he had difficulty using the airplane's rudder pedals. Using a combination of aileron input and the remaining amount of rudder control, he was able to maneuver the airplane for a landing on the airstrip. He said that as the airplane passed over the approach end of the airstrip, it drifted to the right, and he initiated a go-around. The airplane subsequently collided with a stand of trees bordering the airstrip, and sustained structural damage to the wings, fuselage, and empennage. In a written statement to the NTSB, the pilot stated that he suspected that the right elevator's outboard and center hinges or hinge pins failed, allowing the right elevator to swing rearward and jam the airplane's rudder. An FAA airworthiness inspector traveled to the accident scene to examine the airplane. He reported that the right elevator was discovered about 150 feet behind the airplane, within the wreckage debris path through a stand of trees. He said that the right elevator sustained a significant amount of damage along the leading edge, which would normally be protected by the horizontal stabilizer. The FAA inspector examined the airplane's horizontal stabilizer in the area where the right and left elevators connect, and noted signs of new paint on the rivets that held the torque tube support assembly, indicating recent reinstallation or replacement of the torque tube support assembly. He indicated that the torque tube support assembly was installed at a slight angle to the right, which allowed the right elevator to eventually slip off of the center and outboard hinge pins. The inspector said that witness marks on the center and outboard hinge pins showed signs of excessive wear towards the outboard portion of each pin. The inspector noted that a review of the airplane's maintenance records failed to disclose any entries of repair/replacement of the elevator torque tube support assembly.
Probable cause:
An improper and undocumented major repair of the elevator torque tube support assembly by an unknown person, which resulted in an in-flight disconnection of the airplane's right elevator, and a jammed rudder. A factor associated with the accident is the inadequate inspection of the airplane by company maintenance personnel.
Final Report:

Crash of a Let L-410UVP in Mutsamudu: 1 killed

Date & Time: Dec 27, 2002 at 1215 LT
Type of aircraft:
Registration:
9XR-RB
Survivors:
Yes
Schedule:
Moroni - Mutsamudu
MSN:
81 06 36
YOM:
1981
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
13
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
While approaching Mutsamudu Airport, the crew encountered poor weather conditions with thunderstorm activity and heavy rain falls. The crew followed a holding pattern about 30 km away from the airport for weather improvement. Few minutes later, the crew started the descent to Mutsamudu-Ouani Airport. On approach at an altitude of 2,500 feet, the aircraft was struck by lightning. The crew elected to initiate a go-around procedure but the electrical system partially failed due to lightning and both gyro compasses and artificial horizons failed. Control was lost and the aircraft crashed in a wooded area located few km from the airport. A passenger was killed while 15 other occupants were injured.