ICNNRT
Seoul to Narita
Direct and one-stop flights from Incheon International Airport (ICN) to Narita International Airport (NRT), 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 Seoul to Narita.
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 Seoul to Narita
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 Narita 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
- 2h 55m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 01m on average.
- Journey
- 2h 25m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 09m on average.
- Journey
- 2h 25m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 09m on average.
- Journey
- 2h 40m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 15m on average.
- Journey
- 2h 40m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 09m on average.
- Journey
- 2h 25m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 10m on average.
- Journey
- 2h 30m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 05m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 12m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 16m on average.
- Journey
- 2h 35m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 15m on average.
- Journey
- 2h 30m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 26m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 02m on average.
- Journey
- 2h 25m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 18m on average.
- Journey
- 2h 30m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 17m on average.
- Journey
- 2h 25m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 10m on average.
- Journey
- 1h 46m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 46m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 08m on average.
- Journey
- 2h 35m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 05m on average.
- Journey
- 2h 25m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 12m on average.
- Journey
- 2h 23m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 13m on average.
- Journey
- 1h 48m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 48m on average.
- Journey
- 2h 35m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 33m on average.
- Journey
- 2h 25m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 59m on average.
- Journey
- 2h 25m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 27m on average.
- Journey
- 2h 25m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 11m on average.
- Journey
- 2h 25m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 58m on average.
- Journey
- 2h 35m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 18m on average.
- Journey
- 2h 50m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 22m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 17m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 17m on average.
- Journey
- 2h 35m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 07m on average.
- Journey
- 2h 25m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 08m on average.
- Journey
- 2h 25m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 02m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 47m on average.
- Journey
- 2h 30m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 21m on average.
- Journey
- 2h 30m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 56m on average.
- Journey
- 2h 25m
- Arrived on time
- 100%
- Flies
- Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 02m on average.
- 1h 40m stopover in Sapporo · Two airlines: book on one ticket
What this means
These flights are on different airlines. Book them together on one ticket so that if the first flight is late, the airline has to get you on a later flight. On separate tickets, a missed connection is your cost, and you'd usually collect your bags and check in again.
- Journey
- 6h 10m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 6h 01m on average.
- 2h 30m stopover in Fukuoka · Two airlines: book on one ticket
What this means
These flights are on different airlines. Book them together on one ticket so that if the first flight is late, the airline has to get you on a later flight. On separate tickets, a missed connection is your cost, and you'd usually collect your bags and check in again.
- Journey
- 5h 50m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 5h 41m on average.
- 5h 55m stopover in Fukuoka · Two airlines: book on one ticket
What this means
These flights are on different airlines. Book them together on one ticket so that if the first flight is late, the airline has to get you on a later flight. On separate tickets, a missed connection is your cost, and you'd usually collect your bags and check in again.
- Journey
- 9h 15m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 9h 10m on average.
- 2h 10m stopover in Fukuoka · Two airlines: book on one ticket
What this means
These flights are on different airlines. Book them together on one ticket so that if the first flight is late, the airline has to get you on a later flight. On separate tickets, a missed connection is your cost, and you'd usually collect your bags and check in again.
- Journey
- 5h 30m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 5h 21m on average.
- 5h 35m stopover in Fukuoka · Two airlines: book on one ticket
What this means
These flights are on different airlines. Book them together on one ticket so that if the first flight is late, the airline has to get you on a later flight. On separate tickets, a missed connection is your cost, and you'd usually collect your bags and check in again.
- Journey
- 8h 55m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 8h 50m on average.
- 1h 40m stopover in Hong Kong · Two airlines: book on one ticket
What this means
These flights are on different airlines. Book them together on one ticket so that if the first flight is late, the airline has to get you on a later flight. On separate tickets, a missed connection is your cost, and you'd usually collect your bags and check in again.
- Journey
- 9h 55m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 9h 31m on average.
- 2h 15m stopover in Shanghai
- Journey
- 7h 30m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 7h 23m on average.
- 2h 00m stopover in Shanghai
- Journey
- 7h 00m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 6h 53m on average.
- Journey
- 2h 15m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 42m on average.
- Journey
- 2h 20m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 36m on average.
- Journey
- 2h 30m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 33m on average.
- 1h 40m stopover in Sapporo · Two airlines: book on one ticket
What this means
These flights are on different airlines. Book them together on one ticket so that if the first flight is late, the airline has to get you on a later flight. On separate tickets, a missed connection is your cost, and you'd usually collect your bags and check in again.
- Journey
- 6h 10m
- Arrived on time
- 50%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 7h 41m on average.
- 2h 25m stopover in Sapporo · Two airlines: book on one ticket
What this means
These flights are on different airlines. Book them together on one ticket so that if the first flight is late, the airline has to get you on a later flight. On separate tickets, a missed connection is your cost, and you'd usually collect your bags and check in again.
- Journey
- 6h 50m
- Arrived on time
- 50%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 6h 54m on average.
- 3h 20m stopover in Sapporo · Two airlines: book on one ticket
What this means
These flights are on different airlines. Book them together on one ticket so that if the first flight is late, the airline has to get you on a later flight. On separate tickets, a missed connection is your cost, and you'd usually collect your bags and check in again.
- Journey
- 7h 50m
- Arrived on time
- 50%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 7h 53m on average.
- 1h 30m stopover in Sapporo · Two airlines: book on one ticket
What this means
These flights are on different airlines. Book them together on one ticket so that if the first flight is late, the airline has to get you on a later flight. On separate tickets, a missed connection is your cost, and you'd usually collect your bags and check in again.
- Journey
- 6h 00m
- Arrived on time
- 50%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 6h 04m on average.
- Journey
- 2h 20m
- Arrived on time
- 0%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 42m on average.
- Journey
- 2h 25m
- Arrived on time
- 0%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 3h 05m on average.
- Journey
- 2h 20m
- Arrived on time
- 0%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 55m on average.
Direct flights by airline
| Rank | Airline | Verdict | On time | Late | Cancelled | Typical delay when late | Passengers | Crew service |
|---|---|---|---|---|---|---|---|---|
| 1 | Jeju Air 7C1101, 7C1103, 7C1107, 7C1109, 7C1125, 7C1181, 7C1183, 7C1187 · also sold as JL5204, OZ9847 | 10.0 | 100% | 0 of 13 | 0 | — | No ratings yet | — |
| Air Busan BX223, BX265 · also sold as KE5739 | No score yet | 100% | 0 of 3 | 0 | — | No ratings yet | — | |
| Ethiopian Airlines ET672 | No score yet | 100% | 0 of 1 | 0 | — | No ratings yet | — | |
| Korean Air KE703, KE705, KE707, KE711, KE713 · also sold as AF5376, AF5378, AF7904, AM6700, AM6705, AM6752, DL7781, DL7895, DL7897, JL5204, JL5206, JL5250, JL5252, NH5340, OZ9845, OZ9847, OZ9849, OZ9851, TN1575, VS5503, VS5541 | No score yet | 86% | 1 of 7 | 0 | 21 min | No ratings yet | — | |
| British Mediterranean Airways KJ1941 | No score yet | 100% | 0 of 1 | 0 | — | No ratings yet | — | |
| Jin Air LJ211, LJ235, LJ263, LJ5263 · also sold as KE5739 | No score yet | 83% | 1 of 6 | 0 | 40 min | No ratings yet | — | |
| Peach Aviation MM642 | No score yet | 100% | 0 of 2 | 0 | — | No ratings yet | — | |
| All Nippon Airways NH8476 | No score yet | 100% | 0 of 1 | 0 | — | No ratings yet | — | |
| Asiana Airlines OZ102, OZ106, OZ108 · also sold as EY8453, EY8455, KE5497, KE5703, NH6972, NH6978, NZ4060, UA7297, UA7318 | No score yet | 25% | 3 of 4 | 0 | 27 min | No ratings yet | — | |
| Sky Regional RS247, RS259, RS267 | No score yet | 80% | 1 of 5 | 0 | 43 min | No ratings yet | — | |
| Tway Airlines TW241, TW243, TW245, TW247, TW249 · also sold as EY8454, KE5495, NH6976, NZ4056, UA7322 | No score yet | 100% | 0 of 7 | 0 | — | No ratings yet | — | |
| Thai Smile Airways WE501, WE503 · also sold as AM6750, DL7779, JL5202, OZ9843, TN1577 | No score yet | 100% | 0 of 4 | 0 | — | No ratings yet | — | |
| Perimeter Aviation YP731 | No score yet | 100% | 0 of 2 | 0 | — | No ratings yet | — | |
| Eastar Jet ZE601, ZE603, ZE605, ZE607 · also sold as KE5741 | No score yet | 100% | 0 of 6 | 0 | — | No ratings yet | — | |
| Viva Macau ZG44, ZG46 | No score yet | 100% | 0 of 3 | 0 | — | 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 Seoul to Narita?
Over the past 30 days, Jeju Air had the best record on this route, arriving on time on 100% of 13 flights.
Which airlines fly direct from Seoul to Narita?
Jeju Air (7C1101, 7C1103, 7C1107, 7C1109, 7C1125, 7C1181, 7C1183, 7C1187), Air Busan (BX223, BX265), Ethiopian Airlines (ET672), Korean Air (KE703, KE705, KE707, KE711, KE713), British Mediterranean Airways (KJ1941), Jin Air (LJ211, LJ235, LJ263, LJ5263), Peach Aviation (MM642), All Nippon Airways (NH8476), Asiana Airlines (OZ102, OZ106, OZ108), Sky Regional (RS247, RS259, RS267), Tway Airlines (TW241, TW243, TW245, TW247, TW249), Thai Smile Airways (WE501, WE503), Perimeter Aviation (YP731), Eastar Jet (ZE601, ZE603, ZE605, ZE607), Viva Macau (ZG44, ZG46).