BKKCNX
Bangkok to Chiang Mai
Direct and one-stop flights from Suvarnabhumi Airport (BKK) to Chiang Mai International Airport (CNX), ranked by how reliably they actually get you there.
Our recommendation
Not enough flight history yet to recommend a journey
We don't have enough flight history yet to recommend a way to fly from Bangkok to Chiang Mai.
Flexible on dates?
Pick a range of up to 14 days and we'll tell you the best day to fly, and the most reliable journey that actually operates on each date.
Every way to fly Bangkok to Chiang Mai
Past 30 days. Direct flights and one-stop journeys, ranked by how reliably they actually got passengers there. A journey is on time if it reached Chiang Mai within 15 minutes of schedule; a missed connection counts as late.
Live prices aren't connected in this preview yet. When they are, each journey shows its lowest current fare for the date you pick. Prices never affect our recommendation.
- Journey
- 1h 20m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 29m on average.
- Journey
- 1h 20m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 00m on average.
- Journey
- 1h 20m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 11m on average.
- Journey
- 1h 20m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 15m on average.
- Journey
- 1h 30m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 11m on average.
- Journey
- 1h 20m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 30m on average.
- Journey
- 1h 20m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 24m on average.
- Journey
- 1h 25m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 18m on average.
- Journey
- 1h 20m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 10m on average.
- Journey
- 1h 15m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 23m on average.
- Journey
- 1h 25m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 14m on average.
- Journey
- 1h 20m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 12m on average.
- Journey
- 1h 20m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 29m on average.
- Journey
- 1h 20m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 27m on average.
- Journey
- 1h 15m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 28m on average.
- Journey
- 1h 20m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 28m on average.
- Journey
- 1h 35m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 49m on average.
- Journey
- 1h 20m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 25m on average.
- Journey
- 1h 20m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 21m on average.
- Journey
- 1h 30m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 19m on average.
- Journey
- 1h 30m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 40m on average.
- Journey
- 1h 35m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 13m on average.
- Journey
- 1h 25m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 37m on average.
- Journey
- 1h 25m
- Arrived on time
- 0%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 00m on average.
- Journey
- 1h 25m
- Arrived on time
- 0%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; 1 cancelled.
- Journey
- 1h 25m
- Arrived on time
- 0%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; 1 cancelled.
- Journey
- 1h 25m
- Arrived on time
- 0%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; 1 cancelled.
- Journey
- 1h 30m
- Arrived on time
- 0%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 51m on average.
- Journey
- 1h 15m
- Arrived on time
- 0%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 31m on average.
- Journey
- 1h 20m
- Arrived on time
- 0%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 07m on average.
- Journey
- 1h 20m
- Arrived on time
- 0%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 47m on average.
Direct flights by airline
| Rank | Airline | Verdict | On time | Late | Cancelled | Typical delay when late | Passengers | Crew service |
|---|---|---|---|---|---|---|---|---|
| 1 | Thai Airways International TG100, TG102, TG104, TG106, TG110, TG112, TG114, TG120, TG122 | 8.3 | 83% | 3 of 18 | 0 | 22 min | No ratings yet | — |
| 2 | Thai AirAsia FD4096, FD4100, FD4102, FD4104, FD4106, FD4108, FD8206, FD9162 | 5.0 | 50% | 4 of 16 | 4 | 36 min | No ratings yet | — |
| 3 | MyTravel Airways VZ100, VZ102, VZ104, VZ106, VZ108, VZ110, VZ114, VZ116, VZ118, VZ122, VZ2104, VZ2106 | 5.0 | 50% | 6 of 22 | 5 | 1h 17m | No ratings yet | — |
| Bangkok Airways PG215, PG219, PG223, PG225 | No score yet | 75% | 2 of 8 | 0 | 23 min | No ratings yet | — |
On-time record over time
Not enough flights yet to show a trend.
Questions travellers ask
Which airline is most on time from Bangkok to Chiang Mai?
Over the past 30 days, Thai Airways International had the best record on this route, arriving on time on 83% of 18 flights.
Which airlines fly direct from Bangkok to Chiang Mai?
Thai Airways International (TG100, TG102, TG104, TG106, TG110, TG112, TG114, TG120, TG122), Thai AirAsia (FD4096, FD4100, FD4102, FD4104, FD4106, FD4108, FD8206, FD9162), MyTravel Airways (VZ100, VZ102, VZ104, VZ106, VZ108, VZ110, VZ114, VZ116, VZ118, VZ122, VZ2104, VZ2106), Bangkok Airways (PG215, PG219, PG223, PG225).
How often are Thai AirAsia flights from Bangkok to Chiang Mai late?
4 of 16 flights arrived more than 15 minutes late over the past 30 days. When late, the typical delay was 36 min.