SpiceJet and Air India Express flights faced delays of up to 14 hours today, with services from Kochi, Jaipur and Amritsar among those affected, following a wider wave of Asian aviation disruption earlier in the week.
A delay of 12 to 14 hours on a single-leg domestic route is rarely explained by anything happening on that specific flight. Aircraft, in a tightly scheduled airline network, fly multiple legs a day — a delay on an early rotation cascades forward through every subsequent flight that same tail number was assigned to.
That’s why airlines rarely offer a single clean explanation for delays of this magnitude: by the time a 6pm departure is 12 hours late, the actual root cause may have occurred on a completely different route, on a different aircraft, many hours earlier in the day.
The timing here compounds the effect — this disruption follows directly on the heels of the September 11-12 regional wave that delayed 4,804 flights and cancelled 206 across Asia, meaning today’s schedules were likely still absorbing a backlog rather than starting from a clean slate.
For any operation running tightly coupled, sequential scheduling — airlines, logistics, manufacturing lines — the lesson is the same: recovery time after a disruption often exceeds the disruption itself, because the system needs slack to re-synchronize, and that slack doesn’t exist by default in a schedule optimized for utilization.
The Bengaluru–Vijayawada Air India route has also seen recent delay reports, adding to a pattern of disruption across the carrier’s domestic network this month.
Ground handling and crew scheduling pressures have been cited in some recent Indian aviation disruptions, though airlines have not confirmed this as a specific cause for Saturday’s delays.
Passengers travelling on affected routes were advised to check their flight status directly with airlines given the scale and unpredictability of the ongoing disruptions.
SpiceJet aircraft landing in New Delhi, Wikimedia Commons, CC BY-SA 3.0