sensors Mode-S transponder
0D0AAF
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-FGL · GULFSTREAM G280
- Hex
- 0D0AAF
- Octal
- 03205257
- Decimal
- 854,703
- Country
- MX
- Tail
- XA-FGL
- Type
- G280
- Flights observed
- 24
- Distinct callsigns
- 1
- Country
- MX
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address 0D0AAF 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 |
|---|---|---|---|
| XAFGL | - | 24 | 2026-06-14 |
Recent flights last 24
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-14 | XAFGL | - | Jun 14, 22:50 UTC | Jun 14, 23:54 UTC | 1h 5m |
| 2026-06-14 | XAFGL | - | Jun 14, 15:10 UTC | Jun 14, 16:20 UTC | 1h 10m |
| 2026-06-13 | XAFGL | - | Jun 13, 00:20 UTC | Jun 13, 01:25 UTC | 1h 5m |
| 2026-06-11 | XAFGL | - | Jun 11, 04:15 UTC | Jun 11, 04:40 UTC | 25m |
| 2026-06-05 | XAFGL | - | Jun 5, 17:15 UTC | Jun 5, 18:45 UTC | 1h 30m |
| 2026-06-04 | XAFGL | - | Jun 4, 16:25 UTC | Jun 4, 16:55 UTC | 30m |
| 2026-05-27 | XAFGL | - | May 27, 01:05 UTC | May 27, 02:19 UTC | 1h 15m |
| 2026-05-26 | XAFGL | - | May 26, 23:19 UTC | May 27, 00:14 UTC | 55m |
| 2026-05-26 | XAFGL | - | May 26, 16:20 UTC | May 26, 17:04 UTC | 45m |
| 2026-05-26 | XAFGL | - | May 26, 15:05 UTC | May 26, 15:39 UTC | 35m |
| 2026-05-26 | XAFGL | NTR → LRD | May 26, 13:54 UTC | May 26, 14:30 UTC | 35m |
| 2026-05-22 | XAFGL | - | May 22, 17:40 UTC | May 22, 18:55 UTC | 1h 15m |
| 2026-05-21 | XAFGL | LRD → AFW | May 21, 17:30 UTC | May 21, 18:35 UTC | 1h 5m |
| 2026-05-21 | XAFGL | NTR → LRD | May 21, 15:00 UTC | May 21, 15:30 UTC | 30m |
| 2026-05-20 | XAFGL | - | May 20, 17:45 UTC | May 20, 18:10 UTC | 25m |
| 2026-05-20 | XAFGL | AFW → LRD | May 20, 16:10 UTC | May 20, 17:15 UTC | 1h 5m |
| 2026-05-04 | XAFGL | - | May 4, 15:20 UTC | May 4, 16:20 UTC | 1h 0m |
| 2026-05-04 | XAFGL | NTR → LRD | May 4, 14:05 UTC | May 4, 14:40 UTC | 35m |
| 2026-05-03 | XAFGL | - | May 3, 22:34 UTC | May 3, 23:04 UTC | 30m |
| 2026-04-30 | XAFGL | - | Apr 30, 22:10 UTC | Apr 30, 22:30 UTC | 20m |
| 2026-04-25 | XAFGL | - | Apr 25, 22:05 UTC | Apr 26, 02:25 UTC | 4h 20m |
| 2026-04-25 | XAFGL | - | Apr 25, 17:05 UTC | Apr 25, 20:45 UTC | 3h 40m |
| 2026-04-23 | XAFGL | NTR → NTR | Apr 23, 18:45 UTC | Apr 24, 04:45 UTC | 10h 0m |
| 2026-04-12 | XAFGL | - | Apr 12, 19:20 UTC | Apr 12, 20:05 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-FGL page for operator, model, and routing details .