sensors Mode-S transponder
4CAD44
ICAO 24-bit transponder address · allocated to Ireland
Currently assigned to EI-IFA · AIRBUS A-350-900
- Hex
- 4CAD44
- Octal
- 23126504
- Decimal
- 5,025,092
- Country
- IE
- Tail
- EI-IFA
- Type
- A359
- Flights observed
- 66
- Distinct callsigns
- 12
- Country
- IE
- Last broadcast
- 5d ago
Last known position
Country allocation
The ICAO 24-bit address 4CAD44 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 |
|---|---|---|---|
| ITY793 | ITA Airways | 13 | 2026-05-20 |
| ITY792 | ITA Airways | 12 | 2026-05-19 |
| ITY621 | ITA Airways | 10 | 2026-05-23 |
| ITY620 | ITA Airways | 10 | 2026-05-23 |
| ITY681 | ITA Airways | 9 | 2026-05-22 |
| ITY680 | ITA Airways | 6 | 2026-05-21 |
| ITY6MO | ITA Airways | 1 | 2026-05-11 |
| ITY683 | ITA Airways | 1 | 2026-05-09 |
| ITY682 | ITA Airways | 1 | 2026-05-08 |
| ITY679 | ITA Airways | 1 | 2026-04-19 |
| ITY678 | ITA Airways | 1 | 2026-04-19 |
| ITY630 | ITA Airways | 1 | 2026-05-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-23 | ITY621 | LAX → FCO | May 23, 22:25 UTC | May 24, 09:45 UTC | 11h 20m |
| 2026-05-23 | ITY620 | FCO → LAX | May 23, 08:05 UTC | May 23, 20:05 UTC | 12h 0m |
| 2026-05-22 | ITY681 | EZE → FCO | May 22, 15:50 UTC | May 23, 04:05 UTC | 12h 15m |
| 2026-05-21 | ITY680 | FCO → EZE | May 21, 21:20 UTC | May 22, 10:45 UTC | 13h 25m |
| 2026-05-20 | ITY793 | HND → FCO | May 20, 03:50 UTC | May 20, 17:45 UTC | 13h 56m |
| 2026-05-19 | ITY792 | FCO → HND | May 19, 13:20 UTC | May 20, 01:20 UTC | 12h 0m |
| 2026-05-18 | ITY793 | HND → FCO | May 18, 03:50 UTC | May 18, 17:35 UTC | 13h 45m |
| 2026-05-17 | ITY792 | FCO → HND | May 17, 13:15 UTC | May 18, 01:00 UTC | 11h 45m |
| 2026-05-16 | ITY621 | LAX → FCO | May 16, 22:30 UTC | May 17, 09:20 UTC | 10h 50m |
| 2026-05-16 | ITY620 | FCO → LAX | May 16, 07:55 UTC | May 16, 20:05 UTC | 12h 10m |
| 2026-05-14 | ITY621 | LAX → FCO | May 14, 22:30 UTC | May 15, 09:45 UTC | 11h 15m |
| 2026-05-14 | ITY620 | FCO → LAX | May 14, 08:00 UTC | May 14, 20:05 UTC | 12h 5m |
| 2026-05-13 | ITY681 | EZE → FCO | May 13, 16:00 UTC | May 14, 03:40 UTC | 11h 40m |
| 2026-05-12 | ITY680 | FCO → EZE | May 12, 21:40 UTC | May 13, 11:50 UTC | 14h 10m |
| 2026-05-12 | ITY793 | HND → FCO | May 12, 05:35 UTC | May 12, 19:20 UTC | 13h 45m |
| 2026-05-11 | ITY792 | FCO → HND | May 11, 13:15 UTC | May 11, 21:00 UTC | 7h 46m |
| 2026-05-11 | ITY6MO | MIA → FCO | May 11, 00:00 UTC | May 11, 09:15 UTC | 9h 15m |
| 2026-05-10 | ITY630 | FCO → MIA | May 10, 09:05 UTC | May 10, 19:19 UTC | 10h 15m |
| 2026-05-09 | ITY683 | EZE → FCO | May 9, 04:15 UTC | May 9, 16:30 UTC | 12h 15m |
| 2026-05-08 | ITY682 | FCO → EZE | May 8, 12:25 UTC | May 9, 02:15 UTC | 13h 50m |
| 2026-05-07 | ITY681 | EZE → FCO | May 7, 15:55 UTC | May 8, 04:04 UTC | 12h 10m |
| 2026-05-06 | ITY680 | FCO → EZE | May 6, 21:00 UTC | May 7, 10:40 UTC | 13h 40m |
| 2026-05-06 | ITY793 | HND → FCO | May 6, 03:55 UTC | May 6, 18:00 UTC | 14h 4m |
| 2026-05-05 | ITY792 | FCO → HND | May 5, 13:35 UTC | May 6, 01:30 UTC | 11h 55m |
| 2026-05-04 | ITY681 | EZE → FCO | May 4, 23:20 UTC | May 5, 03:55 UTC | 4h 35m |
| 2026-05-04 | ITY681 | EZE → FCO | May 4, 16:10 UTC | May 4, 19:00 UTC | 2h 51m |
| 2026-05-03 | ITY680 | FCO → EZE | May 3, 22:09 UTC | May 4, 11:55 UTC | 13h 45m |
| 2026-05-03 | ITY793 | HND → FCO | May 3, 04:50 UTC | May 3, 18:25 UTC | 13h 35m |
| 2026-05-02 | ITY792 | FCO → HND | May 2, 13:50 UTC | May 3, 01:50 UTC | 12h 0m |
| 2026-05-01 | ITY621 | LAX → FCO | May 1, 22:35 UTC | May 2, 10:05 UTC | 11h 30m |
| 2026-05-01 | ITY620 | FCO → LAX | May 1, 08:05 UTC | May 1, 20:10 UTC | 12h 5m |
| 2026-04-29 | ITY681 | EZE → FCO | Apr 29, 15:50 UTC | Apr 30, 03:45 UTC | 11h 54m |
| 2026-04-28 | ITY680 | FCO → EZE | Apr 28, 21:50 UTC | Apr 29, 11:15 UTC | 13h 26m |
| 2026-04-28 | ITY793 | HND → FCO | Apr 28, 04:30 UTC | Apr 28, 18:45 UTC | 14h 15m |
| 2026-04-27 | ITY792 | FCO → HND | Apr 27, 14:00 UTC | Apr 28, 02:00 UTC | 12h 0m |
| 2026-04-27 | ITY621 | LAX → FCO | Apr 27, 00:25 UTC | Apr 27, 11:25 UTC | 11h 0m |
| 2026-04-26 | ITY620 | FCO → LAX | Apr 26, 09:50 UTC | Apr 26, 22:10 UTC | 12h 20m |
| 2026-04-25 | ITY681 | EZE → FCO | Apr 25, 16:00 UTC | Apr 26, 04:05 UTC | 12h 5m |
| 2026-04-24 | ITY680 | FCO → EZE | Apr 24, 22:00 UTC | Apr 25, 11:15 UTC | 13h 15m |
| 2026-04-24 | ITY793 | HND → FCO | Apr 24, 04:10 UTC | Apr 24, 18:15 UTC | 14h 5m |
| 2026-04-23 | ITY792 | FCO → HND | Apr 23, 13:15 UTC | Apr 24, 01:05 UTC | 11h 50m |
| 2026-04-22 | ITY621 | LAX → FCO | Apr 22, 22:35 UTC | Apr 23, 10:10 UTC | 11h 35m |
| 2026-04-22 | ITY620 | FCO → LAX | Apr 22, 07:50 UTC | Apr 22, 20:30 UTC | 12h 40m |
| 2026-04-21 | ITY793 | HND → FCO | Apr 21, 04:10 UTC | Apr 21, 18:15 UTC | 14h 5m |
| 2026-04-20 | ITY792 | FCO → HND | Apr 20, 13:20 UTC | Apr 21, 01:05 UTC | 11h 45m |
| 2026-04-19 | ITY679 | GRU → FCO | Apr 19, 22:35 UTC | Apr 20, 08:55 UTC | 10h 20m |
| 2026-04-19 | ITY678 | FCO → GRU | Apr 19, 08:40 UTC | Apr 19, 20:25 UTC | 11h 45m |
| 2026-04-15 | ITY793 | HND → FCO | Apr 15, 17:05 UTC | Apr 15, 18:20 UTC | 1h 15m |
| 2026-04-15 | ITY793 | HND → FCO | Apr 15, 15:05 UTC | Apr 15, 17:00 UTC | 1h 55m |
| 2026-04-15 | ITY793 | HND → FCO | Apr 15, 14:35 UTC | Apr 15, 14:55 UTC | 19m |
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-IFA page for operator, model, and routing details .