sensors Mode-S transponder
A9D2B9
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N732CP · CESSNA 172 Skyhawk · operated by CIVIL AIR PATROL
- Hex
- A9D2B9
- Octal
- 52351271
- Decimal
- 11,129,529
- Country
- US
- Tail
- N732CP
- Type
- C172
- Flights observed
- 47
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 19h ago
Last known position
Country allocation
The ICAO 24-bit address A9D2B9 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 |
|---|---|---|---|
| CAP1832 | - | 47 | 2026-05-29 |
Recent flights last 47
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | CAP1832 | - | May 29, 15:00 UTC | May 29, 15:35 UTC | 35m |
| 2026-05-16 | CAP1832 | - | May 16, 11:25 UTC | May 16, 11:51 UTC | 25m |
| 2026-05-12 | CAP1832 | - | May 12, 20:15 UTC | May 12, 22:15 UTC | 2h 0m |
| 2026-05-12 | CAP1832 | - | May 12, 16:15 UTC | May 12, 17:20 UTC | 1h 5m |
| 2026-05-12 | CAP1832 | - | May 12, 14:05 UTC | May 12, 14:50 UTC | 45m |
| 2026-05-11 | CAP1832 | - | May 11, 15:05 UTC | May 11, 16:05 UTC | 1h 0m |
| 2026-05-10 | CAP1832 | - | May 10, 16:00 UTC | May 10, 16:34 UTC | 35m |
| 2026-05-09 | CAP1832 | - | May 9, 17:10 UTC | May 9, 18:15 UTC | 1h 5m |
| 2026-05-08 | CAP1832 | - | May 8, 23:35 UTC | May 9, 01:00 UTC | 1h 25m |
| 2026-05-07 | CAP1832 | - | May 7, 14:55 UTC | May 7, 15:45 UTC | 50m |
| 2026-05-07 | CAP1832 | - | May 7, 12:50 UTC | May 7, 13:40 UTC | 50m |
| 2026-05-05 | CAP1832 | - | May 5, 10:30 UTC | May 5, 13:35 UTC | 3h 5m |
| 2026-05-04 | CAP1832 | - | May 4, 15:20 UTC | May 4, 16:25 UTC | 1h 5m |
| 2026-05-03 | CAP1832 | - | May 3, 19:20 UTC | May 3, 19:40 UTC | 20m |
| 2026-05-03 | CAP1832 | GAI → GAI | May 3, 17:24 UTC | May 3, 18:40 UTC | 1h 15m |
| 2026-05-03 | CAP1832 | - | May 3, 15:25 UTC | May 3, 16:15 UTC | 50m |
| 2026-05-03 | CAP1832 | - | May 3, 13:45 UTC | May 3, 14:50 UTC | 1h 5m |
| 2026-05-03 | CAP1832 | - | May 3, 12:20 UTC | May 3, 12:35 UTC | 15m |
| 2026-05-02 | CAP1832 | GAI → FDK | May 2, 23:40 UTC | May 2, 23:55 UTC | 15m |
| 2026-05-02 | CAP1832 | THV → GAI | May 2, 22:20 UTC | May 2, 22:55 UTC | 35m |
| 2026-05-02 | CAP1832 | - | May 2, 20:45 UTC | May 2, 21:25 UTC | 40m |
| 2026-05-02 | CAP1832 | GAI → GAI | May 2, 17:10 UTC | May 2, 18:45 UTC | 1h 35m |
| 2026-05-02 | CAP1832 | GAI → GAI | May 2, 14:30 UTC | May 2, 16:05 UTC | 1h 35m |
| 2026-05-02 | CAP1832 | - | May 2, 13:40 UTC | May 2, 13:50 UTC | 10m |
| 2026-05-01 | CAP1832 | - | May 1, 22:45 UTC | May 2, 00:10 UTC | 1h 25m |
| 2026-05-01 | CAP1832 | - | May 1, 17:35 UTC | May 1, 18:55 UTC | 1h 20m |
| 2026-05-01 | CAP1832 | - | May 1, 14:15 UTC | May 1, 15:45 UTC | 1h 30m |
| 2026-04-28 | CAP1832 | FDK → FDK | Apr 28, 22:25 UTC | Apr 28, 23:50 UTC | 1h 25m |
| 2026-04-28 | CAP1832 | - | Apr 28, 21:05 UTC | Apr 28, 21:15 UTC | 10m |
| 2026-04-27 | CAP1832 | - | Apr 27, 20:15 UTC | Apr 27, 21:30 UTC | 1h 15m |
| 2026-04-25 | CAP1832 | - | Apr 25, 20:05 UTC | Apr 25, 21:25 UTC | 1h 20m |
| 2026-04-25 | CAP1832 | - | Apr 25, 15:15 UTC | Apr 25, 16:15 UTC | 1h 0m |
| 2026-04-24 | CAP1832 | - | Apr 24, 18:30 UTC | Apr 24, 20:05 UTC | 1h 35m |
| 2026-04-23 | CAP1832 | - | Apr 23, 20:40 UTC | Apr 23, 21:30 UTC | 50m |
| 2026-04-23 | CAP1832 | MTN → MTN | Apr 23, 18:20 UTC | Apr 23, 18:40 UTC | 20m |
| 2026-04-23 | CAP1832 | - | Apr 23, 17:25 UTC | Apr 23, 17:45 UTC | 19m |
| 2026-04-23 | CAP1832 | - | Apr 23, 14:20 UTC | Apr 23, 14:50 UTC | 30m |
| 2026-04-22 | CAP1832 | - | Apr 22, 19:05 UTC | Apr 22, 20:30 UTC | 1h 25m |
| 2026-04-21 | CAP1832 | FDK → FDK | Apr 21, 21:55 UTC | Apr 21, 22:35 UTC | 40m |
| 2026-04-21 | CAP1832 | FDK → FDK | Apr 21, 19:50 UTC | Apr 21, 20:45 UTC | 55m |
| 2026-04-21 | CAP1832 | - | Apr 21, 17:20 UTC | Apr 21, 17:35 UTC | 15m |
| 2026-04-21 | CAP1832 | - | Apr 21, 14:15 UTC | Apr 21, 16:40 UTC | 2h 25m |
| 2026-04-21 | CAP1832 | FDK → GAI | Apr 21, 13:05 UTC | Apr 21, 13:25 UTC | 20m |
| 2026-04-16 | CAP1832 | - | Apr 16, 14:00 UTC | Apr 16, 14:55 UTC | 55m |
| 2026-04-15 | CAP1832 | - | Apr 15, 13:25 UTC | Apr 15, 14:55 UTC | 1h 29m |
| 2026-04-14 | CAP1832 | FDK → FDK | Apr 14, 19:40 UTC | Apr 14, 20:40 UTC | 1h 0m |
| 2026-04-13 | CAP1832 | - | Apr 13, 20:00 UTC | Apr 13, 21:05 UTC | 1h 5m |
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 N732CP page for operator, model, and routing details .