sensors Mode-S transponder
A5AAF8
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N4641F · PIPER PA-28R-180/200/201 · operated by CROSSWINDS FLYING CLUB INC
- Hex
- A5AAF8
- Octal
- 51325370
- Decimal
- 10,857,208
- Country
- US
- Tail
- N4641F
- Type
- P28R
- Flights observed
- 50
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address A5AAF8 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 |
|---|---|---|---|
| N4641F | - | 50 | 2026-07-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | N4641F | - | Jul 14, 11:45 UTC | Jul 14, 12:35 UTC | 50m |
| 2026-07-13 | N4641F | - | Jul 13, 21:55 UTC | Jul 13, 22:30 UTC | 35m |
| 2026-07-11 | N4641F | - | Jul 11, 17:00 UTC | Jul 11, 17:45 UTC | 45m |
| 2026-07-10 | N4641F | - | Jul 10, 19:05 UTC | Jul 10, 20:25 UTC | 1h 20m |
| 2026-07-07 | N4641F | BMI → BMI | Jul 7, 17:05 UTC | Jul 7, 17:55 UTC | 50m |
| 2026-07-04 | N4641F | - | Jul 4, 15:30 UTC | Jul 4, 16:20 UTC | 50m |
| 2026-06-26 | N4641F | - | Jun 26, 20:44 UTC | Jun 26, 22:14 UTC | 1h 30m |
| 2026-06-26 | N4641F | BMI → UES | Jun 26, 18:44 UTC | Jun 26, 20:04 UTC | 1h 20m |
| 2026-06-24 | N4641F | - | Jun 24, 18:44 UTC | Jun 24, 19:24 UTC | 40m |
| 2026-06-20 | N4641F | - | Jun 20, 17:39 UTC | Jun 20, 17:54 UTC | 15m |
| 2026-06-20 | N4641F | - | Jun 20, 16:55 UTC | Jun 20, 17:04 UTC | 10m |
| 2026-06-20 | N4641F | - | Jun 20, 16:05 UTC | Jun 20, 16:14 UTC | 10m |
| 2026-06-20 | N4641F | - | Jun 20, 15:09 UTC | Jun 20, 15:19 UTC | 10m |
| 2026-06-20 | N4641F | - | Jun 20, 13:49 UTC | Jun 20, 14:05 UTC | 15m |
| 2026-06-20 | N4641F | - | Jun 20, 12:14 UTC | Jun 20, 13:14 UTC | 1h 0m |
| 2026-06-19 | N4641F | - | Jun 19, 22:09 UTC | Jun 19, 23:34 UTC | 1h 25m |
| 2026-06-19 | N4641F | - | Jun 19, 12:29 UTC | Jun 19, 14:29 UTC | 2h 0m |
| 2026-06-15 | N4641F | - | Jun 15, 23:39 UTC | Jun 16, 00:29 UTC | 50m |
| 2026-06-12 | N4641F | - | Jun 12, 15:05 UTC | Jun 12, 15:35 UTC | 30m |
| 2026-06-12 | N4641F | - | Jun 12, 13:30 UTC | Jun 12, 14:01 UTC | 30m |
| 2026-06-03 | N4641F | - | Jun 3, 17:35 UTC | Jun 3, 18:20 UTC | 45m |
| 2026-05-30 | N4641F | - | May 30, 14:45 UTC | May 30, 15:05 UTC | 20m |
| 2026-05-29 | N4641F | - | May 29, 15:15 UTC | May 29, 15:40 UTC | 25m |
| 2026-05-28 | N4641F | - | May 28, 17:50 UTC | May 28, 18:35 UTC | 45m |
| 2026-05-25 | N4641F | - | May 25, 21:09 UTC | May 25, 21:49 UTC | 40m |
| 2026-05-25 | N4641F | - | May 25, 18:05 UTC | May 25, 18:35 UTC | 30m |
| 2026-05-23 | N4641F | - | May 23, 16:45 UTC | May 23, 16:55 UTC | 10m |
| 2026-05-23 | N4641F | - | May 23, 11:00 UTC | May 23, 11:10 UTC | 10m |
| 2026-05-20 | N4641F | - | May 20, 15:45 UTC | May 20, 16:50 UTC | 1h 5m |
| 2026-05-16 | N4641F | - | May 16, 13:01 UTC | May 16, 13:21 UTC | 20m |
| 2026-05-14 | N4641F | - | May 14, 12:50 UTC | May 14, 13:40 UTC | 50m |
| 2026-05-13 | N4641F | - | May 13, 18:55 UTC | May 13, 19:40 UTC | 45m |
| 2026-05-12 | N4641F | - | May 12, 12:30 UTC | May 12, 13:00 UTC | 30m |
| 2026-05-08 | N4641F | BMI → BMI | May 8, 22:30 UTC | May 8, 23:35 UTC | 1h 5m |
| 2026-05-06 | N4641F | CMI → BMI | May 6, 20:10 UTC | May 6, 20:36 UTC | 26m |
| 2026-05-06 | N4641F | - | May 6, 18:50 UTC | May 6, 19:35 UTC | 45m |
| 2026-05-06 | N4641F | - | May 6, 13:35 UTC | May 6, 13:55 UTC | 20m |
| 2026-05-01 | N4641F | - | May 1, 17:20 UTC | May 1, 17:35 UTC | 15m |
| 2026-04-26 | N4641F | - | Apr 26, 23:45 UTC | Apr 27, 00:05 UTC | 20m |
| 2026-04-26 | N4641F | - | Apr 26, 22:20 UTC | Apr 26, 22:40 UTC | 20m |
| 2026-04-26 | N4641F | - | Apr 26, 21:10 UTC | Apr 26, 21:35 UTC | 25m |
| 2026-04-25 | N4641F | - | Apr 25, 19:20 UTC | Apr 25, 19:55 UTC | 35m |
| 2026-04-25 | N4641F | - | Apr 25, 17:00 UTC | Apr 25, 17:45 UTC | 45m |
| 2026-04-25 | N4641F | - | Apr 25, 11:35 UTC | Apr 25, 11:45 UTC | 10m |
| 2026-04-22 | N4641F | - | Apr 22, 16:15 UTC | Apr 22, 17:15 UTC | 1h 0m |
| 2026-04-20 | N4641F | - | Apr 20, 18:00 UTC | Apr 20, 18:55 UTC | 55m |
| 2026-04-20 | N4641F | - | Apr 20, 15:45 UTC | Apr 20, 16:40 UTC | 55m |
| 2026-04-16 | N4641F | - | Apr 16, 21:34 UTC | Apr 16, 21:50 UTC | 15m |
| 2026-04-16 | N4641F | - | Apr 16, 19:35 UTC | Apr 16, 20:10 UTC | 35m |
| 2026-04-16 | N4641F | - | Apr 16, 17:15 UTC | Apr 16, 17:25 UTC | 10m |
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 N4641F page for operator, model, and routing details .