Crash of a Beechcraft B200 Super King Air in Atqasuk

Date & Time: May 16, 2011 at 0218 LT
Operator:
Registration:
N786SR
Flight Type:
Survivors:
Yes
Schedule:
Barrow - Atqasuk - Anchorage
MSN:
BB-1016
YOM:
1982
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9000
Captain / Total hours on type:
500.00
Aircraft flight hours:
9847
Circumstances:
The pilot had worked a 10-hour shift the day of the accident and had been off duty about 2 hours when the chief pilot called him around midnight to transport a patient. The pilot accepted the flight and, about 2 hours later, was on an instrument approach to the airport to pick up the patient. While on the instrument approach, all of the anti-ice and deice systems were turned on. The pilot said that the deice boots seemed to be shedding the ice almost completely. He extended the flaps and lowered the landing gear to descend; he then added power, but the airspeed continued to decrease. The airplane continued to descend, and he raised the flaps and landing gear and applied full climb power. The airplane shuddered as it climbed, and the airspeed continued to decrease. The stall warning horn came on, and the pilot lowered the nose to increase the airspeed. The airplane descended until it impacted level, snow-covered terrain. The airplane was equipped with satellite tracking and engine and flight control monitoring. The minimum safe operating speed for the airplane in continuous icing conditions is 140 knots indicated airspeed. The airplane's IAS dropped below 140 knots 4 minutes prior to impact. During the last 1 minute of flight, the indicated airspeed varied from a high of 124.5 knots to a low of 64.6 knots, and the vertical speed varied from 1,965 feet per minute to -2,464 feet per minute. The last data recorded prior to the impact showed that the airplane was at an indicated airspeed of 68 knots, descending at 1,651 feet per minute, and the nose was pitched up at 20 degrees. The pilot did not indicate that there were any mechanical issues with the airplane. The chief pilot reported that pilots are on call for 14 consecutive 24-hour periods before receiving two weeks off. He said that the accident pilot had worked the previous day but that the pilot stated that he was rested enough to accept the mission. The chief pilot indicated he was aware that sleep cycles and circadian rhythms are disturbed by varied and prolonged activity. An NTSB study found that pilots with more than 12 hours of time since waking made significantly more procedural and tactical decision errors than pilots with less than 12 hours of time since waking. A 2000 FAA study found accidents to be more prevalent among pilots who had been on duty for more than 10 hours, and a study by the U.S. Naval Safety Center found that pilots who were on duty for more than 10 of the last 24 hours were more likely to be involved in pilot-at-fault accidents than pilots who had less duty time. The operator’s management stated that they do not prioritize patient transportation with regard to their medical condition but base their decision to transport on a request from medical staff and availability of a pilot and aircraft, and suitable weather. The morning of the accident, the patient subsequently took a commercial flight to another hospital to receive medical treatment for his non-critical injury/illness. Given the long duty day and the early morning departure time of the flight, it is likely the pilot experienced significant levels of fatigue that substantially degraded his ability to monitor the airplane during a dark night instrument flight in icing conditions. The NTSB has issued numerous recommendations to improve emergency medical services aviation operations. One safety recommendation (A-06-13) addresses the importance of conducting a thorough risk assessment before accepting a flight. The safety recommendation asked the Federal Aviation Administration to "require all emergency medical services (EMS) operators to develop and implement flight risk evaluation programs that include training all employees involved in the operation, procedures that support the systematic evaluation of flight risks, and consultation with others trained in EMS flight operations if the risks reach a predefined level." Had such a thorough risk assessment been performed, the decision to launch a fatigued pilot into icing conditions late at night may have been different or additional precautions may have been taken to alleviate the risk. The NTSB is also concerned that the pressure to conduct EMS operations safely and quickly in various environmental conditions (for example, in inclement weather and at night) increases the risk of accidents when compared to other types of patient transport methods, including ground ambulances or commercial flights. However, guidelines vary greatly for determining the mode of and need for transportation. Thus, the NTSB recommended, in safety recommendation A-09-103, that the Federal Interagency Committee on Emergency Medical Services (FICEMS) "develop national guidelines for the selection of appropriate emergency transportation modes for urgent care." The most recent correspondence from FICEMS indicated that the guidelines are close to being finalized and distributed to members. Such guidance will help hospitals and physicians assess the appropriate mode of transport for patients.
Probable cause:
The pilot did not maintain sufficient airspeed during an instrument approach in icing conditions, which resulted in an aerodynamic stall and loss of control. Contributing to the accident were the pilot’s fatigue, the operator’s decision to initiate the flight without conducting a formal risk assessment that included time of day, weather, and crew rest, and the lack of guidelines for the medical
community to determine the appropriate mode of transportation for patients.
Final Report:

