sensors Mode-S transponder
A73DB7
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N566FF · SOCATA TBM-900/910/930/940 · operated by MIDWEST ETHANOL TRANSPORT LLC
- Hex
- A73DB7
- Octal
- 51636667
- Decimal
- 10,960,311
- Country
- US
- Tail
- N566FF
- Type
- TBM9
- Flights observed
- 60
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 8d ago
Last known position
Country allocation
The ICAO 24-bit address A73DB7 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 |
|---|---|---|---|
| N566FF | - | 60 | 2026-07-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-06 | N566FF | - | Jul 6, 12:55 UTC | Jul 6, 13:30 UTC | 35m |
| 2026-07-02 | N566FF | - | Jul 2, 16:30 UTC | Jul 2, 17:25 UTC | 55m |
| 2026-07-02 | N566FF | - | Jul 2, 14:25 UTC | Jul 2, 15:30 UTC | 1h 5m |
| 2026-07-01 | N566FF | - | Jul 1, 20:05 UTC | Jul 1, 20:15 UTC | 10m |
| 2026-06-29 | N566FF | - | Jun 29, 19:15 UTC | Jun 29, 20:00 UTC | 45m |
| 2026-06-29 | N566FF | - | Jun 29, 16:35 UTC | Jun 29, 17:34 UTC | 1h 0m |
| 2026-06-24 | N566FF | - | Jun 24, 17:29 UTC | Jun 24, 17:45 UTC | 15m |
| 2026-06-24 | N566FF | - | Jun 24, 16:50 UTC | Jun 24, 17:25 UTC | 35m |
| 2026-06-19 | N566FF | - | Jun 19, 15:54 UTC | Jun 19, 16:09 UTC | 15m |
| 2026-06-18 | N566FF | - | Jun 18, 22:20 UTC | Jun 18, 23:05 UTC | 45m |
| 2026-06-18 | N566FF | - | Jun 18, 18:25 UTC | Jun 18, 19:05 UTC | 40m |
| 2026-06-16 | N566FF | - | Jun 16, 20:00 UTC | Jun 16, 20:25 UTC | 25m |
| 2026-06-16 | N566FF | - | Jun 16, 16:10 UTC | Jun 16, 16:45 UTC | 35m |
| 2026-06-14 | N566FF | - | Jun 14, 16:00 UTC | Jun 14, 16:10 UTC | 10m |
| 2026-06-14 | N566FF | - | Jun 14, 13:20 UTC | Jun 14, 13:45 UTC | 25m |
| 2026-06-07 | N566FF | - | Jun 7, 19:35 UTC | Jun 7, 20:35 UTC | 1h 0m |
| 2026-06-07 | N566FF | - | Jun 7, 17:55 UTC | Jun 7, 18:45 UTC | 50m |
| 2026-06-06 | N566FF | - | Jun 6, 16:24 UTC | Jun 6, 18:39 UTC | 2h 15m |
| 2026-06-06 | N566FF | - | Jun 6, 13:25 UTC | Jun 6, 15:25 UTC | 2h 0m |
| 2026-06-05 | N566FF | - | Jun 5, 17:40 UTC | Jun 5, 18:30 UTC | 50m |
| 2026-06-05 | N566FF | - | Jun 5, 14:50 UTC | Jun 5, 15:50 UTC | 1h 0m |
| 2026-06-04 | N566FF | - | Jun 4, 15:10 UTC | Jun 4, 17:25 UTC | 2h 15m |
| 2026-06-04 | N566FF | - | Jun 4, 12:15 UTC | Jun 4, 14:20 UTC | 2h 5m |
| 2026-06-03 | N566FF | - | Jun 3, 17:50 UTC | Jun 3, 19:45 UTC | 1h 55m |
| 2026-06-01 | N566FF | ULM → RWF | Jun 1, 21:35 UTC | Jun 1, 21:45 UTC | 10m |
| 2026-05-30 | N566FF | - | May 30, 17:35 UTC | May 30, 18:30 UTC | 55m |
| 2026-05-30 | N566FF | - | May 30, 15:50 UTC | May 30, 16:45 UTC | 55m |
| 2026-05-29 | N566FF | - | May 29, 15:00 UTC | May 29, 15:50 UTC | 50m |
| 2026-05-26 | N566FF | - | May 26, 17:55 UTC | May 26, 18:34 UTC | 40m |
| 2026-05-26 | N566FF | - | May 26, 15:35 UTC | May 26, 16:10 UTC | 35m |
| 2026-05-21 | N566FF | - | May 21, 20:15 UTC | May 21, 21:05 UTC | 50m |
| 2026-05-21 | N566FF | - | May 21, 13:45 UTC | May 21, 14:45 UTC | 1h 0m |
| 2026-05-19 | N566FF | - | May 19, 12:40 UTC | May 19, 13:55 UTC | 1h 15m |
| 2026-05-14 | N566FF | - | May 14, 22:35 UTC | May 15, 00:00 UTC | 1h 25m |
| 2026-05-14 | N566FF | - | May 14, 20:45 UTC | May 14, 21:55 UTC | 1h 10m |
| 2026-05-13 | N566FF | - | May 13, 20:45 UTC | May 14, 00:10 UTC | 3h 25m |
| 2026-05-07 | N566FF | - | May 7, 12:50 UTC | May 7, 13:50 UTC | 1h 0m |
| 2026-05-06 | N566FF | - | May 6, 16:05 UTC | May 6, 16:15 UTC | 10m |
| 2026-05-06 | N566FF | - | May 6, 15:10 UTC | May 6, 15:35 UTC | 25m |
| 2026-05-04 | N566FF | - | May 4, 20:20 UTC | May 4, 21:35 UTC | 1h 15m |
| 2026-05-04 | N566FF | - | May 4, 19:00 UTC | May 4, 19:45 UTC | 45m |
| 2026-05-04 | N566FF | - | May 4, 15:25 UTC | May 4, 16:15 UTC | 50m |
| 2026-04-27 | N566FF | - | Apr 27, 18:40 UTC | Apr 27, 22:00 UTC | 3h 20m |
| 2026-04-26 | N566FF | - | Apr 26, 17:00 UTC | Apr 26, 17:40 UTC | 40m |
| 2026-04-26 | N566FF | - | Apr 26, 15:35 UTC | Apr 26, 16:35 UTC | 1h 0m |
| 2026-04-24 | N566FF | - | Apr 24, 19:05 UTC | Apr 24, 20:40 UTC | 1h 35m |
| 2026-04-24 | N566FF | - | Apr 24, 13:50 UTC | Apr 24, 18:30 UTC | 4h 40m |
| 2026-04-22 | N566FF | - | Apr 22, 20:45 UTC | Apr 22, 21:30 UTC | 45m |
| 2026-04-22 | N566FF | - | Apr 22, 18:05 UTC | Apr 22, 19:00 UTC | 55m |
| 2026-04-20 | N566FF | - | Apr 20, 20:25 UTC | Apr 20, 21:50 UTC | 1h 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 N566FF page for operator, model, and routing details .