Air India A321 Suffers Tail Strike During Hard Landing at Mumbai

Casualties unknown • MUMBAI, IN

An Air India Airbus A321 experienced a significant tail strike and hard landing at Mumbai Airport after thrust levers were not properly retarded during the landing flare.

What happened

On February 15, 2015, an Air India Airbus A321, registration VT-PPD, was completing its third flight sector of the day, traveling from Mangalore to Mumbai. The flight, operating as AI-680, carried 187 individuals, including 7 crew members.

During the ILS approach to runway 2 and 7, the aircraft was being manually flown by the First Officer, while the Pilot in Command (PIC) acted as the pilot monitoring. At approximately 40 feet above the ground, the PIC instructed the First Officer to flare and reduce the descent rate. However, the thrust levers remained in the MAX CLIMB detent rather than being moved to the IDLE position. This caused the autothrust system to remain engaged, actively increasing thrust to maintain target speed.

This configuration resulted in a high rate of descent and an initial bounce on the runway. During the bounce, the PIC took control of the aircraft and moved the thrust levers to IDLE, which disengaged the autothrust. In an attempt to manage the descent, the PIC applied a strong nose-up input. This maneuver, combined with the extension of ground spoilers, led to a second, severe hard landing that caused the aircraft's tail to strike the runway.

The investigation

The AAIB India investigation examined the digital flight data recorder (DFDR) and the aircraft's structural condition. Investigators found that while the crew believed the thrust levers had been retarded, the DFDR confirmed they remained at the MAX CLIMB detent during the initial touchdown.

Physical inspections of the aircraft revealed significant structural damage to the aft fuselage, specifically affecting the skin and internal structures at stations 17 and 18. The investigation also noted that several airframe frames were deformed or cracked, and the main landing gear shock absorbers and tires had exceeded their design load limits. The investigation also reviewed the software status of the Spoiler and Elevator Computer (SEC), noting that a planned modification was only partially completed at the time of the incident.

Findings

  • The primary cause of the incident was that the thrust levers were not retarded to the IDLE detent during the landing flare, causing the autothrust to maintain high power and a high descent rate.
  • The initial bounce was followed by a secondary hard landing caused by the pilot's heavy nose-up input and the subsequent loss of lift following ground spoiler extension.
  • The Pilot in Command did not effectively monitor the First Officer's handling of the thrust levers during the landing phase.
  • There were no injuries to the 180 passengers or 7 crew members on board.
  • The weather, characterized by haze and 4000 meters of visibility, was not a contributing factor to the event.

Probable cause

The incident was caused by the failure to retard the thrust levers to the IDLE detent during the flare, which kept the autothrust engaged and led to a high-energy bounce. This was compounded by the pilot's subsequent heavy nose-up input during the second touchdown, which resulted in a severe hard landing and tail strike.

Frequently asked questions

What happened in the 2015-02-15 AIR INDIA A321 accident near MUMBAI, IN?

An Air India Airbus A321 experienced a significant tail strike and hard landing at Mumbai Airport after thrust levers were not properly retarded during the landing flare.

What aircraft was involved and where did it happen?

The accident on 2015-02-15 involved a AIR INDIA A321, registration VT-PPD, operated by Air India Ltd., India, at MUMBAI, IN.

What was the probable cause of the accident?

The incident was caused by the failure to retard the thrust levers to the IDLE detent during the flare, which kept the autothrust engaged and led to a high-energy bounce. This was compounded by the pilot's subsequent heavy nose-up input during the second touchdown, which resulted in a severe hard landing and tail…

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 40,000+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.