Crash of a Xian MA60 off Kaimana: 25 killed

Date & Time: May 7, 2011 at 1405 LT
Type of aircraft:
Operator:
Registration:
PK-MZK
Survivors:
No
Schedule:
Jayapura - Sorong - Kaimana - Nabire - Biak
MSN:
06 03
YOM:
2008
Flight number:
MZ8968
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
21
Pax fatalities:
Other fatalities:
Total fatalities:
25
Captain / Total flying hours:
24470
Captain / Total hours on type:
199.00
Copilot / Total flying hours:
370
Copilot / Total hours on type:
234
Aircraft flight hours:
615
Aircraft flight cycles:
764
Circumstances:
On 7 May 2011, an Xi ’An MA60 aircraft, registered PK-MZK was being operated by PT. Merpati Nusantara Airline as a scheduled passenger flight MZ 8968, from Domine Eduard Osok Airport, Sorong, Papua Barat to Utarom Airport (WASK), Kaimana1, Papua Barat. The accident flight was part of series of flight scheduled for the crew. The aircraft departed from Sorong at 0345 UTC2 and with estimated arrival time in Kaimana at 0454 UTC. In this flight, the Second in Command (SIC) was as Pilot Flying (PF) and the Pilot in Command (PIC) as Pilot Monitoring (PM). On board the flight were 2 pilots, 2 flight attendants, 2 engineers and 19 passengers consisting of 16 adults, 1 child and 2 infants. The flight from Sorong was planned under the Instrument Flight Rules (IFR)3. The destination, Kaimana, had no published instrument approach procedure. Terminal area operations, including approach and landing, were required to be conducted under the Visual Flight Rules (VFR). At about 0425 UTC, after passing waypoint JOLAM the crew of MZ 8968 contacted Kaimana Radio and informed that the weather at Kaimana was raining, horizontal visibility of 3 to 8 kilometers, cloud Cumulonimbus broken at 1500 feet, south westerly wind at a speed of 3 knots, and ground temperature 29°C. The last communication with the crew of MZ 8968 occurred at about 0450 UTC. The flight crew asked whether there were any changes in ground visibility and the AFIS officer informed them that the ground visibility remained at 2 kilometer. The visual flight rules requires a visibility of minimum 5 km and cloud base higher than 1500 feet. The evidence indicates that during the final segment of the flight, both crew member were looking outside the aircraft to sight the runway. During this period the flight path of the aircraft varied between 376 to 585 feet and the bank angle increased from 11 to 38 degree to the left. The rate of descent then increased significantly up to about 3000 feet per minute and finally the aircraft impacted into the sea. The accident site was about 800 meters south west of the beginning of runway 01 or 550 meters from the coastline. Most of the wreckage were submerged in the shallow sea between 7 down to 15 meter deep. All 25 occupants were fatally injured. The aircraft was destroyed and submerged into the sea.
Probable cause:
FINDINGS:
1. The aircraft was airworthy prior the accident. There is no evidence that the aircraft had malfunction during the flight.
2. The crew had valid flight license and medical certificate. There was no evidence of crew incapacitation.
3. In this flight the SIC acted as Pilot Flying until the PIC took control of the aircraft at the last part of the flight.
4. According to company operation manual (COM), in a VMC (Visual Meteorological Condition), a “minimum, minimum” EGPWS alert while the approach was not stabilized should be followed by the action of abandoning the approach.
5. The cockpit crew did not conduct any crew approach briefing and checklist reading.
6. As it was recorded in the CVR during the final segment of the flight, both crews member were looking out-side to look for the runway. It might reduce the situational awareness.
7. At the final segment of the flight, the FDR recorded as follows:
• The approach was discontinued started at 376 feet pressure altitude (250 feet radio altitude) and reached the highest altitude of 585 feet pressure altitude. While climbing the aircraft was banking to the left reaching a roll angle of 38 degree. The torque of both engines was increased reaching 70% and 82% for the left and right engine respectively.
• During the go-around, the flaps were retracted to 5 and subsequently to 0 position, and the landing gears were retracted. The aircraft started to descend, and the pitch angle reached 13 degree nose down.
• The rate of descend increased significantly reaching about 3000 feet per minute, and finally the aircraft crashed into the shallow sea.
8. The rapid descent was mainly a result of a combination of situations such as high bank angle (up to 38 deg to the left) and the flaps retracted to 5 and subsequently to 0 position, and also the combination of other situations: engine torque, airspeed, and nose-down pitch.
9. The ERS button was determined in the CRUISE mode instead of TOGA mode. This had led the torque reached 70% and 82% during discontinuing the approach.
10. The flaps were retracted to 5 and subsequently to 0, while the MA-60 standard go-around procedure is to set the flaps at 15.
11. There was limited communications between the crew along the flight. This type of interaction indicated that there was a steep trans-cockpit authority gradient.
12. The SIC was trained in the first three batches which was conducted by the aircraft manufacturer instructor and syllabus, while the PIC was trained by Merpati instructor using modified syllabus. Inadequacy/ineffectivity in the training program may lead to actions that deviated from the standard procedure and regression to the previous type.
13. The investigation found that the Flight Crew Operation Manual (FCOM) and Aircraft Maintenance Manual (AMM) used non-standard English Aviation Language. This finding was supported by a review performed by the Australian Transport Safety Bureau (ATSB).
OTHER FINDINGS:
1. The DFDR does not have the Lateral and Longitudinal acceleration. These two parameters which were non safety related items were mandatory according to the CASR parts 121.343 and 121.344, and at the time of the MA 60 certification, the CCAR 121 did not require those two parameters.
2. Due to impact forces and immersion in water, the Emergency Locator Transmitter (ELT) did not transmit any signal.
FACTORS:
Factors contributed to the accident are as follows:
1. The flight was conducted in VFR in condition that was not suitable for visual approach when the visibility was 2 km. In such a situation a visual approach should not have been attempted.
2. There was no checklist reading and crew briefing.
3. The flight crew had lack of situation awareness when tried to find the runway, and discontinued the approach.
4. The missed approach was initiated at altitude 376 feet pressure altitude (250 feet radio altitude), the pilot open power to 70% and 82% torque followed by flap retracted to 5 and subsequently to 0. The rapid descent was mainly caused by continuously increase of roll angle up to 38 degree to the left and the retraction of flaps from 15 to 0 position.
5. Both crew had low experience/flying time on type.
6. Inadequacy/ineffectivity in the training program may lead to actions that deviated from the standard procedure and regression to the previous type.
Final Report:

