sensors Mode-S transponder
0D05D7
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to 3203 · CASA C-295 Persuader
- Hex
- 0D05D7
- Octal
- 03202727
- Decimal
- 853,463
- Country
- MX
- Tail
- 3203
- Type
- C295
- Flights observed
- 52
- Distinct callsigns
- 1
- Country
- MX
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 0D05D7 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 |
|---|---|---|---|
| FAM3203 | - | 52 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | FAM3203 | - | Jul 26, 19:40 UTC | Jul 26, 20:25 UTC | 45m |
| 2026-07-24 | FAM3203 | - | Jul 24, 14:45 UTC | Jul 24, 15:25 UTC | 40m |
| 2026-07-24 | FAM3203 | - | Jul 24, 07:15 UTC | Jul 24, 08:40 UTC | 1h 25m |
| 2026-07-24 | FAM3203 | - | Jul 24, 02:35 UTC | Jul 24, 03:10 UTC | 35m |
| 2026-07-23 | FAM3203 | - | Jul 23, 22:20 UTC | Jul 23, 22:30 UTC | 10m |
| 2026-07-23 | FAM3203 | - | Jul 23, 18:55 UTC | Jul 23, 19:40 UTC | 45m |
| 2026-07-23 | FAM3203 | - | Jul 23, 11:10 UTC | Jul 23, 11:20 UTC | 10m |
| 2026-07-22 | FAM3203 | - | Jul 22, 16:40 UTC | Jul 22, 17:00 UTC | 20m |
| 2026-07-20 | FAM3203 | - | Jul 20, 17:55 UTC | Jul 20, 18:35 UTC | 40m |
| 2026-07-20 | FAM3203 | - | Jul 20, 16:55 UTC | Jul 20, 17:10 UTC | 15m |
| 2026-07-19 | FAM3203 | - | Jul 19, 04:55 UTC | Jul 19, 06:30 UTC | 1h 35m |
| 2026-07-19 | FAM3203 | - | Jul 19, 02:50 UTC | Jul 19, 03:45 UTC | 55m |
| 2026-07-18 | FAM3203 | - | Jul 18, 16:20 UTC | Jul 18, 16:50 UTC | 30m |
| 2026-07-16 | FAM3203 | - | Jul 16, 16:25 UTC | Jul 16, 16:44 UTC | 20m |
| 2026-07-16 | FAM3203 | - | Jul 16, 13:34 UTC | Jul 16, 14:45 UTC | 1h 10m |
| 2026-07-15 | FAM3203 | - | Jul 15, 18:35 UTC | Jul 15, 19:10 UTC | 35m |
| 2026-07-15 | FAM3203 | - | Jul 15, 16:40 UTC | Jul 15, 16:55 UTC | 15m |
| 2026-07-11 | FAM3203 | - | Jul 11, 21:50 UTC | Jul 11, 23:05 UTC | 1h 15m |
| 2026-07-11 | FAM3203 | - | Jul 11, 20:00 UTC | Jul 11, 20:30 UTC | 30m |
| 2026-07-11 | FAM3203 | - | Jul 11, 17:25 UTC | Jul 11, 18:10 UTC | 45m |
| 2026-07-11 | FAM3203 | - | Jul 11, 14:55 UTC | Jul 11, 16:10 UTC | 1h 15m |
| 2026-07-03 | FAM3203 | - | Jul 3, 02:45 UTC | Jul 3, 03:25 UTC | 40m |
| 2026-06-30 | FAM3203 | - | Jun 30, 02:05 UTC | Jun 30, 02:50 UTC | 45m |
| 2026-06-21 | FAM3203 | - | Jun 21, 22:10 UTC | Jun 21, 23:24 UTC | 1h 15m |
| 2026-06-20 | FAM3203 | - | Jun 20, 17:44 UTC | Jun 20, 18:04 UTC | 20m |
| 2026-06-18 | FAM3203 | - | Jun 18, 23:50 UTC | Jun 19, 00:24 UTC | 34m |
| 2026-06-18 | FAM3203 | - | Jun 18, 18:30 UTC | Jun 18, 18:40 UTC | 10m |
| 2026-05-09 | FAM3203 | - | May 9, 15:35 UTC | May 9, 16:25 UTC | 50m |
| 2026-05-08 | FAM3203 | - | May 8, 15:30 UTC | May 8, 15:40 UTC | 10m |
| 2026-05-08 | FAM3203 | - | May 8, 13:30 UTC | May 8, 13:40 UTC | 10m |
| 2026-05-08 | FAM3203 | - | May 8, 11:34 UTC | May 8, 11:44 UTC | 10m |
| 2026-05-07 | FAM3203 | - | May 7, 22:15 UTC | May 7, 22:25 UTC | 10m |
| 2026-05-07 | FAM3203 | - | May 7, 11:40 UTC | May 7, 11:50 UTC | 10m |
| 2026-05-06 | FAM3203 | - | May 6, 16:30 UTC | May 6, 16:45 UTC | 15m |
| 2026-05-06 | FAM3203 | - | May 6, 14:45 UTC | May 6, 14:55 UTC | 10m |
| 2026-05-06 | FAM3203 | - | May 6, 12:45 UTC | May 6, 12:55 UTC | 10m |
| 2026-05-05 | FAM3203 | - | May 5, 15:05 UTC | May 5, 15:15 UTC | 10m |
| 2026-05-03 | FAM3203 | - | May 3, 15:45 UTC | May 3, 16:30 UTC | 45m |
| 2026-05-02 | FAM3203 | - | May 2, 16:35 UTC | May 2, 17:40 UTC | 1h 5m |
| 2026-05-01 | FAM3203 | - | May 1, 16:45 UTC | May 1, 16:55 UTC | 10m |
| 2026-05-01 | FAM3203 | - | May 1, 15:00 UTC | May 1, 15:10 UTC | 10m |
| 2026-05-01 | FAM3203 | - | May 1, 13:00 UTC | May 1, 13:10 UTC | 10m |
| 2026-04-30 | FAM3203 | - | Apr 30, 20:45 UTC | Apr 30, 20:55 UTC | 10m |
| 2026-04-30 | FAM3203 | - | Apr 30, 18:50 UTC | Apr 30, 19:00 UTC | 10m |
| 2026-04-30 | FAM3203 | - | Apr 30, 14:55 UTC | Apr 30, 15:10 UTC | 15m |
| 2026-04-30 | FAM3203 | - | Apr 30, 12:55 UTC | Apr 30, 13:05 UTC | 10m |
| 2026-04-29 | FAM3203 | - | Apr 29, 18:55 UTC | Apr 29, 19:05 UTC | 10m |
| 2026-04-29 | FAM3203 | - | Apr 29, 16:55 UTC | Apr 29, 17:05 UTC | 10m |
| 2026-04-28 | FAM3203 | - | Apr 28, 23:50 UTC | Apr 29, 00:10 UTC | 20m |
| 2026-04-27 | FAM3203 | - | Apr 27, 20:55 UTC | Apr 27, 21:10 UTC | 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 3203 page for operator, model, and routing details .