sensors Mode-S transponder
0D0EC3
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-CMM · DASSAULT Falcon 2000
- Hex
- 0D0EC3
- Octal
- 03207303
- Decimal
- 855,747
- Country
- MX
- Tail
- XA-CMM
- Type
- F2TH
- Flights observed
- 24
- Distinct callsigns
- 1
- Country
- MX
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 0D0EC3 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| XACMM | - | 24 | 2026-06-05 |
Recent flights last 24
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-05 | XACMM | - | Jun 5, 00:00 UTC | Jun 5, 01:05 UTC | 1h 5m |
| 2026-06-02 | XACMM | - | Jun 2, 23:40 UTC | Jun 2, 23:50 UTC | 10m |
| 2026-06-02 | XACMM | - | Jun 2, 16:30 UTC | Jun 2, 16:55 UTC | 25m |
| 2026-05-20 | XACMM | HMO → MTY | May 20, 23:10 UTC | May 21, 00:45 UTC | 1h 35m |
| 2026-05-20 | XACMM | MTY → HMO | May 20, 14:15 UTC | May 20, 15:55 UTC | 1h 40m |
| 2026-05-17 | XACMM | - | May 17, 20:05 UTC | May 17, 21:35 UTC | 1h 30m |
| 2026-05-15 | XACMM | - | May 15, 21:15 UTC | May 15, 22:35 UTC | 1h 20m |
| 2026-05-14 | XACMM | SEA → MTY | May 14, 21:00 UTC | May 15, 01:00 UTC | 4h 0m |
| 2026-05-12 | XACMM | - | May 12, 18:00 UTC | May 12, 21:55 UTC | 3h 55m |
| 2026-05-12 | XACMM | MTY → LRD | May 12, 16:55 UTC | May 12, 17:25 UTC | 30m |
| 2026-05-07 | XACMM | DAL → MTY | May 7, 21:25 UTC | May 7, 22:50 UTC | 1h 25m |
| 2026-05-07 | XACMM | - | May 7, 16:35 UTC | May 7, 17:50 UTC | 1h 15m |
| 2026-05-05 | XACMM | - | May 5, 02:15 UTC | May 5, 03:25 UTC | 1h 10m |
| 2026-05-04 | XACMM | - | May 4, 14:00 UTC | May 4, 14:25 UTC | 25m |
| 2026-05-03 | XACMM | - | May 3, 22:30 UTC | May 3, 23:39 UTC | 1h 10m |
| 2026-05-03 | XACMM | - | May 3, 21:20 UTC | May 3, 21:50 UTC | 30m |
| 2026-04-30 | XACMM | - | Apr 30, 20:40 UTC | Apr 30, 21:55 UTC | 1h 15m |
| 2026-04-28 | XACMM | MTY → MTY | Apr 28, 16:30 UTC | Apr 28, 23:40 UTC | 7h 10m |
| 2026-04-23 | XACMM | - | Apr 23, 22:45 UTC | Apr 24, 00:05 UTC | 1h 20m |
| 2026-04-22 | XACMM | - | Apr 22, 22:40 UTC | Apr 22, 23:00 UTC | 20m |
| 2026-04-22 | XACMM | - | Apr 22, 17:00 UTC | Apr 22, 18:10 UTC | 1h 10m |
| 2026-04-22 | XACMM | - | Apr 22, 13:40 UTC | Apr 22, 14:05 UTC | 25m |
| 2026-04-21 | XACMM | MTY → MTY | Apr 21, 15:10 UTC | Apr 21, 22:45 UTC | 7h 35m |
| 2026-04-16 | XACMM | MTY → MTY | Apr 16, 15:55 UTC | Apr 16, 16:25 UTC | 30m |
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-CMM page for operator, model, and routing details .