IndiGo grounds A321neo after Bengaluru tail strike; DGCA opens probe

IndiGo grounded flight 6E 6542 for inspection after its Airbus A321neo sustained a tail strike while landing in Bengaluru amid gusty weather. India’s aviation regulator, the DGCA, has launched an investigation.

— Source publishedSun, 27 Sept, 2026, 22:58 IST·First seen Sun, 27 Sept, 2026, 23:40 IST·Source NDTV Profit

The development

IndiGo grounded flight 6E 6542 for inspection after an Airbus A321neo suffered a tail strike while landing in Bengaluru on Sunday. The DGCA launched an investigation into the incident, which occurred during gusty weather.

The numbers

  • 6E 6542
  • A321neo
  • roughly a month
  • 6E 2381

Why it matters to operators and investors

Aircraft maintenance, training and weather-operations partners may see a stronger case for solutions that reduce disruption risk and improve incident-response readiness across IndiGo’s network.

What to watch next

  • DGCA preliminary findings on weather, crew handling, runway conditions, and aircraft condition.
  • Whether DGCA orders inspections, audits, training directives, or restrictions beyond the individual aircraft.
  • Duration of the A321neo grounding and whether other IndiGo aircraft are pulled for precautionary checks.
  • Bengaluru cancellation, delay, diversion, and passenger-reaccommodation trends over the following days.
  • Any evidence of prior tail strikes, unstable approaches, or repeated weather-related incidents involving IndiGo.
  • Airbus guidance or maintenance findings indicating structural damage more extensive than initially expected.
  • Complete structural inspection and required Airbus maintenance actions before returning the A321neo to service.
  • Cooperate with DGCA investigation and preserve flight-data, cockpit-voice, weather, runway, and crew records.
  • Review Bengaluru approach, landing, wind-shear, and go-around procedures; reinforce stabilized-approach criteria across flight operations.
  • Deploy spare aircraft, reaccommodate affected passengers, and adjust rotations to contain knock-on delays.
  • Monitor social and customer-service channels to limit reputational damage from disruption rather than the incident itself.

The counter-case

The incident may be operationally immaterial: grounding one aircraft for inspection in a large fleet is unlikely to meaningfully affect capacity, revenue, or network reliability unless the investigation identifies a broader fleet, training, maintenance, or procedural issue. Tail strikes can occur in challenging wind conditions and do not inherently indicate systemic safety failures.