SpiceJet check-in disruption delays Delhi flights, passengers stranded

SpiceJet passengers reported long waits and missed departure times at New Delhi’s Indira Gandhi International Airport after a check-in disruption slowed processing at the airline’s counters, delaying several domestic services and at least one international flight and leaving many travelers stranded inside the terminal.

What happened at Delhi airport and when

Published coverage describes the disruption unfolding early Saturday, September 19, 2026, when SpiceJet check-in operations at Delhi airport were slowed significantly, creating crowding around counters and uncertainty for passengers trying to confirm status updates, baggage acceptance, and rebooking options.

Multiple reports place the most acute issues at Terminal 1 in the early morning hours, when passengers bound for Leh and Jammu were affected. Coverage indicates that some travelers reached the terminal expecting routine check-in but instead encountered delays that pushed flights back by hours.

Delhi airport’s operator also posted public updates acknowledging an operational disruption affecting some SpiceJet flights and indicating that airport teams were coordinating with the airline and other stakeholders to assist affected passengers and help normalize the situation.

Flights and routes affected: Leh, Jammu, and Dubai

Reports indicate more than 500 passengers were impacted across at least four domestic flights and one international flight, with services to Leh and Jammu among those delayed. Flight numbers cited in coverage include SG127 and SG121 on the Delhi–Leh route and SG2160 on the Delhi–Jammu route.

In one widely reported example, SpiceJet flight SG127 from Delhi to Leh, scheduled to depart at 4:50 a.m., was reported to have departed around 9:00 a.m., a delay of more than four hours. Coverage also noted other Leh services, including SG121 (scheduled 6:10 a.m.) and SG125 (scheduled 8:45 a.m.), as being affected.

The disruption was not limited to domestic routes. Published flight-tracking references cited in coverage indicated SpiceJet’s Delhi–Dubai service SG5111, scheduled for 7:45 a.m. from Terminal 3, also departed later than planned, with reports placing takeoff at about 9:42 a.m.

Competing explanations: staffing absence and “operational reasons”

Accounts of the root cause varied across outlets. Some reporting linked the immediate check-in disruption to staff not reporting for duty during the early-morning window at Terminal 1, which would have slowed baggage acceptance and passenger processing and contributed to queues inside the terminal.

Separate coverage raised broader labor and payment concerns, framing the disruption as connected to staff availability and workplace issues. Those reports described passengers arriving to find counters without personnel present and operations resuming only after intervention by senior management and airport authorities.

SpiceJet’s public response, as carried in multiple reports, described the delays to SG121, SG127, and SG2160 as stemming from “operational reasons,” while also stating that the flights later departed and landed at their destinations and expressing regret for the inconvenience.

A turbulent week: Dubai delays and heightened passenger frustration

The September 19 disruption landed amid heightened attention on SpiceJet’s reliability after other high-profile delays earlier in the week. Reports from September 15 and 16 described two Delhi–Dubai services, SG5111 and SG5105, running more than 24 hours late, with passengers staging sit-in protests at the airport while seeking clearer updates, food, and accommodation support.

In that earlier incident, coverage attributed the extreme delays to operational constraints tied to an aircraft being grounded, with additional reporting noting that airport staff provided basic assistance such as food and water while travelers waited for onward arrangements.

Together, the back-to-back disruptions amplified passenger stress at one of India’s busiest hubs, particularly for routes with time-sensitive connections or onward travel plans, such as travelers continuing to Ladakh or those holding international itineraries from Dubai.

What stranded passengers can do next at IGI

For travelers caught in a check-in disruption, the most practical first step is to verify the correct terminal and counter location and then confirm flight status through the airline’s official channels and the airport’s live flight information displays inside the terminal. When check-in counters are congested, passengers without checked baggage may still need to confirm whether boarding passes can be issued and whether baggage cut-off times are being extended.

Passengers who miss a departure due to a long check-in queue often need documentation showing the delay or disruption for insurance and reimbursement claims. Reports around the Delhi incident indicated airport teams were involved in on-ground coordination, and travelers typically benefit from keeping screenshots of status changes, photos of updated departure boards, and any written rebooking details issued at the counter.

India’s passenger-protection rules can require airlines to provide certain facilities in cases of significant delays or cancellations, depending on the length of the delay, the stage of the journey, and the specific circumstances. Travelers affected on September 19 may need to preserve receipts and rebooking paperwork and then follow the airline’s published claims process once travel is completed.