Jump to content

2009 Aviastar British Aerospace 146 crash

Coordinates: 04°02′18″S 138°56′47″E / 4.03833°S 138.94639°E / -4.03833; 138.94639
From Wikipedia, the free encyclopedia

2009 Aviastar British Aerospace 146 crash
Wreckage of the aircraft at the crash site
Accident
Date9 April 2009
SummaryPilot error, CRM failure
SitePikei Hill, Tengah Mountain, Wamena, Indonesia
04°02′18″S 138°56′47″E / 4.03833°S 138.94639°E / -4.03833; 138.94639
Aircraft
Aircraft typeBritish Aerospace 146-300
OperatorAviastar
RegistrationPK-BRD
Flight originSentani Airport, Jayapura, Indonesia
DestinationWamena Airport, Wamena, Indonesia
Occupants6
Passengers0
Crew6
Fatalities6
Survivors0

The 2009 Aviastar British Aerospace 146 crash occurred on April 9, 2009, when a British Aerospace 146 (BAe 146) crashed into Pikei Hill during a ferry flight from Sentani Airport to Wamena Airport, both in Indonesia's Papua province. All 6 crew members were killed. The aircraft was carrying voting paper to Wamena as well as several other goods, as a parliamentary election was held in the month. The wreckage was found in Pikei Hill, Tengah Mountain, Tangma, Yahukimo District.[1]

The accident was the first fatal crash for Aviastar and was the second airliner crash in Indonesia within a week, after an Indonesian Air Force Fokker 27 crashed into a hangar at Bandung on 6 April, killing all 24 people on board.

A final report by the National Transportation Safety Committee (NTSC) concluded that the crash was due to Controlled Flight Into Terrain (CFIT) resulting from pilot error. The Captain ignored the ground proximity warning after the First Officer had warned him many times as he became anxious about how the Captain was handling the aircraft.[2]

Accident

[edit]

The BAe 146-300, registered PK-BRD, was being operated by Aviastar on a ferry flight from Sentani Airport, Jayapura to Wamena Airport, Wamena. The crew consisted of two pilots, Captain Sigit Triwahyono, was the pilot in charge, along with first officer Lukman Yusuf. Also on board were two flight attendants, a flight engineer, and a load master.[1][2]: 2 

The flight was being operated under Instrument Flight Rules (IFR) from Sentani, and a visual descent, approach, and landing at Wamena, because there was no published instrument approach procedure at Wamena. There was low cloud on the final approach track to Runway 15 at Wamena. The aircraft was observed conducting a low altitude go-around over the runway: it then climbed to a low height along the extended centre-line to the south east, before making a right turn onto the downwind leg of the circuit. As it began its second approach into Wamena Airport, it hit Pikei Hill in Tengah Mountain at 07:43 local time (10:43 UTC). All on board were killed instantly.[1][2]: 2 

Aircraft

[edit]
The aircraft involved in the accident while still in service with British European

The aircraft involved in the accident, manufactured in 1990 and registered as PK-BRD with serial number E3189, was a BAe 146 Series 300. Originally built as a passenger aircraft, Aviastar modified the aircraft into a combined passenger and cargo configuration in September 2008. At the time of the accident, the aircraft had accumulated over 22,000 flying hours.[2]: 5 

The aircraft was in the 42-passenger and cargo configuration. However, the weight chart used for the accident flight was for the aircraft in a 110-passenger configuration. That was therefore the incorrect chart.[2]: 6 

Passengers and crew

[edit]

Because the aircraft was conducting a ferry flight there were no passengers; on board were six crew members which all were Indonesian. The Captain was 56-year-old Sigit Triwahyono, who had a total flying experience of more than 8,300 hours, of which 1000 were on the BAe146. The First Officer was 49-year-old Lukman Yusuf, with a total flying experience of over 12,400 hours, 200 on the BAe146.[3][2]: 4–5 

Investigation

[edit]

The investigation was conducted by the National Transportation Safety Committee. At the time of the accident, the weather in Wamena was calm, with slight haze and broken clouds surrounding the area. Visibility was 8 km. The weather was not a factor in the crash. Investigators retrieved both the Flight Data Recorder and Cockpit Voice Recorder. Both had good quality data. Based on the analysis of the flight recorders, investigators then reconstructed the chronological order as follows:[2]: 12–14,19–20 

At its first attempt to land, the runway in Wamena was obscured by low clouds. Knowing that they couldn't fly the aircraft to the established flight path for an approach, the crew abandoned the approach and started a go around to the right at a low height, approx 46 m (150 ft). While on the right circuit down-wind leg, the enhanced ground proximity warning system (EGPWS) warning sounded, eight of them were "Don't sink", two "Too low terrain", two "Bank Angle" and one "Terrain Terrain" voice aural alerts. The flight crew did not respond to any of those alerts. First Officer Lukman became really concerned with Captain Sigit's handling of the aircraft. He later said "be careful, Sir" to Captain Sigit.[2]: 12–14,19–20 

The aircraft then increased its bank angle to the right. First Officer Lukman became really anxious, saying "Sir Sir Sir open Sir left left". Shortly afterwards Captain Sigit banked the aircraft to the left. The "Don't sink" alert sounded for the second time. The bank angle to the left became extreme, exceeding 40°. The aircraft also entered a 10-degree nose down pitch attitude. First Officer Lukman then warned Captain Sigit "don't sink". In repeating the words "don't sink", First Officer Lukman was alerting Captain Sigit to comply with the EGPWS voice aural alert "Don't sink, don't sink". Captain Sigit immediately responded "ya, ya".[2]: 12–14,19–20 

Three seconds later, Lukman urgently commanded "left turn". The EGPWS voice alert then sounded, "Too low, terrain", "bank angle, bank angle" "terrain – terrain" warning. At the same time, First Officer called to Captain Sigit "sir! sir! sir!". The aircraft then impacted the ground.[2]: 12–14,19–20 

NTSC noted that there was not good crew resource management throughout the flight. Neither pilot was trained sufficiently in handling the aircraft when the EGPWS warning alert sounded. The Company Operations Manual (COM) specified that the crew briefing should be updated if changing circumstances so required. Captain Sigit did update the briefing when the first approach was discontinued and the go-around was conducted. Captain Sigit's disregard of the EGPWS alerts that sounded as the aircraft was being maneuvered was in non-conformance with the instructions for crew response to EGPWS alerts and cautions, as published in the COM. That, together with their lack of flight crew training in EGPWS, meant that they had not been properly prepared to respond in a timely and appropriate manner to the alerts and warnings provided by the EGPWS. Had Captain Sigit executed the appropriate responses to those EGPWS alerts it is unlikely that the crash would have occurred.[2]: 22 

Neither flight crew member conformed to the instructions about flight crew responsibilities during a visual approach, as published in the COM. This resulted in their being unable to assure the safety of flight at low level while manoeuvring the aircraft in proximity with terrain in conditions of reduced visibility. Had they more carefully planned the second approach, and closely cooperated with each other, they may have achieved a safe approach and landing. Their disregard of the published procedures bypassed the safety criteria and inbuilt risk treatments in the design of those procedures.[2]: 22 

See also

[edit]

References

[edit]
  1. ^ a b c "Pesawat Aviastar Diduga Jatuh di Wamena". Archived from the original on 9 August 2016. Retrieved 6 June 2016.
  2. ^ a b c d e f g h i j k l "Final Report PK-BRD". Archived from the original on 16 July 2015. Retrieved 6 June 2016.
  3. ^ "Semua Jenazah Kru Pesawat Avia Star Dievakuasi". Kompas. 9 April 2009. Retrieved 6 June 2016.
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy