Not currently tracked · last seen Jul 26, 22:15 UTC
- Flights observed
- 178 showing last 50
- Avg flight time
- 7h 2m
- Typical route
- AYT → AYT
- Last seen
- Jul 26, 22:15 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | AYT → LED | Jul 26, 19:00 UTC | Jul 26, 22:15 UTC | 3h 15m |
| 2026-07-26 | AYT → VKO | Jul 26, 07:05 UTC | Jul 26, 16:30 UTC | 9h 25m |
| 2026-07-25 | AYT → VKO | Jul 25, 18:05 UTC | Jul 26, 05:45 UTC | 11h 40m |
| 2026-07-25 | LED → AYT | Jul 25, 10:15 UTC | Jul 25, 14:10 UTC | 3h 55m |
| 2026-07-25 | IST → PRG | Jul 25, 04:40 UTC | Jul 25, 08:30 UTC | 3h 50m |
| 2026-07-24 | LED → AYT | Jul 24, 23:15 UTC | Jul 25, 01:30 UTC | 2h 15m |
| 2026-07-23 | AMS → IST | Jul 23, 19:10 UTC | Jul 23, 23:40 UTC | 4h 30m |
| 2026-07-22 | IST → BJV | Jul 22, 18:05 UTC | Jul 23, 03:40 UTC | 9h 35m |
| 2026-07-21 | AYT → LED | Jul 21, 18:55 UTC | Jul 21, 22:55 UTC | 4h 0m |
| 2026-07-21 | BER → AYT | Jul 21, 13:35 UTC | Jul 21, 14:30 UTC | 55m |
| 2026-07-20 | AYT → BER | Jul 20, 06:25 UTC | Jul 20, 07:20 UTC | 55m |
| 2026-07-19 | AYT → AYT | Jul 19, 17:40 UTC | Jul 20, 04:10 UTC | 10h 30m |
| 2026-07-19 | - | Jul 19, 04:55 UTC | Jul 19, 14:55 UTC | 10h 0m |
| 2026-07-18 | AYT → AYT | Jul 18, 17:40 UTC | Jul 19, 03:15 UTC | 9h 35m |
| 2026-07-18 | - | Jul 18, 05:10 UTC | Jul 18, 14:45 UTC | 9h 35m |
| 2026-07-17 | - | Jul 17, 17:35 UTC | Jul 18, 03:40 UTC | 10h 6m |
| 2026-07-16 | - | Jul 16, 17:30 UTC | Jul 17, 03:10 UTC | 9h 40m |
| 2026-07-15 | - | Jul 15, 16:55 UTC | Jul 16, 02:15 UTC | 9h 20m |
| 2026-07-14 | AYT → AYT | Jul 14, 18:55 UTC | Jul 15, 04:25 UTC | 9h 29m |
| 2026-07-14 | - | Jul 14, 05:05 UTC | Jul 14, 15:30 UTC | 10h 25m |
| 2026-07-13 | AYT → AYT | Jul 13, 17:40 UTC | Jul 14, 03:35 UTC | 9h 55m |
| 2026-07-13 | - | Jul 13, 06:50 UTC | Jul 13, 15:35 UTC | 8h 45m |
| 2026-07-13 | - | Jul 13, 01:01 UTC | Jul 13, 03:30 UTC | 2h 30m |
| 2026-07-12 | - | Jul 12, 23:20 UTC | Jul 12, 23:50 UTC | 30m |
| 2026-07-12 | - | Jul 12, 07:45 UTC | Jul 12, 11:35 UTC | 3h 50m |
| 2026-07-11 | - | Jul 11, 19:00 UTC | Jul 12, 06:05 UTC | 11h 5m |
| 2026-07-11 | - | Jul 11, 06:10 UTC | Jul 11, 15:40 UTC | 9h 30m |
| 2026-07-10 | - | Jul 10, 17:55 UTC | Jul 11, 04:25 UTC | 10h 30m |
| 2026-07-09 | - | Jul 9, 18:50 UTC | Jul 10, 04:15 UTC | 9h 25m |
| 2026-07-09 | - | Jul 9, 13:00 UTC | Jul 9, 15:55 UTC | 2h 55m |
| 2026-07-09 | - | Jul 9, 06:25 UTC | Jul 9, 09:40 UTC | 3h 15m |
| 2026-07-08 | - | Jul 8, 17:40 UTC | Jul 9, 04:00 UTC | 10h 20m |
| 2026-07-08 | - | Jul 8, 05:25 UTC | Jul 8, 14:40 UTC | 9h 15m |
| 2026-07-07 | AYT → AYT | Jul 7, 17:10 UTC | Jul 8, 03:40 UTC | 10h 30m |
| 2026-07-07 | LED → AYT | Jul 7, 12:40 UTC | Jul 7, 14:45 UTC | 2h 5m |
| 2026-07-07 | - | Jul 7, 05:35 UTC | Jul 7, 08:10 UTC | 2h 35m |
| 2026-07-06 | - | Jul 6, 17:15 UTC | Jul 7, 04:15 UTC | 11h 0m |
| 2026-07-05 | - | Jul 5, 18:45 UTC | Jul 6, 04:15 UTC | 9h 30m |
| 2026-07-05 | - | Jul 5, 06:10 UTC | Jul 5, 16:00 UTC | 9h 50m |
| 2026-07-05 | - | Jul 5, 00:30 UTC | Jul 5, 04:15 UTC | 3h 45m |
| 2026-07-04 | - | Jul 4, 18:55 UTC | Jul 4, 22:55 UTC | 4h 0m |
| 2026-07-04 | - | Jul 4, 05:30 UTC | Jul 4, 14:35 UTC | 9h 5m |
| 2026-07-03 | - | Jul 3, 17:20 UTC | Jul 4, 04:10 UTC | 10h 50m |
| 2026-07-03 | LED → AYT | Jul 3, 10:20 UTC | Jul 3, 14:30 UTC | 4h 10m |
| 2026-07-03 | VIE → ASR | Jul 3, 05:05 UTC | Jul 3, 08:45 UTC | 3h 40m |
| 2026-07-02 | - | Jul 2, 17:20 UTC | Jul 3, 03:10 UTC | 9h 50m |
| 2026-07-02 | - | Jul 2, 03:50 UTC | Jul 2, 06:00 UTC | 2h 10m |
| 2026-07-01 | - | Jul 1, 20:25 UTC | Jul 2, 00:35 UTC | 4h 10m |
| 2026-07-01 | AYT → AYT | Jul 1, 05:15 UTC | Jul 1, 14:55 UTC | 9h 40m |
| 2026-06-30 | - | Jun 30, 17:40 UTC | Jul 1, 03:45 UTC | 10h 5m |
Specifications
| Registration | TC-JRI |
| Aircraft type | AIRBUS A-321 (A321) |
| Mode-S code | 4BAA49 · 22725111 (octal) |
Looking for transponder-level data? View the Mode-S 4BAA49 page for country allocation, callsign history, and ADS-B signal details.
TC-JRI frequently asked
What type of aircraft is TC-JRI?
TC-JRI is a AIRBUS A-321 (ICAO type code A321).
What is the Mode-S transponder code for TC-JRI?
TC-JRI broadcasts on Mode-S (ICAO 24-bit) address 4BAA49 (octal 22725111). View the transponder page.
What route does TC-JRI typically fly?
TC-JRI most frequently flies between AYT and AYT based on observed flights.
Where is TC-JRI right now?
TC-JRI is not currently being tracked; last seen Jul 26, 22:15 UTC.