Flight
JNA425
Flight history and live tracking for JNA425, operated by Jin Air. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | Jin Air |
| Observed route | RKTN → RKJU |
Flight history 51 flights since Mar 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-21estimated | ? | ? | 05:21Z | 05:44Z | 0h 22m | HL8247 |
| 2026-08-20estimated | ? | ? | 04:49Z | 08:24Z | 3h 34m | HL7561 |
| 2026-08-19estimated | ? | ? | 04:42Z | 08:13Z | 3h 30m | HL7560 |
| 2026-08-18estimated | ? | ? | 05:10Z | 08:25Z | 3h 14m | HL8244 |
| 2026-08-16estimated | ? | ? | 04:54Z | 08:19Z | 3h 24m | HL8245 |
| 2026-08-15estimated | ? | ? | 05:01Z | 08:27Z | 3h 26m | HL8243 |
| 2026-08-14estimated | ? | ? | 04:52Z | 08:14Z | 3h 21m | HL7786 |
| 2026-08-13partial | RKTN | ? | 13:58 KST | HL7562 | ||
| 2026-08-12estimated | ? | ? | 04:42Z | 08:08Z | 3h 25m | HL8242 |
Earlier flights (42) - back to 2026-03-13
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-22estimated | ? | ? | 04:38Z | 08:02Z | 3h 24m | HL8244 |
| 2026-07-21estimated | ? | ? | 04:48Z | 06:57Z | 2h 08m | HL8017 |
| 2026-07-20estimated | ? | ? | 04:43Z | 08:10Z | 3h 26m | HL7560 |
| 2026-07-19partial | RKTN | ? | 13:51 KST | HL7560 | ||
| 2026-07-18estimated | ? | ? | 04:46Z | 08:17Z | 3h 31m | HL7562 |
| 2026-07-17estimated | ? | ? | 04:52Z | 05:12Z | 0h 19m | HL8247 |
| 2026-07-16estimated | ? | ? | 04:44Z | 08:16Z | 3h 31m | HL7560 |
| 2026-06-28partial | RKTN | ? | 13:44 KST | HL7561 | ||
| 2026-06-26partial | RKTN | ? | 13:46 KST | HL8015 | ||
| 2026-06-24estimated | RKTN | ? | 13:51 KST | 05:16Z | 0h 25m | HL7562 |
| 2026-06-23partial | RKTN | ? | 13:46 KST | HL8242 | ||
| 2026-06-21partial | RKTN | ? | 13:47 KST | HL8015 | ||
| 2026-06-19partial | RKTN | ? | 13:59 KST | HL7757 | ||
| 2026-06-17partial | RKTN | ? | 14:10 KST | HL7562 | ||
| 2026-06-16partial | RKTN | ? | 13:46 KST | HL7562 | ||
| 2026-06-14partial | RKTN | ? | 13:45 KST | HL7786 | ||
| 2026-06-12partial | RKTN | ? | 13:51 KST | HL8244 | ||
| 2026-05-28partial | RKTN | ? | 13:41 KST | HL8242 | ||
| 2026-05-25partial | RKTN | ? | 13:50 KST | HL7786 | ||
| 2026-05-24partial | RKTN | ? | 14:18 KST | HL7786 | ||
| 2026-05-23partial | RKTN | ? | 13:43 KST | HL8244 | ||
| 2026-05-22estimated | ? | ? | 05:20Z | 08:55Z | 3h 34m | HL8244 |
| 2026-05-19partial | RKTN | ? | 11:09 KST | HL8242 | ||
| 2026-05-12partial | RKTN | ? | 13:47 KST | HL8242 | ||
| 2026-05-11partial | RKTN | ? | 13:58 KST | HL8016 | ||
| 2026-05-10estimated | RKTN | RKJU | 13:48 KST | 17:24 KST | 3h 35m | HL7786 |
| 2026-05-09partial | RKTN | ? | 14:05 KST | HL8242 | ||
| 2026-05-08partial | RKTN | ? | 13:45 KST | HL8246 | ||
| 2026-05-07partial | RKTN | ? | 13:34 KST | HL7561 | ||
| 2026-05-05partial | RKTN | ? | 13:42 KST | HL8242 | ||
| 2026-05-04partial | RKTN | ? | 13:47 KST | HL7561 | ||
| 2026-05-03partial | RKTN | ? | 13:48 KST | HL8013 | ||
| 2026-05-02partial | RKTN | ? | 13:44 KST | HL8247 | ||
| 2026-05-01partial | RKTN | ? | 13:55 KST | HL7561 | ||
| 2026-04-26estimated | RKTN | RKJK | 13:47 KST | 18:04 KST | 4h 16m | HL8245 |
| 2026-04-19estimated | ? | ? | 05:13Z | 08:53Z | 3h 39m | HL8247 |
| 2026-04-16estimated | ? | ? | 04:52Z | 08:56Z | 4h 03m | HL8245 |
| 2026-04-12partial | RKTN | ? | 14:02 KST | HL8015 | ||
| 2026-04-05partial | RKTN | ? | 13:53 KST | HL8015 | ||
| 2026-04-03partial | RKTN | ? | 13:53 KST | 71C569 | ||
| 2026-03-29partial | RKTN | ? | 14:00 KST | HL8224 | ||
| 2026-03-13partial | RKTN | ? | 10:01 KST | HL7718 |
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.
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]