Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

0D0B14

ICAO 24-bit transponder address · allocated to Mexico

Currently assigned to XA-VAD · BOMBARDIER Regional Jet CRJ-200

Hex
0D0B14
Octal
03205424
Decimal
854,804
Country
MX
Tail
XA-VAD
Type
CRJ2
No current signal · last broadcast 1d ago
Flights observed
97
Distinct callsigns
1
Country
MX
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S 0D0B14.

Country allocation

The ICAO 24-bit address 0D0B14 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
VTM392 - 97 2026-07-16

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-16 VTM392 - Jul 16, 18:44 UTCJul 16, 20:09 UTC1h 25m
2026-06-21 VTM392 - Jun 21, 21:19 UTCJun 21, 22:44 UTC1h 25m
2026-06-21 VTM392 - Jun 21, 19:05 UTCJun 21, 20:40 UTC1h 35m
2026-06-21 VTM392 LRD → CLU Jun 21, 04:34 UTCJun 21, 07:04 UTC2h 30m
2026-06-21 VTM392 - Jun 21, 01:45 UTCJun 21, 03:05 UTC1h 20m
2026-06-20 VTM392 - Jun 20, 22:45 UTCJun 20, 23:34 UTC50m
2026-06-20 VTM392 - Jun 20, 12:24 UTCJun 20, 15:54 UTC3h 30m
2026-06-20 VTM392 - Jun 20, 08:55 UTCJun 20, 11:14 UTC2h 20m
2026-06-20 VTM392 - Jun 20, 06:45 UTCJun 20, 07:59 UTC1h 15m
2026-06-19 VTM392 - Jun 19, 17:49 UTCJun 19, 21:39 UTC3h 50m
2026-06-18 VTM392 - Jun 18, 15:00 UTCJun 18, 18:10 UTC3h 10m
2026-06-17 VTM392 - Jun 17, 18:25 UTCJun 18, 03:55 UTC9h 30m
2026-06-17 VTM392 - Jun 17, 00:50 UTCJun 17, 03:15 UTC2h 25m
2026-06-16 VTM392 - Jun 16, 23:05 UTCJun 16, 23:40 UTC35m
2026-06-14 VTM392 - Jun 14, 19:30 UTCJun 14, 21:00 UTC1h 30m
2026-06-14 VTM392 - Jun 14, 16:20 UTCJun 14, 17:50 UTC1h 30m
2026-06-13 VTM392 - Jun 13, 02:00 UTCJun 13, 04:25 UTC2h 24m
2026-06-12 VTM392 - Jun 12, 14:20 UTCJun 13, 00:50 UTC10h 30m
2026-06-12 VTM392 - Jun 12, 11:10 UTCJun 12, 13:40 UTC2h 30m
2026-06-11 VTM392 - Jun 11, 16:40 UTCJun 11, 19:00 UTC2h 20m
2026-06-11 VTM392 - Jun 11, 14:45 UTCJun 11, 16:00 UTC1h 15m
2026-06-10 VTM392 - Jun 10, 21:25 UTCJun 11, 13:40 UTC16h 15m
2026-06-10 VTM392 - Jun 10, 02:25 UTCJun 10, 05:30 UTC3h 5m
2026-06-10 VTM392 - Jun 10, 00:25 UTCJun 10, 01:05 UTC40m
2026-06-09 VTM392 - Jun 9, 23:20 UTCJun 9, 23:30 UTC10m
2026-06-09 VTM392 - Jun 9, 17:00 UTCJun 9, 17:35 UTC35m
2026-06-07 VTM392 - Jun 7, 18:10 UTCJun 7, 19:40 UTC1h 30m
2026-06-07 VTM392 - Jun 7, 15:45 UTCJun 7, 17:05 UTC1h 20m
2026-06-06 VTM392 LRD → IND Jun 6, 21:50 UTCJun 7, 00:14 UTC2h 25m
2026-06-06 VTM392 - Jun 6, 17:10 UTCJun 6, 20:55 UTC3h 45m
2026-06-05 VTM392 - Jun 5, 16:30 UTCJun 5, 21:00 UTC4h 30m
2026-06-04 VTM392 - Jun 4, 16:05 UTCJun 4, 19:15 UTC3h 10m
2026-06-03 VTM392 - Jun 3, 22:05 UTCJun 4, 14:35 UTC16h 30m
2026-06-03 VTM392 LRD → CLE Jun 3, 05:10 UTCJun 3, 08:05 UTC2h 55m
2026-06-03 VTM392 - Jun 3, 03:10 UTCJun 3, 03:40 UTC30m
2026-06-01 VTM392 - Jun 1, 22:55 UTCJun 1, 23:25 UTC30m
2026-05-30 VTM392 - May 30, 16:50 UTCMay 30, 20:25 UTC3h 35m
2026-05-29 VTM392 - May 29, 07:10 UTCMay 29, 09:25 UTC2h 15m
2026-05-29 VTM392 LRD → SHV May 29, 05:15 UTCMay 29, 06:20 UTC1h 5m
2026-05-29 VTM392 - May 29, 00:40 UTCMay 29, 04:05 UTC3h 25m
2026-05-28 VTM392 - May 28, 05:50 UTCMay 28, 08:10 UTC2h 20m
2026-05-28 VTM392 LRD → SDF May 28, 02:15 UTCMay 28, 04:35 UTC2h 20m
2026-05-27 VTM392 - May 27, 18:35 UTCMay 28, 00:05 UTC5h 30m
2026-05-26 VTM392 - May 26, 20:54 UTCMay 26, 22:59 UTC2h 5m
2026-05-26 VTM392 - May 26, 14:50 UTCMay 26, 17:55 UTC3h 5m
2026-05-26 VTM392 - May 26, 13:10 UTCMay 26, 13:50 UTC40m
2026-05-23 VTM392 - May 23, 21:20 UTCMay 23, 22:50 UTC1h 30m
2026-05-23 VTM392 - May 23, 17:55 UTCMay 23, 20:30 UTC2h 36m
2026-05-22 VTM392 - May 22, 23:50 UTCMay 23, 03:00 UTC3h 10m
2026-05-21 VTM392 - May 21, 23:20 UTCMay 22, 01:45 UTC2h 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-VAD page for operator, model, and routing details .

Mode-S 0D0B14 frequently asked

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