Crash of a PZL-Mielec M28-05PI Skytruck near Wami: 5 killed

Date & Time: Oct 27, 2010 at 1630 LT
Type of aircraft:
Operator:
Registration:
P-4204
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Nabire – Ambon – Ujung Pandang – Jakarta
MSN:
AJE003-07
YOM:
2004
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
The twin engine aircraft departed Nabire Airport at 1555LT and was carrying three police officers and two pilots who were returning to Jakarta after they delivered aid to the victims of Wasior floods in West Papua. Two intermediate stops were scheduled in Ambon and Ujung Pandang (Makassar). En route, the aircraft crashed in unknown circumstances near Wami, most probably due to poor weather conditions. The wreckage was found a day later and all five occupants were killed.

Crash of a Let L-410UVP near Bukavu: 2 killed

Date & Time: Oct 21, 2010
Type of aircraft:
Operator:
Registration:
9Q-CUA
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Bukavu – Shabunda
MSN:
X0101
YOM:
1977
Location:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
The aircraft was completing a cargo flight from Bukavu to Shabunda, carrying two pilots and a load of 1,500 kilos of various goods. Few minutes after takeoff from Bukavu-Kavumu Airport, while climbing, the twin engine aircraft went out of control and crashed near the village of Bugulumisa located at the border of the Kahuzi-Biega National Park. The aircraft was totally destroyed and both pilots were killed.
Probable cause:
It is believed that the accident was the consequence of an engine failure.

Crash of a Cessna 208B Grand Caravan near Kirensk

Date & Time: Oct 2, 2010 at 1024 LT
Type of aircraft:
Operator:
Registration:
RA-67701
Flight Phase:
Survivors:
Yes
Schedule:
Lensk – Bratsk
MSN:
208B-0932
YOM:
2002
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13358
Captain / Total hours on type:
4083.00
Copilot / Total flying hours:
4824
Copilot / Total hours on type:
757
Aircraft flight hours:
3203
Aircraft flight cycles:
1423
Circumstances:
The single engine aircraft departed Lensk at 0813LT on a flight to Bratsk. While cruising at 4,200 metres over the cloud layer, the engine failed. The crew elected to divert to Kirensk Airport but was unable to maintain a safe altitude. Eventually, the captain attempted an emergency landing when the aircraft impacted trees and crashed in a wooded area located 37 km west of Kirensk. All nine occupants were injured and the aircraft was damaged beyond repair.
Probable cause:
Engine failure due to the damage of the bearings of the planetary gear from the first stage of the compressor, leading to vibration and destruction of the turbine. It is possible the damage to the bearings was caused by the presence of aluminium or silicon oxide. However, it was not possible to determinate the source of this contamination.

Crash of a Boeing 747-44AF near Dubai: 2 killed

