Trigana Air Service Flight 267

Trigana Air Service Flight 267
PK-YRN, the aircraft involved, in 2008
Accident
Date 16 August 2015 (2015-08-16)
Summary Controlled flight into terrain
Site Mount Tangok, Oksibil, Papua, Indonesia
04°49′28″S 140°29′53″E / 4.82444°S 140.49806°E / -4.82444; 140.49806Coordinates: 04°49′28″S 140°29′53″E / 4.82444°S 140.49806°E / -4.82444; 140.49806
Aircraft
Aircraft type ATR 42-300
Operator Trigana Air Service
IATA flight No. IL267
ICAO flight No. TGN267
Call sign TRIGANA 267
Registration PK-YRN
Flight origin Sentani Airport, Jayapura, Indonesia
Destination Oksibil Airport, Oksibil, Indonesia
Occupants 54
Passengers 49
Crew 5
Fatalities 54 (all)
Survivors 0

Trigana Air Service Flight 267 was a scheduled passenger flight from Sentani to Oksibil in the eastern Indonesian province of Papua. On 16 August 2015, the ATR 42 turboprop operating the service crashed on approach in the Bintang highlands region of Oksibil, killing all 49 passengers and 5 crew members.[1][2][3][4][5][6]

With 54 deaths, it is the deadliest accident involving the ATR 42, and the airline's deadliest accident since its establishment in 1991.[7]

The Indonesian National Transportation Safety Committee published its final report into the accident in December 2017.[8] Deviation from visual approach guidance and visual flight rules without regard to weather and terrain, and the likely deactivation of the EGPWS system contributed directly to the crash, compounded by shortcomings in Trigana Air Service's safety culture.[9]

Flight

Map showing the crash site in Papua

The Trigana Air Service flight took off from Sentani Airport in Jayapura at 14:22 WIT (UTC+9, 05:22 UTC) and was scheduled to land in Oksibil at about 15:16. Oksibil is a remote town near the country's border with Papua New Guinea. Oksibil Airport did not have an instrument landing system to guide aircraft in to land because it is located close to a mountain.[10]

Contact was lost with the aircraft at about 14:55.[11] There was no indication that a distress call was made by the crew.[12][13] The crew had been expected to make contact with ground staff at Oksibil Airport at around 15:00; attempts by those at the airport to contact the aircraft were unsuccessful.[14][15] At the time of the accident, the aircraft was on the final section of its scheduled route.[16]

Weather conditions

Conflicting statements regarding the weather conditions were released. Stormy weather was initially cited as a possible cause of the crash,[17][18][19] however it was later confirmed that the weather was good.[20] Minister of Transportation Ignasius Jonan stated that bad weather was not the cause of the crash. Data from the local Indonesian Agency for Meteorology, Climatology and Geophysics office showed that the weather at the time of the crash was sunny. The crew of another aircraft landing prior to the crash also reported conditions at the time as "good".[21]

Several pilots stated that flying was difficult in the region. A pilot, Captain Andhy Gunawan, stated that the terrain in Papua was very dangerous and warned that the weather conditions in the area are also dangerous, as visibility could be limited.[22] The Ministry of Transportation acknowledged that Indonesia's air navigation system equipment was very outdated and dated back to the 1950s, especially in remote areas such as Papua. Most airports in Papua did not have modern navigation aids at the time. Without this equipment, the airports and flight crew must conduct operations under instrument flight rules and rely on visual flight rules. This however could turn out to be dangerous as Papua's weather was "unforgiving and unpredictable" with most airports not receiving reports about weather condition in the area.[23]

At 15:30, Indonesia's National Search and Rescue Agency (BASARNAS) deployed a search aircraft to find the missing ATR 42. The search was suspended due to foggy weather and was resumed, with several additional search aircraft augmented by a search team on foot, on 17 August.[24][25][26] Local residents contacted police and reported that they saw the aircraft crash into the Tangok Mountain in the Okbape district of Pegunungan Bintang Regency.[15] Airborne searchers spotted the wreckage about 12 km (7 miles) from Oksibil. The Indonesia Transportation Ministry confirmed that the wreckage was located at an elevation of 8,300 feet (2,530 m). All 54 passengers and crew were found to have died.[5] The terrain itself had never been previously explored by humans, according to BASARNAS officials.[27][28][29]

Recovery

Wreckage at the crash site of flight 267

BASARNAS sent 250 personnel to Oksibil in response to the crash. Due to the thin air at this high altitude rescuers were unable to use air transport to recover victims or wreckage, necessitating an overland recovery.[30] The terrain itself is described as "very steep". It took around three days to reach the wreckage on foot, or six hours by vehicle. Indonesian National Police sent three Disaster Victim Identification (DVI) teams into the area to identify the victims of the crash. The bodies will be transported to a military hospital in Jayapura. However, bad weather and low visibility hamper the search and rescue effort. Weather systems around the wreckage were "unpredictable",[31] according to BASARNAS. The identification of the victims will use DNA, tooth samples and forensic DNA analysis from surviving family members. The families have sent post-mortem and ante-mortem data to the police.[32]

By 18 August 2015 all of the dead had been found, but bad weather prevented the recovery of victims' bodies. Some victims' bodies were intact and exhibited burn injuries, others were mutilated and difficult to be identified.[33] Photos taken from the crash site reveal that the aircraft had been heavily fragmented into smaller pieces by the force of the impact with no chance of survival.[34] By nightfall on 19 August seventeen bodies had been carried out from the crash site. Initial reports that both flight recorders had been found in good condition were later contradicted, as authorities revealed on 19 August that the flight data recorder (FDR) was still missing.[35] The Flight Data Recorder was eventually found on 20 August and shown to media.[36]

Aircraft and operator

The ATR 42 aircraft was registered PK-YRN, it was manufactured in 1988 and originally operated in the United States before being transferred to Trigana Air in 2005.[37] The airline operated five more of the same aircraft type and three aircraft of the larger ATR 72 variant at the time of the crash.[38] Aircraft operated by Trigana Air have been involved in fourteen serious accidents between 1992 and 2016, eleven of which resulted in hull loss.[39]

Passengers and crew

The aircraft was carrying 49 passengers and 5 crew members. The passenger manifest released by Trigana Air indicated all on board were Indonesian. There were 44 adults, 3 children and 2 infants among the passengers.[4] There were two pilots; the captain had joined Trigana in 2000, he had 25,200 hours of total flying experience and 7,300 hours' experience flying ATR 42s. The first officer had joined Trigana in 2008 and had a total of 3,800 hours flying experience, of which 2,600 were in flying ATR 42s. Both of them were described by Trigana as very experienced pilots.[40]

Among the passengers were four postal servicemen heading to Oksibil to distribute the Indonesia Sejahtera card, a programme for the poor that President Joko Widodo developed and promoted while campaigning for the 2014 Indonesia Presidential Election.[41] They were reportedly carrying around 6.5 billion rupiah ($US470,000).[42] Three local government officials and two members of the Regional Representatives Council were also on board to attend celebrations in Oksibil for the 70th anniversary of Indonesia's independence.[43][44]

Investigation

The Indonesian National Transportation Safety Committee (NTSC or KNKT) opened an investigation to the crash. In line with international regulations, as the aircraft was built in France, its Bureau d'Enquêtes et d'Analyses pour la Sécurité de l'Aviation Civile (BEA) participated, sending three investigators. Aircraft manufacturer ATR also assisted and sent four technical advisers.[45][46]

The flight manifest released by Trigana was found to be wrong, being for another Trigana flight. As a result, the Chairman of Sentani Airport was fired by the Transportation Ministry. Sixteen workers were also investigated by the police because of their involvement.[47] Two of Trigana's staff remained in custody. Ignasius Jonan, Indonesian Minister of Transportation, criticized the airport staff saying the situation was a "big mess" and needed to be cleaned up.[48]

Investigators rebuilt the predicted flight path of Flight 267, using Google Earth and data from the CVR and its spectrum analysis. They noted that the Flight Data Recorder was unusable. The analysis of the CVR revealed that at 14:55 local time, the flight crew of Flight 267 stated their intention to make a direct left base. Immediately after that, Flight 267 deviated from its predicted flight path.[8]

Flight 267 deviated to the right. The area on the right side of Flight 267 was surrounded by mountainous terrain. Some of the terrain was as high as 8,000 ft. In addition, Papua's unpredictable weather would endanger the flight easily. Pilots have reported that fogs sometimes "came out of nowhere", which could limit the pilot's visibility. Though good condition was reported in the area, there were also localized fogs in the mountains. According to the NTSC, based on the CVR analysis, Flight 267 entered clouds and fogs. The altitude of Flight 267 was not sufficient enough to pass the mountains. The mountains were covered by fog at the time. It is plausible that their proximity to terrain was not noticed by them.[8]

The investigation team decided to investigate the crew's motivation to deviate from the flight's predicted flight path. They checked on the crew's previous flight from Sentani to Oksibil. It was revealed that the crew did exactly the same thing: making a direct left base by deviating from its predicted flight path. Investigators then stated that the crew might have been overconfident with their flying skill. Similar to TransAsia Airways Flight 222, due to their previous success on landing an aircraft prior to the accident (by flying below the minimum safe altitude), the crew believed that they were able to do the same thing in the future without considering the consequences. The crew had accrued thousands of flight hours and were familiar with the airport. Because of their familiarity with the terrain, they tend to be confident with their skill. Thus, their situational awareness were reduced significantly.[8]

However, these were all preventable had the EGPWS sounded and warned the crew of their proximity to terrain. The NTSC noted that the EGPWS didn't sound at all during the flight's final moment, even though Flight 267 was going to hit the mountain. Investigators revealed that the circuit breaker which was responsible for the activation of the EGPWS had been pulled off by Flight 267's crew. Similar to the Mount Salak Sukhoi Superjet tragedy, the crew had shut down the EGPWS warning on purpose. Trigana Air Service's management personnel stated that some pilots had stated that the warnings sometimes sounded during inappropriate condition. This led some pilots to think that the EGPWS had malfunctioned. Thus, the EGPWS was de-activated by pulling the circuit breaker. The management had identified some pilots including the accident pilot of the pilot with behaviour of pulling the EGPWS's circuit breaker.[8]

As per the final report, the investigation concludes that the EGPWS power supply circuit breaker was pulled during the accident flight and the two previous flights, explaining the absence of altitude call out during the two previous approaches and warning prior to the impact. Further investigation revealed that Trigana Air Service had published an approach chart with wrong information to the pilot. The approach chart stated that the minimum safe altitude was at 8,000 ft. Flight 267 impacted the mountain at 8,300 ft. The NTSC considered the approach chart as wrong, ineffective and hard to understand. Aircraft maintenance was also badly performed by the airline.[8]

The final report concluded that the accident was a controlled flight into terrain that was caused by the crews' decision to deviate from its projected flight path. The absence of EGPWS warnings aggravated the condition.[8]

Aftermath

Mourning

The aircraft crashed one day before Indonesia celebrated its 70th anniversary; Indonesian President Joko Widodo urged all Indonesians to pray, and held a minute of silence in order to remember the victims. Crisis centres were set up in Sentani and Jakarta. BASARNAS also set up three crisis centres in Jayapura. Minister of Transportation Ignasius Jonan commented that Trigana Air Service "must treat the affected families as well as possible". Shortly after the crash, flowers and condolence banners were displayed in front of Trigana Air Service's head office. The condolences came from various airlines, including Sriwijaya Air, Aviastar and head staff of INACA.[49][50]

Trigana Air Service stated it would pay compensation as it claimed responsibility for the crash, with a total of Rp.1,25 billion in compensation for each person killed in the crash. Jasa Raharja was also to also pay compensation of Rp. 100 million for each person, bringing the total to Rp. 1,35 billion.[51]

Infrastructure

Indonesia's People's Representative Council urged the government to upgrade the air navigation system at every airport in Indonesia.[52] The Indonesian government stated that it would work with AirNav Indonesia to upgrade the infrastructure in Papua.[23] There were twelve small airports slated for upgrade by the government. Among them were Sumenep Airport, Labuan Bajo Airport and Oksibil Airport. The first phase is the upgrade of the information system transferring data from Aeronautical Flight Information Services (AFIS) to Area Aerodrome Control (ADC) towers. Updated weather reports would also be issued by the local weather station more frequently. The safety procedures upgrade process was to take around six months, and the ADC towers upgrade about a year. Some runways at the airports were also to be upgraded.[53]

Andrew Herdman, head of the Association of Asia Pacific Airlines said:

More resources are needed but of course governments face many demands on their resources. Further investment is needed in infrastructure. Many of the airports in Indonesia are dealing with congestion well beyond their design capacity. Some of the smaller airports, and this most recent tragedy involved short haul service between two remote airports in inhospitable terrain in Papua -- airports in that terrain need upgrading of navigation aids and other operational enhancements.[54]

Regulatory

The crash brought the spotlight back on Indonesian aviation safety. Arnold Barnet, a statistician focusing on aviation safety at the Massachusetts Institute of Technology, told the New York Times in December 2014 that the death rate in Indonesian airline crashes over the previous ten years was one in every million passenger-boardings, compared to one death for every 25 million passengers for airlines in the United States. According to CNN, International Air Transport Association (IATA) CEO Tony Tyler said in March 2015 that Indonesia had seen at least one major crash resulting in the loss of an aircraft every year since 2010; and that Indonesia was rated "below the global average" by the Universal Safety Oversight Audit Program (USOAP) of the International Civil Aviation Organization (ICAO).[54] Aviation expert Mary Schiavo opined that Trigana's prior crashes suggest that better training of its pilots was needed, as controlled flight into terrain was a factor in most of the airline's fatal aircraft crashes.[54]

