sensors Mode-S transponder
A5A654
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N463SD · GULFSTREAM G500 · operated by TD LEASING LLC
- Hex
- A5A654
- Octal
- 51323124
- Decimal
- 10,856,020
- Country
- US
- Tail
- N463SD
- Type
- GA5C
- Flights observed
- 75
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 13d ago
Last known position
Country allocation
The ICAO 24-bit address A5A654 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 |
|---|---|---|---|
| N463SD | - | 75 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | N463SD | - | Jul 26, 02:50 UTC | Jul 26, 11:00 UTC | 8h 11m |
| 2026-07-26 | N463SD | - | Jul 26, 00:20 UTC | Jul 26, 01:00 UTC | 40m |
| 2026-07-20 | N463SD | - | Jul 20, 15:25 UTC | Jul 20, 17:20 UTC | 1h 55m |
| 2026-07-19 | N463SD | - | Jul 19, 16:15 UTC | Jul 19, 18:30 UTC | 2h 15m |
| 2026-07-16 | N463SD | - | Jul 16, 16:09 UTC | Jul 16, 18:15 UTC | 2h 5m |
| 2026-07-16 | N463SD | - | Jul 16, 12:25 UTC | Jul 16, 14:25 UTC | 2h 0m |
| 2026-07-15 | N463SD | - | Jul 15, 16:00 UTC | Jul 15, 19:20 UTC | 3h 20m |
| 2026-07-14 | N463SD | DTW → DFW | Jul 14, 12:10 UTC | Jul 14, 14:05 UTC | 1h 55m |
| 2026-07-13 | N463SD | - | Jul 13, 15:30 UTC | Jul 13, 16:40 UTC | 1h 10m |
| 2026-07-12 | N463SD | - | Jul 12, 21:40 UTC | Jul 12, 23:40 UTC | 2h 0m |
| 2026-07-12 | N463SD | - | Jul 12, 18:35 UTC | Jul 12, 19:40 UTC | 1h 5m |
| 2026-07-12 | N463SD | - | Jul 12, 02:55 UTC | Jul 12, 04:05 UTC | 1h 10m |
| 2026-07-10 | N463SD | - | Jul 10, 18:35 UTC | Jul 10, 18:55 UTC | 20m |
| 2026-07-10 | N463SD | BJC → MMU | Jul 10, 14:20 UTC | Jul 10, 17:10 UTC | 2h 50m |
| 2026-07-10 | N463SD | - | Jul 10, 00:10 UTC | Jul 10, 00:30 UTC | 20m |
| 2026-07-09 | N463SD | - | Jul 9, 20:05 UTC | Jul 9, 23:10 UTC | 3h 5m |
| 2026-07-09 | N463SD | BJC → ORL | Jul 9, 15:50 UTC | Jul 9, 18:50 UTC | 3h 0m |
| 2026-07-07 | N463SD | - | Jul 7, 18:05 UTC | Jul 7, 21:20 UTC | 3h 15m |
| 2026-07-07 | N463SD | - | Jul 7, 14:25 UTC | Jul 7, 15:55 UTC | 1h 30m |
| 2026-07-03 | N463SD | - | Jul 3, 18:50 UTC | Jul 3, 21:05 UTC | 2h 15m |
| 2026-07-01 | N463SD | - | Jul 1, 23:20 UTC | Jul 1, 23:55 UTC | 35m |
| 2026-07-01 | N463SD | - | Jul 1, 20:30 UTC | Jul 1, 22:30 UTC | 2h 0m |
| 2026-07-01 | N463SD | - | Jul 1, 17:20 UTC | Jul 1, 18:50 UTC | 1h 30m |
| 2026-06-30 | N463SD | - | Jun 30, 16:10 UTC | Jun 30, 22:55 UTC | 6h 45m |
| 2026-06-30 | N463SD | - | Jun 30, 14:05 UTC | Jun 30, 14:20 UTC | 15m |
| 2026-06-28 | N463SD | - | Jun 28, 22:39 UTC | Jun 28, 23:34 UTC | 55m |
| 2026-06-28 | N463SD | - | Jun 28, 20:25 UTC | Jun 28, 22:04 UTC | 1h 40m |
| 2026-06-28 | N463SD | - | Jun 28, 17:44 UTC | Jun 28, 19:44 UTC | 2h 0m |
| 2026-06-25 | N463SD | - | Jun 25, 17:39 UTC | Jun 25, 19:49 UTC | 2h 10m |
| 2026-06-25 | N463SD | - | Jun 25, 13:45 UTC | Jun 25, 15:29 UTC | 1h 45m |
| 2026-06-25 | N463SD | - | Jun 25, 11:59 UTC | Jun 25, 13:00 UTC | 1h 0m |
| 2026-06-19 | N463SD | - | Jun 19, 21:24 UTC | Jun 19, 22:24 UTC | 1h 0m |
| 2026-06-19 | N463SD | - | Jun 19, 11:20 UTC | Jun 19, 20:40 UTC | 9h 20m |
| 2026-06-16 | N463SD | - | Jun 16, 11:05 UTC | Jun 16, 11:49 UTC | 45m |
| 2026-06-15 | N463SD | - | Jun 15, 08:00 UTC | Jun 15, 09:35 UTC | 1h 35m |
| 2026-06-15 | N463SD | - | Jun 15, 06:24 UTC | Jun 15, 06:49 UTC | 25m |
| 2026-06-12 | N463SD | BOD → TLS | Jun 12, 09:40 UTC | Jun 12, 10:10 UTC | 30m |
| 2026-06-12 | N463SD | BNA → BOD | Jun 12, 00:45 UTC | Jun 12, 08:30 UTC | 7h 45m |
| 2026-06-10 | N463SD | - | Jun 10, 15:50 UTC | Jun 10, 17:20 UTC | 1h 30m |
| 2026-06-10 | N463SD | - | Jun 10, 12:45 UTC | Jun 10, 14:40 UTC | 1h 55m |
| 2026-06-10 | N463SD | - | Jun 10, 10:25 UTC | Jun 10, 11:00 UTC | 35m |
| 2026-06-02 | N463SD | - | Jun 2, 15:20 UTC | Jun 2, 18:25 UTC | 3h 5m |
| 2026-06-01 | N463SD | - | Jun 1, 21:05 UTC | Jun 2, 18:25 UTC | 21h 20m |
| 2026-06-01 | N463SD | - | Jun 1, 19:05 UTC | Jun 2, 18:25 UTC | 23h 20m |
| 2026-06-01 | N463SD | - | Jun 1, 17:05 UTC | Jun 2, 17:00 UTC | 23h 55m |
| 2026-06-01 | N463SD | - | Jun 1, 16:40 UTC | Jun 1, 21:45 UTC | 5h 5m |
| 2026-06-01 | N463SD | - | Jun 1, 14:55 UTC | Jun 1, 15:30 UTC | 35m |
| 2026-05-29 | N463SD | - | May 29, 22:25 UTC | May 30, 00:50 UTC | 2h 25m |
| 2026-05-29 | N463SD | - | May 29, 20:35 UTC | May 29, 20:45 UTC | 10m |
| 2026-05-29 | N463SD | - | May 29, 15:20 UTC | May 29, 16:40 UTC | 1h 20m |
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 N463SD page for operator, model, and routing details .