Pricing Search Start free trial
Safe with context · Pakistan closure spillover

Dubai to Mumbai — Flight Safety, FIRs Crossed, Airline Routing 2026

Great-circle ~1,000 nm · Scheduled block ~3 h · Last updated: May 2026

TL;DR

DXB–BOM is short, dense and structurally simple: UAE to India via OMAE › OOMM (Muscat / Oman oceanic) › VABF (Mumbai). Pakistan’s 2026 closure to Indian-flagged commercial traffic does not directly affect the DXB–BOM track itself, but it has reshaped the wider regional flow: Indian carriers now route their westbound long-haul via Oman instead of overflying Pakistan, which pushes more traffic through the same southern corridor that DXB–BOM relies on.

Distance
~1,000 nm
~1,950 km direct
Flight time
~3 h
Single short sector
Pre-2022 path
OMAE › OOMM › VABF
Same Arabian Sea track
Current path
OMAE › OOMM › VABF
Same; secondary flow effects

FIRs typically crossed

ICAO FIR Notes
OMAE Emirates (UAE) Departure FIR. Modern radar.
OOMM Muscat (Oman) Arabian Sea oceanic transit. Procedural separation over water.
VABF Mumbai (India) Arrival FIR. Full surveillance over the western Indian coast.

The DXB–BOM track is largely overwater across the Gulf of Oman and the Arabian Sea. Pakistan’s OPLR FIR is not on this routing.

Pre-2022 vs current routing

The DXB–BOM city pair itself has not shifted: the path is short, follows the Arabian Sea south-east from the UAE coast, and enters Indian airspace from the west. Operators have flown essentially the same track for years.

The post-2022 changes in this region are not on DXB–BOM directly but on the broader picture around it. Two effects matter:

First, Pakistan’s extended closure to Indian-flagged commercial traffic in 2025–2026 (multiple NOTAM extensions in 2026) means Indian carriers operating westbound long-haul from BOM and DEL to Europe / North America now detour over the Arabian Sea via Oman before turning north-west — the same southern corridor that DXB–BOM uses for its return leg.

Second, the February 2026 Gulf airspace events introduced managed-corridor procedures around UAE arrival and departure, which slightly tighten the OMAE flow but do not alter the great-circle track to Mumbai.

Operating carriers and their typical routings

EK
Multiple daily DXB-BOM rotations

777-300ER and A380. Standard OMAE › OOMM › VABF routing. No structural detour needed.

AI
Daily DXB-BOM rotations

787-8 and A320 family. DXB-BOM itself is a clean short sector; the wider impact on AI is on its westbound network out of BOM, which now consistently routes through Oman to avoid Pakistani airspace.

6E
IndiGo
Multiple daily DXB-BOM rotations

A320neo / A321neo dominant. High-frequency operator on the pair. Same OMAE-OOMM-VABF track. Pakistan closure impact is felt on IndiGo’s European long-haul rather than on DXB-BOM.

Current airspace conditions on the corridor

UAE managed-corridor regime

Procedural overlays on OMAE departure remain in force; see the UAE security corridor briefing and the broader Gulf 12 FIR shutdown briefing.

Pakistan / India airspace closure

Closure to Indian-flagged carriers reshapes regional flow; full picture in Pakistan / India airspace status 2026.

GNSS environment on the Gulf approach

Periodic GNSS interference reports on the Gulf of Oman / northern Arabian Sea. See the Gulf carriers GPS spoofing briefing and the spoofing vs jamming guide.

Block-time and fuel impact

For DXB-BOM specifically, scheduled block time is essentially unchanged from the pre-2022 baseline — the route was never optimised through Pakistani airspace and does not depend on Iran. Any added minutes come from arrival flow into VABF during peak banks, or from UAE departure-flow controls during managed-corridor periods.

For BOM’s westbound long-haul (BOM-LHR, BOM-EWR), the Pakistan closure adds a measurable detour over the Arabian Sea and Oman before turning north. See why do airlines reroute for the underlying economics.

Common diversion patterns

DXB end alternates: Abu Dhabi (OMAA), Sharjah (OMSJ), Al Maktoum (OMDW). Oceanic-leg alternates: Muscat (OOMS), Salalah (OOSA). BOM end alternates: Ahmedabad (VAAH), Pune (VAPO), Hyderabad (VOHS), Goa (VOGO). The Arabian Sea track does not require ETOPS-extended ratings for modern twins, but it is overwater and operators carry standard ETOPS-120 / 180.

For wider context on overwater diversion planning see ETOPS / EDTO explained.

Sources and related

  • Public ADS-B aggregations (Flightradar24, FlightAware) for routing samples
  • Cirium / OAG schedule data
  • Pakistan CAA NOTAM publications, India DGCA bulletins
  • OPSGROUP and EUROCONTROL conflict-zone advisories

Route-level data for your stack

UAE managed-corridor overlays, Pakistan-India airspace flow context and DXB-BOM routing samples are available via the FlySafe API.

FlySafe API →

This page is editorial information based on publicly available routing, schedule and airspace data. It is not operational guidance, not a route plan, and not a substitute for ICAO / EASA / FAA / state-AIP publications, NOTAMs, or your operator’s dispatch and security teams.