Not currently tracked · last seen 6h ago
- Flights observed
- 146 showing last 50
- Avg flight time
- 3h 13m
- Typical route
- AYT → BZG
- Last seen
- 6h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-02 | - | Jun 2, 13:00 UTC | Jun 2, 21:00 UTC | 8h 0m |
| 2026-06-02 | - | Jun 2, 03:45 UTC | Jun 2, 11:30 UTC | 7h 45m |
| 2026-06-01 | - | Jun 1, 22:45 UTC | Jun 2, 01:05 UTC | 2h 20m |
| 2026-06-01 | AYT → BZG | Jun 1, 18:55 UTC | Jun 1, 21:25 UTC | 2h 30m |
| 2026-06-01 | - | Jun 1, 05:40 UTC | Jun 1, 14:55 UTC | 9h 15m |
| 2026-05-31 | - | May 31, 15:00 UTC | Jun 1, 14:40 UTC | 23h 40m |
| 2026-05-31 | - | May 31, 11:50 UTC | May 31, 13:15 UTC | 1h 25m |
| 2026-05-30 | AYT → AMS | May 30, 20:55 UTC | May 31, 00:25 UTC | 3h 30m |
| 2026-05-30 | - | May 30, 16:40 UTC | May 30, 19:10 UTC | 2h 30m |
| 2026-05-30 | - | May 30, 12:20 UTC | May 30, 15:25 UTC | 3h 5m |
| 2026-05-30 | - | May 30, 08:20 UTC | May 30, 10:50 UTC | 2h 30m |
| 2026-05-30 | AYT → PRG | May 30, 03:55 UTC | May 30, 07:00 UTC | 3h 5m |
| 2026-05-29 | ERF → AYT | May 29, 23:20 UTC | May 30, 02:10 UTC | 2h 50m |
| 2026-05-29 | AYT → ERF | May 29, 18:25 UTC | May 29, 21:40 UTC | 3h 15m |
| 2026-05-28 | MUC → AYT | May 28, 08:40 UTC | May 28, 11:20 UTC | 2h 40m |
| 2026-05-28 | AYT → MUC | May 28, 03:30 UTC | May 28, 06:30 UTC | 3h 0m |
| 2026-05-27 | - | May 27, 22:45 UTC | May 28, 00:55 UTC | 2h 10m |
| 2026-05-27 | AYT → BZG | May 27, 18:50 UTC | May 27, 21:15 UTC | 2h 25m |
| 2026-05-27 | MUC → AYT | May 27, 07:55 UTC | May 27, 10:35 UTC | 2h 40m |
| 2026-05-27 | AYT → MUC | May 27, 03:24 UTC | May 27, 06:15 UTC | 2h 50m |
| 2026-05-26 | FDH → AYT | May 26, 16:00 UTC | May 26, 18:50 UTC | 2h 50m |
| 2026-05-26 | AYT → FDH | May 26, 11:24 UTC | May 26, 14:24 UTC | 3h 0m |
| 2026-05-26 | KUN → AYT | May 26, 02:10 UTC | May 26, 05:10 UTC | 3h 0m |
| 2026-05-25 | - | May 25, 20:40 UTC | May 25, 23:45 UTC | 3h 5m |
| 2026-05-25 | IST → AYT | May 25, 09:15 UTC | May 25, 11:30 UTC | 2h 15m |
| 2026-05-25 | AYT → AYT | May 25, 05:25 UTC | May 25, 07:45 UTC | 2h 20m |
| 2026-05-25 | NUE → AYT | May 25, 01:55 UTC | May 25, 02:30 UTC | 35m |
| 2026-05-24 | NUE → AYT | May 24, 23:35 UTC | May 24, 23:46 UTC | 11m |
| 2026-05-24 | AYT → NUE | May 24, 18:55 UTC | May 24, 21:45 UTC | 2h 50m |
| 2026-05-24 | FKB → AYT | May 24, 11:50 UTC | May 24, 15:00 UTC | 3h 10m |
| 2026-05-24 | AYT → FKB | May 24, 07:25 UTC | May 24, 10:40 UTC | 3h 15m |
| 2026-05-24 | HAJ → AYT | May 24, 01:50 UTC | May 24, 04:55 UTC | 3h 5m |
| 2026-05-23 | AYT → HAJ | May 23, 20:45 UTC | May 24, 00:00 UTC | 3h 15m |
| 2026-05-23 | STR → AYT | May 23, 15:30 UTC | May 23, 18:20 UTC | 2h 51m |
| 2026-05-23 | - | May 23, 13:05 UTC | May 23, 13:55 UTC | 50m |
| 2026-05-23 | - | May 23, 10:45 UTC | May 23, 12:10 UTC | 1h 25m |
| 2026-05-23 | - | May 23, 07:55 UTC | May 23, 09:20 UTC | 1h 25m |
| 2026-05-23 | - | May 23, 05:05 UTC | May 23, 06:35 UTC | 1h 30m |
| 2026-05-22 | - | May 22, 14:15 UTC | May 22, 15:45 UTC | 1h 30m |
| 2026-05-22 | - | May 22, 11:50 UTC | May 22, 13:15 UTC | 1h 25m |
| 2026-05-22 | - | May 22, 07:55 UTC | May 22, 09:50 UTC | 1h 55m |
| 2026-05-22 | - | May 22, 05:05 UTC | May 22, 07:00 UTC | 1h 55m |
| 2026-05-21 | - | May 21, 13:15 UTC | May 21, 14:50 UTC | 1h 35m |
| 2026-05-21 | - | May 21, 10:30 UTC | May 21, 11:55 UTC | 1h 25m |
| 2026-05-21 | - | May 21, 07:40 UTC | May 21, 09:15 UTC | 1h 35m |
| 2026-05-21 | - | May 21, 05:05 UTC | May 21, 06:30 UTC | 1h 25m |
| 2026-05-20 | - | May 20, 16:15 UTC | May 20, 18:20 UTC | 2h 5m |
| 2026-05-20 | AYT → HAJ | May 20, 12:10 UTC | May 20, 15:00 UTC | 2h 50m |
| 2026-05-19 | - | May 19, 07:15 UTC | May 19, 14:50 UTC | 7h 35m |
| 2026-05-18 | - | May 18, 12:00 UTC | May 18, 14:55 UTC | 2h 55m |
Specifications
| Registration | TC-FHC |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 4B9903 · 22714403 (octal) |
Looking for transponder-level data? View the Mode-S 4B9903 page for country allocation, callsign history, and ADS-B signal details.
TC-FHC frequently asked
What type of aircraft is TC-FHC?
TC-FHC is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for TC-FHC?
TC-FHC broadcasts on Mode-S (ICAO 24-bit) address 4B9903 (octal 22714403). View the transponder page.
What route does TC-FHC typically fly?
TC-FHC most frequently flies between AYT and BZG based on observed flights.
Where is TC-FHC right now?
TC-FHC is not currently being tracked; last seen 6h ago.