Flight
JAL3918
Flight history and live tracking for JAL3918. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Flight history 16 flights since Dec 2025
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| No flights in the last 30 days. | ||||||
Earlier flights (16) - back to 2025-12-19
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-01-04 | RJCC | RJOY | 16:03 JST | 17:36 JST | 1h 32m | 851186 |
| 2026-01-03 | RJCJ | RJNT | 16:10 JST | 17:11 JST | 1h 00m | 851C64 |
| 2026-01-02 | RJCC | RJOY | 16:45 JST | 18:22 JST | 1h 36m | 8514D6 |
| 2025-12-31 | RJCC | RJOY | 16:15 JST | 17:48 JST | 1h 32m | 851230 |
| 2025-12-30 | RJCC | RJOO | 16:59 JST | 18:37 JST | 1h 38m | 851BDC |
| 2025-12-29 | RJCC | RJOY | 16:32 JST | 18:11 JST | 1h 39m | 850E58 |
| 2025-12-28 | RJCC | RJOY | 16:10 JST | 17:33 JST | 1h 22m | 851914 |
| 2025-12-27 | RJCC | RJOO | 16:23 JST | 17:58 JST | 1h 34m | 850E58 |
| 2025-12-26 | RJCC | RJOY | 17:26 JST | 18:58 JST | 1h 31m | 850D8C |
| 2025-12-25 | RJCC | RJOY | 16:26 JST | 18:13 JST | 1h 47m | 850E7A |
| 2025-12-24 | RJCC | RJOY | 16:21 JST | 17:57 JST | 1h 36m | 851826 |
| 2025-12-23 | RJCC | RJOO | 16:07 JST | 17:44 JST | 1h 36m | 851CA8 |
| 2025-12-22 | RJCC | RJOY | 16:06 JST | 17:39 JST | 1h 32m | 8514F8 |
| 2025-12-21 | RJCC | RJOO | 16:55 JST | 18:48 JST | 1h 52m | 8515C4 |
| 2025-12-20 | RJCC | RJOO | 16:42 JST | 18:13 JST | 1h 30m | 850DAE |
| 2025-12-19 | RJCC | RJOY | 16:09 JST | 17:38 JST | 1h 28m | 850D8C |
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 JAL3918 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 own receiver network archive. Questions: [email protected]