Date & Time: Sep 3, 2010 at 1941 LT
Type of aircraft:
Operator:
Registration:
N571UP
Flight Type:
Survivors:
No
Schedule:
Hong Kong - Dubai - Cologne
MSN:
35668/1393
YOM:
2007
Flight number:
UPS006
Location:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
11410
Captain / Total hours on type:
367.00
Copilot / Total flying hours:
6130
Copilot / Total hours on type:
78
Aircraft flight hours:
9977
Aircraft flight cycles:
1764
Circumstances:
The four engine aircraft was completing a cargo flight from Hong Kong to Cologne with an intermediate stop in Dubai with two pilots on board. One minute after passing the BALUS waypoint, approaching the top of climb, as the aircraft was climbing to the selected cruise altitude of 32,000 feet, the Fire Warning Master Warning Light illuminated and the Audible Alarm [Fire Bell] sounded, warning the crew of a fire indication on the Main Deck Fire - Forward. The captain advised BAE-C that there was a fire indication on the main deck of the aircraft, informing Bahrain ATC that they needed to land as soon as possible. BAE-C advised that Doha International Airport (DOH) was at the aircraft’s 10 o’clock position 100 nm DME from the current location. The Captain elected to return to the point of departure, DXB. The crew changed the selected altitude from 32,000 feet to 28,000 feet as the aircraft changed heading back to DXB, the Auto Throttle [AT] began decreasing thrust to start the decent. The AP was manually disconnected, then reconnected , followed by the AP manually disconnecting for a short duration, the captain as handling pilot was manually flying the aircraft. Following the turn back and the activation of the fire suppression, for unknown reasons, the PACK 1 status indicated off line [PACKS 2 and 3 were off], in accordance with the fire arm switch activation. There was no corresponding discussion recorded on the CVR that the crew elected to switch off the remaining active PACK 1. As the crew followed the NNC Fire/Smoke/Fumes checklist and donned their supplemental oxygen masks, there is some cockpit confusion regarding the microphones and the intra-cockpit communication as the crew cannot hear the microphone transmissions in their respective headsets. The crew configured the aircraft for the return to DXB, the flight was in a descending turn to starboard onto the 095° reciprocal heading for DXB when the Captain requested an immediate descent to 10,000 ft. The reason for the immediate descent was never clarified in the available data. The AP was disengaged, the Captain then informed the FO that there was limited pitch control of the aircraft when flying manually. The Captain was manually making inputs to the elevators through the control column, with limited response from the aircraft. The flight was approximately 4 minutes into the emergency. The aircraft was turning and descending, the fire suppression has been initiated and there was a pitch control problem. The cockpit was filling with persistent continuous smoke and fumes and the crew had put the oxygen masks on. The penetration by smoke and fumes into the cockpit area occurred early into the emergency. The cockpit environment was overwhelmed by the volume of smoke. There are several mentions of the cockpit either filling with smoke or being continuously ‘full of smoke’, to the extent that the ability of the crew to safely operate the aircraft was impaired by the inability to view their surroundings. Due to smoke in the cockpit, from a continuous source near and contiguous with the cockpit area [probably through the supernumerary area and the ECS flight deck ducting], the crew could neither view the primary flight displays, essential communications panels or the view from the cockpit windows. The crew rest smoke detector activated at 15:15:15 and remained active for the duration of the flight. There is emergency oxygen located at the rear of the cockpit, in the supernumerary area and in the crew rest area. Due to the persistent smoke the Captain called for the opening of the smoke shutter, which stayed open for the duration of the flight. The smoke remained in the cockpit area. There was a discussion between the crew concerning inputting the DXB runway 12 Left [RWY12L] Instrument Landing System [ILS] data into the FMC. With this data in the FMC the crew can acquire the ILS for DXB RWY12L and configure the aircraft for an auto flight/auto land approach. The F.O. mentions on several occasions difficulty inputting the data based on the reduced visibility. However, the ILS was tuned to a frequency of 110.1 (The ILS frequency for DXB Runway 12L is 110.126), the Digital Flight Data Recorder [DFDR] data indicates that this was entered at 15:19:20 which correlates which the CVR discussion and timing. At approximately 15:20, during the emergency descent at around 21,000ft cabin pressure altitude, the Captain made a comment concerning the high temperature in the cockpit. This was followed almost immediately by the rapid onset of the failure of the Captain’s oxygen supply. Following the oxygen supply difficulties there was confusion regarding the location of the alternative supplementary oxygen supply location. The F.O either was not able to assist or did not know where the oxygen bottle was located; the Captain then gets out of the LH seat. This CVR excerpt indicates the following exchange between the Captain and F.O concerning the mask operation and the alternative oxygen supply bottle location. The exchange begins when the Captain’s oxygen supply stops abruptly with no other indications that the oxygen supply is low or failing. Based on the pathological information, the Captain lost consciousness due to toxic poisoning. After the Captain left the LH cockpit seat, the F.O. assumed the PF role. The F.O. remained in position as P.F. for the duration of the flight. There was no further interaction from the Captain or enquiry by the F.O as to the location of the Captain or the ability of the Captain to respond. The PF informed the BAE-C controllers that due to the limited visibility in the cockpit that it was not possible to change the radio frequency on the Audio Control Panel [ACP]. This visibility comment recurs frequently during the flight. The Bahrain East controller was communicating with the emergency aircraft via relays. Several were employed during the transition back to DXB. The aircraft was now out of effective VHF radio range with BAE-C. In order for the crew to communicate with BAE-C, BAE-C advised transiting aircraft that they would act as a communication relay between BAE-C and the emergency aircraft. BAE-C would then communicate to the UAE controllers managing the traffic in the Emirates FIR via a landline, who would then contact the destination aerodrome at Dubai, also by landline. The crew advised relay aircraft that they would stay on the Bahrain frequency as they could not see the ACP to change frequency. All of the 121.5 MHz transmissions by the PF were keyed via the VHF-R, all other radio communication with BAE-C and the relay aircraft are keyed from the VHF-L audio panel. There are several attempts by the UAE’s Area Control [EACC] to contact the flight on the guard frequency in conjunction with aircraft relaying information transmitting on the guard frequency to the accident flight. The PF of the accident flight does not appear to hear any of the transmissions from the air traffic control units or the relay aircraft on the guard frequency. Around this time, given the proximity of the aircraft to the RWY12L intermediate approach fix, Dubai ATC transmits several advisory messages to the flight on the Dubai frequencies, for example DXB ARR on 124.9 MHz advise that ‘Any runway is available’. The Runway lights for RWY30L were turned on to assist the return to DXB. The Aircraft condition inbound as the flight approached DXB for RWY12L. The computed airspeed was 350 knots, at an altitude of 9,000 feet and descending on a heading of 105° which was an interception heading for the ILS at RWY12L. The FMC was tuned for RWY12L, the PF selected the ‘Approach’ push button on the Mode Control Panel [MCP] the aircraft captures the Glide Slope (G/S). The AP did not transition into the Localizer Mode while the Localizer was armed. ATC, through the relay aircraft advised the PF, ‘you're too fast and too high can you make a 360? Further requesting the PF to perform a ‘360° turn if able’. The PF responded ‘Negative, negative, negative’ to the request. The landing gear lever was selected down at 15:38:00, followed approximately 20 seconds later by an the aural warning alarm indicating a new EICAS caution message, which based on the data is a Landing Gear Disagree Caution. At 15:38:20 the PF says: ‘I have no, uh gear’. Following the over flight of DXB, on passing north of the aerodrome abeam RWY12L. The last Radar contact before the flight passed into the zone of silence was at 15:39:03. The flight was on a heading of 89° at a speed of 320 knots , altitude 4200 feet and descending. The flight was cleared direct to Sharjah Airport (SHJ), SHJ was to the aircraft’s left at 10 nm, the SHJ runway is a parallel vector to RWY12L at DXB. The relay pilot asked the PF if it was possible to perform a left hand turn. This turn, if completed would have established the flight onto an approximate 10 mile final approach for SHJ RWY30. The flight was offered vectors to SHJ (left turn required) and accepts. The relay aircraft advised that SHJ was at 095° from the current position at 10 nm. The PF acknowledged the heading change to 095° for SHJ. For reasons undetermined the PF selected 195° degrees on the Mode Control Panel [MCP], the AP was manually disconnected at 15:40:05, the aircraft then banked to the right as the FMC captured the heading change, rolled wings level on the new heading, the throttles were then retarded, the aircraft entered a descending right hand turn at an altitude of 4000 feet, the speed gradually reduced to 240 kts. The PF made a series of pitch inputs which had a limited effect on the descent profile; the descent is arrested temporarily. There then followed a series of rapid pitch oscillations. These were not phugoid oscillations, these were commanded responses where the elevator effectiveness decreased rapidly as the airspeed decayed and the elevators could not compensate for the reduced thrust moment from the engines to maintain level flight in a steady state. This was due to the desynchronization of the control column inputs and the elevators. At this point had the aircraft remained on the current heading and descent profile it would have intercepted the terrain at or near a large urban conurbation, Dubai Silicone Oasis. The PF was in VHF communication with the relay aircraft requesting positional, speed and altitude information. From this point onwards, approximately 50 seconds elapse prior to the data ending. The effectiveness of the pitch control immediately prior to the end of the data was negligible. The control column was fully aft when the data ended, there was no corresponding elevator movement. The aircraft lost control in flight and made an uncontrolled descent into terrain.
Probable cause:
Probable causes:
- A large fire developed in palletized cargo on the main deck at or near pallet positions 4 or 5, in Fire Zone 3, consisting of consignments of mixed cargo including a significant number of lithium type batteries and other combustible materials. The fire escalated rapidly into a catastrophic uncontained fire.
- The large, uncontained cargo fire, that originated in the main cargo deck caused the cargo compartment liners to fail under combined thermal and mechanical loads.
- Heat from the fire resulted in the system/component failure or malfunction of the truss assemblies and control cables, directly affecting the control cable tension and elevator function required for the safe operation of the aircraft when in manual control.
- The uncontained cargo fire directly affected the independent critical systems necessary for crew survivability. Heat from the fire exposed the supplementary oxygen system to extreme thermal loading, sufficient to generate a failure. This resulted in the oxygen supply disruption leading to the abrupt failure of the Captain’s oxygen supply and the incapacitation of the captain.
- The progressive failure of the cargo compartment liner increased the area available for the smoke and fire penetration into the fuselage crown area.
- The rate and volume of the continuous toxic smoke, contiguous with the cockpit and supernumerary habitable area, resulted in inadequate visibility in the cockpit, obscuring the view of the primary flight displays, audio control panels and the view outside the cockpit which prevented all normal cockpit functioning.
- The shutdown of PACK 1 for unknown reasons resulted in loss of conditioned airflow to the upper deck causing the Electronic Equipment Cooling [EEC] system to reconfigure to “closed loop mode”. The absence of a positive pressure differential contributed to the hazardous quantities of smoke and fumes entering the cockpit and upper deck, simultaneously obscuring the crew’s view and creating a toxic environment.
- The fire detection methodology of detecting smoke sampling as an indicator of a fire is inadequate as pallet smoke masking can delay the time it takes for a smoke detection system to detect a fire originating within a cargo container or a pallet with a rain cover.
Contributing Factors:
- There is no regulatory FAA requirement in class E cargo compartments for active fire suppression.
- Freighter main deck class E fire suppression procedures which relay on venting airflow and depressurisation as the primary means of controlling a fire are not effective for large Class E cargo fires involving dangerous goods capable of Class D metal fire combustion.
- No risk assessment had been made for the failure of the cargo compartment liner based on the evolution of cargo logistics and associated cargo content fire threats, cargo hazards and bulk carriage of dangerous goods.
- The regulation standards for passive fire suppression do not adequately address the combined total thermal energy released by current cargo in a large cargo fire and the effect this has on the protection of critical systems.
- FAA and EASA regulatory requirements do not recognize the current total fire risk associated with pallets, pallet covers and containers as demonstrated by the NTSB/FAA testing.
- Class 9 Hazmat packing regulations do not address the total or potential fire risk that can result from lithium battery heat release during thermal runaway. Although non-bulk specification packaging is designed to contain leaks and protect the package from failure, the packaging for Class 9 does not function to contain thermal release.
- The growth rate of container and pallet fires after they become detectable by the aircraft’s smoke detection system can be extremely fast, precluding any mitigating action and resulting in an overwhelming total energy release and peak energy release rate for a standard fire load that cannot be contained.
- The course to return to Dubai required a series of complex radio communication relays due to the Pilot Flying’s inability to view and tune the radio transceivers.
- The relay communication between the Pilot Flying, relay aircraft and the various ATC stations resulted in communication confusion, incomplete and delayed communications, which contributed to the escalated workload and task saturation for the Pilot Flying.
- The Fire Main Deck non-normal checklist in the QRH was not fully completed by the crew or adhered to regarding the fire suppression flight level or land at nearest airport instruction.
- Task saturation due to smoke and multiple systems failures prevented effective use of the checklist by the crew.
- Communications between the ATCO units involved multiple stages of information exchange by landline and the destination aerodrome was not fully aware of the specific nature of the emergency, the difficulty that the Pilot Flying was experiencing or the assistance required.
- The Pilot Flying had not selected transponder code 7700, the emergency code, when radio communication with the destination aerodrome was not established.
Final Report:

