sensors Mode-S transponder

0D104C

ICAO 24-bit transponder address · allocated to Mexico

Currently assigned to XA-YNZ · HAWKER BEECHCRAFT Hawker 750/850

Hex
0D104C
Octal
03210114
Decimal
856,140
Country
MX
Tail
XA-YNZ
Type
H25B
No current signal · last broadcast 10h ago
Flights observed
135
Distinct callsigns
6
Country
MX
Last broadcast
10h ago

Last known position

Most recent position reported by Mode-S 0D104C.

Country allocation

The ICAO 24-bit address 0D104C 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 6 distinct

Callsign Airline Flights Last seen
VTM7701 - 85 2026-07-17
VTM7702 - 42 2026-07-15
VTM2202 - 4 2026-04-15
VTM2203 - 2 2026-04-14
VTM7707 - 1 2026-05-13
7701 - 1 2026-05-27

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-17 VTM7701 - Jul 17, 01:45 UTCJul 17, 16:19 UTC14h 35m
2026-07-16 VTM7701 - Jul 16, 01:25 UTCJul 16, 16:25 UTC15h 0m
2026-07-15 VTM7702 - Jul 15, 01:45 UTCJul 15, 16:25 UTC14h 40m
2026-07-14 VTM7702 - Jul 14, 15:20 UTCJul 14, 16:15 UTC55m
2026-07-10 VTM7701 - Jul 10, 01:35 UTCJul 10, 02:35 UTC1h 0m
2026-07-09 VTM7701 - Jul 9, 01:25 UTCJul 9, 16:45 UTC15h 20m
2026-07-08 VTM7701 - Jul 8, 01:40 UTCJul 8, 16:20 UTC14h 40m
2026-07-07 VTM7701 - Jul 7, 02:20 UTCJul 7, 16:30 UTC14h 10m
2026-07-03 VTM7702 - Jul 3, 03:50 UTCJul 3, 16:25 UTC12h 35m
2026-07-03 VTM7701 - Jul 3, 01:35 UTCJul 3, 02:55 UTC1h 20m
2026-07-02 VTM7702 - Jul 2, 15:15 UTCJul 2, 16:40 UTC1h 25m
2026-07-02 VTM7701 - Jul 2, 03:35 UTCJul 2, 14:30 UTC10h 55m
2026-07-02 VTM7701 - Jul 2, 01:30 UTCJul 2, 02:50 UTC1h 20m
2026-07-01 VTM7702 - Jul 1, 15:30 UTCJul 1, 17:00 UTC1h 30m
2026-07-01 VTM7701 - Jul 1, 03:45 UTCJul 1, 14:40 UTC10h 55m
2026-07-01 VTM7701 - Jul 1, 01:30 UTCJul 1, 02:50 UTC1h 20m
2026-06-30 VTM7702 - Jun 30, 15:10 UTCJun 30, 16:40 UTC1h 30m
2026-06-30 VTM7701 - Jun 30, 03:30 UTCJun 30, 14:35 UTC11h 5m
2026-06-30 VTM7701 - Jun 30, 01:19 UTCJun 30, 02:45 UTC1h 26m
2026-06-26 VTM7702 - Jun 26, 14:59 UTCJun 26, 16:24 UTC1h 25m
2026-06-26 VTM7702 - Jun 26, 13:45 UTCJun 26, 14:09 UTC25m
2026-06-24 VTM7701 - Jun 24, 03:29 UTCJun 24, 04:34 UTC1h 5m
2026-06-24 VTM7701 - Jun 24, 01:19 UTCJun 24, 02:45 UTC1h 25m
2026-06-23 VTM7702 - Jun 23, 14:59 UTCJun 23, 16:20 UTC1h 20m
2026-06-23 VTM7701 - Jun 23, 03:09 UTCJun 23, 14:19 UTC11h 10m
2026-06-23 VTM7701 - Jun 23, 00:54 UTCJun 23, 02:20 UTC1h 25m
2026-06-19 VTM7701 - Jun 19, 14:49 UTCJun 19, 16:14 UTC1h 25m
2026-06-19 VTM7701 - Jun 19, 03:24 UTCJun 19, 13:59 UTC10h 35m
2026-06-19 VTM7701 - Jun 19, 00:55 UTCJun 19, 02:24 UTC1h 30m
2026-06-18 VTM7702 - Jun 18, 15:20 UTCJun 18, 16:45 UTC1h 25m
2026-06-18 VTM7701 - Jun 18, 03:10 UTCJun 18, 14:25 UTC11h 15m
2026-06-18 VTM7701 - Jun 18, 00:55 UTCJun 18, 02:15 UTC1h 20m
2026-06-17 VTM7702 - Jun 17, 15:15 UTCJun 17, 16:45 UTC1h 30m
2026-06-17 VTM7701 - Jun 17, 03:50 UTCJun 17, 14:30 UTC10h 40m
2026-06-17 VTM7701 - Jun 17, 01:25 UTCJun 17, 02:50 UTC1h 25m
2026-06-16 VTM7702 - Jun 16, 15:05 UTCJun 16, 16:30 UTC1h 25m
2026-06-16 VTM7701 - Jun 16, 03:25 UTCJun 16, 14:15 UTC10h 50m
2026-06-16 VTM7701 - Jun 16, 01:15 UTCJun 16, 02:40 UTC1h 25m
2026-06-12 VTM7702 - Jun 12, 14:50 UTCJun 12, 16:15 UTC1h 25m
2026-06-12 VTM7701 - Jun 12, 03:25 UTCJun 12, 14:01 UTC10h 35m
2026-06-12 VTM7701 - Jun 12, 01:00 UTCJun 12, 02:30 UTC1h 30m
2026-06-11 VTM7702 - Jun 11, 15:15 UTCJun 11, 16:35 UTC1h 20m
2026-06-11 VTM7701 - Jun 11, 03:30 UTCJun 11, 14:20 UTC10h 50m
2026-06-11 VTM7701 - Jun 11, 01:20 UTCJun 11, 02:50 UTC1h 30m
2026-06-10 VTM7702 - Jun 10, 15:15 UTCJun 10, 16:40 UTC1h 25m
2026-06-10 VTM7701 - Jun 10, 03:45 UTCJun 10, 14:10 UTC10h 25m
2026-06-10 VTM7701 - Jun 10, 01:40 UTCJun 10, 03:00 UTC1h 20m
2026-06-09 VTM7702 - Jun 9, 15:00 UTCJun 9, 15:50 UTC50m
2026-06-09 VTM7701 - Jun 9, 03:25 UTCJun 9, 14:15 UTC10h 50m
2026-06-09 VTM7701 - Jun 9, 01:20 UTCJun 9, 02:45 UTC1h 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-YNZ page for operator, model, and routing details .

Mode-S 0D104C frequently asked

What is Mode-S code 0D104C?
0D104C is an ICAO 24-bit transponder address. Allocated to Mexico. Assigned to XA-YNZ.
Where is Mode-S 0D104C registered?
Mode-S code 0D104C is allocated to Mexico (MX). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0D104C broadcasting right now?
No active broadcast right now. Last signal was 10h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0D104C, octal 03210114, decimal 856,140.
What flights does 0D104C operate?
Mode-S 0D104C has broadcast 6 distinct callsigns, including VTM7701, VTM7702, VTM2202, VTM2203, VTM7707.