Flight
PGT57W
Flight history and live tracking for PGT57W, operated by Pegasus Airlines. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | Pegasus Airlines |
| Observed route | LTBK → LTCE |
Flight history 41 flights since Mar 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-20estimated | ? | ? | 12:16Z | 13:34Z | 1h 18m | TC-NCU |
| 2026-08-18estimated | ? | ? | 04:01Z | 05:04Z | 1h 02m | TC-NBZ |
| 2026-08-16estimated | ? | ? | 03:29Z | 04:10Z | 0h 40m | TC-NCC |
| 2026-08-13estimated | ? | ? | 11:35Z | 13:45Z | 2h 09m | TC-NBK |
Earlier flights (37) - back to 2026-03-31
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-23estimated | ? | ? | 11:56Z | 12:58Z | 1h 01m | TC-NBJ |
| 2026-07-21estimated | ? | ? | 04:04Z | 07:13Z | 3h 08m | TC-NCB |
| 2026-07-19estimated | ? | ? | 04:07Z | 05:22Z | 1h 14m | TC-NBS |
| 2026-07-16estimated | ? | ? | 11:51Z | 15:23Z | 3h 31m | TC-NCJ |
| 2026-07-14estimated | LTBK | LTAR | 07:27 +03 | 08:20 +03 | 0h 52m | TC-NBT |
| 2026-07-12estimated | LTBK | LTAZ | 06:14 +03 | 09:42 +03 | 3h 27m | TC-NBA |
| 2026-07-09estimated | LTBK | LTAZ | 14:28 +03 | 17:36 +03 | 3h 07m | TC-NBK |
| 2026-07-07estimated | LTBK | LTAZ | 07:19 +03 | 10:50 +03 | 3h 31m | TC-NBI |
| 2026-07-05estimated | LTBK | LTCE | 06:21 +03 | 07:34 +03 | 1h 12m | TC-NCD |
| 2026-07-02estimated | LTBK | LTCE | 15:24 +03 | 16:38 +03 | 1h 14m | TC-NBY |
| 2026-06-30estimated | LTBK | LTCE | 07:03 +03 | 08:16 +03 | 1h 12m | TC-NCT |
| 2026-06-28estimated | LTBK | LTCE | 06:37 +03 | 07:56 +03 | 1h 19m | TC-NCM |
| 2026-06-25estimated | LTBK | LTAZ | 14:58 +03 | 18:26 +03 | 3h 27m | TC-NBU |
| 2026-06-23estimated | LTBK | LTCE | 06:58 +03 | 08:18 +03 | 1h 19m | TC-NCD |
| 2026-06-21estimated | LTBK | LTAZ | 06:38 +03 | 10:12 +03 | 3h 33m | TC-NCT |
| 2026-06-16estimated | LTBK | LTAR | 07:06 +03 | 08:04 +03 | 0h 57m | TC-NCZ |
| 2026-06-14estimated | LTBK | LTCE | 06:22 +03 | 07:42 +03 | 1h 19m | TC-NBC |
| 2026-05-28estimated | LTBK | LTAR | 14:09 +03 | 15:12 +03 | 1h 02m | TC-NBC |
| 2026-05-26estimated | LTBK | LTCE | 06:49 +03 | 08:15 +03 | 1h 25m | TC-NBO |
| 2026-05-24estimated | LTBK | LTCE | 06:27 +03 | 07:52 +03 | 1h 25m | TC-NBM |
| 2026-05-21estimated | LTBJ | LTAZ | 14:26 +03 | 17:58 +03 | 3h 31m | TC-NCB |
| 2026-05-12estimated | LTBK | LTAZ | 07:04 +03 | 11:00 +03 | 3h 55m | TC-NCO |
| 2026-05-10estimated | LTBK | LTCE | 06:20 +03 | 09:46 +03 | 3h 25m | TC-NCH |
| 2026-05-07estimated | LTBK | LTCE | 14:24 +03 | 15:10 +03 | 0h 45m | TC-NCO |
| 2026-05-05estimated | LTBK | LTCE | 06:56 +03 | 10:24 +03 | 3h 27m | TC-NCK |
| 2026-04-30estimated | LTBJ | LTAH | 14:11 +03 | 18:11 +03 | 3h 59m | TC-NBC |
| 2026-04-28estimated | LTBJ | LTBO | 07:05 +03 | 11:11 +03 | 4h 05m | TC-NCI |
| 2026-04-26estimated | LTBJ | ? | 06:22 +03 | 06:56Z | 3h 34m | TC-NCN |
| 2026-04-23estimated | ? | ? | 11:14Z | 14:46Z | 3h 31m | TC-NBK |
| 2026-04-21estimated | ? | ? | 04:04Z | 04:48Z | 0h 43m | TC-NCF |
| 2026-04-19estimated | ? | ? | 03:39Z | 04:30Z | 0h 50m | TC-NCR |
| 2026-04-16estimated | ? | ? | 11:24Z | 12:00Z | 0h 35m | TC-NBH |
| 2026-04-14estimated | ? | ? | 03:58Z | 07:26Z | 3h 27m | TC-NBH |
| 2026-04-12estimated | ? | ? | 03:28Z | 04:46Z | 1h 18m | TC-NBH |
| 2026-04-05estimated | ? | ? | 03:32Z | 04:22Z | 0h 49m | TC-NBL |
| 2026-04-02estimated | ? | ? | 11:20Z | 14:43Z | 3h 23m | TC-NBC |
| 2026-03-31estimated | ? | ? | 03:58Z | 07:48Z | 3h 49m | TC-NBH |
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 PGT57W 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]