Crash of a Dornier DO228-101 near Kathmandu: 14 killed

Date & Time: Aug 24, 2010 at 0725 LT
Type of aircraft:
Operator:
Registration:
9N-AHE
Survivors:
No
Schedule:
Kathmandu - Lukla
MSN:
7032
YOM:
1985
Flight number:
AG101
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
12
Pax fatalities:
Other fatalities:
Total fatalities:
14
Circumstances:
On approach to Lukla, the crew encountered poor weather conditions. Unable to locate the runway, he decided to divert to Simara Airport. Unfortunately, the visibility at Simara Airport was insufficient and the crew eventually decided to return to Kathmandu. While descending to runway 02, a generator failed. The crew did not declare an emergency, contacted his maintenance base and was unable to switch to the backup generator. Shortly after the crew elected to reset the battery system, the aircraft entered an uncontrolled descent and crashed in a rice paddy field. The aircraft disintegrated on impact and all 14 occupants were killed, among them 4 Americans, one British and one Japanese. The wreckage was found about 30 km southeast of Tribhuvan Airport.
Probable cause:
Loss of control on approach following the failure of a generator for undetermined reasons.

Crash of a PZL-Mielec AN-2R near Kumushkino

Date & Time: Aug 3, 2010 at 1900 LT
Type of aircraft:
Operator:
Registration:
UR-17915
Flight Phase:
Survivors:
Yes
MSN:
1G205-56
YOM:
1984
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was performing a crop-spraying flight when a unexpected situation occurred. The pilot-in-command attempted an emergency landing in a dirt track located between Kumushkino and Botanichnoye, when the aircraft crash landed. Both occupants escaped uninjured while the aircraft was damaged beyond repair. According to Ukrainian authorities, it appears that the aircraft was operated without any CofA and CofR.

