sensors Mode-S transponder
A48F0D
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N393MM · PIPER PA-32R-300/301/301T · operated by PISTOL AVIATION LLC
- Hex
- A48F0D
- Octal
- 51107415
- Decimal
- 10,784,525
- Country
- US
- Tail
- N393MM
- Type
- P32R
- Flights observed
- 48
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address A48F0D 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 |
|---|---|---|---|
| N393MM | - | 48 | 2026-07-10 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-10 | N393MM | CUH → SWO | Jul 10, 20:00 UTC | Jul 10, 20:10 UTC | 10m |
| 2026-07-08 | N393MM | - | Jul 8, 23:10 UTC | Jul 9, 00:50 UTC | 1h 40m |
| 2026-07-07 | N393MM | - | Jul 7, 17:35 UTC | Jul 7, 19:15 UTC | 1h 40m |
| 2026-06-29 | N393MM | - | Jun 29, 22:49 UTC | Jun 29, 22:59 UTC | 10m |
| 2026-06-29 | N393MM | - | Jun 29, 20:40 UTC | Jun 29, 21:24 UTC | 45m |
| 2026-06-29 | N393MM | - | Jun 29, 00:05 UTC | Jun 29, 00:49 UTC | 45m |
| 2026-06-28 | N393MM | - | Jun 28, 22:55 UTC | Jun 28, 23:34 UTC | 40m |
| 2026-06-27 | N393MM | - | Jun 27, 15:45 UTC | Jun 27, 17:49 UTC | 2h 5m |
| 2026-06-21 | N393MM | - | Jun 21, 23:00 UTC | Jun 21, 23:40 UTC | 40m |
| 2026-06-21 | N393MM | - | Jun 21, 21:34 UTC | Jun 21, 22:15 UTC | 40m |
| 2026-06-20 | N393MM | - | Jun 20, 00:29 UTC | Jun 20, 02:04 UTC | 1h 35m |
| 2026-06-13 | N393MM | - | Jun 13, 01:00 UTC | Jun 13, 01:35 UTC | 35m |
| 2026-06-12 | N393MM | - | Jun 12, 21:10 UTC | Jun 12, 21:45 UTC | 35m |
| 2026-06-11 | N393MM | - | Jun 11, 16:15 UTC | Jun 11, 17:45 UTC | 1h 30m |
| 2026-06-11 | N393MM | - | Jun 11, 13:25 UTC | Jun 11, 14:40 UTC | 1h 15m |
| 2026-05-22 | N393MM | - | May 22, 18:20 UTC | May 22, 18:50 UTC | 30m |
| 2026-05-22 | N393MM | - | May 22, 12:50 UTC | May 22, 13:40 UTC | 50m |
| 2026-05-17 | N393MM | - | May 17, 21:40 UTC | May 17, 22:20 UTC | 40m |
| 2026-05-17 | N393MM | - | May 17, 19:45 UTC | May 17, 20:15 UTC | 30m |
| 2026-05-16 | N393MM | - | May 16, 03:20 UTC | May 16, 03:50 UTC | 30m |
| 2026-05-16 | N393MM | - | May 16, 01:50 UTC | May 16, 02:10 UTC | 20m |
| 2026-05-15 | N393MM | - | May 15, 21:25 UTC | May 15, 22:30 UTC | 1h 5m |
| 2026-05-13 | N393MM | - | May 13, 19:40 UTC | May 13, 20:10 UTC | 30m |
| 2026-05-13 | N393MM | - | May 13, 12:40 UTC | May 13, 13:35 UTC | 55m |
| 2026-05-11 | N393MM | - | May 11, 21:10 UTC | May 11, 22:05 UTC | 55m |
| 2026-05-10 | N393MM | - | May 10, 21:04 UTC | May 10, 21:40 UTC | 35m |
| 2026-05-10 | N393MM | - | May 10, 20:14 UTC | May 10, 20:30 UTC | 15m |
| 2026-05-10 | N393MM | - | May 10, 00:15 UTC | May 10, 00:34 UTC | 20m |
| 2026-05-08 | N393MM | - | May 8, 23:15 UTC | May 9, 00:30 UTC | 1h 15m |
| 2026-05-08 | N393MM | - | May 8, 20:50 UTC | May 8, 21:25 UTC | 35m |
| 2026-05-02 | N393MM | - | May 2, 23:15 UTC | May 2, 23:50 UTC | 35m |
| 2026-05-02 | N393MM | - | May 2, 19:05 UTC | May 2, 19:35 UTC | 30m |
| 2026-05-01 | N393MM | - | May 1, 19:15 UTC | May 1, 19:25 UTC | 10m |
| 2026-05-01 | N393MM | - | May 1, 17:35 UTC | May 1, 19:00 UTC | 1h 25m |
| 2026-05-01 | N393MM | - | May 1, 14:50 UTC | May 1, 15:45 UTC | 55m |
| 2026-05-01 | N393MM | - | May 1, 01:55 UTC | May 1, 02:50 UTC | 55m |
| 2026-05-01 | N393MM | RQO → PNX | May 1, 00:00 UTC | May 1, 01:20 UTC | 1h 20m |
| 2026-04-30 | N393MM | - | Apr 30, 23:10 UTC | Apr 30, 23:25 UTC | 15m |
| 2026-04-30 | N393MM | - | Apr 30, 22:00 UTC | Apr 30, 22:10 UTC | 10m |
| 2026-04-28 | N393MM | - | Apr 28, 22:55 UTC | Apr 29, 00:05 UTC | 1h 10m |
| 2026-04-28 | N393MM | - | Apr 28, 17:35 UTC | Apr 28, 18:55 UTC | 1h 20m |
| 2026-04-22 | N393MM | - | Apr 22, 18:35 UTC | Apr 22, 19:15 UTC | 40m |
| 2026-04-22 | N393MM | - | Apr 22, 13:45 UTC | Apr 22, 14:35 UTC | 50m |
| 2026-04-21 | N393MM | - | Apr 21, 18:20 UTC | Apr 21, 18:45 UTC | 25m |
| 2026-04-16 | N393MM | - | Apr 16, 21:14 UTC | Apr 16, 22:00 UTC | 45m |
| 2026-04-16 | N393MM | - | Apr 16, 20:35 UTC | Apr 16, 21:10 UTC | 35m |
| 2026-04-16 | N393MM | - | Apr 16, 19:15 UTC | Apr 16, 19:55 UTC | 40m |
| 2026-04-16 | N393MM | - | Apr 16, 18:40 UTC | Apr 16, 19:10 UTC | 30m |
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 N393MM page for operator, model, and routing details .