Crash of a Gippsland GA-8 Airvan in Orange

Date & Time: Jul 6, 2010 at 1745 LT
Type of aircraft:
Operator:
Registration:
VH-YBH
Flight Type:
Survivors:
Yes
Schedule:
Parkes - Orange
MSN:
GA8-08-131
YOM:
2008
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The pilot was performing a cargo flight from Parkes to Orange, New South Wales. On final approach, the single engine aircraft was too low and impacted the roof of a metal hangar located near the runway threshold. The aircraft stalled and struck the runway surface. Upon impact, the nose gear was torn off. Out of control, the aircraft veered off runway and eventually collided with a metal hangar under construction. While the pilot was injured, the aircraft was destroyed.

Crash of a Lockheed C-130 Hercules at Sharana AFB

Date & Time: Jun 4, 2010
Type of aircraft:
Operator:
Registration:
S9-BAT
Flight Type:
Survivors:
Yes
MSN:
4134
YOM:
1966
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Upon landing, the undercarriage collapsed. The aircraft slid on its belly for few dozen metres then veered off runway to the right and came to rest in a sandy area. All four crew members escaped uninjured while the aircraft was damaged beyond repair. It is believed that the airplane touched down few metres short of runway 14/32 which is 4,265 feet long, causing the landing gear to be torn off.

Crash of an Embraer EMB-110P Bandeirante in Cascavel

Date & Time: May 19, 2010 at 0510 LT
Operator:
Registration:
PT-GKQ
Flight Type:
Survivors:
Yes
Schedule:
Sorocaba – Cascavel
MSN:
110125
YOM:
1976
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6879
Captain / Total hours on type:
2000.00
Copilot / Total flying hours:
1121
Copilot / Total hours on type:
15
Circumstances:
The twin engine aircraft departed Sorocaba on a cargo flight to Cascavel, carrying two pilots and a load consisting of pharmaceutical materials. On final approach in low visibility due to bad weather conditions and night, the aircraft descended below the glide and impacted the ground 700 metres short of runway 33. On impact, it lost its undercarriage then slid for 150 metres before coming to rest. Both pilots escaped uninjured while the aircraft was damaged beyond repair. Visibility at the time of the accident was 1,200 metres with mist, local patches of fog and ceiling at 100 feet. Cascavel Airport was equipped with an NDB only.
Probable cause:
Controlled flight into terrain after the crew descended too low in IMC conditions. The following contributing factors were identified:
- Visibility was below minimums,
- The crew continued the descent until the aircraft impacted ground and failed to initiate a go-around procedure,
- A probable crew fatigue,
- It is possible that the crew suffered optical illusions,
- Overconfidence on part of the captain,
- The captain did not request any assistance from the copilot during the approach procedure,
- Inexperienced, the copilot did not interfere despite dangerous flight conditions,
- Poor organizational culture,
- Deficiencies in crew training,
- Lack of crew discipline,
- Poor flight planning,
- Lack of supervision on part of the operator,
- The copilot was inexperienced on this type of aircraft.
Final Report:

Crash of an Antonov AN-12BP near Mexico City: 3 killed

Date & Time: Apr 21, 2010 at 2050 LT
Type of aircraft:
Operator:
Registration:
UP-AN216
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Cebu City - Angeles City
MSN:
4 020 01
YOM:
1964
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The aircraft departed Cebu City on a cargo flight to Angeles City, carrying six crew members and a load of various goods on behalf of UPS. En route, a short circuit occurred in the electrical system, followed by one or more engine failure. The crew elected to divert to the nearest airport. Unfortunately, this was not possible and the captain attempted an emergency landing in a paddy field. The aircraft came to rest on an embankment and was destroyed by a post impact fire. Three crew members were killed while three others were seriously injured.
Probable cause:
In flight short-circuit on the electrical system for unknow reasons.

Crash of an Airbus A300B4-203F in Monterrey: 6 killed

