IndiGo Mumbai Flight From Varanasi Delayed 3.5 Hours After Pilot Reports Sick

Mumbai-bound IndiGo flight 6E-6544 from Lal Bahadur Shastri International Airport, Varanasi, was delayed by about three and a half hours on Thursday, 10 September 2026, before it eventually operated, according to airport and airline accounts that reached this desk. Airport Director Puneet Gupta described the hold-up in technical terms and said there had been no passenger ruckus at the terminal. Airline sources separately said the scheduled pilot reported sick and that a replacement crew member was brought in from Ahmedabad because Varanasi is not a crew base for the carrier.

Both explanations are on the record for this pack. The airport director’s technical framing and denial of disorder address what passengers saw airside and in the departure hall. The airline’s pilot-sick and Ahmedabad-replacement line explains the crew gap that stretched the delay into multi-hour territory. This desk is not choosing one narrative over the other; it is reporting the attributed statements side by side.

A three-and-a-half-hour delay on a domestic trunk sector is long enough to trigger refreshment protocols. Airline sources said refreshments were served to waiting passengers while the replacement arrangement was completed. That detail matters for travellers who spent the afternoon in the terminal, but it does not by itself confirm or deny either the technical or the medical explanation.

Varanasi’s LBSI Airport handles a busy mix of pilgrim, tourist and connecting traffic. When a Mumbai departure slips by hours, onward connections and hotel plans break. Gupta’s statement that the flight later operated closes the operational loop for Thursday’s board: the aircraft left, passengers were not stranded overnight at Varanasi on this service, and the airport rejects any claim of a terminal disturbance tied to the delay.

Crew basing is the quiet constraint behind the Ahmedabad hop. If the scheduled pilot goes sick at an outstation that does not hold spare IndiGo crew, the airline must ferry a replacement from a base city. That logistics chain — positioning a pilot, duty-time checks, and release — routinely consumes hours even when the aircraft and airfield are ready.

Passengers measure delays in missed meetings and missed trains at the far end. Aviation desks measure them in attributed causes and whether the flight eventually departed. On Thursday’s 6E-6544 file, the attributed causes are technical reasons per Airport Director Puneet Gupta and a sick pilot plus Ahmedabad replacement per airline sources, with refreshments served and no ruckus acknowledged by the airport.

Until the Directorate General of Civil Aviation or the airline publishes a formal delay code beyond those statements, the locked Varanasi airport story is straightforward: IndiGo 6E-6544 to Mumbai left about three and a half hours late on 10 September after a crew/technical disruption that the airport and airline described in their own words, and the service did operate once the replacement arrangement was in place.