sensors Mode-S transponder
300A9D
ICAO 24-bit transponder address · allocated to Italy
Currently assigned to I-ITYI · AIRBUS A-330-900
- Hex
- 300A9D
- Octal
- 14005235
- Decimal
- 3,148,445
- Country
- IT
- Tail
- I-ITYI
- Type
- A339
- Flights observed
- 89
- Distinct callsigns
- 20
- Country
- IT
- Last broadcast
- 4h ago
Current position
Country allocation
The ICAO 24-bit address 300A9D falls within the block assigned to Italy (IT) by ICAO Annex 10, Volume III. Every aircraft registered in Italy 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 |
|---|---|---|---|
| ITY650 | ITA Airways | 9 | 2026-04-28 |
| ITY651 | ITA Airways | 7 | 2026-04-28 |
| ITY769 | ITA Airways | 6 | 2026-05-04 |
| ITY675 | ITA Airways | 6 | 2026-05-29 |
| ITY770 | ITA Airways | 5 | 2026-05-04 |
| ITY679 | ITA Airways | 4 | 2026-05-19 |
| ITY678 | ITA Airways | 4 | 2026-05-19 |
| ITY674 | ITA Airways | 4 | 2026-05-28 |
| ITY609 | ITA Airways | 4 | 2026-05-26 |
| ITY608 | ITA Airways | 4 | 2026-05-26 |
| ITY673 | ITA Airways | 3 | 2026-06-02 |
| ITY672 | ITA Airways | 3 | 2026-06-01 |
| ITY641 | ITA Airways | 3 | 2026-05-30 |
| ITY640 | ITA Airways | 3 | 2026-05-30 |
| ITY759 | ITA Airways | 2 | 2026-05-01 |
| ITY758 | ITA Airways | 2 | 2026-04-30 |
| ITY6KC | ITA Airways | 2 | 2026-06-01 |
| ITY629 | ITA Airways | 2 | 2026-05-25 |
| ITY628 | ITA Airways | 2 | 2026-05-25 |
| ITY619 | ITA Airways | 2 | 2026-05-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | ITY673 | GIG → FCO | Jun 2, 17:40 UTC | Jun 2, 18:40 UTC | 1h 0m |
| 2026-06-01 | ITY672 | FCO → GIG | Jun 1, 20:30 UTC | Jun 2, 07:35 UTC | 11h 5m |
| 2026-06-01 | ITY6KC | JFK → FCO | Jun 1, 02:10 UTC | Jun 1, 09:40 UTC | 7h 30m |
| 2026-05-31 | ITY610 | FCO → JFK | May 31, 13:50 UTC | May 31, 23:05 UTC | 9h 15m |
| 2026-05-30 | ITY641 | SFO → FCO | May 30, 22:45 UTC | May 31, 10:10 UTC | 11h 25m |
| 2026-05-30 | ITY640 | FCO → SFO | May 30, 07:30 UTC | May 30, 19:40 UTC | 12h 10m |
| 2026-05-29 | ITY675 | GRU → FCO | May 29, 17:30 UTC | May 30, 04:05 UTC | 10h 35m |
| 2026-05-28 | ITY674 | FCO → GRU | May 28, 20:40 UTC | May 29, 08:20 UTC | 11h 40m |
| 2026-05-27 | ITY6MO | MIA → FCO | May 27, 23:55 UTC | May 28, 09:10 UTC | 9h 15m |
| 2026-05-27 | ITY630 | FCO → MIA | May 27, 09:05 UTC | May 27, 19:20 UTC | 10h 15m |
| 2026-05-26 | ITY609 | JFK → FCO | May 26, 20:24 UTC | May 27, 04:30 UTC | 8h 5m |
| 2026-05-26 | ITY608 | FCO → JFK | May 26, 08:34 UTC | May 26, 17:04 UTC | 8h 30m |
| 2026-05-25 | ITY629 | ORD → FCO | May 25, 20:59 UTC | May 26, 05:49 UTC | 8h 50m |
| 2026-05-25 | ITY628 | FCO → ORD | May 25, 07:45 UTC | May 25, 17:40 UTC | 9h 55m |
| 2026-05-24 | ITY609 | JFK → FCO | May 24, 20:50 UTC | May 25, 05:00 UTC | 8h 10m |
| 2026-05-24 | ITY608 | FCO → JFK | May 24, 09:00 UTC | May 24, 17:45 UTC | 8h 45m |
| 2026-05-23 | ITY629 | ORD → FCO | May 23, 20:30 UTC | May 24, 05:15 UTC | 8h 45m |
| 2026-05-23 | ITY628 | FCO → ORD | May 23, 07:45 UTC | May 23, 17:50 UTC | 10h 5m |
| 2026-05-22 | ITY673 | GIG → FCO | May 22, 17:40 UTC | May 23, 04:10 UTC | 10h 29m |
| 2026-05-21 | ITY672 | FCO → GIG | May 21, 20:45 UTC | May 22, 07:55 UTC | 11h 10m |
| 2026-05-21 | ITY6KC | JFK → FCO | May 21, 03:05 UTC | May 21, 10:55 UTC | 7h 50m |
| 2026-05-20 | ITY610 | FCO → JFK | May 20, 13:45 UTC | May 20, 22:50 UTC | 9h 5m |
| 2026-05-19 | ITY679 | GRU → FCO | May 19, 22:15 UTC | May 20, 09:10 UTC | 10h 56m |
| 2026-05-19 | ITY678 | FCO → GRU | May 19, 08:20 UTC | May 19, 20:00 UTC | 11h 40m |
| 2026-05-18 | ITY673 | GIG → FCO | May 18, 17:35 UTC | May 19, 04:20 UTC | 10h 44m |
| 2026-05-17 | ITY672 | FCO → GIG | May 17, 20:40 UTC | May 18, 08:15 UTC | 11h 35m |
| 2026-05-16 | ITY641 | SFO → FCO | May 16, 22:40 UTC | May 17, 09:50 UTC | 11h 10m |
| 2026-05-16 | ITY640 | FCO → SFO | May 16, 07:35 UTC | May 16, 19:55 UTC | 12h 20m |
| 2026-05-12 | ITY619 | IAD → FCO | May 12, 20:50 UTC | May 13, 05:10 UTC | 8h 20m |
| 2026-05-12 | ITY618 | FCO → IAD | May 12, 08:40 UTC | May 12, 18:00 UTC | 9h 20m |
| 2026-05-10 | ITY641 | SFO → FCO | May 10, 22:25 UTC | May 11, 09:40 UTC | 11h 15m |
| 2026-05-10 | ITY640 | FCO → SFO | May 10, 07:40 UTC | May 10, 20:00 UTC | 12h 20m |
| 2026-05-09 | ITY609 | JFK → FCO | May 9, 20:25 UTC | May 10, 04:19 UTC | 7h 55m |
| 2026-05-09 | ITY608 | FCO → JFK | May 9, 08:35 UTC | May 9, 17:20 UTC | 8h 45m |
| 2026-05-08 | ITY619 | IAD → FCO | May 8, 20:50 UTC | May 9, 05:15 UTC | 8h 25m |
| 2026-05-08 | ITY618 | FCO → IAD | May 8, 08:59 UTC | May 8, 18:25 UTC | 9h 25m |
| 2026-05-07 | ITY615 | BOS → FCO | May 7, 21:35 UTC | May 8, 05:00 UTC | 7h 25m |
| 2026-05-07 | ITY614 | FCO → BOS | May 7, 08:50 UTC | May 7, 17:30 UTC | 8h 40m |
| 2026-05-06 | ITY603 | JFK → FCO | May 6, 22:05 UTC | May 7, 05:50 UTC | 7h 45m |
| 2026-05-06 | ITY602 | FCO → JFK | May 6, 07:55 UTC | May 6, 16:45 UTC | 8h 50m |
| 2026-05-05 | ITY609 | JFK → FCO | May 5, 20:40 UTC | May 6, 04:30 UTC | 7h 50m |
| 2026-05-05 | ITY608 | FCO → JFK | May 5, 08:50 UTC | May 5, 17:35 UTC | 8h 45m |
| 2026-05-04 | ITY769 | DEL → FCO | May 4, 22:00 UTC | May 5, 06:00 UTC | 8h 0m |
| 2026-05-04 | ITY770 | FCO → DEL | May 4, 12:25 UTC | May 4, 19:55 UTC | 7h 31m |
| 2026-05-03 | ITY637 | IAH → FCO | May 3, 23:20 UTC | May 4, 09:40 UTC | 10h 20m |
| 2026-05-03 | ITY636 | FCO → IAH | May 3, 09:15 UTC | May 3, 20:40 UTC | 11h 25m |
| 2026-05-02 | ITY675 | GRU → FCO | May 2, 17:35 UTC | May 3, 04:05 UTC | 10h 29m |
| 2026-05-01 | ITY674 | FCO → GRU | May 1, 21:25 UTC | May 2, 09:35 UTC | 12h 11m |
| 2026-05-01 | ITY759 | BKK → FCO | May 1, 06:35 UTC | May 1, 18:05 UTC | 11h 30m |
| 2026-04-30 | ITY758 | FCO → BKK | Apr 30, 13:45 UTC | May 1, 00:05 UTC | 10h 20m |
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 I-ITYI page for operator, model, and routing details .