Flight
TKJ3NR
Flight history and live tracking for TKJ3NR, operated by Tarkim Havacilik. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | Tarkim Havacilik |
| Observed route | LTBQ → LTAZ |
Flight history 42 flights since Mar 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-17estimated | ? | ? | 14:01Z | 16:48Z | 2h 46m | 4BD8D2 |
| 2026-08-16estimated | ? | ? | 14:04Z | 16:12Z | 2h 08m | 4BB2B2 |
Earlier flights (40) - back to 2026-03-30
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-20estimated | ? | ? | 14:16Z | 14:42Z | 0h 26m | TC-JHD |
| 2026-07-13estimated | LTBQ | LTAZ | 17:10 +03 | 19:18 +03 | 2h 08m | 4BBD0B |
| 2026-07-12estimated | LTBQ | LTAZ | 17:02 +03 | 17:26 +03 | 0h 23m | TC-JHB |
| 2026-07-06estimated | LTBQ | LTAZ | 17:06 +03 | 17:28 +03 | 0h 21m | 4BD8C2 |
| 2026-07-05estimated | LTBQ | LTAZ | 17:06 +03 | 17:32 +03 | 0h 25m | 4BB299 |
| 2026-06-29estimated | LTBQ | LTAZ | 16:58 +03 | 19:18 +03 | 2h 19m | 4BD8C1 |
| 2026-06-28estimated | LTBQ | LTAZ | 17:09 +03 | 19:14 +03 | 2h 04m | 4BD8C9 |
| 2026-06-22estimated | LTBQ | LTAZ | 16:59 +03 | 19:08 +03 | 2h 08m | 4BBD12 |
| 2026-06-21estimated | LTBQ | LTAZ | 17:25 +03 | 19:30 +03 | 2h 05m | 4BBD12 |
| 2026-06-15estimated | LTBQ | LTAZ | 16:54 +03 | 19:00 +03 | 2h 05m | TC-JGY |
| 2026-06-14estimated | LTBQ | LTAZ | 17:54 +03 | 20:00 +03 | 2h 05m | 4BBD16 |
| 2026-05-27estimated | LTBQ | LTAZ | 17:21 +03 | 17:52 +03 | 0h 30m | 4BAA94 |
| 2026-05-26estimated | LTBQ | LTAZ | 16:38 +03 | 18:53 +03 | 2h 14m | 4BBD01 |
| 2026-05-25estimated | LTBQ | LTAZ | 16:48 +03 | 18:55 +03 | 2h 07m | TC-JFZ |
| 2026-05-23estimated | LTBQ | LTAZ | 17:10 +03 | 19:18 +03 | 2h 07m | TC-JGC |
| 2026-05-22estimated | ? | ? | 13:57Z | 14:26Z | 0h 29m | 4BBD19 |
| 2026-05-20estimated | LTBQ | LTAZ | 03:45 +03 | 09:18 +03 | 5h 32m | TC-LTT |
| 2026-05-19partial | LTBX | ? | 19:13 +03 | 4BB295 | ||
| 2026-05-12estimated | LTBX | LTAZ | 16:52 +03 | 19:04 +03 | 2h 11m | 4BBD19 |
| 2026-05-11estimated | LTBX | LTAZ | 17:02 +03 | 19:05 +03 | 2h 02m | TC-JZV |
| 2026-05-10estimated | LTBQ | LTAZ | 17:58 +03 | 19:56 +03 | 1h 58m | TC-LUC |
| 2026-05-08estimated | LTBX | LTAZ | 16:41 +03 | 18:58 +03 | 2h 17m | 4BBD19 |
| 2026-05-05estimated | LTBX | LTAZ | 17:15 +03 | 17:52 +03 | 0h 37m | 4BB299 |
| 2026-05-04estimated | LTBQ | LTAZ | 17:28 +03 | 18:00 +03 | 0h 31m | TC-JFC |
| 2026-05-03estimated | LTBQ | LTAZ | 17:49 +03 | 18:20 +03 | 0h 30m | 4BBD0D |
| 2026-05-02estimated | LTBQ | LTAZ | 17:06 +03 | 19:23 +03 | 2h 16m | TC-LTT |
| 2026-04-25estimated | LTBQ | LTAZ | 16:51 +03 | 17:20 +03 | 0h 28m | 4BBD02 |
| 2026-04-22estimated | ? | ? | 14:32Z | 16:42Z | 2h 09m | TC-JGS |
| 2026-04-21estimated | ? | ? | 14:17Z | 16:28Z | 2h 10m | TC-LAE |
| 2026-04-20estimated | ? | ? | 14:17Z | 16:12Z | 1h 55m | TC-JZU |
| 2026-04-18estimated | ? | ? | 14:04Z | 14:30Z | 0h 25m | TC-JFZ |
| 2026-04-17estimated | ? | ? | 13:35Z | 16:02Z | 2h 26m | TC-JFR |
| 2026-04-15estimated | ? | ? | 14:27Z | 14:52Z | 0h 24m | 4BBD07 |
| 2026-04-14estimated | ? | ? | 13:35Z | 14:00Z | 0h 24m | TC-JZZ |
| 2026-04-12estimated | ? | ? | 14:47Z | 15:20Z | 0h 32m | TC-LAJ |
| 2026-04-11estimated | ? | ? | 14:11Z | 16:17Z | 2h 06m | TC-JFO |
| 2026-04-04estimated | ? | ? | 14:02Z | 16:05Z | 2h 02m | TC-JGS |
| 2026-04-03estimated | ? | ? | 14:21Z | 14:46Z | 0h 24m | TC-JKU |
| 2026-03-31estimated | ? | ? | 14:34Z | 16:50Z | 2h 15m | TC-JFH |
| 2026-03-30estimated | LTFJ | ? | 18:17 +03 | 15:54Z | 0h 36m | 4BAA99 |
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]