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