Jump to content

Petropavlovsk-Kamchatsky Air Flight 251 (2021)

From Alfawiki
Adapted from the English Wikipedia article Petropavlovsk-Kamchatsky Air Flight 251 (2021), available under CC BY-SA 4.0Updated 29 November 202522 sources
Kamchatka Air Enterprise
Company typeAirline
IndustryAviation
Headquarters
Petropavlovsk-Kamchatsky
,
Russia
Area served
Kamchatka Krai, Russia
ProductsPassenger and freight air transport


Template:Infobox aircraft occurrence

Petropavlovsk-Kamchatsky Air Flight 251 (PTK251) was a scheduled domestic flight within Russia, operating between Petropavlovsk-Kamchatsky and Palana, Russia#Palana, both located in Kamchatka Krai of the Russian Far East. On 6 July 2021, the flight's aircraft, an Antonov An-26, crashed during its final approach to Palana, resulting in the loss of all 28 individuals aboard.

Aircraft

The aircraft involved was an Antonov An-26B-100 model with registration number RA-26085 and manufacturer's serial number 12310, operated by Kamchatka Air Enterprise. Originally manufactured as an An-26B in 1982, it underwent conversion to civilian standards during an overhaul completed in October 2012.[1][2]

The An-26 series primarily consists of military transport planes; however, this particular airframe had been modified for civilian applications to carry passengers and freight. It is powered by two Ivchenko AI-24VT turboprop engines.

Prior to its current operator, this airplane served with PermTransAvia and Air Mali International, and was also leased for United Nations missions.[3] Since 2013, Petropavlovsk-Kamchatsky Air Enterprise had been operating this aircraft. Its typical schedule included approximately nine weekly flights, each lasting around two hours.[4]

Crew

The flight was operated by a team of six crew members, which included the captain, first officer, navigator, and flight engineer.[5] Notably, in 2012, another Antonov An-28 flying the identical route and flight number (Flight 251) also crashed during its landing approach at Palana Airport.[6]

Accident

Flight 251 was a scheduled domestic passenger service operating between Elizovo Airport, Petropavlovsk-Kamchatsky and Palana Airport, located in Palana, Russia. The aircraft departed Petropavlovsk-Kamchatsky at 12:56 local time (00:56 UTC) and was expected to arrive at Palana by 15:05 local (03:05 UTC). After successfully passing through the respective area control centers, control was handed over to the ATC of Tigilsky District at 14:09. At this point, the captain contacted Palana airport to inquire about current weather conditions.[7] Communication transcripts reveal that the Palana controller informed the crew that the cloud base over the airport was approximately 720 metres (2,400 ft).[8] According to airline policy, visual approaches from the sea side were prohibited when cloud ceilings fell below 750 metres (2,500 ft). Consequently, the controller advised approaching from the land side using available navigational aids.[8] The pilot dismissed this recommendation, citing the absence of a published approach procedure from land and insisted on continuing with a visual approach from the sea.[8] The controller reiterated that a sea-side approach was discouraged due to increasing fog around the airport, which partially obscured mountains situated between the Sea of Okhotsk and Palana.[8] The final communication with the aircraft occurred at 14:48 local time (02:48 UTC), when the crew reported maintaining an altitude of 800 m.[5][9]

While on final approach to Palana Airport, contact with the aircraft was lost approximately 10 km (6.2 mi) from the runway. ATC did not receive any indication of a go-around maneuver.[10] Weather conditions at that time were reported as cloudy.[11] The aircraft collided with a steep cliff rising to an elevation of 263 metres (863 ft).[7][12] At impact, the plane was flying at roughly 200 metres (660 ft), which was below the minimum safe altitude for this approach and off the designated flight path. The collision resulted in total destruction of the aircraft.[12] Only part of the tail section remained lodged on the cliff face; debris scattered downwards into the Sea of Okhotsk. A skid mark on the rock face marked where the crash occurred.[13]

Response

The crash location was identified on the same day following the deployment of a Mil Mi-8 helicopter and ground search teams by the Russian Ministry of Emergency Situations.[14][15] An emergency locator transmitter (ELT) emitted a faint signal, leading to the discovery of wreckage at 21:00 local time (09:00 UTC).[5] The debris was scattered, with a fuselage section found on the slope of Pyatibratka hill and another fragment located approximately 4 km (2.5 mi) offshore.[16] Tragically, all 28 individuals aboard perished.

By 7 July, rescue teams consisting of 51 personnel had retrieved 19 bodies.[17] The terrain's challenging geography complicated search and rescue efforts.[11] Additionally, high sea waves forced a temporary halt to maritime rescue operations overnight.[2] A mourning period lasting three days was officially declared in the affected region.[17] Condolences were extended by multiple nations, including the United States,[18] Greece,[19] Turkey,[20] Serbia,[21] and Pakistan.[22]

Investigation

