The Manifest
Industry·8 July 2026·10 min read

Navi Mumbai and Noida airports: what operators must reprice

Navi Mumbai and Noida airports are now live. Here is what operators must rewrite on quotes, transfer costs and connection buffers before selling either city.

Masai Mara · 17:45

Mumbai and Delhi-NCR each just became two-airport cities, and most standing quote templates haven't caught up. Navi Mumbai International Airport (NMIA) and Noida International Airport (Jewar) are both taking live traffic now, and neither has an airside or through-checked link to its sibling airport across town. If your quotes, vouchers and driver briefings still say "Mumbai airport" or "Delhi airport" without a code, you have a costing gap and a liability gap on the same line.

This matters for operators specifically, not just as aviation news. It changes which vendor you call for a transfer, what you charge for it, and who pays when an airline moves a passenger from one field to the other. None of that resolves itself; you have to write it into your paperwork.

This post gives you the audit to run on existing packages, the fix for your quotes and vouchers, a structure for rebuilding your transfer cost table, and a rule to set for split-airport connections before your next Mumbai or Delhi-NCR departure goes out.

Two metros just became two-airport cities

Navi Mumbai International Airport began commercial operations on 25 December 2025, and its first international flight, Air India Express IX-208 from Abu Dhabi, landed on 15 July 2026 (Free Press Journal). Noida International Airport (Jewar) started commercial flights on 15 June 2026, and an airport official has said international services are targeted "before the end of 2026," once domestic operations settle (The New Indian Express). That is a target quoted in May 2026, not a confirmed schedule. Do not promise a client, or yourself, a specific month for Jewar's first international flight.

