sensors Mode-S transponder
AC1D9A
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N88XS · BEECHCRAFT Super King Air 350 · operated by DE510 LLC
- Hex
- AC1D9A
- Octal
- 53016632
- Decimal
- 11,279,770
- Country
- US
- Tail
- N88XS
- Type
- B350
- Flights observed
- 52
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address AC1D9A 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 |
|---|---|---|---|
| N88XS | - | 52 | 2026-07-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-19 | N88XS | SUA → PDK | Jul 19, 14:15 UTC | Jul 19, 16:05 UTC | 1h 50m |
| 2026-07-19 | N88XS | PDK → SUA | Jul 19, 11:30 UTC | Jul 19, 13:25 UTC | 1h 55m |
| 2026-07-16 | N88XS | - | Jul 16, 21:15 UTC | Jul 16, 23:10 UTC | 1h 55m |
| 2026-07-16 | N88XS | - | Jul 16, 18:29 UTC | Jul 16, 20:25 UTC | 1h 55m |
| 2026-07-12 | N88XS | - | Jul 12, 17:55 UTC | Jul 12, 19:01 UTC | 1h 5m |
| 2026-07-12 | N88XS | - | Jul 12, 15:01 UTC | Jul 12, 17:10 UTC | 2h 10m |
| 2026-07-11 | N88XS | - | Jul 11, 14:25 UTC | Jul 11, 16:35 UTC | 2h 10m |
| 2026-07-11 | N88XS | - | Jul 11, 12:30 UTC | Jul 11, 13:15 UTC | 45m |
| 2026-07-07 | N88XS | - | Jul 7, 18:50 UTC | Jul 7, 20:40 UTC | 1h 50m |
| 2026-07-07 | N88XS | - | Jul 7, 17:55 UTC | Jul 7, 18:35 UTC | 40m |
| 2026-07-06 | N88XS | TPA → APF | Jul 6, 19:35 UTC | Jul 6, 20:10 UTC | 35m |
| 2026-07-06 | N88XS | - | Jul 6, 13:10 UTC | Jul 6, 14:55 UTC | 1h 45m |
| 2026-06-26 | N88XS | - | Jun 26, 18:15 UTC | Jun 26, 20:10 UTC | 1h 55m |
| 2026-06-25 | N88XS | - | Jun 25, 12:04 UTC | Jun 25, 14:04 UTC | 2h 0m |
| 2026-06-24 | N88XS | - | Jun 24, 20:24 UTC | Jun 24, 22:45 UTC | 2h 20m |
| 2026-06-22 | N88XS | - | Jun 22, 12:25 UTC | Jun 22, 14:55 UTC | 2h 30m |
| 2026-06-20 | N88XS | - | Jun 20, 21:19 UTC | Jun 20, 23:04 UTC | 1h 45m |
| 2026-06-20 | N88XS | - | Jun 20, 13:34 UTC | Jun 20, 14:29 UTC | 55m |
| 2026-06-20 | N88XS | - | Jun 20, 12:30 UTC | Jun 20, 12:59 UTC | 30m |
| 2026-06-14 | N88XS | - | Jun 14, 15:15 UTC | Jun 14, 17:40 UTC | 2h 25m |
| 2026-06-11 | N88XS | - | Jun 11, 20:10 UTC | Jun 11, 22:35 UTC | 2h 25m |
| 2026-06-05 | N88XS | - | Jun 5, 16:30 UTC | Jun 5, 16:45 UTC | 15m |
| 2026-06-04 | N88XS | - | Jun 4, 20:25 UTC | Jun 4, 20:40 UTC | 15m |
| 2026-06-04 | N88XS | SSI → PDK | Jun 4, 18:35 UTC | Jun 4, 19:35 UTC | 1h 0m |
| 2026-06-04 | N88XS | - | Jun 4, 15:55 UTC | Jun 4, 16:55 UTC | 1h 0m |
| 2026-06-03 | N88XS | - | Jun 3, 16:25 UTC | Jun 3, 17:20 UTC | 55m |
| 2026-06-03 | N88XS | - | Jun 3, 13:50 UTC | Jun 3, 14:50 UTC | 1h 0m |
| 2026-06-02 | N88XS | - | Jun 2, 18:50 UTC | Jun 2, 19:40 UTC | 50m |
| 2026-06-02 | N88XS | - | Jun 2, 12:55 UTC | Jun 2, 13:55 UTC | 1h 0m |
| 2026-05-26 | N88XS | - | May 26, 16:10 UTC | May 26, 18:14 UTC | 2h 5m |
| 2026-05-26 | N88XS | - | May 26, 15:00 UTC | May 26, 15:29 UTC | 30m |
| 2026-05-22 | N88XS | - | May 22, 16:20 UTC | May 22, 16:55 UTC | 35m |
| 2026-05-22 | N88XS | - | May 22, 13:00 UTC | May 22, 15:20 UTC | 2h 20m |
| 2026-05-19 | N88XS | - | May 19, 18:25 UTC | May 19, 19:30 UTC | 1h 5m |
| 2026-05-19 | N88XS | - | May 19, 16:10 UTC | May 19, 17:20 UTC | 1h 10m |
| 2026-05-17 | N88XS | - | May 17, 15:05 UTC | May 17, 16:15 UTC | 1h 10m |
| 2026-05-17 | N88XS | - | May 17, 12:55 UTC | May 17, 14:01 UTC | 1h 5m |
| 2026-05-01 | N88XS | RDU → PDK | May 1, 19:20 UTC | May 1, 20:50 UTC | 1h 30m |
| 2026-05-01 | N88XS | BNA → RDU | May 1, 15:55 UTC | May 1, 17:10 UTC | 1h 15m |
| 2026-05-01 | N88XS | - | May 1, 13:30 UTC | May 1, 14:20 UTC | 50m |
| 2026-04-30 | N88XS | - | Apr 30, 19:20 UTC | Apr 30, 20:50 UTC | 1h 30m |
| 2026-04-29 | N88XS | - | Apr 29, 14:15 UTC | Apr 29, 15:55 UTC | 1h 40m |
| 2026-04-27 | N88XS | TPA → PDK | Apr 27, 21:45 UTC | Apr 27, 23:25 UTC | 1h 40m |
| 2026-04-27 | N88XS | - | Apr 27, 14:45 UTC | Apr 27, 16:15 UTC | 1h 30m |
| 2026-04-23 | N88XS | - | Apr 23, 12:10 UTC | Apr 23, 14:10 UTC | 2h 0m |
| 2026-04-21 | N88XS | - | Apr 21, 18:40 UTC | Apr 21, 20:40 UTC | 2h 0m |
| 2026-04-18 | N88XS | - | Apr 18, 03:25 UTC | Apr 18, 03:45 UTC | 20m |
| 2026-04-18 | N88XS | - | Apr 18, 01:35 UTC | Apr 18, 03:20 UTC | 1h 45m |
| 2026-04-17 | N88XS | - | Apr 17, 23:25 UTC | Apr 18, 00:20 UTC | 55m |
| 2026-04-17 | N88XS | - | Apr 17, 22:25 UTC | Apr 17, 23:20 UTC | 55m |
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 N88XS page for operator, model, and routing details .