Crash of a Quest Kodiak 100 in Pskov

Date & Time: Jul 6, 2015 at 1618 LT
Type of aircraft:
Operator:
Registration:
N642RM
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Riga – Pskov – Krutitsy
MSN:
100-0104
YOM:
2013
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
470
Captain / Total hours on type:
52.00
Copilot / Total flying hours:
1041
Copilot / Total hours on type:
10
Aircraft flight hours:
391
Circumstances:
On 03.07.2015 at 15:05, Kodiak-100 N642RM airplane, which had left Riga AP (Latvia), performed a landing at Pskov AD (RF). The airplane was performing a ferry flight from USA (where it was bought) to Krutitsy landing site, which is 80 km to the Southeast from Ryazan (RF). After the landing, flight crewmembers and passengers passed a border and customs control successfully. The aircraft was kept at Pskov AD from July 3 till July 6 under custody of AASS of Pskovavia (JSC). On 06.07.2015 at 08:00, the flight crew – PIC and FO – arrived to Pskov AD with a view to the ferry flight resumption. PIC was planning to fly the aircraft from Pskov AD to Krutitsy landing site on 06.07.2015. In violation of FAP MA CA and FAP-128 requirements, PIC and FO didn't pass a preflight medical check in spite of the fact that Pskovavia medical service was available at the aerodrome. Before the takeoff, two flight crewmembers were in the cockpit: PIC occupying a left seat, and FO occupying a right seat. Both were secured with safety belts. At 13:15:30, PIC performed a takeoff from Pskov AD with MH=190°. According to the flight crew explanatory reports, during the climbing with left turn, they had the engine troubles. Therefore, the flight crew put the airplane into gliding. They failed to re-start the engine in flight. Before the emergency landing, they cut the fuel off and de-energized the aircraft. The landing was performed at 13:18 to a marshy area with some bushes and individual trees around. The aircraft received significant damage during the landing. There was no fire: neither in flight nor on the ground. At 13:21:21, FO reported the forced landing to ATC controller, using the aircraft radio station. Pskov First-Aid Station suggested the help, but the flight crewmembers refused because they did not have any injuries.
Probable cause:
The accident with Kodiak 100 N642RM aircraft occurred when performing a forced landing to the forest. According to the flight crewmembers explanations, the need of this forced landing was caused by the engine power loss in flight. Conducted examinations of engine, rotor and fuel system did not reveal any issue that can cause the power plant loss of power. Because FDIS SD data card from the central display, which storages all recorded power plant flight parameters was lost, it was not possible to access the engine operability and the flight crewmembers' actions in full.
Final Report:

Crash of a Quest Kodiak 100 in Doyo Baru: 2 killed

Date & Time: Apr 9, 2014 at 0940 LT
Type of aircraft:
Operator:
Registration:
PK-SDF
Flight Phase:
Survivors:
Yes
Schedule:
Doyo Baru – Ninia
MSN:
100-0049
YOM:
2011
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
25530
Captain / Total hours on type:
1752.00
Aircraft flight hours:
1752
Aircraft flight cycles:
2211
Circumstances:
A Kodiak-100 aircraft, registered PK-SDF, on 9 April 2014 was being operated by PT. Adventist Aviation Indonesia as non-schedule flight from Doyo Baru Airstrip with intended destination of Ninia Airstrip, Papua. On board in this flight were 7 persons consist of one pilot and six passengers. This flight was the fourth flights for the pilot who has performed flights from Doyo Baru (DOB) – Puldamat (PUL) at 2138-2228 UTC; Puldamat (PUL) –Soya (SOY) at 2243-2247 UTC; Soya (SOY) – Doyo Baru (DOB) at 2256-2344 UTC. The flight time to destination was estimated of 1 hour with cruising altitude of 10,000 feet and the fuel on board were sufficient for 4 hours flight time. Doyo Baru Airstrip located at approximately 10 NM North West of Sentani Airport (WAJJ). Air traffic movement to and from Doyo Baru Airstrip was controlled by Sentani Tower controller. At 0015 UTC, the pilot contacted to Sentani Tower controller, requested for start engine and clearance to fly to Ninia. The requests were approved and to report when ready for departure. At 0021 UTC, the pilot reported to the Sentani Tower controller ready for departure from Doyo Baru Airstrip. The Sentani Tower Controller instructed the pilot to hold to wait an aircraft took off from Sentani Airport. At 0024 UTC, the pilot received clearance for takeoff with additional traffic information and to report after airborne. At 0027 UTC, Sentani Tower controller has not received reports from the PK-SDF pilot and tried to call but was not responded. After several observations toward Doyo Baru area and did not see PK-SDF aircraft, The Sentani Tower controller reported to the Chief Section of Sentani Tower Air Navigation. At 0030 UTC, The Chief Section of Sentani Tower Air Navigation clarified the condition of PK-SDF aircraft to one of Indonesian Adventist Aviation pilot in Doyo Baru and obtained information that the aircraft had experienced in accident during takeoff at Doyo Baru. An engineer after received the information went to the accident site and saw appearance of white smoke came out from the side of the river which was known as the accident aircraft located. After arrived at the accident site the engineer saw the Adventist’s staffs and local people tried to extinguish the fire on the aircraft engine by throwing some water and used two fire extinguishers while some people moved the passengers from the wreckage. Two occupants including the pilot were fatally injured and five other passengers were seriously injured. All occupants were taken to Yowari Hospital (Rumah Sakit Umum Daerah – RSUD Yowari).
Probable cause:
Contributing Factors:
- The failure to airborne was due to the aircraft was not in correct takeoff configuration which required wing flap 20° while the flap was found at approximately 6° position during impact.
- The actions to recover the situation by selection of emergency power and flap were not proper for particular condition.
Final Report: