Airborne now · flying as FHY1528 at 35,000 ft
- Flights observed
- 302 showing last 50
- Avg flight time
- 2h 15m
- Typical route
- RMO → AYT
- Last seen
- Jul 26, 22:45 UTC
Live position
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | AYT → CGN | Jul 26, 20:40 UTC | Jul 26, 22:45 UTC | 2h 5m |
| 2026-07-26 | WAW → AYT | Jul 26, 16:30 UTC | Jul 26, 18:50 UTC | 2h 20m |
| 2026-07-26 | AYT → WAW | Jul 26, 12:25 UTC | Jul 26, 15:05 UTC | 2h 40m |
| 2026-07-26 | HAJ → AYT | Jul 26, 02:45 UTC | Jul 26, 06:00 UTC | 3h 15m |
| 2026-07-25 | AYT → HAJ | Jul 25, 22:10 UTC | Jul 26, 01:30 UTC | 3h 20m |
| 2026-07-25 | - | Jul 25, 18:05 UTC | Jul 25, 20:40 UTC | 2h 35m |
| 2026-07-25 | AYT → BUD | Jul 25, 14:40 UTC | Jul 25, 16:55 UTC | 2h 15m |
| 2026-07-25 | BER → AYT | Jul 25, 10:00 UTC | Jul 25, 13:15 UTC | 3h 15m |
| 2026-07-25 | AYT → BER | Jul 25, 05:30 UTC | Jul 25, 08:30 UTC | 3h 0m |
| 2026-07-24 | RMO → AYT | Jul 24, 22:15 UTC | Jul 25, 03:15 UTC | 5h 0m |
| 2026-07-24 | - | Jul 24, 17:55 UTC | Jul 24, 20:05 UTC | 2h 10m |
| 2026-07-24 | - | Jul 24, 14:40 UTC | Jul 24, 16:50 UTC | 2h 10m |
| 2026-07-24 | BTS → AYT | Jul 24, 09:10 UTC | Jul 24, 11:35 UTC | 2h 25m |
| 2026-07-24 | AYT → BTS | Jul 24, 04:55 UTC | Jul 24, 07:20 UTC | 2h 25m |
| 2026-07-23 | RMO → AYT | Jul 23, 22:10 UTC | Jul 24, 02:35 UTC | 4h 25m |
| 2026-07-23 | BER → AYT | Jul 23, 09:55 UTC | Jul 23, 12:55 UTC | 3h 0m |
| 2026-07-23 | AYT → BER | Jul 23, 05:25 UTC | Jul 23, 08:30 UTC | 3h 5m |
| 2026-07-23 | RMO → AYT | Jul 23, 01:35 UTC | Jul 23, 03:05 UTC | 1h 30m |
| 2026-07-22 | AYT → RMO | Jul 22, 22:15 UTC | Jul 22, 23:40 UTC | 1h 25m |
| 2026-07-22 | - | Jul 22, 11:10 UTC | Jul 22, 11:30 UTC | 20m |
| 2026-07-22 | AYT → WAW | Jul 22, 03:50 UTC | Jul 22, 05:25 UTC | 1h 35m |
| 2026-07-21 | KTW → AYT | Jul 21, 23:10 UTC | Jul 22, 01:30 UTC | 2h 20m |
| 2026-07-21 | - | Jul 21, 18:45 UTC | Jul 21, 21:15 UTC | 2h 30m |
| 2026-07-21 | - | Jul 21, 11:50 UTC | Jul 21, 12:45 UTC | 55m |
| 2026-07-21 | - | Jul 21, 08:15 UTC | Jul 21, 10:35 UTC | 2h 20m |
| 2026-07-21 | - | Jul 21, 04:25 UTC | Jul 21, 06:55 UTC | 2h 30m |
| 2026-07-20 | - | Jul 20, 14:35 UTC | Jul 20, 16:35 UTC | 2h 0m |
| 2026-07-20 | - | Jul 20, 11:30 UTC | Jul 20, 12:20 UTC | 50m |
| 2026-07-20 | - | Jul 20, 07:00 UTC | Jul 20, 09:45 UTC | 2h 45m |
| 2026-07-20 | BLL → AYT | Jul 20, 01:50 UTC | Jul 20, 03:00 UTC | 1h 10m |
| 2026-07-19 | - | Jul 19, 21:20 UTC | Jul 19, 22:20 UTC | 1h 0m |
| 2026-07-19 | - | Jul 19, 19:25 UTC | Jul 19, 20:05 UTC | 40m |
| 2026-07-19 | DUS → AYT | Jul 19, 10:30 UTC | Jul 19, 13:30 UTC | 3h 0m |
| 2026-07-19 | AYT → DUS | Jul 19, 05:25 UTC | Jul 19, 08:50 UTC | 3h 25m |
| 2026-07-19 | - | Jul 19, 02:00 UTC | Jul 19, 03:30 UTC | 1h 30m |
| 2026-07-18 | - | Jul 18, 22:55 UTC | Jul 19, 00:15 UTC | 1h 20m |
| 2026-07-18 | - | Jul 18, 18:15 UTC | Jul 18, 20:30 UTC | 2h 15m |
| 2026-07-18 | - | Jul 18, 14:25 UTC | Jul 18, 17:00 UTC | 2h 35m |
| 2026-07-18 | - | Jul 18, 09:55 UTC | Jul 18, 12:50 UTC | 2h 55m |
| 2026-07-18 | - | Jul 18, 05:25 UTC | Jul 18, 08:30 UTC | 3h 5m |
| 2026-07-18 | RMO → AYT | Jul 18, 01:34 UTC | Jul 18, 03:00 UTC | 1h 26m |
| 2026-07-17 | AYT → RMO | Jul 17, 22:10 UTC | Jul 17, 23:35 UTC | 1h 25m |
| 2026-07-17 | - | Jul 17, 17:50 UTC | Jul 17, 19:45 UTC | 1h 55m |
| 2026-07-17 | - | Jul 17, 14:24 UTC | Jul 17, 16:34 UTC | 2h 10m |
| 2026-07-17 | - | Jul 17, 09:15 UTC | Jul 17, 11:39 UTC | 2h 25m |
| 2026-07-17 | - | Jul 17, 05:10 UTC | Jul 17, 07:30 UTC | 2h 20m |
| 2026-07-17 | RMO → AYT | Jul 17, 01:15 UTC | Jul 17, 02:54 UTC | 1h 40m |
| 2026-07-16 | AYT → RMO | Jul 16, 22:05 UTC | Jul 16, 23:29 UTC | 1h 25m |
| 2026-07-16 | - | Jul 16, 12:55 UTC | Jul 16, 15:00 UTC | 2h 5m |
| 2026-07-16 | - | Jul 16, 09:30 UTC | Jul 16, 11:50 UTC | 2h 20m |
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 RMO and AYT based on observed flights.
Where is TC-FHC right now?
TC-FHC is currently airborne flying as FHY1528. Live position is shown on the map above.