ASN Wikibase Occurrence # 189866
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: | Tuesday 10 March 2015 |
| Time: | 12:31 |
| Type: |  Airbus A330-343X |
| Owner/operator: | Air Asia X |
| Registration: | 9M-XXM |
| MSN: | 741 |
| Year of manufacture: | 2006 |
| Engine model: | Rolls-Royce Trent 772-B60 |
| Fatalities: | Fatalities: 0 / Occupants: 222 |
| Aircraft damage: | None |
| Category: | Incident |
| Location: | nr Sydney-Kingsford Smith International Airport, NSW (SYD/YSSY) -
 Australia
|
| Phase: | Initial climb |
| Nature: | Passenger - Scheduled |
| Departure airport: | Sydney-Kingsford Smith International Airport, NSW (SYD/YSSY) |
| Kuala Lumpur International Airport (KUL/WMKK) | |
| Investigating agency: | ATSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
An Airbus A330, registered 9M-XXM and operated by AirAsia X, was conducting a regular passenger service from Sydney, Australia to Kuala Lumpur, Malaysia. On departure from runway 16R the aircraft was observed by air traffic control to enter the departure flight path of the parallel runway 16L. Following advice from air traffic control, the flight crew identified a problem with the onboard navigation systems. Attempts to troubleshoot and rectify the problem resulted in further degradation of the navigation system, as well as to the aircraft’s flight guidance and flight control systems. The crew elected to discontinue the flight but were unable to return to Sydney as the weather had deteriorated in the Sydney area and the available systems limited the flight to approaches in visual conditions. The aircraft was instead radar vectored to Melbourne and the flight completed in visual conditions.
The ATSB found that when setting up the aircraft’s flight management and guidance system, the captain inadvertently entered the wrong longitudinal position of the aircraft. This adversely affected the onboard navigation systems however, despite a number of opportunities to identify and correct the error, it was not noticed until after the aircraft became airborne and started tracking in the wrong direction. The ATSB also found that the aircraft was not fitted with an upgraded flight management system that would have prevented the data entry error via either automated initialisation or automatic correction of manual errors.
The flight crew attempted to troubleshoot and rectify the situation while under heavy workload. Combined with limited guidance from the available checklists, this resulted in further errors by the flight crew in the diagnosis and actioning of flight deck switches.
Finally, the ATSB identified that effective monitoring and assistance by air traffic control reduced the risk to the occurrence aircraft and other aircraft in the area.
Accident investigation:
 |
|
Sources:
http://www.atsb.gov.au/media/5771318/ao-2015-029_final.pdf
Images:
Planned departure route (green) vs actual route (blue) (Google earth, modified by the ATSB)
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 07-Sep-2016 08:13 | harro | Added |
| 07-Sep-2016 10:09 | harro | Updated [Photo, ] |
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