Casualties unknown

2020-12-26: Cessna 208B (PK-SNR) — Smart Aviation — Sela Airstrip, Papua, ID

Sela Airstrip, Papua, ID

On December 26, 2020, a Cessna 208B (registration PK-SNR) operated by Smart Aviation was involved in an aviation accident near Sela Airstrip, Papua, ID. Investigators recorded the probable cause as: The aircraft failed to stop within the remaining runway length due to insufficient deceleration on a wet, sloped runway, compounded by inaccurate aeronautical information regarding the airstrip's characteristics. This summary draws on records from the Indonesian National Transportation Safety Committee (KNKT); 14 related events involving the same aircraft type or operator are linked below.

Sourcesthe Indonesian National Transportation Safety Committee (KNKT)Primary reportUpdated 1785107694Data APIEditorial standards

A cargo and passenger flight involving a Cessna 208B ended in a runway excursion at Sela Airstrip after the aircraft failed to decelerate sufficiently on a sloped, wet runway.

What happened

On 26 December 2020, a Cessna 208B, registration PK-SNR, was operating an unscheduled cargo and passenger flight from Dekai to Sela Airstrip in Papua, Indonesia. The flight, operated by PT. Smart Cakrawula Aviation, carried two pilots and ten passengers.

During the approach to Runway 21, the aircraft encountered a hill approximately 250 feet above the runway elevation. Upon touchdown, the aircraft was only 160 meters from the start of the runway. Although the pilot applied maximum braking and set the engine to the BETA range, the aircraft failed to decelerate as expected. With only 30 meters of runway remaining, the pilot engaged maximum reverse thrust. Despite these efforts, the aircraft continued forward, eventually impacting higher ground at the end of the airstrip. There were no injuries among the occupants, though the aircraft sustained substantial damage.

The investigation

The KNKT investigation examined the flight data, including GPS logs and the Cockpit Voice and Data Recorder. The investigation revealed that the pilots had received weather reports from local residents suggesting good conditions, but these reports lacked information regarding the runway surface. Upon inspection after the incident, the pilots noted the runway was slightly wet.

Investigators also identified significant discrepancies in aeronautical data. The airstrip reference point and runway length information varied between the official Aeronautical Information Publication (AIP), INDOAVIS, and the operator's own guidance. Furthermore, the runway designation used by the operator did not match the official AIP records.

Findings

  • The aircraft was equipped with STOL and payload extender systems, which impact landing performance.
  • The aircraft touched down 160 meters from the beginning of the runway.
  • Inaccurate aerodrome data regarding runway length, coordinates, and designation was present in official publications.
  • The runway surface was slightly wet, and the presence of moss or algae was a known hazard for the site.
  • The runway is located on a mountain slope, and the approach involved navigating terrain near the runway elevation.

Probable cause

The aircraft failed to stop within the remaining runway length due to insufficient deceleration on a wet, sloped runway, compounded by inaccurate aeronautical information regarding the airstrip's characteristics.