See also

References

  1. ↑ "Plane with 54 on board crashes in remote Indonesian region". Reuters. Retrieved 16 August 2015.
  2. ↑ "Missing Plane: Indonesian Villagers Find Wreckage". Sky News. Retrieved 16 August 2015.
  3. ↑ "Wreckage believed to be of missing Indonesian plane spotted, rescuers race to crash site". Daily Sabah. Turkuvaz Media Group. 16 August 2015. Retrieved 16 August 2015.
  4. 1 2 "Ada Dua Bayi Dalam Pesawat Trigana yang Hilang Kontak" (in Indonesian). MSN. Retrieved 17 August 2015.
  5. 1 2 Armenia, Resty (17 August 2015). "Maskapai Trigana Air Pastikan Bangkai Pesawat Ditemukan". CNN Indonesia. Retrieved 17 August 2015.
  6. ↑ "Villagers find wreckage of Indonesian plane in Papua". Al Jazeera English Online. 16 August 2015. Retrieved 17 August 2015.
  7. ↑ Batubara, Herianto (17 August 2015). "Pakai Jet Kecil, Menhub Jonan Bertolak ke Papua Pantau Evakuasi Trigana Air". DetikCom. Retrieved 17 August 2015.
  8. 1 2 3 4 5 6 7 "PT, Trigana Air Service ATR 42-300; PK-YRN Tanggo Mountain, Oksibili, Papua Republic of Indonesia 15 August 2015" (PDF). Komite Nasional Keselamatan Transportasi. 29 December 2017. Retrieved 30 December 2017.
  9. ↑ Greg Waldron (2 Jan 2018). "Complacency, disconnected EGPWS led to Trigana ATR crash". Flightglobal.
  10. ↑ "Minimnya Infrastruktur Bandara Diduga Penyebab Trigana Air Jatuh". Okezone.com. Retrieved 19 August 2015.
  11. ↑ "10 Menit Penuh Misteri Saat Trigana Air Hilang Meninggalkan Ketinggian". DetikCom. Retrieved 16 August 2015.
  12. ↑ "Indonesian plane goes missing with 54 people on board". CNN. Retrieved 16 August 2015.
  13. ↑ "Ini Dugaan Sementara Penyebab Trigana Air Hilang Kontak" (in Indonesian). JPNN. Retrieved 17 August 2015.
  14. ↑ "Another Indonesian airliner goes missing". NYPost. Retrieved 18 August 2015.
  15. 1 2 Hradecky, Simon. "Crash: Trigana AT42 enroute on Aug 16th 2015, aircraft collided with terrain". avherald.com. Retrieved 17 August 2015.
  16. ↑ "Pesawat Trigana Air Hilang Kontak 10 Menit Sebelum Mendarat". CNNIndonesia. Retrieved 18 August 2015.
  17. ↑ "Kemhub: Info Masyarakat Pesawat Tabrak Gunung, Ditemukan di Okbapeh". detik.com. Retrieved 16 August 2015.
  18. ↑ "Kronologi Hilangnya Pesawat Trigana Air". MetroTvNews.com. Retrieved 16 August 2015.
  19. ↑ Authorities: Villagers say they've found missing plane. CNN.com. Retrieved 16 August 2015.
  20. ↑ "Faktor Cuaca Terkait Hilangnya Trigana Air Belum Akurat". Okezone. Retrieved 17 August 2015.
  21. ↑ "Menhub Tegaskan Trigana Air Jatuh Bukan karena Faktor Cuaca". Okezone. Retrieved 19 August 2015.
  22. ↑ "Medan 'Ajaib' di Papua yang Kerap Bikin Pilot Terperangah". Detiknews.com. Retrieved 18 August 2015.
  23. 1 2 "Perangkat Navigasi Bandara di Indonesia Berusia "Senja"" (in Indonesian). Liputan6. Retrieved 19 August 2015.
  24. ↑ "Titik Jatuh Pesawat Trigana Diperkirakan 2 Hari Jalan Kaki". Republika.co.id. Retrieved 17 August 2015.
  25. ↑ "Pemkab: Lokasi Pesawat Trigana Jatuh Bisa Ditembus Jalur Darat". Liputan6.com. Retrieved 17 August 2015.
  26. ↑ "Menhub: Ada 7-8 Pesawat Dikerahkan Cari Trigana Air". Detik.com. Retrieved 17 August 2015.
  27. ↑ "Indonesian plane debris seen; carried 54 people, gov't cash". AP. Retrieved 17 August 2015.
  28. ↑ "Basarnas: Posisi Pesawat Trigana Sudah Ditemukan!". Okezone. Retrieved 17 August 2015.
  29. ↑ "Diduga Puing Trigana Air Terlihat di Sekitar Air Terjun Oksop". Okezone. Retrieved 17 August 2015.
  30. ↑ "Cuaca Ekstrem, Evakuasi Trigana Air Dilanjutkan Jalur Darat". Okezone.com. Retrieved 18 August 2015.
  31. ↑ "Indonesian airliner that crashed with 54 aboard spotted". USA Today. Retrieved 18 August 2015.
  32. ↑ "Trigana Air Jatuh, DVI Polri Kerahkan Tiga Dokter ke Papua". Okezone.com. Retrieved 18 August 2015.
  33. ↑ "Jenazah seluruh korban Trigana Air sudah ditemukan". Merdeka.com. Retrieved 18 August 2015.
  34. ↑ "Pesawat Trigana Hancur". Sindonews. Retrieved 18 August 2015.
  35. ↑ "Search for missing Trigana plane black box". skynews.com.au. Sky News. 20 August 2015. Retrieved 20 August 2015.
  36. ↑ "Kotak FDR pesawat Trigana ditemukan". BBC Indonesia.
  37. ↑ "Aircraft accident ATR 42-300 PK-YRN between Jayapura and Oksibil". aviation-safety.net. Flight Safety Foundation. 16 August 2015. Retrieved 16 August 2015.
  38. ↑ "Trigana Air Service Fleet Details and History". planespotters.net.
  39. ↑ "Trigana Air accidents and incidents". aviation-safety.net. Flight Safety Foundation. Retrieved 30 December 2017.
  40. ↑ "TRIGANA AIR JATUH: Janji Terakhir Kopilot kepada Anaknya". Tempo. Retrieved 20 August 2015.
  41. ↑ "Empat Pegawai Pos Penumpang Trigana Hendak Bagikan Dana PSKS". Okezone.com. Retrieved 17 August 2015.
  42. ↑ "Indonesian plane 'was carrying nearly $500,000 in cash'". Al Jazeera English Online. 17 August 2015. Retrieved 17 August 2015.
  43. ↑ "Indonesia confirms no survivors as Trigana plane 'totally destroyed'". CBC. Retrieved 19 August 2015.
  44. ↑ "Indonesian search and rescue team in gruelling Trigana Air crash recovery effort". ABC.net.au. Retrieved 19 August 2015.
  45. ↑ "Update 2: ATR statement on Trigana Air Service flight TGN267" (Press release). ATR Aircraft. Retrieved 22 August 2015.
  46. ↑ "Accident in Indonesia to the ATR 42-300, registered PK-YRN, on Sunday 16 August 2015". BEA. Archived from the original on 23 August 2015. Retrieved 22 August 2015. ()
  47. ↑ "16 Saksi Diperiksa Terkait Pemalsuan Manifest Trigana Air yang Jatuh di Papua". Detik.com. Retrieved 31 August 2015.
  48. ↑ "Dampak Insiden Trigana Air, Kepala Bandara Sentani Dicopot". Detik.com. Retrieved 31 August 2015.
  49. ↑ "Jonan Minta Keluarga Penumpang Trigana Air Dilayani Dengan Baik". Tribunnews. Retrieved 18 August 2015.
  50. ↑ "Karangan bunga ucapan bela sungkawa penuhi kantor Trigana Air". Merdeka.com. Retrieved 18 August 2015.
  51. ↑ "EVAKUASI TRIGANA AIR: Setiap Penumpang Dapat Santunan Rp1,3 Miliar". BISNIS.com. Retrieved 20 August 2015.
  52. ↑ "Trigana Jatuh, DPR Desak Pemerintah Perbaiki Navigasi Bandara". Liputan6. Retrieved 19 August 2015.
  53. ↑ "Pasca Trigana Jatuh, Kemenhub akan Tingkatkan Kualitas 12 Bandara Perintis" (in Indonesian). detik.com. Retrieved 27 August 2015.
  54. 1 2 3 "Trigana plane crash: How safe are Indonesian airlines?". CNN. Retrieved 18 August 2015.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.