sensors Mode-S transponder
A22FCB
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N24XZ · PILATUS PC-12 · operated by 31DODGE AIR LLC
- Hex
- A22FCB
- Octal
- 50427713
- Decimal
- 10,629,067
- Country
- US
- Tail
- N24XZ
- Type
- PC12
- Flights observed
- 57
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- Jul 26, 20:10 UTC
Last known position
Country allocation
The ICAO 24-bit address A22FCB falls within the block assigned to United States (US) by ICAO Annex 10, Volume III. Every aircraft registered in United States 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 |
|---|---|---|---|
| N24XZ | - | 57 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | N24XZ | - | Jul 26, 16:55 UTC | Jul 26, 20:10 UTC | 3h 15m |
| 2026-07-24 | N24XZ | - | Jul 24, 20:50 UTC | Jul 24, 23:55 UTC | 3h 5m |
| 2026-07-20 | N24XZ | - | Jul 20, 16:05 UTC | Jul 20, 18:30 UTC | 2h 25m |
| 2026-07-18 | N24XZ | - | Jul 18, 14:10 UTC | Jul 18, 16:45 UTC | 2h 35m |
| 2026-07-13 | N24XZ | - | Jul 13, 22:00 UTC | Jul 13, 22:40 UTC | 40m |
| 2026-07-13 | N24XZ | - | Jul 13, 20:35 UTC | Jul 13, 21:20 UTC | 45m |
| 2026-07-06 | N24XZ | - | Jul 6, 15:10 UTC | Jul 6, 15:50 UTC | 40m |
| 2026-07-06 | N24XZ | - | Jul 6, 13:40 UTC | Jul 6, 14:25 UTC | 45m |
| 2026-07-05 | N24XZ | - | Jul 5, 16:45 UTC | Jul 5, 19:10 UTC | 2h 25m |
| 2026-07-05 | N24XZ | - | Jul 5, 13:25 UTC | Jul 5, 15:55 UTC | 2h 30m |
| 2026-07-02 | N24XZ | - | Jul 2, 18:45 UTC | Jul 2, 20:00 UTC | 1h 15m |
| 2026-07-02 | N24XZ | - | Jul 2, 16:30 UTC | Jul 2, 17:10 UTC | 40m |
| 2026-06-28 | N24XZ | - | Jun 28, 18:14 UTC | Jun 28, 18:59 UTC | 45m |
| 2026-06-28 | N24XZ | - | Jun 28, 17:00 UTC | Jun 28, 17:39 UTC | 40m |
| 2026-06-28 | N24XZ | - | Jun 28, 15:40 UTC | Jun 28, 15:49 UTC | 10m |
| 2026-06-25 | N24XZ | - | Jun 25, 21:44 UTC | Jun 26, 00:24 UTC | 2h 40m |
| 2026-06-25 | N24XZ | - | Jun 25, 18:00 UTC | Jun 25, 20:45 UTC | 2h 45m |
| 2026-06-24 | N24XZ | - | Jun 24, 14:39 UTC | Jun 24, 19:55 UTC | 5h 15m |
| 2026-06-23 | N24XZ | - | Jun 23, 19:29 UTC | Jun 23, 21:59 UTC | 2h 30m |
| 2026-06-23 | N24XZ | - | Jun 23, 15:15 UTC | Jun 23, 17:50 UTC | 2h 35m |
| 2026-06-22 | N24XZ | - | Jun 22, 12:05 UTC | Jun 22, 12:49 UTC | 45m |
| 2026-06-20 | N24XZ | - | Jun 20, 22:35 UTC | Jun 20, 23:14 UTC | 40m |
| 2026-06-20 | N24XZ | - | Jun 20, 17:49 UTC | Jun 20, 19:49 UTC | 2h 0m |
| 2026-06-20 | N24XZ | - | Jun 20, 14:09 UTC | Jun 20, 16:55 UTC | 2h 45m |
| 2026-06-18 | N24XZ | - | Jun 18, 17:21 UTC | Jun 18, 23:00 UTC | 5h 39m |
| 2026-06-11 | N24XZ | - | Jun 11, 19:45 UTC | Jun 11, 22:20 UTC | 2h 35m |
| 2026-06-08 | N24XZ | - | Jun 8, 11:40 UTC | Jun 8, 14:25 UTC | 2h 45m |
| 2026-05-30 | N24XZ | - | May 30, 16:05 UTC | May 30, 19:00 UTC | 2h 55m |
| 2026-05-30 | N24XZ | - | May 30, 11:55 UTC | May 30, 14:45 UTC | 2h 50m |
| 2026-05-27 | N24XZ | - | May 27, 23:50 UTC | May 28, 00:35 UTC | 45m |
| 2026-05-27 | N24XZ | - | May 27, 22:35 UTC | May 27, 23:10 UTC | 35m |
| 2026-05-21 | N24XZ | - | May 21, 20:40 UTC | May 21, 21:20 UTC | 40m |
| 2026-05-21 | N24XZ | - | May 21, 19:25 UTC | May 21, 20:05 UTC | 40m |
| 2026-05-21 | N24XZ | - | May 21, 15:55 UTC | May 21, 18:40 UTC | 2h 45m |
| 2026-05-21 | N24XZ | - | May 21, 12:30 UTC | May 21, 15:10 UTC | 2h 40m |
| 2026-05-18 | N24XZ | - | May 18, 22:05 UTC | May 18, 22:30 UTC | 25m |
| 2026-05-17 | N24XZ | - | May 17, 19:20 UTC | May 17, 19:45 UTC | 25m |
| 2026-05-17 | N24XZ | - | May 17, 16:05 UTC | May 17, 18:35 UTC | 2h 30m |
| 2026-05-17 | N24XZ | - | May 17, 12:50 UTC | May 17, 15:25 UTC | 2h 35m |
| 2026-05-10 | N24XZ | - | May 10, 23:00 UTC | May 11, 00:49 UTC | 1h 50m |
| 2026-05-10 | N24XZ | - | May 10, 19:54 UTC | May 10, 21:59 UTC | 2h 5m |
| 2026-05-07 | N24XZ | - | May 7, 15:35 UTC | May 7, 17:30 UTC | 1h 55m |
| 2026-05-07 | N24XZ | - | May 7, 12:50 UTC | May 7, 15:05 UTC | 2h 15m |
| 2026-05-04 | N24XZ | - | May 4, 17:25 UTC | May 4, 20:35 UTC | 3h 11m |
| 2026-05-04 | N24XZ | - | May 4, 13:05 UTC | May 4, 15:40 UTC | 2h 35m |
| 2026-05-03 | N24XZ | - | May 3, 22:05 UTC | May 3, 23:30 UTC | 1h 25m |
| 2026-05-01 | N24XZ | - | May 1, 18:45 UTC | May 1, 20:40 UTC | 1h 55m |
| 2026-05-01 | N24XZ | - | May 1, 16:35 UTC | May 1, 18:15 UTC | 1h 40m |
| 2026-04-30 | N24XZ | - | Apr 30, 17:50 UTC | Apr 30, 20:45 UTC | 2h 55m |
| 2026-04-30 | N24XZ | - | Apr 30, 16:25 UTC | Apr 30, 16:40 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 N24XZ page for operator, model, and routing details .