Virgin Atlantic and IndiGo connection: missed flight and baggage claims
A Virgin Atlantic-IndiGo misconnection is strongest when all sectors were issued on one protected ticket, the passenger complied with transfer requirements and the final destination was reached late. UK261 can cover Virgin-operated travel between India and the UK, while an IndiGo domestic disruption has to be tested against the operating-carrier rule, Indian CAR and the continuous booking. Separate tickets usually shift the onward risk to the passenger.
Free eligibility check
Check your case in the form
Enter your route, date and type of disruption. We will check whether your case qualifies for a claim under EU 261/2004 or UK261.
What happened to your flight?
Claim up to €600 for a delayed or cancelled flight.
Choose the situation that applies to your flight:
Do not infer protection from through baggage or a shared booking screen alone. Preserve ticket numbers, booking references and the “operated by” line for every sector.
Ticket structure test
| Evidence | One-ticket connection | Separate-ticket warning |
|---|---|---|
| E-ticket | All coupons issued together | Independent ticket documents |
| Reservation | One protected itinerary | Separate references or self-transfer label |
| Baggage | Tagged to final destination | Collection and new check-in required |
| Missed flight | Airline rebooks without new fare | Passenger must buy a new domestic ticket |
| Fare conditions | Connection accepted by carriers | No protection between contracts |
An OTA can sell two tickets in one transaction. Read the documents, not just the confirmation page.
When Virgin operates the delayed international sector
UK departures on Virgin are protected. A Virgin-operated India-to-UK return is generally protected because Virgin is a UK carrier arriving in Britain. If the Virgin delay causes a missed IndiGo connection on the same booking, final arrival at the last ticketed destination can be relevant.
Suppose London-Delhi-Goa is one ticket and Virgin reaches Delhi late. IndiGo rebooks the domestic sector, and Goa arrival is eight hours late. The passenger should present the complete journey, identify Virgin as operator of the causative sector and preserve the protected connection evidence.
If Delhi-Goa was bought separately, Virgin’s contracted endpoint may be Delhi. The replacement domestic ticket needs insurance, OTA guarantee, contract or damages analysis; it is not automatically part of the UK261 fixed amount.
When IndiGo’s sector causes the disruption
IndiGo is the operator for its domestic or regional sector. Indian CAR and IndiGo’s tariff and disruption commitments become central. On a continuous itinerary that began in the UK, UK261 final-destination arguments can be legally complex when a non-UK carrier outside the UK causes the later delay. Do not direct the case to Virgin merely because it sold or marketed the first sector.
Identify which carrier made the operational decision, where the event occurred and how the ticket was issued. Ask both carriers to state responsibility for rerouting, but send fixed-compensation arguments to the operator supported by the applicable territorial rule.
If IndiGo cancellation makes a later Virgin flight impossible, contact the ticketing carrier immediately. A protected through ticket should be rerouted. A separate ticket can be treated as a no-show unless the passenger acts quickly.
Minimum connection and passenger conduct
The passenger must complete immigration, security and transfer steps reasonably and reach the gate on time. Connection processes vary by airport and itinerary, so do not rely on one universal transfer time.
If the carriers issued the connection together, their acceptance of the itinerary supports protection. Preserve scheduled arrival, gate closure, immigration or security timestamps and rebooking notes. Shopping or avoidable delay can break the causal link.
Report a likely miss before landing if possible and again at the transfer desk. Do not cancel the onward sector in the app unless consciously choosing a refund or another route.
Rerouting and care
On a protected UK261 journey, the responsible carrier should reroute to the final destination at the earliest reasonable opportunity and provide care during qualifying waits. Indian CAR also contains assistance, refund and alternate-flight rules for events in its scope.
Ask the carrier to consider another available route or partner when materially sooner. If self-booking becomes necessary, document contact attempts, visible seats, urgency and cost. Preserve later return sectors in writing.
Care can include meals, hotel and airport-hotel transfer. Keep itemised receipts and identify which carrier was approached. Do not seek the same expense twice from Virgin and IndiGo.
Baggage handoff
Through-checked baggage should be retagged after rerouting. Confirm the new tag and destination. If the bag fails to arrive, create a property irregularity report at the final airport before leaving.
International carriage can bring the Montreal Convention into play. The current baggage liability ceiling is 1,519 SDR per passenger for proven loss. Delay claims generally require writing within 21 days after delivery; damage claims within seven days. A report number is evidence but should be followed by the monetary claim.
On separate tickets, baggage may need collection and re-check in India. Missing that step can cause both baggage and boarding problems that are not automatically the airlines’ fault.
Compensation and local remedies
For a Virgin-operated long-distance UK261 journey, final arrival over four hours late can reach GBP 520; three to four hours can mean GBP 260. Virgin can rely on extraordinary circumstances only with causation and reasonable-measures evidence.
Indian CAR uses different assistance and compensation structures. It is not a rupee conversion of UK261. Identify the current CAR revision, operator, flight duration and fare elements before stating an Indian amount. AirSewa can be relevant after the airline complaint.
Avoid duplicate recovery where two systems cover one inconvenience. Separate fixed payment, refund, care expenses and baggage loss.
Claim file
Include all tickets, booking references, boarding passes, operators, baggage tags, original and replacement schedules, final arrival and cause. State which sector made the connection impossible. Attach rebooking records and itemised expenses.
Use the India rights guide for UK261 and CAR separation, and the operating-carrier page for partner responsibility.
Partner and legal information was reviewed on 26 August 2026.
FAQ
Does through baggage prove one protected ticket?
It is useful evidence but not conclusive. Check e-ticket numbers, booking references and fare documents for a self-transfer arrangement.
Who rebooks after a Virgin delay causes the IndiGo miss?
On one ticket, approach the carrier managing the disrupted itinerary immediately. Virgin’s causative operation can support the claim, while ticketing arrangements govern reissue.
Is a separately bought IndiGo flight covered by Virgin?
Usually not automatically. Insurance, an OTA guarantee or proven damages may help, but the separate contract normally creates self-transfer risk.
Can UK261 apply to India-to-UK on Virgin?
Yes. Virgin is a UK carrier, so its own inbound UK operation can generally qualify, subject to delay, cause and other tests.
Where should delayed baggage be reported?
Create the report at the final airport and then submit a written baggage claim with tags, delivery information and receipts within the applicable deadline.