Crash of a De Havilland DHC-8-202Q in Ilulissat

Date & Time: Jan 29, 2014 at 0842 LT
Operator:
Registration:
OY-GRI
Survivors:
Yes
Schedule:
Kangerlussuaq – Ilulissat
MSN:
477
YOM:
1997
Flight number:
GRL3205
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
12
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4201
Captain / Total hours on type:
739.00
Copilot / Total flying hours:
1592
Copilot / Total hours on type:
1022
Aircraft flight hours:
29947
Aircraft flight cycles:
41968
Circumstances:
Upon landing on runway 07 at Ilulissat (BGJN) in gusting crosswind conditions above the aircraft and the operator limited maximum crosswind components, the left main landing gear collapsed. The aircraft skidded off the left side of the runway in a nose right position and into the safety zone. The aircraft continued an increasingly sideways skid in a nose right position, skidded down a steep snow-covered slope and impacted a rocky area approximately 10 meters below the runway elevation. One passenger and one crew member suffered minor injuries. The aircraft was destroyed. The accident occurred in dark night and under visual meteorological conditions (VMC).
Probable cause:
The following factors were identified:
- A non-optimum CRM on final approach to runway 07 led to flight crew target fixation and a mental blocking of an appropriate decision on going around.
- A non-stabilized approach in crosswind conditions above the aircraft and the operator’s crosswind limitations combined with the actual crosswind landing technique and the power levers retarded below flight idle in flight resulted in an accelerated rate of descent leading to a hard landing, with side load on the left main landing gear at touchdown.
- The left main landing gear structural fuse pin sheared as a result of lateral and vertical overload stress.
- Cycling the power levers between ground and flight range prevented an appropriate deceleration of the aircraft and prolonged the landing roll.
- The combination of applying full left rudder and no decisive use of reverse thrust on the side with the unaffected main landing gear made it impossible for the flight crew to maintain directional control.
Final Report:

Crash of a Saab 2000 in Paris-Roissy-CDG

Date & Time: Jan 28, 2014 at 0731 LT
Type of aircraft:
Operator:
Registration:
HB-IZG
Survivors:
Yes
Schedule:
Leipzig – Paris
MSN:
010
YOM:
1994
Flight number:
DWT250
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
16
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6640
Captain / Total hours on type:
2260.00
Copilot / Total flying hours:
630
Copilot / Total hours on type:
80
Circumstances:
Following an uneventful flight from Leipzig, the crew started the descent to Paris-Roissy-CDG Airport runway 27R. At an altitude of 400 feet on approach, the automatic pilot system was deactivated. At an altitude of 200 feet, the decision height, the crew decided to continue the approach as the runway was in sight and the aircraft was stable. During the last segment, at a height of 50 feet, power levers were reduced to flight idle and the aircraft went into a nose up attitude (maximum value of 11°). Both main gears touched down at a speed of 120 knots but the aircraft bounced twice and went into a pitch down attitude, causing the nose gear to land first during the third touchdown. On impact, the nose gear collapsed and the aircraft slid for dozen yards before coming to rest. All 19 occupants were evacuated safely and the aircraft was later considered as damaged beyond repair.
Probable cause:
During the flare the captain detected that the landing would be hard and in an emergency action, he quickly pulled the nose up without announcing his intention to the first officer who was the pilot flying. This lack of coordination within the flight crew caused a double controls and successive and opposite actions on the flight controls during the bouncing management.
Final Report:

Crash of a Beechcraft C90 King Air in Columbia

