sensors Mode-S transponder
ACD4D4
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N926DW · BEECH 200 Super King Air · operated by SOMAX LLC
- Hex
- ACD4D4
- Octal
- 53152324
- Decimal
- 11,326,676
- Country
- US
- Tail
- N926DW
- Type
- BE20
- Flights observed
- 52
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- Jul 26, 04:00 UTC
Last known position
Country allocation
The ICAO 24-bit address ACD4D4 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 |
|---|---|---|---|
| N926DW | - | 52 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | N926DW | - | Jul 26, 03:15 UTC | Jul 26, 04:00 UTC | 45m |
| 2026-07-25 | N926DW | - | Jul 25, 18:30 UTC | Jul 25, 19:15 UTC | 45m |
| 2026-07-07 | N926DW | - | Jul 7, 02:55 UTC | Jul 7, 04:10 UTC | 1h 15m |
| 2026-07-06 | N926DW | - | Jul 6, 22:20 UTC | Jul 6, 23:35 UTC | 1h 15m |
| 2026-07-06 | N926DW | - | Jul 6, 16:25 UTC | Jul 6, 18:45 UTC | 2h 20m |
| 2026-07-06 | N926DW | - | Jul 6, 13:10 UTC | Jul 6, 15:35 UTC | 2h 25m |
| 2026-06-29 | N926DW | - | Jun 29, 14:09 UTC | Jun 29, 19:20 UTC | 5h 10m |
| 2026-06-25 | N926DW | - | Jun 25, 16:55 UTC | Jun 25, 18:10 UTC | 1h 15m |
| 2026-06-25 | N926DW | - | Jun 25, 15:04 UTC | Jun 25, 16:20 UTC | 1h 15m |
| 2026-06-23 | N926DW | - | Jun 23, 22:19 UTC | Jun 23, 23:00 UTC | 40m |
| 2026-06-23 | N926DW | - | Jun 23, 13:55 UTC | Jun 23, 14:35 UTC | 40m |
| 2026-06-12 | N926DW | - | Jun 12, 00:05 UTC | Jun 12, 00:40 UTC | 36m |
| 2026-06-11 | N926DW | - | Jun 11, 19:40 UTC | Jun 11, 20:15 UTC | 35m |
| 2026-06-10 | N926DW | - | Jun 10, 13:10 UTC | Jun 10, 14:50 UTC | 1h 40m |
| 2026-06-05 | N926DW | - | Jun 5, 19:40 UTC | Jun 5, 21:00 UTC | 1h 20m |
| 2026-06-04 | N926DW | - | Jun 4, 17:50 UTC | Jun 4, 19:05 UTC | 1h 15m |
| 2026-06-01 | N926DW | - | Jun 1, 21:15 UTC | Jun 1, 22:35 UTC | 1h 20m |
| 2026-06-01 | N926DW | - | Jun 1, 18:30 UTC | Jun 1, 19:50 UTC | 1h 20m |
| 2026-06-01 | N926DW | - | Jun 1, 17:25 UTC | Jun 1, 17:55 UTC | 30m |
| 2026-05-31 | N926DW | - | May 31, 19:20 UTC | May 31, 20:35 UTC | 1h 15m |
| 2026-05-31 | N926DW | - | May 31, 17:55 UTC | May 31, 19:05 UTC | 1h 10m |
| 2026-05-27 | N926DW | - | May 27, 15:05 UTC | May 27, 15:40 UTC | 35m |
| 2026-05-27 | N926DW | - | May 27, 13:35 UTC | May 27, 14:20 UTC | 45m |
| 2026-05-17 | N926DW | - | May 17, 19:45 UTC | May 17, 20:15 UTC | 30m |
| 2026-05-17 | N926DW | - | May 17, 17:50 UTC | May 17, 18:20 UTC | 30m |
| 2026-05-16 | N926DW | - | May 16, 16:10 UTC | May 16, 17:45 UTC | 1h 35m |
| 2026-05-16 | N926DW | - | May 16, 13:31 UTC | May 16, 15:01 UTC | 1h 30m |
| 2026-05-14 | N926DW | - | May 14, 15:40 UTC | May 14, 17:05 UTC | 1h 25m |
| 2026-05-14 | N926DW | - | May 14, 13:05 UTC | May 14, 14:40 UTC | 1h 35m |
| 2026-05-13 | N926DW | - | May 13, 19:30 UTC | May 13, 21:05 UTC | 1h 35m |
| 2026-05-13 | N926DW | - | May 13, 14:25 UTC | May 13, 16:05 UTC | 1h 40m |
| 2026-05-12 | N926DW | - | May 12, 16:10 UTC | May 12, 17:45 UTC | 1h 35m |
| 2026-05-12 | N926DW | - | May 12, 14:00 UTC | May 12, 15:25 UTC | 1h 25m |
| 2026-05-11 | N926DW | - | May 11, 21:00 UTC | May 11, 21:35 UTC | 35m |
| 2026-05-11 | N926DW | - | May 11, 19:50 UTC | May 11, 20:30 UTC | 40m |
| 2026-05-11 | N926DW | - | May 11, 18:50 UTC | May 11, 19:15 UTC | 25m |
| 2026-05-11 | N926DW | - | May 11, 13:40 UTC | May 11, 14:10 UTC | 30m |
| 2026-05-06 | N926DW | - | May 6, 17:25 UTC | May 6, 19:00 UTC | 1h 34m |
| 2026-05-03 | N926DW | - | May 3, 22:15 UTC | May 4, 00:19 UTC | 2h 5m |
| 2026-04-30 | N926DW | - | Apr 30, 17:35 UTC | Apr 30, 18:00 UTC | 25m |
| 2026-04-30 | N926DW | - | Apr 30, 16:25 UTC | Apr 30, 16:55 UTC | 30m |
| 2026-04-29 | N926DW | - | Apr 29, 21:05 UTC | Apr 29, 22:20 UTC | 1h 15m |
| 2026-04-17 | N926DW | - | Apr 17, 14:25 UTC | Apr 17, 14:45 UTC | 20m |
| 2026-04-17 | N926DW | - | Apr 17, 13:40 UTC | Apr 17, 13:50 UTC | 10m |
| 2026-04-16 | N926DW | - | Apr 16, 15:30 UTC | Apr 16, 15:45 UTC | 15m |
| 2026-04-16 | N926DW | - | Apr 16, 14:30 UTC | Apr 16, 14:55 UTC | 25m |
| 2026-04-14 | N926DW | - | Apr 14, 20:55 UTC | Apr 14, 21:20 UTC | 25m |
| 2026-04-14 | N926DW | - | Apr 14, 20:40 UTC | Apr 14, 20:50 UTC | 10m |
| 2026-04-14 | N926DW | - | Apr 14, 19:35 UTC | Apr 14, 20:15 UTC | 40m |
| 2026-04-13 | N926DW | - | Apr 13, 20:00 UTC | Apr 13, 20:40 UTC | 40m |
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 N926DW page for operator, model, and routing details .