sensors Mode-S transponder
0D0515
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-DLA · BOMBARDIER BD-100 Challenger 300
- Hex
- 0D0515
- Octal
- 03202425
- Decimal
- 853,269
- Country
- MX
- Tail
- XA-DLA
- Type
- CL30
- Flights observed
- 38
- Distinct callsigns
- 1
- Country
- MX
- Last broadcast
- Jul 26, 21:15 UTC
Last known position
Country allocation
The ICAO 24-bit address 0D0515 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 |
|---|---|---|---|
| XADLA | - | 38 | 2026-07-26 |
Recent flights last 38
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | XADLA | - | Jul 26, 20:10 UTC | Jul 26, 21:15 UTC | 1h 5m |
| 2026-07-25 | XADLA | - | Jul 25, 21:00 UTC | Jul 25, 21:55 UTC | 55m |
| 2026-07-25 | XADLA | - | Jul 25, 19:30 UTC | Jul 25, 20:15 UTC | 45m |
| 2026-07-24 | XADLA | - | Jul 24, 20:20 UTC | Jul 24, 22:25 UTC | 2h 5m |
| 2026-07-24 | XADLA | - | Jul 24, 16:40 UTC | Jul 24, 18:55 UTC | 2h 15m |
| 2026-07-24 | XADLA | - | Jul 24, 14:35 UTC | Jul 24, 15:00 UTC | 25m |
| 2026-07-20 | XADLA | - | Jul 20, 20:55 UTC | Jul 20, 21:50 UTC | 55m |
| 2026-07-20 | XADLA | - | Jul 20, 00:10 UTC | Jul 20, 01:10 UTC | 1h 0m |
| 2026-07-19 | XADLA | - | Jul 19, 00:50 UTC | Jul 19, 01:20 UTC | 30m |
| 2026-07-18 | XADLA | - | Jul 18, 23:20 UTC | Jul 18, 23:45 UTC | 25m |
| 2026-07-18 | XADLA | - | Jul 18, 01:25 UTC | Jul 18, 01:54 UTC | 30m |
| 2026-07-17 | XADLA | - | Jul 17, 22:25 UTC | Jul 18, 00:35 UTC | 2h 10m |
| 2026-07-17 | XADLA | - | Jul 17, 17:44 UTC | Jul 17, 19:45 UTC | 2h 0m |
| 2026-07-17 | XADLA | - | Jul 17, 16:04 UTC | Jul 17, 16:29 UTC | 25m |
| 2026-07-16 | XADLA | VNY → NTR | Jul 16, 00:50 UTC | Jul 16, 03:30 UTC | 2h 40m |
| 2026-07-14 | XADLA | NTR → VNY | Jul 14, 21:00 UTC | Jul 14, 23:40 UTC | 2h 39m |
| 2026-07-12 | XADLA | - | Jul 12, 18:10 UTC | Jul 12, 20:10 UTC | 2h 0m |
| 2026-07-09 | XADLA | - | Jul 9, 18:35 UTC | Jul 9, 20:20 UTC | 1h 45m |
| 2026-07-09 | XADLA | NTR → LRD | Jul 9, 17:20 UTC | Jul 9, 17:45 UTC | 25m |
| 2026-07-07 | XADLA | - | Jul 7, 22:00 UTC | Jul 7, 23:15 UTC | 1h 15m |
| 2026-07-07 | XADLA | - | Jul 7, 20:10 UTC | Jul 7, 20:35 UTC | 25m |
| 2026-06-28 | XADLA | - | Jun 28, 00:50 UTC | Jun 28, 03:00 UTC | 2h 10m |
| 2026-06-27 | XADLA | - | Jun 27, 19:34 UTC | Jun 27, 21:25 UTC | 1h 50m |
| 2026-06-27 | XADLA | NTR → LRD | Jun 27, 18:29 UTC | Jun 27, 18:54 UTC | 25m |
| 2026-06-25 | XADLA | - | Jun 25, 23:39 UTC | Jun 26, 02:00 UTC | 2h 20m |
| 2026-06-25 | XADLA | - | Jun 25, 18:00 UTC | Jun 25, 20:14 UTC | 2h 15m |
| 2026-06-23 | XADLA | NTR → NTR | Jun 23, 16:20 UTC | Jun 24, 04:30 UTC | 12h 10m |
| 2026-06-22 | XADLA | - | Jun 22, 03:10 UTC | Jun 22, 03:40 UTC | 30m |
| 2026-06-19 | XADLA | - | Jun 19, 00:10 UTC | Jun 19, 00:34 UTC | 25m |
| 2026-06-12 | XADLA | LNK → NTR | Jun 12, 20:00 UTC | Jun 12, 22:10 UTC | 2h 10m |
| 2026-05-14 | XADLA | LNK → LNK | May 14, 02:10 UTC | May 14, 02:20 UTC | 10m |
| 2026-04-28 | XADLA | LNK → LNK | Apr 28, 12:30 UTC | Apr 28, 13:20 UTC | 50m |
| 2026-04-19 | XADLA | LNK → LNK | Apr 19, 21:45 UTC | Apr 19, 22:05 UTC | 20m |
| 2026-04-13 | XADLA | - | Apr 13, 16:15 UTC | Apr 13, 18:00 UTC | 1h 45m |
| 2026-04-13 | XADLA | - | Apr 13, 16:05 UTC | Apr 13, 16:15 UTC | 10m |
| 2026-04-13 | XADLA | NTR → LRD | Apr 13, 14:35 UTC | Apr 13, 15:15 UTC | 40m |
| 2026-04-13 | XADLA | - | Apr 13, 00:20 UTC | Apr 13, 01:10 UTC | 50m |
| 2026-04-12 | XADLA | - | Apr 12, 23:55 UTC | Apr 13, 01:10 UTC | 1h 15m |
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-DLA page for operator, model, and routing details .