sensors Mode-S transponder
0D074B
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-FLY · EMBRAER EMB-135 Legacy
- Hex
- 0D074B
- Octal
- 03203513
- Decimal
- 853,835
- Country
- MX
- Tail
- XA-FLY
- Type
- E35L
- Flights observed
- 54
- Distinct callsigns
- 1
- Country
- MX
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 0D074B 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 |
|---|---|---|---|
| XAFLY | - | 54 | 2026-05-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | XAFLY | - | May 30, 00:40 UTC | May 30, 01:50 UTC | 1h 10m |
| 2026-05-28 | XAFLY | - | May 28, 15:40 UTC | May 28, 22:10 UTC | 6h 30m |
| 2026-05-25 | XAFLY | - | May 25, 18:35 UTC | May 25, 20:24 UTC | 1h 49m |
| 2026-05-24 | XAFLY | - | May 24, 23:30 UTC | May 24, 23:46 UTC | 16m |
| 2026-05-23 | XAFLY | - | May 23, 22:05 UTC | May 24, 00:00 UTC | 1h 55m |
| 2026-05-21 | XAFLY | - | May 21, 20:10 UTC | May 21, 22:10 UTC | 2h 0m |
| 2026-05-17 | XAFLY | - | May 17, 21:40 UTC | May 17, 22:45 UTC | 1h 5m |
| 2026-05-14 | XAFLY | - | May 14, 23:50 UTC | May 15, 01:00 UTC | 1h 10m |
| 2026-05-10 | XAFLY | - | May 10, 17:45 UTC | May 10, 17:55 UTC | 10m |
| 2026-05-10 | XAFLY | - | May 10, 16:30 UTC | May 10, 16:44 UTC | 15m |
| 2026-05-10 | XAFLY | - | May 10, 14:14 UTC | May 10, 14:40 UTC | 25m |
| 2026-05-09 | XAFLY | - | May 9, 04:55 UTC | May 9, 05:20 UTC | 25m |
| 2026-05-07 | XAFLY | - | May 7, 02:00 UTC | May 7, 03:15 UTC | 1h 15m |
| 2026-05-05 | XAFLY | - | May 5, 18:40 UTC | May 5, 20:25 UTC | 1h 45m |
| 2026-05-04 | XAFLY | - | May 4, 18:40 UTC | May 4, 18:55 UTC | 15m |
| 2026-05-04 | XAFLY | - | May 4, 16:05 UTC | May 4, 16:20 UTC | 15m |
| 2026-05-03 | XAFLY | - | May 3, 02:10 UTC | May 3, 03:25 UTC | 1h 15m |
| 2026-05-02 | XAFLY | - | May 2, 23:40 UTC | May 3, 01:10 UTC | 1h 30m |
| 2026-05-02 | XAFLY | - | May 2, 22:10 UTC | May 2, 22:40 UTC | 30m |
| 2026-05-02 | XAFLY | - | May 2, 02:00 UTC | May 2, 02:10 UTC | 10m |
| 2026-05-02 | XAFLY | - | May 2, 00:10 UTC | May 2, 00:20 UTC | 10m |
| 2026-04-27 | XAFLY | - | Apr 27, 09:00 UTC | Apr 27, 09:15 UTC | 15m |
| 2026-04-27 | XAFLY | - | Apr 27, 08:15 UTC | Apr 27, 08:55 UTC | 40m |
| 2026-04-26 | XAFLY | - | Apr 26, 22:00 UTC | Apr 26, 22:10 UTC | 10m |
| 2026-04-26 | XAFLY | - | Apr 26, 19:05 UTC | Apr 26, 19:15 UTC | 10m |
| 2026-04-23 | XAFLY | - | Apr 23, 20:55 UTC | Apr 23, 21:55 UTC | 1h 0m |
| 2026-04-23 | XAFLY | - | Apr 23, 18:20 UTC | Apr 23, 18:30 UTC | 10m |
| 2026-04-23 | XAFLY | - | Apr 23, 12:10 UTC | Apr 23, 16:05 UTC | 3h 55m |
| 2026-04-23 | XAFLY | - | Apr 23, 11:20 UTC | Apr 23, 11:30 UTC | 10m |
| 2026-04-22 | XAFLY | - | Apr 22, 23:10 UTC | Apr 23, 00:35 UTC | 1h 25m |
| 2026-04-22 | XAFLY | - | Apr 22, 14:10 UTC | Apr 22, 15:15 UTC | 1h 5m |
| 2026-04-21 | XAFLY | - | Apr 21, 18:50 UTC | Apr 21, 20:30 UTC | 1h 40m |
| 2026-04-21 | XAFLY | - | Apr 21, 16:40 UTC | Apr 21, 17:40 UTC | 1h 0m |
| 2026-04-20 | XAFLY | - | Apr 20, 16:35 UTC | Apr 20, 17:00 UTC | 25m |
| 2026-04-20 | XAFLY | - | Apr 20, 12:30 UTC | Apr 20, 14:05 UTC | 1h 35m |
| 2026-04-20 | XAFLY | - | Apr 20, 02:20 UTC | Apr 20, 04:45 UTC | 2h 25m |
| 2026-04-19 | XAFLY | - | Apr 19, 22:40 UTC | Apr 20, 00:25 UTC | 1h 45m |
| 2026-04-19 | XAFLY | - | Apr 19, 20:00 UTC | Apr 19, 21:45 UTC | 1h 45m |
| 2026-04-18 | XAFLY | - | Apr 18, 03:25 UTC | Apr 18, 04:05 UTC | 40m |
| 2026-04-18 | XAFLY | - | Apr 18, 03:00 UTC | Apr 18, 03:20 UTC | 20m |
| 2026-04-18 | XAFLY | - | Apr 18, 01:30 UTC | Apr 18, 02:10 UTC | 40m |
| 2026-04-17 | XAFLY | - | Apr 17, 23:30 UTC | Apr 18, 00:55 UTC | 1h 25m |
| 2026-04-17 | XAFLY | - | Apr 17, 19:25 UTC | Apr 17, 20:20 UTC | 55m |
| 2026-04-17 | XAFLY | - | Apr 17, 19:05 UTC | Apr 17, 19:20 UTC | 15m |
| 2026-04-17 | XAFLY | - | Apr 17, 14:50 UTC | Apr 17, 15:15 UTC | 24m |
| 2026-04-16 | XAFLY | - | Apr 16, 03:09 UTC | Apr 16, 04:54 UTC | 1h 45m |
| 2026-04-16 | XAFLY | - | Apr 16, 02:54 UTC | Apr 16, 03:04 UTC | 10m |
| 2026-04-15 | XAFLY | - | Apr 15, 19:05 UTC | Apr 15, 19:30 UTC | 25m |
| 2026-04-15 | XAFLY | - | Apr 15, 17:45 UTC | Apr 15, 19:00 UTC | 1h 15m |
| 2026-04-13 | XAFLY | - | Apr 13, 19:50 UTC | Apr 13, 21:15 UTC | 1h 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-FLY page for operator, model, and routing details .