sensors Mode-S transponder
0D0983
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-OFM · BOMBARDIER CL-600 Challenger
- Hex
- 0D0983
- Octal
- 03204603
- Decimal
- 854,403
- Country
- MX
- Tail
- XA-OFM
- Type
- CL60
- Flights observed
- 30
- Distinct callsigns
- 1
- Country
- MX
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 0D0983 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 |
|---|---|---|---|
| XAOFM | - | 30 | 2026-07-14 |
Recent flights last 30
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | XAOFM | - | Jul 14, 21:35 UTC | Jul 14, 22:25 UTC | 50m |
| 2026-07-14 | XAOFM | - | Jul 14, 18:10 UTC | Jul 14, 19:55 UTC | 1h 45m |
| 2026-07-13 | XAOFM | - | Jul 13, 00:05 UTC | Jul 13, 04:35 UTC | 4h 30m |
| 2026-07-12 | XAOFM | - | Jul 12, 20:10 UTC | Jul 12, 22:40 UTC | 2h 30m |
| 2026-07-08 | XAOFM | - | Jul 8, 17:40 UTC | Jul 8, 20:30 UTC | 2h 50m |
| 2026-06-30 | XAOFM | - | Jun 30, 16:45 UTC | Jun 30, 19:35 UTC | 2h 50m |
| 2026-06-29 | XAOFM | - | Jun 29, 16:50 UTC | Jun 29, 17:30 UTC | 40m |
| 2026-06-29 | XAOFM | - | Jun 29, 12:29 UTC | Jun 29, 13:09 UTC | 40m |
| 2026-06-28 | XAOFM | - | Jun 28, 23:29 UTC | Jun 29, 02:25 UTC | 2h 55m |
| 2026-06-28 | XAOFM | - | Jun 28, 15:55 UTC | Jun 28, 17:39 UTC | 1h 45m |
| 2026-06-26 | XAOFM | CUN → CUN | Jun 26, 14:55 UTC | Jun 27, 06:40 UTC | 15h 45m |
| 2026-06-25 | XAOFM | - | Jun 25, 18:39 UTC | Jun 25, 20:25 UTC | 1h 45m |
| 2026-06-21 | XAOFM | - | Jun 21, 22:29 UTC | Jun 22, 01:15 UTC | 2h 45m |
| 2026-06-21 | XAOFM | - | Jun 21, 17:29 UTC | Jun 21, 20:24 UTC | 2h 55m |
| 2026-05-31 | XAOFM | - | May 31, 20:25 UTC | May 31, 21:10 UTC | 45m |
| 2026-05-28 | XAOFM | - | May 28, 23:10 UTC | May 29, 00:30 UTC | 1h 20m |
| 2026-05-22 | XAOFM | - | May 22, 00:15 UTC | May 22, 03:15 UTC | 3h 0m |
| 2026-05-21 | XAOFM | - | May 21, 18:55 UTC | May 21, 21:40 UTC | 2h 45m |
| 2026-05-13 | XAOFM | - | May 13, 18:15 UTC | May 13, 20:25 UTC | 2h 10m |
| 2026-05-11 | XAOFM | - | May 11, 18:35 UTC | May 11, 19:10 UTC | 35m |
| 2026-05-08 | XAOFM | - | May 8, 18:10 UTC | May 8, 18:40 UTC | 30m |
| 2026-05-04 | XAOFM | - | May 4, 21:55 UTC | May 4, 22:15 UTC | 20m |
| 2026-05-04 | XAOFM | - | May 4, 19:50 UTC | May 4, 20:10 UTC | 20m |
| 2026-04-20 | XAOFM | - | Apr 20, 00:05 UTC | Apr 20, 01:55 UTC | 1h 50m |
| 2026-04-19 | XAOFM | - | Apr 19, 20:20 UTC | Apr 19, 22:20 UTC | 1h 59m |
| 2026-04-18 | XAOFM | - | Apr 18, 12:10 UTC | Apr 18, 13:30 UTC | 1h 20m |
| 2026-04-17 | XAOFM | - | Apr 17, 23:25 UTC | Apr 18, 00:00 UTC | 35m |
| 2026-04-17 | XAOFM | - | Apr 17, 22:45 UTC | Apr 17, 23:20 UTC | 35m |
| 2026-04-13 | XAOFM | - | Apr 13, 00:20 UTC | Apr 13, 00:40 UTC | 20m |
| 2026-04-12 | XAOFM | - | Apr 12, 23:55 UTC | Apr 13, 00:40 UTC | 45m |
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-OFM page for operator, model, and routing details .