sensors Mode-S transponder
AD6A7F
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N9636K · PIPER PA-32R-300/301/301T · operated by VANDERWERF STAN L
- Hex
- AD6A7F
- Octal
- 53265177
- Decimal
- 11,364,991
- Country
- US
- Tail
- N9636K
- Type
- P32R
- Flights observed
- 50
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- Jul 26, 14:55 UTC
Last known position
Country allocation
The ICAO 24-bit address AD6A7F 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 |
|---|---|---|---|
| N9636K | - | 50 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | N9636K | - | Jul 26, 14:30 UTC | Jul 26, 14:55 UTC | 25m |
| 2026-07-24 | N9636K | - | Jul 24, 17:55 UTC | Jul 24, 18:55 UTC | 1h 0m |
| 2026-07-24 | N9636K | - | Jul 24, 15:45 UTC | Jul 24, 16:20 UTC | 35m |
| 2026-07-23 | N9636K | MCN → IOW | Jul 23, 23:15 UTC | Jul 24, 04:10 UTC | 4h 55m |
| 2026-07-20 | N9636K | - | Jul 20, 21:25 UTC | Jul 21, 02:15 UTC | 4h 49m |
| 2026-07-20 | N9636K | - | Jul 20, 18:25 UTC | Jul 20, 19:05 UTC | 40m |
| 2026-07-18 | N9636K | - | Jul 18, 10:25 UTC | Jul 18, 15:30 UTC | 5h 5m |
| 2026-07-17 | N9636K | - | Jul 17, 20:10 UTC | Jul 17, 21:39 UTC | 1h 30m |
| 2026-07-17 | N9636K | - | Jul 17, 14:55 UTC | Jul 17, 15:29 UTC | 35m |
| 2026-07-16 | N9636K | - | Jul 16, 01:10 UTC | Jul 16, 01:25 UTC | 15m |
| 2026-07-16 | N9636K | - | Jul 16, 00:25 UTC | Jul 16, 00:35 UTC | 10m |
| 2026-06-20 | N9636K | - | Jun 20, 03:09 UTC | Jun 20, 03:49 UTC | 40m |
| 2026-06-20 | N9636K | - | Jun 20, 00:09 UTC | Jun 20, 01:34 UTC | 1h 25m |
| 2026-06-19 | N9636K | - | Jun 19, 22:30 UTC | Jun 19, 23:25 UTC | 55m |
| 2026-06-19 | N9636K | - | Jun 19, 15:24 UTC | Jun 19, 16:44 UTC | 1h 20m |
| 2026-06-19 | N9636K | - | Jun 19, 12:34 UTC | Jun 19, 13:09 UTC | 35m |
| 2026-06-19 | N9636K | - | Jun 19, 11:04 UTC | Jun 19, 11:49 UTC | 45m |
| 2026-06-15 | N9636K | - | Jun 15, 23:39 UTC | Jun 16, 02:24 UTC | 2h 45m |
| 2026-06-15 | N9636K | - | Jun 15, 18:29 UTC | Jun 15, 21:25 UTC | 2h 55m |
| 2026-06-15 | N9636K | - | Jun 15, 16:35 UTC | Jun 15, 17:20 UTC | 45m |
| 2026-06-15 | N9636K | COS → COS | Jun 15, 12:25 UTC | Jun 15, 13:20 UTC | 55m |
| 2026-05-31 | N9636K | - | May 31, 00:05 UTC | May 31, 00:30 UTC | 25m |
| 2026-05-30 | N9636K | - | May 30, 16:45 UTC | May 30, 17:35 UTC | 50m |
| 2026-05-30 | N9636K | - | May 30, 15:25 UTC | May 30, 16:00 UTC | 35m |
| 2026-05-14 | N9636K | - | May 14, 17:15 UTC | May 14, 18:25 UTC | 1h 10m |
| 2026-05-14 | N9636K | - | May 14, 14:20 UTC | May 14, 14:40 UTC | 20m |
| 2026-05-14 | N9636K | - | May 14, 13:10 UTC | May 14, 13:30 UTC | 20m |
| 2026-05-13 | N9636K | - | May 13, 01:40 UTC | May 13, 03:30 UTC | 1h 50m |
| 2026-05-12 | N9636K | - | May 12, 22:01 UTC | May 12, 22:50 UTC | 50m |
| 2026-05-12 | N9636K | - | May 12, 19:25 UTC | May 12, 19:50 UTC | 25m |
| 2026-05-11 | N9636K | - | May 11, 01:50 UTC | May 11, 02:35 UTC | 45m |
| 2026-05-10 | N9636K | - | May 10, 23:50 UTC | May 11, 00:25 UTC | 35m |
| 2026-05-10 | N9636K | - | May 10, 21:44 UTC | May 10, 22:05 UTC | 20m |
| 2026-05-10 | N9636K | - | May 10, 18:05 UTC | May 10, 19:35 UTC | 1h 30m |
| 2026-05-09 | N9636K | - | May 9, 17:55 UTC | May 9, 18:10 UTC | 15m |
| 2026-04-29 | N9636K | - | Apr 29, 20:45 UTC | Apr 29, 20:55 UTC | 10m |
| 2026-04-23 | N9636K | - | Apr 23, 22:00 UTC | Apr 23, 22:50 UTC | 50m |
| 2026-04-23 | N9636K | - | Apr 23, 15:30 UTC | Apr 23, 16:40 UTC | 1h 10m |
| 2026-04-21 | N9636K | - | Apr 21, 19:20 UTC | Apr 21, 19:40 UTC | 20m |
| 2026-04-19 | N9636K | - | Apr 19, 19:40 UTC | Apr 19, 20:10 UTC | 30m |
| 2026-04-19 | N9636K | - | Apr 19, 16:05 UTC | Apr 19, 16:35 UTC | 30m |
| 2026-04-19 | N9636K | - | Apr 19, 13:00 UTC | Apr 19, 13:50 UTC | 50m |
| 2026-04-16 | N9636K | - | Apr 16, 23:20 UTC | Apr 17, 00:15 UTC | 55m |
| 2026-04-16 | N9636K | - | Apr 16, 22:54 UTC | Apr 16, 23:10 UTC | 15m |
| 2026-04-16 | N9636K | - | Apr 16, 20:20 UTC | Apr 16, 21:10 UTC | 50m |
| 2026-04-16 | N9636K | - | Apr 16, 17:15 UTC | Apr 16, 17:40 UTC | 25m |
| 2026-04-16 | N9636K | - | Apr 16, 16:55 UTC | Apr 16, 17:10 UTC | 15m |
| 2026-04-16 | N9636K | - | Apr 16, 13:15 UTC | Apr 16, 13:35 UTC | 20m |
| 2026-04-16 | N9636K | - | Apr 16, 12:34 UTC | Apr 16, 13:05 UTC | 30m |
| 2026-04-12 | N9636K | COS → COS | Apr 12, 17:25 UTC | Apr 12, 18:30 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 N9636K page for operator, model, and routing details .