Flight
PIC6344
Flight history and live tracking for PIC6344, operated by Jetstar Pacific. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | Jetstar Pacific |
| Typical origin | VVCT Can Tho International Airport |
| Typical destination | VVNB NOIBAI INTERNATIONAL |
| Distance | 669 nm |
Flight history 82 flights since Mar 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-21estimated | ? | ? | 10:33Z | 12:14Z | 1h 41m | VN-A363 |
| 2026-08-19estimated | ? | ? | 10:27Z | 10:50Z | 0h 22m | VN-A363 |
| 2026-08-16estimated | ? | ? | 10:01Z | 11:50Z | 1h 48m | VN-A363 |
| 2026-08-15estimated | ? | ? | 10:02Z | 11:49Z | 1h 47m | VN-A363 |
| 2026-08-13estimated | ? | ? | 10:03Z | 10:22Z | 0h 18m | VN-A363 |
| 2026-08-12estimated | ? | ? | 10:07Z | 12:07Z | 2h 00m | VN-A363 |
Earlier flights (76) - back to 2026-03-29
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-23estimated | ? | ? | 09:41Z | 11:48Z | 2h 07m | VN-A354 |
| 2026-07-22estimated | ? | ? | 10:12Z | 11:56Z | 1h 43m | VN-A363 |
| 2026-07-21estimated | ? | ? | 10:00Z | 10:18Z | 0h 17m | VN-A363 |
| 2026-07-20estimated | ? | ? | 10:20Z | 11:57Z | 1h 37m | VN-A363 |
| 2026-07-19estimated | ? | ? | 10:46Z | 11:12Z | 0h 25m | VN-A363 |
| 2026-07-18estimated | ? | ? | 10:15Z | 11:39Z | 1h 23m | VN-A363 |
| 2026-07-17estimated | ? | ? | 10:10Z | 12:01Z | 1h 50m | VN-A363 |
| 2026-07-16estimated | ? | ? | 10:44Z | 12:17Z | 1h 32m | VN-A359 |
| 2026-07-14partial | VVNB | ? | 17:09 +07 | VN-A363 | ||
| 2026-07-12partial | VVNB | ? | 16:50 +07 | VN-A363 | ||
| 2026-07-11partial | VVNB | ? | 16:59 +07 | VN-A363 | ||
| 2026-07-09partial | VVNB | ? | 17:09 +07 | VN-A363 | ||
| 2026-07-08partial | VVNB | ? | 17:24 +07 | VN-A363 | ||
| 2026-07-07partial | VVNB | ? | 17:01 +07 | VN-A363 | ||
| 2026-07-06partial | VVNB | ? | 17:03 +07 | VN-A363 | ||
| 2026-07-05partial | VVNB | ? | 17:00 +07 | VN-A363 | ||
| 2026-07-04partial | VVNB | ? | 17:37 +07 | VN-A363 | ||
| 2026-07-03partial | VVNB | ? | 17:24 +07 | VN-A363 | ||
| 2026-07-01partial | VVNB | ? | 17:14 +07 | VN-A354 | ||
| 2026-06-30partial | VVNB | ? | 16:59 +07 | VN-A363 | ||
| 2026-06-29partial | VVNB | ? | 17:07 +07 | VN-A363 | ||
| 2026-06-27partial | VVNB | ? | 17:10 +07 | VN-A354 | ||
| 2026-06-26partial | VVNB | ? | 17:05 +07 | VN-A354 | ||
| 2026-06-25partial | VVNB | ? | 16:55 +07 | VN-A363 | ||
| 2026-06-24estimated | VVNB | ? | 16:56 +07 | 10:22Z | 0h 26m | VN-A363 |
| 2026-06-23partial | VVNB | ? | 16:56 +07 | VN-A363 | ||
| 2026-06-22partial | VVNB | ? | 16:56 +07 | VN-A363 | ||
| 2026-06-21partial | VVNB | ? | 17:03 +07 | VN-A363 | ||
| 2026-06-20partial | VVNB | ? | 17:18 +07 | VN-A363 | ||
| 2026-06-18partial | VVNB | ? | 17:48 +07 | VN-A363 | ||
| 2026-06-17partial | VVNB | ? | 16:42 +07 | VN-A354 | ||
| 2026-06-16partial | VVNB | ? | 17:00 +07 | VN-A363 | ||
| 2026-06-15partial | VVNB | ? | 17:24 +07 | VN-A363 | ||
| 2026-06-14partial | VVNB | ? | 17:06 +07 | VN-A363 | ||
| 2026-05-29partial | VVNB | ? | 17:09 +07 | VN-A363 | ||
| 2026-05-28partial | VVNB | ? | 17:04 +07 | VN-A363 | ||
| 2026-05-27partial | VVNB | ? | 17:07 +07 | VN-A363 | ||
| 2026-05-26partial | VVNB | ? | 17:22 +07 | VN-A363 | ||
| 2026-05-25partial | VVNB | ? | 17:24 +07 | VN-A363 | ||
| 2026-05-24partial | VVNB | ? | 16:50 +07 | VN-A363 | ||
| 2026-05-23partial | VVNB | ? | 16:39 +07 | VN-A363 | ||
| 2026-05-22estimated | ? | ? | 10:09Z | 10:32Z | 0h 22m | VN-A363 |
| 2026-05-21partial | VVNB | ? | 17:02 +07 | VN-A359 | ||
| 2026-05-20partial | VVNB | ? | 09:39 +07 | VN-A363 | ||
| 2026-05-19partial | VVNB | ? | 09:39 +07 | VN-A363 | ||
| 2026-05-12partial | VVNB | ? | 16:44 +07 | VN-A363 | ||
| 2026-05-11partial | VVNB | ? | 17:09 +07 | VN-A363 | ||
| 2026-05-07partial | VVNB | ? | 16:43 +07 | VN-A359 | ||
| 2026-05-06partial | VVNB | ? | 17:20 +07 | VN-A354 | ||
| 2026-05-05partial | VVNB | ? | 16:53 +07 | VN-A359 | ||
| 2026-05-03partial | VVNB | ? | 16:59 +07 | VN-A363 | ||
| 2026-05-01estimated | VVNB | ? | 16:51 +07 | 10:14Z | 0h 22m | VN-A363 |
| 2026-04-27partial | VVNB | ? | 17:06 +07 | VN-A363 | ||
| 2026-04-24estimated | ? | ? | 10:28Z | 12:18Z | 1h 49m | VN-A363 |
| 2026-04-23estimated | ? | ? | 10:16Z | 10:34Z | 0h 17m | VN-A363 |
| 2026-04-22estimated | ? | ? | 10:10Z | 11:44Z | 1h 33m | VN-A363 |
| 2026-04-21estimated | ? | ? | 09:47Z | 10:06Z | 0h 18m | VN-A363 |
| 2026-04-20estimated | ? | ? | 09:55Z | 10:14Z | 0h 18m | VN-A363 |
| 2026-04-19estimated | ? | ? | 10:02Z | 11:37Z | 1h 35m | VN-A363 |
| 2026-04-18estimated | ? | ? | 09:57Z | 11:28Z | 1h 31m | VN-A363 |
| 2026-04-17estimated | ? | ? | 10:08Z | 11:48Z | 1h 39m | VN-A363 |
| 2026-04-16estimated | ? | ? | 09:53Z | 11:35Z | 1h 41m | VN-A354 |
| 2026-04-15estimated | ? | ? | 10:05Z | 10:26Z | 0h 20m | VN-A363 |
| 2026-04-14estimated | ? | ? | 10:23Z | 12:03Z | 1h 40m | VN-A363 |
| 2026-04-13estimated | ? | ? | 10:00Z | 10:18Z | 0h 17m | VN-A363 |
| 2026-04-12estimated | ? | ? | 09:59Z | 11:35Z | 1h 35m | VN-A363 |
| 2026-04-11estimated | ? | ? | 09:58Z | 11:34Z | 1h 35m | VN-A363 |
| 2026-04-06partial | VVNB | ? | 17:05 +07 | VN-A363 | ||
| 2026-04-05estimated | ? | ? | 10:05Z | 11:43Z | 1h 37m | VN-A363 |
| 2026-04-04estimated | ? | ? | 10:16Z | 11:58Z | 1h 41m | VN-A363 |
| 2026-04-03estimated | ? | ? | 10:09Z | 11:47Z | 1h 38m | VN-A359 |
| 2026-04-02estimated | ? | ? | 09:53Z | 11:35Z | 1h 41m | VN-A359 |
| 2026-04-01estimated | ? | ? | 10:13Z | 10:32Z | 0h 19m | VN-A363 |
| 2026-03-31estimated | ? | ? | 10:16Z | 12:00Z | 1h 43m | VN-A363 |
| 2026-03-30estimated | ? | ? | 10:12Z | 11:51Z | 1h 38m | VN-A363 |
| 2026-03-29estimated | ? | ? | 11:07Z | 11:36Z | 0h 28m | VN-A363 |
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]