Crash of a Socata TBM-850 in Iowa City: 1 killed

Date & Time: Jun 3, 2008 at 1007 LT
Type of aircraft:
Registration:
N849MA
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Iowa City - Decatur
MSN:
412
YOM:
2007
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
5688
Captain / Total hours on type:
4138.00
Aircraft flight hours:
420
Circumstances:
The private pilot arrived at the accident airport as part of an Angel Flight volunteer program to provide transportation of a passenger who had undergone medical treatment at a local hospital. About 0937, the airplane landed on runway 30 (3,900 feet by 150 feet) with winds from 073-080 degrees and 5-6 knots, which continued to increase due to an atmospheric pressure gradient. The pilot met the passengers and departed the terminal about 1003, with winds at 101-103 degrees and 23-36 knots. About 1005 the airplane was near the approach end of runway 30 with wind from 089-096 degrees and 21-31 knots. The pilot stated that he began rotating the airplane about 3,000 feet down the runway. About 1006, the airplane was approximately 3,553 feet down the runway while flying about 30 feet above the runway. The airplane experienced an aerodynamic stall, and the left wing dropped before it impacted the ground. No mechanical anomalies that would have precluded normal operation of the airplane were noted during the investigation. The fatally injured passenger, who had received medical treatment, was 2 years and 10 months of age at the time of the accident. She was held by her mother during the flight, as she had been on previous Angel Flights, but was otherwise unrestrained. According to 14 CFR 91.107(3), each person on board a U.S.-registered civil aircraft must occupy an approved seat with a safety belt properly secured during takeoff, and only unrestrained children who are under the age of 2 may be held by a restrained adult. Although the accident was survivable (both the pilot and the adult passenger survived with non-life-threatening injuries), an autopsy performed on the child revealed that the cause of death was blunt force trauma of the head.
Probable cause:
The pilot's improper decision to depart with a preexisting tailwind and failure to abort takeoff. Contributing to the severity of the injuries was the failure to properly restrain (FAA-required) the child passenger.
Final Report:

Crash of a Piper PA-46-310P Malibu in Berdoues

Date & Time: Jun 1, 2008 at 1700 LT
Operator:
Registration:
F-GJHZ
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Berdoues - Berdoues
Location:
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3180
Captain / Total hours on type:
31.00
Circumstances:
The pilot, owner of the airplane and manager of the Berdoues Aerodrome, offered a first flight to five people with whom he enjoyed the day and lunch. Arriving at the airport, he spotted a large cumulonimbus to the west of the airport, approaching the runway. He thought he was able to perform the flight before weather conditions would deteriorate and decided to complete a flapless takeoff as usual. While taxiing to the runway and passing in front of the windsock, he realized the wind was from the south at 30 knots. He completed engine test on the runway 08 threshold then started the takeoff procedure. Just prior to rotation, while passing again in front of the windsock, he realized the wind changed and was now from the tail with the same speed. As it was too late to abandon the takeoff procedure, he decided to continue. The single engine airplane took off but encountered difficulties to gain height. It descended, struck a grassy area located past the runway end then struck small trees located 200 meters further. On impact, it lost its undercarriage and its left wing before coming to rest in a pasture located 300 meters from the runway end. All six occupants escaped with minor injuries while the aircraft was damaged beyond repair.
Probable cause:
It was determined that the pilot failed to take into consideration weather conditions prior to the flight after his judgment and capabilities were impaired due to alcohol consumption. An hour and 15 minutes after the accident, a blood test revealed a blood alcohol level of 0,98‰. Investigations reported that according to wind and weather conditions, a distance of 1,300 meters was necessary for takeoff while the runway 08 is 780 meters long.
Final Report:

Crash of an Antonov AN-12BP in Chelyabinsk: 9 killed

Date & Time: May 26, 2008 at 2011 LT
Type of aircraft:
Operator:
Registration:
RA-12957
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Chelyabinsk - Perm
MSN:
8 3 455 08
YOM:
1968
Flight number:
GIA9675
Country:
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
9
Aircraft flight hours:
42817
Aircraft flight cycles:
14828
Circumstances:
Following an uneventful cargo flight from Moscow to Chelyabinsk where a load of 9 tons of various goods was deplaned, the aircraft was ferried to Perm. One minute after takeoff from Chelyabinsk Airport runway 09, while climbing in marginal weather conditions, the crew declared an emergency and reported smoke in the cockpit. After being cleared to return, the crew completed a circuit. During a third turn to the left, while in a left bank of 15° and at a speed of 335 km/h, both left engines failed and their propellers autofeathered. About 40 seconds later, the aircraft entered a right turn then descended to the ground and crashed in an open field located 11 km from Chelyabinsk Airport, bursting into flames. The accident occurred 8 minutes after takeoff. The aircraft was totally destroyed and all 9 occupants were killed.
Probable cause:
The accident was the result of a loss of controllability due to the destruction of the aileron control cables while carrying out an emergency approach to Chelyabinsk Airport after smoke spread in the cabin and the cockpit. The destruction of aileron wiring occurred, presumably, in the area of the 23-25 web frames of the cargo hold. The reason for the destruction of the wiring installation has most likely been a significant heating of a control rod located in this zone, made of alloy D16-T, and its subsequent break under tension-load operation. Heating of the control rod could be a consequence of fire of the aircraft's electricity network, in immediate proximity of the control rod. This led smoke to spread in the cargo hold, unexpected triggering of alarm systems, aircraft equipment failures, and the auto-shutdown of two engines. Electrical bunch-conductors, distributors, blocks and aggregates of the aeronautical equipment, located in the 15-25 frames zone (ceiling of the cargo compartment) came under intense attack by fire, resulting in a collision collision with the ground, as a result of which it was impossible to accurately determine the primary origin and reason of the fire.

