sensors Mode-S transponder
0D0A71
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-BPS · EMBRAER EMB-505 Phenom 300
- Hex
- 0D0A71
- Octal
- 03205161
- Decimal
- 854,641
- Country
- MX
- Tail
- XA-BPS
- Type
- E55P
- Flights observed
- 109
- Distinct callsigns
- 9
- Country
- MX
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 0D0A71 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-07-13 | ACW1512 | - | Jul 13, 01:30 UTC | Jul 13, 02:55 UTC | 1h 25m |
| 2026-07-12 | ACW1511 | - | Jul 12, 22:40 UTC | Jul 12, 23:40 UTC | 1h 0m |
| 2026-07-12 | ACW1510 | - | Jul 12, 02:01 UTC | Jul 12, 02:10 UTC | 10m |
| 2026-07-07 | ACW2510 | - | Jul 7, 15:15 UTC | Jul 7, 16:40 UTC | 1h 25m |
| 2026-07-06 | ACW2514 | - | Jul 6, 23:20 UTC | Jul 7, 02:40 UTC | 3h 20m |
| 2026-07-05 | ACW2511 | - | Jul 5, 22:10 UTC | Jul 5, 23:30 UTC | 1h 20m |
| 2026-07-05 | ACW2510 | - | Jul 5, 19:30 UTC | Jul 5, 20:50 UTC | 1h 20m |
| 2026-07-04 | ACW1512 | - | Jul 4, 19:15 UTC | Jul 5, 00:10 UTC | 4h 55m |
| 2026-07-02 | ACW1510 | - | Jul 2, 16:45 UTC | Jul 2, 17:10 UTC | 25m |
| 2026-06-30 | ACW1510 | - | Jun 30, 22:05 UTC | Jun 30, 22:45 UTC | 40m |
| 2026-06-29 | ACW1511 | - | Jun 29, 22:19 UTC | Jun 30, 22:15 UTC | 23h 56m |
| 2026-06-29 | ACW1511 | - | Jun 29, 21:54 UTC | Jun 29, 22:44 UTC | 50m |
| 2026-06-29 | ACW1510 | - | Jun 29, 16:29 UTC | Jun 29, 17:55 UTC | 1h 25m |
| 2026-06-28 | ACW2510 | - | Jun 28, 18:49 UTC | Jun 28, 21:50 UTC | 3h 0m |
| 2026-06-27 | ACW2511 | - | Jun 27, 16:20 UTC | Jun 27, 22:45 UTC | 6h 25m |
| 2026-06-26 | ACW2510 | - | Jun 26, 18:15 UTC | Jun 26, 20:10 UTC | 1h 55m |
| 2026-06-25 | ACW2511 | - | Jun 25, 18:55 UTC | Jun 25, 21:20 UTC | 2h 25m |
| 2026-06-25 | ACW2510 | NTR → LRD | Jun 25, 17:20 UTC | Jun 25, 17:49 UTC | 30m |
| 2026-06-24 | ACW2511 | - | Jun 24, 17:40 UTC | Jun 24, 18:25 UTC | 45m |
| 2026-06-24 | ACW2510 | - | Jun 24, 01:19 UTC | Jun 24, 14:55 UTC | 13h 35m |
| 2026-06-23 | ACW1510 | - | Jun 23, 16:39 UTC | Jun 23, 17:25 UTC | 45m |
| 2026-06-22 | ACW1510 | - | Jun 22, 18:40 UTC | Jun 23, 17:25 UTC | 22h 45m |
| 2026-06-21 | ACW1511 | - | Jun 21, 20:45 UTC | Jun 21, 21:24 UTC | 40m |
| 2026-06-19 | ACW1512 | - | Jun 19, 15:09 UTC | Jun 20, 00:09 UTC | 9h 0m |
| 2026-06-18 | ACW1511 | - | Jun 18, 15:55 UTC | Jun 18, 16:15 UTC | 20m |
| 2026-06-18 | ACW1510 | NTR → MTY | Jun 18, 13:45 UTC | Jun 18, 14:01 UTC | 15m |
| 2026-06-17 | ACW1510 | NTR → NTR | Jun 17, 20:00 UTC | Jun 18, 01:45 UTC | 5h 45m |
| 2026-06-16 | ACW1511 | - | Jun 16, 16:25 UTC | Jun 16, 17:00 UTC | 35m |
| 2026-06-14 | ACW1510 | - | Jun 14, 15:45 UTC | Jun 14, 16:25 UTC | 40m |
| 2026-06-13 | ACW1511 | - | Jun 13, 21:35 UTC | Jun 13, 22:10 UTC | 35m |
| 2026-06-13 | ACW1510 | - | Jun 13, 17:20 UTC | Jun 13, 20:00 UTC | 2h 40m |
| 2026-06-12 | ACW1513 | - | Jun 12, 22:25 UTC | Jun 13, 01:05 UTC | 2h 40m |
| 2026-06-12 | ACW1512 | - | Jun 12, 19:55 UTC | Jun 12, 20:30 UTC | 35m |
| 2026-06-12 | ACW1511 | - | Jun 12, 16:30 UTC | Jun 12, 18:40 UTC | 2h 10m |
| 2026-06-12 | ACW1510 | - | Jun 12, 13:30 UTC | Jun 12, 14:40 UTC | 1h 10m |
| 2026-06-11 | ACW1512 | - | Jun 11, 00:25 UTC | Jun 11, 00:55 UTC | 30m |
| 2026-06-10 | ACW2511 | - | Jun 10, 20:35 UTC | Jun 10, 23:30 UTC | 2h 55m |
| 2026-06-10 | ACW2510 | - | Jun 10, 15:55 UTC | Jun 10, 19:05 UTC | 3h 10m |
| 2026-06-08 | ACW2510 | - | Jun 8, 20:00 UTC | Jun 8, 21:20 UTC | 1h 20m |
| 2026-06-04 | ACW2510 | - | Jun 4, 16:00 UTC | Jun 4, 17:35 UTC | 1h 35m |
| 2026-06-04 | ACW1514 | - | Jun 4, 01:55 UTC | Jun 4, 02:20 UTC | 25m |
| 2026-06-03 | ACW1512 | CVJ → PBC | Jun 3, 20:10 UTC | Jun 4, 01:00 UTC | 4h 50m |
| 2026-06-03 | ACW1511 | - | Jun 3, 18:00 UTC | Jun 3, 18:25 UTC | 25m |
| 2026-06-03 | ACW1510 | - | Jun 3, 16:20 UTC | Jun 3, 16:30 UTC | 10m |
| 2026-06-03 | ACW1511 | - | Jun 3, 01:55 UTC | Jun 3, 02:45 UTC | 50m |
| 2026-06-02 | ACW1510 | - | Jun 2, 13:50 UTC | Jun 2, 14:25 UTC | 35m |
| 2026-05-31 | ACW1510 | - | May 31, 15:20 UTC | May 31, 15:45 UTC | 25m |
| 2026-05-30 | ACW1510 | - | May 30, 21:20 UTC | May 30, 22:40 UTC | 1h 20m |
| 2026-05-29 | ACW2510 | - | May 29, 00:55 UTC | May 29, 02:00 UTC | 1h 5m |
| 2026-05-26 | ACW2510 | - | May 26, 20:34 UTC | May 26, 21:04 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-BPS page for operator, model, and routing details .