sensors Mode-S transponder
4CADCA
ICAO 24-bit transponder address · allocated to Ireland
Currently assigned to EI-HJS · AIRBUS A-330-900
- Hex
- 4CADCA
- Octal
- 23126712
- Decimal
- 5,025,226
- Country
- IE
- Tail
- EI-HJS
- Type
- A339
- Flights observed
- 56
- Distinct callsigns
- 16
- Country
- IE
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 4CADCA 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 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ITY6KC | ITA Airways | 15 | 2026-04-18 |
| ITY610 | ITA Airways | 13 | 2026-04-17 |
| ITY651 | ITA Airways | 5 | 2026-04-25 |
| ITY630 | ITA Airways | 4 | 2026-04-13 |
| ITY678 | ITA Airways | 3 | 2026-04-26 |
| ITY770 | ITA Airways | 2 | 2026-04-18 |
| ITY6MO | ITA Airways | 2 | 2026-04-14 |
| ITY679 | ITA Airways | 2 | 2026-04-26 |
| ITY674 | ITA Airways | 2 | 2026-05-29 |
| ITY650 | ITA Airways | 2 | 2026-04-25 |
| ITY8007 | ITA Airways | 1 | 2026-05-28 |
| ITY8006 | - | 1 | 2026-04-27 |
| ITY769 | ITA Airways | 1 | 2026-04-18 |
| ITY675 | ITA Airways | 1 | 2026-04-24 |
| ITY621 | ITA Airways | 1 | 2026-04-20 |
| ITY620 | ITA Airways | 1 | 2026-04-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | ITY674 | FCO → GRU | May 29, 20:35 UTC | May 30, 00:00 UTC | 3h 25m |
| 2026-05-28 | ITY8007 | CAG → FCO | May 28, 17:00 UTC | May 28, 17:35 UTC | 35m |
| 2026-04-27 | ITY8006 | - | Apr 27, 11:55 UTC | Apr 27, 12:20 UTC | 25m |
| 2026-04-26 | ITY679 | GRU → FCO | Apr 26, 22:15 UTC | Apr 27, 09:05 UTC | 10h 50m |
| 2026-04-26 | ITY678 | FCO → GRU | Apr 26, 19:10 UTC | Apr 26, 19:30 UTC | 20m |
| 2026-04-26 | ITY678 | FCO → GRU | Apr 26, 08:10 UTC | Apr 26, 11:30 UTC | 3h 20m |
| 2026-04-25 | ITY651 | YYZ → FCO | Apr 25, 21:10 UTC | Apr 26, 05:30 UTC | 8h 20m |
| 2026-04-25 | ITY650 | FCO → YYZ | Apr 25, 08:50 UTC | Apr 25, 17:30 UTC | 8h 40m |
| 2026-04-24 | ITY675 | GRU → FCO | Apr 24, 17:55 UTC | Apr 25, 04:55 UTC | 11h 0m |
| 2026-04-23 | ITY674 | FCO → GRU | Apr 23, 20:35 UTC | Apr 24, 08:10 UTC | 11h 35m |
| 2026-04-22 | ITY679 | GRU → FCO | Apr 22, 22:25 UTC | Apr 23, 09:01 UTC | 10h 36m |
| 2026-04-22 | ITY678 | FCO → GRU | Apr 22, 08:15 UTC | Apr 22, 20:00 UTC | 11h 45m |
| 2026-04-20 | ITY621 | LAX → FCO | Apr 20, 00:40 UTC | Apr 20, 12:25 UTC | 11h 45m |
| 2026-04-19 | ITY620 | FCO → LAX | Apr 19, 09:20 UTC | Apr 19, 22:20 UTC | 13h 0m |
| 2026-04-18 | ITY769 | DEL → FCO | Apr 18, 22:25 UTC | Apr 19, 06:25 UTC | 8h 0m |
| 2026-04-18 | ITY770 | FCO → DEL | Apr 18, 19:35 UTC | Apr 18, 19:55 UTC | 20m |
| 2026-04-18 | ITY770 | FCO → DEL | Apr 18, 12:30 UTC | Apr 18, 16:05 UTC | 3h 35m |
| 2026-04-18 | ITY6KC | JFK → FCO | Apr 18, 07:25 UTC | Apr 18, 09:20 UTC | 1h 55m |
| 2026-04-18 | ITY6KC | JFK → FCO | Apr 18, 03:25 UTC | Apr 18, 03:55 UTC | 30m |
| 2026-04-18 | ITY6KC | JFK → FCO | Apr 18, 02:10 UTC | Apr 18, 09:50 UTC | 7h 40m |
| 2026-04-17 | ITY610 | FCO → JFK | Apr 17, 21:55 UTC | Apr 17, 22:55 UTC | 1h 0m |
| 2026-04-17 | ITY610 | FCO → JFK | Apr 17, 15:20 UTC | Apr 17, 16:15 UTC | 55m |
| 2026-04-17 | ITY610 | FCO → JFK | Apr 17, 13:35 UTC | Apr 17, 15:15 UTC | 1h 39m |
| 2026-04-17 | ITY6KC | JFK → FCO | Apr 17, 09:20 UTC | Apr 17, 09:40 UTC | 20m |
| 2026-04-17 | ITY6KC | JFK → FCO | Apr 17, 07:20 UTC | Apr 17, 09:15 UTC | 1h 55m |
| 2026-04-17 | ITY6KC | JFK → FCO | Apr 17, 03:20 UTC | Apr 17, 03:35 UTC | 15m |
| 2026-04-17 | ITY6KC | JFK → FCO | Apr 17, 01:55 UTC | Apr 17, 03:15 UTC | 1h 20m |
| 2026-04-16 | ITY610 | FCO → JFK | Apr 16, 21:14 UTC | Apr 16, 23:00 UTC | 1h 45m |
| 2026-04-16 | ITY610 | FCO → JFK | Apr 16, 20:45 UTC | Apr 16, 21:10 UTC | 25m |
| 2026-04-16 | ITY610 | FCO → JFK | Apr 16, 15:15 UTC | Apr 16, 16:45 UTC | 1h 30m |
| 2026-04-16 | ITY610 | FCO → JFK | Apr 16, 13:50 UTC | Apr 16, 15:10 UTC | 1h 20m |
| 2026-04-16 | ITY6KC | JFK → FCO | Apr 16, 09:10 UTC | Apr 16, 09:45 UTC | 35m |
| 2026-04-16 | ITY6KC | JFK → FCO | Apr 16, 07:09 UTC | Apr 16, 09:05 UTC | 1h 55m |
| 2026-04-16 | ITY6KC | JFK → FCO | Apr 16, 03:09 UTC | Apr 16, 03:39 UTC | 30m |
| 2026-04-16 | ITY6KC | JFK → FCO | Apr 16, 01:55 UTC | Apr 16, 03:04 UTC | 1h 10m |
| 2026-04-15 | ITY610 | FCO → JFK | Apr 15, 21:05 UTC | Apr 15, 22:50 UTC | 1h 45m |
| 2026-04-15 | ITY610 | FCO → JFK | Apr 15, 15:05 UTC | Apr 15, 16:55 UTC | 1h 50m |
| 2026-04-15 | ITY610 | FCO → JFK | Apr 15, 13:40 UTC | Apr 15, 14:55 UTC | 1h 14m |
| 2026-04-15 | ITY6KC | JFK → FCO | Apr 15, 09:00 UTC | Apr 15, 09:55 UTC | 55m |
| 2026-04-15 | ITY6KC | JFK → FCO | Apr 15, 07:40 UTC | Apr 15, 08:55 UTC | 1h 15m |
| 2026-04-15 | ITY6KC | JFK → FCO | Apr 15, 02:55 UTC | Apr 15, 04:00 UTC | 1h 5m |
| 2026-04-15 | ITY6KC | JFK → FCO | Apr 15, 02:15 UTC | Apr 15, 02:50 UTC | 35m |
| 2026-04-14 | ITY610 | FCO → JFK | Apr 14, 20:55 UTC | Apr 14, 22:45 UTC | 1h 50m |
| 2026-04-14 | ITY610 | FCO → JFK | Apr 14, 14:50 UTC | Apr 14, 16:45 UTC | 1h 55m |
| 2026-04-14 | ITY610 | FCO → JFK | Apr 14, 13:45 UTC | Apr 14, 14:45 UTC | 1h 0m |
| 2026-04-14 | ITY6MO | MIA → FCO | Apr 14, 09:10 UTC | Apr 14, 09:35 UTC | 25m |
| 2026-04-14 | ITY6MO | MIA → FCO | Apr 14, 07:30 UTC | Apr 14, 09:05 UTC | 1h 35m |
| 2026-04-13 | ITY630 | FCO → MIA | Apr 13, 19:50 UTC | Apr 13, 20:25 UTC | 35m |
| 2026-04-13 | ITY630 | FCO → MIA | Apr 13, 19:35 UTC | Apr 13, 19:45 UTC | 10m |
| 2026-04-13 | ITY630 | FCO → MIA | Apr 13, 11:55 UTC | Apr 13, 12:25 UTC | 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-HJS page for operator, model, and routing details .