Date & Time: Jan 27, 2014 at 0530 LT
Type of aircraft:
Operator:
Registration:
N350WA
Flight Type:
Survivors:
Yes
Schedule:
Sacramento - Columbia
MSN:
LJ-762
YOM:
1978
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2939
Captain / Total hours on type:
1784.00
Copilot / Total flying hours:
6658
Copilot / Total hours on type:
2237
Aircraft flight hours:
9501
Circumstances:
The commercial pilot, who was the pilot flying (PF), and the airplane transport pilot, who was the pilot not flying (PNF), were conducting an aeromedical positioning flight. The pilots reported that, during a night approach, they visually identified the airport, activated the runway lighting system, and then canceled the instrument flight plan for a visual approach. The PNF reported that, after turning onto the final approach, the flaps were fully lowered and that the airplane was in a “wings level, stabilized approach.” The PF reported that he was initially using the vertical approach slope indicator (VASI) for guidance but that the airplane drifted below the glidepath during the approach, and he did not correct back to the glidepath. On short final, the pilots verified that the landing gear were in the down-and-locked position by noting the illumination of the three green landing gear indicator lights, and the airspeed indicator indicated 110 knots. Both pilots reported that the landing was “firm” and that it was followed by a loud bang and the subsequent failure of all three landing gear. The airplane slid on its belly for about 825 ft down the runway before coming to rest. Both pilots evacuated the airplane, which was subsequently consumed by a postaccident fire. Both pilots reported that the airplane was operating normally with no discrepancies noted. Postaccident examination of the wreckage at the accident site revealed that the airplane impacted the runway about 100 ft short of its displaced threshold. Broken components of the landing gear were located along the debris field, which extended about 565 ft beyond the initial impact point. It is likely that the PF's failure to correct and maintain the VASI glidepath after allowing the airplane to descend below the glidepath and the touchdown at a high descent rate resulted in a hard landing and the subsequent failure of all three landing gear.
Probable cause:
The pilot’s unstabilized night visual approach, which resulted in a hard landing and the collapse of all three landing gear.
Final Report:

Crash of a Boeing 737-3B7(SF) in Honiara

Date & Time: Jan 26, 2014 at 1259 LT
Type of aircraft:
Operator:
Registration:
ZK-TLC
Flight Type:
Survivors:
Yes
Schedule:
Brisbane – Honiara
MSN:
23705/1497
YOM:
1988
Flight number:
PAQ523
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Brisbane, the crew completed the approach and landing at Honiara-Henderson Airport. After touchdown on runway 24, the right main gear collapsed and punctured the right wing. The aircraft veered slightly to the right and came to a halt on the runway. All three occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
The failure of the right main gear was the consequence of an inappropriate rework (ie, machining and re-threading) of the tee-bolt fitting and the associated installation of a reduced size nut and washer, during the last overhaul in 2004.

Crash of an Antonov AN-24RV in Moscow

Date & Time: Jan 22, 2014 at 0819 LT
Type of aircraft:
Operator:
Registration:
RA-46473
Survivors:
Yes
Schedule:
Pskov - Moscow
MSN:
2 73 081 01
YOM:
1972
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
24
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On approach to Moscow-Domodedovo Airport, the crew encountered poor visibility due to marginal weather conditions. Rather than initiating a go-around procedure, the crew continued the descent when the aircraft crash landed to the right of runway 14R, in an area between the runway and the boundary fence. All 28 occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Piper PA-31-350 Navajo Chieftain in Langgur: 4 killed

