Status: | Accident investigation report completed and information captured |
Datum: | dinsdag 7 oktober 2008 |
Tijd: | 12:42 |
Type: | Airbus A330-303 |
Luchtvaartmaatschappij: | Qantas |
Registratie: | VH-QPA |
Constructienummer: | 0553 |
Bouwjaar: | 2003 |
Aantal vlieguren: | 20040 |
Aantal vluchten: | 3740 |
Motoren: | 2 General Electric CF6-80E1A3 |
Bemanning: | slachtoffers: 0 / inzittenden: 12 |
Passagiers: | slachtoffers: 0 / inzittenden: 303 |
Totaal: | slachtoffers: 0 / inzittenden: 315 |
Schade: | Licht |
Gevolgen: | Repaired |
Plaats: | 154 km (96.3 mijl) W of Learmonth, WA, Australia ( Indische Oceaan)
|
Fase: | Kruisvlucht (ENR) |
Soort vlucht: | Internationale lijnvlucht |
Vliegveld van vertrek: | Singapore-Changi International Airport (SIN/WSSS), Singapore |
Vliegveld van aankomst: | Perth Airport, WA (PER/YPPH), Australië |
Vluchtnummer: | 72 |
Beschrijving:At 09:32 local time (01:32 UTC) on 7 October 2008, an Airbus A330-303 aircraft, registered VH-QPA, departed Singapore (SIN) on a scheduled passenger transport service to Perth (PER), Australia. On board flight QF72 were 303 passengers, nine cabin crew and three flight crew. At 12:40:28, while the aircraft was cruising at 37,000 ft, the autopilot disconnected. That was accompanied by various aircraft system failure indications. At 12:42:27, while the crew was evaluating the situation, the aircraft abruptly pitched nose-down. The aircraft reached a maximum pitch angle of about 8.4 degrees nose-down, and descended 650 ft during the event. After returning the aircraft to 37,000 ft, the crew commenced actions to deal with multiple failure messages. At 12:45:08, the aircraft commenced a second uncommanded pitch-down event. The aircraft reached a maximum pitch angle of about 3.5 degrees nose-down, and descended about 400 ft during this second event.
At 12:49, the crew made a PAN emergency broadcast to air traffic control, and requested a clearance to divert to and track direct to Learmonth. At 12:54, after receiving advice from the cabin crew of several serious injuries, the crew declared a MAYDAY. The aircraft subsequently landed at Learmonth Airport, WA (LEA) at 13:50.
At least 110 of the 303 passengers and nine of the 12 crew members were injured; 12 of the occupants were seriously injured and another 39 received hospital medical treatment. Most of the injuries involved passengers who were seated without their seatbelts fastened.
Probable Cause:
CONTRIBUTING SAFETY FACTORS:
- There was a limitation in the algorithm used by the A330/A340 flight control primary computers for processing angle of attack (AOA) data. This limitation meant that, in a very specific situation, multiple AOA spikes from only one of the three air data inertial reference units could result in a nose-down elevator command. [Significant safety issue]
- When developing the A330/A340 flight control primary computer software in the early 1990s, the aircraft manufacturers system safety assessment and other development processes did not fully consider the potential effects of frequent spikes in the data from an air data inertial reference unit. [Minor safety issue]
- One of the aircrafts three air data inertial reference units (ADIRU 1) exhibited a data-spike failure mode, during which it transmitted a significant amount of incorrect data on air data parameters to other aircraft systems, without flagging that this data was invalid. The invalid data included frequent spikes in angle of attack data. Including the 7 October 2008 occurrence, there have been three occurrences of the same failure mode on LTN-101 ADIRUs, all on A330 aircraft. [Minor safety issue]
- The LTN-101 air data inertial reference unit involved in the occurrence (serial number 4167) also had a previous instance of the data-spike failure mode, indicating that it probably contained a marginal weakness in its hardware, which reduced the resilience of the unit to some form of triggering event.
- For the data-spike failure mode, the built-in test equipment of the LTN-101 air data inertial reference unit was not effective, for air data parameters, in detecting the problem, communicating appropriate fault information, and flagging affected data as invalid. [Minor safety issue]
- The air data inertial reference unit manufacturers failure mode effects analysis and other development processes for the LTN-101 ADIRU did not identify the data-spike failure mode.
CONTRIBUTING SAFETY FACTORS:
- There was a limitation in the algorithm used by the A330/A340 flight control primary computers for processing angle of attack (AOA) data. This limitation meant that, in a very specific situation, multiple AOA spikes from only one of the three air data inertial reference units could result in a nose-down elevator command. [Significant safety issue]
- When developing the A330/A340 flight control primary computer software in the early 1990s, the aircraft manufacturers system safety assessment and other development processes did not fully consider the potential effects of frequent spikes in the data from an air data inertial reference unit. [Minor safety issue]
- One of the aircrafts three air data inertial reference units (ADIRU 1) exhibited a data-spike failure mode, during which it transmitted a significant amount of incorrect data on air data parameters to other aircraft systems, without flagging that this data was invalid. The invalid data included frequent spikes in angle of attack data. Including the 7 October 2008 occurrence, there have been three occurrences of the same failure mode on LTN-101 ADIRUs, all on A330 aircraft. [Minor safety issue]
- The LTN-101 air data inertial reference unit involved in the occurrence (serial number 4167) also had a previous instance of the data-spike failure mode, indicating that it probably contained a marginal weakness in its hardware, which reduced the resilience of the unit to some form of triggering event.
- For the data-spike failure mode, the built-in test equipment of the LTN-101 air data inertial reference unit was not effective, for air data parameters, in detecting the problem, communicating appropriate fault information, and flagging affected data as invalid. [Minor safety issue]
- The air data inertial reference unit manufacturers failure mode effects analysis and other development processes for the LTN-101 ADIRU did not identify the data-spike failure mode.
Accident investigation:
|
Investigating agency: | ATSB (Australia) |
Status: | Investigation completed |
Duration: | 3 years and 2 months | Accident number: | AO-2008-070 | Download report: | Final report
|
|
Bronnen:
»
SKYbrary
Veiligheidsmaatregelen
A number of important safety actions have already been implemented arising from the investigation to date. These include:
1) Following a 14 October 2008 telex, Airbus issued an Operations Engineering Bulletin on 15 October, applicable to all A330 aircraft fitted with Northrop-Grumman ADIRUs which detailed a procedure for flight crew to follow in the event that specified fault indications were observed in order to reduce or eliminate the risk of a future similar in-flight upset event.
2) The aircraft operator has incorporated the material from Airbus in a Flight Standing Order for its A330 operations and has commenced a program of focussed training during simulator sessions and route checks to ensure that flight crew undertaking recurrent or endorsement training are aware of the contents of the Flight Standing Order.
3) On 27 October 2008, the Civil Aviation Safety Authority issued a media release to reinforce the ATSB's message that the occurrence was a timely reminder to 'remain buckled up when seated at all stages of the flight'.
EASA issued 1 Airworthiness Directive
EASA issued 3 Emergency Airworthiness Directives
Issued: 19-NOV-2008 | To: Airbus A330, A340 | EASA AD 2008-0203-E |
This AD requires, in case faulty Inertial Reference (IR) is detected, to isolate both the IR and ADR by accomplishment of the modified AFM operational procedure. (Superseded by EASA AD 2008-0225-E) |
Issued: 18-DEC-2008 | To: Airbus A330, A340 | EASA AD 2008-0225-E |
Requires AFM update to instruct the flight crew to de-energize the ADIRU if the OFF light is not illuminated after setting the IR and ADR pushbuttons to OFF. (Superseded by EASA AD 2009-0012-E) |
Issued: 15-JAN-2009 | To: Airbus A330, A340 | EASA AD 2009-0012-E |
Requires AFM update to instruct the flight crew to de-energize the ADIRU if the OFF light is not illuminated after setting the IR and ADR pushbuttons to OFF. |
Issued: 17-MAY-2013 | To: Airbus A340-500, -600 | EASA AD 2013-0107 |
Requires airlines to modify or replace the three FCPCs to integrate a new software standard. |
Show all...
Foto's
accident date:
07-10-2008type: Airbus A330-303
registration: VH-QPA
Video, social media
Kaart
Deze kaart geeft het vliegveld van vetrek weer en de geplande bestemming van de vlucht. De lijn tussen de vliegvelden geeft
niet de exacte vliegroute weer.
De afstand tussen Singapore-Changi International Airport en Perth Airport, WA bedraagt 3892 km (2432 miles).
This information is not presented as the Flight Safety Foundation or the Aviation Safety Network’s opinion as to the cause of the accident. It is preliminary and is based on the facts as they are known at this time.
languages:
Share
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation