{"id":151696,"date":"2026-07-27T19:04:29","date_gmt":"2026-07-27T13:34:29","guid":{"rendered":"https:\/\/aviationa2z.com\/?p=151696"},"modified":"2026-07-27T19:04:33","modified_gmt":"2026-07-27T13:34:33","slug":"indigo-dubai-mumbai-flight-emergency-landing-at-rajkot","status":"publish","type":"post","link":"https:\/\/aviationa2z.com\/index.php\/2026\/07\/27\/indigo-dubai-mumbai-flight-emergency-landing-at-rajkot\/","title":{"rendered":"IndiGo Dubai to Mumbai Flight with A321neo Makes Emergency Landing at Rajkot"},"content":{"rendered":"\n

RAJKOT-<\/strong> An IndiGo (6E)<\/a> flight from Dubai International Airport (DXB) to Mumbai’s Chhatrapati Shivaji Maharaj International Airport (BOM) made a precautionary emergency landing at Hirasar International Airport (HSR) in Rajkot after a suspected cargo hold smoke indication.<\/p>\n\n\n\n

The Airbus A321 landed safely in Rajkot, where emergency services were already on standby. All 187 passengers and seven crew members evacuated the aircraft safely, and no injuries or firefighting intervention were required.<\/p>\n\n\n\n

\"IndiGo
Photo: Mumbai Planes | Siddh Dhuri<\/figcaption><\/figure>\n\n\n\n

IndiGo Flight Emergency Landing at Rajkot<\/h2>\n\n\n\n

IndiGo (6E) Flight 1452 departed Dubai International Airport (DXB) at approximately 11:30 a.m. IST on Monday for Mumbai’s Chhatrapati Shivaji Maharaj International Airport (BOM). During the flight, the crew reportedly detected a smoke indication from the aircraft’s cargo hold.<\/p>\n\n\n\n

Following standard aviation safety procedures, the flight crew decided to divert the Airbus A321 to the nearest suitable airport. The aircraft was redirected to Hirasar International Airport (HSR) in Rajkot, Gujarat, as a precautionary measure.<\/p>\n\n\n\n

The aircraft landed safely at 3:27 p.m. local time.<\/p>\n\n\n\n

Airport authorities immediately activated emergency response protocols. Police personnel, airport security teams, and firefighters were positioned along the runway before the aircraft arrived to ensure a rapid response if required.<\/p>\n\n\n\n

\"IndiGo
Photo: avgeekwithlens\/ Harsh Tekriwal<\/figcaption><\/figure>\n\n\n\n

Passengers and Crew Safe After Landing<\/h3>\n\n\n\n

According to police officials, all 187 passengers and seven crew members safely disembarked after the aircraft came to a stop.<\/p>\n\n\n\n

Authorities stated that no fire or other hazardous situation was found after landing. As a result, firefighting crews were not required to intervene.<\/p>\n\n\n\n

Officials described the diversion as a precautionary landing prompted by a suspected smoke indication rather than a confirmed onboard fire.<\/p>\n\n\n\n

Such precautionary diversions are standard practice in commercial aviation whenever cockpit indications suggest the possibility of smoke or fire. Flight crews are trained to prioritize passenger safety by landing at the nearest suitable airport whenever such warnings occur.<\/p>\n\n\n\n

\"IndiGo
Photo: Siddh Dhuri | MumbaiPlanes<\/figcaption><\/figure>\n\n\n\n

Replacement Aircraft Arranged for Mumbai Passengers<\/h3>\n\n\n\n

Airport sources said IndiGo was arranging another aircraft to transport the stranded passengers from Rajkot to Mumbai.<\/p>\n\n\n\n

The airline worked with airport authorities to assist passengers following the diversion while operational teams inspected the Airbus A321 to determine the cause of the reported cargo hold smoke indication.<\/p>\n\n\n\n

The aircraft will likely undergo a detailed technical inspection before it is cleared to return to commercial service.<\/p>\n\n\n\n

Emergency Diversions Remain Standard Safety Procedure<\/h4>\n\n\n\n

Smoke warnings, whether confirmed or suspected, are treated as high-priority events in aviation because they can indicate electrical faults, overheating equipment, or other technical issues that require immediate assessment.<\/p>\n\n\n\n

Airlines follow established international safety procedures that require flight crews to land at the nearest suitable airport whenever there is uncertainty about onboard smoke or fire.<\/p>\n\n\n\n

In this case, the diversion to Rajkot allowed emergency personnel to inspect the aircraft quickly while ensuring the safety of everyone on board.<\/p>\n\n\n\n

\"IndiGo
Photo: avgeekwithlens\/ Harsh Tekriwal<\/figcaption><\/figure>\n\n\n\n

Similar Emergency Landing<\/h2>\n\n\n\n

IndiGo (6E)<\/strong> flight 6E579 from Visakhapatnam Airport (VTZ)<\/strong> to Delhi Airport (DEL)<\/strong> declared an emergency on approach to the national capital after the crew reported a suspected engine failure. The aircraft landed safely, and no injuries were reported.<\/p>\n\n\n\n

A full emergency was activated at Indira Gandhi International Airport (DEL)<\/strong> as airport and emergency services responded in line with standard aviation procedures. The Boeing 737-800 completed a safe landing, and all passengers and crew disembarked without incident.<\/p>\n\n\n\n

Emergency Response Activated at Delhi Airport<\/strong><\/h4>\n\n\n\n

A full emergency was declared at Indira Gandhi International Airport (DEL) at 10:39 AM IST on Saturday after IndiGo (6E) flight 6E579 reported a suspected engine failure while approaching Delhi.<\/p>\n\n\n\n

The flight was operating from Visakhapatnam Airport (VTZ) to Delhi Airport (DEL) with 160 passengers on board. Following the report from the flight crew, airport authorities immediately activated emergency protocols to ensure a safe arrival.<\/p>\n\n\n\n

The Civil Aviation Ministry confirmed that emergency procedures were initiated promptly. Despite the incident, normal airport operations continued, and there was no disruption to other scheduled flights.<\/p>\n\n\n\n

The Delhi Fire Service received the emergency alert at 10:53 AM and dispatched fire tenders to Runway 28 as a precaution. Emergency personnel remained in position while the aircraft completed its approach.<\/p>\n\n\n\n

According to Flightradar24 data, the aircraft landed safely at 10:59 AM IST, approximately 20 minutes after the emergency declaration. Authorities confirmed there were no injuries among passengers or crew, and no damage to the aircraft was reported during landing.<\/p>\n\n\n\n

\"corendon
Photo: avgeekwithlens\/ Harsh Tekriwal<\/figcaption><\/figure>\n\n\n\n

Aircraft Details and Technical Information<\/strong><\/h2>\n\n\n\n

Flight 6E579 was operated using a Boeing 737-800 leased from Corendon Airlines (XC)<\/strong>. The aircraft carries the registration TC-CON<\/strong> and is approximately 15.1 years old.<\/p>\n\n\n\n

The aircraft is powered by two CFM International CFM56-7B engines, one of the most widely used engine types on the Boeing 737 Next Generation family.<\/p>\n\n\n\n

Following the safe landing, the aircraft was moved for detailed technical inspection in accordance with established maintenance procedures before returning to service.<\/p>\n\n\n\n

IndiGo Confirms Technical Snag<\/h4>\n\n\n\n

IndiGo stated that a technical snag was detected shortly before landing on flight 6E579 operating from Visakhapatnam to Delhi on March 28, 2026.<\/p>\n\n\n\n

The airline said the pilots requested a priority landing as a precaution and followed all standard operating procedures. The aircraft landed safely at Indira Gandhi International Airport without further complications.<\/p>\n\n\n\n

According to the airline, all relevant aviation authorities were informed immediately after the incident. Engineers began the required inspections and maintenance checks once the aircraft reached the ground.<\/p>\n\n\n\n

IndiGo reiterated that passenger and crew safety remains its highest priority and emphasized that the crew followed established aviation safety procedures throughout the event.<\/p>\n\n\n\n

Stay tuned with us. Further, follow us on social media for the latest updates.<\/p>\n\n\n\n

Join us on\u00a0Telegram Group\u00a0<\/a>for the Latest Aviation Updates. Subsequently, follow us on\u00a0Google News<\/a><\/p>\n\n\n\n

\n
IndiGo Flight Evacuated After Smoke Alert as Passengers End Up on Aircraft Wing<\/a><\/blockquote>