Crash of a BAe 125-700A off Loreto

Date & Time: May 5, 2011 at 1155 LT
Type of aircraft:
Operator:
Registration:
N829SE
Flight Type:
Survivors:
Yes
MSN:
257095
YOM:
1980
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Loreto Airport, the crew encountered technical problems and elected to return. On final approach over the Gulf of California, in a gear up configuration, the aircraft struck the water surface and came to rest into the sea close to the shore, few dozen metres short of runway 34 threshold. Both pilots escaped uninjured while the aircraft was damaged beyond repair.

Crash of an Embraer ERJ-145EP in Moscow

Date & Time: Apr 28, 2011 at 1625 LT
Type of aircraft:
Operator:
Registration:
UR-DNK
Survivors:
Yes
Schedule:
Dniepropetrovsk – Moscow
MSN:
145-039
YOM:
1997
Flight number:
UDN505
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
30
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Dniepropetrovsk, the copilot started the approach to Moscow-Sheremetyevo Airport runway 25R with the flaps down at 22°. After touchdown, he started the braking procedure but the aircraft failed to decelerate as expected. The emergency braking systems were activated without any noticeable effect. Approaching the end of the runway at a speed of 70 knots, the copilot turn to the right in an attempt to veer off runway. The airplane ground looped then contacted a grassy area and lost its undercarriage before coming to rest. All 34 occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Failure of the brakes is suspected.

Crash of a Piper PA-31T Cheyenne II in Valparaiso

