Crash of an Antonov AN-12B in Luxor: 5 killed

Date & Time: Feb 20, 2009 at 0418 LT
Type of aircraft:
Operator:
Registration:
S9-SVN
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Kisangani – Entebbe – Luxor – Mykolaiv
MSN:
6 3 443 10
YOM:
1966
Flight number:
LFT1015
Location:
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
20000
Copilot / Total flying hours:
6397
Aircraft flight hours:
11692
Aircraft flight cycles:
6451
Circumstances:
The four engine aircraft was transferred from Kisangani to Mykolaiv, Ukraine, for maintenance purposes. Two enroute stops were scheduled in Entebbe and Luxor. Ar 0417LT, the crew was cleared for takeoff. The aircraft started rolling on runway 02 for takeoff but it kept rolling on it till it reached its end. The aircraft continued rolling in the sand drifting from the runway centerline to the right, crossing a service road and eventually crashing into a military zone located 500 metres from the runway end. The aircraft crashed into one of the buildings inside the military unit causing complete destruction of the building. The right wing also crashed into another building putting the aircraft on fire and forcing the aircraft to turn right. The aircraft kept moving forward the military unit fence (next to Tiba-Luxor road) and stopped there, crashing in its way into oil barrel. The accident resulted in the total destruction and fire of the aircraft and the fatality of its crew but no further injuries.
Probable cause:
The following factors were identified:
- Lack of available thrust which corresponded to the power of only two engines running during take off run,
- Lack of authorized maintenance of the aircraft,
- The uncoordinated crew actions in the critical situation (both pilots had previously flown as captains). The lack of coordination is confirmed by the braking trails left by the main landing gear at the end of RWY -02, based on FCOM instructions, and in case of rejected takeoff attempt, the crew had to set the throttles to idle, lower the nose gear to reach the runway and then use the propellers for braking (releasing them from the stops). Also, to reduce the roll and to maintain the direction they were to use the nose wheel steering and wheel brakes as well as emergency braking if needed. Actually the crew did neither of the above procedures, except using the main wheel brakes.
Final Report:

Crash of an ATR42-320 in Lubbock

Date & Time: Jan 27, 2009 at 0437 LT
Type of aircraft:
Operator:
Registration:
N902FX
Flight Type:
Survivors:
Yes
Schedule:
Fort Worth - Lubbock
MSN:
175
YOM:
1990
Flight number:
FX8284
Location:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13935
Captain / Total hours on type:
2052.00
Copilot / Total flying hours:
2109
Copilot / Total hours on type:
130
Aircraft flight hours:
28768
Aircraft flight cycles:
32379
Circumstances:
Aircraft was on an instrument approach when it crashed short of the runway at Lubbock Preston Smith International Airport, Lubbock, Texas. The captain sustained serious injuries, and the first officer sustained minor injuries. The airplane was substantially damaged. The airplane was registered to FedEx Corporation and operated by Empire Airlines, Inc., as a 14 Code of Federal Regulations Part 121 supplemental cargo flight. The flight departed from Fort Worth Alliance Airport, Fort Worth, Texas, about 0313. Instrument meteorological conditions prevailed, and an instrument flight rules flight plan was filed.
Probable cause:
The National Transportation Safety Board determines that the probable cause of this accident was the flight crew’s failure to monitor and maintain a minimum safe airspeed while executing an instrument approach in icing conditions, which resulted in an aerodynamic stall at low altitude.
Contributing to the accident were:
-the flight crew’s failure to follow published standard operating procedures in response to a flap anomaly,
-the captain’s decision to continue with the unstabilized approach
-the flight crew’s poor crew resource management,
-fatigue due to the time of day in which the accident occurred and a cumulative sleep debt which likely impaired the captain’s performance.
Final Report:

Crash of an Antonov AN-12BP in Sharjah

Date & Time: Jan 2, 2009 at 0751 LT
Type of aircraft:
Operator:
Registration:
S9-SAM
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
3341408
YOM:
1963
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the takeoff roll, the left main gear collapsed. The aircraft sank on the runway, causing the left wing and the engine n°1 to contact the runway surface. All six crew members escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Left main gear collapsed during the takeoff roll for unknown reasons.

Crash of a Dassault Falcon 20C in Jamestown

Date & Time: Dec 21, 2008 at 0100 LT
Type of aircraft:
Operator:
Registration:
N165TW
Flight Type:
Survivors:
Yes
Schedule:
Tulsa – Jamestown
MSN:
65
YOM:
1966
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3028
Captain / Total hours on type:
1160.00
Copilot / Total flying hours:
2086
Copilot / Total hours on type:
80
Aircraft flight hours:
16360
Circumstances:
The co-pilot was performing a nighttime approach and landing to runway 25. No runway condition reports were received by the flight crew while airborne, and a NOTAM was in effect, stating, “thin loose snow over patchy thin ice.” After landing, the co-pilot called out that the airplane was sliding and the wheel brakes were ineffective. The captain took the controls, activated the air brakes, and instructed the co-pilot to deploy the drag chute. The crew could not stop the airplane in the remaining runway distance and the airplane overran the runway by approximately 100 feet. After departing the runway end, the landing gear contacted a snow berm that was the result of earlier plowing. The captain turned the airplane around and taxied to the ramp. Subsequent inspection of the airplane revealed a fractured nose gear strut and buckling of the fuselage. The spring-loaded drag chute extractor cap activated, but the parachute remained in its tail cone container. Both flight crewmembers reported that the runway was icy at the time of the accident and braking action was “nil.” The airport manager reported that when the airplane landed, no airport staff were on duty and had not been for several hours. He also reported that when the airport staff left for the evening, the runway conditions were adequate. The runway had been plowed and sanded approximately 20 hours prior to the accident, sanded two more times during the day, and no measurable precipitation was recorded within that time frame. The reason that the drag chute failed to deploy was not determined.
Probable cause:
The inability to stop the airplane on the remaining runway because of icy runway conditions. A factor was the failure of the drag chute to properly deploy.
Final Report:

Crash of a Cessna 402B in Madison

Date & Time: Dec 16, 2008 at 2252 LT
Type of aircraft:
Operator:
Registration:
N4504B
Flight Type:
Survivors:
Yes
Schedule:
Appleton - Milwaukee
MSN:
402B-1370
YOM:
1978
Flight number:
FRG1531
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2069
Captain / Total hours on type:
274.00
Aircraft flight hours:
12805
Circumstances:
The on-demand cargo flight departed for the destination airport and was delayed en route due to repetitive destination airport closures. The closures were the result of snow-contaminated runways. The pilot then diverted to an alternate airport due to concerns about remaining fuel reserves. The airplane experienced a loss of engine power during an instrument approach at the alternate airport and impacted the ground about 200 yards short of the landing runway. A postaccident inspection of the airplane revealed no usable fuel on board.
Probable cause:
The pilot’s improper fuel management, which resulted in a loss of engine power during an instrument landing due to fuel exhaustion.
Final Report:

Crash of a Rockwell Shrike Commander 500S in Planeta Rica: 2 killed

Date & Time: Dec 3, 2008 at 1825 LT
Registration:
HK-1697
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Medellín – Montería
MSN:
500-3198
YOM:
1974
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
12153
Captain / Total hours on type:
2000.00
Copilot / Total hours on type:
18
Aircraft flight hours:
6179
Circumstances:
The twin engine aircraft departed Medellín-Enrique Olaya Herrera Airport at 1745LT on a cargo flight to Montería, carrying two pilots and a load of bovine embryos. The flight to Montería was completed at FL130 then the crew was cleared to start the descent to Montería-Los Garzones Airport. At an altitude of 7,500 feet on descent, the aircraft went out of control and crashed in an open field located in Verada Arroyo, near Planeta Rica. The aircraft disintegrated on impact and both pilots were killed.
Probable cause:
Loss of control in altitude for undetermined reasons.
Final Report:

Crash of an Antonov AN-12BK near Al-Taqaddum AFB: 7 killed

Date & Time: Nov 13, 2008 at 1124 LT
Type of aircraft:
Operator:
Registration:
S9-SAO
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Al Asad – Bagdad
MSN:
00 346 908
YOM:
1970
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
The four engine aircraft departed Al Asad AFB at 1102LT on a cargo flight to Baghdad with 7 crew members on board, carrying various goods for the allied forces in Iraq. While cruising at an altitude of 9,000 feet, the engine n°2 failed and caught fire. The crew declared an emergency and reduced his altitude in an attempt to make an emergency landing when the aircraft entered an uncontrolled descent and crashed in a desert area located 22 km southeast of Al-Taqaddum AFB, bursting into flames. All seven occupants were killed.
Probable cause:
Failure of engine n°2 for unknown reasons.

Crash of a Beechcraft 100 King Air in Stony Rapids

Date & Time: Nov 11, 2008 at 1817 LT
Type of aircraft:
Registration:
C-GWWQ
Flight Type:
Survivors:
Yes
Schedule:
Uranium City – Stony Rapids
MSN:
B-76
YOM:
1971
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
For unknown reasons, the aircraft made a wheels up landing and skidded on runway at Stony Rapids Airport before coming to rest. Both pilots were uninjured while the aircraft was damaged beyond repair.
Probable cause:
Gear up landing for undetermined reason.

Crash of an Antonov AN-12B in Pointe-Noire

Date & Time: Nov 10, 2008
Type of aircraft:
Registration:
UR-PLV
Flight Type:
Survivors:
Yes
MSN:
4 3 423 08
YOM:
1964
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Few minutes after takeoff from Pointe-Noire Airport, while flying 80 km away, the crew contacted ATC and declared an emergency after a fire erupted in the cargo compartment. The crew was able to return and after landing, the aircraft stopped on the main runway, bursting into flames. All six occupants escaped uninjured while the aircraft was destroyed by fire.
Probable cause:
It is believed that the fire started in the cargo bay near a generator.

Crash of a Boeing 747-228F in Brussels

Date & Time: Oct 27, 2008 at 1600 LT
Type of aircraft:
Operator:
Registration:
OO-CBA
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Brussels – Dakar – Campinas
MSN:
24158/714
YOM:
1988
Flight number:
BB3101
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11360
Captain / Total hours on type:
260.00
Copilot / Total flying hours:
3536
Copilot / Total hours on type:
570
Aircraft flight hours:
82357
Aircraft flight cycles:
15773
Circumstances:
The aircraft took off from Brussels airport at 15:00 UTC. Upon rotation, the crew heard an abnormal noise, and had difficulties to get the aircraft in the air. After adjusting the engine power, the aircraft took off. Observers on the ground saw two white clouds appearing successively under the tail of the aircraft upon rotation, followed by flames. The inspection of the runway revealed that parts separated from the aircraft, amongst which the APU access door. The aircraft dumped the excess of fuel and landed back in Brussels at 16.20 UTC. Inspection on the ground revealed that large portions of the underside skin of the tail section were missing.
Probable cause:
The accident was caused by an inadequate take-off performance calculation, due to wrong gross weight data input error in the software used for the computation of the takeoff performance parameters and the failure to comply with the operator’s SOP for checking the validity of the data.
Contributing factor(s):
- Inadequate pairing of crew members with low experience.
- Lack of distraction management.
Final Report: