BLR → SXVBengaluru to Salem

live

Direct flights from Bengaluru (BLR) to Salem (SXV) run nonstop between the two airports. The nonstop covers 162 km, an estimated 42 minutes in the air.

BLR Bengaluru smooth · +0
SXV Salem tracking
162 km · ~0h 42m est.
Running clean · 0 airlines · nonstop
100 / 100

route health from live BLR and SXV delay boards

Flight time~0h 42mestimated from route distance

Airports right now

live boards
BLRBengaluru +0 min smooth Full BLR delay board →
SXVSalem tracking Full SXV delay board →

How the Bengaluru to Salem route actually runs

Pro Flight Search records official board updates for nonstop BLR to SXV flights through the day: schedules, estimates, gate pushes and actual departures. The verdict above comes from operated flights, so it reflects what this route does rather than what the timetable promises.

Planning around a delay? Live airport delays · Weather delay risk map · Will a delayed flight be cancelled? · Do planes make up time in the air? · How we measure

Cite this data

Journalists, bloggers, and researchers may cite this page with attribution and a link to Pro Flight Search.

Suggested citation

Pro Flight Search: Bengaluru (BLR) to Salem (SXV) route reliability, measured from operated flights on official airport boards.

Canonical URL
https://proflightsearch.com/search-flights/BLR-SXV
How we measure this →

BLR to SXV questions

Is BLR–SXV running on time right now?

Smooth skies ahead. Both endpoints currently score the same, route health score 100/100. The airports section above carries the live status and delay window at both ends.

How long is the flight from BLR to SXV?

Great-circle distance is 162 km. With typical jet cruise speed plus taxi, climb and descent, expect roughly 41–44 min gate-to-gate on this route.

What does the route health score measure?

A blend of departure-side delay at BLR and arrival-side delay at SXV, computed from rolling delay windows (refreshed every 40 minutes) with a daily-rollup fallback. Current MVFR, IFR, or LIFR endpoint weather caps the score when flight rules can limit throughput. Higher is healthier: 100 means operations are clean at both ends.