sensors Mode-S transponder
AC50B9
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N893CP · CESSNA TR182 Turbo Skylane RG · operated by CIVIL AIR PATROL
- Hex
- AC50B9
- Octal
- 53050271
- Decimal
- 11,292,857
- Country
- US
- Tail
- N893CP
- Type
- C82T
- Flights observed
- 98
- Distinct callsigns
- 4
- Country
- US
- Last broadcast
- 8d ago
Last known position
Country allocation
The ICAO 24-bit address AC50B9 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 4 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-05 | CAP1801 | - | Jul 5, 16:00 UTC | Jul 5, 17:45 UTC | 1h 45m |
| 2026-07-03 | CAP1802 | - | Jul 3, 21:35 UTC | Jul 3, 23:25 UTC | 1h 50m |
| 2026-07-03 | CAP1893 | - | Jul 3, 19:50 UTC | Jul 3, 20:15 UTC | 25m |
| 2026-07-03 | CAP1801 | - | Jul 3, 18:05 UTC | Jul 3, 18:35 UTC | 30m |
| 2026-07-03 | CAP1801 | - | Jul 3, 14:35 UTC | Jul 3, 16:25 UTC | 1h 50m |
| 2026-07-02 | CAP1893 | - | Jul 2, 23:00 UTC | Jul 3, 00:55 UTC | 1h 55m |
| 2026-07-01 | CAP1893 | - | Jul 1, 21:00 UTC | Jul 1, 23:05 UTC | 2h 5m |
| 2026-07-01 | CAP1893 | - | Jul 1, 17:05 UTC | Jul 1, 19:10 UTC | 2h 5m |
| 2026-07-01 | CAP1893 | - | Jul 1, 13:55 UTC | Jul 1, 14:15 UTC | 20m |
| 2026-07-01 | CAP1893 | - | Jul 1, 12:35 UTC | Jul 1, 12:55 UTC | 20m |
| 2026-06-30 | CAP1893 | ADW → FME | Jun 30, 15:20 UTC | Jun 30, 15:35 UTC | 15m |
| 2026-06-30 | CAP1893 | - | Jun 30, 11:30 UTC | Jun 30, 13:55 UTC | 2h 25m |
| 2026-06-30 | CAP1893 | FME → ADW | Jun 30, 09:20 UTC | Jun 30, 09:35 UTC | 15m |
| 2026-06-29 | CAP1893 | - | Jun 29, 20:40 UTC | Jun 29, 20:59 UTC | 20m |
| 2026-06-29 | CAP1893 | - | Jun 29, 13:00 UTC | Jun 29, 13:14 UTC | 15m |
| 2026-06-27 | CAP1893 | - | Jun 27, 18:24 UTC | Jun 27, 20:34 UTC | 2h 10m |
| 2026-06-26 | CAP1893 | - | Jun 26, 19:04 UTC | Jun 26, 20:59 UTC | 1h 55m |
| 2026-06-26 | CAP1893 | - | Jun 26, 17:09 UTC | Jun 26, 17:59 UTC | 50m |
| 2026-06-26 | CAP1893 | - | Jun 26, 14:29 UTC | Jun 26, 15:49 UTC | 1h 20m |
| 2026-06-25 | CAP1893 | FME → ANP | Jun 25, 21:59 UTC | Jun 26, 00:24 UTC | 2h 25m |
| 2026-06-25 | CAP1893 | FME → FME | Jun 25, 14:50 UTC | Jun 25, 15:54 UTC | 1h 5m |
| 2026-06-24 | CAP1893 | - | Jun 24, 23:50 UTC | Jun 25, 00:40 UTC | 50m |
| 2026-06-24 | CAP1893 | - | Jun 24, 21:44 UTC | Jun 24, 22:45 UTC | 1h 0m |
| 2026-06-20 | CAP1893 | FME → FME | Jun 20, 20:05 UTC | Jun 20, 21:34 UTC | 1h 30m |
| 2026-06-20 | CAP1801 | - | Jun 20, 16:55 UTC | Jun 20, 18:49 UTC | 1h 55m |
| 2026-06-17 | CAP1893 | - | Jun 17, 22:45 UTC | Jun 17, 23:25 UTC | 40m |
| 2026-06-17 | CAP1893 | - | Jun 17, 20:30 UTC | Jun 17, 21:15 UTC | 45m |
| 2026-06-17 | CAP1893 | FME → LTW | Jun 17, 19:25 UTC | Jun 17, 19:55 UTC | 30m |
| 2026-06-17 | CAP1893 | - | Jun 17, 01:20 UTC | Jun 17, 02:50 UTC | 1h 30m |
| 2026-06-16 | CAP1893 | - | Jun 16, 18:25 UTC | Jun 16, 20:05 UTC | 1h 41m |
| 2026-06-16 | CAP1893 | - | Jun 16, 15:50 UTC | Jun 16, 17:10 UTC | 1h 20m |
| 2026-06-13 | CAP1801 | - | Jun 13, 17:00 UTC | Jun 13, 18:45 UTC | 1h 45m |
| 2026-06-12 | CAP1893 | - | Jun 12, 15:30 UTC | Jun 12, 15:55 UTC | 25m |
| 2026-06-12 | CAP1893 | - | Jun 12, 12:35 UTC | Jun 12, 14:35 UTC | 2h 0m |
| 2026-06-11 | CAP1893 | FME → FME | Jun 11, 15:05 UTC | Jun 11, 17:00 UTC | 1h 55m |
| 2026-06-07 | CAP1893 | - | Jun 7, 14:55 UTC | Jun 7, 16:05 UTC | 1h 10m |
| 2026-06-07 | CAP1893 | - | Jun 7, 13:30 UTC | Jun 7, 14:00 UTC | 30m |
| 2026-06-07 | CAP1893 | - | Jun 7, 12:25 UTC | Jun 7, 12:55 UTC | 30m |
| 2026-06-05 | CAP1893 | - | Jun 5, 15:25 UTC | Jun 5, 16:45 UTC | 1h 20m |
| 2026-06-05 | CAP1893 | - | Jun 5, 13:05 UTC | Jun 5, 13:50 UTC | 45m |
| 2026-06-02 | CAP1893 | - | Jun 2, 22:00 UTC | Jun 2, 22:35 UTC | 35m |
| 2026-05-31 | CAP1893 | - | May 31, 20:10 UTC | May 31, 21:35 UTC | 1h 25m |
| 2026-05-31 | CAP1893 | - | May 31, 18:00 UTC | May 31, 19:15 UTC | 1h 15m |
| 2026-05-31 | CAP1893 | - | May 31, 11:50 UTC | May 31, 12:15 UTC | 25m |
| 2026-05-29 | CAP1893 | - | May 29, 20:10 UTC | May 29, 21:50 UTC | 1h 40m |
| 2026-05-29 | CAP1893 | - | May 29, 16:20 UTC | May 29, 18:10 UTC | 1h 50m |
| 2026-05-29 | CAP1893 | - | May 29, 00:40 UTC | May 29, 01:15 UTC | 35m |
| 2026-05-28 | CAP1893 | - | May 28, 21:55 UTC | May 28, 22:30 UTC | 35m |
| 2026-05-20 | CAP1893 | - | May 20, 14:05 UTC | May 20, 15:55 UTC | 1h 50m |
| 2026-05-19 | CAP1893 | FME → FME | May 19, 20:00 UTC | May 19, 21:40 UTC | 1h 40m |
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 N893CP page for operator, model, and routing details .