Flight
THY6580
Flight history and live tracking for THY6580, operated by Turkish Airlines. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | Turkish Airlines |
| Observed route | LTBP → ZGNN |
Flight history 15 flights since Apr 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-15estimated | ? | ? | 06:24Z | 21:45Z | 15h 21m | TC-LJS |
Earlier flights (14) - back to 2026-04-04
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-18estimated | ? | ? | 07:28Z | 21:58Z | 14h 30m | TC-LJS |
| 2026-07-11estimated | LTBP | ZGSZ | 09:49 +03 | 04:37 CST | 13h 47m | TC-LJS |
| 2026-07-04estimated | LTBQ | LTCE | 10:48 +03 | 11:44 +03 | 0h 55m | TC-LJN |
| 2026-06-27estimated | LTBX | ZGNN | 09:08 +03 | 06:04 CST | 15h 56m | TC-LJO |
| 2026-06-20estimated | LTBP | ZGNN | 09:01 +03 | 04:54 CST | 14h 52m | TC-LJO |
| 2026-06-13estimated | LTBP | ZGSZ | 09:05 +03 | 04:35 CST | 14h 30m | 4BB156 |
| 2026-05-24estimated | UAFM | ZGSZ | 08:02 +06 | 18:11 CST | 8h 08m | TC-LJL |
| 2026-05-23estimated | LTBQ | LTCE | 23:30 +03 | 00:30 +03 | 0h 59m | TC-LJL |
| 2026-05-09estimated | LTBP | ZGNN | 11:17 +03 | 22:30 CST | 6h 12m | TC-LJL |
| 2026-05-02estimated | LTBP | ZGNN | 12:29 +03 | 23:44 CST | 6h 15m | TC-LJT |
| 2026-04-25estimated | LTBP | ZGGG | 11:29 +03 | 05:52 CST | 13h 22m | 4BB155 |
| 2026-04-18estimated | ? | ? | 07:54Z | 22:39Z | 14h 44m | TC-LJL |
| 2026-04-11estimated | ? | ? | 06:05Z | 12:42Z | 6h 36m | TC-LJT |
| 2026-04-04estimated | ? | ? | 14:24Z | 20:54Z | 6h 29m | TC-LJN |
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]