Very recently, we wrote about the effect of the Middle East conflicts on IndiGo, whose tie-up with Norse Airways to operate IndiGo’s 787-9 flights to Europe was stalled for a week due to an EASA advisory. On Sunday, March 8, IndiGo restarted operations with a Mumbai-London Heathrow flight after a week without operating these flights.
IndiGo’s Flight to Nowhere
IndiGo’s fledgling long-haul operations encountered another dramatic disruption today when one of its Europe-bound flights ended up becoming a “flight to nowhere.”
IndiGo’s 6E33, scheduled to operate between Delhi and Manchester, departed as planned but was forced to turn back mid-air after airspace restrictions suddenly made the route unviable, eventually returning to its origin airport without even entering European airspace.
The incident occurred because Eritrea, of which I was unaware until now (pardon my geographical ignorance), did not allow IndiGo to cross its airspace. This happened because Eritrea’s ATC apparently got confused when a request was made with an IndiGo callsign; however, the plane registration was with Norse Atlantic Airways. Perhaps they did not keep up with the news or did not know how damp leases work. I wonder how Hi-Fly of Malta would make do if they had to.
Here is the text sent to the plane, courtesy AnalyticFlying.
Unfortunately, this meant the plane had to turn around, and, given that the Middle East Airspace is off-limits due to an EASA advisory at the moment, the airline had to fly the plane back to India and bring it back to Delhi.
And this was not the only time it happened; the Eritreans did it again when the London Heathrow-Mumbai flight diverted to Cairo because of the same kind of denial of their airspace.
Here is what IndiGo had to say about 6E33, which came back to Delhi.
Due to the evolving situation in and around the Middle East, some of our flights may take longer routes or experience diversions. Our flight 6E 033 operating from Delhi to Manchester had to return to its origin due to last-minute airspace restrictions, owing to the ongoing situation in West Asia. We are working with the relevant authorities to explore the possibilities of resuming the journey. As always, safety and security of our customers, crew and aircraft is of utmost importance to us.
The whole disruption is pretty unfortunate for the passengers and the airline, but the airline might also be on the hook for compensation to passengers under UK261, the English equivalent of EU261. This mostly works for the passengers of 6E2 who were on their way from London Heathrow to Mumbai, but not the ones on their way from Delhi to Manchester.
Bottomline
IndiGo faced two diversions today: one was a return to the origin of its Delhi – Manchester flight from halfway, and the other was a diversion to Cairo because Eritrea won’t grant permission for both flights to operate in its airspace. In both cases, the restriction apparently applied because the plane was a Norse Atlantic Airways aircraft and IndiGo was the one doing the paperwork, requesting the clearance under their own name.
What do you make of the impact of the conflicts on IndiGo’s Europe Strategy? Should they continue to try to reschedule or cancel these flights until the situation resolves itself?
Liked our articles and our efforts? Please pay an amount you are comfortable with; an amount you believe is the fair price for the content you have consumed. Please enter an amount in the box below and click on the button to pay; you can use Netbanking, Debit/Credit Cards, UPI, QR codes, or any Wallet to pay. Every contribution helps cover the cost of the content generated for your benefit.
(Important: to receive confirmation and details of your transaction, please enter a valid email address in the pop-up form that will appear after you click the ‘Pay Now’ button. For international transactions, use Paypal to process the transaction.)
We are not putting our articles behind any paywall where you are asked to pay before you read an article. We are asking you to pay after you have read the article if you are satisfied with the quality and our efforts.
UPDATE – on 6E2 LHR – BBI flight 08/03/2026 – which was diverted to Cairo airport.
The diversion of IndiGo flight 6E2 from London (LHR) to Mumbai (BOM) to Cairo (CAI) on Sunday, March 8, 2026, was quite a significant event, especially as it coincided with another IndiGo “flight to nowhere” (Delhi–Manchester) on the same day.
“While the aircraft had the necessary permits, authorities in Eritrea reportedly became confused because the flight was filed under IndiGo’s code (“iFly”) but operated by a Norse Atlantic aircraft. This led to a last-minute denial of entry into Eritrean airspace.”
This is not a vis major – whatever IndiGo will say. Actually, they cancel phone calls, and their ChatBot is totally incompetent. Indigo website tracking function – using the PNR code makes false statements. Indigo website says – the flight arrived in Mumbai on time.
NO! They are still all in Cairo – on Tuesday afternoon (10/03/2026)
Vis maior (or vis major) is a Latin term for “superior force,” referring to an irresistible, uncontrollable natural event—such as a hurricane, earthquake, or flood—that prevents parties from fulfilling legal or contractual obligations. Often called an “act of God,” this legal defense shields against liability for damages.
This was a technical permit confusion involving Eritrean airspace.
Fatal error! But nothing to do with ‘act of God’ or vis major.
We have more information and photos, videos about what is STILL GOING ON in Cairo.
Yes, the Indigo flight IGO75E 6E2 B789 (operated by Norse), which departed from LHR almost 30 hours later than Sunday’s flight (IndiGo 6E2 LHR – BBI), is actually in ERITREA airspace, and it will arrive at the Mumbai airport earlier than the Sunday flight.
Is this clear? People who left London on Sunday are still sitting in Cairo. 300+ passengers.
Lucky ones – leaving LHR on Monday night, they will get to Mumbai before the 300 others.
What is the CLEAR PROOF – it was an “erroneous human decision”?
They did not change the plane; they did not change the route; they did get new permits.
The only TRICK – they changed the flight name from IndiGo – to NORSE.
Problem solved.
So this is not about war, nothing to do with geopolitical tensions.
It was confusion, administrative error, illiteracy, or incompetent staff.
GREAT JOB INDIGO – GREAT JOB ERITREA.
People should all Submit the Claim to IndiGo.
Since your flight (6E2) departed from London Heathrow (LHR), you are protected under UK261 (the UK version of the EU261 regulation). Because the delay to your final destination (Mumbai) exceeded 4 hours and the distance is over 3,500 km, you
Here is how to start your case:
1. Gather Your Evidence
Before contacting the airline, collect these details to ensure they can’t dismiss the claim easily:
Boarding Pass/Booking Reference (PNR): Essential for identification.
Proof of Delay: Photos of the departure boards in Cairo or a screenshot of the flight status (showing the arrival time in Mumbai was ~24+ hours late).
Expense Receipts: If you paid for your own meals, water, or transport in Cairo because IndiGo didn’t provide them, keep those receipts. You are entitled to reimbursement for “duty of care” expenses regardless of the reason for the delay.
2. Submit the Claim to IndiGo
You must first give the airline a chance to resolve the claim.
Official Portal: Visit the IndiGo Compensation Page.
Direct Emails: Since this involves a UK departure and a leased Norse Atlantic aircraft, cc these specific addresses to ensure it reaches the right legal department:
Nodal Officer: NodalOfficer@goindigo.in
Customer Experience: customer.experience@goindigo.in
What to say: “I am claiming compensation under UK Regulation 261/2004 for flight 6E2 on March 8, 2026, from LHR to BOM. The arrival delay exceeded 4 hours. Please compensate the statutory amount of £600 per passenger.”
This is tardiness. And it’s growing on Indigo.