Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

0D0AF2

ICAO 24-bit transponder address · allocated to Mexico

Currently assigned to XA-UZV · MCDONNELL-DOUGLAS MD-83

Hex
0D0AF2
Octal
03205362
Decimal
854,770
Country
MX
Tail
XA-UZV
Type
MD83
No current signal · last broadcast 3d ago
Flights observed
106
Distinct callsigns
2
Country
MX
Last broadcast
3d ago

Last known position

Most recent position reported by Mode-S 0D0AF2.

Country allocation

The ICAO 24-bit address 0D0AF2 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 2 distinct

Callsign Airline Flights Last seen
VTM288 - 105 2026-07-24
VTM990 - 1 2026-06-05

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-24 VTM288 - Jul 24, 18:20 UTCJul 24, 18:40 UTC20m
2026-07-24 VTM288 - Jul 24, 13:55 UTCJul 24, 15:20 UTC1h 25m
2026-07-24 VTM288 TOL → SHV Jul 24, 10:35 UTCJul 24, 12:25 UTC1h 50m
2026-07-23 VTM288 LRD → TOL Jul 23, 20:00 UTCJul 23, 22:50 UTC2h 50m
2026-07-23 VTM288 - Jul 23, 16:45 UTCJul 23, 17:30 UTC45m
2026-07-20 VTM288 - Jul 20, 14:30 UTCJul 20, 15:00 UTC30m
2026-07-19 VTM288 - Jul 19, 23:50 UTCJul 20, 00:20 UTC30m
2026-07-09 VTM288 - Jul 9, 14:15 UTCJul 9, 15:35 UTC1h 20m
2026-07-09 VTM288 TOL → SHV Jul 9, 11:05 UTCJul 9, 13:00 UTC1h 55m
2026-07-08 VTM288 LRD → TOL Jul 8, 17:30 UTCJul 8, 20:25 UTC2h 55m
2026-07-08 VTM288 - Jul 8, 15:45 UTCJul 8, 16:20 UTC35m
2026-07-02 VTM288 - Jul 2, 18:45 UTCJul 2, 20:00 UTC1h 15m
2026-07-02 VTM288 LRD → AFW Jul 2, 01:40 UTCJul 2, 02:45 UTC1h 5m
2026-07-01 VTM288 - Jul 1, 23:50 UTCJul 2, 00:20 UTC30m
2026-07-01 VTM288 - Jul 1, 18:35 UTCJul 1, 23:05 UTC4h 30m
2026-06-30 VTM288 - Jun 30, 18:30 UTCJun 30, 19:45 UTC1h 15m
2026-06-29 VTM288 LRD → AFW Jun 29, 23:09 UTCJun 30, 00:14 UTC1h 5m
2026-06-29 VTM288 - Jun 29, 21:34 UTCJun 29, 22:05 UTC30m
2026-06-29 VTM288 - Jun 29, 14:39 UTCJun 29, 14:50 UTC10m
2026-06-28 VTM288 - Jun 28, 07:20 UTCJun 28, 13:25 UTC6h 5m
2026-06-26 VTM288 - Jun 26, 13:49 UTCJun 26, 19:24 UTC5h 35m
2026-06-26 VTM288 - Jun 26, 10:15 UTCJun 26, 12:05 UTC1h 50m
2026-06-25 VTM288 LRD → TOL Jun 25, 21:29 UTCJun 26, 00:15 UTC2h 45m
2026-06-25 VTM288 - Jun 25, 19:39 UTCJun 25, 20:09 UTC30m
2026-06-18 VTM288 - Jun 18, 22:20 UTCJun 18, 23:30 UTC1h 10m
2026-06-18 VTM288 - Jun 18, 06:35 UTCJun 18, 07:35 UTC1h 0m
2026-06-18 VTM288 - Jun 18, 04:35 UTCJun 18, 05:10 UTC35m
2026-06-18 VTM288 - Jun 18, 00:05 UTCJun 18, 03:55 UTC3h 50m
2026-06-16 VTM288 - Jun 16, 20:15 UTCJun 16, 20:35 UTC20m
2026-06-16 VTM288 - Jun 16, 17:59 UTCJun 16, 19:40 UTC1h 40m
2026-06-15 VTM288 - Jun 15, 22:35 UTCJun 16, 19:40 UTC21h 5m
2026-06-15 VTM288 - Jun 15, 21:04 UTCJun 16, 19:40 UTC22h 35m
2026-06-15 VTM288 - Jun 15, 16:04 UTCJun 15, 22:49 UTC6h 45m
2026-06-15 VTM288 - Jun 15, 10:55 UTCJun 15, 14:55 UTC4h 0m
2026-06-15 VTM288 - Jun 15, 07:00 UTCJun 15, 07:15 UTC15m
2026-06-13 VTM288 LRD → YQG Jun 13, 05:40 UTCJun 13, 08:35 UTC2h 55m
2026-06-12 VTM288 - Jun 12, 22:55 UTCJun 13, 03:35 UTC4h 40m
2026-06-11 VTM288 - Jun 11, 21:55 UTCJun 11, 23:15 UTC1h 20m
2026-06-11 VTM288 - Jun 11, 06:35 UTCJun 11, 07:55 UTC1h 20m
2026-06-11 VTM288 LRD → CHA Jun 11, 02:30 UTCJun 11, 04:35 UTC2h 5m
2026-06-10 VTM288 - Jun 10, 21:55 UTCJun 11, 01:00 UTC3h 5m
2026-06-10 VTM288 - Jun 10, 06:55 UTCJun 10, 07:10 UTC15m
2026-06-10 VTM288 - Jun 10, 02:00 UTCJun 10, 02:10 UTC10m
2026-06-09 VTM288 - Jun 9, 22:35 UTCJun 10, 01:05 UTC2h 30m
2026-06-09 VTM288 - Jun 9, 06:05 UTCJun 9, 08:20 UTC2h 15m
2026-06-09 VTM288 - Jun 9, 02:10 UTCJun 9, 04:55 UTC2h 45m
2026-06-06 VTM288 - Jun 6, 16:10 UTCJun 6, 18:39 UTC2h 30m
2026-06-05 VTM990 LRD → CHA Jun 5, 10:30 UTCJun 5, 12:35 UTC2h 5m
2026-06-05 VTM288 - Jun 5, 06:55 UTCJun 5, 09:20 UTC2h 25m
2026-06-04 VTM288 - Jun 4, 23:05 UTCJun 5, 01:35 UTC2h 30m

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

Mode-S 0D0AF2 frequently asked

What is Mode-S code 0D0AF2?
0D0AF2 is an ICAO 24-bit transponder address. Allocated to Mexico. Assigned to XA-UZV.
Where is Mode-S 0D0AF2 registered?
Mode-S code 0D0AF2 is allocated to Mexico (MX). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0D0AF2 broadcasting right now?
No active broadcast right now. Last signal was 3d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0D0AF2, octal 03205362, decimal 854,770.
What flights does 0D0AF2 operate?
Mode-S 0D0AF2 has broadcast 2 distinct callsigns, including VTM288, VTM990.