Date & Time: Apr 15, 2011 at 1200 LT
Type of aircraft:
Registration:
CC-CZC
Flight Type:
Survivors:
Yes
Schedule:
Robinson Crusoe Island - Valparaiso
MSN:
31-7920072
YOM:
1979
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7396
Captain / Total hours on type:
1092.00
Aircraft flight hours:
7168
Circumstances:
The twin engine aircraft departed Robinson Crusoe Island on a cargo flight to Valparaiso, carrying one passenger, one pilot and a load consisting of 1,000 lbs of lobsters. Upon landing at Valparaiso Airport in good weather conditions, the airplane went out of control, veered off runway, crossed a road and came to rest in a wooded area located along the highway. The aircraft was damaged beyond repair and both occupants escaped with minor injuries.
Probable cause:
The most likely cause of the accident would have been the loss of control of the aircraft when performing the flare, caused by a loss of lift (stall), because the CofG was beyond the rear limit.
The following contributing factors were identified:
- The aircraft was unstable on its longitudinal axis because the CofG was too far aft,
- The cargo was not properly secured in the cabin.
Final Report:

Crash of a Cessna 421B Golden Eagle II in Castries

Date & Time: Apr 13, 2011 at 1140 LT
Operator:
Registration:
N511LC
Flight Type:
Survivors:
Yes
Schedule:
Bridgetown – Castries
MSN:
421B-0423
YOM:
1973
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Bridgetown-Grantley Adams Airport, the pilot landed at Castries-George F. L. Charles (Vigie) Airport. Upon touchdown, the left main gear collapsed. The aircraft veered off runway and came to rest against a fence. The pilot was uninjured and the aircraft was damaged beyond repair.

Crash of a Cessna 402B in Biddeford: 1 killed

Date & Time: Apr 10, 2011 at 1805 LT
Type of aircraft:
Operator:
Registration:
N402RC
Flight Type:
Survivors:
No
Site:
Schedule:
White Plains - Portland
MSN:
402B-1218
YOM:
1977
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
4735
Captain / Total hours on type:
120.00
Aircraft flight hours:
6624
Circumstances:
The multi-engine airplane was being repositioned to its base airport, and the pilot had requested to change the destination, but gave no reason for the destination change. Radar data indicated that the airplane entered the left downwind leg of the traffic pattern, flew at pattern attitude, and then performed a right approximate 250-degree turn to enter the final leg of the approach. During the final leg of the approach, the airplane crashed short of the runway into a house located in a residential neighborhood near the airport. According to the airplane's pilot operating handbook, the minimum multi-engine approach speed was 95 knots indicated airspeed (KIAS), and the minimum controllable airspeed was 82 KIAS. According to radar data, the airplane's ground speed was about 69 knots with the probability of a direct crosswind. Post accident examination of the propellers indicated that both propellers were turning at a low power setting at impact. During a controlled test run of the right engine, a partial power loss was noted. After examination of the throttle and control assembly, two o-rings within the assembly were found to be damaged. The o-rings were replaced with comparable o-rings and the assembly was reinstalled. During the subsequent test run, the engine operated smoothly with no noted anomalies. Examination of the o-rings revealed that the damage was consistent with the o-rings being pinched between the corner of the top o-ring groove and the fuel inlet surface during installation. It is probable that the right engine had a partial loss of engine power while on final approach to the runway due to the damaged o-ring and that the pilot retarded the engine power to prevent the airplane from rolling to the right. The investigation found no mechanical malfunction of the left engine that would have prevented the airplane from maintaining the published airspeed.
Probable cause:
The pilot did not maintain minimum controllable airspeed while on final approach with a partial loss of power in the right engine, which resulted in a loss of control. Contributing to the accident was the partial loss of engine power in the right engine due to the improperly installed o-rings in the engine’s throttle and control assembly.
Final Report:

Crash of a Rockwell Sabreliner 60 in Fort Lauderdale

