Flight
THY236
Flight history and live tracking for THY236, 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 | LTBQ → UGGG |
Flight history 44 flights since Jan 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-21estimated | ? | ? | 16:14Z | 17:44Z | 1h 29m | TC-LNF |
| 2026-08-19estimated | ? | ? | 16:19Z | 17:34Z | 1h 14m | TC-JOG |
| 2026-08-17estimated | ? | ? | 16:52Z | 18:20Z | 1h 28m | TC-JOI |
| 2026-08-14estimated | ? | ? | 16:24Z | 18:12Z | 1h 47m | TC-JOH |
| 2026-08-12estimated | ? | ? | 16:10Z | 17:14Z | 1h 03m | TC-JNP |
Earlier flights (39) - back to 2026-01-28
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-22estimated | ? | ? | 17:22Z | 18:06Z | 0h 43m | TC-JNT |
| 2026-07-18estimated | ? | ? | 16:00Z | 17:08Z | 1h 07m | TC-JNJ |
| 2026-07-17estimated | ? | ? | 16:21Z | 17:30Z | 1h 08m | TC-JOA |
| 2026-07-15estimated | ? | ? | 15:53Z | 17:08Z | 1h 15m | TC-LNC |
| 2026-07-10estimated | LTBQ | ? | 19:01 +03 | 16:46Z | 0h 45m | TC-JOI |
| 2026-07-04estimated | UGGG | ? | 12:06 +04 | 17:02Z | 8h 55m | TC-JNJ |
| 2026-07-03estimated | LTAX | UGGG | 19:05 +03 | 21:20 +04 | 1h 14m | TC-JNJ |
| 2026-07-01estimated | LTAX | LTCM | 19:14 +03 | 19:36 +03 | 0h 21m | TC-LNF |
| 2026-06-29 | LTBP | LTAW | 19:06 +03 | 19:48 +03 | 0h 41m | TC-LNF |
| 2026-06-27estimated | LTBX | UGGG | 19:37 +03 | 22:06 +04 | 1h 28m | TC-JOB |
| 2026-06-26estimated | LTBX | LTCE | 20:01 +03 | 21:06 +03 | 1h 04m | TC-JOK |
| 2026-06-22estimated | LTBP | UGGG | 19:01 +03 | 21:30 +04 | 1h 29m | TC-JOG |
| 2026-06-20estimated | LTBQ | UGGG | 19:06 +03 | 21:30 +04 | 1h 23m | TC-JOD |
| 2026-06-19estimated | LTBQ | UGGG | 19:18 +03 | 21:30 +04 | 1h 11m | TC-LND |
| 2026-06-15estimated | LTBQ | LTAL | 19:04 +03 | 19:24 +03 | 0h 19m | TC-JNJ |
| 2026-05-29estimated | LTBQ | LTCE | 19:11 +03 | 20:14 +03 | 1h 02m | TC-JOD |
| 2026-05-27estimated | ? | ? | 19:40Z | 20:22Z | 0h 41m | TC-JNT |
| 2026-05-23estimated | ? | ? | 05:03Z | 20:42Z | 15h 38m | TC-JNT |
| 2026-05-22estimated | ? | ? | 17:00Z | 20:32Z | 3h 31m | TC-JNT |
| 2026-05-20estimated | LTBQ | LTCE | 19:15 +03 | 20:24 +03 | 1h 09m | TC-JNK |
| 2026-05-19partial | LTBP | ? | 06:36 +03 | TC-LND | ||
| 2026-05-11estimated | LTBQ | UGGG | 19:00 +03 | 00:42 +04 | 4h 41m | TC-JOI |
| 2026-05-09estimated | LTBQ | UGGG | 19:14 +03 | 00:44 +04 | 4h 30m | TC-JNT |
| 2026-05-06estimated | LTBP | LTCE | 19:00 +03 | 20:12 +03 | 1h 11m | TC-LNF |
| 2026-05-04estimated | LTBX | LTAR | 18:55 +03 | 23:46 +03 | 4h 50m | TC-LNG |
| 2026-05-01estimated | ? | ? | 20:12Z | 20:54Z | 0h 41m | TC-JOG |
| 2026-04-29estimated | LTBX | LTAR | 18:57 +03 | 23:36 +03 | 4h 38m | TC-JNM |
| 2026-04-24estimated | ? | ? | 15:54Z | 20:22Z | 4h 27m | TC-JNN |
| 2026-04-22estimated | ? | ? | 15:44Z | 20:18Z | 4h 33m | TC-LND |
| 2026-04-20estimated | ? | ? | 15:55Z | 20:28Z | 4h 32m | TC-LND |
| 2026-04-18estimated | ? | ? | 04:58Z | 21:12Z | 16h 13m | TC-JOK |
| 2026-04-17estimated | ? | ? | 15:42Z | 16:56Z | 1h 13m | TC-JOK |
| 2026-04-11estimated | ? | ? | 04:35Z | 20:56Z | 16h 20m | TC-LNE |
| 2026-04-04estimated | ? | ? | 15:47Z | 20:40Z | 4h 53m | TC-LNF |
| 2026-04-03estimated | ? | ? | 16:06Z | 20:42Z | 4h 35m | TC-JOB |
| 2026-03-30estimated | ? | ? | 20:13Z | 20:50Z | 0h 36m | TC-JOL |
| 2026-03-13estimated | ? | ? | 19:51Z | 20:28Z | 0h 36m | TC-JNM |
| 2026-02-11 | LTBA | ? | 18:35 +03 | 16:51Z | 1h 16m | 4BA9C3 |
| 2026-01-28 | LTBA | ? | 19:05 +03 | 20:23Z | 4h 17m | 4BA9C1 |
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]