sensors Mode-S transponder
A73D2B
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N56592 · PIPER PA-28-140/150/160/180 · operated by ETRESS JAMES A
- Hex
- A73D2B
- Octal
- 51636453
- Decimal
- 10,960,171
- Country
- US
- Tail
- N56592
- Type
- P28A
- Flights observed
- 62
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 7d ago
Last known position
Country allocation
The ICAO 24-bit address A73D2B 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 |
|---|---|---|---|
| N56592 | - | 61 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | N56592 | GAD → GAD | Jul 26, 21:10 UTC | Jul 26, 21:40 UTC | 30m |
| 2026-07-23 | N56592 | - | Jul 23, 19:10 UTC | Jul 23, 19:35 UTC | 25m |
| 2026-07-22 | N56592 | GAD → GAD | Jul 22, 22:50 UTC | Jul 22, 23:30 UTC | 40m |
| 2026-07-22 | N56592 | - | Jul 22, 19:25 UTC | Jul 22, 20:35 UTC | 1h 10m |
| 2026-07-21 | N56592 | GAD → GAD | Jul 21, 22:05 UTC | Jul 21, 23:00 UTC | 55m |
| 2026-07-21 | N56592 | GAD → GAD | Jul 21, 19:25 UTC | Jul 21, 20:30 UTC | 1h 5m |
| 2026-07-19 | N56592 | - | Jul 19, 13:50 UTC | Jul 19, 14:30 UTC | 40m |
| 2026-07-18 | N56592 | - | Jul 18, 16:35 UTC | Jul 18, 17:00 UTC | 25m |
| 2026-07-18 | N56592 | - | Jul 18, 15:30 UTC | Jul 18, 15:50 UTC | 20m |
| 2026-07-18 | N56592 | - | Jul 18, 10:40 UTC | Jul 18, 11:05 UTC | 25m |
| 2026-07-16 | - | - | Jul 16, 20:09 UTC | Jul 16, 20:19 UTC | 10m |
| 2026-07-11 | N56592 | - | Jul 11, 15:35 UTC | Jul 11, 15:55 UTC | 20m |
| 2026-07-11 | N56592 | - | Jul 11, 14:40 UTC | Jul 11, 15:05 UTC | 25m |
| 2026-07-11 | N56592 | - | Jul 11, 00:30 UTC | Jul 11, 00:50 UTC | 20m |
| 2026-07-10 | N56592 | - | Jul 10, 18:50 UTC | Jul 10, 19:00 UTC | 10m |
| 2026-07-08 | N56592 | - | Jul 8, 22:35 UTC | Jul 8, 23:40 UTC | 1h 5m |
| 2026-07-03 | N56592 | - | Jul 3, 15:35 UTC | Jul 3, 16:10 UTC | 35m |
| 2026-06-29 | N56592 | - | Jun 29, 19:44 UTC | Jun 29, 20:15 UTC | 30m |
| 2026-06-28 | N56592 | - | Jun 28, 19:59 UTC | Jun 28, 20:34 UTC | 35m |
| 2026-06-24 | N56592 | - | Jun 24, 23:20 UTC | Jun 24, 23:59 UTC | 40m |
| 2026-06-24 | N56592 | - | Jun 24, 22:10 UTC | Jun 24, 22:35 UTC | 25m |
| 2026-06-24 | N56592 | - | Jun 24, 02:24 UTC | Jun 24, 04:00 UTC | 1h 35m |
| 2026-06-23 | N56592 | - | Jun 23, 22:44 UTC | Jun 23, 23:00 UTC | 15m |
| 2026-06-15 | N56592 | - | Jun 15, 23:04 UTC | Jun 15, 23:15 UTC | 10m |
| 2026-06-13 | N56592 | - | Jun 13, 23:10 UTC | Jun 13, 23:45 UTC | 35m |
| 2026-06-13 | N56592 | - | Jun 13, 17:00 UTC | Jun 13, 17:55 UTC | 55m |
| 2026-06-05 | N56592 | - | Jun 5, 19:50 UTC | Jun 5, 20:55 UTC | 1h 5m |
| 2026-06-04 | N56592 | - | Jun 4, 19:20 UTC | Jun 4, 20:50 UTC | 1h 30m |
| 2026-06-04 | N56592 | - | Jun 4, 02:10 UTC | Jun 4, 03:25 UTC | 1h 15m |
| 2026-06-03 | N56592 | - | Jun 3, 22:55 UTC | Jun 3, 23:15 UTC | 20m |
| 2026-06-02 | N56592 | - | Jun 2, 22:15 UTC | Jun 2, 22:30 UTC | 15m |
| 2026-05-23 | N56592 | - | May 23, 19:25 UTC | May 23, 20:05 UTC | 40m |
| 2026-05-16 | N56592 | - | May 16, 23:10 UTC | May 16, 23:20 UTC | 10m |
| 2026-05-16 | N56592 | - | May 16, 19:50 UTC | May 16, 20:05 UTC | 15m |
| 2026-05-15 | N56592 | - | May 15, 15:05 UTC | May 15, 15:25 UTC | 20m |
| 2026-05-14 | N56592 | - | May 14, 23:10 UTC | May 14, 23:25 UTC | 15m |
| 2026-05-14 | N56592 | - | May 14, 19:20 UTC | May 14, 20:25 UTC | 1h 5m |
| 2026-05-12 | N56592 | - | May 12, 22:35 UTC | May 12, 23:10 UTC | 35m |
| 2026-05-12 | N56592 | - | May 12, 02:45 UTC | May 12, 04:00 UTC | 1h 15m |
| 2026-05-10 | N56592 | - | May 10, 21:30 UTC | May 10, 21:54 UTC | 25m |
| 2026-05-08 | N56592 | - | May 8, 19:40 UTC | May 8, 19:55 UTC | 15m |
| 2026-05-05 | N56592 | - | May 5, 18:30 UTC | May 5, 18:40 UTC | 10m |
| 2026-05-05 | N56592 | - | May 5, 11:40 UTC | May 5, 12:05 UTC | 25m |
| 2026-05-01 | N56592 | - | May 1, 22:35 UTC | May 1, 22:50 UTC | 15m |
| 2026-05-01 | N56592 | - | May 1, 21:45 UTC | May 1, 21:55 UTC | 10m |
| 2026-04-26 | N56592 | - | Apr 26, 15:45 UTC | Apr 26, 16:00 UTC | 15m |
| 2026-04-24 | N56592 | - | Apr 24, 02:30 UTC | Apr 24, 02:45 UTC | 15m |
| 2026-04-23 | N56592 | - | Apr 23, 22:35 UTC | Apr 23, 23:00 UTC | 25m |
| 2026-04-23 | N56592 | - | Apr 23, 15:50 UTC | Apr 23, 17:35 UTC | 1h 45m |
| 2026-04-23 | N56592 | - | Apr 23, 14:50 UTC | Apr 23, 15:15 UTC | 25m |
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 N56592 page for operator, model, and routing details .