Flight
VJC3901
Flight history and live tracking for VJC3901, 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 | ZGGG → VMMC |
Flight history 46 flights since Mar 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-21estimated | ? | ? | 16:50Z | 21:00Z | 4h 09m | 8881EF |
| 2026-08-20estimated | ? | ? | 20:53Z | 21:10Z | 0h 16m | 8881EF |
| 2026-08-19partial | ? | ? | 00:14Z | VN-A526 | ||
| 2026-08-17partial | ? | ? | 01:38Z | VN-A670 | ||
| 2026-08-15estimated | ? | ? | 08:31Z | 20:52Z | 12h 20m | 888218 |
| 2026-08-13estimated | ? | ? | 20:23Z | 20:40Z | 0h 16m | VN-A684 |
Earlier flights (40) - back to 2026-03-14
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-23partial | ? | ? | 02:37Z | VN-A674 | ||
| 2026-07-21estimated | ? | ? | 08:03Z | 21:10Z | 13h 07m | VN-A521 |
| 2026-07-18partial | ? | ? | 02:41Z | VN-A644 | ||
| 2026-07-17estimated | ? | ? | 18:08Z | 20:24Z | 2h 16m | VN-A684 |
| 2026-07-14estimated | VTBU | ? | 18:43 +07 | 20:58Z | 9h 14m | VN-A636 |
| 2026-07-13estimated | ? | ? | 02:47Z | 20:42Z | 17h 54m | VN-A698 |
| 2026-07-12estimated | ? | VMMC | 06:15Z | 04:38 CST | 14h 22m | VN-A532 |
| 2026-07-10estimated | ? | VMMC | 10:51Z | 04:20 CST | 9h 29m | VN-A535 |
| 2026-07-06estimated | ? | VMMC | 04:04Z | 04:50 CST | 16h 45m | 8881EF |
| 2026-07-05partial | ? | ? | 01:40Z | VN-A627 | ||
| 2026-07-04partial | WMBT | ? | 09:51 +08 | VN-A667 | ||
| 2026-07-03estimated | WMBT | VMMC | 16:06 +08 | 05:12 CST | 13h 05m | 8881EF |
| 2026-07-02estimated | WMBT | VMMC | 13:00 +08 | 04:40 CST | 15h 39m | 888219 |
| 2026-07-01partial | WMBT | ? | 09:29 +08 | VN-A629 | ||
| 2026-06-29partial | WMBT | ? | 09:35 +08 | VN-A673 | ||
| 2026-06-22estimated | ? | ? | 20:39Z | 20:58Z | 0h 18m | 8881F4 |
| 2026-06-21estimated | ZGGG | VMMC | 04:37 CST | 04:54 CST | 0h 16m | 888216 |
| 2026-06-18partial | ? | ? | 01:23Z | VN-A693 | ||
| 2026-05-27estimated | ZGGG | VMMC | 04:16 CST | 04:34 CST | 0h 17m | VN-A640 |
| 2026-05-24estimated | ZGGG | VMMC | 04:01 CST | 04:20 CST | 0h 18m | VN-A697 |
| 2026-05-20partial | WMBT | ? | 09:34 +08 | VN-A647 | ||
| 2026-05-07estimated | ZGGG | VMMC | 04:54 CST | 05:12 CST | 0h 18m | VN-A648 |
| 2026-05-06estimated | ZGGG | VMMC | 04:51 CST | 05:08 CST | 0h 16m | VN-A697 |
| 2026-05-05estimated | WMBT | VMMC | 14:33 +08 | 05:18 CST | 14h 45m | VN-A670 |
| 2026-05-04estimated | ZGGG | VMMC | 04:43 CST | 05:00 CST | 0h 16m | VN-A670 |
| 2026-05-03estimated | ZGGG | VMMC | 04:59 CST | 05:18 CST | 0h 18m | VN-A629 |
| 2026-05-02estimated | WMBT | VMMC | 20:10 +08 | 05:20 CST | 9h 09m | VN-A648 |
| 2026-04-30estimated | WMBT | VMMC | 11:59 +08 | 05:28 CST | 17h 28m | VN-A630 |
| 2026-04-28estimated | ZGGG | VMMC | 05:21 CST | 05:38 CST | 0h 16m | VN-A532 |
| 2026-04-26partial | RCTP | ? | 09:31 CST | 8881D9 | ||
| 2026-04-25estimated | ZGGG | VMMC | 04:31 CST | 04:50 CST | 0h 18m | 8881D9 |
| 2026-04-24estimated | ? | ? | 06:44Z | 21:48Z | 15h 03m | 8881FF |
| 2026-04-22estimated | ? | ? | 20:22Z | 20:42Z | 0h 19m | 8881FF |
| 2026-04-18estimated | ? | ? | 20:09Z | 20:26Z | 0h 16m | 8881F5 |
| 2026-04-16estimated | ? | ? | 20:13Z | 20:38Z | 0h 24m | VN-A646 |
| 2026-04-15estimated | ? | ? | 20:20Z | 20:38Z | 0h 17m | 8881EF |
| 2026-04-05estimated | ? | ? | 13:18Z | 20:24Z | 7h 05m | VN-A646 |
| 2026-04-02estimated | ? | ? | 03:16Z | 20:38Z | 17h 21m | VN-A523 |
| 2026-03-15estimated | ? | ? | 08:15Z | 20:28Z | 12h 12m | 8881FF |
| 2026-03-14estimated | ? | ? | 20:17Z | 20:36Z | 0h 18m | 8881FF |
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]