sensors Mode-S transponder
A1A0BA
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N20389 · CESSNA 172 Skyhawk · operated by KCN AERO CLUB INC
- Hex
- A1A0BA
- Octal
- 50320272
- Decimal
- 10,592,442
- Country
- US
- Tail
- N20389
- Type
- C172
- Flights observed
- 52
- Distinct callsigns
- 2
- Country
- US
- Last broadcast
- Jul 26, 15:40 UTC
Last known position
Country allocation
The ICAO 24-bit address A1A0BA 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | N20389 | - | Jul 26, 14:25 UTC | Jul 26, 15:40 UTC | 1h 15m |
| 2026-07-20 | N20389 | - | Jul 20, 15:10 UTC | Jul 20, 16:00 UTC | 50m |
| 2026-07-18 | N20389 | - | Jul 18, 23:35 UTC | Jul 18, 23:50 UTC | 15m |
| 2026-07-18 | N20389 | - | Jul 18, 13:10 UTC | Jul 18, 13:25 UTC | 15m |
| 2026-07-17 | N20389 | - | Jul 17, 21:34 UTC | Jul 17, 21:50 UTC | 15m |
| 2026-07-17 | N20389 | - | Jul 17, 19:05 UTC | Jul 17, 19:55 UTC | 50m |
| 2026-07-17 | N20389 | - | Jul 17, 00:25 UTC | Jul 17, 01:59 UTC | 1h 35m |
| 2026-07-15 | N20389 | OJC → OJC | Jul 15, 13:25 UTC | Jul 15, 14:15 UTC | 50m |
| 2026-07-15 | N20389 | OJC → OJC | Jul 15, 02:55 UTC | Jul 15, 03:20 UTC | 25m |
| 2026-07-14 | N20389 | OJC → OJC | Jul 14, 22:40 UTC | Jul 14, 23:00 UTC | 19m |
| 2026-07-14 | 00000000 | - | Jul 14, 16:15 UTC | Jul 14, 16:35 UTC | 20m |
| 2026-07-14 | 00000000 | - | Jul 14, 15:10 UTC | Jul 14, 15:40 UTC | 30m |
| 2026-07-12 | N20389 | - | Jul 12, 21:40 UTC | Jul 12, 21:55 UTC | 15m |
| 2026-07-12 | N20389 | - | Jul 12, 19:50 UTC | Jul 12, 21:10 UTC | 1h 20m |
| 2026-07-11 | N20389 | - | Jul 11, 15:25 UTC | Jul 11, 15:40 UTC | 15m |
| 2026-07-11 | N20389 | - | Jul 11, 14:35 UTC | Jul 11, 14:50 UTC | 15m |
| 2026-07-10 | N20389 | - | Jul 10, 17:50 UTC | Jul 10, 20:05 UTC | 2h 15m |
| 2026-07-08 | N20389 | - | Jul 8, 13:25 UTC | Jul 8, 17:35 UTC | 4h 10m |
| 2026-07-07 | N20389 | OJC → OJC | Jul 7, 12:15 UTC | Jul 7, 13:10 UTC | 55m |
| 2026-07-05 | N20389 | - | Jul 5, 17:40 UTC | Jul 5, 18:05 UTC | 25m |
| 2026-07-05 | N20389 | - | Jul 5, 15:45 UTC | Jul 5, 16:55 UTC | 1h 10m |
| 2026-07-05 | N20389 | - | Jul 5, 13:50 UTC | Jul 5, 15:05 UTC | 1h 15m |
| 2026-07-02 | N20389 | OJC → OJC | Jul 2, 21:35 UTC | Jul 2, 22:30 UTC | 55m |
| 2026-06-24 | N20389 | OJC → OJC | Jun 24, 22:10 UTC | Jun 24, 23:10 UTC | 1h 0m |
| 2026-06-24 | N20389 | - | Jun 24, 17:10 UTC | Jun 24, 17:40 UTC | 30m |
| 2026-06-24 | N20389 | - | Jun 24, 15:29 UTC | Jun 24, 15:49 UTC | 20m |
| 2026-06-23 | N20389 | - | Jun 23, 16:50 UTC | Jun 23, 17:09 UTC | 20m |
| 2026-06-23 | N20389 | - | Jun 23, 15:24 UTC | Jun 23, 16:09 UTC | 45m |
| 2026-06-21 | N20389 | - | Jun 21, 19:24 UTC | Jun 21, 19:34 UTC | 10m |
| 2026-06-21 | N20389 | - | Jun 21, 02:50 UTC | Jun 21, 04:10 UTC | 1h 20m |
| 2026-06-20 | N20389 | - | Jun 20, 23:50 UTC | Jun 21, 01:14 UTC | 1h 25m |
| 2026-04-25 | N20389 | - | Apr 25, 19:40 UTC | Apr 25, 19:55 UTC | 15m |
| 2026-04-25 | N20389 | OJC → OJC | Apr 25, 18:10 UTC | Apr 25, 19:00 UTC | 50m |
| 2026-04-25 | N20389 | OJC → OJC | Apr 25, 14:50 UTC | Apr 25, 16:35 UTC | 1h 45m |
| 2026-04-25 | N20389 | - | Apr 25, 00:25 UTC | Apr 25, 01:15 UTC | 50m |
| 2026-04-24 | N20389 | - | Apr 24, 22:15 UTC | Apr 24, 23:40 UTC | 1h 25m |
| 2026-04-24 | N20389 | - | Apr 24, 20:25 UTC | Apr 24, 21:00 UTC | 35m |
| 2026-04-22 | N20389 | - | Apr 22, 17:10 UTC | Apr 22, 17:45 UTC | 35m |
| 2026-04-22 | N20389 | - | Apr 22, 15:20 UTC | Apr 22, 15:45 UTC | 25m |
| 2026-04-22 | N20389 | - | Apr 22, 00:10 UTC | Apr 22, 01:35 UTC | 1h 25m |
| 2026-04-21 | N20389 | - | Apr 21, 15:05 UTC | Apr 21, 16:31 UTC | 1h 25m |
| 2026-04-21 | N20389 | OJC → OJC | Apr 21, 03:15 UTC | Apr 21, 03:25 UTC | 10m |
| 2026-04-21 | N20389 | OJC → OJC | Apr 21, 03:05 UTC | Apr 21, 03:10 UTC | 5m |
| 2026-04-19 | N20389 | OJC → OJC | Apr 19, 20:05 UTC | Apr 19, 21:50 UTC | 1h 45m |
| 2026-04-19 | N20389 | - | Apr 19, 17:00 UTC | Apr 19, 17:40 UTC | 40m |
| 2026-04-19 | N20389 | - | Apr 19, 15:50 UTC | Apr 19, 16:10 UTC | 20m |
| 2026-04-18 | N20389 | OJC → OJC | Apr 18, 18:10 UTC | Apr 18, 19:00 UTC | 50m |
| 2026-04-16 | N20389 | OJC → OJC | Apr 16, 23:25 UTC | Apr 17, 00:15 UTC | 50m |
| 2026-04-16 | N20389 | OJC → OJC | Apr 16, 21:30 UTC | Apr 16, 22:30 UTC | 1h 0m |
| 2026-04-16 | N20389 | - | Apr 16, 15:50 UTC | Apr 16, 16:25 UTC | 35m |
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 N20389 page for operator, model, and routing details .