An IndiGo ATR 72 bound for Diu aborted takeoff at Ahmedabad’s Sardar Vallabhbhai Patel International Airport after the cockpit indicated an engine fire warning. The alert emerged during the takeoff roll, prompting pilots to reject takeoff and taxi the aircraft back to the stand. All 60 passengers and crew disembarked safely, with no injuries reported.
Flight 6E‑7966, scheduled for departure around 11 AM, had already begun its rollout when the warning appeared. The pilots promptly informed air traffic control and halted the aircraft well below decision speed. Standard safety protocols were followed, ensuring a swift and orderly evacuation.
IndiGo stated the affected ATR 72‑600 displayed a “technical snag” and will undergo comprehensive inspections and maintenance before it returns to service. Passengers were offered refreshments, rebooking options, or refunds to minimise inconvenience.
The Directorate General of Civil Aviation has opened an inquiry into the incident, which occurs against a backdrop of heightened scrutiny following the June crash of Air India flight AI 171 in Ahmedabad. That tragedy, which claimed 260 lives, has led to increased regulatory oversight of commercial Indian carriers and heightened attention to aircraft safety protocols.
This is the third high-profile technical issue affecting IndiGo in July. On July 17, flight 6E‑5118 from Delhi to Imphal returned mid‑air shortly after takeoff due to “a technical snag,” later identified as minor. On July 22, another service experienced engine failure diverting it en route to Goa. All were resolved without injury, but the pattern has raised questions about maintenance resilience amid fleet utilisation pressures.
Industry analysts note that ATR models often operate in demanding regional environments, raising maintenance and aging‑aircraft concerns. Safety experts emphasise that prompt crew action, as seen in this case, is key, but root‑cause analysis remains crucial. Should recurring engine alerts stem from systemic faults—such as sensor malfunctions or component wear—it may trigger broader inspections or revisions to flight‑deck procedures.
Passengers praised the cabin crew and flight deck for their composure and professionalism. One flyer told local press that the deplaning was “calm and efficient, despite the tense moment when the warning light came on.” Crew training, especially for rejected takeoff scenarios, is designed to ensure safety during low‑speed emergencies. The aircraft was brought to a halt safely, and evacuees reported no cause for panic.
IndiGo operates one of India’s largest turboprop fleets, using ATR 72‑600s primarily on short domestic routes. The carrier has maintained that these incidents are isolated and unconnected, adding that routine checks will reaffirm airworthiness. Meanwhile, the DGCA is closely monitoring follow‑up actions and awaiting technical reports to ensure transparency and uphold confidence in aviation safety.
The aborted takeoff underlines the importance of infrastructure and regulatory vigilance, especially in the wake of high-magnitude accidents. Pilots’ response to this event demonstrates effective crisis protocol. Still, aviation authorities, operators, and manufacturers now face renewed impetus to examine performance trends and potential systemic risks across regional fleets.
