sensors Mode-S transponder
0D0C4F
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-VCY · LEARJET 35
- Hex
- 0D0C4F
- Octal
- 03206117
- Decimal
- 855,119
- Country
- MX
- Tail
- XA-VCY
- Type
- LJ35
- Flights observed
- 66
- Distinct callsigns
- 1
- Country
- MX
- Last broadcast
- 17d ago
Last known position
Country allocation
The ICAO 24-bit address 0D0C4F 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 |
|---|---|---|---|
| XAVCY | - | 66 | 2026-06-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-30 | XAVCY | - | Jun 30, 17:35 UTC | Jun 30, 18:00 UTC | 25m |
| 2026-06-30 | XAVCY | - | Jun 30, 13:50 UTC | Jun 30, 15:25 UTC | 1h 35m |
| 2026-06-29 | XAVCY | - | Jun 29, 21:24 UTC | Jun 29, 21:54 UTC | 30m |
| 2026-06-28 | XAVCY | - | Jun 28, 18:25 UTC | Jun 28, 18:59 UTC | 35m |
| 2026-06-22 | XAVCY | - | Jun 22, 17:10 UTC | Jun 22, 18:04 UTC | 55m |
| 2026-06-22 | XAVCY | - | Jun 22, 13:35 UTC | Jun 22, 15:50 UTC | 2h 15m |
| 2026-06-17 | XAVCY | - | Jun 17, 00:15 UTC | Jun 17, 01:05 UTC | 50m |
| 2026-06-16 | XAVCY | - | Jun 16, 22:25 UTC | Jun 16, 22:40 UTC | 15m |
| 2026-06-16 | XAVCY | - | Jun 16, 21:05 UTC | Jun 16, 21:30 UTC | 25m |
| 2026-06-16 | XAVCY | - | Jun 16, 18:29 UTC | Jun 16, 19:15 UTC | 45m |
| 2026-06-16 | XAVCY | - | Jun 16, 13:00 UTC | Jun 16, 15:00 UTC | 2h 0m |
| 2026-06-03 | XAVCY | - | Jun 3, 00:05 UTC | Jun 3, 00:50 UTC | 45m |
| 2026-06-02 | XAVCY | - | Jun 2, 22:05 UTC | Jun 2, 22:20 UTC | 15m |
| 2026-06-02 | XAVCY | - | Jun 2, 20:05 UTC | Jun 2, 20:20 UTC | 15m |
| 2026-06-02 | XAVCY | - | Jun 2, 17:45 UTC | Jun 2, 18:00 UTC | 15m |
| 2026-06-02 | XAVCY | - | Jun 2, 14:25 UTC | Jun 2, 16:10 UTC | 1h 45m |
| 2026-05-31 | XAVCY | - | May 31, 22:15 UTC | Jun 1, 01:10 UTC | 2h 55m |
| 2026-05-31 | XAVCY | - | May 31, 18:50 UTC | May 31, 19:35 UTC | 45m |
| 2026-05-31 | XAVCY | - | May 31, 13:10 UTC | May 31, 14:05 UTC | 55m |
| 2026-05-27 | XAVCY | - | May 27, 21:40 UTC | May 27, 22:05 UTC | 25m |
| 2026-05-27 | XAVCY | - | May 27, 18:55 UTC | May 27, 19:20 UTC | 25m |
| 2026-05-26 | XAVCY | - | May 26, 20:09 UTC | May 26, 22:05 UTC | 1h 55m |
| 2026-05-26 | XAVCY | - | May 26, 18:45 UTC | May 26, 19:20 UTC | 35m |
| 2026-05-26 | XAVCY | - | May 26, 15:05 UTC | May 26, 17:20 UTC | 2h 15m |
| 2026-05-26 | XAVCY | - | May 26, 11:44 UTC | May 26, 13:45 UTC | 2h 0m |
| 2026-05-20 | XAVCY | - | May 20, 17:50 UTC | May 20, 18:35 UTC | 45m |
| 2026-05-20 | XAVCY | - | May 20, 06:20 UTC | May 20, 06:35 UTC | 15m |
| 2026-05-19 | XAVCY | - | May 19, 09:50 UTC | May 20, 04:35 UTC | 18h 45m |
| 2026-05-19 | XAVCY | - | May 19, 08:55 UTC | May 20, 04:35 UTC | 19h 40m |
| 2026-05-19 | XAVCY | - | May 19, 04:25 UTC | May 19, 05:35 UTC | 1h 10m |
| 2026-05-17 | XAVCY | - | May 17, 21:10 UTC | May 17, 21:40 UTC | 30m |
| 2026-05-17 | XAVCY | - | May 17, 12:15 UTC | May 17, 12:40 UTC | 25m |
| 2026-05-15 | XAVCY | - | May 15, 00:40 UTC | May 15, 01:30 UTC | 50m |
| 2026-05-14 | XAVCY | - | May 14, 21:50 UTC | May 14, 22:05 UTC | 15m |
| 2026-05-14 | XAVCY | - | May 14, 20:30 UTC | May 14, 20:40 UTC | 10m |
| 2026-05-14 | XAVCY | - | May 14, 17:40 UTC | May 14, 19:55 UTC | 2h 15m |
| 2026-05-14 | XAVCY | - | May 14, 14:55 UTC | May 14, 15:55 UTC | 1h 0m |
| 2026-05-13 | XAVCY | - | May 13, 21:55 UTC | May 14, 00:05 UTC | 2h 10m |
| 2026-05-13 | XAVCY | - | May 13, 18:40 UTC | May 13, 20:25 UTC | 1h 45m |
| 2026-05-10 | XAVCY | - | May 10, 18:15 UTC | May 10, 20:30 UTC | 2h 15m |
| 2026-05-10 | XAVCY | - | May 10, 15:15 UTC | May 10, 17:45 UTC | 2h 30m |
| 2026-05-08 | XAVCY | - | May 8, 11:25 UTC | May 8, 12:34 UTC | 1h 10m |
| 2026-05-08 | XAVCY | - | May 8, 04:39 UTC | May 8, 08:14 UTC | 3h 35m |
| 2026-05-02 | XAVCY | - | May 2, 05:00 UTC | May 2, 06:15 UTC | 1h 15m |
| 2026-05-02 | XAVCY | - | May 2, 00:55 UTC | May 2, 02:10 UTC | 1h 15m |
| 2026-04-29 | XAVCY | - | Apr 29, 06:10 UTC | Apr 29, 06:45 UTC | 35m |
| 2026-04-29 | XAVCY | - | Apr 29, 01:45 UTC | Apr 29, 04:39 UTC | 2h 55m |
| 2026-04-28 | XAVCY | RBD → MSP | Apr 28, 21:00 UTC | Apr 28, 23:10 UTC | 2h 10m |
| 2026-04-28 | XAVCY | - | Apr 28, 17:40 UTC | Apr 28, 19:10 UTC | 1h 30m |
| 2026-04-27 | XAVCY | - | Apr 27, 02:20 UTC | Apr 27, 04:45 UTC | 2h 25m |
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-VCY page for operator, model, and routing details .