Varanasi (VNS) → Kathmandu (KTM)
A reference for the Lal Bahadur Shastri Airport to Tribhuvan International Airport route. You'll find the operators on file, the great-circle geometry, the connecting options if no nonstop fits your dates, and a short profile of each endpoint airport.
The flight from Varanasi (VNS) to Kathmandu (KTM) covers a great-circle distance of roughly 352 km (219 miles). Aircraft leave Lal Bahadur Shastri Airport on an initial northeast heading. As international sectors go, this one sits in the short-haul bracket: long enough that most carriers run it as its own dedicated rotation, but short enough to fit inside a single crew duty period.
Air India Limited is the only carrier filing a scheduled VNS to KTM service in the dataset. Single-operator routes like this usually reflect a focus-city or hub-spoke relationship, or a market that's big enough to support one dedicated daily but not big enough to attract a second entrant yet.
Operators on the VNS → KTM direction
Carriers with at least one scheduled rotation on this sector in the OpenFlights dataset, ranked by the number of code-shared filings.
At well under 1,500 km this is a regional sector. Carriers typically run narrow-body aircraft from the Airbus A320 family or the Boeing 737 series, with regional jets (Embraer E-Jet, CRJ) showing up on lower-frequency rotations. Block time runs around 1h 09m. Expect a single-aisle cabin and no real meal service. A snack and a drink is usually all you get.
If a nonstop doesn't match your dates, Delhi (DEL), Mumbai (BOM), and Kolkata (CCU) show up on both ends of the network and make the most natural connecting points. The connecting-hubs grid below extends that list to the eight strongest options, ranked by each airport's overall departure activity. That ranking is a fast proxy for how many onward flights a single stop is likely to feed.
Connecting hubs
Airports that already appear on both ends of this network. They're the natural one-stop options when no nonstop matches your dates, ranked by overall departure activity.
This is an international sector between India and Nepal. Build in time for passport validity, possible visa requirements, and the time-zone gap between Varanasi and Kathmandu. International itineraries are quoted in local time at each end, so a "midnight" departure in Varanasi typically lands the next morning in Kathmandu. Customs clearance happens on first arrival in the destination country.
On the day of operation, the VNS to KTM direction lifts off heading northeast, then the great-circle track curves to compensate for the Earth's rotation. The return KTM to VNS sector heads southwest out of the gate, with 1 operators on file for the inbound side. Combine the two operator lists for a full picture of the city pair's competitive landscape.
Endpoints
Other routes from Varanasi (VNS)
Other destinations served from the same origin. Handy for combining trips or for finding an alternate first leg.
Other routes into Kathmandu (KTM)
Other origins that already file scheduled service into the destination airport.
Reading this route page
The operator list reflects scheduled-route filings in the OpenFlights dataset, not real-time availability. A carrier appearing here publishes a scheduled service on this sector. It isn't a live timetable, and the actual flight numbers, frequencies, and aircraft types shift season to season. For booking and current schedules, cross-reference the airline page above with the carrier's own website.
Distance here is the great-circle arc between the two airports' published coordinates. Real flight tracks wander off that line because of wind, ATC routings, oceanic crossings, and political airspace constraints. Block time is an estimate covering ground taxi, climb, cruise at typical jet speeds, and descent. Real block times shift with aircraft type, weather, and traffic, so treat the stat-strip number as a planning indicator rather than a published flight time.