ASN Wikibase Occurrence # 236680
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Friday 24 November 2017 |
| Time: | 12:22 LT |
| Type: |  Airbus A320-216 (WL) |
| Owner/operator: | Indonesia AirAsia |
| Registration: | PK-AZE |
| MSN: | 5098 |
| Year of manufacture: | 2012 |
| Fatalities: | Fatalities: 0 / Occupants: 151 |
| Aircraft damage: | None |
| Category: | Incident |
| Location: | near Perth Int Airport, WA -
 Australia
|
| Phase: | Initial climb |
| Nature: | Passenger - Scheduled |
| Departure airport: | Perth Airport, WA (PER/YPPH) |
| Denpasar-Ngurah Rai Bali International Airport (DPS/WADD) | |
| Investigating agency: | ATSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The Indonesia AirAsia Airbus A320 departed Perth, Australia on a scheduled passenger flight to Denpasar, Indonesia. Shortly after take-off from runway 21, the aircraft turned left, contrary to the cleared standard instrument departure, and at a height of about 223 ft above ground level, which was below the minimum height for turns specified by the operator. Air traffic control (ATC) assigned a series of headings to the flight crew. The aircraft was also turned through one of the headings assigned by ATC. An additional heading was subsequently issued by ATC to return the aircraft back to its planned track. The flight continued to Denpasar without further incident.
ATSB Findings:
From the evidence available, the following findings are made with respect to the data entry error related operational non-compliance of an Airbus A320, registered PK-AZE that occurred at Perth Airport, Western Australia, on 24 November 2017.
Contributing factors:
- Based on a recent landing, the first officer assumed runway 03 would be in use and programmed this runway for take-off into the flight management guidance system (FMGS) before listening to the automatic terminal information service (ATIS). Although the first officer copied runway 21 from the data recorded onto the flight plan, he did not notice this differed from what he had programmed into the FMGS and briefed the captain for a runway 03 takeoff.
- The captain did not obtain any independent information about the runway-in-use for pre-departure checks, including listening to the ATIS and reviewing data recorded on the flight plan, and likely relied on verbal information from the first officer.
- The incorrect programming of the FMGS was not detected before take-off despite numerous cues that the departure runway and flight path was different to what was briefed. Although the flight crew sensed there was something amiss with their pre-flight preparation, they continued without further checking.
- Shortly after take-off from runway 21, the aircraft was turned left at 223 ft above ground level. This was below the minimum allowable height of 400 ft stipulated by the operator, and well before and in the opposite direction to the cleared standard instrument departure.
Other factors that increased risk:
- The flight crew did not communicate the nature of the problem to air traffic control and so did not effectively utilise air traffic control as an available resource. This resulted in the captain unnecessarily reprogramming the FMGS at a time when workload was already high.
Accident investigation:
 |
|
Sources:
ATSB
Images:
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 03-Jun-2020 10:36 | harro | Added |
| 10-Jun-2022 09:19 | Ron Averes | Updated [Location] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation