Crash of a Beechcraft B60 Duke in Gainesville: 3 killed

Date & Time: Apr 16, 2006 at 1153 LT
Type of aircraft:
Operator:
Registration:
N999DE
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Gainesville - Gainesville
MSN:
P-447
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
1500
Aircraft flight hours:
2901
Circumstances:
The airplane crashed into the terminal building following a loss of control on takeoff initial climb from runway 25. Witnesses reported that shortly after takeoff, the airplane banked sharply to the left, then it seemed to momentarily stabilize and commence a climb before beginning to roll to the left again. The airplane rolled to an inverted position, entered a dive, collided with the airport terminal building and exploded on impact. The entire airplane sustained severe fire and impact damage. Examination of the engines and propellers revealed no evidence of any discrepancies that would preclude normal operation. All the propeller blades displayed signatures indicative of high rotational energy at the time of impact, indicating that both propellers were rotating, not feathered, and the engines were operating at high power at the time of impact. Components of the autopilot system, specifically the pitch servo assembly and a portion of the roll servo assembly, were identified in the wreckage. The portion of the roll servo assembly found remained attached to a piece of skin torn from the airframe and consisted of the mounting bracket for the roll servo with the capstan bolted to the bracket, clearly indicating that this component had been reinstalled and strongly suggesting that the pilot reinstalled/reactivated all of the removed autopilot components the day before the accident. Maintenance personnel started an annual inspection on the airplane the month prior to the accident and found an autopilot installed in the airplane without the proper paperwork. The pilot explained to them that he designed and built the autopilot and was in the process of getting the proper paperwork for the installation of the system in his airplane. During the inspection, a mechanic found the aileron cable rubbing on the autopilot's roll servo capstan so the mechanic removed the roll servo along with the capstan. Additionally, mechanics disabled the autopilot's pitch servo and removed the autopilot control head. They were in the process of completing the inspection when the pilot asked for the airplane stating that he needed it for a trip. The pilot also asked that the airplane be returned to him without the interior installed. Two days before the accident, the airplane was returned to the pilot with the annual inspection incomplete. The autopilot control head, roll servo and capstan were returned to the pilot in a cardboard box on this date. A friend of the pilot reported that the day before the accident, the pilot completed reinstalling the seats and "other things" in order to fly the airplane the next day. It is possible that improper installation or malfunction of the autopilot resulted in the loss of control; however, the extent of damage and fragmentation of the entire airplane wreckage precluded detailed examination of the flight control and autopilot systems and hence a conclusive determination of the reason for the loss of control.
Probable cause:
The loss of control for an undetermined reason.
Final Report:

Crash of a Fokker F27 Friendship 400M in Guayaramerín: 1 killed

Date & Time: Apr 16, 2006 at 1137 LT
Type of aircraft:
Operator:
Registration:
FAB-91
Flight Type:
Survivors:
Yes
Schedule:
Riberalta – Guayaramerín
MSN:
10580
YOM:
1978
Country:
Crew on board:
4
Crew fatalities:
Pax on board:
27
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The aircraft departed Riberalta-General Buech Airport at 1123LT on a flight to Guayaramerín, carrying 27 passengers and a crew of four, among them two children and one baby. Few minutes after takeoff, the crew was informed about the deterioration of the weather conditions at destination with limited visibility due to heavy rain falls. After landing and a course of about 300 metres, the airplane skidded on a wet runway. It went out of control, veered off runway, lost its both wings and came to rest. All 31 occupants were rescued but an 80 years old men died few hours later from a heart attack.

Crash of a Lockheed C-130H Hercules in Kinshasa

Date & Time: Apr 14, 2006 at 1445 LT
Type of aircraft:
Operator:
Registration:
9T-TCB
Flight Type:
Survivors:
Yes
Schedule:
Kinshasa - Kinshasa
MSN:
4416
YOM:
1971
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was performing a test flight on this aircraft that was parked for 10 years at Kinshasa-N'Djili Airport. On landing, the left main gear collapsed and the aircraft came to rest. All seven occupants escaped uninjured while the aircraft was damaged beyond repair. The General Kikunda Ombala was PIC at the time of the accident.

Crash of a Lockheed C-5B Galaxy at Dover AFB

Date & Time: Apr 3, 2006 at 0642 LT
Type of aircraft:
Operator:
Registration:
84-0059
Flight Type:
Survivors:
Yes
Schedule:
Dover – Ramstein – Koweït City
MSN:
500-0083
YOM:
1986
Crew on board:
14
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The four engine aircraft departed Dover AFB at 0621LT on a flight to Kuwait City with an intermediate stop at Ramstein Airbase, Germany, carrying 17 people, three passengers and 14 crew members. Ten minutes into the flight, the copilot informed ATC about technical problems and was cleared for an immediate return. On final approach to runway 32, the aircraft descended below the glide and impacted ground few hundred metres short of runway. It came to rest in a prairie, broken in three. All 17 occupants were injured.
Probable cause:
Based on clear and convincing evidence, the Board President determined the primary cause of the mishap was the pilots' and flight engineers' failure to use the number three, fully operational, engine; the instructor's and primary flight engineer's failure to brief, and the pilots' failure to consider or utilize a 62.5 or 40% flap setting (instead of a 100% flap setting); and the pilots' attempt at a visual approach to runway 32, descending well below a normal glidepath for an instrument-aided approach or the normal VFR pattern altitude of 1,800 ft. There is substantial evidence that a contributing factor to this mishap was MP1's failure to give a complete approach briefing, in that, nonstandard factors, configuration, landing distance, and missed approach intentions were not addressed.

Crash of an Ilyushin II-62M in Moscow

Date & Time: Mar 29, 2006 at 2051 LT
Type of aircraft:
Registration:
5A-DKR
Flight Type:
Survivors:
Yes
Schedule:
Mitiga - Moscow
MSN:
4053514
YOM:
1990
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew departed Mitiga on a positioning flight to Moscow-Domodedovo where the airplane should follow an overhaul program. The airplane crossed the runway 32R threshold at a height of 12 metres and with an excessive speed of 304 km/h. At a height of about five metres, the captain instructed the flight engineer to reduce the speed and to bring back the speed levers to idle. This instruction was confirmed by the flight engineer then the captain asked for the thrust reversers to be activated. In a certain confusion, the flight engineer did not confirm this instruction and asked again the order. Possibly due to a certain distraction, the flight engineer failed to position the power lever in the correction position. As a result, the aircraft floated at a height estimated between 0,5 and one metre before it landed firmly 1,100 metres past the runway threshold at a speed of 258 km/h. Unable to stop within the landing distance available, the aircraft overran, lost its undercarriage and came to rest 680 metres further, broken in three. All six occupants were rescued, among them two were injured.
Probable cause:
The accident occurred as a result of erroneous actions by the flight engineer during operations to turn on the engine reverse when landing the plane, expressed in shifting the reverse buckets to direct thrust and putting the 1st and 4th engines to take-off mode after landing. The Commission concluded that the flight engineer’s erroneous actions were facilitated by:
- A low level of technological discipline in the crew due to the weak role of the captain as a leader in the crew, which was manifested in the crew members not fully fulfilling the "Instructions for the interaction and technology of the crew members of the IL-62M aircraft" and Aircraft Flight Manual during descent, approach and landing,
- Emotional relaxation of the crew at the end of a business trip and return to base,
- Lack of effective control, including according to the data of flight recorders over flight operations with LIBAVIA,
- In the "Instructions for the interaction and technology of the crew of the IL-62M aircraft" there are no control functions on the part of other crew members for the actions of the flight engineer at the stage of aircraft landing and the status of the reverse on/off alarm,
- The absence in the training programs of the simulator of exercises for practicing the actions of crew members in case of erroneous actions by the flight engineer when the reverse is turned on,
- Lack of equipment for the flight engineer’s workplace with a radio headset, lack of procedures in the "Instructions for Interaction and the Work Technology of the Crew Members of the Il-62M Aircraft" for the use of a radio headset for flight personnel in flights with a reduced crew,
- Excessive volume of the SSU speakers broadcasting external radio communications, which created additional difficulties when listening to the commands given by the captain,
- Fuzziness (illegibility) of the commands given by the PIC and the lack of response of the PIC to the non-confirmation of the commands given by him to the flight engineer.

Crash of a Pilatus PC-6/B2-H4 Turbo Porter in Chanthaburi: 4 killed

Date & Time: Mar 29, 2006
Operator:
Registration:
1312
Flight Phase:
Survivors:
Yes
Schedule:
Chanthaburi - Chanthaburi
MSN:
754
YOM:
1975
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
The aircraft departed Chanthaburi Airport for a cloud-seeding mission with four passengers and a pilot on board. Shortly after takeoff, while climbing, the engine failed. The aircraft stalled and crashed, bursting into flames. A passenger was seriously injured while four other occupants were killed.
Probable cause:
Engine failure for unknown reasons.

Crash of an Antonov AN-12BK in Payam

Date & Time: Mar 28, 2006 at 1648 LT
Type of aircraft:
Operator:
Registration:
EK-46741
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Payam - Sharjah
MSN:
8 3 454 08
YOM:
1968
Location:
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed Payam Airport on a cargo flight to Sharjah. Shortly after takeoff, while in initial climb, the crew declared an emergency following technical problems with three engines and was cleared for an immediate return. After the captain realized he could not make it, he attempted an emergency landing when the aircraft crash landed in a field located 5 km from the airport. On impact, the aircraft broke into several pieces, bursting into flames. All 12 occupants escaped with minor injuries.
Probable cause:
Failure of engines n°1, 3 and 4 following birdstrike during initial climb.

Crash of a Cessna 340A in Melbourne: 3 killed

Date & Time: Mar 23, 2006 at 1057 LT
Type of aircraft:
Operator:
Registration:
N37JB
Survivors:
No
Schedule:
Jacksonville – Melbourne
MSN:
340A-0124
YOM:
1976
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
801
Aircraft flight hours:
3068
Circumstances:
A commercial pilot with two passengers on a business flight was arriving at the destination airport in a light twin-engine airplane. The air traffic tower controller advised the pilot to follow a slower airplane that was on base leg. The controller subsequently asked the accident pilot if he could reduce his speed,"a little bit." The accident pilot responded that he was slowing down. Less than a minute later, the controller told the accident pilot that he was cleared to land. The accident pilot's last radio transmission was his acknowledgement of the landing clearance. The controller stated that he did not see the accident airplane other than on the radar scope, but did see a plume of smoke on the final approach course for the active runway. Ground witnesses described the airplane as flying slowly with its wings wobbling, turn right, and dive into the ground. The majority of the airplane was consumed by a post crash fire. Inspection of the flight controls and engines disclosed no evidence of any preimpact mechanical problems. Low speed flight reduces the margin between a safe operating speed and an aerodynamic stall. Wing "wobble" at low speeds is often an indicator of an incipient aerodynamic stall. Toxicological samples from the pilot’s blood detected diphenhydramine (a sedating antihistamine commonly known by the trade name Benadryl) at a level consistent with recent use of at least the maximum over-the-counter dose. Diphenhydramine is used over-the-counter for allergies and as a sleep aid, and has been shown to impair the performance of complex cognitive and motor tasks at typical doses. The FAA does not specifically prohibit the use of diphenhydramine by pilots, though Federal Air Regulation 91.17, states, in part: "No crewmember may act, or attempt to act as a crewmember of a civil aircraft...while using any drug that affects the person's faculties in any way contrary to safety..."
Probable cause:
The pilot's failure to maintain adequate airspeed to avoid a stall during the final approach to land. Contributing to the accident was the pilot's impairment due to the use of a sedating antihistamine.
Final Report:

Crash of an Antonov AN-24B at Talil AFB

Date & Time: Mar 23, 2006
Type of aircraft:
Operator:
Registration:
ER-AZZ
Flight Type:
Survivors:
Yes
Schedule:
Baghdad - Talil AFB
MSN:
7 99 011 10
YOM:
1967
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On approach to Talil AFB, the crew was forced to shut down one of the engines due to the failure of the engine control system. As the nose gear could not be lowered, the crew initiated a go-around. As the main gears could not be retracted, the captain decided to attempt an emergency landing. The aircraft crash landed in an unpaved area of the airfield and came to rest. All occupants escaped uninjured and the aircraft was damaged beyond repair.

Crash of a Learjet 35A in Philadelphia

Date & Time: Mar 22, 2006 at 0155 LT
Type of aircraft:
Operator:
Registration:
N58EM
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Philadelphie – Charlotte
MSN:
35-046
YOM:
1976
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2900
Captain / Total hours on type:
1300.00
Copilot / Total flying hours:
1600
Copilot / Total hours on type:
700
Aircraft flight hours:
18040
Circumstances:
During the takeoff roll, after the pilot disengaged the nose gear steering, the airplane began to turn to the right. The copilot noticed fluctuations with the engine indications, and called for an abort. Power was reduced to idle, and the pilot corrected to the left using left rudder pedal and braking. The airplane turned to the right again, and the pilot corrected to the left. The airplane continued to turn left, and departed the left side of the runway, tail first, and was substantially damaged. The airplane had accrued 18,040.3 total hours of operation. It was powered by two turbofan engines, each equipped with an electronic fuel computer. Examination of the left engine's wiring harness revealed that the outer shielding on the fuel computer harness assembly was loose, deteriorated, and an approximate 3-inch section was missing. Multiple areas of the outer shielding were also chaffed, the ground wire for the shielding was worn through, and the wiring was exposed. Testing of the wiring to the fuel computer connector, revealed an intermittent connection. After disassembly of the connector, it was discovered that the connector pin's wire was broken off at its crimp location. Examination under a microscope of the interior of the pin, revealed broken wire fragments that displayed evidence of corrosion. Simulation of an intermittent electrical connection resulted in N1 spool fluctuations of 2,000 rpm during engine test cell runs. According to the airplane's wiring maintenance manual, a visual inspection of all electrical wiring in the nacelle to check for security, clamping, routing, clearance, and general condition was to be conducted every 300 hours or 12 calendar months. Additionally, all wire harness shield overbraids and shield terminations were required to be inspected for security and general condition every 300 hours or 12 calendar months, and at every 600 hours or 24 calendar months. According to company maintenance records, the wiring had been inspected 6 days prior to the accident.
Probable cause:
The operator's inadequate maintenance of the fuel computer harness which resulted in engine surging and a subsequent loss of control by the flight crew during the takeoff roll.
Final Report: