sensors Mode-S transponder
0D11B3
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-VHZ · LEARJET 35
- Hex
- 0D11B3
- Octal
- 03210663
- Decimal
- 856,499
- Country
- MX
- Tail
- XA-VHZ
- Type
- LJ35
- Flights observed
- 62
- Distinct callsigns
- 1
- Country
- MX
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 0D11B3 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 |
|---|---|---|---|
| XAVHZ | - | 62 | 2026-07-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-21 | XAVHZ | - | Jul 21, 20:00 UTC | Jul 21, 22:25 UTC | 2h 25m |
| 2026-07-21 | XAVHZ | - | Jul 21, 14:00 UTC | Jul 21, 16:00 UTC | 2h 0m |
| 2026-07-17 | XAVHZ | - | Jul 17, 16:19 UTC | Jul 17, 17:40 UTC | 1h 20m |
| 2026-07-16 | XAVHZ | - | Jul 16, 23:15 UTC | Jul 17, 00:35 UTC | 1h 20m |
| 2026-07-15 | XAVHZ | - | Jul 15, 22:45 UTC | Jul 16, 00:10 UTC | 1h 25m |
| 2026-07-15 | XAVHZ | - | Jul 15, 18:35 UTC | Jul 15, 21:05 UTC | 2h 30m |
| 2026-07-14 | XAVHZ | - | Jul 14, 21:15 UTC | Jul 15, 15:45 UTC | 18h 29m |
| 2026-07-14 | XAVHZ | - | Jul 14, 19:15 UTC | Jul 15, 15:45 UTC | 20h 29m |
| 2026-07-14 | XAVHZ | - | Jul 14, 16:00 UTC | Jul 14, 18:20 UTC | 2h 20m |
| 2026-07-14 | XAVHZ | - | Jul 14, 03:50 UTC | Jul 14, 06:40 UTC | 2h 50m |
| 2026-07-14 | XAVHZ | - | Jul 14, 00:45 UTC | Jul 14, 01:40 UTC | 55m |
| 2026-07-08 | XAVHZ | - | Jul 8, 15:40 UTC | Jul 8, 16:10 UTC | 30m |
| 2026-07-07 | XAVHZ | - | Jul 7, 20:30 UTC | Jul 7, 21:00 UTC | 30m |
| 2026-07-03 | XAVHZ | - | Jul 3, 15:55 UTC | Jul 3, 16:20 UTC | 25m |
| 2026-07-02 | XAVHZ | - | Jul 2, 20:20 UTC | Jul 2, 20:45 UTC | 25m |
| 2026-06-30 | XAVHZ | - | Jun 30, 13:35 UTC | Jun 30, 13:50 UTC | 15m |
| 2026-06-24 | XAVHZ | - | Jun 24, 15:35 UTC | Jun 24, 18:25 UTC | 2h 50m |
| 2026-06-23 | XAVHZ | - | Jun 23, 21:10 UTC | Jun 23, 22:34 UTC | 1h 25m |
| 2026-06-23 | XAVHZ | - | Jun 23, 15:19 UTC | Jun 23, 17:30 UTC | 2h 10m |
| 2026-06-23 | XAVHZ | - | Jun 23, 00:04 UTC | Jun 23, 01:35 UTC | 1h 30m |
| 2026-06-22 | XAVHZ | LRD → DAL | Jun 22, 02:14 UTC | Jun 22, 03:35 UTC | 1h 20m |
| 2026-06-22 | XAVHZ | - | Jun 22, 00:04 UTC | Jun 22, 01:40 UTC | 1h 35m |
| 2026-06-21 | XAVHZ | - | Jun 21, 15:59 UTC | Jun 21, 16:19 UTC | 20m |
| 2026-06-21 | XAVHZ | - | Jun 21, 12:24 UTC | Jun 21, 15:25 UTC | 3h 0m |
| 2026-06-18 | XAVHZ | - | Jun 18, 20:15 UTC | Jun 18, 20:40 UTC | 25m |
| 2026-06-18 | XAVHZ | - | Jun 18, 06:20 UTC | Jun 18, 18:00 UTC | 11h 40m |
| 2026-06-10 | XAVHZ | - | Jun 10, 23:05 UTC | Jun 10, 23:35 UTC | 30m |
| 2026-06-10 | XAVHZ | - | Jun 10, 21:20 UTC | Jun 10, 21:45 UTC | 25m |
| 2026-06-04 | XAVHZ | - | Jun 4, 14:35 UTC | Jun 4, 15:00 UTC | 25m |
| 2026-06-04 | XAVHZ | - | Jun 4, 04:25 UTC | Jun 4, 05:55 UTC | 1h 30m |
| 2026-06-03 | XAVHZ | - | Jun 3, 21:15 UTC | Jun 3, 21:30 UTC | 15m |
| 2026-06-01 | XAVHZ | - | Jun 1, 05:05 UTC | Jun 1, 08:05 UTC | 3h 0m |
| 2026-05-31 | XAVHZ | - | May 31, 19:50 UTC | Jun 1, 01:20 UTC | 5h 30m |
| 2026-05-30 | XAVHZ | - | May 30, 03:05 UTC | May 30, 06:00 UTC | 2h 55m |
| 2026-05-29 | XAVHZ | - | May 29, 21:30 UTC | May 29, 23:05 UTC | 1h 35m |
| 2026-05-29 | XAVHZ | - | May 29, 15:50 UTC | May 29, 17:50 UTC | 2h 0m |
| 2026-05-22 | XAVHZ | - | May 22, 17:00 UTC | May 22, 22:25 UTC | 5h 25m |
| 2026-05-22 | XAVHZ | - | May 22, 03:30 UTC | May 22, 06:25 UTC | 2h 55m |
| 2026-05-21 | XAVHZ | - | May 21, 22:10 UTC | May 21, 23:20 UTC | 1h 10m |
| 2026-05-21 | XAVHZ | - | May 21, 17:55 UTC | May 21, 19:55 UTC | 2h 0m |
| 2026-05-20 | XAVHZ | - | May 20, 15:00 UTC | May 20, 15:55 UTC | 55m |
| 2026-05-20 | XAVHZ | - | May 20, 12:40 UTC | May 20, 13:30 UTC | 50m |
| 2026-05-09 | XAVHZ | - | May 9, 20:00 UTC | May 9, 21:25 UTC | 1h 25m |
| 2026-05-08 | XAVHZ | - | May 8, 18:30 UTC | May 9, 04:35 UTC | 10h 5m |
| 2026-05-04 | XAVHZ | - | May 4, 18:30 UTC | May 4, 19:45 UTC | 1h 16m |
| 2026-05-02 | XAVHZ | - | May 2, 00:00 UTC | May 2, 01:05 UTC | 1h 5m |
| 2026-05-01 | XAVHZ | - | May 1, 20:30 UTC | May 1, 20:45 UTC | 15m |
| 2026-04-30 | XAVHZ | - | Apr 30, 21:15 UTC | Apr 30, 22:30 UTC | 1h 15m |
| 2026-04-30 | XAVHZ | - | Apr 30, 15:45 UTC | Apr 30, 18:10 UTC | 2h 25m |
| 2026-04-30 | XAVHZ | - | Apr 30, 02:20 UTC | Apr 30, 05:15 UTC | 2h 55m |
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-VHZ page for operator, model, and routing details .