sensors Mode-S transponder
0D0654
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-CMA · LEARJET 45
- Hex
- 0D0654
- Octal
- 03203124
- Decimal
- 853,588
- Country
- MX
- Tail
- XA-CMA
- Type
- LJ45
- Flights observed
- 62
- Distinct callsigns
- 9
- Country
- MX
- Last broadcast
- 17d ago
Last known position
Country allocation
The ICAO 24-bit address 0D0654 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 9 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-30 | ACW1432 | - | Jun 30, 20:55 UTC | Jun 30, 21:15 UTC | 20m |
| 2026-06-30 | ACW2431 | - | Jun 30, 17:50 UTC | Jun 30, 18:40 UTC | 50m |
| 2026-06-30 | ACW2430 | - | Jun 30, 14:50 UTC | Jun 30, 16:40 UTC | 1h 50m |
| 2026-06-24 | ACW1430 | - | Jun 24, 14:20 UTC | Jun 24, 14:45 UTC | 25m |
| 2026-06-23 | ACW1430 | - | Jun 23, 22:15 UTC | Jun 23, 23:29 UTC | 1h 15m |
| 2026-06-21 | ACW2431 | - | Jun 21, 17:24 UTC | Jun 21, 19:20 UTC | 1h 55m |
| 2026-06-21 | ACW2430 | - | Jun 21, 13:34 UTC | Jun 21, 16:25 UTC | 2h 50m |
| 2026-06-20 | ACW2431 | - | Jun 20, 17:44 UTC | Jun 20, 20:25 UTC | 2h 40m |
| 2026-06-20 | ACW2430 | - | Jun 20, 14:19 UTC | Jun 20, 16:24 UTC | 2h 5m |
| 2026-06-19 | ACW2431 | - | Jun 19, 22:55 UTC | Jun 19, 23:54 UTC | 1h 0m |
| 2026-06-19 | ACW2430 | - | Jun 19, 18:49 UTC | Jun 19, 20:29 UTC | 1h 40m |
| 2026-06-16 | ACW1430 | - | Jun 16, 21:25 UTC | Jun 16, 21:55 UTC | 30m |
| 2026-06-15 | ACW1430 | - | Jun 15, 15:45 UTC | Jun 15, 16:15 UTC | 30m |
| 2026-06-14 | ACW1430 | - | Jun 14, 18:30 UTC | Jun 15, 16:15 UTC | 21h 44m |
| 2026-06-12 | ACW1431 | - | Jun 12, 19:00 UTC | Jun 12, 19:55 UTC | 55m |
| 2026-06-12 | ACW1430 | - | Jun 12, 02:15 UTC | Jun 12, 17:55 UTC | 15h 40m |
| 2026-06-10 | ACW1430 | - | Jun 10, 19:25 UTC | Jun 10, 19:35 UTC | 10m |
| 2026-06-09 | ACW1431 | - | Jun 9, 18:10 UTC | Jun 9, 18:20 UTC | 10m |
| 2026-06-07 | ACW1430 | - | Jun 7, 21:15 UTC | Jun 7, 21:25 UTC | 10m |
| 2026-05-22 | ACW1432 | - | May 22, 22:00 UTC | May 22, 22:30 UTC | 30m |
| 2026-05-22 | ACW1431 | - | May 22, 18:55 UTC | May 22, 19:25 UTC | 30m |
| 2026-05-15 | ACW1431 | - | May 15, 22:00 UTC | May 15, 22:20 UTC | 20m |
| 2026-05-15 | ACW1430 | - | May 15, 15:20 UTC | May 15, 17:35 UTC | 2h 15m |
| 2026-05-14 | ACW1432 | - | May 14, 16:15 UTC | May 14, 22:10 UTC | 5h 55m |
| 2026-05-14 | ACW2430 | - | May 14, 13:45 UTC | May 14, 14:20 UTC | 35m |
| 2026-05-13 | ACW2433 | - | May 13, 23:50 UTC | May 14, 01:40 UTC | 1h 50m |
| 2026-05-13 | ACW1432 | MTY → CUN | May 13, 14:40 UTC | May 13, 22:20 UTC | 7h 40m |
| 2026-05-13 | ACW1433 | - | May 13, 02:10 UTC | May 13, 03:40 UTC | 1h 30m |
| 2026-05-13 | ACW1432 | - | May 13, 01:20 UTC | May 13, 01:35 UTC | 15m |
| 2026-05-12 | ACW1431 | - | May 12, 19:10 UTC | May 12, 19:25 UTC | 15m |
| 2026-05-12 | ACW2430 | - | May 12, 15:40 UTC | May 12, 17:50 UTC | 2h 10m |
| 2026-05-11 | ACW2432 | - | May 11, 18:20 UTC | May 11, 18:40 UTC | 20m |
| 2026-05-10 | ACW1431 | - | May 10, 21:35 UTC | May 10, 22:09 UTC | 35m |
| 2026-05-10 | ACW1431 | - | May 10, 19:19 UTC | May 10, 19:40 UTC | 20m |
| 2026-05-09 | ACW1430 | - | May 9, 17:25 UTC | May 9, 17:45 UTC | 20m |
| 2026-05-09 | ACW1432 | - | May 9, 00:15 UTC | May 9, 00:35 UTC | 20m |
| 2026-05-08 | ACW1431 | - | May 8, 22:55 UTC | May 8, 23:30 UTC | 35m |
| 2026-05-05 | ACW1430 | - | May 5, 18:40 UTC | May 5, 19:10 UTC | 30m |
| 2026-05-04 | ACW2431 | PHX → MTY | May 4, 19:45 UTC | May 4, 21:45 UTC | 2h 0m |
| 2026-05-04 | ACW2430 | - | May 4, 17:30 UTC | May 4, 18:30 UTC | 1h 0m |
| 2026-05-03 | ACW1430 | - | May 3, 17:54 UTC | May 3, 18:14 UTC | 20m |
| 2026-05-02 | ACW1431 | - | May 2, 16:55 UTC | May 2, 17:25 UTC | 30m |
| 2026-05-01 | ACW1431 | NTR → MTY | May 1, 22:00 UTC | May 2, 17:25 UTC | 19h 25m |
| 2026-05-01 | ACW1432 | MTY → MTY | May 1, 14:45 UTC | May 1, 20:35 UTC | 5h 50m |
| 2026-04-30 | ACW1434 | - | Apr 30, 23:45 UTC | May 1, 00:55 UTC | 1h 10m |
| 2026-04-30 | ACW1430 | - | Apr 30, 15:10 UTC | Apr 30, 15:20 UTC | 10m |
| 2026-04-28 | ACW1431 | - | Apr 28, 20:55 UTC | Apr 28, 21:30 UTC | 35m |
| 2026-04-28 | ACW1430 | - | Apr 28, 19:05 UTC | Apr 28, 19:35 UTC | 30m |
| 2026-04-27 | ACW1430 | - | Apr 27, 13:35 UTC | Apr 27, 13:55 UTC | 20m |
| 2026-04-26 | ACW2430 | - | Apr 26, 22:30 UTC | Apr 26, 23:15 UTC | 45m |
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-CMA page for operator, model, and routing details .