Flight
PGT123F
Flight history and live tracking for PGT123F, 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 |
| Typical origin | LTAI ANTALYA |
| Typical destination | LTDB |
Flight history 52 flights since Apr 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-10-03partial | LTAI | ? | 19:41 +03 | TC-NBP | ||
| 2026-09-16partial | LTAI | ? | 19:41 +03 | TC-DCH | ||
| 2026-09-14partial | LTAI | ? | 19:29 +03 | TC-NCE | ||
| 2026-09-13partial | LTAI | ? | 19:41 +03 | TC-NCL | ||
| 2026-09-12estimated | ? | ? | 16:20Z | 18:30Z | 2h 10m | TC-NCL |
| 2026-09-11partial | LTAI | ? | 16:41 +03 | TC-NBH | ||
| 2026-09-10partial | LTAI | ? | 13:22 +03 | TC-NCO | ||
| 2026-09-09partial | LTAI | ? | 19:25 +03 | TC-NCA | ||
| 2026-09-08partial | LTAI | ? | 23:31 +03 | TC-NCA |
Earlier flights (43) - back to 2026-04-14
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-09-06partial | LTAI | ? | 19:33 +03 | TC-NCV | ||
| 2026-09-05partial | LTAI | ? | 19:57 +03 | TC-NCV | ||
| 2026-09-04partial | LTAI | ? | 16:58 +03 | TC-NCN | ||
| 2026-09-03partial | LTAI | ? | 15:03 +03 | TC-DCG | ||
| 2026-09-01partial | LTAI | ? | 23:37 +03 | TC-NBJ | ||
| 2026-08-31partial | LTAI | ? | 15:36 +03 | TC-NBJ | ||
| 2026-08-30partial | LTAI | ? | 19:45 +03 | TC-DCL | ||
| 2026-08-29partial | LTAI | ? | 20:38 +03 | TC-DCL | ||
| 2026-08-28partial | LTAI | ? | 16:57 +03 | TC-NBI | ||
| 2026-07-23partial | LTAI | ? | 13:08 +03 | TC-NCP | ||
| 2026-07-22partial | LTAI | ? | 20:00 +03 | TC-NCE | ||
| 2026-07-21partial | LTAI | ? | 00:45 +03 | 4BC88D | ||
| 2026-07-20partial | LTAI | ? | 15:43 +03 | TC-NCE | ||
| 2026-07-19partial | LTAI | ? | 19:45 +03 | TC-NBH | ||
| 2026-07-18partial | LTAI | ? | 19:50 +03 | TC-NBH | ||
| 2026-07-17partial | LTAI | ? | 17:09 +03 | TC-NCR | ||
| 2026-07-16partial | LTAI | ? | 13:11 +03 | TC-DCM | ||
| 2026-07-15partial | LTAI | ? | 19:43 +03 | TC-NBH | ||
| 2026-07-14partial | LTAI | ? | 23:59 +03 | TC-NCS | ||
| 2026-07-13partial | LTAI | ? | 15:30 +03 | TC-NCP | ||
| 2026-07-12estimated | LTAI | ? | 19:31 +03 | 16:58Z | 0h 26m | TC-NCP |
| 2026-07-11partial | LTAI | ? | 19:53 +03 | TC-NCN | ||
| 2026-07-10partial | LTAI | ? | 16:48 +03 | TC-NCN | ||
| 2026-07-09partial | LTAI | ? | 13:49 +03 | TC-NBN | ||
| 2026-07-06partial | LTAI | ? | 17:06 +03 | TC-NCC | ||
| 2026-07-05partial | LTAI | ? | 20:46 +03 | TC-NCE | ||
| 2026-07-04partial | LTAI | ? | 20:26 +03 | TC-NCE | ||
| 2026-07-03partial | LTAI | ? | 17:24 +03 | TC-NBC | ||
| 2026-07-02partial | LTAI | ? | 15:01 +03 | TC-NCL | ||
| 2026-07-01partial | LTAI | ? | 19:37 +03 | TC-NCE | ||
| 2026-06-29partial | LTAI | ? | 16:05 +03 | TC-NCE | ||
| 2026-06-28partial | LTAI | ? | 19:31 +03 | TC-NCE | ||
| 2026-06-27partial | LTAI | ? | 19:33 +03 | TC-NCN | ||
| 2026-06-26partial | LTAI | ? | 16:51 +03 | TC-NBN | ||
| 2026-06-24partial | LTAI | ? | 19:23 +03 | TC-NCN | ||
| 2026-06-23partial | LTAI | ? | 23:32 +03 | TC-NCN | ||
| 2026-06-22partial | LTAI | ? | 15:38 +03 | TC-NCN | ||
| 2026-06-21partial | LTAI | ? | 19:43 +03 | TC-NCN | ||
| 2026-06-20partial | LTAI | ? | 19:27 +03 | TC-NCN | ||
| 2026-06-19partial | LTAI | ? | 16:56 +03 | TC-NCL | ||
| 2026-04-17estimated | ? | ? | 14:33Z | 14:52Z | 0h 18m | TC-NBV |
| 2026-04-16partial | LTAI | ? | 13:10 +03 | TC-DCG | ||
| 2026-04-14estimated | ? | ? | 20:30Z | 20:54Z | 0h 23m | TC-NBG |
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 PGT123F 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]