Flight
PGT1617
Flight history and live tracking for PGT1617. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Flight history 14 flights since Aug 2025
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-09-30estimated | LTAZ | EDDB | 04:50 +03 | 06:56 CEST | 3h 05m | 4BC8CD |
| 2026-09-23estimated | LTAZ | EDDB | 05:06 +03 | 07:22 CEST | 3h 15m | 4BC8D2 |
| 2026-09-16estimated | ? | ? | 04:31Z | 04:56Z | 0h 24m | 4BC8DA |
| 2026-09-09estimated | LTAZ | EDDB | 05:03 +03 | 07:06 CEST | 3h 02m | 4BC8D2 |
Earlier flights (10) - back to 2025-08-20
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-19estimated | LTAZ | EDDB | 05:08 +03 | 07:16 CEST | 3h 07m | TC-RBK |
| 2026-08-12estimated | ? | ? | 02:21Z | 05:28Z | 3h 06m | 4BC886 |
| 2026-07-22estimated | LTAZ | EDDB | 05:02 +03 | 07:00 CEST | 2h 57m | TC-RBH |
| 2026-07-15estimated | LTAZ | EDDB | 05:08 +03 | 07:10 CEST | 3h 01m | 4BC8CD |
| 2026-07-08estimated | LTAZ | EDDB | 05:09 +03 | 07:10 CEST | 3h 00m | 4BC895 |
| 2026-07-01estimated | LTAZ | EDDB | 05:14 +03 | 07:02 CEST | 2h 47m | 4BC8D2 |
| 2026-04-22estimated | LTAZ | EDDB | 05:26 +03 | 07:26 CEST | 2h 59m | 4BC8C4 |
| 2026-04-15estimated | ? | EDDB | 02:13Z | 07:12 CEST | 2h 58m | TC-NCT |
| 2026-04-01estimated | ? | EDDB | 02:07Z | 06:58 CEST | 2h 50m | TC-NCE |
| 2025-08-20estimated | LTAZ | EDDB | 06:33 +03 | 09:28 CEST | 3h 55m | 4BC88A |
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 PGT1617 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]