Emergency Landing: IndiGo Delhi–Goa Flight Diverted to Mumbai Today

On the evening of July 16, 2025, IndiGo flight 6E 6271—an Airbus A320neo—departed from Delhi’s Indira Gandhi International Airport bound for Goa’s Mopa Airport. Roughly an hour into the flight, en route over the Bay of Bengal, the aircraft encountered a technical malfunction and was forced to divert to Mumbai, issuing a “PAN PAN PAN” emergency alert. This incident underscores aviation safety protocols, crew professionalism, and airline responsiveness. Here’s a detailed breakdown of what happened, why it matters, and what passengers need to know.

What Happened: Flight Diversion & Engine Snag

1. Takeoff: Flight 6E 6271 departed Delhi at ~8:02 PM IST, carrying 191 passengers and crew. 

2. Mid‑flight snag: Over the coastline near Bhubaneswar (~100 nautical miles), pilots detected an engine malfunction in engine No. 1 and issued “PAN PAN PAN”—an urgency signal—but below “Mayday” level.

3. Diversion to Mumbai: Standard procedures were followed; Mumbai’s CSMIA declared a full emergency at 9:35 PM, readying fire and rescue teams. 

4. Safe landing: The A320neo landed at 9:52–9:53 PM without incident. Emergency status was lifted at ~9:57 PM IST. 

5. Aftermath & passenger care: No injuries were reported. IndiGo arranged an alternative aircraft to continue journeys to Goa, and the diverted plane is undergoing thorough inspections. 

Aviation Terms Explained

Why It Matters

• Redundancy in aviation systems
  Airbus twin-engine aircraft are designed to fly safely even if one engine fails—this incident demonstrates that fail-safe design works under pressure.

• Crew training & clear communication
  The pilot’s swift “PAN PAN PAN” call allowed ground teams to mobilize quickly, displaying exemplary coordination.

• Regulatory oversight
  The DGCA (Directorate General of Civil Aviation) will investigate the root cause, ensuring technical protocols are followed and safety reinforced.

Sequence of Events: Timeline of Flight 6E 6271

• 8:02 PM – Flight departs Delhi. 

• 9:27 PM – Crew detects engine issue and declares “PAN PAN PAN”. 

• 9:32 PM – Requests diversion to Mumbai. Rescue services activated. 

• 9:35 PM – Mumbai Airport declares full emergency. 

• 9:52–9:53 PM – Flight lands smoothly.

• 9:57 PM – Emergency declared over; disembarkation begins.

Takeaways – Passenger Safety First

• Passengers remained safe
  All on board were unharmed, thanks to rigorous crew protocols and airport emergency services.

• Alternative travel arranged
  IndiGo promptly provided replacement aircraft for affected passengers, minimizing delays.

• Engineering checks in progress
  The aircraft is undergoing a full technical inspection before returning to service.

• Proactive industry response
  This comes just months after other incidents (e.g., bird strike at Patna, go-around at Patna, dual flameouts), prompting airlines to tighten safety measures.

Passenger Advisory & Next Steps

• Flight updates: Monitor booking portals and IndiGo’s official updates (e.g. X/Twitter) for your flight status.

• Weather watch: Delhi flights may still face delays due to heavy rain and gusty winds—airlines have issued advisories urging early airport arrival.

• Safety trust: Reassuringly, such incidents remain rare; aviation professionals undergo rigorous training and procedures.

Final Thoughts

This incident involving Delhi → Goa flight 6E 6271 underscores:

• The resilience of modern aircraft systems

• The efficiency of emergency protocols (PAN alerts, airport readiness)

• The industry’s commitment to passenger safety and contingency planning

While the engine failure was concerning, the smooth handling of the situation reflects well on IndiGo, IGIA, and CSMIA emergency teams. For affected travellers, the airline’s quick arrangements provided relief and continuity.