sensors Mode-S transponder
4CAD49
ICAO 24-bit transponder address · allocated to Ireland
Currently assigned to EI-IFF · AIRBUS A-350-900
- Hex
- 4CAD49
- Octal
- 23126511
- Decimal
- 5,025,097
- Country
- IE
- Tail
- EI-IFF
- Type
- A359
- Flights observed
- 151
- Distinct callsigns
- 19
- Country
- IE
- Last broadcast
- 38m ago
Last known position
Country allocation
The ICAO 24-bit address 4CAD49 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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ITY792 | - | 25 | 2026-07-14 |
| ITY793 | - | 23 | 2026-07-11 |
| ITY621 | - | 22 | 2026-07-13 |
| ITY620 | - | 22 | 2026-07-13 |
| ITY681 | - | 21 | 2026-07-13 |
| ITY680 | - | 21 | 2026-07-11 |
| ITY683 | ITA Airways | 3 | 2026-05-23 |
| ITY682 | ITA Airways | 2 | 2026-05-22 |
| ITY673 | ITA Airways | 2 | 2026-04-13 |
| ITY6KC | - | 1 | 2026-06-16 |
| ITY675 | - | 1 | 2026-06-20 |
| ITY674 | - | 1 | 2026-06-19 |
| ITY641 | - | 1 | 2026-06-14 |
| ITY640 | ITA Airways | 1 | 2026-06-14 |
| ITY610 | ITA Airways | 1 | 2026-06-15 |
| ITY609 | ITA Airways | 1 | 2026-04-28 |
| ITY608 | ITA Airways | 1 | 2026-04-28 |
| ITY603 | - | 1 | 2026-06-21 |
| ITY602 | - | 1 | 2026-06-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | ITY792 | - | Jul 14, 13:30 UTC | Jul 14, 22:15 UTC | 8h 45m |
| 2026-07-13 | ITY621 | - | Jul 13, 22:20 UTC | Jul 14, 09:30 UTC | 11h 10m |
| 2026-07-13 | ITY620 | - | Jul 13, 08:05 UTC | Jul 13, 20:15 UTC | 12h 10m |
| 2026-07-13 | ITY681 | - | Jul 13, 02:40 UTC | Jul 13, 04:10 UTC | 1h 30m |
| 2026-07-12 | ITY681 | - | Jul 12, 15:50 UTC | Jul 12, 23:45 UTC | 7h 55m |
| 2026-07-11 | ITY680 | - | Jul 11, 21:35 UTC | Jul 12, 11:05 UTC | 13h 30m |
| 2026-07-11 | ITY793 | - | Jul 11, 03:50 UTC | Jul 11, 17:20 UTC | 13h 30m |
| 2026-07-10 | ITY792 | - | Jul 10, 13:30 UTC | Jul 11, 01:05 UTC | 11h 35m |
| 2026-07-09 | ITY621 | - | Jul 9, 22:25 UTC | Jul 10, 09:40 UTC | 11h 15m |
| 2026-07-09 | ITY620 | - | Jul 9, 08:00 UTC | Jul 9, 20:00 UTC | 12h 0m |
| 2026-07-08 | ITY681 | EZE → FCO | Jul 8, 16:00 UTC | Jul 9, 04:25 UTC | 12h 25m |
| 2026-07-07 | ITY680 | - | Jul 7, 20:50 UTC | Jul 8, 10:05 UTC | 13h 15m |
| 2026-07-07 | ITY793 | HND → FCO | Jul 7, 04:15 UTC | Jul 7, 18:00 UTC | 13h 45m |
| 2026-07-06 | ITY792 | - | Jul 6, 13:25 UTC | Jul 7, 00:55 UTC | 11h 30m |
| 2026-07-05 | ITY621 | - | Jul 5, 22:45 UTC | Jul 6, 09:50 UTC | 11h 5m |
| 2026-07-05 | ITY620 | - | Jul 5, 08:15 UTC | Jul 5, 20:35 UTC | 12h 20m |
| 2026-07-04 | ITY681 | EZE → FCO | Jul 4, 15:45 UTC | Jul 5, 03:50 UTC | 12h 5m |
| 2026-07-03 | ITY680 | - | Jul 3, 21:25 UTC | Jul 4, 11:00 UTC | 13h 35m |
| 2026-07-03 | ITY793 | HND → FCO | Jul 3, 03:55 UTC | Jul 3, 17:30 UTC | 13h 35m |
| 2026-07-02 | ITY792 | - | Jul 2, 13:55 UTC | Jul 3, 01:40 UTC | 11h 45m |
| 2026-07-01 | ITY621 | - | Jul 1, 22:40 UTC | Jul 2, 09:45 UTC | 11h 5m |
| 2026-07-01 | ITY620 | - | Jul 1, 07:55 UTC | Jul 1, 19:50 UTC | 11h 55m |
| 2026-06-30 | ITY681 | - | Jun 30, 15:55 UTC | Jul 1, 04:10 UTC | 12h 15m |
| 2026-06-29 | ITY680 | - | Jun 29, 20:59 UTC | Jun 30, 10:25 UTC | 13h 26m |
| 2026-06-29 | ITY793 | HND → FCO | Jun 29, 03:54 UTC | Jun 29, 17:40 UTC | 13h 45m |
| 2026-06-28 | ITY792 | - | Jun 28, 13:55 UTC | Jun 28, 16:00 UTC | 2h 5m |
| 2026-06-27 | ITY621 | - | Jun 27, 22:29 UTC | Jun 28, 09:50 UTC | 11h 20m |
| 2026-06-27 | ITY620 | - | Jun 27, 08:10 UTC | Jun 27, 20:14 UTC | 12h 5m |
| 2026-06-26 | ITY793 | HND → FCO | Jun 26, 04:10 UTC | Jun 26, 17:59 UTC | 13h 50m |
| 2026-06-25 | ITY792 | - | Jun 25, 13:45 UTC | Jun 26, 01:34 UTC | 11h 50m |
| 2026-06-24 | ITY681 | - | Jun 24, 16:05 UTC | Jun 25, 04:35 UTC | 12h 30m |
| 2026-06-23 | ITY680 | - | Jun 23, 21:05 UTC | Jun 24, 09:59 UTC | 12h 55m |
| 2026-06-22 | ITY621 | - | Jun 22, 22:49 UTC | Jun 23, 10:10 UTC | 11h 20m |
| 2026-06-22 | ITY620 | - | Jun 22, 08:25 UTC | Jun 22, 20:30 UTC | 12h 5m |
| 2026-06-21 | ITY603 | JFK → FCO | Jun 21, 22:15 UTC | Jun 22, 05:44 UTC | 7h 30m |
| 2026-06-21 | ITY602 | - | Jun 21, 08:30 UTC | Jun 21, 16:59 UTC | 8h 30m |
| 2026-06-20 | ITY675 | - | Jun 20, 18:14 UTC | Jun 21, 05:10 UTC | 10h 55m |
| 2026-06-19 | ITY674 | - | Jun 19, 20:29 UTC | Jun 20, 07:29 UTC | 11h 0m |
| 2026-06-17 | ITY793 | HND → FCO | Jun 17, 04:00 UTC | Jun 17, 17:35 UTC | 13h 35m |
| 2026-06-16 | ITY792 | - | Jun 16, 13:44 UTC | Jun 17, 01:40 UTC | 11h 56m |
| 2026-06-16 | ITY6KC | - | Jun 16, 02:24 UTC | Jun 16, 09:45 UTC | 7h 20m |
| 2026-06-15 | ITY610 | FCO → JFK | Jun 15, 14:15 UTC | Jun 15, 23:04 UTC | 8h 50m |
| 2026-06-14 | ITY641 | SFO → FCO | Jun 14, 22:50 UTC | Jun 15, 10:15 UTC | 11h 25m |
| 2026-06-14 | ITY640 | FCO → SFO | Jun 14, 08:10 UTC | Jun 14, 19:55 UTC | 11h 45m |
| 2026-06-13 | ITY681 | - | Jun 13, 16:10 UTC | Jun 14, 04:40 UTC | 12h 30m |
| 2026-06-12 | ITY680 | - | Jun 12, 21:25 UTC | Jun 13, 10:35 UTC | 13h 9m |
| 2026-06-12 | ITY793 | HND → FCO | Jun 12, 04:05 UTC | Jun 12, 18:05 UTC | 14h 0m |
| 2026-06-11 | ITY792 | FCO → HND | Jun 11, 13:30 UTC | Jun 12, 01:10 UTC | 11h 41m |
| 2026-06-10 | ITY621 | LAX → FCO | Jun 10, 22:20 UTC | Jun 11, 09:15 UTC | 10h 55m |
| 2026-06-10 | ITY620 | FCO → LAX | Jun 10, 08:10 UTC | Jun 10, 20:05 UTC | 11h 55m |
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-IFF page for operator, model, and routing details .