sensors Mode-S transponder
300A62
ICAO 24-bit transponder address · allocated to Italy
Currently assigned to I-ITYF · AIRBUS A-330-900
- Hex
- 300A62
- Octal
- 14005142
- Decimal
- 3,148,386
- Country
- IT
- Tail
- I-ITYF
- Type
- A339
- Flights observed
- 160
- Distinct callsigns
- 20
- Country
- IT
- Last broadcast
- Jul 26, 22:30 UTC
Current position
Country allocation
The ICAO 24-bit address 300A62 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 |
|---|---|---|---|
| ITY6KC | ITA Airways | 11 | 2026-07-23 |
| ITY610 | ITA Airways | 11 | 2026-07-22 |
| ITY672 | - | 8 | 2026-07-08 |
| ITY6MO | - | 7 | 2026-07-13 |
| ITY673 | - | 7 | 2026-07-09 |
| ITY630 | - | 7 | 2026-07-12 |
| ITY614 | - | 7 | 2026-07-11 |
| ITY770 | - | 6 | 2026-07-01 |
| ITY769 | - | 6 | 2026-07-01 |
| ITY675 | ITA Airways | 6 | 2026-07-24 |
| ITY674 | ITA Airways | 6 | 2026-07-23 |
| ITY615 | - | 6 | 2026-07-12 |
| ITY679 | - | 5 | 2026-07-04 |
| ITY678 | - | 5 | 2026-07-04 |
| ITY651 | - | 5 | 2026-07-02 |
| ITY650 | - | 4 | 2026-07-02 |
| ITY640 | ITA Airways | 4 | 2026-07-25 |
| ITY683 | - | 3 | 2026-07-08 |
| ITY682 | - | 3 | 2026-07-07 |
| ITY641 | ITA Airways | 3 | 2026-07-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | ITY758 | FCO → BKK | Jul 26, 14:30 UTC | Jul 26, 22:30 UTC | 8h 0m |
| 2026-07-25 | ITY641 | SFO → FCO | Jul 25, 22:45 UTC | Jul 26, 09:45 UTC | 11h 0m |
| 2026-07-25 | ITY640 | FCO → SFO | Jul 25, 07:45 UTC | Jul 25, 20:20 UTC | 12h 35m |
| 2026-07-24 | ITY675 | GRU → FCO | Jul 24, 17:25 UTC | Jul 25, 04:30 UTC | 11h 5m |
| 2026-07-23 | ITY674 | FCO → GRU | Jul 23, 21:25 UTC | Jul 24, 08:50 UTC | 11h 25m |
| 2026-07-23 | ITY6KC | JFK → FCO | Jul 23, 02:05 UTC | Jul 23, 10:10 UTC | 8h 5m |
| 2026-07-22 | ITY610 | FCO → JFK | Jul 22, 14:20 UTC | Jul 22, 23:15 UTC | 8h 55m |
| 2026-07-21 | ITY641 | SFO → FCO | Jul 21, 23:20 UTC | Jul 22, 10:25 UTC | 11h 5m |
| 2026-07-21 | ITY640 | - | Jul 21, 08:00 UTC | Jul 21, 20:40 UTC | 12h 40m |
| 2026-07-20 | ITY8011 | FCO → NAP | Jul 20, 00:10 UTC | Jul 20, 11:10 UTC | 11h 0m |
| 2026-07-16 | ITY640 | - | Jul 16, 07:50 UTC | Jul 16, 20:35 UTC | 12h 45m |
| 2026-07-14 | ITY675 | - | Jul 14, 17:35 UTC | Jul 15, 04:45 UTC | 11h 9m |
| 2026-07-13 | ITY674 | - | Jul 13, 21:00 UTC | Jul 14, 08:20 UTC | 11h 20m |
| 2026-07-13 | ITY6MO | - | Jul 13, 00:25 UTC | Jul 13, 09:40 UTC | 9h 15m |
| 2026-07-12 | ITY630 | - | Jul 12, 10:15 UTC | Jul 12, 20:20 UTC | 10h 5m |
| 2026-07-12 | ITY615 | - | Jul 12, 00:01 UTC | Jul 12, 07:25 UTC | 7h 25m |
| 2026-07-11 | ITY614 | - | Jul 11, 12:20 UTC | Jul 11, 20:45 UTC | 8h 25m |
| 2026-07-10 | ITY637 | - | Jul 10, 22:00 UTC | Jul 11, 08:15 UTC | 10h 15m |
| 2026-07-10 | ITY636 | - | Jul 10, 07:35 UTC | Jul 10, 19:15 UTC | 11h 40m |
| 2026-07-09 | ITY673 | - | Jul 9, 18:00 UTC | Jul 10, 04:30 UTC | 10h 30m |
| 2026-07-08 | ITY672 | - | Jul 8, 22:30 UTC | Jul 9, 09:35 UTC | 11h 5m |
| 2026-07-08 | ITY683 | EZE → FCO | Jul 8, 04:45 UTC | Jul 8, 17:30 UTC | 12h 45m |
| 2026-07-07 | ITY682 | - | Jul 7, 12:45 UTC | Jul 8, 02:30 UTC | 13h 45m |
| 2026-07-07 | ITY8615 | - | Jul 7, 02:10 UTC | Jul 7, 09:30 UTC | 7h 20m |
| 2026-07-06 | ITY614 | - | Jul 6, 14:45 UTC | Jul 6, 23:20 UTC | 8h 35m |
| 2026-07-06 | ITY6KC | JFK → FCO | Jul 6, 04:00 UTC | Jul 6, 11:35 UTC | 7h 35m |
| 2026-07-05 | ITY610 | - | Jul 5, 14:15 UTC | Jul 5, 23:20 UTC | 9h 5m |
| 2026-07-04 | ITY679 | - | Jul 4, 22:25 UTC | Jul 5, 09:20 UTC | 10h 55m |
| 2026-07-04 | ITY678 | - | Jul 4, 08:20 UTC | Jul 4, 19:55 UTC | 11h 35m |
| 2026-07-03 | ITY615 | BOS → FCO | Jul 3, 21:55 UTC | Jul 4, 05:10 UTC | 7h 15m |
| 2026-07-03 | ITY614 | - | Jul 3, 09:15 UTC | Jul 3, 17:50 UTC | 8h 35m |
| 2026-07-02 | ITY651 | - | Jul 2, 23:35 UTC | Jul 3, 05:50 UTC | 6h 15m |
| 2026-07-02 | ITY651 | - | Jul 2, 22:10 UTC | Jul 2, 23:30 UTC | 1h 20m |
| 2026-07-02 | ITY650 | - | Jul 2, 10:05 UTC | Jul 2, 19:25 UTC | 9h 20m |
| 2026-07-01 | ITY769 | - | Jul 1, 22:50 UTC | Jul 2, 06:51 UTC | 8h 1m |
| 2026-07-01 | ITY770 | - | Jul 1, 13:15 UTC | Jul 1, 20:30 UTC | 7h 15m |
| 2026-07-01 | ITY6KC | - | Jul 1, 02:00 UTC | Jul 1, 09:40 UTC | 7h 40m |
| 2026-06-30 | ITY610 | - | Jun 30, 14:45 UTC | Jun 30, 23:30 UTC | 8h 45m |
| 2026-06-29 | ITY679 | - | Jun 29, 22:39 UTC | Jun 30, 09:30 UTC | 10h 51m |
| 2026-06-29 | ITY678 | - | Jun 29, 08:35 UTC | Jun 29, 20:15 UTC | 11h 40m |
| 2026-06-28 | ITY619 | IAD → FCO | Jun 28, 20:59 UTC | Jun 29, 05:15 UTC | 8h 15m |
| 2026-06-28 | ITY618 | - | Jun 28, 09:05 UTC | Jun 28, 18:19 UTC | 9h 15m |
| 2026-06-27 | ITY629 | ORD → FCO | Jun 27, 20:19 UTC | Jun 28, 05:04 UTC | 8h 45m |
| 2026-06-27 | ITY628 | FCO → ORD | Jun 27, 07:55 UTC | Jun 27, 17:34 UTC | 9h 40m |
| 2026-06-26 | ITY615 | BOS → FCO | Jun 26, 21:45 UTC | Jun 27, 04:54 UTC | 7h 10m |
| 2026-06-26 | ITY614 | - | Jun 26, 09:59 UTC | Jun 26, 18:20 UTC | 8h 20m |
| 2026-06-25 | ITY675 | - | Jun 25, 17:30 UTC | Jun 26, 04:30 UTC | 11h 0m |
| 2026-06-24 | ITY674 | - | Jun 24, 20:30 UTC | Jun 25, 07:49 UTC | 11h 20m |
| 2026-06-24 | ITY683 | - | Jun 24, 04:39 UTC | Jun 24, 17:45 UTC | 13h 5m |
| 2026-06-23 | ITY682 | - | Jun 23, 12:55 UTC | Jun 24, 02:20 UTC | 13h 25m |
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-ITYF page for operator, model, and routing details .