Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

0D0FFD

ICAO 24-bit transponder address · allocated to Mexico

Currently assigned to XA-VVA · AIRBUS A-320

Hex
0D0FFD
Octal
03207775
Decimal
856,061
Country
MX
Tail
XA-VVA
Type
A320
Broadcasting now · callsign VOI3481 · 37,000 ft
Flights observed
266
Distinct callsigns
20
Country
MX
Last broadcast
19m ago

Current position

0D0FFD is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address 0D0FFD 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 - 6 2026-07-07
VOI5608 - 4 2026-07-13
VOI5584 - 4 2026-06-15
VOI441 - 4 2026-07-10
VOI381 - 4 2026-07-08
VOI3257 - 4 2026-07-07
VOI244 - 4 2026-07-11
VOI1232 Volaris 4 2026-04-30
VOI1103 Volaris 4 2026-05-31
VOI5616 - 3 2026-07-02
VOI5589 - 3 2026-07-12
VOI5588 - 3 2026-07-11
VOI5548 - 3 2026-07-11
VOI491 - 3 2026-07-06
VOI490 - 3 2026-07-06
VOI440 - 3 2026-07-09
VOI3599 - 3 2026-07-09
VOI3598 - 3 2026-07-09
VOI3577 Volaris 3 2026-05-24
VOI3317 - 3 2026-06-17

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 VOI3481 - Jul 14, 12:40 UTCJul 14, 13:15 UTC35m
2026-07-14 VOI3324 - Jul 14, 02:45 UTCJul 14, 04:05 UTC1h 20m
2026-07-13 VOI3122 - Jul 13, 19:55 UTCJul 14, 01:40 UTC5h 45m
2026-07-13 VOI5608 - Jul 13, 16:25 UTCJul 13, 18:50 UTC2h 25m
2026-07-13 VOI1090 MTY → MTY Jul 13, 12:00 UTCJul 13, 15:25 UTC3h 25m
2026-07-13 VOI5593 CUN → MTY Jul 13, 03:55 UTCJul 13, 05:50 UTC1h 55m
2026-07-13 VOI5592 MTY → CUN Jul 13, 00:50 UTCJul 13, 02:55 UTC2h 5m
2026-07-12 VOI5614 MTY → MTY Jul 12, 20:20 UTCJul 12, 23:40 UTC3h 20m
2026-07-12 VOI5613 MTY → MTY Jul 12, 15:55 UTCJul 12, 19:25 UTC3h 30m
2026-07-12 VOI5552 MTY → MTY Jul 12, 12:15 UTCJul 12, 15:01 UTC2h 45m
2026-07-12 VOI5589 CUN → MTY Jul 12, 00:40 UTCJul 12, 02:45 UTC2h 5m
2026-07-11 VOI5588 MTY → CUN Jul 11, 21:40 UTCJul 11, 23:45 UTC2h 5m
2026-07-11 VOI5590 MTY → MTY Jul 11, 16:25 UTCJul 11, 20:45 UTC4h 20m
2026-07-11 VOI5548 MTY → MTY Jul 11, 12:20 UTCJul 11, 15:25 UTC3h 5m
2026-07-11 VOI244 MEX → MTY Jul 11, 02:35 UTCJul 11, 03:55 UTC1h 20m
2026-07-10 VOI247 MTY → MEX Jul 10, 22:05 UTCJul 10, 23:40 UTC1h 35m
2026-07-10 VOI5591 MTY → MTY Jul 10, 16:30 UTCJul 10, 20:45 UTC4h 15m
2026-07-10 VOI5548 MTY → MTY Jul 10, 12:20 UTCJul 10, 15:35 UTC3h 15m
2026-07-10 VOI248 - Jul 10, 04:10 UTCJul 10, 05:10 UTC1h 0m
2026-07-10 VOI441 - Jul 10, 02:05 UTCJul 10, 02:35 UTC30m
2026-07-09 VOI1243 - Jul 9, 20:55 UTCJul 9, 23:55 UTC3h 0m
2026-07-09 VOI3598 - Jul 9, 17:55 UTCJul 9, 19:10 UTC1h 15m
2026-07-09 VOI3599 - Jul 9, 15:15 UTCJul 9, 16:45 UTC1h 30m
2026-07-09 VOI440 - Jul 9, 13:35 UTCJul 9, 14:05 UTC30m
2026-07-08 VOI381 - Jul 8, 03:20 UTCJul 8, 03:30 UTC10m
2026-07-08 VOI381 - Jul 8, 01:25 UTCJul 8, 01:45 UTC20m
2026-07-07 VOI3182 - Jul 7, 22:50 UTCJul 7, 23:55 UTC1h 5m
2026-07-07 VOI3257 - Jul 7, 18:00 UTCJul 7, 22:00 UTC4h 0m
2026-07-07 VOI3183 - Jul 7, 15:55 UTCJul 7, 17:00 UTC1h 5m
2026-07-07 VOI380 - Jul 7, 14:45 UTCJul 7, 15:00 UTC15m
2026-07-07 VOI380 - Jul 7, 12:40 UTCJul 7, 13:00 UTC20m
2026-07-06 VOI145 - Jul 6, 23:00 UTCJul 7, 02:15 UTC3h 15m
2026-07-06 VOI143 GDL → MEX Jul 6, 18:30 UTCJul 6, 21:45 UTC3h 15m
2026-07-06 VOI491 - Jul 6, 16:45 UTCJul 6, 17:00 UTC15m
2026-07-06 VOI490 - Jul 6, 12:30 UTCJul 6, 12:55 UTC25m
2026-07-05 VOI249 MTY → MEX Jul 5, 06:15 UTCJul 5, 07:20 UTC1h 5m
2026-07-05 VOI5589 CUN → MTY Jul 5, 00:50 UTCJul 5, 03:10 UTC2h 20m
2026-07-04 VOI5588 MTY → CUN Jul 4, 21:50 UTCJul 4, 23:45 UTC1h 55m
2026-07-04 VOI5585 CUN → MTY Jul 4, 16:25 UTCJul 4, 18:35 UTC2h 10m
2026-07-04 VOI110 MEX → CUN Jul 4, 03:40 UTCJul 4, 05:30 UTC1h 50m
2026-07-03 VOI491 AZP → MEX Jul 3, 17:30 UTCJul 3, 17:40 UTC10m
2026-07-03 VOI490 - Jul 3, 13:25 UTCJul 3, 13:40 UTC15m
2026-07-03 VOI371 - Jul 3, 00:55 UTCJul 3, 01:40 UTC45m
2026-07-02 VOI3268 - Jul 2, 20:30 UTCJul 2, 23:30 UTC3h 0m
2026-07-02 VOI3269 - Jul 2, 16:15 UTCJul 2, 19:25 UTC3h 10m
2026-07-02 VOI370 - Jul 2, 14:40 UTCJul 2, 15:10 UTC30m
2026-07-02 VOI5616 - Jul 2, 13:30 UTCJul 2, 13:40 UTC10m
2026-07-02 VOI5616 - Jul 2, 12:30 UTCJul 2, 13:00 UTC30m
2026-07-02 VOI5611 - Jul 2, 00:10 UTCJul 2, 02:35 UTC2h 25m
2026-07-01 VOI3257 - Jul 1, 18:00 UTCJul 1, 22:15 UTC4h 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-VVA page for operator, model, and routing details .

Mode-S 0D0FFD frequently asked

What is Mode-S code 0D0FFD?
0D0FFD is an ICAO 24-bit transponder address. Allocated to Mexico. Assigned to XA-VVA.
Where is Mode-S 0D0FFD registered?
Mode-S code 0D0FFD is allocated to Mexico (MX). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0D0FFD broadcasting right now?
Yes. Mode-S 0D0FFD is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0D0FFD, octal 03207775, decimal 856,061.
What flights does 0D0FFD operate?
Mode-S 0D0FFD has broadcast 20 distinct callsigns, including VOI380, VOI5608, VOI5584, VOI441, VOI381.