sensors Mode-S transponder
AA580F
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N766CL · CESSNA 700 Citation Longitude
- Hex
- AA580F
- Octal
- 52454017
- Decimal
- 11,163,663
- Country
- US
- Tail
- N766CL
- Type
- C700
- Flights observed
- 52
- Distinct callsigns
- 6
- Country
- US
- Last broadcast
- 20d ago
Last known position
Country allocation
The ICAO 24-bit address AA580F 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 6 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | N766CL | - | Jul 17, 20:50 UTC | Jul 17, 23:55 UTC | 3h 5m |
| 2026-07-17 | N766CL | - | Jul 17, 19:25 UTC | Jul 17, 20:10 UTC | 45m |
| 2026-07-17 | N766CL | - | Jul 17, 17:15 UTC | Jul 17, 18:00 UTC | 45m |
| 2026-07-17 | N766CL | - | Jul 17, 11:50 UTC | Jul 17, 14:50 UTC | 3h 0m |
| 2026-07-15 | N766CL | - | Jul 15, 19:15 UTC | Jul 15, 21:30 UTC | 2h 15m |
| 2026-07-15 | N766CL | - | Jul 15, 12:55 UTC | Jul 15, 18:25 UTC | 5h 30m |
| 2026-07-14 | N766CL | - | Jul 14, 18:00 UTC | Jul 14, 20:10 UTC | 2h 10m |
| 2026-07-10 | N766CL | - | Jul 10, 20:35 UTC | Jul 10, 23:10 UTC | 2h 35m |
| 2026-07-10 | N766CL | - | Jul 10, 16:30 UTC | Jul 10, 19:35 UTC | 3h 5m |
| 2026-07-10 | N766CL | - | Jul 10, 00:55 UTC | Jul 10, 03:25 UTC | 2h 30m |
| 2026-07-09 | N766CL | - | Jul 9, 20:35 UTC | Jul 10, 00:25 UTC | 3h 50m |
| 2026-07-09 | N766CL | - | Jul 9, 18:15 UTC | Jul 9, 19:05 UTC | 50m |
| 2026-07-06 | N766CL | - | Jul 6, 15:20 UTC | Jul 6, 16:35 UTC | 1h 15m |
| 2026-07-02 | N766CL | ICT → ICT | Jul 2, 11:40 UTC | Jul 2, 16:25 UTC | 4h 45m |
| 2026-07-01 | N766CL | - | Jul 1, 18:40 UTC | Jul 1, 23:50 UTC | 5h 10m |
| 2026-07-01 | N766CL | - | Jul 1, 15:25 UTC | Jul 1, 17:50 UTC | 2h 25m |
| 2026-06-30 | N766CL | - | Jun 30, 19:30 UTC | Jun 30, 20:15 UTC | 45m |
| 2026-06-30 | N766CL | - | Jun 30, 17:20 UTC | Jun 30, 17:50 UTC | 30m |
| 2026-06-30 | N766CL | - | Jun 30, 12:50 UTC | Jun 30, 15:30 UTC | 2h 40m |
| 2026-06-28 | N766CL | - | Jun 28, 16:05 UTC | Jun 28, 17:19 UTC | 1h 15m |
| 2026-06-28 | N766CL | - | Jun 28, 13:59 UTC | Jun 28, 15:40 UTC | 1h 40m |
| 2026-06-28 | N766CL | - | Jun 28, 01:10 UTC | Jun 28, 01:55 UTC | 45m |
| 2026-06-27 | DOVE48 | - | Jun 27, 23:10 UTC | Jun 28, 00:35 UTC | 1h 25m |
| 2026-06-27 | DOVE48 | - | Jun 27, 21:29 UTC | Jun 27, 22:40 UTC | 1h 10m |
| 2026-06-26 | N766CL | - | Jun 26, 20:40 UTC | Jun 26, 22:14 UTC | 1h 35m |
| 2026-06-26 | N766CL | CUN → MSY | Jun 26, 18:49 UTC | Jun 26, 20:15 UTC | 1h 25m |
| 2026-06-12 | N766CL | - | Jun 12, 21:50 UTC | Jun 12, 22:45 UTC | 55m |
| 2026-06-12 | N766CL | - | Jun 12, 01:55 UTC | Jun 12, 04:05 UTC | 2h 10m |
| 2026-06-11 | N766CL | - | Jun 11, 20:05 UTC | Jun 11, 22:40 UTC | 2h 35m |
| 2026-06-10 | N766CL | - | Jun 10, 22:15 UTC | Jun 10, 23:30 UTC | 1h 15m |
| 2026-06-10 | N766CL | - | Jun 10, 17:40 UTC | Jun 10, 18:50 UTC | 1h 10m |
| 2026-06-05 | N766CL | - | Jun 5, 13:30 UTC | Jun 5, 15:05 UTC | 1h 35m |
| 2026-06-04 | N766CL | - | Jun 4, 18:10 UTC | Jun 4, 19:45 UTC | 1h 35m |
| 2026-05-27 | N766CL | - | May 27, 19:00 UTC | May 27, 20:15 UTC | 1h 15m |
| 2026-05-27 | N766CL | - | May 27, 14:50 UTC | May 27, 16:10 UTC | 1h 20m |
| 2026-05-22 | N766CL | - | May 22, 19:50 UTC | May 22, 21:45 UTC | 1h 55m |
| 2026-05-22 | N766CL | - | May 22, 18:15 UTC | May 22, 19:00 UTC | 45m |
| 2026-05-22 | N766CL | - | May 22, 15:50 UTC | May 22, 16:25 UTC | 35m |
| 2026-05-21 | N766CL | - | May 21, 21:50 UTC | May 21, 22:30 UTC | 40m |
| 2026-05-21 | N766CL | IAD → CRW | May 21, 19:50 UTC | May 21, 20:35 UTC | 45m |
| 2026-05-21 | N766CL | - | May 21, 14:45 UTC | May 21, 16:50 UTC | 2h 5m |
| 2026-05-20 | N766CL | - | May 20, 23:35 UTC | May 21, 00:30 UTC | 55m |
| 2026-05-20 | N766CL | - | May 20, 21:50 UTC | May 20, 22:45 UTC | 55m |
| 2026-05-20 | N766CL | - | May 20, 14:15 UTC | May 20, 15:45 UTC | 1h 30m |
| 2026-05-20 | N766CL | - | May 20, 11:35 UTC | May 20, 12:50 UTC | 1h 15m |
| 2026-05-15 | N766CL | - | May 15, 18:50 UTC | May 15, 21:00 UTC | 2h 10m |
| 2026-05-11 | CITT33 | - | May 11, 16:00 UTC | May 11, 17:00 UTC | 1h 1m |
| 2026-05-06 | CITT40 | - | May 6, 20:45 UTC | May 6, 21:05 UTC | 20m |
| 2026-04-27 | CITT49 | - | Apr 27, 15:25 UTC | Apr 27, 16:40 UTC | 1h 15m |
| 2026-04-25 | CITT45 | - | Apr 25, 15:25 UTC | Apr 25, 16:55 UTC | 1h 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 N766CL page for operator, model, and routing details .