Qantas Flight 30

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Qantas Flight 30
File:Qf30 damage.jpeg
Structural damage sustained on the 747
Accident summary
Date 25 July 2008 (2008-07-25)
Summary In-flight structural damage[1]
Rapid decompression[2]
Site South China Sea west of Luzon
Passengers 346
Crew 19
Injuries (non-fatal) 0
Fatalities 0
Survivors 365 (all)
Aircraft type Boeing 747-438
Aircraft name City of Newcastle[3]
Operator Qantas
Registration VH-OJK[4]
Flight origin London Heathrow Airport
Stopover Hong Kong International Airport
Destination Melbourne Airport

Qantas Flight 30 (QF30, QFA30) was a Qantas Boeing 747-438, construction number 25067, registered in Australia as VH-OJK. QF30 was a scheduled flight from London Heathrow Airport to Melbourne Airport with a stopover in Hong Kong International Airport on 25 July 2008. The flight was interrupted when an oxygen tank exploded[5] causing a fuselage rupture just forward of the starboard wing root. There were no injuries and the plane made an emergency descent to a breathable altitude of about 10,000 feet and eventually made an emergency landing at Ninoy Aquino International Airport, Metro Manila, Philippines.

In-flight accident

The flight left Hong Kong on 25 July 2008 shortly after 9:00 am HKT (0100 UTC).[6] At 10:17 HKT (0217 UTC), passengers and crew heard a loud bang; the cabin de-pressurised and a hole in the floor of the passenger deck appeared, as well as a hole in the outside wall of the cargo deck.[7] During the emergency, parts of the aircraft's floor and ceiling collapsed.[8] Passengers reported that, despite the noise and the deployment of the oxygen masks, there was very little panic.[9] The pilots conducted an emergency descent from 29,000 feet to ensure adequate oxygen supply for the passengers, reaching 10,000 feet by 10:24 HKT (02:24 UTC).[7][10]

After the accident, numerous passengers said that some oxygen masks did not deploy, whilst others had deteriorated elastic.[11] Consequently, it was reported that one passenger smashed a panel of the ceiling to attempt to gain access to the masks. It was stated that these passengers were deprived of oxygen until the plane was lowered to a breathable altitude. The Australian Transport Safety Bureau interviewed passengers who reported problems with the oxygen masks as part of their investigation.[2]

The hole in the fuselage – roughly in an inverted T-shape – was up to 2.01 m wide and approximately 1.52 m high, located on the right side of the fuselage, below cabin floor level and immediately forward of the wing. The wing-fuselage fairing was missing, revealing some palletised cargo in the hold. However, the freight forwarder reported that all items on the manifest were accounted for. Other than some items which were located near the cylinder and resulting hole, no other cargo or baggage on the flight was damaged.[7]

The airline, in a news release, said there were no reports of injuries.[12] A few passengers reportedly displayed signs of nausea upon exiting the aircraft.[13]

Investigation

The Australian Transport Safety Bureau led the investigation, sending 4 investigators to Manila to conduct a detailed inspection of the aircraft, with Qantas, Federal Aviation Administration, Boeing, the Australian Civil Aviation Safety Authority and the Civil Aviation Authority of the Philippines also involved.[2][8][14][15][16]

Soon after the accident, the ATSB announced that air safety investigators found that an oxygen cylinder which was located in the area of the explosion hadn't been accounted for, but that it was too early to say that an oxygen cylinder could be the cause of the mid-air explosion on QF30. Regardless, the Civil Aviation Safety Authority ordered Qantas to inspect all of its oxygen cylinders and brackets which hold the cylinders on its Boeing 747 fleet.[2][17][18] The valve and mounting brackets were found, but not the bottle, number four of thirteen fitted in that bank.[19] A senior investigator, Neville Blyth, reported that the cylinder valve was found inside the cabin, having punched a hole "at least twenty centimetres in diameter" through the cabin floor.[20]

Blyth said that the flight recorders were to be analysed in the Canberra laboratories of the ATSB.[21] However, because the plane had remained airborne and operational throughout the incident, the cockpit voice recorder does not contain records of the initial event itself; its two-hour memory had been overwritten with recordings taking place after this event, during the diversion and landing. The twenty-four-hour flight data recorder does contain data covering the entire incident.[22][23][24]

On 29 August, the ATSB gave an update confirming further aspects of the initial investigation. They stated that these initial investigations had found that the aircraft took about five and a half minutes to descend from the decompression event at 29,000 feet to the altitude of 10,000 feet and that it appeared that part of an oxygen cylinder and its valve had entered the passenger cabin, then impacted with the number 2 right door handle, turning it part way. The ATSB noted that there was no risk of the door being opened by this movement, with the door systems performing as designed. All three of the aircraft's instrument landing systems as well as the anti-skid braking system were unavailable for the landing; the pilots subsequently landed the aircraft without using those systems. Most of the oxygen masks deployed in the incident, with 426 out of the 476 deployed being activated by the 346 passengers, pulling them down to activate the flow of oxygen.[25]

Preliminary findings

The cause of the accident has been determined to be an exploding oxygen tank in the cargo area, according to a preliminary finding of the Australian Transport Safety Bureau:[26]

"After clearing the baggage and cargo from the forward aircraft hold, it was evident that one passenger oxygen cylinder (number-4 from a bank of seven cylinders along the right side of the cargo hold) had sustained a sudden failure and forceful discharge of its pressurised contents into the aircraft hold, rupturing the fuselage in the vicinity of the wing-fuselage leading edge fairing. The cylinder had been propelled upward by the force of the discharge, puncturing the cabin floor and entering the cabin adjacent to the second main cabin door. The cylinder had subsequently impacted the door frame, door handle and overhead panelling, before falling to the cabin floor and exiting the aircraft through the ruptured fuselage."

Other safety concerns

Oxygen masks that were deployed after the blast failed to function properly. Some passengers were forced to share a mask when the Qantas Boeing 747 ran into trouble, while others panicked when they failed to open.[11] The FAA had recently issued airworthiness directives regarding problems with the masks on this and several other Boeing commercial aircraft models.[27]

The ATSB issued two Safety Advisory Notices, advising responsible organisations to review procedures, equipment, techniques and personnel qualifications for maintenance, inspection and handling of aviation oxygen cylinders.[28][29]

ATSB final report

Just over two years after the incident, the final report of the event was released on 22 November 2010.

From the summary released by the ATSB:

"On 25 July 2008, a Boeing Company 747-438 aircraft carrying 369 passengers and crew rapidly depressurised following the forceful rupture of one of the aircraft's emergency oxygen cylinders in the forward cargo hold. The aircraft was cruising at 29,000 ft and was 55 minutes into a flight between Hong Kong and Melbourne."

"Following an emergency descent to 10,000 ft, the flight crew diverted the aircraft to Ninoy Aquino International Airport, Manila, Philippines, where it landed safely. None of the passengers or crew sustained any physical injury."

"A team of investigators, led by the Australian Transport Safety Bureau (ATSB) and including representatives from the US National Transportation Safety Board (NTSB), the US Federal Aviation Authority (FAA), Boeing and the Civil Aviation Authority of the Philippines (CAAP) examined the aircraft on the ground in Manila. From that work, it was evident that the oxygen cylinder (number-4 in a bank along the right side of the forward cargo hold) had burst in such a way as to rupture the adjacent fuselage wall and be propelled upwards; puncturing the cabin floor and impacting the frame and handle of the R2 door and the overhead cabin panelling. No part of the cylinder (other than the valve assembly) was recovered and it was presumed lost from the aircraft during the depressurisation."

"The ATSB undertook a close and detailed study of the cylinder type, including a review of all possible failure scenarios and an engineering evaluation of other cylinders from the same production batch and of the type in general. It was evident that the cylinder had failed by bursting through, or around the base – allowing the release of pressurised contents to project it vertically upwards. While it was hypothesised that the cylinder may have contained a defect or flaw, or been damaged in a way that promoted failure, there was no evidence found to support such a finding. Nor was there any evidence found to suggest the cylinders from the subject production batch, or the type in general, were in any way predisposed to premature failure."

Repairs

Structural repairs of the aircraft were conducted in Manila by Boeing. It was ferried to Avalon on 10 November 2008. The original captain and first officer were part of the ferry crew. The only work that remained to be done at that point was replacement of the carpets and seat covers. On 18 November 2008, with all work complete, the aircraft was damaged again when another Qantas Boeing 747 collided with it at Avalon.[30]

The aircraft was eventually returned to service on 15 January 2009 but retired from service at the end of 2009.

In October 2011 the aircraft was re-registered to Nigerian Airline MaxAir, under registration code 5N-HMB.

IFALPA

In early 2010, the International Federation of Air Line Pilots' Associations awarded the Polaris Award to the three pilots involved in this incident.

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 2.2 2.3 Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 7.2 Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.0 8.1 Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. 11.0 11.1 Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Airworthiness directives
  28. AO-2008-053-SAN-006 ATSB, 29 August 2008
  29. AO-2008-053-SAN-007 ATSB, 29 August 2008
  30. Lua error in package.lua at line 80: module 'strict' not found.

External links

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.