Overview
• Operator: IndiGo Airlines
• Aircraft Model: Airbus A321-200N (neo)
• Registration: VT-IBI
• Flight Number: 6E-5325
• Route: Mumbai (BOM) → Chennai (MAA)
• Date: 8 March 2025
• Occupants: 186 (passengers and crew)
• Casualties: None
• Aircraft Status: Grounded in Chennai for inspection
• Investigation: Led by India’s DGCA
⸻
Incident Summary
IndiGo flight 6E-5325, an Airbus A321neo, suffered a tail strike while landing on runway 25 at Chennai International Airport.
The aircraft continued its rollout without further incident and taxied to the apron. No injuries were reported.
Following the event, India’s DGCA (Directorate General of Civil Aviation) launched an investigation.
The aircraft remains grounded in Chennai for a structural inspection and possible repairs.
⸻
Sequence of Events
Final Approach & Landing
• The A321neo was on approach to Chennai’s runway 25 after a routine flight from Mumbai.
• During touchdown, the aircraft pitched up excessively, causing the rear fuselage to make contact with the runway.
Rollout & Taxi to Apron
• Despite the tail strike, the aircraft remained controllable and completed its landing roll safely.
• The crew taxied to the apron normally, where maintenance teams inspected the aircraft.
Post-Landing Assessment & Investigation
• A tail strike was confirmed, prompting an immediate grounding for further inspections.
• India’s DGCA was notified and initiated a formal investigation into the incident.
⸻
Investigation Findings & Initial Analysis
1. Excessive Pitch During Landing
• A321neo aircraft are susceptible to tail strikes if the nose is raised too high during touchdown.
• This can happen due to:
• Flare technique errors (pilot holds nose too high)
• Delayed or excessive nose-up inputs
• Autoland system behavior in gusty conditions
2. Possible Contributing Factors
• High approach angle or misjudged flare:
• If the aircraft approached with too much nose-up attitude, the tail could have made contact before the main gear fully settled.
• Incorrect landing speed:
• If the aircraft was too slow on touchdown, a higher pitch angle may have been needed to arrest descent, increasing the risk of a tail strike.
• Weather & runway conditions:
• Winds or turbulence may have caused sudden pitch changes before landing.
⸻
Potential Causes & Contributing Factors
1. Pilot-Induced Flare Issues
• The flare phase may have been too aggressive, leading to excessive nose-up pitch.
• Possible overcorrection or delayed input by the pilot.
2. Aircraft Weight & Balance
• If the aircraft was near aft center of gravity (CG) limits, the nose could have been more sensitive to pitch changes, making a tail strike more likely.
3. Approach & Landing Speed Management
• Incorrect approach speed or late flare initiation could have led to excessive nose-up inputs to compensate for descent rate.
4. Autopilot or Autothrottle Behavior
• If the aircraft was on autoland or auto-throttle during approach, system behavior may have influenced pitch handling.
⸻
Safety Recommendations & Future Prevention
1. Enhanced Pilot Training for Tail Strike Prevention
• Pilots should receive updated training on A321neo-specific landing techniques to avoid excessive pitch angles.
• Use of flight simulators to practice tail strike avoidance.
2. Improved Flare & Speed Monitoring
• Flight crews should closely monitor approach speeds and flare techniques to prevent excessive pitch inputs.
• Consider more detailed standard operating procedures (SOPs) for the A321neo.
3. Aircraft Weight & Balance Considerations
• Airlines should review loading procedures to avoid aft CG bias, which increases sensitivity to pitch inputs.
4. Investigate Possible System Factors
• The investigation should determine whether autoland/autothrottle settings influenced pitch behavior.
⸻
Conclusion
IndiGo flight 6E-5325 suffered a tail strike during landing at Chennai, but landed safely without injuries.
The aircraft remains grounded for further inspection, and India’s DGCA is leading the investigation to determine the exact cause.
While pilot technique is a leading factor in tail strikes, aircraft weight, approach speed, and system behavior will also be analyzed.
⸻
Disclaimer
“This report is based on available information as of 10 March 2025. While every effort has been made to ensure accuracy, the completeness of the details cannot be guaranteed. If you are the rightful owner of any referenced materials and wish them removed, please email takedown@cockpitking.com.”