The operator-facing fact underneath both dates is simpler and more urgent: NMIA and CSMIA (Mumbai's existing airport) have no airside connection between them, and DEL and DXN (Jewar) have none either. Getting a passenger from one to the other means a full ground transfer, re-check-in, and a fresh security queue. As of August 2026, there is no interline or through-check agreement linking either pair, which is exactly why your paperwork now has to carry the airport code, not just the city name.

Which of your standing packages carry a hidden airport assumption

Run a quick audit before your next departure using either city. Any package, quote or voucher that says "Mumbai airport pickup" or "Delhi airport transfer" without naming the specific airport is now ambiguous, and that's where costing errors and no-show pickups happen. Check these four places:

  • Standing quote templates. If "airport transfer included" is a static line item, it's currently priced for one airport only, and you may not know which one your vendor assumed.
  • Saved WhatsApp scripts. Reply templates for "how do I reach you from the airport" often predate NMIA and DXN entirely.
  • Hotel voucher headers. A voucher that lists "pickup: Mumbai Airport" gives the hotel's transport desk nothing to route a driver by if the client's actual flight lands at NMIA.
  • Rooming sheets and driver briefing sheets. These are the documents your ground team actually works from on departure day. If they carry only the city name, your driver finds out the airport code from the client at the gate, not from you.

None of this needs new software, just one pass through your existing document set checking for "Mumbai airport" and "Delhi airport" used as bare phrases.

Put the code on the paper, not the city name

From now on, every quote, e-ticket cross-check, voucher and rooming sheet for Mumbai or Delhi-NCR should carry the airport code, not just the city. Use NMI or BOM/CSMIA for Mumbai, and DXN or DEL for Delhi-NCR, on every document a client or a driver will actually read.

Noida's airport carries a deliberate two-code setup worth knowing before your team gets confused by it. Its passenger-facing IATA code is DXN, appearing on tickets, boarding passes and baggage tags; its operational ICAO code, VIND, is used internally by pilots and air traffic control. The airport's former CEO said the letters were chosen on purpose (D for Delhi, N for Noida, X for connectivity) rather than something more obvious like NIA or JEW (Business Today). If your driver or a hotel's transport desk sees "DXN" and doesn't recognise it, that gap is now a wrong pickup point.

This isn't only a new-city-sales problem, either. Reported plans put nearly 30% of Mumbai's international flight traffic on a path to shift from CSMIA to NMIA from 1 October 2026, as part of a realignment tied to the redevelopment of Mumbai's older Terminal 1 (Free Press Journal). No airline-by-airline breakdown is public, so treat it as a reported direction, not a fixed route list. But it means even a Mumbai package you haven't touched in a year is worth rechecking, because the airport a client's flight lands at could change under a routing you assumed was fixed.

Rebuilding your transfer cost table for the new zone

No published tariff table exists yet for cab or coach transfers to and from NMI or DXN, so don't reuse your old city-airport rate for either. Build a new line item from your own vendor's quote, structured by pickup zone, the same way you'd structure any vehicle costing worked from per-km and driver bata rather than a flat guess.

Ask your vehicle vendor for a fresh quote specifically to and from NMI and DXN, broken out by the catchment zones your clients actually book from, rather than one blended "airport transfer" figure:

Pickup zone Ask your vendor for Why it's a separate line
NMIA catchment (Thane, Panvel, Navi Mumbai) Per-km rate + toll estimate to/from NMI Distinct road route from the CSMIA transfer you already price
CSMIA catchment (South/Central Mumbai) Existing rate, rechecked Still valid, but no longer the only Mumbai airport line
DXN catchment (Greater Noida, Ghaziabad) Per-km rate + toll estimate to/from DXN New route, likely a different vendor zone than your DEL line
DEL catchment (Central/South Delhi) Existing rate, rechecked Confirm it still holds once DXN traffic starts pulling business

Example: Say your regular Mumbai vendor quotes a hypothetical ₹1,900 one-way for a Panvel-to-NMIA run versus ₹1,400 for the same pickup point to CSMIA. If your quote template still charges the CSMIA figure by default because that's the only line item that exists, you eat the ₹500 gap on every NMIA booking until you add the new zone as its own row.

Treat this the way you'd treat any new pickup city entering your route map: a fresh costing exercise with the vendor, not an assumption carried over from the airport it's replacing.

The connection buffer: what to enforce when two flights land at two different fields

Because NMIA has no rail or metro link to CSMIA yet, and DXN has none to DEL, any itinerary where an inbound and an onward flight land at different airports in the same city needs a full ground-transfer buffer built in, not just a generic "connection time." There is no through-check agreement and no published minimum connection time between either pair, so there's nothing to look up. You have to set the number yourself.

In practice, treat a same-city, different-airport connection the way you'd treat an inter-city one: full drive time between the two fields, plus re-check-in, plus security, plus a margin for traffic. NMIA's planned metro and rail links to CSMIA are still under construction, so today's transfer between them is road-only (Wikipedia).

Careful: "Same city" on an itinerary sheet is not the same as "same airport." A rooming sheet or tour quotation that lists "Mumbai, arrival and departure" without airport codes reads as one clean connection to whoever's building the day plan. If the arrival is NMI and the departure is BOM, that's two separate ground movements, and the buffer needs to reflect it before you promise a client a same-day onward connection.

Who eats the cost when the airline re-times you to the other airport

There's no DGCA rule or codified circular governing who pays when an airline reassigns a passenger from one city airport to the other, so this is a policy you set yourself, not one you can cite, the same gap operators hit when weather or a strike breaks a day of the itinerary. Given the reported CSMIA-to-NMIA shift from 1 October 2026, build a clear rule into your own terms and vendor briefing before it happens to a client mid-trip.

Two things to decide and write down now:

  1. Who absorbs the extra transfer cost when an airline moves a confirmed booking from CSMIA to NMIA (or, eventually, DEL to DXN) after your quote was priced against the original airport.
  2. Who absorbs a missed connection if that reassignment shortens the buffer between an inbound flight and an already-booked onward transfer or activity.

Confirm the airline's own current compensation policy for change-of-airport disruptions directly with the carrier before you finalise your rule. Don't assume it mirrors delay or cancellation compensation; airport reassignment is a different category with no published carrier policy on record yet.

The sales opening: nearer departure points for six catchment areas

The flip side of two more airports is a shorter run to the airport for clients who live near them, and that's a genuine opening once route networks fill in. NMIA opens up Navi Mumbai, Thane and Panvel as departure catchments that no longer have to cross the harbour to CSMIA. DXN does the same for Greater Noida, Ghaziabad and the west UP/Agra corridor, roughly 70 km from central Delhi by DXN's own positioning (Jagran Josh), a source worth treating as reported rather than independently verified.

A planned Namo Bharat corridor between Ghaziabad and Jewar, spanning roughly 72 km, is projected to eventually cut travel times from Ghaziabad, Greater Noida and Noida to around 40-50 minutes (Swarajya). That's a future projection tied to a corridor still in planning, not today's drive time, but it's a directional signal for which departure-city page or pickup radius to build next.

Route lists for both airports are still thin this early. IndiGo is Noida International Airport's designated launch carrier, initially planning 18-plus destinations, with Akasa Air as a strategic partner (Wikipedia). Treat any specific route claim as current-as-of-August-2026 and recheck before building sales copy around it.

Common questions

Which international flights operate from Navi Mumbai airport?

As of August 2026, NMIA's confirmed international service is Air India Express flight IX-208 to and from Abu Dhabi, which began operating 15 July 2026 (Free Press Journal). Expect this list to expand as the airport ramps up and as the reported CSMIA-to-NMIA traffic shift from 1 October 2026 moves more international routes across. Recheck before quoting a specific route to a client.

When will Noida airport start international flights?

There is no confirmed date. An airport official told The New Indian Express in May 2026 that international services are targeted "before the end of 2026," once domestic operations, which started 15 June 2026, have stabilised. Treat that as a target, not a schedule, and don't commit a client to a specific month until the airport or an airline confirms it.

How far is Navi Mumbai airport from Mumbai city?

NMIA is reported to sit about 35 km from Mumbai's existing airport, CSMIA (Wikipedia). No verified road travel time is available for that route today, and current NMIA-CSMIA transfers are road-only since the planned metro and rail links are still under construction, so build your own transfer buffer from a live vendor quote rather than an assumed drive time.

The short version

  • Audit every standing Mumbai or Delhi-NCR package for a bare "airport transfer" line. If it doesn't name NMI, BOM/CSMIA, DXN or DEL specifically, it's ambiguous and needs fixing.
  • Write the airport code, not just the city name, on every quote, e-ticket cross-check, voucher and rooming sheet from now on.
  • Rebuild your transfer cost table as new line items for NMI and DXN zones. Don't reuse a CSMIA or DEL rate for the new airport.
  • Set a written minimum connection buffer for any itinerary where the inbound and onward flights land at different airports in the same city. There's no official minimum connection time to fall back on.
  • Decide, and put in your terms, who pays when an airline reassigns a passenger from one city airport to the other, especially with the reported CSMIA-to-NMIA shift starting 1 October 2026.
  • Watch that October shift even on Mumbai routes you haven't changed; it can move a client's airport without you touching the package.
  • Every date and figure above is as of August 2026. Recheck before you quote, and confirm any airline change-of-airport policy directly with the carrier.