Date & Time: Jan 19, 2014 at 1225 LT
Operator:
Registration:
PK-IWT
Flight Type:
Survivors:
No
Schedule:
Jayapura – Langgur – Kendari – Surabaya
MSN:
31-7752090
YOM:
1977
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
2860
Captain / Total hours on type:
1045.00
Aircraft flight hours:
5859
Circumstances:
On 19 January 2014, a PA-31-350 Piper Chieftain, registered PK-IWT, was being operated by PT. Intan Angkasa Air Service, on positioning flight from Sentani Airport, Jayapura with intended destination of Juanda Airport, Surabaya for aircraft maintenance. The positioning flight was planned to transit at Dumatubun Airport Langgur of Tual, Maluku and Haluoleo Airport, Kendari at South East Sulawesi for refuelling. On the first sector, the aircraft departed Sentani Airport at 2351 UTC (0851 WIT) and estimated arrival at Langgur was 0320 UTC. On board on this flight was one pilot, two company engineers and one ground staff. At 0240 UTC the pilot contacted to the Langgur FISO, reported that the aircraft position was 85 Nm to Langgur Airport at altitude 10,000 feet and requested weather information. Langgur FISO acknowledged and informed that the weather was rain and thunderstorm and the runway in used was 09. When the aircraft passing 5,000 feet, the pilot contacted the Langgur FISO and reported that the aircraft position was 50 Nm from langgur and informed the estimated time of arrival was 0320 UTC. The Langgur FISO acknowledged and advised the pilot to contact when the aircraft was at long final runway 09. At 0318 UTC, the pilot contacted Langgur FISO, reported the position was 25 Nm to Langgur at altitude of 2,500 feet and requested to use runway 27. The Langgur FISO advised the pilot to contact on final runway 27. At 0325 UTC, Langgur FISO contacted the pilot with no reply. At 0340 UTC, Langgur FISO received information from local people that the aircraft had crashed. The aircraft was found at approximately 1.6 Nm north east of Langgur Airport at coordinate 5° 38’ 30.40” S; 132° 45’ 21.57” E. All occupants fatally injured and the aircraft destroyed by impact force and post impact fire. The aircraft was destroyed by impact forces and post impact fire, several parts of the remaining wreckage such as cockpit could not be examined due to the level of damage. The aircraft was not equipped with flight recorders and the communication between ATC and the pilot was not recorded. No eye witness saw the aircraft prior to impact. Information available for the investigation was limited. The analysis utilizes available information mainly on the wreckage information including the information of the wings, engines and propellers.
Probable cause:
The investigation concluded that the left engine most likely failed during approach and the propeller did not set to feather resulted in significant asymmetric forces. The asymmetric forces created yaw and roll tendency and the aircraft became uncontrolled, subsequently led the aircraft to impact to the terrain.
Final Report:

Crash of a Cessna 208B Grand Caravan in Olive Creek: 2 killed

