sensors Mode-S transponder
4B990B
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-FHK · AIRBUS A-320
- Hex
- 4B990B
- Octal
- 22714413
- Decimal
- 4,954,379
- Country
- TR
- Tail
- TC-FHK
- Type
- A320
- Flights observed
- 58
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 4B990B falls within the block assigned to Turkey (TR) by ICAO Annex 10, Volume III. Every aircraft registered in Turkey receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FHY418 | Freebird Airlines | 4 | 2026-05-09 |
| FHY417 | Freebird Airlines | 4 | 2026-05-08 |
| FHY7102 | - | 3 | 2026-04-22 |
| FHY542 | - | 3 | 2026-04-13 |
| FHY541 | - | 3 | 2026-04-13 |
| FHY1898 | Freebird Airlines | 3 | 2026-05-15 |
| FHY9612 | - | 2 | 2026-04-14 |
| FHY770 | Freebird Airlines | 2 | 2026-05-24 |
| FHY7112 | - | 2 | 2026-04-16 |
| FHY546 | Freebird Airlines | 2 | 2026-04-14 |
| FHY536 | - | 2 | 2026-04-13 |
| FHY1907 | Freebird Airlines | 2 | 2026-05-23 |
| FHY1903 | Freebird Airlines | 2 | 2026-04-29 |
| FHY9611 | - | 1 | 2026-04-14 |
| FHY952 | - | 1 | 2026-04-30 |
| FHY951 | - | 1 | 2026-04-30 |
| FHY949 | - | 1 | 2026-05-28 |
| FHY9451 | - | 1 | 2026-04-12 |
| FHY907P | - | 1 | 2026-05-20 |
| FHY906P | - | 1 | 2026-05-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | FHY1949 | - | May 28, 09:25 UTC | May 28, 09:55 UTC | 30m |
| 2026-05-28 | FHY949 | - | May 28, 06:15 UTC | May 28, 07:40 UTC | 1h 25m |
| 2026-05-24 | FHY770 | KTW → AYT | May 24, 15:35 UTC | May 24, 16:15 UTC | 40m |
| 2026-05-24 | FHY770 | KTW → AYT | May 24, 11:20 UTC | May 24, 14:35 UTC | 3h 15m |
| 2026-05-24 | FHY769 | - | May 24, 07:35 UTC | May 24, 10:05 UTC | 2h 30m |
| 2026-05-24 | FHY769P | - | May 24, 05:55 UTC | May 24, 06:30 UTC | 35m |
| 2026-05-23 | FHY1907 | SAW → CPH | May 23, 13:20 UTC | May 23, 14:10 UTC | 50m |
| 2026-05-23 | FHY806 | - | May 23, 06:25 UTC | May 23, 11:45 UTC | 5h 20m |
| 2026-05-20 | FHY907P | - | May 20, 16:55 UTC | May 20, 17:35 UTC | 40m |
| 2026-05-20 | FHY1907 | SAW → CPH | May 20, 14:50 UTC | May 20, 15:50 UTC | 1h 0m |
| 2026-05-20 | FHY906P | - | May 20, 11:35 UTC | May 20, 12:25 UTC | 50m |
| 2026-05-15 | FHY1898 | RMO → AYT | May 15, 22:05 UTC | May 16, 02:35 UTC | 4h 30m |
| 2026-05-14 | FHY1898 | RMO → AYT | May 14, 01:15 UTC | May 14, 04:40 UTC | 3h 25m |
| 2026-05-10 | FHY1898 | RMO → AYT | May 10, 01:24 UTC | May 10, 02:55 UTC | 1h 30m |
| 2026-05-09 | FHY1897 | AYT → RMO | May 9, 22:10 UTC | May 9, 23:35 UTC | 1h 25m |
| 2026-05-09 | FHY754 | KRK → AYT | May 9, 11:00 UTC | May 9, 13:20 UTC | 2h 20m |
| 2026-05-09 | FHY753 | AYT → BZG | May 9, 07:35 UTC | May 9, 09:55 UTC | 2h 20m |
| 2026-05-09 | FHY418 | TLL → AYT | May 9, 01:40 UTC | May 9, 05:20 UTC | 3h 40m |
| 2026-05-08 | FHY417 | AYT → TLL | May 8, 20:35 UTC | May 9, 00:20 UTC | 3h 45m |
| 2026-04-30 | FHY952 | - | Apr 30, 11:40 UTC | Apr 30, 13:55 UTC | 2h 15m |
| 2026-04-30 | FHY951 | - | Apr 30, 08:20 UTC | Apr 30, 10:15 UTC | 1h 55m |
| 2026-04-29 | FHY1903 | STN → SAW | Apr 29, 09:20 UTC | Apr 29, 11:40 UTC | 2h 20m |
| 2026-04-26 | FHY1903 | STN → SAW | Apr 26, 13:30 UTC | Apr 26, 16:15 UTC | 2h 45m |
| 2026-04-25 | FHY7211 | - | Apr 25, 14:50 UTC | Apr 25, 22:25 UTC | 7h 35m |
| 2026-04-23 | FHY7204 | - | Apr 23, 03:20 UTC | Apr 23, 22:30 UTC | 19h 10m |
| 2026-04-22 | FHY7216 | - | Apr 22, 14:50 UTC | Apr 23, 09:55 UTC | 19h 5m |
| 2026-04-22 | FHY7102 | - | Apr 22, 13:40 UTC | Apr 23, 09:55 UTC | 20h 15m |
| 2026-04-22 | FHY7102 | - | Apr 22, 08:50 UTC | Apr 23, 08:45 UTC | 23h 55m |
| 2026-04-22 | FHY7102 | - | Apr 22, 08:40 UTC | Apr 23, 04:40 UTC | 20h 0m |
| 2026-04-22 | FHY710P | - | Apr 22, 06:10 UTC | Apr 22, 06:25 UTC | 15m |
| 2026-04-19 | FHY728 | RIX → AYT | Apr 19, 02:05 UTC | Apr 19, 05:10 UTC | 3h 5m |
| 2026-04-18 | FHY727 | AYT → AMS | Apr 18, 20:50 UTC | Apr 19, 00:10 UTC | 3h 20m |
| 2026-04-18 | FHY418 | TLL → AYT | Apr 18, 04:45 UTC | Apr 18, 05:20 UTC | 35m |
| 2026-04-18 | FHY418 | TLL → AYT | Apr 18, 03:25 UTC | Apr 18, 05:20 UTC | 1h 55m |
| 2026-04-18 | FHY418 | TLL → AYT | Apr 18, 01:50 UTC | Apr 18, 03:20 UTC | 1h 30m |
| 2026-04-17 | FHY417 | AYT → TLL | Apr 17, 23:25 UTC | Apr 18, 00:40 UTC | 1h 15m |
| 2026-04-17 | FHY417 | AYT → TLL | Apr 17, 21:25 UTC | Apr 17, 23:20 UTC | 1h 55m |
| 2026-04-17 | FHY417 | AYT → TLL | Apr 17, 20:45 UTC | Apr 17, 21:20 UTC | 35m |
| 2026-04-16 | FHY711P | - | Apr 16, 11:25 UTC | Apr 16, 11:35 UTC | 10m |
| 2026-04-16 | FHY7112 | - | Apr 16, 09:10 UTC | Apr 16, 09:45 UTC | 35m |
| 2026-04-16 | FHY7112 | - | Apr 16, 08:24 UTC | Apr 16, 09:05 UTC | 40m |
| 2026-04-16 | FHY7111 | - | Apr 16, 03:30 UTC | Apr 16, 05:00 UTC | 1h 30m |
| 2026-04-14 | FHY9612 | - | Apr 14, 20:55 UTC | Apr 14, 21:30 UTC | 35m |
| 2026-04-14 | FHY9612 | - | Apr 14, 20:10 UTC | Apr 14, 20:50 UTC | 40m |
| 2026-04-14 | FHY9611 | - | Apr 14, 14:50 UTC | Apr 14, 15:40 UTC | 50m |
| 2026-04-14 | FHY546 | LYS → AYT | Apr 14, 09:10 UTC | Apr 14, 10:00 UTC | 50m |
| 2026-04-14 | FHY546 | LYS → AYT | Apr 14, 07:45 UTC | Apr 14, 09:05 UTC | 1h 20m |
| 2026-04-14 | FHY545 | AYT → ARN | Apr 14, 05:15 UTC | Apr 14, 06:45 UTC | 1h 30m |
| 2026-04-13 | FHY542 | - | Apr 13, 16:15 UTC | Apr 13, 16:55 UTC | 40m |
| 2026-04-13 | FHY542 | - | Apr 13, 15:50 UTC | Apr 13, 16:55 UTC | 1h 5m |
About Mode-S
A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.
Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.
Prefer a tail-number view? See the TC-FHK page for operator, model, and routing details .