Route profile

Chiang Mai (CNX) → Luang Prabang (LPQ)

A reference for the Chiang Mai International Airport to Luang Phabang 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.

358 kmGreat-circle distance
223 miIn miles
1h 10mApprox. block time
1Operators on file

The flight from Chiang Mai (CNX) to Luang Prabang (LPQ) covers a great-circle distance of roughly 358 km (223 miles). Aircraft leave Chiang Mai International Airport on an initial east 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.

Lao Airlines is the only carrier filing a scheduled CNX to LPQ 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 CNX → LPQ direction

Carriers with at least one scheduled rotation on this sector in the OpenFlights dataset, ranked by the number of code-shared filings.

IATAAirlineCountryCallsign
QV Lao Airlines Lao Peoples Democratic Republic LAO

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 10m. 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, Bangkok (BKK), –, and – 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 Thailand and Laos. Build in time for passport validity, possible visa requirements, and the time-zone gap between Chiang Mai and Luang Prabang. International itineraries are quoted in local time at each end, so a "midnight" departure in Chiang Mai typically lands the next morning in Luang Prabang. Customs clearance happens on first arrival in the destination country.

On the day of operation, the CNX to LPQ direction lifts off heading east, then the great-circle track curves to compensate for the Earth's rotation. The return LPQ to CNX sector heads west 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 Chiang Mai (CNX)

Other destinations served from the same origin. Handy for combining trips or for finding an alternate first leg.

Other routes into Luang Prabang (LPQ)

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.