Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

0D10BD

ICAO 24-bit transponder address · allocated to Mexico

Currently assigned to XA-VVC · AIRBUS A-320

Hex
0D10BD
Octal
03210275
Decimal
856,253
Country
MX
Tail
XA-VVC
Type
A320
No current signal · last broadcast 11h ago
Flights observed
284
Distinct callsigns
20
Country
MX
Last broadcast
11h ago

Last known position

Most recent position reported by Mode-S 0D10BD.

Country allocation

The ICAO 24-bit address 0D10BD 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 20 distinct

Callsign Airline Flights Last seen
VOI380 - 8 2026-07-05
VOI381 - 7 2026-07-06
VOI3268 Volaris 7 2026-05-20
VOI3257 - 6 2026-07-05
VOI243 - 6 2026-07-04
VOI441 Volaris 5 2026-06-03
VOI3182 - 5 2026-07-05
VOI244 - 5 2026-07-03
VOI5585 - 4 2026-06-22
VOI390 Volaris 4 2026-05-17
VOI371 Volaris 4 2026-05-21
VOI3598 Volaris 4 2026-06-03
VOI3183 - 4 2026-07-05
VOI249 - 4 2026-06-27
VOI1091 - 4 2026-06-19
VOI1050 Volaris 4 2026-05-29
VOI1047 Volaris 4 2026-05-29
VOI5609 - 3 2026-07-06
VOI5608 - 3 2026-07-07
VOI5596 - 3 2026-06-22

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 VOI1105 - Jul 14, 01:25 UTCJul 14, 02:15 UTC50m
2026-07-13 VOI7417 - Jul 13, 20:30 UTCJul 13, 23:30 UTC3h 0m
2026-07-13 VOI7400 - Jul 13, 15:45 UTCJul 13, 19:15 UTC3h 30m
2026-07-13 VOI1104 - Jul 13, 13:45 UTCJul 13, 14:30 UTC45m
2026-07-12 VOI1411 - Jul 12, 14:30 UTCJul 12, 15:01 UTC30m
2026-07-11 VOI1340 - Jul 11, 20:15 UTCJul 12, 13:35 UTC17h 20m
2026-07-11 VOI1340 - Jul 11, 17:20 UTCJul 12, 13:35 UTC20h 15m
2026-07-11 VOI1049 - Jul 11, 15:50 UTCJul 12, 13:35 UTC21h 45m
2026-07-09 VOI5082 - Jul 9, 17:50 UTCJul 9, 22:10 UTC4h 20m
2026-07-09 VOI5269 - Jul 9, 13:30 UTCJul 9, 16:35 UTC3h 5m
2026-07-09 VOI5268 - Jul 9, 09:10 UTCJul 9, 12:15 UTC3h 5m
2026-07-08 VOI3221 - Jul 8, 20:30 UTCJul 8, 23:40 UTC3h 10m
2026-07-08 VOI3552 CUN → PBC Jul 8, 17:50 UTCJul 8, 19:40 UTC1h 50m
2026-07-08 VOI5644 - Jul 8, 09:10 UTCJul 8, 15:15 UTC6h 5m
2026-07-07 VOI1008 - Jul 7, 20:50 UTCJul 8, 03:40 UTC6h 50m
2026-07-07 VOI5608 - Jul 7, 16:35 UTCJul 7, 19:00 UTC2h 25m
2026-07-07 VOI1090 MTY → MTY Jul 7, 12:00 UTCJul 7, 15:35 UTC3h 35m
2026-07-06 VOI5578 MTY → MTY Jul 6, 23:20 UTCJul 7, 02:30 UTC3h 10m
2026-07-06 VOI5609 - Jul 6, 19:45 UTCJul 6, 22:15 UTC2h 30m
2026-07-06 VOI3255 - Jul 6, 13:10 UTCJul 6, 18:25 UTC5h 15m
2026-07-06 VOI5180 - Jul 6, 08:40 UTCJul 6, 11:45 UTC3h 5m
2026-07-06 VOI381 - Jul 6, 03:55 UTCJul 6, 04:05 UTC10m
2026-07-06 VOI381 - Jul 6, 01:55 UTCJul 6, 02:10 UTC15m
2026-07-05 VOI3182 - Jul 5, 23:00 UTCJul 6, 00:05 UTC1h 5m
2026-07-05 VOI3257 - Jul 5, 18:00 UTCJul 5, 22:00 UTC4h 0m
2026-07-05 VOI3183 - Jul 5, 15:50 UTCJul 5, 16:50 UTC1h 0m
2026-07-05 VOI380 - Jul 5, 14:35 UTCJul 5, 14:45 UTC10m
2026-07-05 VOI380 - Jul 5, 12:35 UTCJul 5, 12:55 UTC20m
2026-07-04 VOI243 MTY → MEX Jul 4, 23:30 UTCJul 5, 00:35 UTC1h 5m
2026-07-04 VOI5591 MTY → MTY Jul 4, 16:40 UTCJul 4, 20:55 UTC4h 15m
2026-07-04 VOI5548 MTY → MTY Jul 4, 12:30 UTCJul 4, 15:45 UTC3h 15m
2026-07-04 VOI5589 - Jul 4, 01:05 UTCJul 4, 03:05 UTC2h 0m
2026-07-03 VOI5588 MTY → CUN Jul 3, 22:05 UTCJul 4, 00:00 UTC1h 55m
2026-07-03 VOI5590 MTY → MTY Jul 3, 16:40 UTCJul 3, 21:00 UTC4h 20m
2026-07-03 VOI5548 MTY → MTY Jul 3, 12:10 UTCJul 3, 15:40 UTC3h 30m
2026-07-03 VOI244 - Jul 3, 02:15 UTCJul 3, 03:30 UTC1h 15m
2026-07-02 VOI243 MTY → MEX Jul 2, 23:45 UTCJul 3, 00:55 UTC1h 10m
2026-07-02 VOI5587 CUN → MTY Jul 2, 20:00 UTCJul 2, 22:10 UTC2h 10m
2026-07-02 VOI5586 MTY → CUN Jul 2, 16:55 UTCJul 2, 18:55 UTC2h 0m
2026-07-02 VOI5617 MEX → MTY Jul 2, 14:50 UTCJul 2, 15:55 UTC1h 5m
2026-07-02 VOI301 - Jul 2, 05:40 UTCJul 2, 05:50 UTC10m
2026-07-02 VOI300 - Jul 2, 01:30 UTCJul 2, 01:45 UTC15m
2026-07-01 VOI471 - Jul 1, 23:15 UTCJul 2, 00:00 UTC45m
2026-07-01 VOI470 - Jul 1, 20:45 UTCJul 1, 21:10 UTC25m
2026-06-29 VOI145 - Jun 29, 01:25 UTCJun 29, 02:09 UTC45m
2026-06-27 VOI1271 - Jun 27, 21:29 UTCJun 28, 00:45 UTC3h 15m
2026-06-27 VOI3577 - Jun 27, 14:25 UTCJun 27, 20:24 UTC6h 0m
2026-06-27 VOI249 - Jun 27, 03:55 UTCJun 27, 04:19 UTC25m
2026-06-27 VOI249 - Jun 27, 02:55 UTCJun 27, 03:25 UTC30m
2026-06-26 VOI3502 CUN → MTY Jun 26, 20:40 UTCJun 27, 01:54 UTC5h 15m

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-VVC page for operator, model, and routing details .

Mode-S 0D10BD frequently asked

What is Mode-S code 0D10BD?
0D10BD is an ICAO 24-bit transponder address. Allocated to Mexico. Assigned to XA-VVC.
Where is Mode-S 0D10BD registered?
Mode-S code 0D10BD is allocated to Mexico (MX). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0D10BD broadcasting right now?
No active broadcast right now. Last signal was 11h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0D10BD, octal 03210275, decimal 856,253.
What flights does 0D10BD operate?
Mode-S 0D10BD has broadcast 20 distinct callsigns, including VOI380, VOI381, VOI3268, VOI3257, VOI243.