DGCA Probes IndiGo A321 Tail Strike

An IndiGo Airbus A321neo operating flight 6E 6542 from Guwahati to Bengaluru suffered a tail strike while landing at Kempegowda International Airport on September 28, 2026. The aircraft experienced what the airline described as an abnormal runway contact during gusty weather conditions, touched down safely on its second attempt, and was subsequently grounded for maintenance checks. All passengers and crew were safe, and the aircraft was declared AOG — aircraft on ground — pending inspection.

The Directorate General of Civil Aviation (DGCA), India's civil aviation regulator, has initiated an investigation into the event. The inquiry comes amid concern over a cluster of tail strike incidents involving A321-family aircraft in IndiGo's fleet, one of the largest narrowbody operations in the world.

What happened on 6E 6542

According to details of the event, the A321neo made its initial approach into Bengaluru in gusty conditions and contacted the runway with its tail during the landing flare — the classic geometry of a tail strike, in which the nose is raised far enough that the aft fuselage reaches the pavement before or as the main landing gear touches. The crew executed a go-around, and on the second attempt the aircraft landed without further incident.

Passengers and crew were unharmed and the flight concluded without evacuation. The aircraft, however, did not return to service. A tail strike is treated by manufacturers and regulators as a significant structural event: the aft fuselage and the tail cone absorb the contact loads, and the damage is not always visible from a walk-around. Undetected damage to the aft pressure bulkhead or fuselage frames can compromise structural integrity under pressurisation cycles, which is why any confirmed or suspected tail strike triggers a defined inspection regime before the aeroplane flies again.

The A321neo's geometry problem

The A321 is a stretched aeroplane, and its length is the root of its tail strike propensity. With a fuselage over 44 metres long and the main landing gear sitting well forward of the tail, the pitch angle at which the tail contacts the runway — the tail strike pitch angle — is close to the pitch attitudes used routinely during normal landings and rotations. The margin between a normal touchdown attitude and a strike is measured in a handful of degrees.

Gusty conditions compress that margin further. A gust on the approach or during the flare changes airspeed and sink rate late in the manoeuvre, and a crew compensating with thrust or pitch can find the attitude drifting past the limit. The A321neo's longer length relative to the A320 makes it less forgiving than its shorter sibling — a fact reflected in flight crew operating manuals, which specify lower rotation rates and, on some variants, tail strike protection in the flight control logic. The type rating syllabus for the A321 differs from the A320 precisely because of handling differences of this kind, and recurrent training emphasises flare discipline on the longer variant.

A pattern, not an isolated event

The DGCA's investigation carries an added dimension because the Bengaluru event was not the only recent tail strike in the fleet. In the same month, another IndiGo A321 flight from Delhi to Gorakhpur executed a go-around after suffering a tail strike on approach. Two events in a month, at different airports, in different weather regimes, draws the regulator's attention toward fleet-level questions rather than a single crew's flare technique.

When a regulator sees a cluster of similar events across one operator's fleet, the lines of inquiry typically widen to include training standards — how flare and go-around technique is being taught and checked — line operations data, and whether scheduling and rostering practices leave crews fatigued on the sectors where these events are occurring. Neither event resulted in injuries, but the DGCA's concern is structural and systemic: tail strikes are expensive, they take aeroplanes out of service for days, and a strike that goes undetected or improperly inspected is one of the classic precursors to in-flight structural failure. The aft pressure bulkhead is a single load path; history has shown what undetected damage there can lead to.

Grounded and inspected

For the aircraft involved in Bengaluru, the immediate path is engineering. Post-tail-strike inspections on the A321 family follow a defined schedule based on the severity of the reported contact: visual checks of the aft fuselage skin and tail cone, then, depending on findings, detailed inspections of frames and stringers in the contact zone, and checks of the aft pressure bulkhead and its attachments. Where damage is confirmed, repairs run through Airbus structural repair manuals and may require MRO capacity for skin panels or frame replacement. IndiGo's maintenance organisation will complete the work before the aircraft is released to service; the length of the AOG depends on what the inspections find.

India's aviation market context sharpens the stakes. IndiGo operates one of the world's largest A320-family fleets, and India's air traffic growth continues at a pace that keeps utilisation high and schedules tight. An AOG event removes capacity from a network with little slack, and a fleet-level pattern of tail strikes could, if unaddressed, result in the DGCA imposing additional operational requirements — from revised training programmes to restrictions on how the A321 fleet is operated into shorter or gust-prone runways. Landing accidents and abnormal runway contacts remain the highest-frequency serious event category in commercial aviation, as the 21 Air 767 overrun at Miami illustrated last month, and the A321neo's sheer fleet volume — with carriers from Delta's 100-aircraft order to IndiGo's own hundreds of examples — multiplies the exposure to any fleet-level handling issue.

For now, the DGCA investigation is in its early phases: data from the aircraft, crew statements, weather records from Kempegowda International Airport, and the results of the engineering inspections will all feed its findings. IndiGo has not commented publicly beyond confirming the event and the grounding. The regulator's report, when it arrives, will indicate whether Bengaluru was a gusty-day aberration — or the visible edge of a training and operations issue worth correcting across the fleet.