sensors Mode-S transponder
A69B8F
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N525AP · CESSNA 525B Citation CJ3
- Hex
- A69B8F
- Octal
- 51515617
- Decimal
- 10,918,799
- Country
- US
- Tail
- N525AP
- Type
- C25B
- Flights observed
- 49
- Distinct callsigns
- 2
- Country
- US
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address A69B8F 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 2 distinct
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | N915AB | AUS → LRD | Jul 12, 18:50 UTC | Jul 12, 19:25 UTC | 35m |
| 2026-07-12 | N915AB | - | Jul 12, 15:20 UTC | Jul 12, 17:55 UTC | 2h 35m |
| 2026-07-11 | N915AB | - | Jul 11, 15:05 UTC | Jul 11, 17:45 UTC | 2h 40m |
| 2026-07-11 | N915AB | LRD → AUS | Jul 11, 13:25 UTC | Jul 11, 14:05 UTC | 40m |
| 2026-07-10 | N525AP | - | Jul 10, 14:25 UTC | Jul 10, 17:25 UTC | 3h 0m |
| 2026-07-09 | N915AB | - | Jul 9, 17:35 UTC | Jul 9, 18:30 UTC | 55m |
| 2026-07-09 | N915AB | - | Jul 9, 15:30 UTC | Jul 9, 16:25 UTC | 55m |
| 2026-07-06 | N915AB | - | Jul 6, 18:20 UTC | Jul 6, 18:55 UTC | 35m |
| 2026-07-06 | N915AB | - | Jul 6, 13:20 UTC | Jul 6, 14:00 UTC | 40m |
| 2026-07-02 | N525AP | - | Jul 2, 11:45 UTC | Jul 2, 14:35 UTC | 2h 50m |
| 2026-07-01 | N525AP | - | Jul 1, 18:55 UTC | Jul 1, 20:15 UTC | 1h 20m |
| 2026-07-01 | N525AP | - | Jul 1, 13:55 UTC | Jul 1, 14:05 UTC | 10m |
| 2026-07-01 | N525AP | - | Jul 1, 11:55 UTC | Jul 1, 13:10 UTC | 1h 15m |
| 2026-06-29 | N915AB | - | Jun 29, 22:19 UTC | Jun 29, 22:55 UTC | 35m |
| 2026-06-29 | N915AB | - | Jun 29, 19:54 UTC | Jun 29, 21:19 UTC | 1h 25m |
| 2026-06-29 | N915AB | - | Jun 29, 16:39 UTC | Jun 29, 19:05 UTC | 2h 25m |
| 2026-06-26 | N915AB | - | Jun 26, 17:15 UTC | Jun 26, 19:39 UTC | 2h 25m |
| 2026-06-26 | N915AB | - | Jun 26, 15:34 UTC | Jun 26, 16:24 UTC | 50m |
| 2026-06-24 | N915AB | - | Jun 24, 17:34 UTC | Jun 24, 18:25 UTC | 50m |
| 2026-06-24 | N915AB | LRD → IAH | Jun 24, 15:35 UTC | Jun 24, 16:40 UTC | 1h 5m |
| 2026-06-23 | N915AB | - | Jun 23, 21:05 UTC | Jun 23, 21:45 UTC | 40m |
| 2026-06-23 | N915AB | - | Jun 23, 12:45 UTC | Jun 23, 13:24 UTC | 40m |
| 2026-06-08 | N525AP | - | Jun 8, 20:05 UTC | Jun 8, 20:20 UTC | 15m |
| 2026-06-08 | N525AP | - | Jun 8, 00:45 UTC | Jun 8, 01:55 UTC | 1h 10m |
| 2026-06-07 | N915AB | AUS → LRD | Jun 7, 03:05 UTC | Jun 7, 03:50 UTC | 45m |
| 2026-06-06 | N915AB | - | Jun 6, 20:49 UTC | Jun 6, 21:35 UTC | 45m |
| 2026-06-05 | N525AP | ORL → PDK | Jun 5, 15:40 UTC | Jun 5, 16:50 UTC | 1h 10m |
| 2026-06-03 | N915AB | - | Jun 3, 05:20 UTC | Jun 3, 06:15 UTC | 55m |
| 2026-06-03 | N915AB | - | Jun 3, 03:05 UTC | Jun 3, 04:20 UTC | 1h 15m |
| 2026-06-02 | N525AP | - | Jun 2, 20:30 UTC | Jun 2, 21:05 UTC | 35m |
| 2026-06-02 | N525AP | - | Jun 2, 18:30 UTC | Jun 2, 19:20 UTC | 50m |
| 2026-06-02 | N525AP | - | Jun 2, 16:40 UTC | Jun 2, 17:15 UTC | 35m |
| 2026-06-01 | N525AP | - | Jun 1, 23:50 UTC | Jun 2, 01:00 UTC | 1h 10m |
| 2026-06-01 | N525AP | ORL → PDK | Jun 1, 17:40 UTC | Jun 1, 19:00 UTC | 1h 20m |
| 2026-05-31 | N915AB | LAS → LRD | May 31, 17:20 UTC | May 31, 20:35 UTC | 3h 15m |
| 2026-05-29 | N915AB | - | May 29, 16:15 UTC | May 29, 19:20 UTC | 3h 5m |
| 2026-05-29 | N915AB | - | May 29, 15:35 UTC | May 29, 15:40 UTC | 5m |
| 2026-05-20 | N525AP | - | May 20, 00:30 UTC | May 20, 01:30 UTC | 1h 0m |
| 2026-05-19 | N525AP | - | May 19, 13:55 UTC | May 19, 15:15 UTC | 1h 20m |
| 2026-05-17 | N915AB | AUS → LRD | May 17, 15:55 UTC | May 17, 16:35 UTC | 40m |
| 2026-05-16 | N915AB | LRD → AUS | May 16, 19:30 UTC | May 16, 20:15 UTC | 45m |
| 2026-05-15 | N915AB | - | May 15, 18:10 UTC | May 15, 18:40 UTC | 30m |
| 2026-05-11 | N525AP | ORL → PDK | May 11, 13:25 UTC | May 11, 14:35 UTC | 1h 10m |
| 2026-04-27 | N525AP | PNS → ORL | Apr 27, 20:00 UTC | Apr 27, 21:35 UTC | 1h 35m |
| 2026-04-27 | N525AP | - | Apr 27, 16:10 UTC | Apr 27, 16:45 UTC | 35m |
| 2026-04-27 | N525AP | - | Apr 27, 14:45 UTC | Apr 27, 15:25 UTC | 40m |
| 2026-04-20 | N525AP | - | Apr 20, 18:35 UTC | Apr 20, 19:45 UTC | 1h 10m |
| 2026-04-20 | N525AP | - | Apr 20, 13:25 UTC | Apr 20, 14:45 UTC | 1h 20m |
| 2026-04-13 | N525AP | - | Apr 13, 21:50 UTC | Apr 13, 22:00 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 N525AP page for operator, model, and routing details .