sensors Mode-S transponder
A65B61
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N509AB · LEARJET 60 · operated by LJ60-073 LLC
- Hex
- A65B61
- Octal
- 51455541
- Decimal
- 10,902,369
- Country
- US
- Tail
- N509AB
- Type
- LJ60
- Flights observed
- 165
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address A65B61 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 |
|---|---|---|---|
| FTD509 | - | 165 | 2026-07-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-23 | FTD509 | - | Jul 23, 23:40 UTC | Jul 24, 01:15 UTC | 1h 35m |
| 2026-07-23 | FTD509 | BNA → BUF | Jul 23, 17:25 UTC | Jul 23, 18:55 UTC | 1h 30m |
| 2026-07-22 | FTD509 | - | Jul 22, 21:30 UTC | Jul 22, 23:30 UTC | 2h 0m |
| 2026-07-22 | FTD509 | - | Jul 22, 16:55 UTC | Jul 22, 18:45 UTC | 1h 50m |
| 2026-07-22 | FTD509 | - | Jul 22, 14:15 UTC | Jul 22, 15:40 UTC | 1h 25m |
| 2026-07-21 | FTD509 | - | Jul 21, 12:35 UTC | Jul 21, 17:00 UTC | 4h 25m |
| 2026-07-20 | FTD509 | - | Jul 20, 15:40 UTC | Jul 20, 18:05 UTC | 2h 25m |
| 2026-07-20 | FTD509 | - | Jul 20, 14:25 UTC | Jul 20, 14:55 UTC | 30m |
| 2026-07-19 | FTD509 | - | Jul 19, 20:10 UTC | Jul 19, 22:20 UTC | 2h 10m |
| 2026-07-19 | FTD509 | - | Jul 19, 18:20 UTC | Jul 19, 19:05 UTC | 45m |
| 2026-07-19 | FTD509 | - | Jul 19, 15:45 UTC | Jul 19, 17:30 UTC | 1h 45m |
| 2026-07-19 | FTD509 | - | Jul 19, 12:15 UTC | Jul 19, 12:55 UTC | 40m |
| 2026-07-17 | FTD509 | - | Jul 17, 13:20 UTC | Jul 17, 15:29 UTC | 2h 10m |
| 2026-07-16 | FTD509 | BNA → SRQ | Jul 16, 20:35 UTC | Jul 16, 22:10 UTC | 1h 35m |
| 2026-07-16 | FTD509 | HIO → BNA | Jul 16, 00:10 UTC | Jul 16, 04:10 UTC | 4h 0m |
| 2026-07-15 | FTD509 | BNA → HIO | Jul 15, 15:45 UTC | Jul 15, 19:45 UTC | 4h 0m |
| 2026-07-13 | FTD509 | - | Jul 13, 22:35 UTC | Jul 13, 23:10 UTC | 35m |
| 2026-07-13 | FTD509 | - | Jul 13, 16:25 UTC | Jul 13, 17:00 UTC | 35m |
| 2026-07-12 | FTD509 | - | Jul 12, 21:05 UTC | Jul 12, 22:25 UTC | 1h 20m |
| 2026-07-12 | FTD509 | - | Jul 12, 14:35 UTC | Jul 12, 15:45 UTC | 1h 10m |
| 2026-07-11 | FTD509 | - | Jul 11, 19:30 UTC | Jul 11, 20:55 UTC | 1h 25m |
| 2026-07-11 | FTD509 | - | Jul 11, 12:15 UTC | Jul 11, 13:35 UTC | 1h 20m |
| 2026-07-10 | FTD509 | - | Jul 10, 05:15 UTC | Jul 10, 08:20 UTC | 3h 5m |
| 2026-07-09 | FTD509 | - | Jul 9, 22:30 UTC | Jul 10, 01:25 UTC | 2h 55m |
| 2026-07-09 | FTD509 | - | Jul 9, 17:50 UTC | Jul 9, 18:55 UTC | 1h 5m |
| 2026-07-09 | FTD509 | - | Jul 9, 12:40 UTC | Jul 9, 13:50 UTC | 1h 10m |
| 2026-07-08 | FTD509 | - | Jul 8, 18:10 UTC | Jul 8, 19:15 UTC | 1h 5m |
| 2026-07-08 | FTD509 | - | Jul 8, 12:25 UTC | Jul 8, 13:30 UTC | 1h 5m |
| 2026-07-08 | FTD509 | AGC → BNA | Jul 8, 02:25 UTC | Jul 8, 03:35 UTC | 1h 10m |
| 2026-07-07 | FTD509 | BNA → AGC | Jul 7, 20:30 UTC | Jul 7, 21:40 UTC | 1h 10m |
| 2026-07-06 | FTD509 | - | Jul 6, 16:50 UTC | Jul 6, 19:30 UTC | 2h 40m |
| 2026-07-06 | FTD509 | - | Jul 6, 10:15 UTC | Jul 6, 12:30 UTC | 2h 15m |
| 2026-07-05 | FTD509 | BOS → BNA | Jul 5, 19:35 UTC | Jul 5, 21:50 UTC | 2h 15m |
| 2026-07-05 | FTD509 | - | Jul 5, 14:05 UTC | Jul 5, 14:40 UTC | 35m |
| 2026-07-02 | FTD509 | - | Jul 2, 14:00 UTC | Jul 2, 16:40 UTC | 2h 40m |
| 2026-06-30 | FTD509 | - | Jun 30, 18:25 UTC | Jun 30, 19:10 UTC | 45m |
| 2026-06-30 | FTD509 | - | Jun 30, 12:35 UTC | Jun 30, 13:25 UTC | 50m |
| 2026-06-29 | FTD509 | - | Jun 29, 23:25 UTC | Jun 30, 00:45 UTC | 1h 20m |
| 2026-06-29 | FTD509 | - | Jun 29, 20:09 UTC | Jun 29, 22:10 UTC | 2h 0m |
| 2026-06-29 | FTD509 | - | Jun 29, 17:19 UTC | Jun 29, 17:59 UTC | 40m |
| 2026-06-29 | FTD509 | - | Jun 29, 12:55 UTC | Jun 29, 14:50 UTC | 1h 55m |
| 2026-06-28 | FTD509 | - | Jun 28, 01:29 UTC | Jun 28, 03:29 UTC | 2h 0m |
| 2026-06-27 | FTD509 | - | Jun 27, 17:04 UTC | Jun 27, 19:19 UTC | 2h 15m |
| 2026-06-27 | FTD509 | - | Jun 27, 15:14 UTC | Jun 27, 16:10 UTC | 55m |
| 2026-06-26 | FTD509 | - | Jun 26, 20:10 UTC | Jun 26, 21:35 UTC | 1h 25m |
| 2026-06-26 | FTD509 | - | Jun 26, 12:59 UTC | Jun 26, 14:50 UTC | 1h 50m |
| 2026-06-25 | FTD509 | - | Jun 25, 20:05 UTC | Jun 25, 20:39 UTC | 35m |
| 2026-06-24 | FTD509 | - | Jun 24, 21:19 UTC | Jun 24, 23:50 UTC | 2h 30m |
| 2026-06-23 | FTD509 | - | Jun 23, 15:24 UTC | Jun 23, 17:44 UTC | 2h 20m |
| 2026-06-23 | FTD509 | - | Jun 23, 11:45 UTC | Jun 23, 12:09 UTC | 25m |
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 N509AB page for operator, model, and routing details .