Flight
HYT9057
Flight history and live tracking for HYT9057. 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 Mar 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| No flights in the last 30 days. | ||||||
Earlier flights (16) - back to 2026-03-13
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-10 | VGTJ | VGZR | 11:58 +06 | 14:33 +06 | 2h 35m | B-221F |
| 2026-07-03 | VGTJ | VGZR | 12:28 +06 | 15:34 +06 | 3h 05m | B-221F |
| 2026-06-30partial | VGZR | ? | 12:00 +06 | B-221F | ||
| 2026-06-19estimated | VGTJ | VGZR | 14:00 +06 | 16:20 +06 | 2h 19m | B-221F |
| 2026-06-16 | VGTJ | VGZR | 12:07 +06 | 14:38 +06 | 2h 30m | B-221F |
| 2026-06-12partial | VGZR | ? | 12:21 +06 | B-221F | ||
| 2026-05-22estimated | ? | VGHS | 06:05Z | 14:13 +06 | 2h 08m | B-221F |
| 2026-04-17estimated | ? | VGHS | 06:23Z | 14:31 +06 | 2h 08m | B-221H |
| 2026-04-15estimated | ? | ? | 07:16Z | 10:09Z | 2h 52m | B-221F |
| 2026-04-12estimated | ? | VGHS | 06:39Z | 14:52 +06 | 2h 13m | B-221H |
| 2026-04-05estimated | ? | VGHS | 06:25Z | 13:02 +06 | 0h 36m | B-221H |
| 2026-04-03estimated | ? | VGHS | 06:25Z | 14:59 +06 | 2h 34m | B-221H |
| 2026-04-01estimated | ? | VGHS | 06:27Z | 14:33 +06 | 2h 05m | B-221F |
| 2026-03-29estimated | ? | VGHS | 06:35Z | 13:26 +06 | 0h 50m | B-221H |
| 2026-03-15estimated | ? | VGHS | 17:39Z | 02:26 +06 | 2h 47m | B-2853 |
| 2026-03-13estimated | ? | VGHS | 07:03Z | 15:22 +06 | 2h 18m | B-2859 |
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 HYT9057 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]