Date & Time: Jan 18, 2014 at 1057 LT
Type of aircraft:
Operator:
Registration:
8R-GHS
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Olive Creek - Imbaimadai
MSN:
208B-0830
YOM:
2000
Flight number:
TGY700
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
3108
Captain / Total hours on type:
2555.00
Aircraft flight hours:
17998
Circumstances:
On 17th January, 2014, the day before the accident, the pilot departed from his company base, Ogle International Airport (SYGO) with another aircraft, a Cessna 208B, Registration – 8R-GHT. He was tasked to do two days of shuttling; the first day between Olive Creek and Ekereku Bottom Airstrips, and the second day between Olive Creek and Imbaimadai Airstrips. The pilot was accompanied by a third crew/loader, whose duty was to ensure that the aircraft was properly loaded for each trip, and an aircraft engineer who was assigned to carry out minor maintenance duties and refuel the aircraft as required for the duration of the shuttle operations. It was reported that on the first day, during a landing at Ekereku Bottom, the aircraft encountered severe wind conditions that resulted in a hard landing. The pilot was very concerned about the hard landing and expressed this to several individuals. He was concerned enough to log the hard landing in the Aircraft Technical Log. After the hard landing the aircraft was visually inspected by the engineer who declared the aircraft fit for flight. However while taxying prior to takeoff the aircraft suffered a right brake seizure. The engineer freed and bled the brake line. Tests were done on the brakes and the aircraft was flown to Olive Creek. The hard landing and the brake failure were reported to base and an instruction was passed that this aircraft should be brought back to Ogle by another pilot. Another Cessna 208B aircraft, 8R-GHS, the accident aircraft, was left with the pilot for him to complete his shuttle schedule the next day. On the afternoon of the first day, the pilot flew this aircraft, 8R-GHS to Kamarang Airstrip, where he overnighted. On the second day, 18th January, 2014, he departed Kamarang at 10:30hrs UTC for Olive Creek with the engineer and the loader. The engineer was left at Olive Creek. The pilot, with the loader, did one shuttle from Olive Creek to Imbaimadai. He returned to Olive Creek where the aircraft was refueled and then did three shuttles between Olive Creek and Imbaimadai. After these three shuttles the aircraft was again refueled. He completed one shuttle, Olive Creek/Imbaimadai/Olive Creek and had just taken off on the second in this series of shuttles when the accident occurred during midmorning. Both the pilot and the third crew were killed in the crash.
Probable cause:
The investigation revealed that the probable cause of the accident was due to a power loss suffered by the engine. The power loss was associated with the fracture of one of the 1st stage compressor stator vanes by fatigue. The fatigue crack originated from a lack of brazing adhesion extending over approximately 0.280 inches along the chord length and 0.050 inches in the direction of the shroud thickness and was located between the leading edge and mid-chord of the vane.
The following findings were identified:
1. The flight was one of a series of cargo shuttles that had originated the day before the accident, with another aircraft that was fitted with the Blackhawk modification.
2. The hard landing followed by the brake failure that occurred on the originating day had upset the pilot and caused him much concern.
3. A decision was taken to replace the original aircraft being used by the accident pilot with another one, which was also fitted with the Blackhawk modification.
4. The pilot had completed five shuttles on the day of the accident. The sixth shuttle was the accident flight.
5. The weather was satisfactory for VFR operations.
6. There was no fire.
7. Both the pilot and the third crew/loader were killed in this accident.
8. This accident occurred 2½ minutes after take-off.
9. The wreckage site was difficult to access, this along with unavailability of suitable equipment, contributed to the delay in extraction of the bodies.
Final Report:

Crash of a Douglas DC-9-33CF in Saltillo

Date & Time: Jan 18, 2014 at 0423 LT
Type of aircraft:
Operator:
Registration:
XA-UQM
Flight Type:
Survivors:
Yes
Schedule:
Managua – Tapachula – Saltillo
MSN:
47191/280
YOM:
1968
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13447
Captain / Total hours on type:
9235.00
Copilot / Total flying hours:
10736
Copilot / Total hours on type:
525
Aircraft flight hours:
57319
Aircraft flight cycles:
53457
Circumstances:
The aircraft departed Managua on a cargo flight to Saltillo with an intermediate stop in Tapachula, carrying two passengers and two pilots on behalf of DHL. During a night approach to Saltillo Airport, the crew was cleared to land on runway 17. One minute later, he initiated a go-around and decided to divert to Monterrey Airport which was the alternate. Due to a poor flight preparation, the crew was unaware that Monterrey Airport was closed to traffic that night. So few minutes later, the crew returned to Saltillo and was again cleared to land on runway 17. At that time, weather conditions were marginal with a limited visibility due to fog. Following an ILS CAT I approach, the pilot-in-command descended below the MDA and continued the approach despite he did not establish any visual contact with the runway and its equipment. The aircraft landed hard to the right of the runway and on the last third of the runway. After landing, the aircraft rolled for few dozen metres, lost its nose gear and came to rest against an embankment. All four occupants were injured and the aircraft was damaged beyond repair.
Probable cause:
Continuing the precision approach (ILS CAT 1) in conditions of reduced visibility by fog (no visual contact with the runway at an airport below minimums), which resulted in an abrupt landing and misaligned to the right on the last third of the runway, during a second landing attempt. The continuation of the landing was the lack of fuel to fly to a second alternate airport not contemplated in the operation.
Contributing factors:
1. Lack of analysis of pre-flight operational information (current NOTAMs, METAR, forecasts, fuel to second alternate airport and flight tracking).
2. Unstabilized approach.
3. Lack of application of CRM concepts.
4. Lack of adherence to procedure - operations, of providing METAR and NOTAM to the crew for the dispatch of the aircraft.
5. Lack of adherence to the procedure for flight control and tracking.
6. Lack of procedures to establish two alternate airports when the destination airport is below minimums.
7. Lack of Company supervision, operation and maintenance surveillance of aircraft flight recorders.
Final Report:

