If you wish to contribute or participate in the discussions about articles you are invited to join SKYbrary as a registered user

 Actions

A332, Montego Bay Jamaica, 2008

From SKYbrary Wiki

Summary
Prior to the departure of a Thomas Cook Airlines Airbus A330-200 from Montego Bay Jamaica during the hours of darkness and in normal visibility on 28 October 2008, incorrect takeoff speeds had been input to the FMS by the flight crew without this being recognised. When rotation during take off was, as a consequence, initiated too early, the aircraft failed to become airborne as expected. The aircraft commander, acting as PF, quickly selected TOGA power and the aircraft became airborne before the end of the available runway had been reached and climbed away safely.
Event Details
When October 2008
Actual or Potential
Event Type
GND, HF, RE
Day/Night Night
Flight Conditions On Ground - Normal Visibility
Flight Details
Aircraft AIRBUS A-330-200
Operator Thomas Cook Airlines
Domicile United Kingdom
Type of Flight Public Transport (Passenger)
Origin Montego Bay/Sangster International Airport
Intended Destination London Gatwick Airport
Flight Phase Take Off
TOF
Location - Airport
Airport Montego Bay/Sangster International Airport
General
Tag(s) Extra flight crew (no training)
Inadequate Aircraft Operator Procedures
HF
Tag(s) Data use error
Ineffective Monitoring
RE
Tag(s) Unable to rotate at VR
Reduced Thrust Take Off
Outcome
Damage or injury No
Causal Factor Group(s)
Group(s) Aircraft Operation
Safety Recommendation(s)
Group(s) Aircraft Operation
Investigation Type
Type Independent

Description

Prior to the departure of a Thomas Cook Airlines Airbus A330-200 from Montego Bay Jamaica during the hours of darkness on 28 October 2008, incorrect takeoff speeds had been input to the FMS by the flight crew without this being recognised and when rotation during take off was, as a consequence, initiated too early, the aircraft failed to become airborne as expected. The aircraft commander acting as PF quickly selected TOGA power and the aircraft became airborne before the end of the available runway had been reached and climbed away safely.

The Investigation

The Investigation was delegated to the UK AAIB by the State of Occurrence. It was found that the operating crew had been supplemented by an additional on duty crew member. This pilot was an A330 line Captain and also a qualified A320/A321 Training Captain.

The Investigation found that during the pre-flight preparation, the flight crew had been unable to locate the aircraft performance manual and had therefore asked the Operator’s flight dispatch department in the UK to calculate the figures using the Airbus Flight Operations Versatile Environment (FOVE) computer system. The FOVE system is a Class 1 Hardware and Type 3 Software Electronic Flight Bag

Both the aircraft commander and the co-pilot stated that they had independently received the same takeoff performance figures and these were entered into the Flight Management Guidance System (FMGS).

Neither the improbably low takeoff mass of 120,800kg266,318.412 lbs
120.8 tonnes
supplied (the actual figure recorded on the aircraft load sheet was 210,183kg463,374.196 lbs
210.183 tonnes
) nor the correspondingly low thrust settings and reference speeds were recognised as such by any of the pilots.

The Investigation was unable to identify the exact source of the data error made by the flight dispatch department but found procedural deficiencies in the Aircraft Operator’s methods for calculating performance using the FOVE system. These have since been addressed.

The flight crew were unable to explain to investigators why they did not recognise that the figures they used were outside the expected range, and it is considered possible that other crews, especially those less experienced or less rested, might be expected to make a similar oversight.

The Investigation found that a tail strike had been avoided in this event because the aircraft pitch attitude only reached a maximum of 9.5° whilst the main landing gear shock absorbers were compressed; whereas 11.5° of pitch would have been required for the tail to contact the runway.

The Investigation noted numerous other similar takeoff incidents and also that most current improvement work was focused on EFB procedural robustness and on reducing the probability of incorrect data input rather than on the addition of any additional safety net to actively monitor takeoff performance.

The Final Report of the Investigation was published on 12 November 2009 and may be read in full at the SKYbrary bookshelf: AAIB Bulletin: 11/2009, ref: EW/G2008/10/08

Two Safety Recommendations were made.

  • It is recommended that the European Aviation Safety Agency develop a specification for an aircraft takeoff performance monitoring system which provides a timely alert to flight crews when achieved takeoff performance is inadequate for given aircraft configurations and airfield conditions.”
  • It is recommended that the European Aviation Safety Agency establish a requirement for transport category aircraft to be equipped with a takeoff performance monitoring system which provides a timely alert to flight crews when achieved takeoff performance is inadequate for given aircraft configurations and airfield conditions.

Further Reading