Flight
PGT2019
Flight history and live tracking for PGT2019, 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 | LTAI → LTBR |
Flight history 66 flights since Apr 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-10-02estimated | LTAI | LTBR | 18:33 +03 | 19:20 +03 | 0h 46m | TC-NBD |
| 2026-09-30estimated | LTAI | LTBR | 18:27 +03 | 19:02 +03 | 0h 34m | TC-NCK |
| 2026-09-29estimated | LTAI | LTBR | 19:13 +03 | 19:48 +03 | 0h 34m | TC-NBK |
| 2026-09-28estimated | LTAI | LTBR | 19:47 +03 | 20:22 +03 | 0h 35m | TC-NBI |
| 2026-09-27estimated | LTAI | LTBR | 18:58 +03 | 19:34 +03 | 0h 35m | TC-NBY |
| 2026-09-26estimated | LTAI | LTBR | 19:52 +03 | 20:32 +03 | 0h 40m | TC-NBL |
| 2026-09-25estimated | LTAI | LTBR | 19:17 +03 | 19:54 +03 | 0h 36m | TC-NBU |
| 2026-09-24estimated | LTAI | LTBR | 19:05 +03 | 21:30 +03 | 2h 24m | TC-NCY |
| 2026-09-23estimated | LTAI | LTBR | 18:34 +03 | 21:30 +03 | 2h 56m | TC-NCV |
| 2026-09-22estimated | LTAI | LTBR | 19:12 +03 | 19:52 +03 | 0h 39m | TC-NBE |
| 2026-09-16 | LTAI | LTFJ | 18:26 +03 | 19:12 +03 | 0h 45m | TC-NBP |
| 2026-09-14estimated | LTAI | LTBR | 19:51 +03 | 20:12 +03 | 0h 20m | TC-NBI |
| 2026-09-13estimated | LTAI | LTBR | 18:27 +03 | 18:50 +03 | 0h 22m | TC-NBO |
| 2026-09-11estimated | LTAI | LTBR | 18:33 +03 | 18:54 +03 | 0h 20m | TC-NBK |
| 2026-09-09estimated | LTAI | LTBR | 19:06 +03 | 19:40 +03 | 0h 33m | TC-NCT |
| 2026-09-08estimated | LTAI | LTBR | 19:02 +03 | 19:34 +03 | 0h 31m | TC-NCR |
| 2026-09-06estimated | LTAI | LTBR | 18:42 +03 | 19:18 +03 | 0h 35m | TC-NBY |
| 2026-09-05estimated | LTAI | LTBR | 20:01 +03 | 20:26 +03 | 0h 24m | TC-NCE |
| 2026-09-04estimated | LTAI | LTBR | 18:43 +03 | 19:14 +03 | 0h 30m | TC-NBS |
Earlier flights (47) - back to 2026-04-12
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-09-03estimated | LTAI | LTBR | 19:24 +03 | 19:56 +03 | 0h 31m | TC-NCV |
| 2026-09-01estimated | LTAI | LTBR | 19:31 +03 | 20:06 +03 | 0h 34m | TC-DCG |
| 2026-08-31estimated | LTAI | LTBR | 19:40 +03 | 20:12 +03 | 0h 32m | TC-NBP |
| 2026-08-30estimated | LTAI | LTBR | 19:07 +03 | 19:36 +03 | 0h 29m | TC-NCU |
| 2026-08-29estimated | LTAI | LTBR | 20:44 +03 | 23:12 +03 | 2h 27m | TC-NCL |
| 2026-08-28estimated | LTAI | LTBR | 18:39 +03 | 19:10 +03 | 0h 30m | TC-NCB |
| 2026-07-23estimated | ? | LTBR | 16:14Z | 19:46 +03 | 0h 31m | TC-NCP |
| 2026-07-22estimated | LTAI | LTBR | 18:37 +03 | 19:10 +03 | 0h 32m | TC-NCY |
| 2026-07-21estimated | LTAI | LTBR | 20:35 +03 | 21:06 +03 | 0h 31m | TC-NCC |
| 2026-07-20estimated | ? | ? | 06:08Z | 18:14Z | 12h 05m | TC-NCG |
| 2026-07-19estimated | LTAI | LTBR | 18:18 +03 | 19:08 +03 | 0h 49m | TC-NCG |
| 2026-07-18estimated | ? | ? | 17:35Z | 20:59Z | 3h 24m | 4BC89A |
| 2026-07-17estimated | LTAI | LTBR | 18:29 +03 | 19:02 +03 | 0h 32m | TC-NBC |
| 2026-07-16estimated | LTAI | LTBR | 19:08 +03 | 19:44 +03 | 0h 35m | TC-NBF |
| 2026-07-15estimated | LTAI | LTBR | 18:58 +03 | 19:34 +03 | 0h 35m | TC-NBF |
| 2026-07-14estimated | LTAI | LTBR | 20:08 +03 | 20:38 +03 | 0h 29m | TC-NCZ |
| 2026-07-13estimated | LTAI | LTBR | 19:48 +03 | 20:18 +03 | 0h 29m | TC-NCA |
| 2026-07-12estimated | LTAI | LTBR | 18:26 +03 | 18:56 +03 | 0h 29m | TC-NCT |
| 2026-07-10estimated | LTAI | LTBR | 18:30 +03 | 19:02 +03 | 0h 31m | TC-NCA |
| 2026-07-09estimated | LTAI | LTBR | 19:15 +03 | 19:48 +03 | 0h 32m | TC-DCM |
| 2026-07-07estimated | LTAI | LTBR | 19:23 +03 | 23:26 +03 | 4h 02m | TC-NBE |
| 2026-07-06estimated | LTAI | LTBR | 20:01 +03 | 20:30 +03 | 0h 28m | TC-NCN |
| 2026-07-05estimated | LTAI | ? | 08:59 +03 | 17:02Z | 11h 02m | TC-NCB |
| 2026-07-04estimated | LTAI | LTBR | 20:01 +03 | 20:34 +03 | 0h 33m | TC-NCB |
| 2026-07-03estimated | LTAI | LTBR | 18:32 +03 | 19:06 +03 | 0h 33m | TC-NBS |
| 2026-07-02estimated | LTAI | ? | 06:36 +03 | 16:40Z | 13h 04m | TC-NCI |
| 2026-07-01estimated | LTAI | ? | 11:52 +03 | 16:16Z | 7h 23m | TC-NBN |
| 2026-06-30estimated | ? | ? | 20:30Z | 20:50Z | 0h 19m | TC-NBN |
| 2026-06-29estimated | LTAI | ? | 08:19 +03 | 17:28Z | 12h 08m | TC-NCI |
| 2026-06-28estimated | LTAI | LTBR | 19:45 +03 | 20:18 +03 | 0h 33m | TC-NCI |
| 2026-06-27estimated | LTAI | LTBR | 20:10 +03 | 22:32 +03 | 2h 21m | TC-NBS |
| 2026-06-26estimated | LTAI | LTBR | 18:27 +03 | 21:35 +03 | 3h 08m | TC-NCD |
| 2026-06-25estimated | LTAI | LTBR | 19:12 +03 | 19:48 +03 | 0h 35m | 4BC888 |
| 2026-06-24estimated | LTAI | LTBR | 18:55 +03 | 19:30 +03 | 0h 34m | TC-NBV |
| 2026-06-23estimated | LTAI | LTBR | 19:14 +03 | 21:46 +03 | 2h 31m | TC-NBB |
| 2026-06-22estimated | LTAI | LTBR | 19:35 +03 | 20:08 +03 | 0h 32m | TC-NCB |
| 2026-06-21estimated | LTAI | LTBR | 18:24 +03 | 18:56 +03 | 0h 31m | TC-NBB |
| 2026-06-20estimated | LTAI | LTBR | 20:10 +03 | 20:44 +03 | 0h 33m | TC-NCH |
| 2026-06-19estimated | LTAI | ? | 10:13 +03 | 16:02Z | 8h 48m | TC-NCR |
| 2026-05-20partial | LTBX | ? | 04:30 +03 | TC-NBF | ||
| 2026-05-19partial | LTBX | ? | 06:53 +03 | TC-NCV | ||
| 2026-05-11estimated | LTAH | ? | 20:05 +03 | 17:22Z | 0h 16m | TC-NBA |
| 2026-04-26estimated | LTBX | ? | 20:02 +03 | 19:41Z | 2h 39m | TC-RBS |
| 2026-04-17estimated | ? | ? | 16:27Z | 16:52Z | 0h 24m | TC-NBR |
| 2026-04-16estimated | ? | ? | 16:13Z | 16:40Z | 0h 26m | TC-NCE |
| 2026-04-14estimated | ? | ? | 17:11Z | 17:36Z | 0h 24m | 4BC8CB |
| 2026-04-12estimated | ? | ? | 16:33Z | 17:02Z | 0h 28m | TC-NCU |
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 PGT2019 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]