sensors Mode-S transponder
4CAA6D
ICAO 24-bit transponder address · allocated to Ireland
Currently assigned to EI-EJO · AIRBUS A-330-200
- Hex
- 4CAA6D
- Octal
- 23125155
- Decimal
- 5,024,365
- Country
- IE
- Tail
- EI-EJO
- Type
- A332
- Flights observed
- 152
- Distinct callsigns
- 20
- Country
- IE
- Last broadcast
- 25m ago
Last known position
Country allocation
The ICAO 24-bit address 4CAA6D 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 |
|---|---|---|---|
| ITY619 | - | 21 | 2026-07-17 |
| ITY618 | - | 20 | 2026-07-17 |
| ITY615 | - | 14 | 2026-07-02 |
| ITY651 | - | 13 | 2026-06-22 |
| ITY650 | - | 13 | 2026-06-22 |
| ITY614 | - | 11 | 2026-07-02 |
| ITY608 | ITA Airways | 10 | 2026-05-22 |
| ITY609 | ITA Airways | 9 | 2026-05-22 |
| ITY603 | - | 7 | 2026-07-03 |
| ITY629 | - | 6 | 2026-07-01 |
| ITY628 | ITA Airways | 6 | 2026-07-01 |
| ITY602 | - | 6 | 2026-07-03 |
| ITY8006 | - | 4 | 2026-04-14 |
| ITY673 | - | 3 | 2026-07-15 |
| ITY672 | - | 3 | 2026-07-14 |
| RYR3864 | Ryanair | 1 | 2026-06-16 |
| ITY863 | ITA Airways | 1 | 2026-05-02 |
| ITY8012 | - | 1 | 2026-07-07 |
| ITY8009 | - | 1 | 2026-07-14 |
| ITY770 | ITA Airways | 1 | 2026-05-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | ITY619 | IAD → FCO | Jul 17, 21:00 UTC | Jul 18, 05:00 UTC | 8h 1m |
| 2026-07-17 | ITY618 | - | Jul 17, 09:20 UTC | Jul 17, 18:44 UTC | 9h 25m |
| 2026-07-16 | ITY619 | IAD → FCO | Jul 16, 20:49 UTC | Jul 17, 04:54 UTC | 8h 5m |
| 2026-07-16 | ITY618 | - | Jul 16, 09:15 UTC | Jul 16, 18:29 UTC | 9h 15m |
| 2026-07-15 | ITY673 | - | Jul 15, 17:35 UTC | Jul 16, 04:25 UTC | 10h 50m |
| 2026-07-14 | ITY672 | - | Jul 14, 21:30 UTC | Jul 15, 08:40 UTC | 11h 9m |
| 2026-07-14 | ITY8009 | - | Jul 14, 18:15 UTC | Jul 14, 19:00 UTC | 45m |
| 2026-07-07 | ITY8012 | - | Jul 7, 17:30 UTC | Jul 7, 17:50 UTC | 20m |
| 2026-07-07 | ITY619 | IAD → FCO | Jul 7, 06:25 UTC | Jul 7, 15:20 UTC | 8h 55m |
| 2026-07-06 | ITY618 | - | Jul 6, 16:25 UTC | Jul 7, 02:35 UTC | 10h 10m |
| 2026-07-06 | ITY619 | - | Jul 6, 04:10 UTC | Jul 6, 13:05 UTC | 8h 55m |
| 2026-07-05 | ITY618 | FCO → IAD | Jul 5, 13:50 UTC | Jul 5, 23:45 UTC | 9h 55m |
| 2026-07-05 | ITY619 | IAD → FCO | Jul 5, 02:15 UTC | Jul 5, 11:00 UTC | 8h 45m |
| 2026-07-04 | ITY618 | - | Jul 4, 09:20 UTC | Jul 4, 19:15 UTC | 9h 55m |
| 2026-07-03 | ITY603 | JFK → FCO | Jul 3, 21:40 UTC | Jul 4, 05:55 UTC | 8h 15m |
| 2026-07-03 | ITY602 | - | Jul 3, 09:05 UTC | Jul 3, 18:35 UTC | 9h 30m |
| 2026-07-02 | ITY615 | BOS → FCO | Jul 2, 21:50 UTC | Jul 3, 05:45 UTC | 7h 55m |
| 2026-07-02 | ITY614 | - | Jul 2, 10:00 UTC | Jul 2, 19:05 UTC | 9h 5m |
| 2026-07-01 | ITY629 | - | Jul 1, 21:50 UTC | Jul 2, 06:41 UTC | 8h 51m |
| 2026-07-01 | ITY628 | FCO → ORD | Jul 1, 08:25 UTC | Jul 1, 18:45 UTC | 10h 20m |
| 2026-06-30 | ITY673 | GIG → FCO | Jun 30, 17:45 UTC | Jul 1, 04:15 UTC | 10h 30m |
| 2026-06-29 | ITY672 | - | Jun 29, 22:44 UTC | Jun 30, 10:10 UTC | 11h 25m |
| 2026-06-24 | ITY615 | BOS → FCO | Jun 24, 21:24 UTC | Jun 25, 04:49 UTC | 7h 25m |
| 2026-06-24 | ITY614 | - | Jun 24, 08:55 UTC | Jun 24, 17:34 UTC | 8h 40m |
| 2026-06-23 | ITY615 | BOS → FCO | Jun 23, 21:29 UTC | Jun 24, 04:59 UTC | 7h 30m |
| 2026-06-23 | ITY614 | - | Jun 23, 08:59 UTC | Jun 23, 17:30 UTC | 8h 30m |
| 2026-06-22 | ITY651 | - | Jun 22, 21:19 UTC | Jun 23, 05:20 UTC | 8h 0m |
| 2026-06-22 | ITY650 | - | Jun 22, 16:29 UTC | Jun 22, 17:55 UTC | 1h 25m |
| 2026-06-22 | ITY650 | - | Jun 22, 08:54 UTC | Jun 22, 16:24 UTC | 7h 30m |
| 2026-06-21 | ITY651 | YYZ → FCO | Jun 21, 21:44 UTC | Jun 22, 05:49 UTC | 8h 5m |
| 2026-06-21 | ITY650 | - | Jun 21, 08:54 UTC | Jun 21, 17:45 UTC | 8h 50m |
| 2026-06-20 | ITY603 | JFK → FCO | Jun 20, 22:05 UTC | Jun 21, 05:35 UTC | 7h 30m |
| 2026-06-20 | ITY602 | - | Jun 20, 08:05 UTC | Jun 20, 16:59 UTC | 8h 55m |
| 2026-06-19 | ITY629 | ORD → FCO | Jun 19, 20:14 UTC | Jun 20, 04:54 UTC | 8h 40m |
| 2026-06-19 | ITY628 | FCO → ORD | Jun 19, 08:34 UTC | Jun 19, 18:09 UTC | 9h 35m |
| 2026-06-18 | ITY651 | YYZ → FCO | Jun 18, 21:30 UTC | Jun 19, 05:40 UTC | 8h 9m |
| 2026-06-18 | ITY650 | - | Jun 18, 10:20 UTC | Jun 18, 19:20 UTC | 9h 0m |
| 2026-06-17 | ITY615 | BOS → FCO | Jun 17, 21:20 UTC | Jun 18, 04:40 UTC | 7h 20m |
| 2026-06-17 | ITY614 | - | Jun 17, 09:15 UTC | Jun 17, 17:40 UTC | 8h 25m |
| 2026-06-16 | ITY619 | IAD → FCO | Jun 16, 21:05 UTC | Jun 17, 04:55 UTC | 7h 50m |
| 2026-06-16 | ITY618 | FCO → IAD | Jun 16, 09:00 UTC | Jun 16, 18:25 UTC | 9h 25m |
| 2026-06-16 | RYR3864 | CUF → FCO | Jun 16, 06:54 UTC | Jun 16, 07:15 UTC | 20m |
| 2026-06-15 | ITY619 | IAD → FCO | Jun 15, 21:55 UTC | Jun 16, 05:45 UTC | 7h 50m |
| 2026-06-15 | ITY618 | FCO → IAD | Jun 15, 08:45 UTC | Jun 15, 18:15 UTC | 9h 30m |
| 2026-06-14 | ITY651 | YYZ → FCO | Jun 14, 21:25 UTC | Jun 15, 05:20 UTC | 7h 55m |
| 2026-06-14 | ITY650 | FCO → YYZ | Jun 14, 09:55 UTC | Jun 14, 18:35 UTC | 8h 40m |
| 2026-06-13 | ITY619 | IAD → FCO | Jun 13, 20:50 UTC | Jun 14, 05:00 UTC | 8h 10m |
| 2026-06-13 | ITY618 | FCO → IAD | Jun 13, 08:55 UTC | Jun 13, 18:20 UTC | 9h 25m |
| 2026-06-12 | ITY629 | ORD → FCO | Jun 12, 21:10 UTC | Jun 13, 05:50 UTC | 8h 39m |
| 2026-06-12 | ITY628 | FCO → ORD | Jun 12, 08:45 UTC | Jun 12, 18:35 UTC | 9h 50m |
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-EJO page for operator, model, and routing details .