sensors Mode-S transponder
A63B9D
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N500TD · PIPER PA-23 · operated by PACIFIC FLEET AVIATION LLC
- Hex
- A63B9D
- Octal
- 51435635
- Decimal
- 10,894,237
- Country
- US
- Tail
- N500TD
- Type
- PA23
- Flights observed
- 61
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 15d ago
Last known position
Country allocation
The ICAO 24-bit address A63B9D 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 |
|---|---|---|---|
| N500TD | - | 61 | 2026-07-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-02 | N500TD | - | Jul 2, 14:45 UTC | Jul 2, 16:05 UTC | 1h 20m |
| 2026-06-30 | N500TD | - | Jun 30, 18:25 UTC | Jun 30, 19:00 UTC | 35m |
| 2026-06-30 | N500TD | - | Jun 30, 13:25 UTC | Jun 30, 14:45 UTC | 1h 20m |
| 2026-06-28 | N500TD | - | Jun 28, 14:50 UTC | Jun 28, 15:40 UTC | 50m |
| 2026-06-27 | N500TD | - | Jun 27, 00:25 UTC | Jun 27, 00:55 UTC | 30m |
| 2026-06-26 | N500TD | - | Jun 26, 19:45 UTC | Jun 26, 20:20 UTC | 35m |
| 2026-06-26 | N500TD | - | Jun 26, 15:34 UTC | Jun 26, 18:39 UTC | 3h 5m |
| 2026-06-26 | N500TD | - | Jun 26, 13:19 UTC | Jun 26, 14:35 UTC | 1h 15m |
| 2026-06-25 | N500TD | - | Jun 25, 23:05 UTC | Jun 25, 23:49 UTC | 45m |
| 2026-06-24 | N500TD | - | Jun 24, 17:45 UTC | Jun 24, 19:10 UTC | 1h 25m |
| 2026-06-21 | N500TD | - | Jun 21, 20:40 UTC | Jun 21, 20:59 UTC | 20m |
| 2026-06-21 | N500TD | - | Jun 21, 18:10 UTC | Jun 21, 18:20 UTC | 10m |
| 2026-06-20 | N500TD | - | Jun 20, 20:14 UTC | Jun 20, 23:29 UTC | 3h 15m |
| 2026-06-19 | N500TD | - | Jun 19, 22:55 UTC | Jun 20, 01:44 UTC | 2h 50m |
| 2026-06-17 | N500TD | - | Jun 17, 20:45 UTC | Jun 17, 21:20 UTC | 35m |
| 2026-06-16 | N500TD | BNG → BNG | Jun 16, 21:10 UTC | Jun 17, 00:50 UTC | 3h 40m |
| 2026-06-15 | N500TD | - | Jun 15, 16:40 UTC | Jun 15, 21:04 UTC | 4h 25m |
| 2026-06-14 | N500TD | - | Jun 14, 15:55 UTC | Jun 14, 17:45 UTC | 1h 50m |
| 2026-06-14 | N500TD | - | Jun 14, 13:40 UTC | Jun 14, 14:50 UTC | 1h 10m |
| 2026-06-13 | N500TD | - | Jun 13, 15:45 UTC | Jun 13, 18:40 UTC | 2h 55m |
| 2026-06-13 | N500TD | - | Jun 13, 13:45 UTC | Jun 13, 15:00 UTC | 1h 15m |
| 2026-06-12 | N500TD | - | Jun 12, 17:15 UTC | Jun 12, 18:35 UTC | 1h 20m |
| 2026-06-12 | N500TD | - | Jun 12, 14:45 UTC | Jun 12, 16:30 UTC | 1h 45m |
| 2026-06-10 | N500TD | - | Jun 10, 15:40 UTC | Jun 10, 15:55 UTC | 15m |
| 2026-05-28 | N500TD | - | May 28, 14:35 UTC | May 28, 15:05 UTC | 30m |
| 2026-05-27 | N500TD | - | May 27, 23:00 UTC | May 27, 23:25 UTC | 25m |
| 2026-05-27 | N500TD | - | May 27, 21:45 UTC | May 27, 22:20 UTC | 35m |
| 2026-05-27 | N500TD | - | May 27, 20:10 UTC | May 27, 20:40 UTC | 30m |
| 2026-05-27 | N500TD | - | May 27, 16:25 UTC | May 27, 17:00 UTC | 35m |
| 2026-05-22 | N500TD | - | May 22, 19:25 UTC | May 22, 19:40 UTC | 15m |
| 2026-05-21 | N500TD | - | May 21, 18:10 UTC | May 21, 19:30 UTC | 1h 20m |
| 2026-05-20 | N500TD | - | May 20, 20:35 UTC | May 21, 01:00 UTC | 4h 25m |
| 2026-05-18 | N500TD | - | May 18, 23:40 UTC | May 19, 01:30 UTC | 1h 50m |
| 2026-05-18 | N500TD | - | May 18, 20:45 UTC | May 18, 22:55 UTC | 2h 10m |
| 2026-05-17 | N500TD | - | May 17, 23:30 UTC | May 18, 02:00 UTC | 2h 30m |
| 2026-05-17 | N500TD | - | May 17, 15:25 UTC | May 17, 17:55 UTC | 2h 30m |
| 2026-05-11 | N500TD | - | May 11, 20:25 UTC | May 11, 22:35 UTC | 2h 9m |
| 2026-05-11 | N500TD | - | May 11, 15:00 UTC | May 11, 19:00 UTC | 4h 0m |
| 2026-05-09 | N500TD | - | May 9, 21:14 UTC | May 10, 01:20 UTC | 4h 5m |
| 2026-05-09 | N500TD | - | May 9, 15:30 UTC | May 9, 17:40 UTC | 2h 10m |
| 2026-05-03 | N500TD | HIO → MVW | May 3, 22:34 UTC | May 3, 23:55 UTC | 1h 20m |
| 2026-05-03 | N500TD | - | May 3, 16:45 UTC | May 3, 21:44 UTC | 5h 0m |
| 2026-04-29 | N500TD | - | Apr 29, 18:15 UTC | Apr 29, 21:10 UTC | 2h 55m |
| 2026-04-26 | N500TD | - | Apr 26, 16:10 UTC | Apr 26, 21:35 UTC | 5h 25m |
| 2026-04-25 | N500TD | - | Apr 25, 16:25 UTC | Apr 25, 22:05 UTC | 5h 40m |
| 2026-04-24 | N500TD | - | Apr 24, 16:50 UTC | Apr 24, 22:40 UTC | 5h 50m |
| 2026-04-21 | N500TD | - | Apr 21, 18:20 UTC | Apr 21, 18:30 UTC | 10m |
| 2026-04-19 | N500TD | - | Apr 19, 21:05 UTC | Apr 19, 22:20 UTC | 1h 15m |
| 2026-04-19 | N500TD | - | Apr 19, 19:30 UTC | Apr 19, 20:10 UTC | 40m |
| 2026-04-19 | N500TD | - | Apr 19, 17:00 UTC | Apr 19, 18:45 UTC | 1h 45m |
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 N500TD page for operator, model, and routing details .