Flight
PGT95DP
Flight history and live tracking for PGT95DP, 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 | LTBX → LTFJ |
Flight history 43 flights since Mar 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-09-30estimated | ? | ? | 17:35Z | 20:36Z | 3h 01m | TC-RBO |
| 2026-09-23estimated | ? | ? | 18:08Z | 20:10Z | 2h 01m | 4BC8CA |
| 2026-09-16estimated | ? | ? | 17:49Z | 20:02Z | 2h 13m | 4BC889 |
Earlier flights (40) - back to 2026-03-30
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-31estimated | ? | ? | 18:12Z | 18:38Z | 0h 25m | 4BC894 |
| 2026-08-29estimated | ? | ? | 17:34Z | 18:02Z | 0h 27m | TC-RBK |
| 2026-07-22estimated | ? | ? | 18:16Z | 18:38Z | 0h 21m | 4BC8CC |
| 2026-07-20estimated | ? | ? | 18:14Z | 18:40Z | 0h 25m | 4BC8CD |
| 2026-07-18estimated | ? | ? | 17:38Z | 18:06Z | 0h 27m | 4BC8E1 |
| 2026-07-15estimated | ? | ? | 17:35Z | 20:08Z | 2h 32m | 4BC8D9 |
| 2026-07-13estimated | LTBS | ? | 21:10 +03 | 18:36Z | 0h 25m | 4BC8D4 |
| 2026-07-11estimated | LTBS | ? | 20:37 +03 | 18:04Z | 0h 26m | TC-RBK |
| 2026-07-06estimated | LTBS | ? | 21:14 +03 | 18:40Z | 0h 25m | TC-RBV |
| 2026-07-04estimated | LTBS | ? | 20:38 +03 | 18:06Z | 0h 27m | 4BC88C |
| 2026-07-01estimated | LTBS | ? | 20:39 +03 | 18:04Z | 0h 24m | TC-RBY |
| 2026-06-29estimated | LTBS | ? | 21:15 +03 | 18:40Z | 0h 24m | 4BC896 |
| 2026-06-27estimated | LTBS | ? | 20:50 +03 | 18:18Z | 0h 27m | TC-RBP |
| 2026-06-24estimated | LTBS | ? | 20:19 +03 | 17:46Z | 0h 27m | TC-RBG |
| 2026-06-22estimated | LTBS | ? | 21:03 +03 | 20:32Z | 2h 29m | 4BC8DA |
| 2026-06-20estimated | LTBS | ? | 20:42 +03 | 18:10Z | 0h 27m | 4BC8CD |
| 2026-06-17estimated | LTBS | ? | 20:15 +03 | 17:42Z | 0h 26m | TC-RBF |
| 2026-06-15estimated | LTBS | ? | 21:12 +03 | 18:42Z | 0h 29m | 4BC8C3 |
| 2026-05-27estimated | LTBS | ? | 20:22 +03 | 17:50Z | 0h 27m | TC-RBV |
| 2026-05-23estimated | LTBS | ? | 21:09 +03 | 18:38Z | 0h 28m | 4BC8CF |
| 2026-05-22estimated | ? | ? | 20:14Z | 20:38Z | 0h 23m | TC-RDA |
| 2026-05-20partial | LTBX | ? | 07:07 +03 | 4BC88D | ||
| 2026-05-19partial | LTBX | ? | 06:54 +03 | 4BC8CB | ||
| 2026-05-11estimated | LTBS | ? | 21:04 +03 | 18:38Z | 0h 33m | TC-RBR |
| 2026-05-09estimated | LTBX | LTFJ | 20:54 +03 | 23:29 +03 | 2h 35m | 4BC8C5 |
| 2026-05-08estimated | LTBS | ? | 20:49 +03 | 18:18Z | 0h 28m | 4BC88D |
| 2026-05-06estimated | LTBS | ? | 20:34 +03 | 18:04Z | 0h 29m | TC-RBR |
| 2026-05-04estimated | LTAY | ? | 21:40 +03 | 20:52Z | 2h 11m | TC-RBC |
| 2026-05-02estimated | LTAY | ? | 21:36 +03 | 18:54Z | 0h 17m | 4BC88D |
| 2026-04-29estimated | LTBS | ? | 20:17 +03 | 17:34Z | 0h 17m | 4BC8CA |
| 2026-04-27estimated | LTBS | ? | 21:04 +03 | 18:24Z | 0h 19m | 4BC8C6 |
| 2026-04-22estimated | ? | ? | 17:26Z | 17:48Z | 0h 22m | TC-RBS |
| 2026-04-20estimated | ? | ? | 18:07Z | 18:38Z | 0h 30m | TC-RBP |
| 2026-04-18estimated | ? | ? | 17:36Z | 17:58Z | 0h 21m | 4BC8CE |
| 2026-04-17estimated | ? | ? | 17:52Z | 18:18Z | 0h 25m | 4BC886 |
| 2026-04-15estimated | ? | ? | 17:20Z | 17:46Z | 0h 25m | 4BC894 |
| 2026-04-11estimated | ? | ? | 17:37Z | 18:00Z | 0h 22m | 4BC8CE |
| 2026-04-04estimated | ? | ? | 17:49Z | 19:54Z | 2h 04m | 4BC89A |
| 2026-04-03estimated | ? | ? | 18:27Z | 18:58Z | 0h 30m | TC-RBY |
| 2026-03-30estimated | ? | LTFJ | 19:20Z | 00:50 +03 | 2h 30m | TC-RBH |
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 PGT95DP 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]