Flight
THY96F
Flight history and live tracking for THY96F, 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 → LTAZ |
Flight history 78 flights since Mar 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-21estimated | ? | ? | 19:08Z | 19:36Z | 0h 27m | TC-JZG |
| 2026-08-20estimated | ? | ? | 19:25Z | 19:42Z | 0h 16m | TC-JLT |
| 2026-08-19estimated | ? | ? | 19:00Z | 19:28Z | 0h 27m | TC-JHK |
| 2026-08-17estimated | ? | ? | 19:04Z | 21:06Z | 2h 02m | TC-JLS |
| 2026-08-15estimated | ? | ? | 19:36Z | 21:41Z | 2h 05m | TC-JLY |
| 2026-08-14estimated | ? | ? | 19:03Z | 21:11Z | 2h 08m | TC-JLU |
| 2026-08-12estimated | ? | ? | 19:03Z | 21:11Z | 2h 08m | TC-JYJ |
Earlier flights (71) - back to 2026-03-29
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-23estimated | ? | ? | 18:55Z | 21:00Z | 2h 05m | TC-JLY |
| 2026-07-21partial | ? | ? | 01:07Z | TC-JLY | ||
| 2026-07-20estimated | ? | ? | 18:59Z | 19:30Z | 0h 31m | TC-JLY |
| 2026-07-19estimated | ? | ? | 19:05Z | 20:59Z | 1h 53m | TC-JLZ |
| 2026-07-18estimated | ? | ? | 19:06Z | 19:40Z | 0h 33m | TC-JLT |
| 2026-07-17estimated | ? | ? | 19:00Z | 20:59Z | 1h 59m | TC-JPH |
| 2026-07-16estimated | ? | ? | 18:56Z | 21:02Z | 2h 06m | TC-JLZ |
| 2026-07-15estimated | ? | ? | 18:59Z | 19:32Z | 0h 32m | TC-JLZ |
| 2026-07-14estimated | LTBP | LTAZ | 22:07 +03 | 00:12 +03 | 2h 05m | TC-JVP |
| 2026-07-13partial | LTAZ | ? | 04:14 +03 | TC-JTK | ||
| 2026-07-12estimated | LTBP | LTAZ | 22:28 +03 | 22:58 +03 | 0h 29m | TC-JTK |
| 2026-07-11estimated | LTBP | LTAZ | 22:03 +03 | 00:01 +03 | 1h 58m | TC-JLV |
| 2026-07-10estimated | LTBP | LTAZ | 23:11 +03 | 23:40 +03 | 0h 28m | TC-JPL |
| 2026-07-08estimated | LTBX | LTAZ | 21:53 +03 | 22:26 +03 | 0h 32m | TC-JVD |
| 2026-07-06partial | LTAZ | ? | 04:20 +03 | TC-JYG | ||
| 2026-07-05partial | LTAZ | ? | 04:13 +03 | TC-JPJ | ||
| 2026-07-04estimated | LTBP | LTAZ | 21:54 +03 | 22:22 +03 | 0h 27m | TC-JPJ |
| 2026-07-03estimated | LTBQ | LTAZ | 22:04 +03 | 00:00 +03 | 1h 55m | TC-JPR |
| 2026-07-02estimated | LTBP | LTAZ | 22:26 +03 | 22:56 +03 | 0h 29m | TC-JLU |
| 2026-07-01estimated | LTBP | LTAZ | 22:00 +03 | 22:32 +03 | 0h 31m | TC-JVF |
| 2026-06-29estimated | LTBX | LTAZ | 21:55 +03 | 22:28 +03 | 0h 32m | TC-JLT |
| 2026-06-28estimated | LTBX | LTAZ | 21:57 +03 | 22:28 +03 | 0h 30m | TC-JPS |
| 2026-06-26estimated | LTBP | LTAZ | 22:06 +03 | 22:38 +03 | 0h 31m | TC-JPP |
| 2026-06-24estimated | LTBX | ? | 22:05 +03 | 19:36Z | 0h 30m | TC-JVK |
| 2026-06-21estimated | LTBQ | LTAZ | 22:08 +03 | 00:13 +03 | 2h 05m | TC-JPL |
| 2026-06-20partial | ? | ? | 01:17Z | TC-JPP | ||
| 2026-06-19estimated | LTBQ | LTAZ | 22:00 +03 | 22:32 +03 | 0h 31m | TC-JPP |
| 2026-06-17estimated | LTBP | LTAZ | 21:49 +03 | 22:20 +03 | 0h 30m | TC-JYB |
| 2026-06-16partial | LTAZ | ? | 04:09 +03 | TC-JLU | ||
| 2026-06-15estimated | LTBP | LTAZ | 22:03 +03 | 22:34 +03 | 0h 31m | TC-JLU |
| 2026-06-14partial | LTAZ | ? | 04:14 +03 | TC-JLY | ||
| 2026-06-13estimated | LTBQ | LTAZ | 21:56 +03 | 22:22 +03 | 0h 25m | TC-JLY |
| 2026-06-12estimated | LTBQ | LTAZ | 22:00 +03 | 22:30 +03 | 0h 30m | TC-JSS |
| 2026-05-28partial | LTAZ | ? | 04:09 +03 | TC-JPK | ||
| 2026-05-27estimated | LTBP | LTAZ | 21:58 +03 | 22:32 +03 | 0h 33m | TC-JPK |
| 2026-05-26partial | LTAZ | ? | 04:10 +03 | TC-JPN | ||
| 2026-05-25estimated | LTBQ | LTAZ | 21:58 +03 | 22:30 +03 | 0h 31m | TC-JPN |
| 2026-05-24estimated | LTBQ | LTAZ | 22:05 +03 | 22:32 +03 | 0h 26m | TC-JLY |
| 2026-05-23estimated | LTBQ | LTAZ | 22:04 +03 | 00:08 +03 | 2h 03m | TC-JLY |
| 2026-05-22partial | ? | ? | 01:09Z | TC-JLS | ||
| 2026-05-21estimated | LTBX | LTAZ | 21:58 +03 | 22:32 +03 | 0h 33m | TC-JLS |
| 2026-05-20partial | LTBX | ? | 04:23 +03 | TC-JPI | ||
| 2026-05-19partial | LTBX | ? | 07:18 +03 | TC-JPJ | ||
| 2026-05-12estimated | LTBP | LTAZ | 21:59 +03 | 22:32 +03 | 0h 33m | TC-JPS |
| 2026-05-11partial | LTAZ | ? | 04:17 +03 | TC-JPR | ||
| 2026-05-10estimated | LTBX | LTAZ | 21:55 +03 | 22:28 +03 | 0h 33m | TC-JPR |
| 2026-05-09estimated | LTBP | LTAZ | 22:00 +03 | 22:28 +03 | 0h 28m | TC-JLT |
| 2026-05-08partial | LTAZ | ? | 04:12 +03 | TC-JLV | ||
| 2026-05-07estimated | LTBX | LTAZ | 22:02 +03 | 22:36 +03 | 0h 33m | TC-JLV |
| 2026-05-06partial | LTAZ | ? | 04:10 +03 | TC-JPP | ||
| 2026-05-05partial | LTAZ | ? | 04:17 +03 | TC-JPN | ||
| 2026-05-04estimated | LTBX | LTAZ | 22:00 +03 | 22:34 +03 | 0h 33m | TC-JPN |
| 2026-05-03partial | LTAZ | ? | 04:06 +03 | TC-JPN | ||
| 2026-05-02estimated | LTBX | LTAZ | 21:54 +03 | 22:26 +03 | 0h 31m | TC-JPN |
| 2026-04-26estimated | LTBP | LTAZ | 22:02 +03 | 00:14 +03 | 2h 11m | TC-JLT |
| 2026-04-25partial | LTAZ | ? | 04:10 +03 | TC-JSO | ||
| 2026-04-24estimated | ? | ? | 19:02Z | 19:32Z | 0h 30m | TC-JSO |
| 2026-04-21estimated | ? | ? | 18:54Z | 19:26Z | 0h 31m | TC-JPM |
| 2026-04-20estimated | ? | ? | 19:05Z | 19:36Z | 0h 31m | TC-JMK |
| 2026-04-19estimated | ? | ? | 18:58Z | 19:32Z | 0h 33m | TC-JLS |
| 2026-04-18partial | ? | ? | 01:14Z | TC-JPT | ||
| 2026-04-17partial | ? | ? | 01:06Z | TC-JLS | ||
| 2026-04-16estimated | ? | ? | 19:01Z | 19:32Z | 0h 31m | TC-JLS |
| 2026-04-15estimated | ? | ? | 19:05Z | 19:38Z | 0h 32m | TC-JLS |
| 2026-04-14partial | ? | ? | 01:11Z | TC-JPT | ||
| 2026-04-11estimated | ? | ? | 19:01Z | 19:30Z | 0h 29m | TC-JPS |
| 2026-04-05partial | ? | ? | 01:19Z | TC-JRT | ||
| 2026-04-04partial | ? | ? | 01:24Z | TC-JRS | ||
| 2026-04-03estimated | ? | ? | 19:08Z | 19:36Z | 0h 27m | TC-JRS |
| 2026-04-02estimated | ? | ? | 19:01Z | 19:38Z | 0h 36m | TC-JPT |
| 2026-03-29estimated | ? | ? | 19:08Z | 21:14Z | 2h 06m | TC-JHR |
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]