Flight
PGT54RR
Flight history and live tracking for PGT54RR, 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 | LTBA → LTAI |
Flight history 16 flights since Apr 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-15estimated | ? | ? | 08:31Z | 12:51Z | 4h 19m | TC-NCO |
| 2026-08-12estimated | ? | ? | 11:26Z | 14:06Z | 2h 39m | TC-NBR |
Earlier flights (14) - back to 2026-04-11
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-18partial | LTAI | ? | 12:19 +03 | TC-NCC | ||
| 2026-07-15partial | LTAI | ? | 14:33 +03 | TC-NCP | ||
| 2026-07-11 | LTBA | LTAI | 12:15 +03 | 14:37 +03 | 2h 22m | TC-NCS |
| 2026-07-04estimated | LTBA | LTAI | 11:43 +03 | 13:04 +03 | 1h 20m | TC-NBC |
| 2026-06-27partial | LTAI | ? | 12:38 +03 | TC-NBG | ||
| 2026-06-24partial | LTAI | ? | 14:46 +03 | TC-NBD | ||
| 2026-06-20partial | LTAI | ? | 12:12 +03 | TC-NBS | ||
| 2026-05-27estimated | LTBA | LTAH | 14:17 +03 | 17:02 +03 | 2h 45m | TC-NCS |
| 2026-05-09estimated | LTBX | LTBN | 12:00 +03 | 16:08 +03 | 4h 07m | TC-NBA |
| 2026-05-02estimated | LTBA | ? | 12:09 +03 | 12:14Z | 3h 04m | TC-NBB |
| 2026-04-25estimated | ? | LTBO | 08:20Z | 12:18 +03 | 0h 57m | TC-NCP |
| 2026-04-22estimated | ? | ? | 11:25Z | 13:43Z | 2h 17m | TC-NCA |
| 2026-04-18estimated | ? | ? | 09:04Z | 09:26Z | 0h 21m | TC-NBY |
| 2026-04-11estimated | ? | ? | 08:41Z | 11:54Z | 3h 12m | TC-DCL |
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 PGT54RR 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]