| Date | Flight | Origin | STD | ATD | Destination | STA | Delay | Status | Duration | Replay |
|---|---|---|---|---|---|---|---|---|---|---|
Current | ||||||||||
| 2026 Feb 10 | Shenzhen (SZX/ZGSZ) | 04:01 CST | Tokyo Narita (NRT/RJAA) | 08:24 JST | Est. Arrival 08:24 JST | |||||
Past | ||||||||||
| 2026 Feb 9 | Tokyo Narita (NRT/RJAA) | 22:15 JST | Shenzhen (SZX/ZGSZ) | 02:16 CST | Landed 01:52 CST Landing time derived from ADS-B/Radar data | 04h37m | ||||
| 2026 Feb 9 | Osaka (KIX/RJBB) | 18:57 JST | Tokyo Narita (NRT/RJAA) | 19:55 JST | Landed 19:59 JST Landing time derived from ADS-B/Radar data | 01h02m | ||||
| 2026 Feb 9 | Tokyo Narita (NRT/RJAA) | 09:04 JST | Osaka (KIX/RJBB) | 10:12 JST | Landed 10:21 JST Landing time derived from ADS-B/Radar data | 01h16m | ||||
| 2026 Feb 9 | Shenzhen (SZX/ZGSZ) | 02:21 CST | Tokyo Narita (NRT/RJAA) | 06:43 JST | Landed 06:49 JST Landing time derived from ADS-B/Radar data | 03h27m | ||||
| 2026 Feb 7 | Seoul (ICN/RKSI) | 23:44 KST | Shenzhen (SZX/ZGSZ) | 02:19 CST | Landed 02:23 CST Landing time derived from ADS-B/Radar data | 03h39m | ||||
| 2026 Feb 7 | Zhengzhou (CGO/ZHCC) | 19:00 CST | Seoul (ICN/RKSI) | 21:46 KST | Landed 21:48 KST Landing time derived from ADS-B/Radar data | 01h48m | ||||
| 2026 Feb 7 | Seoul (ICN/RKSI) | 15:21 KST | Zhengzhou (CGO/ZHCC) | 16:33 CST | Landed 16:32 CST Landing time derived from ADS-B/Radar data | 02h11m | ||||
| 2026 Feb 6 | Anchorage, AK (ANC/PANC) | 08:48 AKST | 09:33 AKST | Seoul (ICN/RKSI) | Landed 12:43 KST Landing time derived from ADS-B/Radar data | 09h09m | ||||
| 2026 Feb 6 | Louisville, KY (SDF/KSDF) | 03:49 EST | 04:20 EST | Anchorage, AK (ANC/PANC) | 07:10 AKST | Landed 07:26 AKST Landing time derived from ADS-B/Radar data | 07h05m | |||
| 2026 Feb 5 | London Stansted (STN/EGSS) | 20:45 GMT | 20:43 GMT | Louisville, KY (SDF/KSDF) | 23:49 EST | Landed 23:58 EST Landing time derived from ADS-B/Radar data | 08h01m | |||
| 2026 Feb 5 | Cologne (CGN/EDDK) | 03:29 CET | 03:20 CET | London Stansted (STN/EGSS) | 03:37 GMT | Landed 03:38 GMT Landing time derived from ADS-B/Radar data | 00h56m | |||
| 2026 Feb 4 | Nottingham (EMA/EGNX) | 21:51 GMT | 21:51 GMT | Cologne (CGN/EDDK) | 00:08 CET | Landed 00:07 CET Landing time derived from ADS-B/Radar data | 01h06m | |||
| 2026 Feb 4 | Philadelphia, PA (PHL/KPHL) | 08:43 EST | 08:48 EST | Nottingham (EMA/EGNX) | 20:04 GMT | Landed 20:17 GMT Landing time derived from ADS-B/Radar data | 06h29m | |||
| 2026 Feb 4 | Nottingham (EMA/EGNX) | 04:19 GMT | 04:06 GMT | Philadelphia, PA (PHL/KPHL) | 06:15 EST | Landed 06:22 EST Landing time derived from ADS-B/Radar data | 07h06m | |||
| 2026 Feb 4 | Cologne (CGN/EDDK) | 02:08 CET | 02:04 CET | Nottingham (EMA/EGNX) | 02:21 GMT | Landed 02:21 GMT Landing time derived from ADS-B/Radar data | 00h56m | |||
| 2026 Feb 3 | Dublin (DUB/EIDW) | 21:25 GMT | 21:04 GMT | Cologne (CGN/EDDK) | 23:55 CET | Landed 23:56 CET Landing time derived from ADS-B/Radar data | 01h30m | |||
| 2026 Feb 3 | Shannon (SNN/EINN) | 19:55 GMT | 19:40 GMT | Dublin (DUB/EIDW) | 20:20 GMT | Landed 20:19 GMT Landing time derived from ADS-B/Radar data | 00h29m | |||
| 2026 Feb 3 | Dublin (DUB/EIDW) | 05:40 GMT | 05:20 GMT | Shannon (SNN/EINN) | 06:16 GMT | Landed 06:15 GMT Landing time derived from ADS-B/Radar data | 00h33m | |||
| 2026 Feb 3 | Cologne (CGN/EDDK) | 04:02 CET | 04:06 CET | Dublin (DUB/EIDW) | 04:46 GMT | Landed 04:45 GMT Landing time derived from ADS-B/Radar data | 01h24m | |||
Flight history for N353UP is available for a period over 7 days under our Basic subscription. More details here
More airport data is available for purchase. Please check our On Demand API.
Facebook
X