Bangalore Airport (BLR) — Direct Flights, Airlines, USD Fares | India

Kempegowda International (BLR, ICAO VOBL) serves Bangalore, India and is a reference and transit hub in our catalogue. No non-stop African corridor is catalogued here yet, so Bangalore appears as a transit and reference point — travellers usually reach it via a Gulf or European hub.

At a glance

0 catalogued corridors touch Bangalore (BLR / VOBL) in India: 0 outbound and 0 inbound, flown by 0 carriers. 0 of those corridors carry a cached USD quote in our fare file; the rest are catalogued on schedule evidence alone. The mix runs 0 sectors under four hours, 0 of four to seven and 0 beyond seven.

The route mix at BLR splits into 0 short sectors under four hours, 0 medium sectors of four to seven hours and 0 long-haul sectors beyond seven — a profile that tells you what the terminal is actually built around. 0 of the corridors here are flagged in our data as labour-migration or diaspora routes, where checked-baggage terms drive booking decisions more than schedule does.

Two codes, two uses. BLR is the IATA code you will see on a ticket, a baggage tag and a departure board, while VOBL is the ICAO code used in flight plans, NOTAMs and air-traffic filing. They are not interchangeable: IATA codes are reused across the world’s smaller fields and are the ones that cause mis-booking, which is why every corridor on this site is keyed on the pair of codes rather than a city name.

Passenger compensation rights at BLR

1 instrument reaches BLR: the Montreal Convention 1999. India operates no EU261-style fixed cash scheme, so there is no statutory payout for a long delay — the cover is for baggage and provable delay losses, capped at about 1,288 SDR per passenger (the Special Drawing Right cap, roughly $1,700 USD at recent IMF rates).

Bangalore’s catalogued arrivals sit outside the EU261 / UK261 / GACA / APPR / DOT cash-compensation schemes, so the Montreal Convention is the operative floor — it covers baggage loss and provable delay losses on any international ticket.

Bangalore’s catalogued arrivals sit outside the EU261 / UK261 / GACA / APPR / DOT cash-compensation schemes, so the Montreal Convention is the operative floor — it covers baggage loss and provable delay losses on any international ticket.

FAQ

3 questions below answer what travellers ask most often about this page’s subject, drawn from the same route, carrier, airport and fare files as everything above. Where a figure is missing from our data, the answer says so rather than estimating.

Is BLR in the CheapFlightsAfrica catalogue? Kempegowda International (BLR) is included as a reference and transit airport, but no non-stop African corridor to or from Bangalore is catalogued here yet — travellers usually reach Bangalore via a Gulf or European connection.

What are the IATA and ICAO codes for BLR airport? The IATA code is BLR and the ICAO code is VOBL. The airport serves Bangalore, India.

Can I claim compensation for a disrupted flight at BLR? No fixed cash-compensation scheme applies to Bangalore arrivals, but the Montreal Convention covers baggage loss and provable delay losses on any international ticket.

How current are these numbers? Routes, carriers and airports come from data files refreshed with each content cycle; fares come from a Travelpayouts cache with a weekly history log behind it. Each page states its own last-updated date.

Sources

2 primary sources cited on this page are regulator and government material, not secondary summaries. Each is listed with what it actually governs, so a claim on this page can be checked against the instrument it comes from. Where a value is missing from our own files we leave the cell blank rather than estimate it.

• Montreal Convention 1999 — ICAO

• AirHelp — flight-compensation claims

• Montreal Convention 1999 — ICAO — the ICAO treaty collection, the source for the Montreal Convention 1999 baggage and delay liability limits.

• AirHelp — flight-compensation claims — a commercial claims service, cited as the industry explainer alongside the regulator rather than instead of it.

Every legal claim above is anchored to the instrument that creates it rather than to a summary of it, with commercial explainers cited only alongside, never instead. That is also why amounts appear in euro, pound, Canadian dollar and SDR rather than converted into the USD used for fares: a compensation tariff is a fixed figure in its own currency, and converting it would invent movement the law does not have.

Related

1 related page follow. Each is linked because it shares an endpoint, a carrier, a country or an audience cluster with this one — the annotations say what each adds, so the ones that do not apply to your trip can be skipped.

• Flights to India — country landing page: 4 catalogued corridors from African airports, carriers, visa row and the USD fare floor we have on file.

The relationship behind each link is structural: a common origin or destination airport, a common operating carrier, a common country, or the same audience cluster in our segmentation. No keyword matching is involved, so an unexpected entry here usually means a shared hub or a shared airline rather than a shared destination.

Corridor pages carry the per-route detail — carriers, weekly frequency, scheduled block time, great-circle distance and whatever the fare cache holds. Airport pages carry the full catalogued route list at that field, the based hub carriers and the compensation regime of the country it sits in. Carrier pages carry the baggage baseline, alliance and the network as this catalogue records it.