IndiGo Plan B: What Really Happens If You Miss a Connection

IndiGo's Plan B covers airline-caused missed connections — but not self-caused ones.

FlightGPT can make mistakes. Confirm flight & fare details before paying.

IndiGo Plan B: What Really Happens If You Miss a Connection

By Arjun Kapoor (Arjun Kapoor tracks error fares, mileage runs and award-chart sweet spots for Indian travellers. He moderates two Telegram fare-alert channels and has booked Europe round-trips at sub-₹25,000 four times in the last 24 months.) · Published · 11 min read

IndiGo's Plan B sounds reassuring in the marketing — 'we'll take care of you if you miss a connection.' The reality is more specific and more limited than that. Whether you get rebooking or a refund depends entirely on one question: who caused the missed connection? Here's the breakdown.

TL;DR — What Is IndiGo Plan B?

IndiGo's Plan B is their connecting-itinerary protection scheme. If IndiGo causes you to miss a connection — through a delay, cancellation, or late arrival on the first leg — they will rebook you on the next available IndiGo flight to your final destination at no extra charge. If no IndiGo flight works within a reasonable timeframe, you may be eligible for a full refund. What Plan B does not cover: self-booked back-to-back tickets on separate PNRs, insufficient connection time you chose yourself, or delays caused by factors outside airline control (weather, ATC holds, slot issues).

The Critical Distinction: One PNR vs Two PNRs

This is where a lot of passengers get burned. If you booked a Bengaluru–Guwahati–Imphal itinerary as a single through-ticket on one PNR through IndiGo (or an OTA that issued it as one booking), you're on a connecting itinerary and Plan B applies if IndiGo delays your first leg.

If you separately booked BLR–GAU on one ticket and GAU–IMF on a different booking — which many people do to chase a cheaper combination — those are legally two separate contracts. IndiGo has no obligation under Plan B to rescue you if the first flight runs late and you miss the independently-booked second one. You'd need to rebook the second flight at whatever the going rate is, which on a thin route like GAU–IMF could be ugly.

This distinction matters enormously if you're routing through hubs like Bengaluru (BLR), Hyderabad (HYD), or Mumbai (BOM) to reach Northeast destinations. The temptation to mix and match tickets for a lower total fare is real — I've done it myself — but you're carrying the connection risk entirely.

What IndiGo Actually Owes You on an Airline-Caused Missed Connection

If you're on a single IndiGo PNR and their delay causes you to miss the connecting IndiGo flight, here's what the policy generally provides:

The DGCA's passenger charter outlines your statutory rights separately from whatever the airline's own policy says — your rights under DGCA rules exist regardless of IndiGo's internal policy wording. Always worth knowing both.

What You Lose When It's Self-Caused

If you built in only 45 minutes of connection time at Bengaluru (a notorious airport for delays) and your inbound flight ran 55 minutes late, that's on you — not on Plan B. IndiGo will treat your missed onward flight as a no-show and the ticket is typically forfeited unless you had a refundable fare.

Bengaluru is the connection point where I've seen the most failure stories. The airport is consistently congested, and even 60–75 minute domestic connections there can be tight during busy periods (morning rush 7–9am, evening peak 5–8pm). If you're building a self-booked connection at BLR, I'd personally want at least 90 minutes between scheduled arrival and next departure — and even then I'd accept the risk consciously.

The minimum connection time IndiGo recommends for their through-connections at major hubs is stated in their booking flow — pay attention to it. OTAs sometimes flag 'tight connection' warnings; don't ignore those.

Real Bengaluru Connection Failure Scenarios

Here's how it typically plays out in practice based on what travellers report:

Scenario A — Airline fault, single PNR: BLR–GAU on IndiGo delayed by 90 minutes. You miss GAU–IMF. IndiGo acknowledges the delay is their fault. They rebook you on the next GAU–IMF departure, which might be the following morning. They arrange a hotel in Guwahati for the night. Annoying, but you get to your destination and it costs you nothing extra. This is Plan B working as intended.

