Flight Information Regions in India Explained: The Delhi, Mumbai, Kolkata and Chennai FIRs, the Guwahati Sub-FIR, and What They Mean for Your Flight

Every flight over India is handed from one air traffic control centre to the next inside a set of invisible boxes called flight information regions. India has four of them, named after the cities whose control centres run them: Delhi, Mumbai, Kolkata and Chennai, with a fifth, smaller box, the Guwahati sub-FIR, tucked into the north-east. Together they cover not just the Indian landmass but enormous stretches of the Arabian Sea, the Bay of Bengal and the Indian Ocean.

This guide explains what each Indian FIR covers, who runs them, why the ocean parts matter more than most passengers realise, how Indian airspace fits into the Europe-to-Asia routing picture, and what the proposed Project ISHAN, a single Indian sky controlled from Nagpur, would change. If you want the general concept first, start with our explainer on [what a flight information region is](/blog/what-is-a-flight-information-region-fir-explained); this post is the India-specific version.

Who manages Indian airspace

Civil air traffic services over India are provided by the Airports Authority of India (AAI), a statutory body that began operating on 1 April 1995 when the National Airports Authority and the International Airports Authority of India were merged. It works under the Ministry of Civil Aviation, with the Directorate General of Civil Aviation (DGCA) as the safety regulator. AAI runs the area control centres that correspond to the four FIRs, the approach and tower units at airports, and the communication, navigation and surveillance infrastructure that ties them together.

The split into four regions is historical and practical: each centre grew up around a major international airport and the radar and radio coverage available at the time. Internationally, the boundaries are agreed through ICAO's Asia-Pacific regional air navigation plan, which is why India's FIRs sit neatly against those of Pakistan, Nepal, Bangladesh, Myanmar, Sri Lanka, Oman and the other neighbours whose airspace India borders. By AAI's own count, India's FIRs share boundaries with 12 neighbouring countries.

The four Indian FIRs, one by one

Each FIR has a four-letter ICAO location indicator, the code you will see on charts, in NOTAMs and on flight-tracking sites. India's codes begin with V, the ICAO letter for the region, with the second letter marking the part of the country.

Delhi FIR (VIDF)

The northern region, controlled from Delhi. It covers the capital, Punjab, Haryana, Rajasthan, Uttar Pradesh, Himachal Pradesh, Uttarakhand and the Jammu and Kashmir and Ladakh region, and it shares borders with the Lahore and Karachi FIRs of Pakistan to the west, and with Nepal and China to the north. Almost everything that flies between Delhi and Europe, the Gulf or Central Asia leaves India through this FIR, which is why the on-again, off-again closures of Pakistani airspace to Indian carriers hit Delhi departures hardest; our post on the [Pakistan airspace closure and Indian airlines](/blog/pakistan-airspace-closure-indian-airlines-september-2026) explains the detours.

Mumbai FIR (VABF)

The western region, controlled from Mumbai. On land it covers Maharashtra, Gujarat, Goa, Madhya Pradesh and parts of the central states; at sea it extends far into the Arabian Sea, where it meets the Karachi FIR to the north-west and the Muscat FIR of Oman across the water. This oceanic portion is one of the busiest pieces of sky in the region, because the great majority of traffic between the Gulf and India, and much of the traffic between Europe and South-East Asia, crosses it.

Kolkata FIR (VECF) and the Guwahati sub-FIR

The eastern region, controlled from Kolkata. It covers West Bengal, Bihar, Jharkhand, Odisha and the north-east, and a large slice of the Bay of Bengal, bordering the Dhaka FIR of Bangladesh, the Yangon FIR of Myanmar and the Kathmandu FIR of Nepal. Inside it sits the Guwahati sub-FIR, a delegated area that handles the north-eastern states, where terrain, weather and the narrow Siliguri corridor make a dedicated unit sensible. A sub-FIR is not a separate flight information region in ICAO terms; it is part of the Kolkata FIR with its own control centre doing the day-to-day work.

Chennai FIR (VOMF)

The southern region, controlled from Chennai. It covers Tamil Nadu, Kerala, Karnataka, Andhra Pradesh and Telangana, the Lakshadweep islands and a very large oceanic area reaching south across the Indian Ocean, where it borders the Colombo FIR of Sri Lanka, the Malé FIR of the Maldives and, further out, the Jakarta and Kuala Lumpur FIRs. Flights between the Gulf and Singapore, Kuala Lumpur or Australia spend hours in the Chennai FIR without ever being over Indian land, which is the clearest example of why an FIR is about responsibility, not sovereignty.

