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
- 155
- Distinct callsigns
- 20
- Country
- IE
- Last broadcast
- Jul 26, 22:30 UTC
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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ITY6KC | ITA Airways | 16 | 2026-06-08 |
| ITY610 | ITA Airways | 14 | 2026-06-07 |
| ITY630 | - | 8 | 2026-07-16 |
| ITY770 | - | 7 | 2026-07-11 |
| ITY678 | ITA Airways | 7 | 2026-07-22 |
| ITY651 | - | 7 | 2026-07-15 |
| ITY769 | - | 6 | 2026-07-11 |
| ITY6MO | - | 6 | 2026-07-16 |
| ITY679 | ITA Airways | 6 | 2026-07-22 |
| ITY675 | - | 6 | 2026-07-19 |
| ITY674 | ITA Airways | 6 | 2026-07-18 |
| ITY603 | ITA Airways | 6 | 2026-07-26 |
| ITY602 | ITA Airways | 6 | 2026-07-26 |
| ITY615 | ITA Airways | 5 | 2026-07-21 |
| ITY614 | ITA Airways | 5 | 2026-07-21 |
| ITY673 | ITA Airways | 4 | 2026-07-24 |
| ITY672 | ITA Airways | 4 | 2026-07-23 |
| ITY650 | - | 4 | 2026-07-15 |
| ITY629 | ITA Airways | 4 | 2026-07-25 |
| ITY628 | ITA Airways | 4 | 2026-07-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | ITY603 | JFK → FCO | Jul 26, 22:10 UTC | Jul 26, 22:30 UTC | 20m |
| 2026-07-26 | ITY602 | FCO → JFK | Jul 26, 08:25 UTC | Jul 26, 17:05 UTC | 8h 40m |
| 2026-07-25 | ITY629 | ORD → FCO | Jul 25, 20:50 UTC | Jul 26, 05:20 UTC | 8h 30m |
| 2026-07-25 | ITY628 | FCO → ORD | Jul 25, 08:30 UTC | Jul 25, 18:10 UTC | 9h 40m |
| 2026-07-24 | ITY673 | GIG → FCO | Jul 24, 18:10 UTC | Jul 25, 04:50 UTC | 10h 40m |
| 2026-07-23 | ITY672 | FCO → GIG | Jul 23, 21:55 UTC | Jul 24, 08:50 UTC | 10h 55m |
| 2026-07-22 | ITY679 | GRU → FCO | Jul 22, 23:35 UTC | Jul 23, 10:40 UTC | 11h 5m |
| 2026-07-22 | ITY678 | FCO → GRU | Jul 22, 11:10 UTC | Jul 22, 21:20 UTC | 10h 10m |
| 2026-07-21 | ITY615 | BOS → FCO | Jul 21, 21:30 UTC | Jul 22, 05:10 UTC | 7h 40m |
| 2026-07-21 | ITY614 | FCO → BOS | Jul 21, 09:05 UTC | Jul 21, 17:30 UTC | 8h 25m |
| 2026-07-20 | ITY603 | JFK → FCO | Jul 20, 22:30 UTC | Jul 21, 06:10 UTC | 7h 40m |
| 2026-07-20 | ITY602 | - | Jul 20, 09:20 UTC | Jul 20, 18:05 UTC | 8h 45m |
| 2026-07-19 | ITY675 | - | Jul 19, 17:30 UTC | Jul 20, 04:10 UTC | 10h 40m |
| 2026-07-18 | ITY674 | FCO → GRU | Jul 18, 22:05 UTC | Jul 19, 09:35 UTC | 11h 30m |
| 2026-07-18 | ITY683 | EZE → FCO | Jul 18, 04:40 UTC | Jul 18, 17:25 UTC | 12h 45m |
| 2026-07-17 | ITY682 | - | Jul 17, 12:40 UTC | Jul 18, 02:05 UTC | 13h 25m |
| 2026-07-16 | ITY6MO | - | Jul 16, 23:59 UTC | Jul 17, 09:25 UTC | 9h 25m |
| 2026-07-16 | ITY630 | - | Jul 16, 09:45 UTC | Jul 16, 20:05 UTC | 10h 20m |
| 2026-07-15 | ITY651 | - | Jul 15, 22:20 UTC | Jul 16, 06:10 UTC | 7h 50m |
| 2026-07-15 | ITY650 | - | Jul 15, 10:20 UTC | Jul 15, 19:25 UTC | 9h 5m |
| 2026-07-14 | ITY615 | - | Jul 14, 21:55 UTC | Jul 15, 05:30 UTC | 7h 34m |
| 2026-07-14 | ITY614 | - | Jul 14, 10:05 UTC | Jul 14, 18:15 UTC | 8h 10m |
| 2026-07-13 | ITY629 | ORD → FCO | Jul 13, 22:25 UTC | Jul 14, 07:30 UTC | 9h 5m |
| 2026-07-13 | ITY628 | - | Jul 13, 10:05 UTC | Jul 13, 19:40 UTC | 9h 35m |
| 2026-07-12 | ITY609 | - | Jul 12, 21:50 UTC | Jul 13, 05:45 UTC | 7h 55m |
| 2026-07-12 | ITY608 | - | Jul 12, 09:45 UTC | Jul 12, 18:20 UTC | 8h 35m |
| 2026-07-11 | ITY769 | DEL → FCO | Jul 11, 22:15 UTC | Jul 12, 06:40 UTC | 8h 25m |
| 2026-07-11 | ITY770 | - | Jul 11, 12:40 UTC | Jul 11, 19:40 UTC | 7h 0m |
| 2026-07-10 | ITY679 | - | Jul 10, 23:00 UTC | Jul 11, 09:35 UTC | 10h 35m |
| 2026-07-10 | ITY678 | - | Jul 10, 09:05 UTC | Jul 10, 20:25 UTC | 11h 20m |
| 2026-07-09 | ITY629 | ORD → FCO | Jul 9, 21:45 UTC | Jul 10, 06:25 UTC | 8h 40m |
| 2026-07-09 | ITY628 | - | Jul 9, 09:00 UTC | Jul 9, 18:55 UTC | 9h 55m |
| 2026-07-08 | ITY675 | - | Jul 8, 17:50 UTC | Jul 9, 04:45 UTC | 10h 55m |
| 2026-07-07 | ITY674 | - | Jul 7, 20:35 UTC | Jul 8, 08:10 UTC | 11h 35m |
| 2026-07-06 | ITY641 | - | Jul 6, 22:45 UTC | Jul 7, 10:00 UTC | 11h 15m |
| 2026-07-06 | ITY640 | - | Jul 6, 07:40 UTC | Jul 6, 20:15 UTC | 12h 35m |
| 2026-07-05 | ITY675 | - | Jul 5, 17:25 UTC | Jul 6, 04:15 UTC | 10h 50m |
| 2026-07-04 | ITY674 | - | Jul 4, 20:35 UTC | Jul 5, 08:00 UTC | 11h 25m |
| 2026-07-04 | ITY683 | - | Jul 4, 04:50 UTC | Jul 4, 17:20 UTC | 12h 30m |
| 2026-07-03 | ITY682 | - | Jul 3, 13:00 UTC | Jul 4, 02:45 UTC | 13h 45m |
| 2026-07-02 | ITY679 | - | Jul 2, 22:25 UTC | Jul 3, 09:20 UTC | 10h 55m |
| 2026-07-02 | ITY678 | - | Jul 2, 08:50 UTC | Jul 2, 20:05 UTC | 11h 15m |
| 2026-07-01 | ITY673 | GIG → FCO | Jul 1, 17:55 UTC | Jul 2, 04:35 UTC | 10h 40m |
| 2026-06-30 | ITY672 | - | Jun 30, 21:00 UTC | Jul 1, 08:10 UTC | 11h 10m |
| 2026-06-29 | ITY673 | GIG → FCO | Jun 29, 17:40 UTC | Jun 30, 04:05 UTC | 10h 25m |
| 2026-06-28 | ITY672 | - | Jun 28, 20:50 UTC | Jun 29, 07:59 UTC | 11h 10m |
| 2026-06-28 | ITY6MO | - | Jun 28, 00:25 UTC | Jun 28, 09:39 UTC | 9h 15m |
| 2026-06-27 | ITY630 | FCO → MIA | Jun 27, 09:15 UTC | Jun 27, 19:34 UTC | 10h 20m |
| 2026-06-26 | ITY6MO | - | Jun 26, 20:44 UTC | Jun 27, 06:09 UTC | 9h 25m |
| 2026-06-26 | ITY630 | FCO → MIA | Jun 26, 07:55 UTC | Jun 26, 18:29 UTC | 10h 35m |
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 .