Mount Salak Sukhoi Superjet 100 crash
97004, the aircraft involved in the incident, seen at Naypyidaw International Airport two days before the crash flight in Indonesia. The plane is bound for Indonesia.
|
|
Incident summary | |
---|---|
Date | 9 May 2012 |
Summary | Controlled flight into terrain Human factor Impacted mountainside during demonstration flight Pilot error |
Site | Mount Salak, Indonesia Lua error in package.lua at line 80: module 'strict' not found. |
Passengers | 37 |
Crew | 8 |
Fatalities | 45 (all) |
Survivors | 0 |
Aircraft type | Sukhoi SSJ-100-95 |
Operator | Sukhoi |
Registration | 97004 |
Flight origin | Halim Perdanakusuma Airport, Jakarta, Indonesia |
Destination | Soekarno Hatta International Airport, Jakarta, Indonesia |
The Mount Salak Sukhoi Superjet 100 (SSJ-100) crash occurred on 9 May 2012 when an SSJ-100 aircraft crashed on a demonstration flight operating from Halim Perdanakusuma Airport, Jakarta, Indonesia.[1] On 10 May, the wreckage of the Sukhoi Superjet was spotted on a cliff in Mount Salak, a volcano in the province of West Java. Due to the widespread debris field where the aircraft hit the mountain, rescuers concluded that the aircraft directly impacted the rocky side of the mountain and that there was "no chance of survival".[2][3] On 12 May 2012, it was reported that the remains of several victims' bodies had been recovered and airlifted to Halim Airport and then taken to the National Police Hospital for identification.[4]
The final report, released 18 December 2012, indicated that the accident was caused by crew members ignoring terrain warnings that they had incorrectly attributed to a database problem. The crew had turned off the terrain warning system and were unaware that they were operating in close proximity to mountains. The crew, including the captain, were engaging in conversation with potential customers as the aircraft impacted the ground.[5]
Contents
Background
Aircraft
The aircraft involved in the accident was a Sukhoi SSJ-100-95, registration 97004,[6] msn 95004. The aircraft was manufactured in 2009 and had accumulated over 800 flight hours at the time of the accident.[7] The Superjet 100 is the first production airliner model produced in Russia since the dissolution of the USSR in 1991.[8]
Demonstration tour
The jet was flying as part of a "Welcome Asia!" demonstration tour when the crash happened. With a different jet, a demo flight had been flown successfully in Kazakhstan, but when the tour moved to Pakistan, potential buyers could see the aircraft only on the runway as no flight took place, reportedly due to a technical glitch. A leak in a 'nozzle in the engine' was found in this plane on the way to Myanmar, according to Alexander Tulyakov, vice-president of the United Aircraft Corporation, and it returned to Moscow. The jet involved in the accident was then flown in as a replacement to continue the tour.[9] It had been scheduled to visit Laos and Vietnam.[10] At the time of the crash, Sukhoi had 42 orders of the type from Indonesia, 170 in total, and was hoping to produce up to 1,000 aircraft.[11]
Mount Salak
<templatestyles src="Module:Hatnote/styles.css"></templatestyles>
In the decade between 2002 and 2012, there were seven aviation crashes in the area of Mount Salak. Three people were killed in a crash of a training aircraft not long before the SSJ-100 accident; 18 people were killed in a crash of an Indonesian Air Force military aircraft in 2008; five people were killed in a small crash in June 2004, two in April 2004, seven in October 2003, and one in October 2002.[12][13]
The Jakarta Post has dubbed Mount Salak "an airplane graveyard".[13] High turbulence and fast-changing weather conditions of the mountainous terrain are cited as contributing factors to multiple aviation crashes in the area.[13]
Crash
At 14:00 local time (07:00 UTC),[14] the SSJ-100 departed from Halim Perdanakusuma Airport for a local demonstration flight, and was due to return to the departure point.[7][15] This was the second demonstration flight the aircraft was operating that day.[16] There were six crew, two representatives from Sukhoi and 37 passengers on board.[7] Amongst the passengers were representatives from Aviastar Mandiri, Batavia Air, Pelita Air Service and Sriwijaya Air.[17] At 14:21 (07:21 UTC), the crew requested permission to descend from 10,000 feet (3,000 m) to 6,000 feet (1,800 m) for reasons which were unclear, and this was granted. This was the last contact that Air Traffic Control had with the aircraft,[7] which was then about 75 nautical miles (139 km) south of Jakarta,[17] in the vicinity of 7,254-foot (2,211 m) high Mount Salak, a mountain higher than the requested flight level.[7]
Simon Hradecky, of The Aviation Herald, later reported:
"Indonesia's Air Traffic Control, Jakarta Branch, reported that communication between ATC and aircraft was done in English, there was no language problem hampering communication. The aircraft had been in the area of Bogor, approximate coordinates Lua error in package.lua at line 80: module 'strict' not found., about 13 nautical miles (24 km) northeast of the peak of Mount Salak and 7 nautical miles (13 km) clear of mountainous terrain in safe flat area, when the crew requested to descend and to perform a right orbit. As there was no reason to decline such a clearance the flight was cleared down and for the right orbit. This was the last transmission from the aircraft, the aircraft could not be reached afterwards. The plane having finished right orbit flew a course about 210°. It is unclear how the aircraft got into the area of Mount Salak and crashed afterwards, ATC services hope the black boxes will explain how the aircraft got there. All data including flight plan, radar data and ATC recordings as well as transcripts of interviews with the air traffic controller have been handed to Indonesia's NTSC."[7]
In December 2012, the crash investigation determined that the plane's terrain warning system had been functioning correctly and had warned the pilots about the collision course with the mountain. The pilots, however, turned the system off, suspecting it to have malfunctioned. Due to being distracted by conversation on the flight deck, unrelated to flying the plane, they failed to notice that the plane was in danger.[18]
A ground and air search for the aircraft was initiated, but was called off as night fell. On 10 May at 09:00 (02:00 UTC), the wreckage of the Sukhoi Superjet was found on Mount Salak.[2] It is only known that the aircraft had been flying on a clockwise flightpath around the mountain, towards Jakarta, before the crash.[7][19] Preliminary reports indicated that the aircraft had hit the edge of a cliff at an elevation of 6,270 feet (1,910 m), slid down a slope and came to rest at an elevation of 5,200 feet (1,600 m). Despite appearing relatively intact from the air, the aircraft sustained substantial damage, and there was no sign of survivors. The site of the accident was not accessible by air and no rescuers had reached the site by nightfall on 10 May. Multiple groups of rescue personnel attempted to reach the wreckage on foot.[7]
Victims
Nationality | Passengers | Crew | Total |
---|---|---|---|
Indonesia | 35 | 0 | 35 |
Russia | 0 | 8 | 8[20] |
USA | 1 | 0 | 1[21] |
France | 1 | 0 | 1[22] |
Total | 37 | 8 | 45[20] |
Most of the passengers were journalists and prospective clients.[1][23] The 45 people on board included 14 people from the Indonesian airline Sky Aviation, Captain Aan Husdiana (Director of Operations for Kartika Airlines) and five reporters, Dody Aviantara (journalist) and Didik Nur Yusuf (photographer) from Angkasa aviation magazine, Ismiati Soenarto and Aditya Sukardi of Trans TV and Femi Adi of the American Bloomberg News.[20] An accomplished and experienced pilot, Peter Adler held a US passport, acting as a consultant and a passenger on the flight;[21] according to Vladimir Prisyazhnyuk, the head of Sukhoi Civil Aircraft, two Italians and one French citizen of Vietnamese descent were also on board.[22] The captain of the jet was Alexander Yablontsev, a former Russian test pilot;[24] he had been the pilot for the first test flight of Superjet 100 in May 2008.[25] The first officer was Alexander Kotchetkov.[26]
Investigation
The day after the crash Russian Prime Minister Dmitry Medvedev set up a commission, to investigate the cause of the accident, headed by the Industry and Trade Ministry's Yury Slyusar.[27] According to the National Transportation Safety Committee (NTSC), the Indonesian agency for the investigation of civil aircraft accidents, analysis of the crash would take up to 12 months.[28] On 15 May 2012, it was reported in the local media that the Indonesian government had turned down Russia's request to send back the flight data recorder, stating that Indonesian investigators would determine the cause of the crash, while Russian experts would provide support only.[29] The cockpit voice recorder was found on 15 May 2012 at a distance of 200 m from the tail section.[9] The flight data recorder was found on 31 May 2012[30] at a distance of 200 m from the tail section.[31]
The Indonesian NTSC had released their Preliminary Report, which listed factual findings but did not attempt to determine the cause of the accident.[32]
According to sources within the investigating committee, the aircraft was in full working order and the incident was ascribed to human error.[33][34]
The final report was released 18 December 2012[35] and indicated that the accident was caused by crew members ignoring terrain warnings that they had incorrectly attributed to a database problem. The crew had turned off the terrain warning system and were unaware that they were operating in close proximity to mountains. The crew, including the captain, were engaging in conversation with potential customers as the aircraft impacted the ground.[5]
Aftermath
Sky Aviation, an Indonesian air carrier, delayed the delivery of 12 Superjet 100s following the accident.[36] Arifin Seman, the commissioner of Kartika Airlines, another domestic Indonesian carrier, went on record to say that the delivery of 30 Superjet 100s, which his company had ordered, would likely be delayed following the crash.[37] Several days later, however, the same source published Sky Aviation's statement in which they declared that they were not going to cancel the contract. Moreover, Sky Aviation's general manager for promotion, Sutito Zainuddin, added that "the additional 100-seat planes would be needed to connect major cities in Indonesia, particularly Jakarta".[38] Mexico's Interjet Board chairman Miguel Alemаn Velasco said the crash had no influence on the company's desire to purchase additional Superjets.[39]
The Russian airline Aeroflot and Armenian Armavia, the two operators of the SSJ-100 at the time of the crash, had not suspended operations of the type.[40] Armavia said that it would continue negotiations over the purchase of another Superjet 100 for its fleet.[41]
See Also
References
- ↑ 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 5.0 5.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Aircraft registry Sukhoi Superjet 100. RussianPlanes.net (Russian)
- ↑ 7.0 7.1 7.2 7.3 7.4 7.5 7.6 7.7 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 13.0 13.1 13.2 Mt. Salak: An airplane graveyard Archived 12 May 2012 at the Wayback Machine thejakartapost.com
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 17.0 17.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 20.0 20.1 20.2 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 21.0 21.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 22.0 22.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.[dead link]
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ «Армавиа» продолжит переговоры о покупке второго самолета SuperJet-100
Further reading
- Soejatman, Gerry. "SSJ100 Accident: Reflections After a Week." The Jakarta Globe. 22 May 2012.
External links
Wikimedia Commons has media related to RA-97004 (aircraft). |
Wikinews has related news: Russian passenger jet crashes on Indonesian demonstration flight |
Wikinews has related news: Indonesians retrieve missing recorder from crashed Russian jet |
- National Transportation Safety Committee
- Final report (Archive), 18 December 2012
- Preliminary report (Archive)
- "Media Release KNKT.12.05.09.04". (Archive) 18 December 2012.
- "Media Release KNKT.12.05.09.04". (Archive) 18 December 2012. (Indonesian)
- Immediate Recommendation Aircraft Accident Investigation of a Sukhoi RRJ-95B aircraft Registered 97004 operated by Sukhoi Civil Aircraft Company at Mount Salak, West Java on 9 May 2012 (Archive)
- SuperJet International
- "РАССЛЕДОВАНИЕ КРУШЕНИЯ SUKHOI SUPERJET-100." (Archive) Ministry of Industry and Trade. (Russian)
- National Search and Rescue Agency (Indonesian)
- Sukhoi: "JSC United Aircraft Corporation, JSC Sukhoi Company and JSC Sukhoi Civil Aircraft express their deepest condolences to relatives and dear ones of those people who were on board the Sukhoi Superjet 100 №97004." (Archive) – Includes passenger list
- First footage of Sukhoi Superjet 100 crash site on YouTube
- "Sukhoi SSJ-100 aircraft crash in Indonesia" (Russian)
- "Superjet 100 Captain's Mistake Revealed"
- Articles with dead external links from May 2016
- EngvarB from July 2014
- Use dmy dates from July 2014
- Pages with broken file links
- Commons category link is locally defined
- Articles with Indonesian-language external links
- Articles with Russian-language external links
- Aviation accidents and incidents in 2012
- Aviation accidents and incidents in Indonesia
- Airliner accidents and incidents involving controlled flight into terrain
- 2012 in Indonesia
- Sukhoi