sensors Mode-S transponder

0D09BD

ICAO 24-bit transponder address · allocated to Mexico

Currently assigned to XA-VLS · AIRBUS A-320

Hex
0D09BD
Octal
03204675
Decimal
854,461
Country
MX
Tail
XA-VLS
Type
A320
No current signal · last broadcast 7h ago
Flights observed
300
Distinct callsigns
20
Country
MX
Last broadcast
7h ago

Last known position

Most recent position reported by Mode-S 0D09BD.

Country allocation

The ICAO 24-bit address 0D09BD 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
VOI751 Volaris 5 2026-06-10
VOI750 Volaris 5 2026-06-09
VOI5615 - 5 2026-07-13
VOI248 - 4 2026-07-02
VOI1233 Volaris 4 2026-04-25
VOI901 Volaris 3 2026-05-23
VOI900 Volaris 3 2026-05-23
VOI801 - 3 2026-07-01
VOI7429 Volaris 3 2026-04-24
VOI731 Volaris 3 2026-04-13
VOI7113 Volaris 3 2026-05-05
VOI7110 Volaris 3 2026-05-05
VOI491 Volaris 3 2026-06-19
VOI490 Volaris 3 2026-06-19
VOI3519 - 3 2026-07-12
VOI3518 - 3 2026-07-13
VOI3483 - 3 2026-06-26
VOI1750 Volaris 3 2026-04-28
VOI1721 Volaris 3 2026-04-20
VOI1231 Volaris 3 2026-05-11

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 VOI1051 - Jul 14, 03:50 UTCJul 14, 05:40 UTC1h 50m
2026-07-14 VOI5592 MTY → CUN Jul 14, 00:35 UTCJul 14, 02:35 UTC2h 0m
2026-07-13 VOI5615 - Jul 13, 20:20 UTCJul 13, 23:40 UTC3h 20m
2026-07-13 VOI5613 MTY → MTY Jul 13, 16:05 UTCJul 13, 19:15 UTC3h 10m
2026-07-13 VOI3518 - Jul 13, 00:55 UTCJul 13, 15:05 UTC14h 10m
2026-07-12 VOI3519 - Jul 12, 16:25 UTCJul 12, 22:05 UTC5h 40m
2026-07-11 VOI3518 - Jul 11, 23:30 UTCJul 12, 15:01 UTC15h 30m
2026-07-11 VOI3519 - Jul 11, 16:25 UTCJul 11, 22:20 UTC5h 55m
2026-07-11 VOI3352 - Jul 11, 04:50 UTCJul 11, 15:05 UTC10h 15m
2026-07-10 VOI525 MCO → MTY Jul 10, 19:15 UTCJul 11, 02:20 UTC7h 5m
2026-07-10 VOI524 QRO → MCO Jul 10, 01:30 UTCJul 10, 17:15 UTC15h 45m
2026-07-09 VOI816 - Jul 9, 18:05 UTCJul 9, 23:20 UTC5h 15m
2026-07-09 VOI537 VER → QRO Jul 9, 14:25 UTCJul 9, 17:00 UTC2h 35m
2026-07-09 VOI3518 CUN → VER Jul 9, 00:35 UTCJul 9, 13:35 UTC13h 0m
2026-07-08 VOI3519 CUN → CUN Jul 8, 18:35 UTCJul 8, 23:35 UTC5h 0m
2026-07-08 VOI3515 - Jul 8, 16:35 UTCJul 8, 17:00 UTC25m
2026-07-08 VOI5657 - Jul 8, 01:35 UTCJul 8, 15:55 UTC14h 20m
2026-07-07 VOI3388 - Jul 7, 21:00 UTCJul 8, 00:35 UTC3h 35m
2026-07-07 VOI1012 - Jul 7, 13:25 UTCJul 7, 19:55 UTC6h 30m
2026-07-06 VOI1008 - Jul 6, 21:00 UTCJul 7, 03:45 UTC6h 45m
2026-07-06 VOI3210 - Jul 6, 09:15 UTCJul 6, 15:00 UTC5h 45m
2026-07-06 VOI3241 - Jul 6, 00:10 UTCJul 6, 07:40 UTC7h 30m
2026-07-05 VOI3221 - Jul 5, 19:45 UTCJul 5, 23:15 UTC3h 30m
2026-07-05 VOI3552 CUN → PBC Jul 5, 17:00 UTCJul 5, 18:50 UTC1h 50m
2026-07-05 VOI3553 - Jul 5, 14:05 UTCJul 5, 15:45 UTC1h 40m
2026-07-05 VOI3220 - Jul 5, 10:00 UTCJul 5, 13:05 UTC3h 5m
2026-07-05 VOI3317 - Jul 5, 04:30 UTCJul 5, 05:45 UTC1h 15m
2026-07-05 VOI3316 - Jul 5, 02:15 UTCJul 5, 03:15 UTC1h 0m
2026-07-04 VOI3143 - Jul 4, 22:00 UTCJul 5, 01:20 UTC3h 20m
2026-07-04 VOI3140 - Jul 4, 17:25 UTCJul 4, 20:40 UTC3h 15m
2026-07-04 VOI7945 - Jul 4, 08:55 UTCJul 4, 16:30 UTC7h 35m
2026-07-03 VOI7944 MTY → SMF Jul 3, 23:30 UTCJul 4, 05:50 UTC6h 20m
2026-07-03 VOI5609 - Jul 3, 20:00 UTCJul 3, 22:25 UTC2h 25m
2026-07-03 VOI5608 - Jul 3, 16:20 UTCJul 3, 18:55 UTC2h 35m
2026-07-03 VOI1091 MTY → MTY Jul 3, 12:05 UTCJul 3, 15:20 UTC3h 15m
2026-07-03 VOI5593 CUN → MTY Jul 3, 03:25 UTCJul 3, 05:30 UTC2h 5m
2026-07-03 VOI5592 MTY → CUN Jul 3, 00:20 UTCJul 3, 02:20 UTC2h 0m
2026-07-02 VOI5615 - Jul 2, 20:00 UTCJul 2, 23:30 UTC3h 30m
2026-07-02 VOI5613 MTY → MTY Jul 2, 15:50 UTCJul 2, 19:10 UTC3h 20m
2026-07-02 VOI5552 MTY → MTY Jul 2, 12:10 UTCJul 2, 15:00 UTC2h 50m
2026-07-02 VOI248 - Jul 2, 04:25 UTCJul 2, 05:35 UTC1h 10m
2026-07-02 VOI145 - Jul 2, 02:55 UTCJul 2, 03:10 UTC15m
2026-07-01 VOI1091 - Jul 1, 12:05 UTCJul 1, 12:25 UTC20m
2026-07-01 VOI248 - Jul 1, 08:55 UTCJul 1, 10:10 UTC1h 15m
2026-07-01 VOI801 DFW → MEX Jul 1, 02:15 UTCJul 1, 04:20 UTC2h 5m
2026-06-30 VOI1800 - Jun 30, 17:55 UTCJun 30, 23:55 UTC6h 0m
2026-06-30 VOI800 - Jun 30, 13:50 UTCJun 30, 16:00 UTC2h 10m
2026-06-30 VOI381 - Jun 30, 03:20 UTCJun 30, 03:40 UTC20m
2026-06-30 VOI381 - Jun 30, 01:19 UTCJun 30, 01:35 UTC16m
2026-06-29 VOI3182 - Jun 29, 22:59 UTCJun 30, 00:00 UTC1h 0m

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

Mode-S 0D09BD frequently asked

What is Mode-S code 0D09BD?
0D09BD is an ICAO 24-bit transponder address. Allocated to Mexico. Assigned to XA-VLS.
Where is Mode-S 0D09BD registered?
Mode-S code 0D09BD is allocated to Mexico (MX). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0D09BD broadcasting right now?
No active broadcast right now. Last signal was 7h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0D09BD, octal 03204675, decimal 854,461.
What flights does 0D09BD operate?
Mode-S 0D09BD has broadcast 20 distinct callsigns, including VOI751, VOI750, VOI5615, VOI248, VOI1233.