sensors Mode-S transponder
A88370
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N648F · CESSNA 182 Skylane · operated by BFC N648F
- Hex
- A88370
- Octal
- 52101560
- Decimal
- 11,043,696
- Country
- US
- Tail
- N648F
- Type
- C182
- Flights observed
- 45
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- Jul 25, 07:25 UTC
Last known position
Country allocation
The ICAO 24-bit address A88370 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 |
|---|---|---|---|
| N648F | - | 45 | 2026-07-25 |
Recent flights last 45
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | N648F | - | Jul 25, 07:05 UTC | Jul 25, 07:20 UTC | 15m |
| 2026-07-25 | N648F | - | Jul 25, 05:35 UTC | Jul 25, 06:35 UTC | 1h 0m |
| 2026-07-24 | N648F | - | Jul 24, 21:25 UTC | Jul 24, 22:20 UTC | 55m |
| 2026-07-24 | N648F | BJC → APA | Jul 24, 20:30 UTC | Jul 24, 20:50 UTC | 20m |
| 2026-07-23 | N648F | GXY → BJC | Jul 23, 14:25 UTC | Jul 23, 16:20 UTC | 1h 55m |
| 2026-07-23 | N648F | BJC → GXY | Jul 23, 13:20 UTC | Jul 23, 13:50 UTC | 30m |
| 2026-07-21 | N648F | BJC → BJC | Jul 21, 12:55 UTC | Jul 21, 15:15 UTC | 2h 20m |
| 2026-07-16 | N648F | BJC → BJC | Jul 16, 12:14 UTC | Jul 16, 13:25 UTC | 1h 10m |
| 2026-07-16 | N648F | BJC → BJC | Jul 16, 03:00 UTC | Jul 16, 03:55 UTC | 55m |
| 2026-07-14 | N648F | BJC → BJC | Jul 14, 13:10 UTC | Jul 14, 15:35 UTC | 2h 25m |
| 2026-07-14 | N648F | BJC → BJC | Jul 14, 02:35 UTC | Jul 14, 02:45 UTC | 10m |
| 2026-07-13 | N648F | - | Jul 13, 16:15 UTC | Jul 13, 17:20 UTC | 1h 5m |
| 2026-07-13 | N648F | - | Jul 13, 13:00 UTC | Jul 13, 14:20 UTC | 1h 20m |
| 2026-07-10 | N648F | - | Jul 10, 18:05 UTC | Jul 10, 19:25 UTC | 1h 20m |
| 2026-07-10 | N648F | - | Jul 10, 15:20 UTC | Jul 10, 16:30 UTC | 1h 10m |
| 2026-07-07 | N648F | BJC → BJC | Jul 7, 14:00 UTC | Jul 7, 15:20 UTC | 1h 20m |
| 2026-07-03 | N648F | BJC → BJC | Jul 3, 03:05 UTC | Jul 3, 03:45 UTC | 40m |
| 2026-07-02 | N648F | BJC → BJC | Jul 2, 13:55 UTC | Jul 2, 15:35 UTC | 1h 40m |
| 2026-06-30 | N648F | BJC → BJC | Jun 30, 16:05 UTC | Jun 30, 18:00 UTC | 1h 55m |
| 2026-06-30 | N648F | BJC → BJC | Jun 30, 13:10 UTC | Jun 30, 15:00 UTC | 1h 50m |
| 2026-06-29 | N648F | - | Jun 29, 02:45 UTC | Jun 29, 03:29 UTC | 45m |
| 2026-06-28 | N648F | - | Jun 28, 23:20 UTC | Jun 29, 00:29 UTC | 1h 10m |
| 2026-06-23 | N648F | BJC → BJC | Jun 23, 10:19 UTC | Jun 23, 10:44 UTC | 25m |
| 2026-06-01 | N648F | BJC → BJC | Jun 1, 03:20 UTC | Jun 1, 04:15 UTC | 55m |
| 2026-05-31 | N648F | BJC → BJC | May 31, 22:30 UTC | May 31, 22:35 UTC | 5m |
| 2026-05-27 | N648F | BJC → BJC | May 27, 19:55 UTC | May 27, 20:25 UTC | 30m |
| 2026-05-26 | N648F | BJC → BJC | May 26, 16:45 UTC | May 26, 17:44 UTC | 1h 0m |
| 2026-05-21 | N648F | BJC → BJC | May 21, 15:55 UTC | May 21, 17:20 UTC | 1h 25m |
| 2026-05-07 | N648F | - | May 7, 16:35 UTC | May 7, 18:45 UTC | 2h 10m |
| 2026-05-07 | N648F | BJC → BJC | May 7, 15:30 UTC | May 7, 15:35 UTC | 5m |
| 2026-05-03 | N648F | - | May 3, 22:34 UTC | May 3, 23:25 UTC | 50m |
| 2026-05-03 | N648F | - | May 3, 15:30 UTC | May 3, 18:55 UTC | 3h 25m |
| 2026-04-30 | N648F | - | Apr 30, 16:50 UTC | Apr 30, 17:20 UTC | 30m |
| 2026-04-29 | N648F | - | Apr 29, 21:20 UTC | Apr 29, 21:30 UTC | 10m |
| 2026-04-29 | N648F | - | Apr 29, 19:15 UTC | Apr 29, 20:00 UTC | 45m |
| 2026-04-29 | N648F | - | Apr 29, 17:35 UTC | Apr 29, 18:35 UTC | 1h 0m |
| 2026-04-29 | N648F | - | Apr 29, 14:50 UTC | Apr 29, 15:45 UTC | 55m |
| 2026-04-19 | N648F | BJC → BJC | Apr 19, 20:55 UTC | Apr 19, 23:35 UTC | 2h 40m |
| 2026-04-18 | N648F | - | Apr 18, 21:35 UTC | Apr 18, 22:35 UTC | 1h 0m |
| 2026-04-18 | N648F | - | Apr 18, 20:05 UTC | Apr 18, 20:35 UTC | 30m |
| 2026-04-18 | N648F | - | Apr 18, 18:10 UTC | Apr 18, 18:50 UTC | 40m |
| 2026-04-16 | N648F | - | Apr 16, 20:00 UTC | Apr 16, 20:40 UTC | 40m |
| 2026-04-16 | N648F | - | Apr 16, 18:30 UTC | Apr 16, 18:55 UTC | 25m |
| 2026-04-16 | N648F | - | Apr 16, 15:15 UTC | Apr 16, 16:30 UTC | 1h 15m |
| 2026-04-14 | N648F | BJC → BJC | Apr 14, 16:05 UTC | Apr 14, 16:15 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 N648F page for operator, model, and routing details .