sensors Mode-S transponder
AD493C
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N955WP · BEECHCRAFT Super King Air 350 · operated by AIR BC LLC
- Hex
- AD493C
- Octal
- 53244474
- Decimal
- 11,356,476
- Country
- US
- Tail
- N955WP
- Type
- B350
- Flights observed
- 55
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- Jul 26, 20:25 UTC
Last known position
Country allocation
The ICAO 24-bit address AD493C 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 |
|---|---|---|---|
| N955WP | - | 55 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | N955WP | - | Jul 26, 18:05 UTC | Jul 26, 20:25 UTC | 2h 20m |
| 2026-07-26 | N955WP | - | Jul 26, 14:55 UTC | Jul 26, 17:00 UTC | 2h 5m |
| 2026-07-23 | N955WP | - | Jul 23, 23:35 UTC | Jul 24, 01:30 UTC | 1h 55m |
| 2026-07-20 | N955WP | - | Jul 20, 21:00 UTC | Jul 20, 21:50 UTC | 50m |
| 2026-07-20 | N955WP | - | Jul 20, 19:20 UTC | Jul 20, 20:25 UTC | 1h 5m |
| 2026-07-20 | N955WP | - | Jul 20, 17:45 UTC | Jul 20, 18:45 UTC | 1h 0m |
| 2026-07-19 | N955WP | - | Jul 19, 19:10 UTC | Jul 19, 20:25 UTC | 1h 15m |
| 2026-07-19 | N955WP | - | Jul 19, 16:00 UTC | Jul 19, 17:25 UTC | 1h 25m |
| 2026-07-15 | N955WP | - | Jul 15, 21:10 UTC | Jul 16, 00:55 UTC | 3h 45m |
| 2026-07-13 | N955WP | - | Jul 13, 20:40 UTC | Jul 13, 23:55 UTC | 3h 15m |
| 2026-07-12 | N955WP | - | Jul 12, 19:40 UTC | Jul 12, 20:30 UTC | 50m |
| 2026-07-12 | N955WP | - | Jul 12, 16:35 UTC | Jul 12, 17:25 UTC | 50m |
| 2026-07-10 | N955WP | - | Jul 10, 21:20 UTC | Jul 10, 23:15 UTC | 1h 55m |
| 2026-07-03 | N955WP | - | Jul 3, 15:45 UTC | Jul 3, 16:35 UTC | 50m |
| 2026-06-26 | N955WP | - | Jun 26, 17:09 UTC | Jun 26, 17:35 UTC | 25m |
| 2026-06-26 | N955WP | - | Jun 26, 14:05 UTC | Jun 26, 14:29 UTC | 25m |
| 2026-06-23 | N955WP | - | Jun 23, 18:50 UTC | Jun 23, 20:10 UTC | 1h 20m |
| 2026-06-23 | N955WP | - | Jun 23, 15:15 UTC | Jun 23, 17:04 UTC | 1h 50m |
| 2026-06-23 | N955WP | - | Jun 23, 12:05 UTC | Jun 23, 14:15 UTC | 2h 10m |
| 2026-06-21 | N955WP | - | Jun 21, 16:25 UTC | Jun 21, 16:59 UTC | 35m |
| 2026-06-19 | N955WP | - | Jun 19, 13:50 UTC | Jun 19, 14:39 UTC | 50m |
| 2026-06-10 | N955WP | - | Jun 10, 19:55 UTC | Jun 10, 20:20 UTC | 25m |
| 2026-06-10 | N955WP | - | Jun 10, 15:20 UTC | Jun 10, 15:40 UTC | 20m |
| 2026-06-08 | N955WP | - | Jun 8, 18:30 UTC | Jun 8, 18:40 UTC | 10m |
| 2026-06-08 | N955WP | - | Jun 8, 14:30 UTC | Jun 8, 15:00 UTC | 30m |
| 2026-06-07 | N955WP | - | Jun 7, 15:10 UTC | Jun 7, 16:00 UTC | 50m |
| 2026-06-05 | N955WP | - | Jun 5, 00:05 UTC | Jun 5, 02:00 UTC | 1h 55m |
| 2026-05-31 | N955WP | - | May 31, 16:50 UTC | May 31, 17:40 UTC | 50m |
| 2026-05-29 | N955WP | - | May 29, 21:55 UTC | May 29, 23:50 UTC | 1h 55m |
| 2026-05-25 | N955WP | - | May 25, 18:25 UTC | May 25, 19:15 UTC | 50m |
| 2026-05-25 | N955WP | - | May 25, 16:15 UTC | May 25, 17:00 UTC | 45m |
| 2026-05-23 | N955WP | - | May 23, 20:55 UTC | May 23, 21:45 UTC | 50m |
| 2026-05-22 | N955WP | - | May 22, 22:35 UTC | May 23, 00:35 UTC | 2h 0m |
| 2026-05-15 | N955WP | - | May 15, 14:35 UTC | May 15, 15:15 UTC | 39m |
| 2026-05-15 | N955WP | - | May 15, 12:15 UTC | May 15, 13:00 UTC | 45m |
| 2026-05-14 | N955WP | - | May 14, 19:15 UTC | May 14, 20:00 UTC | 45m |
| 2026-05-14 | N955WP | - | May 14, 16:10 UTC | May 14, 16:55 UTC | 45m |
| 2026-05-13 | N955WP | - | May 13, 18:40 UTC | May 13, 19:25 UTC | 45m |
| 2026-05-03 | N955WP | - | May 3, 22:09 UTC | May 3, 22:54 UTC | 45m |
| 2026-05-03 | N955WP | - | May 3, 16:45 UTC | May 3, 17:20 UTC | 35m |
| 2026-05-02 | N955WP | - | May 2, 17:15 UTC | May 2, 17:30 UTC | 15m |
| 2026-05-01 | N955WP | - | May 1, 23:05 UTC | May 2, 01:15 UTC | 2h 10m |
| 2026-04-26 | N955WP | - | Apr 26, 05:15 UTC | Apr 26, 06:10 UTC | 55m |
| 2026-04-25 | N955WP | - | Apr 25, 20:50 UTC | Apr 25, 21:50 UTC | 1h 0m |
| 2026-04-24 | N955WP | - | Apr 24, 19:55 UTC | Apr 24, 20:10 UTC | 15m |
| 2026-04-24 | N955WP | - | Apr 24, 12:10 UTC | Apr 24, 12:35 UTC | 25m |
| 2026-04-19 | N955WP | - | Apr 19, 15:45 UTC | Apr 19, 16:35 UTC | 50m |
| 2026-04-19 | N955WP | - | Apr 19, 14:10 UTC | Apr 19, 15:10 UTC | 1h 0m |
| 2026-04-17 | N955WP | - | Apr 17, 21:30 UTC | Apr 17, 22:10 UTC | 40m |
| 2026-04-17 | N955WP | - | Apr 17, 20:25 UTC | Apr 17, 21:10 UTC | 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 N955WP page for operator, model, and routing details .