Crash of a Boeing 747-209F in Brussels

Date & Time: May 25, 2008 at 1331 LT
Type of aircraft:
Operator:
Registration:
N704CK
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
New York – Brussels – Bahrain
MSN:
22299/462
YOM:
1980
Flight number:
CKS207
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
15000
Captain / Total hours on type:
3000.00
Copilot / Total flying hours:
7000
Copilot / Total hours on type:
200
Aircraft flight hours:
108560
Aircraft flight cycles:
20599
Circumstances:
The flight crew arrived at Brussels the day before the accident, with a flight from Bahrain. The crew rested until the Sunday morning. The aircraft arrived at Brussels on Sunday with another crew; the two crews exchanged some information regarding the airplane. There were no mechanical problems reported. Runway 20 was in service for take-offs, while Runway 25L was mostly used for landings. The pilot performed the pre-flight inspection; he found only minor discrepancies (left inner tire check and E&E door latch down). The pre-flight briefing covered the standard departure call-outs, the runway incursion information, a discussion on the Runway 20 length, etc.. The crew also briefed about the engine failure procedures for an engine failure prior to V1, and they also briefed about an abort takeoff after V1 if there was a dangerous situation that would not allow the airplane to fly. After completing the flight documents, the crew requested an early departure, which they received. For the computation of the take-off parameters, the crew used the Kalitta Air On-board Performance System (OPS computer). The crew determined they needed the full length of the runway for take-off. The airplane taxied towards the B1 intersection for the Runway 20. After a few minutes, waiting for another airplane to land on Runway 25, they lined up on Runway 20, making a tight turn, in order to gain a few meters with respect to the usual departure position. The airplane was cleared for take-off at 11:29. The pilot pushed the throttles forward and checked the engines were stable. The Flight Engineers then set the engine power for take-off (setting “normal”, also known as “reduced thrust”). The aircraft started to accelerate. The standard call-out were made when the speed reached the determined value.
- “airspeed”
- 80 knots
- V1
A few seconds after reaching V1, the engine N°3 ingested a bird. Approximately 5 seconds after V1, the engine N°3 stalled and caused a loud “bang”, and a vibration felt in the cockpit. The pilot stated he had the feeling that the aircraft was no longer accelerating, and decided to abort the take-off. Two seconds after having heard the detonation, the thrust levers were brought back to idle, and braking action was initiated. The thrust reversers were not deployed. The FO called the tower, and notified the aircraft was going to the overrun. The pilot turned the aircraft a few degrees to the right, in order to avoid the approach lights at the end of the runway. The aircraft left the runway at a speed of approximately 72 Knots. The aircraft reached a first embankment, dropping from a height of 4 m, and broke in three parts. The aircraft came to a stop just above the top of the railroad embankment. The crew exited the airplane through the service door since the L1 door normally used was blocked due to deformation of the structure.
Probable cause:
The accident was caused by the decision to reject the takeoff 12 knots after passing V1 speed. The following factors contributed to the accident:
- Engine Nr 3 experienced a bird strike, causing it to stall. This phenomenon was accompanied by a loud bang, noticed by the crew.
- The aircraft line up at the B1 intersection although the take-off parameters were computed with the full length of the runway.
- The situational awareness of the crew,
- Less than maximum use of deceleration devices.
- Although the RESA conforms to the minimum ICAO requirement, it does not conform to the ICAO recommendation for length.
Final Report:

Crash of a Beechcraft 1900C in Billings: 1 killed

Date & Time: May 23, 2008 at 0124 LT
Type of aircraft:
Operator:
Registration:
N195GA
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Billings - Great Falls
MSN:
UB-65
YOM:
1986
Flight number:
AIP5008
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
4770
Captain / Total hours on type:
362.00
Aircraft flight hours:
34651
Circumstances:
About one minute after takeoff on a night Instrument Flight Rules (IFR) contract cargo flight, the tower controller advised the pilot that he was squawking the wrong transponder code. Although the pilot reset the transponder to the correct code, he was advised that he was still squawking the wrong code. He then realized that he had selected the wrong transponder, and then switched to the correct one. During the time the pilot was dealing with this issue, the airplane drifted about 30 degrees right of the assigned heading, but the pilot returned to the correct heading as he was contacting the departure controller. The departure controller cleared him to continue his climb and instructed him to turn left about 120 degrees, which he did. About 40 seconds after initiating his left turn of about 120 degrees, while climbing straight ahead through an altitude about 4,700 feet above ground level (AGL), the pilot was instructed to turn 20 degrees further left. Almost immediately thereafter, the airplane began turning to the right, and then suddenly entered a rapidly descending right turn. The airplane ultimately impacted the terrain in a nearly wings-level nose-down attitude of greater than 45 degrees. At the moment of impact the airplane was on a heading about 220 degrees to the right of the its last stabilized course. The investigation did not find any indication of an airframe, control system, or engine mechanical failure or malfunction that would have precluded normal flight, and no autopsy or toxicological information could be acquired due to the high amount of energy that was released when the airplane impacted the terrain. The determination of the initiating event that led to the uncontrolled descent into the terrain was not able to be determined.
Probable cause:
The pilot's failure to maintain aircraft control during the initial climb for undetermined reasons.
Final Report:

Crash of a Cessna 208B Grand Caravan in Doro

Date & Time: Apr 28, 2008 at 1240 LT
Type of aircraft:
Operator:
Registration:
5Y-SPK
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Doro - Nairobi
MSN:
208B-0243
YOM:
1990
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single aircraft was on a return flight from Doro to Nairobi, carrying four mission personnel who took part to a humanitarian mission in the region of Doro. The takeoff was performed from a muddy airstrip and the aircraft was unable to gain sufficient height after liftoff. As a result, the left wing impacted a tree trunk and the airplane crashed in a ditch, coming to rest upside down. All five occupants escaped uninjured.

Crash of a Piper PA-31-310 Navajo in Caracas: 6 killed

Date & Time: Apr 28, 2008 at 0955 LT
Type of aircraft:
Registration:
N6463L
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Caracas – Willemstad
MSN:
31-421
YOM:
1969
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
6
Circumstances:
The twin engine aircraft departed Caracas-Maiquetía-Simón Bolívar Airport on a private flight to Willemstad-Hato Airport, Curaçao, with two passengers and one pilot on board. During initial climb, the pilot reported engine problems and was cleared for an immediate return when he lost control of the airplane that crashed onto several buildings located in the district of Catia La Mar, about 6 km short of runway 09 threshold. The aircraft burst into flames and was totally destroyed. All three occupants as well as three people on the ground were killed. Five other people were injured.

Crash of a Fletcher FU-24-950 in Kaihoka

Date & Time: Apr 26, 2008 at 1115 LT
Type of aircraft:
Operator:
Registration:
ZK-DZC
Flight Phase:
Survivors:
Yes
MSN:
205
YOM:
1975
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3500
Captain / Total hours on type:
1928.00
Circumstances:
During takeoff the topdressing aircraft collided with a low hill. The pilot lost control soon after the collision. During the ensuing crash he was seriously injured and the aircraft was destroyed.
Probable cause:
Cause factors reported by pilot were a possible tailwind component, and the aircraft may have been overloaded for the conditions.

Crash of a Cessna 421A Golden Eagle I in Saltillo

Date & Time: Apr 25, 2008 at 1200 LT
Type of aircraft:
Registration:
XB-WUF
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Saltillo – Aguascalientes
MSN:
421A-0124
YOM:
1968
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Saltillo-Plan de Guadalupe Airport, while in initial climb, one of the engine caught fire. The pilot attempted an emergency landing when the aircraft crash landed in a field past the runway end, bursting into flames. All six occupants escaped with minor injuries and the aircraft was destroyed.
Probable cause:
Engine fire for unknown reasons.

Crash of a Douglas DC-9-51 in Goma: 40 killed

Date & Time: Apr 15, 2008 at 1430 LT
Type of aircraft:
Operator:
Registration:
9Q-CHN
Flight Phase:
Survivors:
Yes
Site:
Schedule:
Goma – Kisangani
MSN:
47731/860
YOM:
1977
Location:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
86
Pax fatalities:
Other fatalities:
Total fatalities:
40
Circumstances:
During the takeoff roll from runway 18 at Goma Airport, the crew started the rotation but the aircraft failed to respond. The aircraft continued, overran and crashed in the Birere District, about 100 metres past the runway end, bursting into flames. Three passengers were killed as well as 37 people on the ground. All other occupants were injured. The aircraft was totally destroyed by impact forces and a post crash fire.
Probable cause:
It is possible that one of the engine or maybe both suffered a loss of power during takeoff after the aircraft passed through a puddle.