IndiGo Guwahati-Chennai Flight Diverts to Bengaluru After Mayday Scare.
The diversion, prompted by heavy congestion at Chennai International Airport, sparked concern among passengers and heightened aviation safety discussions, especially in the wake of a recent Air India plane crash in Ahmedabad. Despite the scare, the Airbus A321, operating as flight 6E-6764, landed safely at 8:15 PM, with no injuries reported. This report delves into the incident, its causes, passenger experiences, and the broader implications for aviation safety.
Incident OverviewIndiGo flight 6E-6764 departed Guwahati at 4:40 PM IST on June 19, 2025, with an expected arrival in Chennai at 7:45 PM. However, upon approaching Chennai International Airport, the aircraft encountered significant air traffic congestion, preventing a timely landing. The pilot attempted to land at approximately 7:45 PM but was forced to perform a “baulked landing” (a go-around maneuver) after the landing gear briefly touched the runway, due to an unstabilized approach. Unable to secure clearance for a second landing attempt in Chennai, the pilot diverted the flight to Bengaluru’s KIA, approximately 300 nautical miles away.
During the diversion, fuel reserves dwindled to critical levels, prompting the pilot to issue a ‘Fuel Mayday’ call about 35 nautical miles from Bengaluru, around 7:40 PM. The distress signal, repeated three times as per international aviation protocols (“Mayday, Mayday, Mayday”), alerted Bengaluru’s Air Traffic Control (ATC) to the life-threatening situation, ensuring priority landing clearance. The aircraft landed safely at 8:15 PM, and all 168 passengers were deplaned without incident. The plane was refueled, provided with a new crew, and resumed its journey to Chennai at 10:24 PM, landing safely around 11:15 PM.The incident, reported by multiple sources including Hindustan Times, Times of India, and India Today, underscored the challenges of air traffic management and fuel planning, particularly in high-traffic airspace. Both pilots were de-rostered pending a Directorate General of Civil Aviation (DGCA) investigation, as is standard procedure following such incidents. IndiGo has not issued an official statement, though a spokesperson clarified to The New Indian Express that the Mayday call was fuel-related and not indicative of a broader emergency.
Timeline of Events
4:40 PM: IndiGo flight 6E-6764 departs Guwahati for Chennai with 168 passengers.
7:45 PM: The aircraft attempts to land at Chennai but aborts due to an unstabilized approach and congestion, initiating a go-around.
7:50 PM: After circling Chennai airspace, the pilot decides to divert to Bengaluru due to inability to land.
7:40 PM (approx.): Approximately 35 nautical miles from Bengaluru, the pilot issues a ‘Fuel Mayday’ call, signaling critically low fuel.
8:15 PM: The aircraft lands safely at Kempegowda International Airport in Bengaluru.
8:15–10:24 PM: Passengers are deplaned, provided refreshments, and the aircraft is refueled with a new crew assigned.
10:24 PM: The flight departs Bengaluru for Chennai.
11:15 PM: The aircraft lands safely in Chennai.
Causes of the DiversionThe primary cause of the diversion was heavy air traffic congestion at Chennai International Airport, which delayed the flight’s landing. Sources indicate that the aircraft circled in holding patterns over Chennai, consuming significant fuel reserves. This prolonged holding, combined with the decision to divert to Bengaluru, led to critically low fuel levels. The Times of India reported that the flight may not have carried sufficient diversion fuel—the minimum required to safely reach an alternate airport if landing at the intended destination is not possible.A passenger quoted by TOI described the aircraft’s sudden and steep climb during the go-around in Chennai as unnerving, leaving many “on the edge of their seats.” The pilot’s decision to divert to Bengaluru, rather than attempt a second landing in Chennai, was likely influenced by the unstabilized approach and dwindling fuel reserves. The ‘Fuel Mayday’ call, issued 35 minutes before landing, ensured priority clearance at KIA, where emergency protocols were swiftly activated, including the mobilization of fire and medical services.
Some sources, such as Archyde, suggested adverse weather conditions over Chennai as a contributing factor, though most reports emphasized congestion as the primary issue. The discrepancy highlights the need for a comprehensive DGCA investigation to clarify the exact circumstances, including weather, fuel planning, and ATC coordination.
Passenger Experience
The 168 passengers aboard flight 6E-6764 experienced a tense ordeal, particularly during the go-around in Chennai and the subsequent diversion. The sudden climb after the aborted landing caused anxiety, with one passenger noting the “steep approach” that left many unsettled. However, the pilot’s communication and the safe landing in Bengaluru alleviated concerns, and no injuries were reported.
Upon landing at KIA, passengers were deplaned and provided refreshments during the two-hour stopover while the aircraft was refueled and a new crew was assigned. IndiGo’s spokesperson assured that passenger safety was never compromised, and the provision of refreshments suggests efforts to mitigate inconvenience. The flight’s resumption to Chennai at 10:24 PM allowed passengers to reach their destination with a delay of approximately three hours.
The incident’s timing, just days after a tragic Air India crash in Ahmedabad that killed over 270 people, likely amplified passenger unease. Social media posts on X reflected public concern, with some users speculating about aviation safety in India, though others praised the pilot’s professionalism in handling the emergency.
Aviation Safety ContextThe IndiGo incident occurred against the backdrop of heightened scrutiny of Indian aviation following the Air India Boeing 787 Dreamliner crash in Ahmedabad on June 12, 2025, which killed 241 passengers and crew and 29 people on the ground. The crash, also preceded by a Mayday call, intensified public and regulatory focus on safety protocols, fuel management, and ATC efficiency. While no connection exists between the two incidents, the proximity raised concerns, as noted by sources in Live India and OrissaPOST.
On June 20, 2025, another IndiGo flight from Chennai to Madurai returned to Chennai after a mid-air technical fault, carrying 68 passengers. The safe landing underscored the robustness of emergency procedures but added to the narrative of recent aviation incidents. Additionally, an IndiGo flight from Delhi to Leh returned to Delhi on June 19 due to technical issues, and another from Delhi to Srinagar was diverted to Chandigarh due to bad weather, highlighting a string of disruptions.The ‘Mayday’ call, derived from the French “m’aider” (help me), is a globally recognized distress signal reserved for life-threatening emergencies, such as low fuel, system failures, or imminent crashes. Governed by International Civil Aviation Organization (ICAO) protocols, it requires pilots to clearly state the emergency, location, and assistance needed. Misuse is a criminal offense, underscoring its gravity. The less severe ‘Pan-Pan’ signal is used for non-life-threatening issues, but the IndiGo pilot’s Mayday call reflected the critical fuel situation.
Regulatory and Operational Response
Following the emergency landing, both pilots were de-rostered, a standard procedure to allow for rest and investigation. The DGCA was informed, and a formal inquiry is underway to examine fuel planning, ATC coordination, and the decision-making process. Sources suggest the flight may have lacked adequate diversion fuel, a critical safety requirement, which could lead to penalties or revised protocols if confirmed.
Bengaluru’s ATC responded swiftly, granting priority landing and activating emergency services, including fire trucks and medical teams, which were on standby as the aircraft touched down. The efficient response ensured a safe outcome, as noted by India Today and The Hindu. The crew change in Bengaluru before the flight’s resumption to Chennai complied with safety regulations, ensuring rested pilots for the final leg.
IndiGo’s silence on the matter, as reported by multiple outlets, has drawn criticism, with passengers and analysts calling for transparency. The airline’s spokesperson, Rashmi, told IANS that no official statement was issued, but clarified to The New Indian Express that the Mayday was fuel-related, not an emergency in the broader sense. This distinction may mitigate public alarm but underscores the need for clear communication during such incidents.
Broader Implications
The incident highlights several critical issues in Indian aviation:
Air Traffic Congestion: Chennai’s congested airspace, a recurring issue at major Indian airports, delayed the landing, forcing prolonged holding patterns. Enhanced ATC capacity and coordination are essential to prevent similar incidents.
Fuel Planning: The potential lack of sufficient diversion fuel raises questions about pre-flight calculations and adherence to ICAO standards. Airlines must ensure robust fuel policies to account for unexpected delays or diversions.
Passenger Communication: While the pilot’s handling was professional, clearer in-flight updates could reduce passenger anxiety during emergencies. IndiGo’s post-incident silence further eroded trust.
Regulatory Oversight: The DGCA’s investigation must address systemic issues, including fuel management, ATC efficiency, and airline accountability. Recent incidents suggest a need for stricter audits and enforcement.
The incident also underscores the professionalism of pilots and ATC in averting disaster. The safe landing, despite critical fuel levels, reflects rigorous training and adherence to emergency protocols. However, the frequency of diversions and technical issues in recent weeks—Delhi-Leh, Delhi-Srinagar, Chennai-Madurai—calls for a comprehensive review of operational resilience.
Public and Media Reaction
Media coverage, including Hindustan Times, Times of India, and NDTV, emphasized the scare’s severity, linking it to the Ahmedabad crash for context. Social media posts on X ranged from alarmist speculation to praise for the pilot’s composure. For instance, @IndiaToday reported the diversion promptly, while @Indian_Analyzer’s post humorously dismissed political conspiracies, reflecting mixed sentiments. The hashtag #IndiGo trended briefly, amplifying public interest.
Passengers’ accounts, particularly the TOI report of a “steep climb,” humanized the ordeal, highlighting the emotional toll of such incidents. The DGCA’s swift action in de-rostering pilots and launching an investigation was noted positively, though calls for IndiGo’s official response persisted across platforms.
What’s Next?
The DGCA investigation will determine whether fuel planning errors, ATC delays, or other factors were primarily responsible. Potential outcomes include revised fuel policies, enhanced ATC training, or sanctions for IndiGo if lapses are found. The airline may face pressure to issue a public statement to restore confidence, particularly given its silence thus far.
For passengers, the incident reinforces the importance of robust safety measures but may heighten anxiety amid recent aviation incidents. Chennai and Bengaluru airports, key hubs, must address congestion issues to prevent future diversions. The aviation industry, already under scrutiny post-Ahmedabad, faces a critical moment to demonstrate resilience and transparency.
Comments
Post a Comment