If you wish to contribute or participate in the discussions about articles you are invited to join SKYbrary as a registered user
Difference between revisions of "B744, Bangkok Thailand, 1999"
From SKYbrary Wiki
|Line 1:||Line 1:|
Revision as of 21:02, 12 July 2010
|On 23 September 1999, a Boeing 747-400 being operated by Qantas on a scheduled passenger service from Sydney Australia to Bangkok overran Runway 21L during an attempted night landing in normal visibility and came to a halt substantially intact 320 metres beyond the runway end. There was no fire and a precautionary evacuation of the aircraft was not begun until 20 minutes after it came to rest. Only minor injuries were sustained by 38 of the 410 occupants, some during the initial runway excursion, others as a consequence of the evacuation. The aircraft remained substantially intact during the overrun although the nose landing gear and one main landing gear separated. The picture below, taken from the Official Accident Report, shows the aircraft in its final stopping position.|
|Actual or Potential
|Human Factors, Runway Excursion, Weather|
|Flight Conditions||On Ground - Normal Visibility|
|Aircraft||BOEING 747-400 (international, winglets)|
|Type of Flight||Public Transport (Passenger)|
|Location - Airport|
|Airport||Bangkok/Suvarnabhumi International Airport|
Flight / Cabin Crew Co-operation
|Tag(s)||Overrun on Landing,|
Excess Water Depth"Excess Water Depth" is not in the list (Overrun on Landing, Directional Control, Excessive Airspeed, RTO decision after V1, High Speed RTO (V above 80 but not above V1), Unable to rotate at VR, Collision Avoidance Action, Late Touchdown, Significant Tailwind Component, Significant Crosswind Component, ...) of allowed values for the "RE" property.
|Damage or injury||Yes|
|Fatalities||None"None" is not in the list (Few occupants, Many occupants, Most or all occupants) of allowed values for the "Fatalities" property. ()|
|Causal Factor Group(s)|
On 23 September 1999, a Boeing 747-400 being operated by Qantas on a scheduled passenger service from Sydney Australia to Bangkok overran Runway 21L during an attempted night landing in normal visibility and came to a halt substantially intact 320 metres beyond the runway end. There was no fire and a precautionary evacuation of the aircraft was not begun until 20 minutes after it came to rest. Only minor injuries were sustained by 38 of the 410 occupants, some during the initial runway excursion, others as a consequence of the evacuation. The aircraft remained substantially intact during the overrun although the nose landing gear and one main landing gear separated. The picture below, taken from the Official Accident Report, shows the aircraft in its final stopping position.
The Aircraft Accident Investigation Committee of Thailand would normally have investigated the event but on 18 November, this Committee delegated the investigation to the Australian Transport Safety Bureau (ATSB).
The ATSB Investigation established that the approach had been flown with the First Officer as PF and with flaps 25 selected and that the flight crew had intended to select idle reverse thrust after touchdown. It was noted that an on-duty Second Officer had been occupying the principal supernumerary seat in the flight deck and that the aircraft commander was a management pilot with relatively little experience on the aircraft type compared to both the other pilots.
The crew elected to use flaps 25 and idle reverse as the configuration for the approach and landing, in accordance with normal company practice. At various stages during the approach to runway 21L, the crew were informed by ATC that there was a thunderstorm and heavy rain at the airport, and that visibility was 4 km or greater. The crew was not made aware of the fact that another Company aircraft had gone around from the same final approach at about 250 feet agl a few minutes earlier but were told shortly before landing that the runway was wet and that the last landing aircraft (which had preceded the Company go around) had reported that braking action was ‘good’. The flight crew noted no effect from the weather until visibility reduced when the aircraft entered very heavy rain as it descended through 200 ft on late final approach. The aircraft had then started to deviate above the ILS GS, passing over the runway threshold at 169 knots and a height of 76 feet. Those parameters were within company limits. (The applicable target speed for the final approach was 154 knots and the ideal threshold crossing height was 44 feet.). When the aircraft had been approximately 10 feet above the runway, the Captain instructed the First Officer to go around, but when the main gear touched the runway as the First Officer was advancing the engine thrust levers, the Captain immediately cancelled the go-around by retarding the thrust levers without announcing his actions. Those events were concluded to have resulted in confusion amongst the other pilots and contributed to the crew not selecting (or noticing the absence of) reverse thrust during the landing roll. In addition, the actual touchdown point was found to have been 1002 metres along the 3,150 metre runway, 636 m beyond the ideal point.
Due to a variety of factors associated with the cancellation of the go-around, the aircraft’s speed did not begin to decrease below the actual touchdown speed until the aircraft was over halfway down the runway. The investigation established that, during the landing roll, the aircraft tyres had aquaplaned on the water-affected runway such that the effectiveness of the wheel brakes was limited to about one third of that on an equivalent dry runway. In such conditions and without reverse thrust, there was no prospect of the crew stopping the aircraft in the runway distance remaining after touchdown. The aircraft overran the 100 metre stopway (at the end of the runway) at a speed of 88 knots, before stopping 220 metres later with the nose resting on an airport perimeter road. The depth of water on the runway when the aircraft landed could not be determined but it was sufficient to allow dynamic aquaplaning to occur (i.e. at least 3 mm). The water buildup was the result of heavy rain on the runway in the preceding minutes, and possibly because the runway was both un-grooved and without a porous friction course.
The Investigation concluded that although there were no definite measurements available, there had been sufficient rainfall just prior to the landing to have caused the runway surface water depth to have exceeded 3 mm. It was considered likely that the distribution of water on the runway had changed during the six minute period between the previous landing aircraft and the accident aircraft with actual braking action likely to have been close to ‘poor’.
During the examination of the performance of the aircraft on the runway, it became evident that the Flaps 25 / Idle Reverse Thrust landing procedure used (and which was the ‘preferred’ company procedure) had not been appropriate for operations on to water-affected runways. The more appropriate approach/landing procedure would have been Flaps 30 / Full Reverse Thrust, which would have involved a lower approach speed, probably been easier to fly in terms of speed control and the runway aim point and provided maximum aerodynamic drag after touchdown when the effectiveness of the wheel brakes could be reduced because of aquaplaning. The Investigation concluded that had this configuration been used, the overrun would most probably have been avoided. The Investigation also considered that, as with other Company B747-400 pilots, the accident flight crew had “not been provided with appropriate procedures and training to properly evaluate the potential effect the Bangkok Airport weather conditions might have had on the stopping performance of the aircraft. In particular, they were not sufficiently aware of the potential for aquaplaning and of the importance of reverse thrust as a stopping force on water-affected runways.”
Conclusions of the Investigation
The overall structure of the Investigation followed the Reason Model of accident causation and so the Conclusions were presented in those terms and are quoted below verbatim.
(1) Significant Active Failures
A number of active failures that had a significant influence on the development of the accident were identified:
- The flight crew did not use an adequate risk management strategy for the approach and landing.
- The first officer did not fly the aircraft accurately during final approach.
- The captain cancelled the go-around decision by retarding the thrust levers.
- The flight crew did not select (or notice the absence of) idle reverse thrust.
- The flight crew did not select (or notice the absence of) full reverse thrust.
- The flight crew did not consider all relevant issues when deciding not to conduct an immediate evacuation.
- Some crew members did not communicate important information during the emergency period.
Other significant active failures found were:
- The runway surface was affected by water.
- The cabin interphone and passenger address system became inoperable.
(2) Significant Latent Failures - Qantas Flight Operations"
- Company-published information, procedures, and flight crew training for landing on water-affected runways were deficient.
- Flight crew training in evaluating the procedural and configuration options for approach and landing was deficient.
- Procedures and training for flight crew in evaluating whether or not to conduct an emergency evacuation were deficient.
- Procedures and training for cabin crew in identifying and communicating relevant information during an emergency were deficient.
- The processes for identifying hazards were primarily reactive and informal, rather than proactive and systematic.
- The processes to assess the risks associated with identified hazards were deficient.
- The processes to manage the development, introduction and evaluation of changes to operations were deficient.
- The design of operational procedures and training were over-reliant on the decision making ability of Company flight crew and cabin crew and did not place adequate emphasis on structured processes.
- Management culture was over-reliant on personal experience and did not place adequate emphasis on structured processes, available expertise, management training and research and development when making strategic decisions.
Significant Latent Failures - CASA (the Australian National Aviation Authority (NAA)):
- The regulations covering contaminated runway operations were deficient.
- The regulations covering emergency procedures and emergency procedures training were deficient.
- The surveillance of airline flight operations was deficient.
Other Significant Latent failures:
- The redundancy provided by the normal and alternate cabin interphone and public address systems in B747-400 aircraft was significantly reduced because components for both systems were co-located in the same relatively damage-prone position in the lower fuselage aft of the nose wheel.
Five Safety Recommendations were made where important safety matters had not been (or were not being) addressed at the conclusion of the Investigation. These were:
- Safety Recommendation R20000239
That CASA ensures that all Australian operators of high capacity jet aircraft have in place procedures and training to ensure flight crews are adequately equipped for operations on wet/contaminated runways.
- Safety Recommendation R20000235
That CASA review the intent of CAO 48 to ensure that operators consider all duties associated with a pilot’s employment (including managerial and administrative duties) when designing flight and duty time schedules, and that this requirement is not restricted to situations where there are one or two pilots.
- Safety Recommendation R20000231
That the FAA and JAA review the design requirements for high capacity aircraft to ensure the integrity of the cabin interphone and passenger address systems, particularly with respect to cabin/flight deck communications, in the event of runway overruns and other relatively common types of events which result in landing gear and lower fuselage damage.
- Safety Recommendation R20000234
That CASA should consider including the following issues as requirements of operators during its current development of new legislation in the area of emergency procedures training:
- How flight crew should gather and evaluate relevant information and make a decision regarding which type of emergency response is most suitable.
- How cabin crew should communicate with each other and the flight deck in emergency situations (in terms of technique, terminology, and methods to ensure that accurate information reaches the flight deck).
- How cabin crew should communicate during an emergency on the ground when there is a loss of PA and interphone communications.
- How cabin crew should systematically and regularly identify problematic situations in an aircraft during an emergency (including guidelines on what types of information are most important and ensuring that all areas of the aircraft are examined).
- Leadership and coordination functions of cabin crew supervisors during an emergency situation. For example, how the supervisors should assess the situation (particularly in circumstances that had not been clearly defined), assign roles and responsibilities amongst the cabin crew, coordinate the gathering of information, and coordinate the distribution of information.
- How cabin crew should effectively obtain information from passengers concerning safety-related issues.
- How cabin crew should effectively use language and assertiveness for crowd control and managing passenger movement towards exits during emergency situations, as well as passenger control outside the aircraft.
- That cabin crew supervisors are provided with appropriate resources to ensure that they can effectively communicate with other areas of the cabin during emergency situations (e.g. providing the supervisor with ready access to an ‘assist’ crewmember at their assigned location).
- Safety Recommendation R20000238
That CASA consider widening its existing skill-base within the Compliance Branch to ensure that CASA audit teams have expertise in all relevant areas, including human factors and management processes.
The Final Report of the Investigation was released on 26 April 2001 and may be seen in full at SKYbrary bookshelf: Investigation Report 199904538 Boeing 747-438, VH-OJH, Bangkok,Thailand 23 September 1999)