sensors Mode-S transponder
471F14
ICAO 24-bit transponder address · allocated to Hungary
Currently assigned to HA-LUA · BEECH 400 Beechjet
- Hex
- 471F14
- Octal
- 21617424
- Decimal
- 4,661,012
- Country
- HU
- Tail
- HA-LUA
- Type
- BE40
- Flights observed
- 51
- Distinct callsigns
- 7
- Country
- HU
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 471F14 falls within the block assigned to Hungary (HU) by ICAO Annex 10, Volume III. Every aircraft registered in Hungary 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 7 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-07 | FCA3UA | - | Jun 7, 21:15 UTC | Jun 7, 22:05 UTC | 50m |
| 2026-06-07 | FCA2UA | NCE → ATH | Jun 7, 17:40 UTC | Jun 7, 19:45 UTC | 2h 5m |
| 2026-06-07 | FCA1UA | BUD → NCE | Jun 7, 11:05 UTC | Jun 7, 13:00 UTC | 1h 55m |
| 2026-06-06 | FCA1UA | - | Jun 6, 17:44 UTC | Jun 6, 17:54 UTC | 10m |
| 2026-05-31 | FCA1UA | - | May 31, 16:15 UTC | May 31, 16:50 UTC | 35m |
| 2026-05-28 | FCA2UA | - | May 28, 10:50 UTC | May 28, 12:25 UTC | 1h 35m |
| 2026-05-28 | FCA1UA | - | May 28, 08:40 UTC | May 28, 09:50 UTC | 1h 10m |
| 2026-05-27 | FCA3UA | - | May 27, 08:25 UTC | May 27, 09:10 UTC | 45m |
| 2026-05-27 | FCA2UA | - | May 27, 06:29 UTC | May 27, 07:30 UTC | 1h 1m |
| 2026-05-27 | FCA1UA | - | May 27, 04:14 UTC | May 27, 05:24 UTC | 1h 10m |
| 2026-05-24 | FCA2UA | - | May 24, 14:45 UTC | May 24, 15:50 UTC | 1h 5m |
| 2026-05-24 | FCA1UA | - | May 24, 13:10 UTC | May 24, 14:05 UTC | 55m |
| 2026-05-23 | FCA2UA | KTW → BUD | May 23, 03:20 UTC | May 23, 04:00 UTC | 40m |
| 2026-05-23 | FCA1UA | - | May 23, 02:05 UTC | May 23, 02:45 UTC | 39m |
| 2026-05-20 | FCA4UA | - | May 20, 14:55 UTC | May 20, 15:25 UTC | 30m |
| 2026-05-20 | FCA3UA | - | May 20, 13:50 UTC | May 20, 14:15 UTC | 25m |
| 2026-05-20 | FCA2UA | - | May 20, 09:20 UTC | May 20, 09:55 UTC | 35m |
| 2026-05-20 | FCA1UA | - | May 20, 08:10 UTC | May 20, 08:25 UTC | 15m |
| 2026-05-19 | FCA1UA | - | May 19, 14:05 UTC | May 19, 15:05 UTC | 1h 0m |
| 2026-05-15 | FCA2UA | - | May 15, 15:45 UTC | May 15, 17:30 UTC | 1h 45m |
| 2026-05-15 | FCA1UA | BUD → GRQ | May 15, 07:30 UTC | May 15, 09:10 UTC | 1h 40m |
| 2026-05-13 | FCA3UA | MXP → BUD | May 13, 17:05 UTC | May 13, 18:20 UTC | 1h 15m |
| 2026-05-13 | FCA2UA | - | May 13, 14:00 UTC | May 13, 15:50 UTC | 1h 50m |
| 2026-05-13 | FCA1UA | - | May 13, 12:00 UTC | May 13, 13:05 UTC | 1h 5m |
| 2026-05-11 | FCA4UA | - | May 11, 09:50 UTC | May 11, 10:50 UTC | 1h 0m |
| 2026-05-11 | FCA3UA | - | May 11, 08:00 UTC | May 11, 08:45 UTC | 45m |
| 2026-05-11 | FCA2UA | - | May 11, 06:30 UTC | May 11, 07:00 UTC | 30m |
| 2026-05-11 | FCA1UA | - | May 11, 04:25 UTC | May 11, 05:20 UTC | 55m |
| 2026-05-08 | FCA2UA | VIE → BUD | May 8, 19:00 UTC | May 8, 19:35 UTC | 35m |
| 2026-05-08 | FCA1UA | BUD → VIE | May 8, 12:04 UTC | May 8, 12:34 UTC | 30m |
| 2026-05-05 | FCA2UA | - | May 5, 03:20 UTC | May 5, 04:20 UTC | 1h 0m |
| 2026-05-05 | FCA1UA | - | May 5, 01:45 UTC | May 5, 02:35 UTC | 50m |
| 2026-04-28 | FCA3UA | - | Apr 28, 17:35 UTC | Apr 28, 18:30 UTC | 55m |
| 2026-04-28 | FCA2UA | - | Apr 28, 15:30 UTC | Apr 28, 16:40 UTC | 1h 10m |
| 2026-04-28 | FCA1UA | BUD → BZG | Apr 28, 13:35 UTC | Apr 28, 14:45 UTC | 1h 10m |
| 2026-04-27 | FCA7UA | - | Apr 27, 16:50 UTC | Apr 27, 18:45 UTC | 1h 55m |
| 2026-04-27 | FCA6UA | - | Apr 27, 15:00 UTC | Apr 27, 15:30 UTC | 30m |
| 2026-04-27 | FCA5UA | - | Apr 27, 12:55 UTC | Apr 27, 14:10 UTC | 1h 15m |
| 2026-04-27 | FCA4UA | - | Apr 27, 10:05 UTC | Apr 27, 11:40 UTC | 1h 35m |
| 2026-04-27 | FCA3UA | LIN → CRL | Apr 27, 08:10 UTC | Apr 27, 09:25 UTC | 1h 15m |
| 2026-04-27 | FCA2UA | - | Apr 27, 05:45 UTC | Apr 27, 07:10 UTC | 1h 25m |
| 2026-04-27 | FCA1UA | - | Apr 27, 04:30 UTC | Apr 27, 04:50 UTC | 20m |
| 2026-04-26 | FCA2UA | NUE → BUD | Apr 26, 11:25 UTC | Apr 26, 12:25 UTC | 1h 0m |
| 2026-04-26 | FCA1UA | - | Apr 26, 08:30 UTC | Apr 26, 09:35 UTC | 1h 5m |
| 2026-04-24 | FCA3UA | BCN → BUD | Apr 24, 22:35 UTC | Apr 25, 00:45 UTC | 2h 10m |
| 2026-04-24 | FCA2UA | VNO → BCN | Apr 24, 17:10 UTC | Apr 24, 20:25 UTC | 3h 15m |
| 2026-04-24 | FCA1UA | BUD → VNO | Apr 24, 14:55 UTC | Apr 24, 16:20 UTC | 1h 25m |
| 2026-04-23 | FCA2UA | - | Apr 23, 17:05 UTC | Apr 23, 17:45 UTC | 39m |
| 2026-04-23 | FCA1UA | - | Apr 23, 12:50 UTC | Apr 23, 13:20 UTC | 30m |
| 2026-04-15 | FCA1UA | - | Apr 15, 08:05 UTC | Apr 15, 08:55 UTC | 50m |
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 HA-LUA page for operator, model, and routing details .