Scenario B — Airline fault, two PNRs: Same delay, but you booked the two legs separately. IndiGo rebooks you on the next BLR–GAU flight (because that's the flight they delayed). But they have no obligation for the separately-booked GAU–IMF ticket, which you've now missed. You're at Guwahati airport buying a new ticket to Imphal at whatever the last-minute fare is. If it's a thin route, that could easily cost ₹8,000–12,000 on top of your original spend.

Scenario C — Weather/ATC delay: ATC holds your BLR–GAU due to fog at Guwahati. Technically an 'extraordinary circumstance' — similar to EU261's force majeure carve-out. IndiGo may still rebook you (good airlines do this regardless) but their compensation obligations under DGCA rules are more limited for genuine extraordinary circumstances. Check DGCA's current passenger rights circular for specifics.

How to Actually Use Plan B at the Airport

If your first leg is delayed and you're worried about missing a connection, don't wait until you land. As soon as the delay is announced:

  1. Call IndiGo's customer care line (number on their site) and flag you're at risk of missing a connecting IndiGo flight on the same PNR.
  2. At the gate, tell the ground staff you have a connection. They can sometimes hold the connecting aircraft for a few minutes if multiple passengers are affected.
  3. If you do miss it, go directly to the IndiGo transfer desk at your connection airport — don't exit the terminal first.
  4. Get everything in writing or via SMS — the delay reason, the rebooking confirmation, any hotel/meal vouchers. This matters if you need to claim travel insurance later.

Travel insurance with trip interruption cover can also help bridge the gap, especially if the delay means additional hotel nights or meals not covered by the airline. Check your policy before travel, not after the delay happens.

The Bottom Line on Plan B

Plan B is genuinely useful when it applies — but 'when it applies' is doing a lot of heavy lifting in that sentence. For single-PNR IndiGo connecting itineraries delayed by IndiGo, it's a real safety net. For the very common scenario of self-booked back-to-back tickets, it's irrelevant.

If you're frequently routing through hubs for Northeast travel or other thin-route destinations, booking as a single itinerary is usually worth the small fare premium over mixing two tickets. The insurance value of being on one PNR is real.

For finding multi-city or connecting itineraries as a single booking, try FlightGPT's AI search — it can surface through-connections that might not be obvious in a standard one-way search. Also see our guide to Northeast India thin routes and the SpiceJet 2026 reliability assessment if you're considering alternatives.

Frequently asked questions

Does IndiGo Plan B cover me if I miss a connection due to a delay?

Only if the delay was caused by IndiGo and your two flights are on a single PNR (through-ticket). If IndiGo caused the delay, they'll rebook you on the next available IndiGo flight at no charge, and provide meals/hotel if the wait is overnight. If you self-booked two separate tickets and chose an aggressive connection time, Plan B does not apply.

What's the minimum connection time I should book at Bengaluru airport on IndiGo?

IndiGo specifies minimum connection times in their booking system for through-itineraries — follow those. If you're building your own connection at BLR, I'd allow at least 90 minutes to 2 hours for domestic-to-domestic, especially during morning and evening peak hours. Bengaluru airport is reliably congested and even on-time flights can take 20–30 minutes to deplane.

What does DGCA say about missed connections caused by the airline?

DGCA's passenger rights circular requires airlines to offer rebooking or a full refund when a delay causes you to miss an onward flight on the same booking. For delays above specified hour thresholds, meals and hotel accommodation are also mandated. Check the current DGCA passenger charter on dgca.gov.in for the specific thresholds, as these rules are updated periodically.

Can I get a full refund instead of rebooking under Plan B?

Yes — if IndiGo cannot rebook you within a reasonable timeframe (or at all) due to a delay they caused, you can opt for a full refund of the unused portion of your ticket instead of waiting for rebooking. Get this in writing at the airport or escalate via IndiGo's customer care.

Does Plan B apply if SpiceJet or Air India causes the delay on a codeshare?

IndiGo Plan B applies to IndiGo-operated flights on IndiGo-issued single-PNR itineraries. If you're on a codeshare or interline with another carrier, the rules get more complicated — each carrier's policy and DGCA rules both apply, but the obligation chain depends on who operated the delayed flight. For clean application of Plan B, book directly on IndiGo or via an OTA that issues a single IndiGo PNR.

Will IndiGo pay for a hotel if I'm stranded overnight due to a missed connection?

If IndiGo caused the delay and your missed connection means an overnight wait, yes — their Plan B policy and DGCA rules both provide for hotel accommodation in this scenario. Confirm at the IndiGo transfer desk at your connection airport. Don't book your own hotel assuming reimbursement without getting airline approval first; the process varies and pre-approval avoids disputes.