Flight
PGT2660
Flight history and live tracking for PGT2660, 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 | LTAE → LTAC |
Flight history 16 flights since Feb 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-15estimated | ? | ? | 16:10Z | 16:35Z | 0h 24m | TC-NBP |
Earlier flights (15) - back to 2026-02-08
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-18estimated | ? | ? | 14:10Z | 17:57Z | 3h 47m | TC-NCL |
| 2026-07-11partial | LTAC | ? | 17:47 +03 | TC-NBI | ||
| 2026-06-27 | LTAE | LTAC | 17:09 +03 | 17:32 +03 | 0h 22m | TC-NCO |
| 2026-06-20partial | LTAE | ? | 17:09 +03 | TC-NBE | ||
| 2026-06-13estimated | LTBQ | LTAE | 17:53 +03 | 20:36 +03 | 2h 42m | TC-NCO |
| 2026-05-09estimated | LTBX | LTAE | 17:38 +03 | 18:06 +03 | 0h 27m | TC-RBP |
| 2026-05-02partial | LTAE | ? | 17:16 +03 | TC-NCH | ||
| 2026-04-18estimated | ? | ? | 14:06Z | 15:56Z | 1h 49m | TC-NCC |
| 2026-04-11estimated | ? | ? | 14:08Z | 14:36Z | 0h 27m | TC-NBS |
| 2026-04-04estimated | ? | ? | 14:20Z | 14:48Z | 0h 27m | TC-NCO |
| 2026-03-16estimated | ? | ? | 04:00Z | 04:28Z | 0h 28m | TC-CRG |
| 2026-03-15estimated | ? | ? | 04:03Z | 04:32Z | 0h 28m | TC-DCL |
| 2026-03-14estimated | ? | ? | 04:19Z | 05:54Z | 1h 35m | TC-NBR |
| 2026-03-13estimated | ? | ? | 04:01Z | 04:22Z | 0h 20m | TC-CRE |
| 2026-02-08 | LTBQ | LTAC | 07:07 +03 | 08:39 +03 | 1h 32m | 4BC84F |
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 PGT2660 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]