sensors Mode-S transponder
0D0841
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-FSA · HAWKER BEECHCRAFT Hawker 750/850
- Hex
- 0D0841
- Octal
- 03204101
- Decimal
- 854,081
- Country
- MX
- Tail
- XA-FSA
- Type
- H25B
- Flights observed
- 76
- Distinct callsigns
- 2
- Country
- MX
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 0D0841 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | XAFSA | - | Jul 17, 23:35 UTC | Jul 18, 00:04 UTC | 30m |
| 2026-07-17 | XAFSA | - | Jul 17, 20:44 UTC | Jul 17, 21:10 UTC | 25m |
| 2026-07-17 | XAFSA | - | Jul 17, 19:05 UTC | Jul 17, 19:40 UTC | 35m |
| 2026-07-17 | XAFSA | - | Jul 17, 17:15 UTC | Jul 17, 17:44 UTC | 30m |
| 2026-07-17 | XAFSA | - | Jul 17, 15:55 UTC | Jul 17, 16:24 UTC | 30m |
| 2026-07-17 | XAFSA | - | Jul 17, 14:24 UTC | Jul 17, 14:50 UTC | 25m |
| 2026-07-11 | XAFSA | - | Jul 11, 03:10 UTC | Jul 11, 05:15 UTC | 2h 5m |
| 2026-07-10 | XAFSA | - | Jul 10, 22:45 UTC | Jul 11, 01:05 UTC | 2h 20m |
| 2026-07-10 | XAFSA | - | Jul 10, 19:10 UTC | Jul 10, 21:20 UTC | 2h 10m |
| 2026-07-10 | XAFSA | - | Jul 10, 15:00 UTC | Jul 10, 17:20 UTC | 2h 20m |
| 2026-07-09 | XAFSA | - | Jul 9, 23:15 UTC | Jul 10, 00:40 UTC | 1h 25m |
| 2026-07-08 | XAFSA | - | Jul 8, 14:00 UTC | Jul 8, 14:30 UTC | 30m |
| 2026-07-06 | XAFSA | - | Jul 6, 22:30 UTC | Jul 6, 23:55 UTC | 1h 25m |
| 2026-07-06 | XAFSA | - | Jul 6, 18:00 UTC | Jul 6, 18:25 UTC | 25m |
| 2026-07-06 | XAFSA | - | Jul 6, 16:35 UTC | Jul 6, 17:05 UTC | 30m |
| 2026-07-05 | XAFSA | - | Jul 5, 14:55 UTC | Jul 5, 15:20 UTC | 25m |
| 2026-07-04 | XAFSA | - | Jul 4, 18:10 UTC | Jul 4, 18:40 UTC | 30m |
| 2026-07-04 | XAFSA | - | Jul 4, 15:00 UTC | Jul 4, 15:25 UTC | 25m |
| 2026-07-03 | XAFSA | - | Jul 3, 21:15 UTC | Jul 3, 21:45 UTC | 30m |
| 2026-07-03 | XAFSA | - | Jul 3, 15:50 UTC | Jul 3, 16:15 UTC | 25m |
| 2026-07-02 | XAFSA | - | Jul 2, 01:00 UTC | Jul 2, 01:30 UTC | 30m |
| 2026-06-30 | XAFSA | - | Jun 30, 16:30 UTC | Jun 30, 16:50 UTC | 20m |
| 2026-06-25 | XAFSA | - | Jun 25, 21:59 UTC | Jun 25, 22:24 UTC | 25m |
| 2026-06-25 | XAFSA | - | Jun 25, 20:45 UTC | Jun 25, 21:10 UTC | 25m |
| 2026-06-24 | XBNRG | - | Jun 24, 20:40 UTC | Jun 24, 20:49 UTC | 10m |
| 2026-06-22 | XAFSA | - | Jun 22, 00:34 UTC | Jun 22, 01:05 UTC | 30m |
| 2026-06-21 | XAFSA | - | Jun 21, 20:59 UTC | Jun 21, 21:29 UTC | 30m |
| 2026-06-15 | XAFSA | - | Jun 15, 18:35 UTC | Jun 15, 19:35 UTC | 1h 0m |
| 2026-06-15 | XAFSA | - | Jun 15, 13:54 UTC | Jun 15, 14:20 UTC | 25m |
| 2026-06-13 | XAFSA | - | Jun 13, 20:55 UTC | Jun 13, 21:25 UTC | 30m |
| 2026-06-13 | XAFSA | - | Jun 13, 18:30 UTC | Jun 13, 19:35 UTC | 1h 5m |
| 2026-06-12 | XBNRG | - | Jun 12, 17:05 UTC | Jun 12, 17:15 UTC | 10m |
| 2026-06-10 | XAFSA | - | Jun 10, 18:05 UTC | Jun 10, 19:15 UTC | 1h 10m |
| 2026-06-10 | XAFSA | - | Jun 10, 13:40 UTC | Jun 10, 14:10 UTC | 30m |
| 2026-06-07 | XAFSA | - | Jun 7, 17:15 UTC | Jun 7, 19:45 UTC | 2h 30m |
| 2026-06-06 | XAFSA | - | Jun 6, 19:10 UTC | Jun 6, 21:30 UTC | 2h 20m |
| 2026-06-04 | XAFSA | - | Jun 4, 01:30 UTC | Jun 4, 02:05 UTC | 35m |
| 2026-06-03 | XAFSA | - | Jun 3, 23:45 UTC | Jun 4, 00:10 UTC | 25m |
| 2026-05-29 | XAFSA | - | May 29, 00:50 UTC | May 29, 01:20 UTC | 30m |
| 2026-05-28 | XAFSA | - | May 28, 20:40 UTC | May 28, 21:00 UTC | 20m |
| 2026-05-27 | XAFSA | NTR → NTR | May 27, 14:10 UTC | May 28, 02:20 UTC | 12h 10m |
| 2026-05-27 | XAFSA | - | May 27, 02:34 UTC | May 27, 03:04 UTC | 30m |
| 2026-05-26 | XAFSA | - | May 26, 23:10 UTC | May 26, 23:35 UTC | 25m |
| 2026-05-26 | XBNRG | - | May 26, 21:04 UTC | May 26, 21:14 UTC | 10m |
| 2026-05-24 | XAFSA | - | May 24, 20:45 UTC | May 24, 21:15 UTC | 30m |
| 2026-05-23 | XBNRG | - | May 23, 20:10 UTC | May 23, 20:20 UTC | 10m |
| 2026-05-23 | XAFSA | - | May 23, 14:40 UTC | May 23, 15:05 UTC | 25m |
| 2026-05-22 | XAFSA | - | May 22, 01:15 UTC | May 22, 01:45 UTC | 30m |
| 2026-05-21 | XAFSA | - | May 21, 21:15 UTC | May 21, 21:40 UTC | 25m |
| 2026-05-20 | XBNRG | - | May 20, 17:10 UTC | May 20, 18:05 UTC | 55m |
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-FSA page for operator, model, and routing details .