sensors Mode-S transponder
0D0A9A
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-ADG · BOEING 787-9 Dreamliner
- Hex
- 0D0A9A
- Octal
- 03205232
- Decimal
- 854,682
- Country
- MX
- Tail
- XA-ADG
- Type
- B789
- Flights observed
- 120
- Distinct callsigns
- 20
- Country
- MX
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 0D0A9A falls within the block assigned to Mexico (MX) by ICAO Annex 10, Volume III. Every aircraft registered in Mexico 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 |
|---|---|---|---|
| AMX015 | Aeroméxico | 23 | 2026-05-07 |
| AMX014 | Aeroméxico | 23 | 2026-05-07 |
| AMX091 | Aeroméxico | 10 | 2026-05-20 |
| AMX090 | Aeroméxico | 5 | 2026-05-19 |
| AMX058 | Aeroméxico | 4 | 2026-05-08 |
| AMX034 | Aeroméxico | 4 | 2026-05-14 |
| AMX008 | - | 4 | 2026-05-29 |
| AMX007 | - | 4 | 2026-05-29 |
| AMX971 | Aeroméxico | 3 | 2026-05-25 |
| AMX057 | Aeroméxico | 3 | 2026-05-09 |
| AMX035 | Aeroméxico | 3 | 2026-05-24 |
| AMX030 | Aeroméxico | 3 | 2026-05-10 |
| AMX029 | Aeroméxico | 3 | 2026-05-11 |
| AMX022 | Aeroméxico | 3 | 2026-05-22 |
| AMX021 | Aeroméxico | 3 | 2026-05-22 |
| AMX006 | - | 3 | 2026-05-16 |
| AMX005 | - | 3 | 2026-05-15 |
| AMX647 | Aeroméxico | 2 | 2026-05-01 |
| AMX646 | Aeroméxico | 2 | 2026-05-01 |
| AMX409 | Aeroméxico | 2 | 2026-05-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | AMX008 | - | May 29, 22:05 UTC | May 29, 23:15 UTC | 1h 10m |
| 2026-05-29 | AMX007 | - | May 29, 05:00 UTC | May 29, 14:50 UTC | 9h 50m |
| 2026-05-28 | AMX409 | JFK → MEX | May 28, 20:40 UTC | May 29, 01:05 UTC | 4h 25m |
| 2026-05-28 | AMX408 | MEX → JFK | May 28, 13:55 UTC | May 28, 18:10 UTC | 4h 15m |
| 2026-05-27 | AMX008 | - | May 27, 21:55 UTC | May 28, 08:25 UTC | 10h 30m |
| 2026-05-27 | AMX007 | - | May 27, 05:04 UTC | May 27, 14:55 UTC | 9h 50m |
| 2026-05-26 | AMX409 | JFK → MEX | May 26, 20:54 UTC | May 27, 01:34 UTC | 4h 40m |
| 2026-05-26 | AMX408 | MEX → JFK | May 26, 13:45 UTC | May 26, 17:50 UTC | 4h 5m |
| 2026-05-25 | AMX026 | AMS → MEX | May 25, 20:30 UTC | May 26, 07:55 UTC | 11h 25m |
| 2026-05-25 | AMX025 | MEX → AMS | May 25, 06:40 UTC | May 25, 17:00 UTC | 10h 20m |
| 2026-05-25 | AMX971 | MTY → MEX | May 25, 03:20 UTC | May 25, 04:30 UTC | 1h 10m |
| 2026-05-24 | AMX035 | MAD → MTY | May 24, 13:15 UTC | May 24, 23:46 UTC | 10h 31m |
| 2026-05-24 | AMX001 | MEX → MAD | May 24, 00:45 UTC | May 24, 10:50 UTC | 10h 5m |
| 2026-05-22 | AMX022 | MAD → MEX | May 22, 22:05 UTC | May 23, 08:55 UTC | 10h 49m |
| 2026-05-22 | AMX021 | MEX → MAD | May 22, 04:20 UTC | May 22, 14:20 UTC | 10h 0m |
| 2026-05-20 | AMX091 | ICN → MEX | May 20, 16:10 UTC | May 20, 16:20 UTC | 10m |
| 2026-05-20 | AMX091 | ICN → MEX | May 20, 03:10 UTC | May 20, 14:40 UTC | 11h 31m |
| 2026-05-19 | AMX090 | MTY → ICN | May 19, 07:10 UTC | May 19, 22:05 UTC | 14h 55m |
| 2026-05-19 | AMX090 | MTY → ICN | May 19, 03:25 UTC | May 19, 04:40 UTC | 1h 15m |
| 2026-05-17 | AMX026 | AMS → MEX | May 17, 20:20 UTC | May 18, 07:30 UTC | 11h 10m |
| 2026-05-17 | AMX025 | MEX → AMS | May 17, 04:50 UTC | May 17, 14:45 UTC | 9h 55m |
| 2026-05-16 | AMX006 | - | May 16, 13:15 UTC | May 17, 00:55 UTC | 11h 40m |
| 2026-05-15 | AMX005 | - | May 15, 23:20 UTC | May 16, 09:21 UTC | 10h 1m |
| 2026-05-15 | AMX002 | MAD → MEX | May 15, 09:15 UTC | May 15, 20:45 UTC | 11h 29m |
| 2026-05-14 | AMX034 | MEX → MTY | May 14, 17:05 UTC | May 15, 02:30 UTC | 9h 25m |
| 2026-05-14 | AMX034 | MEX → MTY | May 14, 13:50 UTC | May 14, 15:01 UTC | 1h 10m |
| 2026-05-13 | AMX022 | MAD → MEX | May 13, 22:05 UTC | May 14, 08:55 UTC | 10h 50m |
| 2026-05-13 | AMX021 | MEX → MAD | May 13, 04:10 UTC | May 13, 14:20 UTC | 10h 10m |
| 2026-05-12 | AMX006 | - | May 12, 13:20 UTC | May 13, 01:10 UTC | 11h 50m |
| 2026-05-12 | AMX005 | - | May 12, 02:45 UTC | May 12, 09:20 UTC | 6h 35m |
| 2026-05-11 | AMX029 | EZE → MEX | May 11, 02:40 UTC | May 11, 11:15 UTC | 8h 35m |
| 2026-05-10 | AMX030 | MEX → EZE | May 10, 16:00 UTC | May 11, 00:25 UTC | 8h 25m |
| 2026-05-09 | AMX057 | NRT → MEX | May 9, 00:55 UTC | May 9, 10:50 UTC | 9h 55m |
| 2026-05-08 | AMX058 | MTY → NRT | May 8, 08:14 UTC | May 8, 21:40 UTC | 13h 25m |
| 2026-05-08 | AMX058 | MTY → NRT | May 8, 05:35 UTC | May 8, 06:39 UTC | 1h 5m |
| 2026-05-07 | AMX015 | GRU → MEX | May 7, 13:20 UTC | May 7, 21:50 UTC | 8h 30m |
| 2026-05-07 | AMX014 | MEX → GRU | May 7, 01:35 UTC | May 7, 10:25 UTC | 8h 50m |
| 2026-05-06 | AMX971 | MTY → MEX | May 6, 22:20 UTC | May 6, 22:25 UTC | 5m |
| 2026-05-06 | AMX971 | MTY → MEX | May 6, 21:20 UTC | May 6, 21:45 UTC | 25m |
| 2026-05-06 | AMX035 | MAD → MTY | May 6, 17:00 UTC | May 6, 19:15 UTC | 2h 14m |
| 2026-05-06 | AMX035 | MAD → MTY | May 6, 07:30 UTC | May 6, 16:55 UTC | 9h 25m |
| 2026-05-05 | AMX034 | MEX → MTY | May 5, 17:05 UTC | May 6, 02:15 UTC | 9h 10m |
| 2026-05-05 | AMX034 | MEX → MTY | May 5, 13:25 UTC | May 5, 14:25 UTC | 1h 0m |
| 2026-05-04 | AMX038 | BCN → MEX | May 4, 15:45 UTC | May 5, 03:30 UTC | 11h 46m |
| 2026-05-04 | AMX037 | MEX → BCN | May 4, 03:05 UTC | May 4, 13:20 UTC | 10h 15m |
| 2026-05-03 | AMX091 | ICN → MEX | May 3, 16:20 UTC | May 3, 16:30 UTC | 10m |
| 2026-05-03 | AMX091 | ICN → MEX | May 3, 03:15 UTC | May 3, 14:50 UTC | 11h 34m |
| 2026-05-02 | AMX090 | MTY → ICN | May 2, 06:25 UTC | May 2, 21:05 UTC | 14h 40m |
| 2026-05-02 | AMX090 | MTY → ICN | May 2, 03:40 UTC | May 2, 04:40 UTC | 1h 0m |
| 2026-05-01 | AMX647 | LAX → MEX | May 1, 22:30 UTC | May 1, 22:35 UTC | 5m |
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 XA-ADG page for operator, model, and routing details .