sensors Mode-S transponder
4CAD47
ICAO 24-bit transponder address · allocated to Ireland
Currently assigned to EI-IFD · AIRBUS A-350-900
- Hex
- 4CAD47
- Octal
- 23126507
- Decimal
- 5,025,095
- Country
- IE
- Tail
- EI-IFD
- Type
- A359
- Flights observed
- 90
- Distinct callsigns
- 12
- Country
- IE
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 4CAD47 falls within the block assigned to Ireland (IE) by ICAO Annex 10, Volume III. Every aircraft registered in Ireland 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 12 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ITY680 | ITA Airways | 16 | 2026-05-28 |
| ITY621 | ITA Airways | 16 | 2026-05-26 |
| ITY620 | ITA Airways | 12 | 2026-05-26 |
| ITY793 | ITA Airways | 11 | 2026-05-28 |
| ITY792 | ITA Airways | 11 | 2026-05-27 |
| ITY681 | ITA Airways | 10 | 2026-05-29 |
| ITY6MO | ITA Airways | 3 | 2026-05-25 |
| ITY675 | ITA Airways | 3 | 2026-04-15 |
| ITY674 | ITA Airways | 3 | 2026-04-14 |
| ITY630 | ITA Airways | 3 | 2026-05-24 |
| ITY683 | ITA Airways | 1 | 2026-05-16 |
| ITY682 | ITA Airways | 1 | 2026-05-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | ITY681 | EZE → FCO | May 29, 15:55 UTC | May 30, 03:45 UTC | 11h 50m |
| 2026-05-28 | ITY680 | FCO → EZE | May 28, 21:20 UTC | May 29, 10:45 UTC | 13h 25m |
| 2026-05-28 | ITY793 | HND → FCO | May 28, 04:05 UTC | May 28, 15:40 UTC | 11h 35m |
| 2026-05-27 | ITY792 | FCO → HND | May 27, 13:35 UTC | May 28, 01:15 UTC | 11h 40m |
| 2026-05-26 | ITY621 | LAX → FCO | May 26, 22:25 UTC | May 27, 09:50 UTC | 11h 25m |
| 2026-05-26 | ITY620 | FCO → LAX | May 26, 08:04 UTC | May 26, 20:09 UTC | 12h 5m |
| 2026-05-25 | ITY6MO | MIA → FCO | May 25, 02:10 UTC | May 25, 09:30 UTC | 7h 20m |
| 2026-05-24 | ITY630 | FCO → MIA | May 24, 09:25 UTC | May 24, 19:30 UTC | 10h 5m |
| 2026-05-23 | ITY681 | EZE → FCO | May 23, 15:50 UTC | May 24, 04:00 UTC | 12h 11m |
| 2026-05-23 | ITY680 | FCO → EZE | May 23, 06:45 UTC | May 23, 10:15 UTC | 3h 30m |
| 2026-05-22 | ITY680 | FCO → EZE | May 22, 21:00 UTC | May 23, 02:10 UTC | 5h 10m |
| 2026-05-22 | ITY793 | HND → FCO | May 22, 04:15 UTC | May 22, 17:50 UTC | 13h 35m |
| 2026-05-21 | ITY792 | FCO → HND | May 21, 13:20 UTC | May 22, 01:15 UTC | 11h 55m |
| 2026-05-21 | ITY621 | LAX → FCO | May 21, 06:40 UTC | May 21, 09:30 UTC | 2h 50m |
| 2026-05-20 | ITY621 | LAX → FCO | May 20, 22:35 UTC | May 21, 03:15 UTC | 4h 40m |
| 2026-05-20 | ITY620 | FCO → LAX | May 20, 08:05 UTC | May 20, 19:55 UTC | 11h 50m |
| 2026-05-19 | ITY681 | EZE → FCO | May 19, 15:45 UTC | May 20, 04:00 UTC | 12h 15m |
| 2026-05-18 | ITY680 | FCO → EZE | May 18, 21:35 UTC | May 19, 10:40 UTC | 13h 5m |
| 2026-05-18 | ITY6MO | MIA → FCO | May 18, 00:25 UTC | May 18, 09:20 UTC | 8h 55m |
| 2026-05-17 | ITY630 | FCO → MIA | May 17, 09:50 UTC | May 17, 20:35 UTC | 10h 45m |
| 2026-05-16 | ITY683 | EZE → FCO | May 16, 04:40 UTC | May 16, 16:31 UTC | 11h 51m |
| 2026-05-15 | ITY682 | FCO → EZE | May 15, 12:45 UTC | May 16, 02:30 UTC | 13h 44m |
| 2026-05-10 | ITY621 | LAX → FCO | May 10, 22:25 UTC | May 11, 09:45 UTC | 11h 20m |
| 2026-05-10 | ITY620 | FCO → LAX | May 10, 08:15 UTC | May 10, 20:00 UTC | 11h 45m |
| 2026-05-09 | ITY681 | EZE → FCO | May 9, 16:25 UTC | May 10, 04:25 UTC | 12h 0m |
| 2026-05-08 | ITY680 | FCO → EZE | May 8, 20:55 UTC | May 9, 10:35 UTC | 13h 40m |
| 2026-05-08 | ITY793 | HND → FCO | May 8, 04:14 UTC | May 8, 18:35 UTC | 14h 20m |
| 2026-05-07 | ITY792 | FCO → HND | May 7, 13:15 UTC | May 8, 01:04 UTC | 11h 49m |
| 2026-05-06 | ITY621 | LAX → FCO | May 6, 22:35 UTC | May 7, 10:00 UTC | 11h 25m |
| 2026-05-06 | ITY620 | FCO → LAX | May 6, 08:10 UTC | May 6, 19:40 UTC | 11h 29m |
| 2026-05-05 | ITY681 | EZE → FCO | May 5, 15:55 UTC | May 6, 03:30 UTC | 11h 35m |
| 2026-05-04 | ITY680 | FCO → EZE | May 4, 21:05 UTC | May 5, 11:00 UTC | 13h 55m |
| 2026-05-04 | ITY6MO | MIA → FCO | May 4, 00:05 UTC | May 4, 08:50 UTC | 8h 45m |
| 2026-05-03 | ITY630 | FCO → MIA | May 3, 09:10 UTC | May 3, 19:50 UTC | 10h 40m |
| 2026-05-02 | ITY681 | EZE → FCO | May 2, 15:45 UTC | May 3, 03:50 UTC | 12h 4m |
| 2026-05-01 | ITY680 | FCO → EZE | May 1, 20:40 UTC | May 2, 10:10 UTC | 13h 31m |
| 2026-05-01 | ITY793 | HND → FCO | May 1, 04:05 UTC | May 1, 17:55 UTC | 13h 50m |
| 2026-04-30 | ITY792 | FCO → HND | Apr 30, 13:15 UTC | May 1, 00:50 UTC | 11h 35m |
| 2026-04-28 | ITY681 | EZE → FCO | Apr 28, 15:50 UTC | Apr 29, 04:05 UTC | 12h 15m |
| 2026-04-28 | ITY680 | FCO → EZE | Apr 28, 06:20 UTC | Apr 28, 10:15 UTC | 3h 55m |
| 2026-04-27 | ITY680 | FCO → EZE | Apr 27, 21:00 UTC | Apr 28, 06:15 UTC | 9h 15m |
| 2026-04-26 | ITY681 | EZE → FCO | Apr 26, 16:00 UTC | Apr 27, 03:55 UTC | 11h 55m |
| 2026-04-25 | ITY680 | FCO → EZE | Apr 25, 21:05 UTC | Apr 26, 10:25 UTC | 13h 20m |
| 2026-04-25 | ITY793 | HND → FCO | Apr 25, 05:20 UTC | Apr 25, 17:55 UTC | 12h 35m |
| 2026-04-25 | ITY793 | HND → FCO | Apr 25, 04:00 UTC | Apr 25, 04:35 UTC | 35m |
| 2026-04-25 | ITY792 | FCO → HND | Apr 25, 00:40 UTC | Apr 25, 01:30 UTC | 50m |
| 2026-04-24 | ITY792 | FCO → HND | Apr 24, 13:40 UTC | Apr 25, 00:20 UTC | 10h 40m |
| 2026-04-21 | ITY681 | EZE → FCO | Apr 21, 15:55 UTC | Apr 22, 04:05 UTC | 12h 10m |
| 2026-04-20 | ITY680 | FCO → EZE | Apr 20, 22:05 UTC | Apr 21, 11:50 UTC | 13h 45m |
| 2026-04-20 | ITY793 | HND → FCO | Apr 20, 05:15 UTC | Apr 20, 19:35 UTC | 14h 20m |
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 EI-IFD page for operator, model, and routing details .