Flight Disruptions Trigger Chaos at Mumbai Airport Terminal 1 as SpiceJet Services Delayed, Cancelled

Scenes of disruption unfolded at Mumbai Airport Terminal 1 after multiple flights operated by SpiceJet were delayed or cancelled, leaving hundreds of passengers stranded overnight and prompting protests inside the terminal.

Overnight Ordeal for Passengers

A large number of travellers were forced to spend the night at the airport amid prolonged delays and last-minute cancellations. What was expected to be routine travel turned into a stressful experience, with many passengers left without clear information on revised departure schedules or alternative arrangements.

Among the worst affected was a late-night Mumbai–Bengaluru service, which departed nearly nine hours behind schedule. Passengers for a red-eye flight scheduled at 1:55 am had arrived at the airport around midnight, only to face repeated delays before finally departing later in the morning.

Similarly, a Mumbai–Delhi flight scheduled for 11:15 pm was delayed for several hours before being cancelled altogether. A daytime Mumbai–Gorakhpur flight was also scrapped, while a Mumbai–Ahmedabad service experienced a delay of approximately three hours before eventual departure.

Passenger Frustration Mounts

Frustration among passengers spilled over onto social media, with many sharing accounts of long waits, lack of communication, and limited assistance. Some travellers reported waiting at the airport since midnight as departure times were repeatedly pushed back, while others described heated exchanges between passengers and airline staff.

In one instance, a passenger claimed she had to spend nearly ₹15,000 on an alternative ticket after her flight was cancelled following hours of delay, citing inadequate support from the airline.

Operational Issues Behind Disruptions

According to airline officials, the disruptions were initially linked to technical issues. However, in a formal statement, SpiceJet clarified that three flights—Mumbai–Delhi, Mumbai–Gorakhpur, and Mumbai–Bengaluru—were cancelled on April 29 due to a combination of operational challenges.

These included the grounding of an aircraft, adverse weather conditions at Bagdogra (the previous station of the operating aircraft), and crew duty limitations under Flight Duty Time Limitation (FDTL) norms. Additionally, delays affecting two Mumbai–Ahmedabad flights were attributed to unfavourable weather conditions at earlier stations, including Varanasi and Bagdogra.

Security Intervention and Recovery Measures

As tensions escalated within the terminal, personnel from the Central Industrial Security Force intervened to manage the situation and restore order.

In response to the disruptions, SpiceJet announced that additional flights were being operated to accommodate affected passengers and clear the backlog. The airline expressed regret for the inconvenience caused and thanked passengers for their patience.

By Thursday morning, operations at the airport had largely stabilised, with flight schedules returning to normal. However, the incident has once again raised concerns over airline reliability, passenger communication, and crisis management during large-scale disruptions.