Flight
VJC826
Flight history and live tracking for VJC826, operated by VietJet Air. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | VietJet Air |
| Observed route | WMKK → VHSK |
Flight history 18 flights since Mar 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-21estimated | ? | ? | 05:54Z | 10:56Z | 5h 01m | VN-A523 |
| 2026-08-18estimated | ? | ? | 06:00Z | 10:30Z | 4h 29m | VN-A667 |
| 2026-08-15estimated | ? | ? | 05:55Z | 13:52Z | 7h 56m | VN-A646 |
| 2026-08-14estimated | ? | ? | 05:41Z | 13:34Z | 7h 52m | VN-A522 |
| 2026-08-13estimated | ? | ? | 05:49Z | 10:46Z | 4h 56m | VN-A629 |
Earlier flights (13) - back to 2026-03-30
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-18estimated | ? | ? | 05:57Z | 10:32Z | 4h 34m | VN-A639 |
| 2026-07-07partial | WMKK | ? | 13:47 +08 | 8881ED | ||
| 2026-07-05estimated | WMKK | VHSK | 13:59 +08 | 19:29 HKT | 5h 29m | VN-A648 |
| 2026-07-02partial | WMKK | ? | 14:05 +08 | 888224 | ||
| 2026-07-01partial | WMKK | ? | 14:02 +08 | VN-A673 | ||
| 2026-06-26partial | WMKK | ? | 13:57 +08 | VN-A607 | ||
| 2026-06-20estimated | WMKK | WMKM | 14:32 +08 | 18:31 +08 | 3h 58m | VN-A673 |
| 2026-06-19estimated | WMKK | VHSK | 13:55 +08 | 19:36 HKT | 5h 40m | VN-A526 |
| 2026-06-15partial | WMKK | ? | 13:47 +08 | VN-A646 | ||
| 2026-06-14partial | WMKK | ? | 10:58 +08 | VN-A640 | ||
| 2026-05-11partial | WMKK | ? | 14:22 +08 | VN-A646 | ||
| 2026-04-28partial | WMKK | ? | 13:50 +08 | VN-A607 | ||
| 2026-03-30partial | ? | ? | 02:26Z | VN-A524 |
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]