sensors Mode-S transponder
A32E6E
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N304CP · CESSNA 172 Skyhawk · operated by CIVIL AIR PATROL
- Hex
- A32E6E
- Octal
- 50627156
- Decimal
- 10,694,254
- Country
- US
- Tail
- N304CP
- Type
- C172
- Flights observed
- 75
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address A32E6E 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 |
|---|---|---|---|
| CAP1904 | - | 75 | 2026-07-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-20 | CAP1904 | - | Jul 20, 15:50 UTC | Jul 20, 17:30 UTC | 1h 40m |
| 2026-07-20 | CAP1904 | - | Jul 20, 11:50 UTC | Jul 20, 14:50 UTC | 3h 0m |
| 2026-07-19 | CAP1904 | - | Jul 19, 22:15 UTC | Jul 19, 23:20 UTC | 1h 5m |
| 2026-07-18 | CAP1904 | - | Jul 18, 15:30 UTC | Jul 18, 16:00 UTC | 30m |
| 2026-07-18 | CAP1904 | - | Jul 18, 11:50 UTC | Jul 18, 12:40 UTC | 50m |
| 2026-07-17 | CAP1904 | - | Jul 17, 02:15 UTC | Jul 17, 02:34 UTC | 20m |
| 2026-07-17 | CAP1904 | - | Jul 17, 01:25 UTC | Jul 17, 01:45 UTC | 20m |
| 2026-07-16 | CAP1904 | - | Jul 16, 17:25 UTC | Jul 16, 18:15 UTC | 50m |
| 2026-07-16 | CAP1904 | - | Jul 16, 16:05 UTC | Jul 16, 16:40 UTC | 35m |
| 2026-07-16 | CAP1904 | - | Jul 16, 14:45 UTC | Jul 16, 15:19 UTC | 35m |
| 2026-07-16 | CAP1904 | - | Jul 16, 12:05 UTC | Jul 16, 12:40 UTC | 35m |
| 2026-07-10 | CAP1904 | - | Jul 10, 12:50 UTC | Jul 10, 13:50 UTC | 1h 0m |
| 2026-07-09 | CAP1904 | - | Jul 9, 23:30 UTC | Jul 10, 00:20 UTC | 50m |
| 2026-07-09 | CAP1904 | - | Jul 9, 20:40 UTC | Jul 9, 22:35 UTC | 1h 55m |
| 2026-07-08 | CAP1904 | - | Jul 8, 13:10 UTC | Jul 8, 13:55 UTC | 45m |
| 2026-07-06 | CAP1904 | - | Jul 6, 18:25 UTC | Jul 6, 19:10 UTC | 45m |
| 2026-07-06 | CAP1904 | - | Jul 6, 14:50 UTC | Jul 6, 15:15 UTC | 25m |
| 2026-07-05 | CAP1904 | - | Jul 5, 16:20 UTC | Jul 5, 17:10 UTC | 50m |
| 2026-07-05 | CAP1904 | - | Jul 5, 14:45 UTC | Jul 5, 15:30 UTC | 45m |
| 2026-07-05 | CAP1904 | - | Jul 5, 13:50 UTC | Jul 5, 14:30 UTC | 40m |
| 2026-07-05 | CAP1904 | - | Jul 5, 11:25 UTC | Jul 5, 12:15 UTC | 50m |
| 2026-07-02 | CAP1904 | - | Jul 2, 13:15 UTC | Jul 2, 14:00 UTC | 45m |
| 2026-06-30 | CAP1904 | - | Jun 30, 02:00 UTC | Jun 30, 03:00 UTC | 1h 0m |
| 2026-06-29 | CAP1904 | - | Jun 29, 22:35 UTC | Jun 29, 23:05 UTC | 30m |
| 2026-06-29 | CAP1904 | - | Jun 29, 20:24 UTC | Jun 29, 20:49 UTC | 25m |
| 2026-06-27 | CAP1904 | - | Jun 27, 14:35 UTC | Jun 27, 16:35 UTC | 2h 0m |
| 2026-06-26 | CAP1904 | - | Jun 26, 21:45 UTC | Jun 26, 23:04 UTC | 1h 20m |
| 2026-06-21 | CAP1904 | - | Jun 21, 19:29 UTC | Jun 21, 20:34 UTC | 1h 5m |
| 2026-06-21 | CAP1904 | - | Jun 21, 17:45 UTC | Jun 21, 18:29 UTC | 45m |
| 2026-06-21 | CAP1904 | - | Jun 21, 16:04 UTC | Jun 21, 16:44 UTC | 40m |
| 2026-06-21 | CAP1904 | - | Jun 21, 14:44 UTC | Jun 21, 15:25 UTC | 40m |
| 2026-06-21 | CAP1904 | - | Jun 21, 13:00 UTC | Jun 21, 13:44 UTC | 45m |
| 2026-06-02 | CAP1904 | - | Jun 2, 19:55 UTC | Jun 2, 20:40 UTC | 45m |
| 2026-06-01 | CAP1904 | - | Jun 1, 20:30 UTC | Jun 1, 20:40 UTC | 10m |
| 2026-05-31 | CAP1904 | - | May 31, 19:25 UTC | May 31, 19:50 UTC | 25m |
| 2026-05-31 | CAP1904 | - | May 31, 18:30 UTC | May 31, 18:50 UTC | 20m |
| 2026-05-31 | CAP1904 | - | May 31, 17:55 UTC | May 31, 18:25 UTC | 30m |
| 2026-05-31 | CAP1904 | - | May 31, 16:10 UTC | May 31, 16:50 UTC | 40m |
| 2026-05-31 | CAP1904 | - | May 31, 14:55 UTC | May 31, 15:30 UTC | 35m |
| 2026-05-31 | CAP1904 | - | May 31, 13:05 UTC | May 31, 13:15 UTC | 10m |
| 2026-05-26 | CAP1904 | - | May 26, 19:55 UTC | May 26, 20:34 UTC | 40m |
| 2026-05-26 | CAP1904 | - | May 26, 12:40 UTC | May 26, 13:40 UTC | 1h 0m |
| 2026-05-23 | CAP1904 | - | May 23, 19:05 UTC | May 23, 19:35 UTC | 30m |
| 2026-05-23 | CAP1904 | - | May 23, 16:55 UTC | May 23, 17:45 UTC | 50m |
| 2026-05-23 | CAP1904 | - | May 23, 15:40 UTC | May 23, 16:15 UTC | 35m |
| 2026-05-23 | CAP1904 | - | May 23, 14:10 UTC | May 23, 14:45 UTC | 35m |
| 2026-05-23 | CAP1904 | - | May 23, 12:50 UTC | May 23, 13:30 UTC | 40m |
| 2026-05-22 | CAP1904 | - | May 22, 15:45 UTC | May 22, 16:15 UTC | 30m |
| 2026-05-22 | CAP1904 | - | May 22, 14:15 UTC | May 22, 15:15 UTC | 1h 0m |
| 2026-05-17 | CAP1904 | - | May 17, 18:01 UTC | May 17, 18:35 UTC | 35m |
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 N304CP page for operator, model, and routing details .