Why the ocean parts matter

If you draw the four FIRs on a map, more than half of the area is water. That is normal for a country with a long coastline, but it has consequences. Over the oceanic parts there is no ground radar, so aircraft are followed by satellite-based surveillance and position reports, and separation standards are wider. It also means Indian controllers are responsible for traffic that has nothing to do with India: a flight from Dubai to Perth, or from Doha to Singapore, is 'in India' for air traffic purposes for a long time.

For passengers this is mostly invisible, but it shows up in two ways. First, when something disrupts the Middle East corridors, such as the Gulf and Iranian closures covered in our [Middle East restrictions explainer](/blog/how-long-will-middle-east-airspace-restrictions-last), the rerouted traffic piles into the Mumbai and Chennai oceanic sectors, and capacity there becomes the bottleneck. Second, the oceanic boundaries are where flights change frequency and hand over to another country, and that is where the occasional delay or hold waiting for a slot into the next FIR occurs.

Indian FIRs and the Europe-to-Asia routing picture

India sits in the middle of the great east-west air corridor. Flights from Europe to South-East Asia, Australia and the Far East that avoid Russian airspace to the north, and want to stay clear of the more restricted Middle Eastern FIRs, tend to enter India from Oman or Pakistan, cross the Delhi or Mumbai FIR, and leave through Kolkata towards Myanmar and Thailand, or through Chennai towards the Bay of Bengal and Malaysia.

That makes India a stable, well-served piece of sky in a region that has had a lot of instability. There are no EASA conflict-zone bulletins for Indian FIRs, and the main airspace risk to a traveller is not conflict but politics between India and Pakistan, which has periodically closed Pakistani airspace to Indian carriers and Indian airspace to Pakistani ones. Those closures do not affect third-country airlines. If your flight is on a European or Gulf carrier, the India-Pakistan dispute is irrelevant to your routing; if you are on an Indian airline flying west, it may add an hour or more via the Arabian Sea. Our guide to [Europe-India routes without Iranian airspace](/blog/europe-to-india-routes-without-iranian-airspace) shows how those options fit together.

Project ISHAN: one Indian sky from Nagpur

The four-region arrangement is under review. In 2024 the Airports Authority of India invited expressions of interest for a detailed project report on ISHAN, the Indian Single Sky Harmonised Air Traffic Management initiative, which would merge the four FIRs into a single continuous airspace managed from Nagpur, geographically close to the centre of the country. In October 2025 the Union minister Nitin Gadkari told the Air Traffic Controllers' Guild he would push for the project to be based there; air traffic controllers quoted at the time noted that it would mean more staff and a major expansion of Nagpur's control centre.

At the time of writing the project is still at the planning and feasibility stage, with no published date for the switch. If it goes ahead, the practical change for passengers would be fewer hand-offs and more flexible routing inside India, the same logic behind Europe's Single European Sky. The four FIR codes may live on in charts for years regardless; airspace reorganisations of this size are slow, deliberate affairs.

How to see which Indian FIR your flight is in

If you are curious, or trying to understand a delay, there are three easy ways.

1. On a flight-tracking site, look at the route line: the FIR boundaries are usually shown as faint lines on the map, and the aircraft's current controlling unit is sometimes listed in the details.
2. On the inflight map, the handover points roughly match the FIR boundaries: entering India from the Arabian Sea puts you in Mumbai; crossing the centre of the country usually means a Delhi-to-Kolkata or Mumbai-to-Chennai hand-off.
3. In NOTAMs and advisories, the four-letter codes VIDF, VABF, VECF and VOMF identify the region; our guide on [how to read a NOTAM](/blog/what-is-a-notam-how-to-read-airspace-closure-notices) explains the rest of the format.

The short version

India has four flight information regions, Delhi, Mumbai, Kolkata and Chennai, plus the Guwahati sub-FIR inside Kolkata, all run by the Airports Authority of India. Mumbai and Chennai carry huge oceanic areas that handle traffic between the Gulf and South-East Asia and Australia. There are no conflict-zone bulletins for any of them; the only recurring restriction is the India-Pakistan dispute, which affects Indian and Pakistani carriers rather than foreign ones. And the whole structure may one day be replaced by a single region run from Nagpur, if Project ISHAN moves from plan to reality.