Crash of a Cessna 501 Citation I/SP in Trier: 4 killed

Date & Time: Jan 12, 2014 at 1152 LT
Type of aircraft:
Operator:
Registration:
N452TS
Flight Type:
Survivors:
No
Schedule:
Shoreham - Trier
MSN:
501-0231
YOM:
1981
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
4800
Captain / Total hours on type:
32.00
Copilot / Total flying hours:
1350
Copilot / Total hours on type:
550
Aircraft flight hours:
4282
Aircraft flight cycles:
4413
Circumstances:
On Friday, 10 January 2014, the airplane had flown from Trier to Shoreham, where it landed at 1456 UTC. Two pilots and two passengers were on board the aircraft. Over the weekend, the passengers wanted to participate in a hunt. On the afternoon of 11 January 2014 the PIC told the service provider, tasked by the aircraft owner with the flight planning, to prepone the scheduled return flight on Sunday, 12 January 2014, from 1400 UTC to 1015 UTC. In the ATC flight plan Trier-Föhren Airfield was the destination aerodrome and Luxembourg Airport the alternate aerodrome. According to the flight plan the change of flight rules from IFR to VFR was to occur at reporting point PITES. The handling agent at Shoreham Airport stated that the PIC and the co-pilot had arrived on Sunday at 0850 UTC. The airport made the recordings of a video camera for apron surveillance available to the BFU. These recordings show that the airplane was refuelled in the presence of the pilots. The two passengers arrived at 0936 UTC and about 11 minutes later the aircraft taxied from the apron. At 1000 UTC, the airplane took off from runway 20. At 1138:25 hrs, the co-pilot established contact with Langen Radar. At that time the airplane was in Flight Level (FL) 170. At 1142:51 hrs, after the airplane had descended to FL140, the controller issued the descent clearance to FL70. Approximately one minute later the controller said: "… proceed direct destination again and descend altitude five thousand feet … Spangdahlem QNH one zero two five." The pilot in command acknowledged the clearance. At 1145:23 hrs the PIC said: "… standing by for cancelling IFR." The controller answered: "... roger, IFR is cancelled at one zero two five, your position is one five miles northwest of your destination airfield, squawk VFR, approved to leave." According to radar data, the airplane was approximately in FL90 and continued to fly with a southern heading. At 1147:26 hrs, about 5 NM east of the omnidirectional radio beacon Nattenheim (VOR NTM), the altitude was 4,900 ft AMSL. According to the radar data at 1148:10 hrs the airplane had reached 3,500 ft AMSL. The flight path continued east until 1149 hrs when, in the area of the city of Wittlich in an altitude of 3,500 ft AMSL, the airplane turned right. The ground speed was approximately 180 kt. In the course of the right turn until 1150:30 hrs, the altitude decreased further to about 2,800 ft AMSL and the ground speed to about 160 kt. At 1151:10 hrs the aircraft turned left maintaining altitude until it had reached a southern heading. From 1151:30 hrs on it continued to descend. At the time the airplane was approximately 6.7 NM from the runway threshold and about 0.5 NM north of the extended runway centre line. Approximately 15 seconds later it reached the extended runway centre line of runway 22 while it turned right into the final approach direction. It was in about 2,300 ft AMSL and approximately 5.7 NM from the runway. From 1152:20 hrs on, at approximately 4.6 NM from the threshold, the aircraft began to leave the extended runway centre line to the south. At that time, altitude was approximately 1,600 ft AMSL and ground speed about 160 kt. The last radar target was recorded at 1152:40 hrs with an altitude indication of approximately 1,300 ft AMSL and a ground speed of about 140 kt. The attention of several witnesses, located about 600 m north-east and south-east, respectively, of the accident site in the valley of the river Salm, was drawn to the airplane by engine noise. They congruently stated that the aircraft had come from the direction of the town Esch and flown in low altitude, below the fog or cloud cover, toward the south-west. One of the witnesses estimated the altitude was 15 to 20 m above the trees bordering the river Salm, approximately the same height as the open wire located in the area. According to congruent witnesses’ statements, the engine thrust was increased and the airplane pulled up shortly before reaching a wooded escarpment rising by about 60 m, banked left and disappeared in the fog. Immediately afterwards fire had become visible and impact noises had been heard. The airplane impacted the ground in an inverted position. The occupants suffered fatal injuries and the aircraft was destroyed. The Flugleiter (A person required by German regulation at uncontrolled aerodromes to provide aerodrome information service to pilots) at Trier-Fohren Airfield stated, that on the morning of the accident day, at about 1010 hrs, he had received a phone call from the PIC. During the call the arrival of the airplane had been announced for 1230 hrs. The Flugleiter had informed the PIC about the severe fog prevailing at the airfield. He had also told him that, if at all, he expected visibility would increase after 1330 or 1400 hrs. After the phone conversation the Flugleiter assumed, that the airplane would fly to another airport. According to statements by the PIC’s wife, she had talked with her husband on the landline and then witnessed the PIC’s phone conversation on his mobile phone with the passenger, where he was asked to prepone the return flight to late morning. An unexpected appointment of the passengers was named as reason for the wish. During a phone conversation prior to departure her husband had explained that he had talked with Trier Airfield and learned that fog was prevailing there and one would fly either to Hahn or Luxembourg. The son of the passengers stated at the police that on the morning of the day of the accident his father had called him. He had told him that the airplane would probably land at Frankfurt-Hahn Airport. He stated that for his parents there was no deadline pressure. He said, that for him it is “völlig unvorstellbar (entirely inconceivable)” that his father would pressure the pilot to fly to Trier. In the past deviation to another airport had often been the case. It had never been a problem.
Probable cause:
The accident was due to the following:
- The Pilot in Command (PIC) decided to conduct the VFR approach even though he was aware of the prevailing instrument weather conditions at the airport,
- It is likely that a wrong vertical profile was flown due to an erroneous selection on the navigation system,
- Due to an insufficient situational awareness of the pilots the descent was not aborted in time.
The following factors contributed to the accident:
- Insufficient Crew Resource Management (CRM).
Final Report:

Crash of a Gippsland GA-8 Airvan in Cayenne

Date & Time: Jan 6, 2014 at 1508 LT
Type of aircraft:
Registration:
F-ORPH
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Cayenne – Maripasoula
MSN:
GA8-04-050
YOM:
2004
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1100
Captain / Total hours on type:
41.00
Circumstances:
The single engine aircraft departed Cayenne-Rochambeau-Félix Éboué Airport runway 08 at 1448LT on a cargo flight to Maripasoula, carrying one female passenger and one pilot. About three minutes into the flight, while cruising at an altitude of 1,500 feet, the plot encountered engine problems, declared an emergency and was cleared for an immediate return. The aircraft landed back at 1452LT. Some controls were performed on the engine and the aircraft took off again at 1507LT. Less than a minute later, the engine lost power. The pilot again declared an emergency and returned to the airport. On short final, the aircraft lost height and crashed in bushes some 800 metres short of runway 26. The passenger was seriously injured and the pilot was slightly injured. The aircraft was destroyed.
Probable cause:
Loss of engine power during initial climb due to an abnormal wear of the cam lobes and tappets, for reasons that investigations were unable to determine. It is possible that pitting corrosion initiated this degradation which was not identified during the last periodic engine inspection.
Final Report: