Air India Flight Tail Scrapes Runway During Go‑Around at Bengaluru Airport

On the twenty-second day of May in the year two thousand twenty‑six, at approximately fifteen hundred and fifteen hours local time, an Air India Airbus A320‑200, registration VT‑AIJ, while executing a go‑around maneuver at Bangalore's Kempegowda International Airport, reportedly allowed its tail to make contact with the threshold of runway three‑four, thereby producing a visible scrape and prompting an immediate cessation of the flight's departure sequence.

The pilot in command, subsequently identified as Captain Rajiv Singh, communicated to the airport tower that the aircraft's rear fuselage had grazed the runway surface, a claim later corroborated by photographic evidence released by the airport's fire and rescue services, whilst the tower's controller logged the incident as an unplanned aircraft‑ground contact requiring immediate remedial action under standard operating protocols.

The Directorate General of Civil Aviation, invoking its mandate to safeguard civil aviation safety, issued an immediate advisory ordering the aircraft to be withdrawn from service pending a thorough technical examination, and announced that an independent safety audit would be convened by the Accident Investigation Bureau within the ensuing forty‑eight hours to ascertain causative factors and compliance with prevailing maintenance directives.

Passengers aboard flight AI‑321, numbering approximately one hundred and twenty‑three souls, were consequently subjected to a protracted delay of over three hours, during which they were escorted to the terminal lounge where they were offered complimentary refreshments, yet remained without a definitive re‑booking schedule, thereby exposing the airline's contingency planning deficiencies and raising concerns regarding passenger rights under the Civil Aviation Requirements.

Observers of Indian aviation governance have noted that the recurrence of runway‑contact incidents, despite the promulgation of advanced safety management systems, may reflect a systemic lag in the translation of regulatory edicts into practical operational discipline, an observation that invites scrutiny of the efficacy of audit mechanisms, the robustness of crew training curricula, and the adequacy of infrastructural maintenance regimes at major hubs such as Bengaluru.

Does the existing framework of civil aviation oversight, which ostensibly entrusts the Directorate General of Civil Aviation with unilateral investigatory authority, truly afford sufficient transparency and independence to guarantee that findings of such runway‑contact events are insulated from administrative influence, or does it permit a latitude of discretion that may, in practice, dilute the potency of remedial measures prescribed to avert recurrence? To what extent does the present regulatory design, which mandates periodic safety audits yet relies heavily upon self‑reported compliance by the carriers, enable a substantive verification of maintenance records and pilot procedural adherence, especially in circumstances where the immediate visual evidence of structural contact suggests possible procedural lapses that may be obfuscated by institutional inertia? Might the financial outlay necessary to ground, inspect, and subsequently certify an aircraft following such an incident, funded largely by public aviation levies, be justified in the absence of a demonstrably transparent adjudication process, thereby compelling the ordinary citizen to bear the fiscal and liberty‑costs of an administrative apparatus that appears, at times, more preoccupied with preserving institutional reputation than with delivering unequivocal safety assurances?

Is it incumbent upon the civil aviation regulator to assume full evidentiary responsibility for the veracity of incident reports, thereby mandating an exhaustive forensic analysis of both flight data recorder outputs and runway surface integrity, or does the prevailing practice of delegating such duties to the airline's internal safety unit risk engendering a conflict of interest that undermines the public's confidence in the impartiality of the investigative findings? Should the parliamentary oversight committees, entrusted with representing the citizenry's concerns, exercise a more proactive stance by instituting mandatory public hearings on each such runway incident, thereby compelling the aviation authorities to justify their procedural choices before elected representatives, or does the current reliance on confidential briefings erode the democratic principle that governmental accountability must be visibly demonstrable to the electorate? Can the ordinary Indian commuter, equipped merely with the publicly released aviation safety bulletins, feasibly contest the official narrative presented by the airline and regulator, or does the asymmetry of information and the technical opacity inherent in aeronautical investigations render such citizen‑led scrutiny a distant ideal, thereby challenging the very premise of an accountable administrative state?

Published: May 22, 2026

Published: May 22, 2026