Flight
RDHK762
Flight history and live tracking for RDHK762. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Flight history 15 flights since May 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| No flights in the last 30 days. | ||||||
Earlier flights (15) - back to 2026-05-27
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-06-25partial | KNGU | ? | 20:08 EDT | AE4D5B | ||
| 2026-06-24 | KORF | KNGU | 16:17 EDT | 19:48 EDT | 3h 30m | AE4D5B |
| 2026-06-24 | KORF | KNGU | 13:10 EDT | 13:54 EDT | 0h 43m | AE4D5B |
| 2026-06-17 | KPHF | KNGU | 00:10 EDT | 00:32 EDT | 0h 22m | AE4D5B |
| 2026-06-17 | KNGU | KPHF | 22:28 EDT | 23:18 EDT | 0h 50m | AE4D5B |
| 2026-06-16estimated | KNGU | KPHF | 16:40 EDT | 17:40 EDT | 1h 00m | AE4D5B |
| 2026-06-14partial | KNGU | ? | 20:27 EDT | AE4D5B | ||
| 2026-06-12 | KNGU | KPHF | 21:20 EDT | 21:56 EDT | 0h 35m | AE4D5B |
| 2026-05-29 | KJGG | KORF | 12:03 EDT | 12:36 EDT | 0h 32m | AE4D5B |
| 2026-05-28 | KFAF | KNGU | 19:09 EDT | 19:58 EDT | 0h 48m | AE4D5B |
| 2026-05-28 | KNGU | KFAF | 17:35 EDT | 18:42 EDT | 1h 06m | AE4D5B |
| 2026-05-28 | KFAF | KNGU | 16:19 EDT | 17:16 EDT | 0h 56m | AE4D5B |
| 2026-05-28 | KNGU | KFAF | 14:07 EDT | 15:32 EDT | 1h 24m | AE4D5B |
| 2026-05-27 | KORF | KNGU | 15:50 EDT | 16:26 EDT | 0h 35m | AE4D5B |
| 2026-05-27estimated | KORF | KFAF | 13:01 EDT | 15:06 EDT | 2h 05m | AE4D5B |
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 RDHK762 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 archive (from $9.99, with a free one-day sample). Questions: [email protected]