IndiGo has issued ₹827 crore in refunds to passengers affected by mass flight cancellations between november 21 and december 7.

The disruption impacted over 5.8 lakh passengers, making it one of the biggest operational breakdowns in India’s aviation sector.

Out of 9,000 misplaced bags, the airline has so far returned 4,500, and expects the remaining baggage to be delivered within 36 hours.

The government has stated that it will take “exemplary action” against indigo once the inquiry into the crisis concludes.

🔹 Cause of the Breakdown

The Civil Aviation Ministry confirmed that the meltdown was triggered by an internal systems failure within IndiGo.

Civil Aviation minister Ram Mohan Naidu clarified that the regulatory framework was not responsible for the crisis.

The ministry asserted that indigo alone is accountable, as the failure originated from the airline’s own processes and controls.

🔹 Government’s Position and Market Concerns

Minister Naidu highlighted IndiGo’s dominance of over 60% of India’s aviation market.

The government expressed a desire for more airlines and greater competition to avoid overdependence on a single carrier.

After the inquiry, the government aims to take measures that “set an example for all airlines” in terms of accountability.

🔹 Scale of the Disruption

The situation worsened on monday when nearly 500 indigo flights were cancelled, marking the seventh consecutive day of operational instability.

Passengers across major airports experienced long queues, cancellations, delays, and lost baggage.

🔹 Judicial & airport Advisory Developments

The supreme court declined an urgent hearing on petitions related to the crisis, noting that the Centre had already initiated corrective steps.

Delhi airport issued an advisory warning passengers of possible continued delays and urged them to check live flight updates before travelling.

IndiGo has stated that it hopes to fully restore operations by december 10, though delays are still occurring across its network.

Disclaimer:

The information contained in this article is for general informational purposes only. While we strive to ensure accuracy, we make no warranties or representations of any kind, express or implied, about the completeness, accuracy, reliability, suitability, or availability of the content. Any reliance you place on the information is strictly at your own risk. The views, opinions, or claims expressed in this article are those of the author and do not necessarily reflect the official policy or position of any organization mentioned. We disclaim any liability for any loss or damage arising directly or indirectly from the use of this article.