Crash of a Boeing 737-2J8C in Khartoum

Date & Time: Jul 19, 1998 at 1105 LT
Type of aircraft:
Operator:
Registration:
ST-AFL
Survivors:
Yes
Schedule:
Khartoum - Dongola
MSN:
21170
YOM:
1975
Flight number:
SD122
Country:
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
91
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Khartoum-Haj Yussuf Airport, while climbing, the captain reported hydraulic problems and was cleared by ATC for an immediate return. After touchdown, several tires burst and the crew thought it was an engine malfunction so he deactivated the thrust reverser systems. Unable to stop within the remaining distance, the aircraft overran and collided with construction machines before coming to rest near a telecommunication relay. All 100 occupants evacuated safely while the aircraft was damaged beyond repair.

Crash of a Piper PA-31-310 Navajo in Kendall: 1 killed

Date & Time: Jul 17, 1998 at 1431 LT
Type of aircraft:
Operator:
Registration:
N7578L
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Kendall - Kendall
MSN:
31-7401201
YOM:
1974
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
6700
Circumstances:
An aircraft mechanic working abeam of the point on the runway that the airplane lifted off was attracted by the sound of engine roughness, and observed black smoke trailing from the left engine. The airplane continued to climb to about 150 feet above ground level, entered a series of shallow left turns at about the airport's east boundary at a slow speed, and then entered a rapid left roll and pitched down. The pilot transmitted an unreadable call on FAA tower frequency, but the words, 'we got a..' and 'engine' were clearly discernable. The airplane crashed in dense brush about 1.25 miles northeast of the airport. Contamination was found in the left engine fuel system. Post crash testing of the left fuel servo revealed it would not sustain a steady state fuel flow above about one half throttle due to contamination.
Probable cause:
The pilot's inadequate preflight inspection which led to fuel contamination and subsequent loss of engine power. Also causal was the pilot's failure to maintain single engine flying speed (VMC).
Final Report:

Crash of an Ilyushin II-78 in Asmara: 10 killed

Date & Time: Jul 17, 1998 at 0415 LT
Type of aircraft:
Operator:
Registration:
UR-UCI
Flight Type:
Survivors:
No
Schedule:
Burgas - Asmara
MSN:
0834 14444
YOM:
1978
Flight number:
UKS701
Location:
Country:
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
10
Circumstances:
Following an uneventful cargo flight from Burgas, the crew started a night approach to Asmara-Yohannes IV Airport. The visibility was relatively limited due to local patches of fog on approach. On final, at an altitude of 2,405 metres, the aircraft struck the slope of a mountain located 4,3 km short of runway 25. The aircraft disintegrated on impact and all 10 occupants were killed. The wreckage was found 72 metres below the summit. Remains still present at N15.304268 E38.959811 by December 2012.
Probable cause:
The following findings were identified:
- The crew decided to perform a visual approach to runway 25 while an instrument approach to runway 07 was the normal procedure,
- Limited visibility due to marginal weather conditions,
- ATC cleared the crew for an approach to runway 25 which was non-compliant according to published procedures,
- The crew failed to initiate a go-around procedure,
- The total weight of the aircraft at takeoff from Burgas Airport was at least 37 tons above MTOW and the crew was probably not aware of this situation.

Crash of a Cessna T303 Crusader near Nottingham

