Insufficient takeoff thrust during intersection departure at Basel-Mulhouse

Casualties unknown • Basel-Mulhouse Airport LFSB, CH

An Airbus A320 failed to achieve necessary takeoff performance after the crew decided to depart from an intersection using thrust settings calculated for the full runway length.

What happened

On October 6, 2014, an Airbus A320-214, registration HB-IOP, was preparing for a flight from Basel-Mulhouse (LFSB) to Djerba, Tunisia. While the crew initially intended to depart from runway 33, they later decided to use runway 15 due to air traffic.

During the taxi phase, the crew made a rapid decision to perform an intersection takeoff from taxiway GOLF to save time. This change reduced the available runway length to 2370 meters. However, the crew proceeded to takeoff without stopping at the new position, utilizing engine thrust settings that had been calculated for the much longer full runway length of 3900 meters.

As the aircraft reached the end of the takeoff roll, the captain realized the engine thrust was insufficient. To prevent an overrun, the captain increased the thrust to the maximum available and rotated the aircraft at 150 knots. The aircraft successfully climbed and continued the flight to its destination without further incident or damage.

The investigation

SUST examined the crew's decision-making process and the technical performance of the aircraft. The investigation focused on why the discrepancy between the required thrust for the shorter runway and the applied thrust went undetected. Investigators reviewed the airline's standard operating procedures, specifically looking at the "silent" verification methods used during taxiing. The investigation also looked into the use of Electronic Flight Bags (EFBs) for performance calculations and the crew's awareness of recently implemented safety checks.

Findings

  • The primary cause of the incident was that the aircraft did not achieve the required takeoff performance because the crew performed an intersection takeoff using thrust settings calculated for the full runway length.
  • The decision to utilize the intersection takeoff was made within a very short timeframe.
  • Existing company procedures required essential checks to be performed silently, which prevented a closed-loop verification process between the two pilots.
  • A recently implemented safety feature, a "caution box" designed to verify Flight Management Guidance System (FMGS) data during lineup, was ineffective because the crew was unaware of its existence.

Probable cause

The incident was caused by the crew performing a takeoff from an intersection using engine power settings intended for the full runway length, compounded by a lack of verbal cross-checking due to silent verification procedures and a lack of familiarity with new safety verification tools.

Frequently asked questions

What happened in the 2014-10-05 AIRBUS SAS A320-214 accident near Basel-Mulhouse Airport LFSB, CH?

An Airbus A320 failed to achieve necessary takeoff performance after the crew decided to depart from an intersection using thrust settings calculated for the full runway length.

What aircraft was involved and where did it happen?

The accident on 2014-10-05 involved a AIRBUS SAS A320-214, registration HB-IOP, at Basel-Mulhouse Airport LFSB, CH.

What was the probable cause of the accident?

The incident was caused by the crew performing a takeoff from an intersection using engine power settings intended for the full runway length, compounded by a lack of verbal cross-checking due to silent verification procedures and a lack of familiarity with new safety verification tools.

Investigation report by the Swiss Transportation Safety Investigation Board (STSB / SUST). Original record: https://www.sust.admin.ch/inhalte/AV-berichte/2256_d.pdf. This page is a structured re-presentation; facts and quotes are in the Swiss Transportation Safety Investigation Board (STSB), Switzerland.

Loading the flight search…