sensors Mode-S transponder
4CADFA
ICAO 24-bit transponder address · allocated to Ireland
Currently assigned to EI-HPA · AIRBUS A-330-900
- Hex
- 4CADFA
- Octal
- 23126772
- Decimal
- 5,025,274
- Country
- IE
- Tail
- EI-HPA
- Type
- A339
- Flights observed
- 90
- Distinct callsigns
- 20
- Country
- IE
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address 4CADFA 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ITY608 | ITA Airways | 9 | 2026-05-07 |
| ITY673 | ITA Airways | 8 | 2026-05-24 |
| ITY609 | ITA Airways | 7 | 2026-05-25 |
| ITY682 | ITA Airways | 6 | 2026-04-15 |
| ITY672 | ITA Airways | 6 | 2026-05-23 |
| ITY683 | ITA Airways | 5 | 2026-04-15 |
| ITY6MO | ITA Airways | 4 | 2026-05-27 |
| ITY630 | ITA Airways | 4 | 2026-05-26 |
| ITY770 | ITA Airways | 3 | 2026-05-27 |
| ITY769 | ITA Airways | 3 | 2026-05-27 |
| ITY675 | ITA Airways | 3 | 2026-05-11 |
| ITY674 | ITA Airways | 3 | 2026-05-10 |
| ITY602 | ITA Airways | 3 | 2026-05-25 |
| ITY651 | ITA Airways | 2 | 2026-05-28 |
| ITY650 | ITA Airways | 2 | 2026-05-28 |
| ITY637 | ITA Airways | 2 | 2026-05-29 |
| ITY636 | ITA Airways | 2 | 2026-05-29 |
| ITY629 | ITA Airways | 2 | 2026-05-21 |
| ITY628 | ITA Airways | 2 | 2026-05-21 |
| ITY615 | ITA Airways | 2 | 2026-05-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | ITY637 | IAH → FCO | May 29, 23:35 UTC | May 30, 00:30 UTC | 55m |
| 2026-05-29 | ITY636 | FCO → IAH | May 29, 09:50 UTC | May 29, 21:15 UTC | 11h 25m |
| 2026-05-28 | ITY651 | YYZ → FCO | May 28, 22:50 UTC | May 29, 07:15 UTC | 8h 25m |
| 2026-05-28 | ITY650 | FCO → YYZ | May 28, 09:15 UTC | May 28, 18:00 UTC | 8h 45m |
| 2026-05-27 | ITY769 | DEL → FCO | May 27, 22:25 UTC | May 28, 06:35 UTC | 8h 10m |
| 2026-05-27 | ITY770 | FCO → DEL | May 27, 12:20 UTC | May 27, 19:40 UTC | 7h 20m |
| 2026-05-27 | ITY6MO | MIA → FCO | May 27, 00:00 UTC | May 27, 09:15 UTC | 9h 15m |
| 2026-05-26 | ITY630 | FCO → MIA | May 26, 08:59 UTC | May 26, 19:15 UTC | 10h 15m |
| 2026-05-25 | ITY609 | JFK → FCO | May 25, 20:30 UTC | May 26, 04:35 UTC | 8h 5m |
| 2026-05-25 | ITY602 | FCO → JFK | May 25, 07:55 UTC | May 25, 16:30 UTC | 8h 35m |
| 2026-05-24 | ITY673 | GIG → FCO | May 24, 17:40 UTC | May 25, 04:20 UTC | 10h 40m |
| 2026-05-23 | ITY672 | FCO → GIG | May 23, 20:45 UTC | May 24, 07:45 UTC | 11h 0m |
| 2026-05-22 | ITY637 | IAH → FCO | May 22, 23:30 UTC | May 23, 09:30 UTC | 9h 59m |
| 2026-05-22 | ITY636 | FCO → IAH | May 22, 08:55 UTC | May 22, 20:20 UTC | 11h 25m |
| 2026-05-21 | ITY629 | ORD → FCO | May 21, 20:45 UTC | May 22, 05:10 UTC | 8h 25m |
| 2026-05-21 | ITY628 | FCO → ORD | May 21, 07:55 UTC | May 21, 17:50 UTC | 9h 55m |
| 2026-05-20 | ITY673 | GIG → FCO | May 20, 17:40 UTC | May 21, 04:20 UTC | 10h 40m |
| 2026-05-19 | ITY672 | FCO → GIG | May 19, 20:35 UTC | May 20, 07:35 UTC | 11h 1m |
| 2026-05-18 | ITY621 | LAX → FCO | May 18, 22:30 UTC | May 19, 09:35 UTC | 11h 5m |
| 2026-05-18 | ITY620 | FCO → LAX | May 18, 07:35 UTC | May 18, 20:10 UTC | 12h 34m |
| 2026-05-17 | ITY673 | GIG → FCO | May 17, 17:40 UTC | May 18, 03:45 UTC | 10h 5m |
| 2026-05-16 | ITY672 | FCO → GIG | May 16, 20:40 UTC | May 17, 08:15 UTC | 11h 35m |
| 2026-05-15 | ITY6MO | MIA → FCO | May 15, 23:50 UTC | May 16, 08:41 UTC | 8h 51m |
| 2026-05-15 | ITY630 | FCO → MIA | May 15, 09:00 UTC | May 15, 19:55 UTC | 10h 54m |
| 2026-05-14 | ITY769 | DEL → FCO | May 14, 22:15 UTC | May 15, 06:25 UTC | 8h 10m |
| 2026-05-14 | ITY770 | FCO → DEL | May 14, 12:45 UTC | May 14, 20:20 UTC | 7h 35m |
| 2026-05-13 | ITY679 | GRU → FCO | May 13, 22:55 UTC | May 14, 09:15 UTC | 10h 20m |
| 2026-05-13 | ITY678 | FCO → GRU | May 13, 08:20 UTC | May 13, 20:30 UTC | 12h 10m |
| 2026-05-11 | ITY675 | GRU → FCO | May 11, 17:50 UTC | May 12, 04:00 UTC | 10h 10m |
| 2026-05-10 | ITY674 | FCO → GRU | May 10, 20:45 UTC | May 11, 08:45 UTC | 12h 0m |
| 2026-05-07 | ITY609 | JFK → FCO | May 7, 20:25 UTC | May 8, 04:09 UTC | 7h 45m |
| 2026-05-07 | ITY608 | FCO → JFK | May 7, 08:45 UTC | May 7, 18:00 UTC | 9h 15m |
| 2026-05-06 | ITY673 | GIG → FCO | May 6, 17:40 UTC | May 7, 03:40 UTC | 10h 0m |
| 2026-05-05 | ITY672 | FCO → GIG | May 5, 20:40 UTC | May 6, 08:50 UTC | 12h 10m |
| 2026-05-04 | ITY629 | ORD → FCO | May 4, 20:25 UTC | May 5, 05:35 UTC | 9h 10m |
| 2026-05-04 | ITY628 | FCO → ORD | May 4, 08:15 UTC | May 4, 18:00 UTC | 9h 45m |
| 2026-05-03 | ITY615 | BOS → FCO | May 3, 21:20 UTC | May 4, 05:00 UTC | 7h 40m |
| 2026-05-03 | ITY614 | FCO → BOS | May 3, 08:55 UTC | May 3, 17:35 UTC | 8h 40m |
| 2026-05-02 | ITY603 | JFK → FCO | May 2, 21:55 UTC | May 3, 05:50 UTC | 7h 54m |
| 2026-05-02 | ITY602 | FCO → JFK | May 2, 08:40 UTC | May 2, 17:20 UTC | 8h 40m |
| 2026-05-01 | ITY615 | BOS → FCO | May 1, 21:40 UTC | May 2, 05:40 UTC | 8h 0m |
| 2026-05-01 | ITY614 | FCO → BOS | May 1, 10:45 UTC | May 1, 18:40 UTC | 7h 55m |
| 2026-04-30 | ITY651 | YYZ → FCO | Apr 30, 23:40 UTC | May 1, 08:05 UTC | 8h 25m |
| 2026-04-30 | ITY650 | FCO → YYZ | Apr 30, 12:30 UTC | Apr 30, 21:05 UTC | 8h 35m |
| 2026-04-29 | ITY769 | DEL → FCO | Apr 29, 22:20 UTC | Apr 30, 06:30 UTC | 8h 9m |
| 2026-04-29 | ITY770 | FCO → DEL | Apr 29, 12:30 UTC | Apr 29, 19:30 UTC | 7h 0m |
| 2026-04-28 | ITY6MO | MIA → FCO | Apr 28, 23:50 UTC | Apr 29, 09:30 UTC | 9h 41m |
| 2026-04-28 | ITY630 | FCO → MIA | Apr 28, 09:45 UTC | Apr 28, 20:25 UTC | 10h 40m |
| 2026-04-27 | ITY603 | JFK → FCO | Apr 27, 21:45 UTC | Apr 28, 05:50 UTC | 8h 5m |
| 2026-04-27 | ITY602 | FCO → JFK | Apr 27, 08:00 UTC | Apr 27, 16:30 UTC | 8h 30m |
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-HPA page for operator, model, and routing details .