Flight
THY6072
Flight history and live tracking for THY6072. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Flight history 16 flights since Oct 2025
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| No flights in the last 30 days. | ||||||
Earlier flights (16) - back to 2025-10-04
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-03-13partial | LFSB | ? | 21:16 CET | 4B9DF5 | ||
| 2026-03-13estimated | ? | ? | 04:18Z | 04:58Z | 0h 39m | 4B9DF5 |
| 2026-02-18estimated | ? | ? | 00:53Z | 02:50Z | 1h 57m | 4B9DEC |
| 2026-01-02estimated | ? | ? | 00:02Z | 02:00Z | 1h 57m | TC-LJR |
| 2026-01-01partial | GOBD | ? | 20:01 GMT | 4BB152 | ||
| 2025-12-26 | GOBD | LTFM | 02:30 GMT | 11:12 +03 | 5h 41m | TC-LJR |
| 2025-12-26estimated | ? | GOBD | 00:03Z | 00:34 GMT | 0h 30m | TC-LJR |
| 2025-12-25estimated | ? | ? | 15:28Z | 23:58Z | 8h 30m | TC-LJR |
| 2025-12-19 | ? | LTFM | 00:28Z | 08:08 +03 | 4h 40m | TC-LJS |
| 2025-12-18partial | GOBD | ? | 22:49 GMT | 4BB153 | ||
| 2025-12-12 | ? | LTFM | 00:25Z | 05:28 +03 | 2h 02m | TC-LJO |
| 2025-12-11partial | GOBD | ? | 20:15 GMT | 4BB14F | ||
| 2025-11-28estimated | ? | ? | 01:22Z | 02:18Z | 0h 55m | TC-LJL |
| 2025-11-27estimated | ? | GOBD | 11:45Z | 18:26 GMT | 6h 40m | TC-LJL |
| 2025-10-24 | LIMC | ? | 04:21 CEST | 04:06Z | 1h 44m | TC-SGM |
| 2025-10-04 | LIMC | LTFM | 18:28 CEST | 20:14 +03 | 0h 45m | ER-BAG |
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 THY6072 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]