Date & Time: Jul 16, 1998 at 1833 LT
Type of aircraft:
Registration:
G-BSPF
Flight Type:
Survivors:
Yes
Schedule:
Sheffield – Nottingham
MSN:
303-00100
YOM:
1982
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
290
Captain / Total hours on type:
68.00
Circumstances:
The aircraft was en route from Sheffield City Airport to Nottingham where it was based. The pilot joined the traffic zone at Burton Joyce, an unofficial but well used Visual Reporting Point, at a height of about 1,000 feet. The weather was fine with good visibility and the pilot took the opportunity to view the house of the aircraft's co-owner located in the vicinity of Burton Joyce. While orbiting the house, the pilot felt a moderate 'bumping' sensation which he attributed to thermal activity rather than pre-stall buffet. The left wing suddenly dropped and the aircraft rolled through the vertical. The pilot applied corrective rudder and moved the control column forward which rolled the aircraft erect but he was unable to arrest the rate of descent because the engines did not appear to be developing full power. He therefore elected to carry out a forced landing with the landing gear retracted. On approaching the field, the aircraft struck a telegraph pole, yawed to the left and landed with a very high rate of descent before coming to a halt after a short ground slide. The pilot was unable to evacuate the aircraft because of his injuries but was rescued by local people who were quickly on the scene. There was no fire. The pilot stated that at the time the aircraft departed from normal flight, he was flying at about 100 kt with 60° of bank. The basic stalling speed of the aircraft in the configuration at the time was about 70 kt. Application of the correction for load factor in the turn would have given a stalling speed of 100 kt. The majority of eye witnesses stated that the aircraft was very low at the point at which it departed from normal flight, probably in the region of 300 feet above ground level.
Final Report:

Crash of a Mitsubishi MU-2B-25 Marquise in São Paulo

Date & Time: Jul 10, 1998
Type of aircraft:
Operator:
Registration:
PT-LTC
Flight Phase:
Survivors:
Yes
MSN:
314
YOM:
1975
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the takeoff roll at São Paulo-Congonhas Airport, the crew encountered an engine failure and decided to abort. The airplane was stopped on the main runway and all five occupants escaped uninjured. However, debris punctured a fuel tank and the aircraft caught fire and was severely damaged by fire and later written off.
Probable cause:
Uncontained failure on takeoff for unknown reasons.

Crash of a Let L-410UVP-E in Dhaka

Date & Time: Jun 27, 1998
Type of aircraft:
Operator:
Registration:
S2-ADD
Survivors:
Yes
Schedule:
Ishwardi - Dhaka
MSN:
91 26 18
YOM:
1991
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
While approaching Dhaka-Tejgaon Airport at an altitude of 4,000 feet, the crew encountered technical problems with the right engine they shut down. Few seconds later, the crew was able to restart the right engine but as the temperature of the turbine increased, he shut down the engine again. This time, he was unable to feather the propeller. Due to excessive drag, the aircraft lost height and the captain attempted an emergency landing in an open field. On landing, the aircraft lost its undercarriage and came to rest. All seven occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Failure of the right engine for unknown reasons. Failure of the automatic propeller pitch control mechanism was a contributing factor.

Crash of a Swearingen SA226AC Metro II in Montreal: 11 killed

Date & Time: Jun 18, 1998 at 0728 LT
Type of aircraft:
Operator:
Registration:
C-GQAL
Survivors:
No
Schedule:
Montreal - Peterborough
MSN:
TC-233
YOM:
1977
Flight number:
PRO420
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
11
Captain / Total flying hours:
6515
Captain / Total hours on type:
4200.00
Copilot / Total flying hours:
2730
Copilot / Total hours on type:
93
Aircraft flight hours:
28931
Circumstances:
On the morning of 18 June 1998, Propair 420, a Fairchild-Swearingen Metro II (SA226-TC), C-GQAL, took off for an instrument flight rules flight from Dorval, Quebec, to Peterborough, Ontario. The aircraft took off from Runway 24 left (L) at 0701 eastern daylight time. During the ground acceleration phase, the aircraft was pulling to the left of the runway centreline, and the right rudder was required to maintain take-off alignment. Two minutes later, Propair 420 was cleared to climb to 16 000 feet above sea level (asl). At 0713, the crew advised the controller of a decrease in hydraulic pressure and requested to return to the departure airport, Dorval. The controller immediately gave clearance for a 180° turn and descent to 8000 feet asl. During this time, the crew indicated that, for the moment, there was no on-board emergency. The aircraft initiated its turn 70 seconds after receiving clearance. At 0713:36, something was wrong with the controls. Shortly afterward came the first perceived indication that engine trouble was developing, and the left wing overheat light illuminated about 40 seconds later. Within 30 seconds, without any apparent checklist activity, the light went out. At 0718:12, the left engine appeared to be on fire, and it was shut down. Less than one minute later, the captain took the controls. The flight controls were not responding normally: abnormal right aileron pressure was required to keep the aircraft on heading. At 0719:19, the crew advised air traffic control (ATC) that the left engine was shut down, and, in response to a second suggestion from ATC, the crew agreed to proceed to Mirabel instead of Dorval. Less than a minute and a half later, the crew informed ATC that flames were coming out of the 'engine nozzle'. Preparations were made for an emergency landing, and the emergency procedure for manually extending the landing gear was reviewed. At 0723:10, the crew informed ATC that the left engine was no longer on fire, but three and a half minutes later, they advised ATC that the fire had started again. During this time, the aircraft was getting harder to control in roll, and the aileron trim was set at the maximum. Around 0727, when the aircraft was on short final for Runway 24L, the landing gear lever was selected, but only two gear down indicator lights came on. Near the runway threshold, the left wing failed upwards. The aircraft then rotated more than 90° to the left around its longitudinal axis and crashed, inverted, on the runway. The aircraft immediately caught fire, slid 2500 feet, and came to rest on the left side the runway. When the aircraft crashed, firefighters were near the runway threshold and responded promptly. The fire was quickly brought under control, but all occupants were fatally injured.
Probable cause:
Findings as to Causes and Contributing Factors:
- The crew did not realize that the pull to the left and the extended take-off run were due to the left brakes' dragging, which led to overheating of the brake components.
- Dragging of the left brakes was most probably caused by an unidentified pressure locking factor upstream of the brakes on take-off. The dragging caused overheating and leakage, probably at one of the piston seals that retain the brake hydraulic fluid.
- When hydraulic fluid leaked onto the hot brake components, the fluid caught fire and initiated an intense fire in the left nacelle, leading to failure of the main hydraulic system.
- When the L WING OVHT light went out, the overheating problem appeared corrected; however, the fire continued to burn.
- The crew never realized that all of the problems were associated with a fire in the wheel well, and they did not realize how serious the situation was.
- The left wing was weakened by the wing/engine fire and failed, rendering the aircraft uncontrollable.
Findings as to Risk:
- Numerous previous instances of brake overheating or fire on SA226 and SA227 aircraft had the potential for equally tragic consequences. Not all crews flying this type of aircraft are aware of its history of numerous brake overheating or fire problems.
- The aircraft flight manual and the emergency procedures checklist provide no information on the possibility of brake overheating, precautions to prevent brake overheating, the symptoms that could indicate brake problems, or actions to take if overheated brakes are suspected.
- More stringent fire-blocking requirements would have retarded combustion of the seats, reducing the fire risk to the aircraft occupants.
- A mixture of the two types of hydraulic fluid lowered the temperature at which the fluid would ignite, that is, below the flashpoint of pure MIL-H-83282 fluid.
- The aircraft maintenance manual indicated that the two hydraulic fluids were compatible but did not mention that mixing them would reduce the fire resistance of the fluid.
Other Findings:
- The master cylinders were not all of the same part number, resulting in complex linkage and master cylinder adjustments, complicated overall brake system functioning, and difficult troubleshooting of the braking system. However, there was no indication that this circumstance caused residual brake pressure.
- The latest recommended master cylinders are required to be used only with specific brake assembly part numbers, thereby simplifying adjustments, functioning, and troubleshooting.
- Although the emergency checklist for overheating in the wing required extending the landing gear, the crew did not do this because the wing overheat light went out before the crew initiated the checklist.
- The effect of the fire in the wheel well made it difficult to move the ailerons, but the exact cause of the difficulty was not determined.
Final Report:

Crash of a Rockwell Grand Commander 680FL in Helena: 1 killed

Date & Time: Jun 16, 1998 at 1800 LT
Operator:
Registration:
N446JR
Flight Type:
Survivors:
No
Schedule:
Kalispell - Helena
MSN:
680-1325-10
YOM:
1963
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1506
Captain / Total hours on type:
344.00
Aircraft flight hours:
17972
Circumstances:
The pilot of the Part 135 cargo flight was executing the 'full' ILS runway 27 approach at Helena Regional Airport in a non-radar environment. Although the approach calls for the pilot to maintain 7,000 feet until intercepting the glideslope, the aircraft impacted the terrain at 5,300 about 1.5 miles prior to reaching the point where the pilot should have crossed the Hauser NDB at an altitude of 6,741 feet. According to the approach plate, the aircraft should not have descended to an altitude below 5,400 feet until reaching the outer marker, which is located about five and one-half miles west of the impact site.
Probable cause:
The pilot's failure to maintain the correct altitude while turning inbound during a procedure turn to the ILS final approach course. Factors include hilly/mountainous terrain and clouds in the area where the course reversal was performed.
Final Report:

Crash of a Piper PA-61 Aerostar (Ted Smith 601) in Altoona: 3 killed

Date & Time: Jun 10, 1998 at 1304 LT
Registration:
N60721
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Altoona – Syracuse
MSN:
61-0736-8063360
YOM:
1980
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
1100
Circumstances:
Shortly after the airplane took off, a witness about 1 mile from the airport observed the airplane about 150 feet above the ground in a left turn, before it disappeared into the clouds. A witness across from where the airplane crashed stated he was in his shed when he heard the sound of an airplane overhead. When the sound faded and returned, like the airplane had circled above the shed, he stepped outside and looked for the airplane. He saw the airplane exit the clouds in a near vertical position and impact the ground. He described the engine noise as loud and smooth. The airplane impacted in a field about 3/4 miles from the departure airport and was consumed by a post crash fire. Streaks of oil were observed on the leading edge of the right horizontal stabilizer extending to its upper and lower surfaces. Disassembly of both engines did not reveal any pre-impact mechanical malfunctions. A weather observation taken after the accident reported included a visibility of 2 miles with light drizzle and mist, and the ceiling was 400 foot overcast. Witnesses described the weather at the accident site as '...pretty foggy,' and worse than the conditions reported at the airport.
Probable cause:
The pilot's failure to maintain airspeed due to spatial disorientation, which resulted in an inadvertent stall and subsequent collision with terrain. A factor in the accident was the low ceiling.
Final Report:

Crash of a Beechcraft 65-80 Queen Air in North Myrtle Beach

Date & Time: Jun 5, 1998 at 1531 LT
Type of aircraft:
Registration:
N215AB
Flight Type:
Survivors:
Yes
Schedule:
Malone - North Myrtle Beach
MSN:
LD-58
YOM:
1963
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
535
Captain / Total hours on type:
48.00
Aircraft flight hours:
6758
Circumstances:
After a 4.7 hour flight, while turning onto final, the airplane landed short. The pilot did not mention engine problems during a police interview. He subsequently told an FAA Inspector that the left engine failed, then later, that the right engine failed. He told the Safety Board that both engines failed. Adequate fuel was confirmed. The previous day, the right engine failed approaching another airport. The pilot performed a single-engine go-around, with landing gear and flaps down. He refused assistance and performed his own maintenance. He cleaned the fuel filters of both engines. During a ground runup, the right engine was hard to start, and required a high fuel flow to remain running. After the pilot re-cleaned the right fuel filter the engine ran fine. The flight was uneventful until the accident. Post-flight examination revealed all propeller blades bent back 90 degrees, with significant chordwise scoring on one blade per engine. The left engine fuel filter was relatively clean, with some brown residue which contained ferrous material. The right engine fuel filter was heavily coated with a white residue which contained aluminum, and brown material which contained ferrous material. The pilot received his multi-engine rating on April 22, 1998.
Probable cause:
The pilot's failure to follow emergency procedures, and his failure to maintain control of the airplane after a loss of power from one engine. Factors include fuel filter blockage, inadequate maintenance, and the pilot's lack of experience in multi-engine airplanes.
Final Report: