Crash of a Mitsubishi MU-2B-60 Marquise in Baltimore: 1 killed

Date & Time: May 14, 2004 at 0724 LT
Type of aircraft:
Operator:
Registration:
N755AF
Flight Type:
Survivors:
No
Site:
Schedule:
Philadelphia - Baltimore
MSN:
755
YOM:
1980
Flight number:
EPS101
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
6800
Aircraft flight hours:
6951
Circumstances:
The pilot was finishing his third round-trip, Part 135 cargo flight. The first round trip began the previous evening, about 2150, and the approach back to the origination airport resulted in a landing on runway 15R at 2305. The second approach back to the origination airport resulted in a landing on runway 28 at 0230. Prior to the third approach back to the airport, the pilot was cleared for, and acknowledged a visual approach to runway 33R twice, at 0720, and at 0721. However, instead of proceeding to the runway, the airplane flew north of it, on a westerly track consistent with a modified downwind to runway 15L. During the westerly track, the airplane descended to 700 feet. Just prior to an abeam position for runway 15L, the airplane made a "sharp" left turn back toward the southeast, and descended into the ground. Witnesses reported the airplane's movements as "swaying motions as if it were going to bank left, then right, and back left again," and "the nose...pointing up more than anything...but doing a corkscrew motion." Other witnesses reported the "wings straight up and down," and "wings vertical." Tower controllers also noted the airplane to be "low and tight," and "in an unusually nose high attitude close to the ground. It then "banked left and appeared to stall and then crashed." A post-flight examination of the wreckage revealed no evidence of mechanical malfunction. The pilot, who reported 6,800 hours of flight time, had also flown multiple round trips the previous two evenings. He had checked into a hotel at 0745, the morning prior to the accident flight, checked out at 1956, the same day, and reported for work about 1 hour before the first flight began.
Probable cause:
The pilot's failure to maintain airspeed during a sharp turn, which resulted in an inadvertent stall and subsequent impact with terrain. Factors included the pilot's failure to fly to the intended point of landing, and his abrupt course reversal back towards it.
Final Report:

Crash of an Antonov AN-26 in Boende: 33 killed

Date & Time: Nov 29, 2003 at 1516 LT
Type of aircraft:
Operator:
Registration:
9T-TAD
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Boende – Kinshasa
Location:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
18
Pax fatalities:
Other fatalities:
Total fatalities:
33
Circumstances:
The aircraft was completing a flight from Boende to Kinshasa, carrying 18 passengers, six crew members and a load of 672 kilos of various goods. During the takeoff roll, the captain decided to abandon the procedure and returned to the parking. A second attempt to takeoff was initiated few minutes later. During the takeoff run, at high speed, a tyre burst. The captain rejected takeoff but the aircraft was unable to stop within the remaining distance (the runway is 1,400 metres long). It overran, struck a fence and eventually crashed in a local market. All six crew members and 14 passengers were killed as well as 13 people on the ground. Four passengers and six people on the ground suffered injuries of various degrees.

Crash of a Piper PA-31-310 Navajo in Clearwater: 2 killed

Date & Time: Aug 21, 2003 at 1648 LT
Type of aircraft:
Registration:
N93DC
Flight Type:
Survivors:
Yes
Site:
Schedule:
Saint Augustine - Clearwater
MSN:
31-7712017
YOM:
1977
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
760
Copilot / Total flying hours:
600
Aircraft flight hours:
6019
Circumstances:
The airplane experienced an in-flight loss of control and crashed into a residential area. The flight departed VFR and when near the destination airport flew between areas with VIP Level 5 reflectivity. There was no record of a preflight weather briefing. The flight continued towards the destination airport and encountered lesser intensity reflectivity. An individual at the destination airport reported hearing an occupant of the airplane ask, "...for an advisory for the field", and "...what the weather was like." The individual at the airport advised that the winds appeared to be in favor for runway 16, which was left hand traffic, the runway was wet, and the rain seemed to be letting up. There were no further communications from the accident aircraft. A pilot-rated witness located north of the destination airport, and nearly due west of the accident site reported seeing the airplane on what he thought was final approach to runway 16, but the airplane was "very low." The witness reported the airplane made a, "sudden, sharp turn to the left [flying eastbound]." He then lost sight of the airplane and proceeded to the accident site. Another pilot-rated witness who was located in a vehicle approximately 1/4 mile west-northwest of the accident site reported observing an airplane flying from the northwest. The airplane banked to the left flying eastbound at a, "...very slow airspeed and banking and yawing left and right." While flying eastbound it appeared to him that whomever was flying the airplane was executing a go-around as evidenced by the landing gear retracting, followed by the flaps. The airplane then appeared to climb which appeared very unstable, again yawing left and right. The airplane then banked to the right, stalled, and entered a spin impacting the ground. Still another witness who was located approximately 1/10th of a nautical mile east-southeast from the accident site reported he came out of his house after the rain ended and was facing west. He saw the accident airplane from the northwest and thought it had descended lower than normal. The airplane was flying above the tops of nearby trees and while flying in a southeasterly direction, pitched up, "darn near got 90 degrees", rolled to the left, and descended straight down. He reported that he did not hear the engines, and thought he should have been able to hear them if the pilot had "revved them up." He estimated his view of the flight lasted approximately 10-15 seconds, and couldn't tell if the landing gear was extended. He did not see any smoke trailing the airplane, and after the impact he ran into his house, called 911, got into his car, and drove to the scene. He heard an explosion, and saw flames. He got to the airplane and helped rescue a passenger who was beating on the aircraft's door. The airplane descended nearly vertical in a residential area and damaged trees approximately 30 feet above ground level. A post crash fire consumed the cockpit, cabin, portions of both wings, and portions of both engines. Examination of the flight controls, both engines, propellers, and propeller governors revealed no evidence of preimpact mechanical failure or malfunction. Accessories of both engines including the magnetos were destroyed by the post crash fire. Additionally, both servo fuel injectors were heat damaged which precluded bench testing. During disassembly of the right servo fuel injector, the hub stud was found separated from the hub at the fuel diaphragm. No determination was made whether this occurred during disassembly or occurred preimpact. No determination could be made as to who was operating the controls at the time of the accident.
Probable cause:
The failure of the flightcrew to maintain airspeed (Vs) resulting in an inadvertent stall, uncontrolled descent, and in-flight collision with the ground.
Final Report:

Crash of a Lockheed C-130H Hercules at Boufarik AFB: 15 killed

Date & Time: Jun 30, 2003 at 1100 LT
Type of aircraft:
Operator:
Registration:
7T-WHQ
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Boufarik AFB - Boufarik AFB
MSN:
4926
YOM:
1982
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
15
Circumstances:
The crew departed Boufarik AFB on a local training flight. Shortly after takeoff, while in initial climb, the crew informed ATC about an engine fire and elected to return for an emergency landing. Few seconds later, control was lost and the aircraft crashed in the district of Beni Mered, less than 2 km from the end of runway 22. The aircraft was totally destroyed by impact forces and a post crash fire as well as eight houses. All four crew members were killed as well as 11 people on the ground. Six other people on the ground were seriously injured.
Probable cause:
Engine fire for unknown reasons.

Crash of a Piper PA-31T Cheyenne II in Denver: 2 killed

Date & Time: Jan 24, 2003 at 1721 LT
Type of aircraft:
Registration:
N360LL
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Broomfield – Denver
MSN:
31-7520036
YOM:
1975
Location:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
9365
Copilot / Total flying hours:
1944
Aircraft flight hours:
6478
Circumstances:
A Piper PA-31T "Cheyenne" and a Cessna 172P "Skyhawk" collided in midair during cruise flight at dusk and in visual meteorological conditions. The Cheyenne departed under visual flight rules (VFR) from a local airport northwest of Denver, and was proceeding direct at 7,800 feet to another local airport south of Denver. Radar indicated its ground speed was 230 knots. Its altitude encoder was transmitting intermittently. The Skyhawk departed VFR from the south airport and was en route to Cheyenne, Wyoming, at 7,300 feet. The pilot requested and was cleared to climb to 8,500 feet and penetrate class B airspace. Radar indicated its ground speed was 110 knots. The Skyhawk was flying in the suggested "VFR flyway"; the Cheyenne was not. When the controller observed the two airplanes converging, he asked the pilot of the Cheyenne for his altitude. He replied he was at 7,600 feet. The controller immediately issued a traffic advisory, but the pilot did not acknowledge. Both airplanes departed controlled flight: the Skyhawk struck a house, and the Cheyenne fell inverted into the backyard of a residence. Wreckage was scattered over a 24 square block area in west Denver. At the time of the accident, the controller was handling low altitude en route, arrival and departure traffic for both airports. Wreckage examination disclosed four slashes, consistent with propeller strikes, on top of the Cheyenne's right engine nacelle, the cabin above the right wing trailing edge, the empennage at the root of the dorsal fin, and at the tail cone. The Cheyenne was on a similar flight three days before the collision when the pilot was informed by air traffic control that the transponder was operating intermittently. According to recorded radar and voice communications from that flight, the transponder/encoder operated intermittently and the pilot was so advised. Examination of the Cheyenne's altimeter/encoder revealed a cold solder connection on pin 8 of the 15-pin altimeter connector. When the wire was resoldered to the pin, the information from the altimeters, encoder, and altitude serializer was normal.
Probable cause:
Both pilots' inadequate visual lookout. A contributing factor was the Cheyenne pilot operating the airplane with a known transponder deficiency.
Final Report:

Crash of an Antonov AN-26B in Antalya

Date & Time: Nov 9, 2002 at 1900 LT
Type of aircraft:
Operator:
Registration:
RA-26012
Survivors:
Yes
Site:
Schedule:
Asmara – Port Sudan – Hurghada – Antalya
MSN:
100 07
YOM:
1980
Flight number:
TMN9012
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
19
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft was completing a charter flight from Asmara to Antalya with intermediate stops in Port Sudan and Hurghada, carrying helicopter crews back in Russia. On approach to Antalya by night, the crew was informed about the poor weather conditions at destination with thunderstorm activity, visibility limited to two km, wind from 220 gusting at 35 knots. ATC advised the crew to maintain heading and to initiate a go-around in case they would not establish a visual contact with the runway. On short final, the left engine struck a 10 metres high electric pole. The aircraft lost height and crashed on a road located 1,325 metres short of runway and 550 metres to the left of its extended centerline. All 27 occupants were rescued, among them eight were injured. The aircraft was destroyed.
Probable cause:
The following findings were identified:
- The crew mistook the road lights for the airport lights and descended to low,
- The crew continued the approach after passing the MDA,
- The crew failed to initiate a go-around procedure,
- Limited visibility due to poor weather conditions,
- Some ATC instructions lead to confusion,
- Informations related to weather condition were inaccurate.

Crash of a Boeing 707-123B in Bangui: 28 killed

Date & Time: Jul 4, 2002 at 1115 LT
Type of aircraft:
Registration:
9XR-IS
Flight Type:
Survivors:
Yes
Site:
Schedule:
N'Djamena - Brazzaville
MSN:
19335
YOM:
1967
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
21
Pax fatalities:
Other fatalities:
Total fatalities:
28
Circumstances:
The aircraft departed N'Djamena Airport on a cargo flight to Brazzaville, carrying 21 passengers, nine crew members and a load of onions and garlic. Few minutes after takeoff, the crew reported technical problems with the undercarriage and was cleared to divert to Bangui Airport. The crew completed a holding circuit over Bangui to consume fuel then later started the descent to the airport. On final approach to runway 35, all four engines stopped simultaneously due to fuel exhaustion. The aircraft stalled and crashed in a residential area located 4 km short of runway. A crew member and one passenger were injured while 28 other people were killed. There were no casualties on the ground.
Probable cause:
The crew reported that the undercarriage could not be raised. Loss of control on final approach after all four engines stopped due to a fuel exhaustion.

Crash of a Rockwell Shrike Commander 500S in Fortaleza

Date & Time: Jul 2, 2002 at 1640 LT
Operator:
Registration:
PT-KZD
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Fortaleza - Fortaleza
MSN:
500-3140
YOM:
1972
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8000
Captain / Total hours on type:
2900.00
Aircraft flight hours:
9960
Circumstances:
The twin engine aircraft departed Fortaleza-Pinto Martins Airport on a local post maintenance test flight (50 hours), carrying two passengers and one pilot. After takeoff, while climbing to a height of 200 feet, the power on the left engine fluctuated. The pilot modified the position of the fuel selector but the situation did not change. As the aircraft was losing height, the pilot shut down the left engine and feathered its propeller when the aircraft rolled to the left, causing the left wing to struck a concrete wall. Out of control, the aircraft struck the roof of a house, then a second one and eventually crashed on a third residence. All three occupants were injured as well as one people on the ground.
Probable cause:
The fuel pump and the servo-injectors had faults which certainly contributed to the accident as the left engine was not properly supplied with fuel.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Winnipeg: 1 killed

Date & Time: Jun 11, 2002 at 0920 LT
Operator:
Registration:
C-GPOW
Survivors:
Yes
Site:
Schedule:
Gunisao Lake - Winnipeg
MSN:
31-7305093
YOM:
1973
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
3000
Circumstances:
The aircraft was on an instrument flight rules flight from Gunisao Lake, Manitoba, to Winnipeg. One pilot and six passengers were on board. At 0913 central daylight time, KEE208 began an instrument landing system approach to Runway 13 at Winnipeg International Airport. The captain flew the approach at a higher-than-normal approach airspeed and well above the glide path. When the aircraft broke out of the cloud layer, it was not in position to land safely on the remaining runway. The captain executed a missed approach at 0916 and, after switching to the approach frequency from tower frequency, requested an expedited return to the airport. The approach controller issued instructions for a turn back to the airport. Almost immediately, at 0918, the captain declared a 'Mayday' for an engine failure. Less than 20 seconds later the captain transmitted that the aircraft had experienced a double engine failure. The aircraft crashed at a major traffic intersection at 0920, striking traffic signals and several vehicles. All seven of the aircraft passengers and several of the vehicle occupants were seriously injured; one passenger subsequently died of his injuries. The aircraft experienced extensive structural damage, with the wings and engines tearing off along the wreckage trail. There was a small post-crash fire in the right wing and engine area.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The pilot did not correctly calculate the amount of fuel required to accomplish the flight from Winnipeg to Gunisao Lake and return, and did not ensure that the aircraft carried sufficient fuel for the flight.
2. The ILS approach was flown above the glideslope and beyond the missed approach point, which reduced the possibility of a safe landing at Winnipeg, and increased the risk of collision with terrain.
3. During the missed approach, the aircraft's engines lost power as a result of fuel exhaustion, and the pilot conducted a forced landing at a major city intersection.
4. The pilot did not ensure that the aircraft was equipped with an autopilot as specified by CARs.
Findings as to Risk:
1. The company did not provide an adequate level of supervision and allowed the flight to depart without an autopilot.
2. The company operations manual did not reflect current company procedures.
3. The company did not provide an adequate level of supervision and allowed the flight to depart without adequate fuel reserves. The company did not have a safety system in place to prevent a fuel exhaustion situation developing.
Other Findings:
1. The pilot did not advise air traffic control of his critical situation in a timely fashion.
Final Report:

Crash of a BAc 111-525FT in Kano: 149 killed

Date & Time: May 4, 2002 at 1335 LT
Type of aircraft:
Operator:
Registration:
5N-ESF
Flight Phase:
Survivors:
Yes
Site:
Schedule:
Jos - Kano - Lagos
MSN:
266
YOM:
1980
Flight number:
EXW4226
Location:
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
71
Pax fatalities:
Other fatalities:
Total fatalities:
85
Circumstances:
The aircraft was completing a regular schedule flight from Jos to Lagos with an intermediate stop in Kano. Weather conditions were good but the OAT at the time of the accident was +42° C. Due to construction works (retreatment of the asphalt surface), the longest runway 24/06 was closed to traffic so the crew was departing from runway 23 at Kano-Mallam Aminu Kano Airport which is 2,600 metres long. Due to high temperature and reduced performances, the aircraft used the entire runway length, overran and rolled on a grassy area for few dozen metres before lifting off. During initial climb, the aircraft encountered difficulties to gain sufficient height and to follow a positive rate of climb when it collided with obstacles and crashed in the district of Gwammaja located about 2 km past the end of runway 23. The aircraft was totally destroyed by impact forces and a post crash fire as well a several buildings, among them a school and a mosque. Among the 77 people on board the aircraft, six survived (five passengers and one stewardess). All 71 other occupants were killed as well as 78 people on the ground. More than 70 other people on the ground were injured, some seriously. It was later reported that the aircraft was out of service for 52 days due to engine problems. Nevertheless, both engines were changed few days prior to the accident and accumulated 10 hours of flight since.