In Russia, the responsibility for probing aviation accidents lies with the Interstate Aviation Committee. The Investigative Committee of Russia identified three potential factors that might have contributed to the crash: adverse weather conditions, mechanical malfunction, or pilot error. On 9 July, the aircraft's flight data recorder (FDR) was located. A representative stated that an initial inspection revealed "no significant damage," and the device was scheduled for data extraction in Moscow. The cockpit voice recorder was also recovered on the same day; however, it suffered severe damage, with only fragments of its casing found, rendering data retrieval impossible.

On 17 July, the Federal Air Transport Agency, known as Rosaviatsia, published its preliminary evaluation of the FDR. According to their findings, after reaching the Palana non-directional beacon (NDB) at an altitude of approximately 800 metres (2,600 ft), the aircraft initiated a turn away from the NDB to visually maneuver back for final approach to the airport. The air traffic controller informed the crew that they were on a heading of 340 degrees (north-northwest), differing from the west-northwest 289-degree bearing prescribed by the NDB approach procedure. Following communication with air traffic control, the crew reported descending to 600 metres (2,000 ft), but did not confirm reaching this altitude nor requested permission for further descent. The flight data showed the aircraft completed the base and final turns without any recorded deployment of landing gear or flaps. Upon exiting the final turn roughly 12 kilometres (7.5 miles) from the airport, the plane was aligned on a heading of 140 degrees (approximately southeast), directly toward the aerodrome. Approximately one minute before impact, air traffic control notified them they were positioned on a bearing of 320 degrees and about 9 kilometres (5.6 miles) from the airport. The collision occurred at terrain elevation near 260 metres (850 feet), situated on a coastal cliff topped with trees approximately 10 metres (33 feet) tall.

Among other recommendations, Rosaviatsia advised revisiting the circumstances surrounding the 2012 crash of RA-28715 during an attempted landing at Palana. This review aims to evaluate how effectively safety measures proposed following that earlier accident have been implemented.

Final Report

In 2025, the Interstate Aviation Committee (IAC) published the conclusive report on the accident. The findings indicated that the flight crew did not communicate regarding their altitude and neglected to track both their altitude and descent rate prior to the crash. The incident was determined to be a controlled flight into terrain, with recommendations addressing how to manage CFM failures and prevent terrain collisions.[9]

References

  1. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named ASN
  2. ↑ 2.0 2.1 Cite error: Invalid <ref> tag; no text was provided for refs named WSJ
  3. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named :0
  4. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named kommersant0706
  5. ↑ 5.0 5.1 5.2 Hradecky, Simon (17 July 2021). "Crash: Petropavlovsk-Kamchatsky AN26 near Palana on Jul 6th 2021, missing aircraft impacted edge of coast". The Aviation Herald. Retrieved 17 July 2021.
  6. ↑ Ferrara, Lee (12 September 2012). "Petropavlovsk-Kamchatsky Antonov An-28 Plane Crashes in Russia, 10 Killed". Airnation.net. Archived from the original on 22 December 2015. Retrieved 18 September 2012.
  7. ↑ 7.0 7.1 Kaminski-Morrow, David (7 July 2021). "No survivors after Kamchatka An-26 collided with steep cliff". Flight Global. Retrieved 7 July 2021.
  8. ↑ 8.0 8.1 8.2 8.3 Mashkin, Sergey (19 August 2021). "Самоуверенность пилота привела в склон горы" [Over-confidence of the pilot led to the side of the mountain]. Kommersant (in русский). Retrieved 8 May 2023.
  9. ↑ 9.0 9.1 "Окончательный отчет самолет Ан-26Б-100 RA-26085" (PDF). mak-iac.org. 2025. Retrieved 30 August 2025.
  10. ↑ "Авиакомпания: разбившийся на Камчатке Ан-26 не заходил на второй круг перед посадкой" [Airline: An-26 crashed in Kamchatka did not go around before landing] (in русский). Kommersant. 7 July 2021. Retrieved 7 July 2021.
  11. ↑ 11.0 11.1 "Plane with 28 people on board crashes in Russia's far east". France 24. 6 July 2021. Retrieved 6 July 2021.
  12. ↑ 12.0 12.1 "Катастрофа Ан-26Б-100 Камчатского АП в районе Паланы" [Accident of An-26B-100 Kamchatka AP near Palana]. airdisaster.ru (in русский). Retrieved 9 July 2021.
  13. ↑ Mashkin, Sergey (7 July 2021). "Пассажирский "Ан" разбился о скалу" [Passenger "An" crashed on a rock]. Kommersant (in русский). Retrieved 22 July 2021.
  14. ↑ ...
  15. ↑ ...
  16. ↑ ...
  17. ↑ 17.0 17.1 ...
  18. ↑ ...
  19. ↑ ...
  20. ↑ ...
  21. ↑ ...
  22. ↑ ...

External links

Template:Aviation accidents and incidents in 2021 Template:Aviation accidents and incidents in Russia in the 2020s