Crash of a De Havilland DHC-2 Beaver in Ketchikan: 1 killed

Date & Time: Jul 23, 2010 at 0727 LT
Type of aircraft:
Operator:
Registration:
N9290Z
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Thorne Bay - Ketchikan
MSN:
1387
YOM:
1959
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
5300
Captain / Total hours on type:
4500.00
Aircraft flight hours:
21065
Circumstances:
The pilot had been advised by the Federal Aviation Administration flight service station (FSS) specialist to remain clear of the destination airport until the specialist could issue a special visual flight rules clearance. Instrument meteorological conditions prevailed at the airport, with a strong southeasterly wind. About 8 minutes after initial contact, the FSS specialist attempted to contact the pilot to issue the clearance but received no response. A witness about 0.5 mile southeast of the accident site said he saw the accident airplane flying very low over the treetops. He said the weather conditions consisted of low clouds, rain, and gusty southeasterly wind estimated at 30 to 40 knots. He said that, as the airplane passed overhead, it turned sharply to the left. As he watched the airplane, the wings rocked violently from side to side, and the nose pitched up and down. As the airplane passed low over hilly, tree-covered terrain, it rolled to the right, the right wing struck a large tree and separated, and the airplane descended behind a stand of trees. Pilots flying in the accident area reported strong wind with significant downdrafts and turbulence. A postaccident examination of the airplane did not disclose any preimpact mechanical malfunctions. Given the lack of mechanical deficiencies and the reports of turbulence and downdrafts, as well as the witness’ account of the airplane’s physical movements, it is likely that the pilot encountered significant terrain-induced turbulence and downdrafts while flying at low altitude. The area surrounding the accident site and portions of the pilot's earlier flight path were bordered by large areas of open and protected water, several of which were suitable for landing the float-equipped airplane.
Probable cause:
The pilot’s decision to continue the flight toward his destination in significant turbulence and downdrafts, and his subsequent failure to maintain control of the airplane while flying low over rising terrain.
Final Report:

Crash of a Piper PA-31T Cheyenne II near La Fragua Dam: 8 killed

Date & Time: Jul 7, 2010 at 1020 LT
Type of aircraft:
Operator:
Registration:
XB-MPV
Flight Phase:
Survivors:
No
Schedule:
Piedras Negras - Piedras Negras
MSN:
31-7820077
YOM:
1978
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
The twin engine aircraft was chartered by the State of Coahuila to conduct a survey flight of the area around Piedras Negras following recent floods and damages caused by hurricane Alex. The aircraft departed Piedras Negras Airport at 0930LT bound to the northwest. En route, while performing an aerial inspection of the area around the La Fragua Lake, the aircraft went out of control and crashed in a field, bursting into flames. The wreckage was found 600 metres south of the La Fragua Dam, about 35 km northwest of Piedras Negras Airport. The aircraft was destroyed by a post crash fire and all 8 occupants were killed.
Crew:
Juan Roberto Rendón, pilot,
Guillermo Ainsle Ibarra, copilot.
Passengers:
Horacio del Bosque Dávila, Coahuila's Secretary of Public works,
José Manuel Maldonado Maldonado, Mayor of Piedras Negras,
Ricardo Garza Bermea, Director of the Piedras Negras Civil Protection,
David Rey Chavira Jiménez,
Guillermo Ainsle Montemayor,
Alfonso Ainsle Montemayor.

Crash of a PZL-Mielec AN-2R in Sarybulak: 2 killed

Date & Time: Jun 24, 2010 at 1730 LT
Type of aircraft:
Operator:
Registration:
UP-A0161
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Taiynsha - Sorochinskiy
MSN:
1G206-40
YOM:
1984
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
The crew was on a positioning flight for a crop-spraying mission in North Kazakhstan when he lost his orientation between the villages of Taiynsha and Sorochinskiy. He landed on a small field near the village of Sarybulak to establish his position. After takeoff with a slight tail wind, at a height of 15 metres, the pilot-in-command initiated a left turn when the left lower wing struck a tree. The aircraft stalled and crashed, bursting into flames. Both pilots were killed while the engineer was seriously injured. The aircraft was totally destroyed by a post crash fire.
Probable cause:
The following findings were identified:
- Takeoff from a limited area,
- Failure to take into account obstacles by the crew during takeoff,
- Incorrect selection of the take-off site;
- High outside air temperature and tailwind component.

Crash of a Casa 212 Aviocar 100 near Mintom: 11 killed

Date & Time: Jun 19, 2010 at 1000 LT
Type of aircraft:
Operator:
Registration:
TN-AFA
Flight Phase:
Survivors:
No
Schedule:
Yaoundé - Yangadou
MSN:
151
YOM:
1979
Location:
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
11
Circumstances:
The aircraft departed Yaoundé-Nsimalen Airport at 0913LT on a charter flight to Yangadou, a small airstrip serving several iron mines in north Congo. At 0951LT, the crew made its last radio contact with ATC then the aircraft disappeared from radar screens. The wreckage was found around 1700LT on June 21 near Mintom. The aircraft was totally destroyed and all 11 occupants were killed, among them Ken Talbot, an Australian investor in iron business. The flight was conducted for the Cameroon company Cam Iron, a subcontractor of the Australian Sundance Resources Group.