Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

0D0FC0

ICAO 24-bit transponder address · allocated to Mexico

Currently assigned to XA-VGY

Hex
0D0FC0
Octal
03207700
Decimal
856,000
Country
MX
Tail
XA-VGY
Type
B734
No current signal · last broadcast Jul 26, 15:05 UTC
Flights observed
87
Distinct callsigns
14
Country
MX
Last broadcast
Jul 26, 15:05 UTC

Last known position

Most recent position reported by Mode-S 0D0FC0.

Country allocation

The ICAO 24-bit address 0D0FC0 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 14 distinct

Callsign Airline Flights Last seen
VTM5001 - 23 2026-07-24
VTM5002 - 12 2026-07-21
VTM9902 - 11 2026-07-25
VTM9901 - 8 2026-07-26
VTM4401 - 7 2026-06-20
VTM4402 - 6 2026-07-26
VTM6602 - 4 2026-07-19
VTM1102 - 4 2026-06-17
VTM8802 - 3 2026-06-05
VTM8801 - 3 2026-06-09
VTM848 - 2 2026-06-09
VTM1101 - 2 2026-06-18
VTM2203 - 1 2026-06-02
VTM2022 - 1 2026-06-03

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 VTM4402 - Jul 26, 04:15 UTCJul 26, 15:05 UTC10h 51m
2026-07-26 VTM9901 - Jul 26, 01:40 UTCJul 26, 02:00 UTC20m
2026-07-25 VTM9902 - Jul 25, 12:30 UTCJul 25, 12:55 UTC25m
2026-07-25 VTM9902 - Jul 25, 04:50 UTCJul 25, 11:00 UTC6h 10m
2026-07-24 VTM5001 - Jul 24, 11:50 UTCJul 25, 03:35 UTC15h 45m
2026-07-24 VTM5001 MTY → MTY Jul 24, 04:30 UTCJul 25, 03:35 UTC23h 5m
2026-07-23 VTM5001 - Jul 23, 11:45 UTCJul 24, 03:30 UTC15h 45m
2026-07-23 VTM5001 MTY → MTY Jul 23, 05:10 UTCJul 24, 03:30 UTC22h 20m
2026-07-22 VTM5001 - Jul 22, 12:30 UTCJul 23, 03:50 UTC15h 20m
2026-07-22 VTM5001 - Jul 22, 04:40 UTCJul 23, 03:50 UTC23h 10m
2026-07-22 VTM5001 - Jul 22, 03:05 UTCJul 22, 03:40 UTC35m
2026-07-21 VTM5002 - Jul 21, 04:45 UTCJul 21, 12:45 UTC8h 0m
2026-07-21 VTM5001 - Jul 21, 03:00 UTCJul 21, 03:40 UTC40m
2026-07-20 VTM5002 - Jul 20, 12:50 UTCJul 20, 13:00 UTC10m
2026-07-20 VTM5002 - Jul 20, 11:50 UTCJul 20, 12:15 UTC25m
2026-07-19 VTM6602 - Jul 19, 13:25 UTCJul 20, 12:00 UTC22h 35m
2026-07-19 VTM6602 - Jul 19, 12:20 UTCJul 19, 12:30 UTC10m
2026-07-19 VTM9901 - Jul 19, 04:00 UTCJul 19, 04:40 UTC40m
2026-07-19 VTM9901 - Jul 19, 01:50 UTCJul 19, 02:15 UTC25m
2026-07-18 VTM9902 - Jul 18, 12:25 UTCJul 18, 12:50 UTC25m
2026-07-18 VTM9902 - Jul 18, 04:30 UTCJul 18, 10:55 UTC6h 25m
2026-07-17 VTM5001 - Jul 17, 11:45 UTCJul 18, 03:50 UTC16h 6m
2026-07-17 VTM5001 - Jul 17, 04:25 UTCJul 18, 03:50 UTC23h 26m
2026-07-16 VTM5001 - Jul 16, 11:45 UTCJul 17, 03:30 UTC15h 45m
2026-07-16 VTM5001 MTY → MTY Jul 16, 04:30 UTCJul 17, 03:30 UTC23h 0m
2026-07-15 VTM5001 - Jul 15, 11:50 UTCJul 16, 03:40 UTC15h 50m
2026-07-15 VTM5002 MTY → MTY Jul 15, 04:30 UTCJul 16, 03:40 UTC23h 10m
2026-07-14 VTM5002 - Jul 14, 12:00 UTCJul 15, 03:50 UTC15h 49m
2026-07-12 VTM5002 - Jul 12, 04:10 UTCJul 12, 04:30 UTC20m
2026-07-11 VTM5002 - Jul 11, 11:55 UTCJul 12, 03:35 UTC15h 40m
2026-07-11 VTM5002 - Jul 11, 04:55 UTCJul 12, 03:35 UTC22h 40m
2026-07-10 VTM5001 - Jul 10, 11:55 UTCJul 11, 04:05 UTC16h 10m
2026-07-10 VTM9901 - Jul 10, 01:40 UTCJul 10, 02:00 UTC20m
2026-07-09 VTM9902 - Jul 9, 13:35 UTCJul 9, 14:05 UTC30m
2026-07-09 VTM9902 - Jul 9, 04:30 UTCJul 9, 12:10 UTC7h 40m
2026-07-08 VTM5001 - Jul 8, 12:15 UTCJul 9, 03:45 UTC15h 30m
2026-07-08 VTM5001 MTY → MTY Jul 8, 04:40 UTCJul 9, 03:45 UTC23h 5m
2026-07-07 VTM5001 - Jul 7, 12:50 UTCJul 8, 03:45 UTC14h 55m
2026-07-01 VTM9901 - Jul 1, 04:20 UTCJul 1, 04:50 UTC30m
2026-07-01 VTM9901 - Jul 1, 01:35 UTCJul 1, 02:00 UTC25m
2026-06-30 VTM9902 - Jun 30, 13:10 UTCJun 30, 13:35 UTC25m
2026-06-30 VTM9902 - Jun 30, 10:55 UTCJun 30, 11:40 UTC45m
2026-06-27 VTM6602 - Jun 27, 13:24 UTCJun 27, 13:44 UTC20m
2026-06-27 VTM5001 MTY → HMO Jun 27, 04:59 UTCJun 27, 12:50 UTC7h 50m
2026-06-27 VTM5001 - Jun 27, 03:34 UTCJun 27, 04:09 UTC35m
2026-06-26 VTM5002 - Jun 26, 13:49 UTCJun 26, 14:09 UTC20m
2026-06-26 VTM9901 - Jun 26, 04:10 UTCJun 26, 13:04 UTC8h 55m
2026-06-26 VTM9901 - Jun 26, 01:39 UTCJun 26, 02:00 UTC20m
2026-06-25 VTM9902 - Jun 25, 12:15 UTCJun 25, 12:40 UTC25m
2026-06-25 VTM9902 - Jun 25, 10:09 UTCJun 25, 10:45 UTC35m

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

Mode-S 0D0FC0 frequently asked

What is Mode-S code 0D0FC0?
0D0FC0 is an ICAO 24-bit transponder address. Allocated to Mexico. Assigned to XA-VGY.
Where is Mode-S 0D0FC0 registered?
Mode-S code 0D0FC0 is allocated to Mexico (MX). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0D0FC0 broadcasting right now?
No active broadcast right now. Last signal was Jul 26, 15:05 UTC.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0D0FC0, octal 03207700, decimal 856,000.
What flights does 0D0FC0 operate?
Mode-S 0D0FC0 has broadcast 14 distinct callsigns, including VTM5001, VTM5002, VTM9902, VTM9901, VTM4401.