Flight
PGT265B
Flight history and live tracking for PGT265B. 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 Jun 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-16estimated | ? | ? | 23:11Z | 23:30Z | 0h 18m | TC-NCT |
| 2026-08-15estimated | ? | ? | 00:00Z | 00:48Z | 0h 47m | TC-NCT |
Earlier flights (14) - back to 2026-06-20
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-20estimated | ? | ? | 00:00Z | 00:36Z | 0h 35m | TC-NCE |
| 2026-07-19estimated | ? | ? | 23:29Z | 23:52Z | 0h 23m | TC-NCE |
| 2026-07-18estimated | ? | ? | 00:00Z | 01:06Z | 1h 05m | TC-NBH |
| 2026-07-13estimated | ? | ? | 00:00Z | 02:45Z | 2h 45m | TC-NCP |
| 2026-07-12estimated | LBSF | LTBU | 02:39 EEST | 02:59 +03 | 0h 20m | TC-NCP |
| 2026-07-11estimated | ? | ? | 00:04Z | 01:14Z | 1h 09m | TC-NBH |
| 2026-07-06estimated | LWSK | LTAZ | 12:19 CEST | 16:53 +03 | 3h 33m | TC-NBF |
| 2026-07-04estimated | ? | LTAR | 00:00Z | 06:21 +03 | 3h 21m | TC-NCE |
| 2026-06-29estimated | LTBF | ? | 03:01 +03 | 00:34Z | 0h 32m | TC-NCE |
| 2026-06-28estimated | LWSK | LTBH | 01:14 CEST | 02:52 +03 | 0h 37m | TC-NCE |
| 2026-06-27estimated | LWSK | LTCG | 02:13 CEST | 06:45 +03 | 3h 31m | TC-NCN |
| 2026-06-22estimated | LTBO | ? | 03:00 +03 | 00:30Z | 0h 30m | TC-NCN |
| 2026-06-21estimated | LWSK | LTAZ | 01:09 CEST | 02:58 +03 | 0h 48m | TC-NCN |
| 2026-06-20estimated | LGKM | ? | 03:00 EEST | 01:06Z | 1h 06m | TC-NCN |
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 PGT265B 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]