Flight
JAL2720
Flight history and live tracking for JAL2720, operated by Japan Airlines. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | Japan Airlines |
| Typical origin | RJCM MEMANBETSU |
| Typical destination | RJCO SAPPORO |
| Distance | 130 nm |
Flight history 70 flights since Aug 2025
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| No flights in the last 30 days. | ||||||
Earlier flights (70) - back to 2025-08-17
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-03-11 | RJCM | RJCO | 10:28 JST | 11:04 JST | 0h 35m | JA11HC |
| 2026-03-10 | RJCM | RJCO | 10:22 JST | 10:58 JST | 0h 35m | 846A16 |
| 2026-03-09 | RJCM | RJCO | 10:25 JST | 11:02 JST | 0h 37m | JA11HC |
| 2026-03-06 | RJCM | RJCO | 10:32 JST | 11:10 JST | 0h 38m | JA12HC |
| 2026-03-05 | RJCM | RJCO | 10:27 JST | 11:02 JST | 0h 34m | JA11HC |
| 2026-03-04 | RJCM | RJCO | 11:03 JST | 11:42 JST | 0h 38m | 846A16 |
| 2026-03-03 | RJCM | RJCO | 10:16 JST | 10:52 JST | 0h 35m | 846A16 |
| 2026-03-02 | RJCM | RJCO | 10:19 JST | 10:56 JST | 0h 37m | 846A16 |
| 2026-03-01estimated | ? | RJCO | 02:07Z | 11:44 JST | 0h 37m | JA12HC |
| 2026-02-28 | RJCM | RJCO | 11:10 JST | 11:50 JST | 0h 39m | JA12HC |
| 2026-02-27 | RJCM | RJCO | 09:54 JST | 10:36 JST | 0h 41m | 846A16 |
| 2026-02-26 | RJCM | RJCO | 09:55 JST | 10:34 JST | 0h 38m | 846A16 |
| 2026-02-25 | RJCM | RJCO | 09:47 JST | 10:28 JST | 0h 41m | JA12HC |
| 2026-02-24estimated | RJCO | ? | 11:14 JST | 03:14Z | 0h 59m | 846A16 |
| 2026-02-24 | RJCM | RJCO | 09:50 JST | 10:34 JST | 0h 43m | 846A16 |
| 2026-02-23 | RJCM | RJCO | 09:57 JST | 10:44 JST | 0h 46m | JA11HC |
| 2026-02-22 | RJCM | RJCO | 09:58 JST | 10:38 JST | 0h 39m | JA12HC |
| 2026-02-21 | RJCM | RJCO | 11:26 JST | 12:06 JST | 0h 39m | JA12HC |
| 2026-02-20 | RJCM | RJCO | 09:55 JST | 10:32 JST | 0h 36m | JA11HC |
| 2026-02-17estimated | ? | RJCO | 01:12Z | 10:32 JST | 0h 19m | 846A16 |
| 2026-02-16estimated | ? | RJCO | 02:15Z | 11:32 JST | 0h 16m | JA12HC |
| 2026-02-13estimated | ? | RJCO | 01:16Z | 10:36 JST | 0h 20m | 846A16 |
| 2026-02-12 | RJCM | RJCO | 10:08 JST | 10:50 JST | 0h 41m | 846A16 |
| 2026-02-11 | RJCM | RJCO | 09:52 JST | 10:34 JST | 0h 41m | 846A16 |
| 2026-02-07 | RJCM | RJCO | 11:34 JST | 12:10 JST | 0h 35m | 846A16 |
| 2026-02-06 | RJCM | RJCO | 09:50 JST | 10:36 JST | 0h 45m | JA11HC |
| 2026-02-05 | RJCM | RJCO | 09:57 JST | 10:38 JST | 0h 40m | JA12HC |
| 2026-02-04 | RJCM | RJCO | 09:52 JST | 10:32 JST | 0h 39m | 846A16 |
| 2026-02-03 | RJCM | RJCO | 10:04 JST | 10:42 JST | 0h 37m | JA12HC |
| 2026-02-02 | RJCM | RJCO | 09:54 JST | 10:32 JST | 0h 37m | JA12HC |
| 2026-01-30 | RJCM | RJCO | 09:48 JST | 10:24 JST | 0h 35m | JA11HC |
| 2026-01-29 | RJCM | RJCO | 09:52 JST | 10:28 JST | 0h 35m | 846A16 |
| 2026-01-28 | RJCM | RJCO | 10:07 JST | 10:44 JST | 0h 36m | JA11HC |
| 2026-01-27 | RJCM | RJCO | 09:53 JST | 10:32 JST | 0h 38m | JA11HC |
| 2026-01-24 | RJCM | RJCO | 09:52 JST | 10:32 JST | 0h 40m | JA01JC |
| 2026-01-23 | RJCM | RJCO | 10:03 JST | 10:40 JST | 0h 36m | JA01JC |
| 2026-01-22 | RJCM | RJCO | 10:02 JST | 10:40 JST | 0h 37m | JA01JC |
| 2026-01-20 | RJCM | RJCO | 09:47 JST | 10:26 JST | 0h 38m | JA01JC |
| 2026-01-19 | RJCM | RJCO | 09:49 JST | 10:30 JST | 0h 41m | JA01JC |
| 2026-01-09 | RJCM | RJCO | 10:01 JST | 10:42 JST | 0h 40m | JA01JC |
| 2026-01-08estimated | RJCM | ? | 10:27 JST | 02:30Z | 1h 02m | JA01JC |
| 2026-01-07 | RJCM | RJCO | 09:48 JST | 10:28 JST | 0h 40m | JA11HC |
| 2026-01-06 | RJCM | RJCO | 09:53 JST | 10:32 JST | 0h 38m | JA01JC |
| 2026-01-05 | RJCM | RJCO | 09:59 JST | 10:40 JST | 0h 40m | JA01JC |
| 2026-01-04 | RJCM | RJCO | 09:56 JST | 10:38 JST | 0h 41m | JA11HC |
| 2026-01-03 | RJCM | RJCO | 10:10 JST | 10:46 JST | 0h 36m | JA01JC |
| 2026-01-02 | RJCM | RJCO | 10:39 JST | 11:14 JST | 0h 34m | JA11HC |
| 2026-01-01 | RJCM | RJCO | 09:53 JST | 10:50 JST | 0h 56m | JA01JC |
| 2025-12-31 | RJCM | RJCO | 10:04 JST | 10:42 JST | 0h 38m | JA01JC |
| 2025-12-30 | RJCM | RJCO | 10:00 JST | 10:46 JST | 0h 45m | JA01JC |
| 2025-12-29 | RJCM | RJCO | 09:52 JST | 10:36 JST | 0h 43m | JA01JC |
| 2025-12-28 | RJCM | RJCO | 09:59 JST | 10:40 JST | 0h 41m | JA01JC |
| 2025-12-27 | RJCM | RJCO | 10:05 JST | 10:50 JST | 0h 44m | JA11HC |
| 2025-12-26 | RJCM | RJCO | 10:12 JST | 10:52 JST | 0h 39m | JA01JC |
| 2025-12-25 | RJCM | RJCO | 09:52 JST | 10:32 JST | 0h 39m | JA13HC |
| 2025-12-24 | RJCM | RJCO | 09:49 JST | 10:32 JST | 0h 42m | JA04JC |
| 2025-12-23 | RJCM | RJCO | 09:52 JST | 10:32 JST | 0h 39m | JA04JC |
| 2025-12-22 | RJCM | RJCO | 09:56 JST | 10:34 JST | 0h 37m | JA04JC |
| 2025-12-21 | RJCM | RJCO | 09:43 JST | 10:26 JST | 0h 42m | JA01JC |
| 2025-12-20 | RJCM | RJCO | 09:51 JST | 10:38 JST | 0h 47m | JA01JC |
| 2025-12-19 | RJCM | RJCO | 09:53 JST | 10:34 JST | 0h 40m | JA04JC |
| 2025-12-18 | RJCM | RJCO | 09:50 JST | 10:30 JST | 0h 39m | JA04JC |
| 2025-12-17 | RJCM | RJCO | 11:19 JST | 12:08 JST | 0h 48m | JA04JC |
| 2025-12-16 | RJCM | RJCO | 11:11 JST | 11:58 JST | 0h 46m | JA01JC |
| 2025-12-14 | RJCM | RJCO | 09:53 JST | 10:28 JST | 0h 34m | JA04JC |
| 2025-12-13 | RJCM | RJCO | 09:57 JST | 10:36 JST | 0h 38m | JA01JC |
| 2025-12-12 | RJCM | RJCO | 09:57 JST | 10:38 JST | 0h 41m | JA01JC |
| 2025-12-11 | RJCM | RJCO | 09:51 JST | 10:36 JST | 0h 44m | JA04JC |
| 2025-12-10 | RJCM | RJCO | 09:50 JST | 10:32 JST | 0h 41m | 846A16 |
| 2025-08-17estimated | RJCM | ? | 14:47 JST | 06:04Z | 0h 16m | 846A16 |
Times are local to each airport. Hover for UTC. Flights marked estimated were completed with route prediction or partial coverage; partial records have a confirmed departure but no reliable arrival fix.
Follow this flight
Get an email when JAL2720 flies + if it runs late.
Data access
Live positions and 365-day history for this flight are available through the PlaneTrack API (commercial use from $29/month) and as one-off CSV extracts from our archive (from $9.99, with a free one-day sample). Questions: [email protected]