Flight
HDSN32
Flight history and live tracking for HDSN32. 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 Feb 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| No flights in the last 30 days. | ||||||
Earlier flights (16) - back to 2026-02-02
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-06-17estimated | YSWG | YMAY | 10:50 AEST | 16:20 AEST | 5h 29m | A32-671 |
| 2026-06-16 | YMMB | YMPC | 08:19 AEST | 09:58 AEST | 1h 38m | A32-671 |
| 2026-05-29partial | YMAV | ? | 10:00 AEST | A32-670 | ||
| 2026-05-28partial | YMES | ? | 10:21 AEST | A32-651 | ||
| 2026-05-19estimated | YMES | YMMB | 23:38 AEST | 00:04 AEST | 0h 25m | A32-988 |
| 2026-04-29 | ? | YBAS | 00:00Z | 12:50 ACST | 3h 19m | A32-671 |
| 2026-04-28partial | YMES | ? | 09:20 AEST | A32-671 | ||
| 2026-04-27partial | YMES | ? | 10:01 AEST | A32-671 | ||
| 2026-04-26estimated | YMLT | YMES | 15:41 AEST | 16:24 AEST | 0h 42m | A32-021 |
| 2026-04-24estimated | ? | ? | 05:25Z | 06:04Z | 0h 38m | A32-021 |
| 2026-04-14estimated | ? | ? | 00:32Z | 04:30Z | 3h 57m | A32-988 |
| 2026-04-13estimated | ? | ? | 03:07Z | 03:42Z | 0h 34m | A32-021 |
| 2026-04-01estimated | ? | ? | 03:17Z | 03:34Z | 0h 17m | A32-670 |
| 2026-02-18 | ? | YSRI | 00:02Z | 14:12 AEDT | 3h 10m | 7CFA34 |
| 2026-02-05estimated | ? | ? | 00:00Z | 02:14Z | 2h 13m | 7CF8EF |
| 2026-02-02 | YMES | YSCB | 12:13 AEDT | 14:01 AEDT | 1h 48m | 7CF8EC |
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 HDSN32 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]