Date & Time: Apr 9, 2011 at 1357 LT
Type of aircraft:
Operator:
Registration:
N71CC
Flight Type:
Survivors:
Yes
Schedule:
Fort Lauderdale – West Palm Beach
MSN:
306-71
YOM:
1974
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On approach to West Palm Beach Airport, the crew encountered technical problems with the undercarriage that could not be lowered. The crew decided to return to his base in Fort Lauderdale. On final, the crew was again unable to lower the gear so the decision was taken to complete a wheels-up landing. The airplane landed on its belly on runway 08 then slid for few dozen metres before coming to rest. The occupants escaped uninjured and the aircraft was damaged beyond repair.
Probable cause:
No investigation was carried out by the NTSB.

Crash of a Rockwell Shrike Commander 500S in Eden Prairie

Date & Time: Apr 8, 2011 at 1730 LT
Operator:
Registration:
N51RF
Flight Type:
Survivors:
Yes
Schedule:
Eden Prairie - Eden Prairie
MSN:
500-3298
YOM:
1976
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
473
Captain / Total hours on type:
217.00
Copilot / Total flying hours:
4659
Copilot / Total hours on type:
2480
Aircraft flight hours:
11298
Circumstances:
The pilot reported that he performed a stabilized visual approach with a right crosswind. The airplane touched down on the centerline and subsequently drifted to the right. The pilot overcorrected for the drift and the airplane veered hard to the left. The airplane continued off the left side of the runway and skidded to a complete stop. The right main landing gear collapsed and the right wingtip hit the ground, which resulted in substantial damage to the fuselage and wing. A postaccident inspection of the airplane revealed no preimpact anomalies. The pilot additionally reported that there was no mechanical malfunction or failure.
Probable cause:
The pilot's inadequate compensation for the crosswind while landing, which resulted in a loss of directional control.
Final Report:

Crash of a Canadair RegionalJet CRJ-100ER in Kinshasa: 32 killed

Date & Time: Apr 4, 2011 at 1356 LT
Operator:
Registration:
4L-GAE
Flight Type:
Survivors:
Yes
Schedule:
Kisangani – Kinshasa
MSN:
7070
YOM:
1995
Flight number:
UNO834
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
29
Pax fatalities:
Other fatalities:
Total fatalities:
32
Captain / Total flying hours:
2811
Captain / Total hours on type:
1622.00
Copilot / Total flying hours:
495
Copilot / Total hours on type:
344
Circumstances:
On final approach to Kinshasa-N'Djili Airport, the crew encountered very poor weather conditions and decided to make a go around. After a climb process of 12 seconds, the aircraft nosed down and at a speed of 180 knots, hit the ground 170 meters to the left of the displaced threshold of runway 24. The aircraft slid for 400 meters before coming to rest in flames upside down. Three passengers were seriously injured and evacuated but of them died from their injuries few hours later. Finally, only one passenger survived the accident. Aircraft was performing a special flight from Kisangani to Kinshasa on behalf of the United Nations Organization Stabilization Mission in the Democratic Republic of the Congo (MONUSCO). The only survivor reported that the aircraft suddenly plunged into the earth while on final approach. At the time of the accident, weather conditions were marginal with storm activity, heavy rain showers, scattered at 2,200 feet and cumulonimbus at 1,500 feet.
Probable cause:
Weather in Kinshasa was bad at the time of the accident, ATC failed to inform the crew about the degradation of the weather conditions and the runway in use was not closed to traffic while the visibility was below the minima. Despite this situation, the crew took the decision to continue the approach procedure while the aircraft was unstable and the approach speed was too high (180 knots). It is reported that the following factors contributed to the accident:
- the crew ignored the published approach procedures,
- improper crew resources management during the execution of the flight,
- during the go around process, the crew encountered adverse weather conditions with vertical wind gusts, downdrafts and a 'magenta' effect. This caused the aircraft to adopt nose down attitude while it was in the final stage of the flight, preventing the pilot to take over the control,
- the pilot training program was inadequate and did not include a proportionate number of flight in the simulator,
- the authority for civil aviation of Georgia has probably approved a small training program for upgrading the captain to his position,
- lack of oversight of the operator by the Georgian Civil Aviation Authority.
In conclusion, investigators believe that the most probable cause of the accident is the fact that the plane encountered a very dangerous meteorological phenomena similar to a microburst, to a very low level during the overshoot process. The dangerous vertical downdraft and gust caused a sudden and remarkable change in the attitude of the aircraft and a substantial loss of altitude. Flying at very low altitude, recovery of such disturbance was not possible.
Final Report: