Flight
PGT46D
Flight history and live tracking for PGT46D, 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 | LTAR → LTCG |
Flight history 49 flights since Mar 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-20estimated | ? | ? | 03:06Z | 04:29Z | 1h 22m | TC-NCT |
Earlier flights (48) - back to 2026-03-31
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-23estimated | ? | ? | 03:02Z | 03:24Z | 0h 21m | TC-NCE |
| 2026-07-22estimated | ? | ? | 06:51Z | 07:14Z | 0h 22m | 4BC88D |
| 2026-07-21estimated | ? | ? | 07:31Z | 08:00Z | 0h 28m | TC-NCE |
| 2026-07-18estimated | ? | ? | 03:26Z | 03:50Z | 0h 23m | TC-NBH |
| 2026-07-17estimated | ? | ? | 12:51Z | 14:06Z | 1h 15m | TC-NBH |
| 2026-07-09estimated | LTAR | LTCG | 06:09 +03 | 06:32 +03 | 0h 22m | TC-NBF |
| 2026-07-06estimated | LTAR | LTCG | 11:51 +03 | 12:16 +03 | 0h 24m | TC-NCC |
| 2026-07-05estimated | LTAR | LTCG | 09:55 +03 | 10:16 +03 | 0h 20m | TC-NCE |
| 2026-07-04estimated | LTAR | LTCG | 06:22 +03 | 06:46 +03 | 0h 23m | TC-NCE |
| 2026-07-03estimated | LTAR | LTCG | 15:22 +03 | 15:46 +03 | 0h 23m | TC-NCE |
| 2026-07-02partial | LTCG | ? | 06:19 +03 | TC-NCE | ||
| 2026-06-30estimated | LTAR | LTCG | 10:47 +03 | 11:24 +03 | 0h 36m | TC-NBO |
| 2026-06-28partial | LTCG | ? | 09:52 +03 | TC-NCE | ||
| 2026-06-25partial | LTCG | ? | 06:14 +03 | TC-NCN | ||
| 2026-06-18partial | LTCG | ? | 06:13 +03 | TC-NBY | ||
| 2026-06-17partial | LTCG | ? | 09:54 +03 | TC-NBY | ||
| 2026-06-16partial | LTCG | ? | 10:31 +03 | TC-NBY | ||
| 2026-06-14estimated | LTAR | LTCG | 09:46 +03 | 10:12 +03 | 0h 25m | TC-NBY |
| 2026-06-12partial | LTCG | ? | 16:05 +03 | TC-NBH | ||
| 2026-05-28partial | LTCG | ? | 06:15 +03 | TC-NCZ | ||
| 2026-05-27partial | LTCG | ? | 09:43 +03 | TC-NCZ | ||
| 2026-05-26partial | LTCG | ? | 10:28 +03 | TC-NBM | ||
| 2026-05-25partial | LTCG | ? | 13:50 +03 | TC-NCR | ||
| 2026-05-24estimated | LTAR | LTCG | 09:49 +03 | 10:12 +03 | 0h 22m | TC-NBF |
| 2026-05-20partial | LTCG | ? | 03:05 +03 | TC-NBG | ||
| 2026-05-11partial | LTCG | ? | 14:01 +03 | TC-NCT | ||
| 2026-05-10estimated | LTAR | LTCG | 09:52 +03 | 10:22 +03 | 0h 29m | TC-NCT |
| 2026-05-09estimated | LTAR | LTCG | 06:17 +03 | 06:46 +03 | 0h 29m | TC-NCT |
| 2026-05-08estimated | LTAR | LTCG | 16:30 +03 | 16:52 +03 | 0h 21m | TC-NBO |
| 2026-05-05estimated | LTAR | LTCG | 10:30 +03 | 10:54 +03 | 0h 23m | TC-NBM |
| 2026-05-04estimated | LTAR | LTCG | 14:01 +03 | 14:22 +03 | 0h 20m | TC-NBM |
| 2026-04-27partial | LTCG | ? | 14:06 +03 | TC-DCI | ||
| 2026-04-26estimated | LTAF | LTCG | 09:20 +03 | 10:54 +03 | 1h 33m | TC-DCI |
| 2026-04-25estimated | LTAG | LTCG | 05:58 +03 | 06:44 +03 | 0h 45m | TC-DCI |
| 2026-04-22partial | LTCG | ? | 09:44 +03 | TC-NBG | ||
| 2026-04-21partial | LTCG | ? | 10:22 +03 | TC-NBV | ||
| 2026-04-20estimated | ? | ? | 11:16Z | 13:57Z | 2h 40m | TC-NCJ |
| 2026-04-19partial | LTCG | ? | 09:43 +03 | TC-NBG | ||
| 2026-04-18estimated | ? | ? | 03:16Z | 03:42Z | 0h 25m | TC-NBG |
| 2026-04-17estimated | ? | ? | 13:34Z | 14:02Z | 0h 27m | TC-DCG |
| 2026-04-15partial | LTCG | ? | 09:43 +03 | TC-NBG | ||
| 2026-04-14estimated | ? | ? | 07:20Z | 07:42Z | 0h 21m | TC-NBG |
| 2026-04-12estimated | ? | ? | 06:48Z | 07:10Z | 0h 21m | TC-NBG |
| 2026-04-11estimated | ? | ? | 03:11Z | 03:30Z | 0h 18m | TC-NBH |
| 2026-04-06estimated | ? | ? | 10:55Z | 11:18Z | 0h 22m | TC-NCT |
| 2026-04-03estimated | ? | ? | 12:55Z | 13:18Z | 0h 22m | TC-NBL |
| 2026-04-01estimated | ? | ? | 06:41Z | 07:12Z | 0h 31m | TC-NBB |
| 2026-03-31partial | LTCG | ? | 10:46 +03 | TC-NBB |
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.
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]