Date & Time: Apr 13, 2010 at 2319 LT
Type of aircraft:
Operator:
Registration:
XA-TUE
Flight Type:
Survivors:
No
Schedule:
Mexico City - Monterrey - Los Angeles
MSN:
78
YOM:
1979
Flight number:
TNO302
Country:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
16754
Captain / Total hours on type:
5446.00
Copilot / Total flying hours:
3114
Copilot / Total hours on type:
1994
Aircraft flight hours:
55170
Circumstances:
The aircraft departed Mexico City-Benito Juarez Airport on a cargo service to Los Angeles with an intermediate stop in Monterrey, carrying five crew members. On final approach to Monterrey-General Mariano Escobedo Airport by night, the crew encountered poor weather conditions with CB's and sky broken at 600 feet. On short final, while at a distance of 2 km from the runway threshold, the crew was cleared to land on runway 11. Shortly later, the aircraft rolled to the left then crashed on a motorway located 700 metres short of runway. The aircraft was totally destroyed and all five crew members were killed as well as one people in a car.
Probable cause:
The accident was the consequence of a loss of control following an unstable approach.
The following contributing factors were identified:
- Lack of crew coordination and crew resources management (CRM),
- Diminished situational awareness,
- Failure to follow proper operational procedures,
- Unstabilized non-precision approach,
- Unsuitable aircraft configuration,
- Adverse weather condition.
Final Report:

Crash of an Antonov AN-26B in Tallinn

Date & Time: Mar 18, 2010 at 1018 LT
Type of aircraft:
Operator:
Registration:
SP-FDO
Flight Type:
Survivors:
Yes
Schedule:
Helsinki – Tallinn
MSN:
105 03
YOM:
1980
Flight number:
EXN3589
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4695
Captain / Total hours on type:
2295.00
Copilot / Total flying hours:
990
Copilot / Total hours on type:
495
Aircraft flight hours:
25941
Circumstances:
Exin Co was operating An-26B for regular cargo flight between Tallinn and Helsinki. The crew performed last maintenance check in Tallinn on previous day and made uneventful flight to Helsinki on 17th March afternoon. Next morning the aircraft took off from Helsinki for regular flight EXN3589 to Tallinn at 09:46 local time. The takeoff weight was 23,954 kg, 46 kg below the MTOW. Four crewmembers, company mechanic and one cargo attendant were on board. During takeoff crew used RU 19-300 APU for additional thrust as prescribed in AFM. The RU 19-300 was shot down after takeoff. The flight was uneventful until 08:14:50, 9.5 nm from the runway 26. When power levers were retarded to flight idle crew noticed engine vibration and smelled a smoke in the cockpit. The engine chip detector indicator in the cockpit was lit. After short discussion about which engine should be shot down the flight engineer shot down the left engine and the captain tried to start the RU19A-300 (APU) to gain more thrust. During the approach the air traffic controller noticed the aircraft deviation from the approach path to the left and notified the crew. According to the FDR and CVR data the crew was unable to maintain a proper approach path both in lateral and vertical dimensions. The attempts to start RU19A-300 engine failed. Visual contact with the RWY was established 0.5 nm from the threshold. The aircraft crossed the airport boundary being not configured for landing and with IAS 295-300 km/h. The flaps were extended for 10˚ over the threshold; the landing gear was lowered after passing the RWY threshold and retracted again. The aircraft made a high speed low path over the runway on ca 10-15 feet altitude with the landing gear traveling down and up again. Flaps were extended over runway, and then retracted again seconds before impact. At the end of the RWY the full power on right engine was selected, aircraft climbed 15-20 feet and started turning left. Crew started retracting flaps and lowered landing gear. Aircraft crossed the highway at the end of the RWY on altitude ca 30 feet, then descended again, collided with the treetops at the lake shore and made crash-landing on the snow and ice-covered lake waterline. Due to the thick ice the aircraft remained on the ice and glided 151 m on the ice with heading 238˚ before coming to full stop. After the impact the flight engineer shoot down the RH engine and power and released all engine fire extinguishers. All persons onboard escaped immediately through the main door. No emergency was declares and despite suggestions from FO go-around was not commanded.
Probable cause:
Causes of the accident:
1. The failure of the left engine lubrication oil system, leading to the failure of the rear compressor bearing and inflight engine failure.
2. The failure of the crew to maintain the approach path and adhere to single engine landing procedures.
Factors contributing to the accident:
1. Improper and insufficient crew training, inter alia complete absence of simulator training.
2. The lack of effective coordination between crewmembers.
3. The failure of the crew to start RU19A-300 (APU).
4. Adverse weather conditions.
5. Inadequate company supervision by Polish CAA, consisting in not noticing the lack.
of flight crew training and companies generally pour safety culture.
6. Inadequate company maintenance practices, leaving preexisting breather duct failure unnoticed.
Final Report:

Crash of a Fokker F27 Friendship 300M in Bosaso

Date & Time: Mar 4, 2010
Type of aircraft:
Operator:
Registration:
5Y-BRN
Flight Type:
Survivors:
Yes
MSN:
10155
YOM:
1960
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Bosaso Airport, the crew encountered poor weather conditions when the aircraft crashed short of runway. Both pilots escaped with minor injuries and the aircraft was damaged beyond repair.

Crash of an Airbus A300B4-203F at Bagram AFB

Date & Time: Mar 1, 2010 at 1210 LT
Type of aircraft:
Operator:
Registration:
TC-ACB
Flight Type:
Survivors:
Yes
Schedule:
Bahrain - Bagram AFB
MSN:
121
YOM:
1980
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
12923
Captain / Total hours on type:
8000.00
Aircraft flight hours:
25300
Aircraft flight cycles:
46516
Circumstances:
While approaching Bagram AFB, the crew did not obtain the three green lights when the undercarriage were lowered. The left main gear signal appears to remain red. The captain obtained the authorization to make two low passes over the airport then ATC confirmed that all three gears were down. The final approach was completed at low speed and after touchdown, while braking, the left main gear collapsed. The aircraft veered off runway to the left and came to rest some 2 km past the runway threshold. All five crewmen were unhurt while the aircraft was damaged beyond repair.
Probable cause:
Cracks as result of fatigue caused the fracture of the hinge arm of the left main gear strut. The cracking most likely occurred as result of corrosion that remained undetected during the last maintenance inspection. The origin of pitting could not be identified, the investigation however identified deficiencies in the maintenance task conducted during last overhaul of the gear strut. Incomplete maintenance documentation and tools available during overhaul contributed to the accident.
Final Report:

Crash of a Beechcraft 65-A90 King Air in Jacmel

Date & Time: Jan 23, 2010
Type of aircraft:
Operator:
Registration:
N316AF
Flight Type:
Survivors:
Yes
MSN:
LJ-214
YOM:
1967
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was apparently completing a cargo flight from Florida. Upon landing at Jacmel Airport, the undercarriage collapsed. The twin engine aircraft went out of control, veered off runway and came to rest against trees. Both occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Beechcraft 1900C-1 off Sand Point: 2 killed

Date & Time: Jan 21, 2010 at 2345 LT
Type of aircraft:
Operator:
Registration:
N112AX
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Sand Point - Anchorage
MSN:
UC-45
YOM:
1988
Flight number:
AER22
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
3700
Captain / Total hours on type:
3080.00
Copilot / Total flying hours:
1000
Copilot / Total hours on type:
280
Aircraft flight hours:
56184
Aircraft flight cycles:
45158
Circumstances:
The crew departed on a commercial cargo flight during dark night, visual meteorological conditions on an instrument flight rules flight plan. The departure end of the runway is adjacent to an ocean bay, and wind gusts up to 26 knots were reported. Local residents north of the airport reported stronger wind, estimated between 50 and 60 knots. A fuel truck operator, who was familiar with the crew’s normal routine, reported that, before the airplane taxied to the runway, it remained on the ramp for 6 or 8 minutes with both engines operating, which he described as very unusual. There were no reports of radio communications with the flight crew after the airplane departed. The airplane crashed about 1 mile offshore, and the fragmented wreckage sank in ocean water. Because of the fragmented nature of the wreckage and ocean current, the complete wreckage was not recovered. The cockpit area forward of the wings was extensively fragmented, thus the validity of any postaccident cockpit and instrument findings was unreliable. Likewise, structural damage to the airframe precluded determining flight control continuity. Both propellers had witness marks consistent with operating under engine power and within their normal operating range. A postaccident examination of the engines and recovered components did not disclose any evidence of a mechanical malfunction. Due to the lack of mechanical deficiencies of the engines and propellers, and the extensive airframe fragmentation consistent with a high-speed water impact, it is likely that the crew had an in-flight loss of control of an unknown origin before impact.
Probable cause:
An in-flight loss of control for an undetermined reason, which resulted in an uncontrolled descent.
Final Report: