Hate speech: Jagadish Karanth granted interim bail hours after arrest

IndiGo, India’s largest airline, is battling one of its worst operational disruptions in recent years, with hundreds of delays and cancellations throwing domestic travel into chaos.

Government data on Tuesday showed its on-time performance plunging to 35%, an unusual dip for a carrier long associated with punctuality.

By Wednesday afternoon, airports in Delhi, Mumbai, Bengaluru and Hyderabad had collectively reported close to 200 cancellations, stranding travellers across the country.

Crew Shortage After New Duty Norms

A major trigger behind the meltdown is a severe crew shortage, especially among pilots, following the rollout of revised Flight Duty Time Limitation (FDTL) norms last month.

The rules mandate longer rest hours and more humane rosters — a shift IndiGo has struggled to incorporate across its vast network.

Sources said several flights were grounded due to lack of cabin crew, while some delays stretched upwards of eight hours.

With IndiGo controlling over 60% of India’s domestic aviation market, the ripple effect has impacted airports nationwide.

IndiGo Issues Apology, Lists “Compounding Factors”

In a statement, IndiGo acknowledged the large-scale disruption:

“We sincerely apologise to customers. A series of unforeseen operational challenges — technology glitches, winter schedule changes, adverse weather, system congestion and updated FDTL norms — created a compounding impact that could not have been anticipated.”

To stabilise operations, the airline has begun calibrated schedule adjustments for the next 48 hours, aiming to restore punctuality. Affected passengers are being offered refunds or alternate travel arrangements, IndiGo said.

What the FDTL Rules Require

The FDTL norms, designed to reduce pilot fatigue, cap duty and flying hours as follows:
•    Maximum 8 hours of flying per day
•    35 hours per week
•    125 hours per month
•    1,000 hours per year

Crew must also receive rest equalling twice the flight duration, with a minimum 10-hour rest period in any 24-hour window.

The DGCA introduced these limits to enhance flight safety.

Hyderabad: 33 Flights Cancelled, Long Queues Reported

Hyderabad’s Rajiv Gandhi International Airport saw heavy early-morning crowds as 33 IndiGo flights (arrivals and departures) were cancelled.

The airport clarified on X that operations were normal, advising passengers to contact IndiGo directly for latest flight status.

Cancellations included flights to and from Visakhapatnam, Goa, Ahmedabad, Delhi, Bengaluru, Chennai, Madurai, Hubli, Bhopal and Bhubaneswar.

Bengaluru: 42 Flights Disrupted

Bengaluru’s Kempegowda International Airport recorded 42 cancellations — 22 arrivals and 20 departures — affecting routes to Delhi, Mumbai, Chennai, Hyderabad, Goa, Kolkata and Lucknow.

Passengers Vent on Social Media

Irate travellers took to X to share their experiences. One passenger stranded in Hyderabad wrote: “I have been here since 3 a.m. and missed an important meeting.”

Another said: “My flight was pushed from 1:55 PM to 2:55 PM and now 4:35 PM. I was informed only three minutes before entering the airport.”

Delhi Airport Hit by Tech Glitch

At Delhi Airport, the disruption deepened due to a slowdown in the Amadeus system — used for reservations, check-ins and departure control.

The technical issue led to longer queues and sluggish processing, adding to delays already worsened by staff shortages.

Mangaluru: Chaos erupted at Mangaluru International Airport (MIA) after IndiGo flight 6E 5150, bound for Mumbai, was repeatedly delayed and ultimately cancelled, leaving around 100 passengers stranded overnight. The incident highlights the ongoing country-wide operational disruptions affecting the airline, largely due to the implementation of new Flight Duty Time Limitations (FDTL) norms for crew.

The flight was initially scheduled for 9:25 PM on Tuesday but was first postponed to 11:40 PM, then midnight, before being cancelled around 3:00 AM. Passengers expressed frustration over last-minute communication and the lack of clarity, with elderly and ailing travellers particularly affected. “Though the airline arranged food, there was no proper communication, leaving us confused,” said one family member.

An IndiGo executive at MIA cited the FDTL rules, designed to prevent pilot fatigue by limiting crew working hours, as the cause of the cancellation. While alternative arrangements, including hotel stays, were offered, about 100 passengers chose to remain at the airport, creating tension. A replacement flight was arranged but also faced delays due to the same constraints, finally departing for Mumbai around 1:45 PM on Wednesday. Passengers either flew, requested refunds, or postponed their travel.

The Mangaluru delay is part of a broader crisis for IndiGo. The airline has been forced to make “calibrated schedule adjustments”—a euphemism for widespread cancellations and delays—after stricter FDTL norms came into effect on November 1.

While an IndiGo spokesperson acknowledged unavoidable flight disruptions due to technology issues, operational requirements, and the updated crew rostering rules, the DGCA has intervened, summoning senior airline officials to explain the chaos and outline corrective measures.

The ripple effect has been felt across the country, with major hubs like Bengaluru and Mumbai reporting numerous cancellations. The Mangaluru incident underscores the systemic operational strain currently confronting India’s largest carrier, leaving passengers nationwide grappling with uncertainty and delays.

Congress president Mallikarjun Kharge on Thursday announced that he will convene a high-level meeting in New Delhi with senior leaders — including Rahul Gandhi, Karnataka Chief Minister Siddaramaiah and Deputy Chief Minister D.K. Shivakumar — to resolve the escalating leadership turmoil in Karnataka and “put an end to the confusion.”

Kharge said the discussions would focus on the way forward for the ruling party, as rumours of a possible leadership change continue to swirl. The speculation has intensified after the Congress government crossed the halfway mark of its five-year term on November 20, reviving talk of an alleged 2023 “power-sharing agreement” between Siddaramaiah and Shivakumar.

“After reaching Delhi, I will call three or four important leaders and hold discussions. Once we talk, we will decide how to move ahead and end this confusion,” Kharge told reporters in Bengaluru, according to PTI.

When asked specifically about calling Siddaramaiah and Shivakumar to Delhi, he responded: “Certainly, we should call them. We will discuss with them and settle the issue.”

He confirmed that Rahul Gandhi, the Chief Minister, the Deputy Chief Minister and other senior members would be part of the deliberations. “After discussing with everyone, a decision will be made,” he said.

Meanwhile, Siddaramaiah held a separate strategy meeting at his Bengaluru residence with ministers and leaders seen as his close confidants, including G. Parameshwara, Satish Jarkiholi, H.C. Mahadevappa, K. Venkatesh and K.N. Rajanna.
Signalling calm, the Chief Minister told reporters, “Will go to Delhi if the high command calls.”

Shivakumar echoed a similar stance, saying he too would head to the national capital if summoned by the party leadership.