sensors Mode-S transponder
0D0AF2
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-UZV · MCDONNELL-DOUGLAS MD-83
- Hex
- 0D0AF2
- Octal
- 03205362
- Decimal
- 854,770
- Country
- MX
- Tail
- XA-UZV
- Type
- MD83
- Flights observed
- 70
- Distinct callsigns
- 2
- Country
- MX
- Last broadcast
- 2h ago
Current position
Country allocation
The ICAO 24-bit address 0D0AF2 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-12 | VTM288 | - | Jun 12, 22:55 UTC | Jun 13, 03:35 UTC | 4h 40m |
| 2026-06-11 | VTM288 | - | Jun 11, 21:55 UTC | Jun 11, 23:15 UTC | 1h 20m |
| 2026-06-11 | VTM288 | - | Jun 11, 06:35 UTC | Jun 11, 07:55 UTC | 1h 20m |
| 2026-06-11 | VTM288 | LRD → CHA | Jun 11, 02:30 UTC | Jun 11, 04:35 UTC | 2h 5m |
| 2026-06-10 | VTM288 | - | Jun 10, 21:55 UTC | Jun 11, 01:00 UTC | 3h 5m |
| 2026-06-10 | VTM288 | - | Jun 10, 06:55 UTC | Jun 10, 07:10 UTC | 15m |
| 2026-06-10 | VTM288 | - | Jun 10, 02:00 UTC | Jun 10, 02:10 UTC | 10m |
| 2026-06-09 | VTM288 | - | Jun 9, 22:35 UTC | Jun 10, 01:05 UTC | 2h 30m |
| 2026-06-09 | VTM288 | - | Jun 9, 06:05 UTC | Jun 9, 08:20 UTC | 2h 15m |
| 2026-06-09 | VTM288 | - | Jun 9, 02:10 UTC | Jun 9, 04:55 UTC | 2h 45m |
| 2026-06-06 | VTM288 | - | Jun 6, 16:10 UTC | Jun 6, 18:39 UTC | 2h 30m |
| 2026-06-05 | VTM990 | LRD → CHA | Jun 5, 10:30 UTC | Jun 5, 12:35 UTC | 2h 5m |
| 2026-06-05 | VTM288 | - | Jun 5, 06:55 UTC | Jun 5, 09:20 UTC | 2h 25m |
| 2026-06-04 | VTM288 | - | Jun 4, 23:05 UTC | Jun 5, 01:35 UTC | 2h 30m |
| 2026-06-04 | VTM288 | - | Jun 4, 07:05 UTC | Jun 4, 09:10 UTC | 2h 5m |
| 2026-06-04 | VTM288 | - | Jun 4, 01:10 UTC | Jun 4, 05:35 UTC | 4h 25m |
| 2026-06-03 | VTM288 | - | Jun 3, 21:55 UTC | Jun 3, 23:25 UTC | 1h 30m |
| 2026-06-02 | VTM288 | - | Jun 2, 21:50 UTC | Jun 3, 00:05 UTC | 2h 15m |
| 2026-06-02 | VTM288 | - | Jun 2, 16:35 UTC | Jun 2, 19:55 UTC | 3h 20m |
| 2026-06-02 | VTM288 | - | Jun 2, 06:40 UTC | Jun 2, 15:10 UTC | 8h 30m |
| 2026-05-30 | VTM288 | - | May 30, 22:10 UTC | May 30, 23:35 UTC | 1h 25m |
| 2026-05-30 | VTM288 | - | May 30, 19:35 UTC | May 30, 21:05 UTC | 1h 30m |
| 2026-05-30 | VTM288 | - | May 30, 03:20 UTC | May 30, 05:35 UTC | 2h 15m |
| 2026-05-30 | VTM288 | - | May 30, 01:25 UTC | May 30, 01:55 UTC | 30m |
| 2026-05-29 | VTM288 | - | May 29, 22:35 UTC | May 29, 22:45 UTC | 10m |
| 2026-05-26 | VTM288 | - | May 26, 22:54 UTC | May 27, 01:54 UTC | 3h 0m |
| 2026-05-26 | VTM288 | - | May 26, 04:24 UTC | May 26, 06:39 UTC | 2h 15m |
| 2026-05-26 | VTM288 | - | May 26, 02:10 UTC | May 26, 02:55 UTC | 45m |
| 2026-05-24 | VTM288 | - | May 24, 00:45 UTC | May 24, 02:20 UTC | 1h 35m |
| 2026-05-23 | VTM288 | - | May 23, 21:35 UTC | May 23, 23:05 UTC | 1h 30m |
| 2026-05-23 | VTM288 | - | May 23, 04:55 UTC | May 23, 07:10 UTC | 2h 15m |
| 2026-05-22 | VTM288 | - | May 22, 23:00 UTC | May 23, 03:35 UTC | 4h 34m |
| 2026-05-21 | VTM288 | - | May 21, 15:55 UTC | May 21, 17:25 UTC | 1h 30m |
| 2026-05-21 | VTM288 | - | May 21, 10:20 UTC | May 21, 11:50 UTC | 1h 30m |
| 2026-05-21 | VTM288 | - | May 21, 06:05 UTC | May 21, 08:15 UTC | 2h 10m |
| 2026-05-21 | VTM288 | - | May 21, 03:40 UTC | May 21, 04:15 UTC | 35m |
| 2026-05-21 | VTM288 | - | May 21, 00:25 UTC | May 21, 03:00 UTC | 2h 35m |
| 2026-05-16 | VTM288 | - | May 16, 09:25 UTC | May 16, 12:55 UTC | 3h 30m |
| 2026-05-15 | VTM288 | LRD → YIP | May 15, 14:30 UTC | May 15, 17:15 UTC | 2h 44m |
| 2026-05-15 | VTM288 | - | May 15, 11:50 UTC | May 15, 12:35 UTC | 45m |
| 2026-05-14 | VTM288 | - | May 14, 14:40 UTC | May 15, 12:35 UTC | 21h 55m |
| 2026-05-13 | VTM288 | - | May 13, 22:05 UTC | May 14, 01:05 UTC | 3h 0m |
| 2026-05-13 | VTM288 | LRD → YIP | May 13, 04:50 UTC | May 13, 07:40 UTC | 2h 50m |
| 2026-05-12 | VTM288 | - | May 12, 23:25 UTC | May 13, 03:30 UTC | 4h 5m |
| 2026-05-10 | VTM288 | - | May 10, 18:05 UTC | May 10, 21:30 UTC | 3h 25m |
| 2026-05-09 | VTM288 | LRD → TOL | May 9, 22:45 UTC | May 10, 01:14 UTC | 2h 30m |
| 2026-05-09 | VTM288 | - | May 9, 21:05 UTC | May 9, 21:34 UTC | 30m |
| 2026-05-09 | VTM288 | - | May 9, 16:35 UTC | May 9, 20:34 UTC | 4h 0m |
| 2026-05-08 | VTM288 | - | May 8, 16:15 UTC | May 8, 19:15 UTC | 3h 0m |
| 2026-05-08 | VTM288 | - | May 8, 10:04 UTC | May 8, 11:49 UTC | 1h 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-UZV page for operator, model, and routing details .