sensors Mode-S transponder
ACC0DB
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N9202U · CESSNA 172R Cutlass RG · operated by OKLAHOMA STATE UNIVERSITY
- Hex
- ACC0DB
- Octal
- 53140333
- Decimal
- 11,321,563
- Country
- US
- Tail
- N9202U
- Type
- C72R
- Flights observed
- 56
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 22d ago
Last known position
Country allocation
The ICAO 24-bit address ACC0DB 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 |
|---|---|---|---|
| OST10 | - | 56 | 2026-06-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-26 | OST10 | - | Jun 26, 19:50 UTC | Jun 26, 20:44 UTC | 55m |
| 2026-06-26 | OST10 | - | Jun 26, 15:45 UTC | Jun 26, 16:49 UTC | 1h 5m |
| 2026-06-25 | OST10 | - | Jun 25, 01:24 UTC | Jun 25, 02:14 UTC | 50m |
| 2026-06-24 | OST10 | - | Jun 24, 23:04 UTC | Jun 24, 23:14 UTC | 10m |
| 2026-06-24 | OST10 | - | Jun 24, 21:50 UTC | Jun 24, 22:29 UTC | 40m |
| 2026-06-24 | OST10 | - | Jun 24, 19:44 UTC | Jun 24, 20:14 UTC | 30m |
| 2026-06-21 | OST10 | - | Jun 21, 00:45 UTC | Jun 21, 01:10 UTC | 25m |
| 2026-06-19 | OST10 | - | Jun 19, 20:04 UTC | Jun 19, 21:04 UTC | 1h 0m |
| 2026-06-16 | OST10 | - | Jun 16, 20:20 UTC | Jun 16, 21:15 UTC | 55m |
| 2026-06-16 | OST10 | - | Jun 16, 15:45 UTC | Jun 16, 17:15 UTC | 1h 30m |
| 2026-06-16 | OST10 | - | Jun 16, 13:15 UTC | Jun 16, 14:05 UTC | 50m |
| 2026-06-15 | OST10 | - | Jun 15, 22:59 UTC | Jun 16, 00:10 UTC | 1h 10m |
| 2026-06-15 | OST10 | - | Jun 15, 19:55 UTC | Jun 15, 21:20 UTC | 1h 25m |
| 2026-06-15 | OST10 | - | Jun 15, 17:15 UTC | Jun 15, 18:25 UTC | 1h 10m |
| 2026-06-12 | OST10 | - | Jun 12, 13:10 UTC | Jun 12, 13:30 UTC | 20m |
| 2026-06-10 | OST10 | - | Jun 10, 12:15 UTC | Jun 10, 13:05 UTC | 50m |
| 2026-06-09 | OST10 | - | Jun 9, 20:05 UTC | Jun 9, 20:25 UTC | 20m |
| 2026-06-08 | OST10 | SWO → SWO | Jun 8, 14:55 UTC | Jun 8, 15:04 UTC | 10m |
| 2026-06-07 | OST10 | - | Jun 7, 23:40 UTC | Jun 8, 01:20 UTC | 1h 40m |
| 2026-06-04 | OST10 | - | Jun 4, 19:50 UTC | Jun 4, 21:20 UTC | 1h 30m |
| 2026-06-04 | OST10 | - | Jun 4, 15:55 UTC | Jun 4, 16:55 UTC | 1h 0m |
| 2026-06-03 | OST10 | - | Jun 3, 16:00 UTC | Jun 3, 17:20 UTC | 1h 20m |
| 2026-06-02 | OST10 | - | Jun 2, 22:40 UTC | Jun 2, 23:20 UTC | 40m |
| 2026-06-02 | OST10 | - | Jun 2, 19:35 UTC | Jun 2, 20:45 UTC | 1h 10m |
| 2026-06-02 | OST10 | - | Jun 2, 00:05 UTC | Jun 2, 01:10 UTC | 1h 5m |
| 2026-06-01 | OST10 | - | Jun 1, 21:40 UTC | Jun 1, 22:55 UTC | 1h 15m |
| 2026-06-01 | OST10 | - | Jun 1, 19:40 UTC | Jun 1, 20:10 UTC | 30m |
| 2026-06-01 | OST10 | - | Jun 1, 16:45 UTC | Jun 1, 17:50 UTC | 1h 5m |
| 2026-05-31 | OST10 | - | May 31, 22:55 UTC | May 31, 23:55 UTC | 1h 0m |
| 2026-05-29 | OST10 | - | May 29, 18:20 UTC | May 29, 19:05 UTC | 45m |
| 2026-05-26 | OST10 | - | May 26, 22:50 UTC | May 26, 23:54 UTC | 1h 5m |
| 2026-05-26 | OST10 | - | May 26, 15:39 UTC | May 26, 16:30 UTC | 50m |
| 2026-05-26 | OST10 | SWO → SWO | May 26, 14:05 UTC | May 26, 14:50 UTC | 45m |
| 2026-05-23 | OST10 | - | May 23, 19:45 UTC | May 23, 21:10 UTC | 1h 25m |
| 2026-05-15 | OST10 | - | May 15, 00:15 UTC | May 15, 02:15 UTC | 2h 0m |
| 2026-05-05 | OST10 | - | May 5, 18:20 UTC | May 5, 18:30 UTC | 10m |
| 2026-04-27 | OST10 | - | Apr 27, 23:40 UTC | Apr 28, 00:40 UTC | 1h 0m |
| 2026-04-27 | OST10 | - | Apr 27, 21:50 UTC | Apr 27, 22:35 UTC | 45m |
| 2026-04-27 | OST10 | - | Apr 27, 19:00 UTC | Apr 27, 20:05 UTC | 1h 5m |
| 2026-04-21 | OST10 | - | Apr 21, 18:25 UTC | Apr 21, 18:55 UTC | 30m |
| 2026-04-20 | OST10 | - | Apr 20, 21:10 UTC | Apr 20, 22:05 UTC | 55m |
| 2026-04-20 | OST10 | - | Apr 20, 18:15 UTC | Apr 20, 19:45 UTC | 1h 30m |
| 2026-04-20 | OST10 | - | Apr 20, 16:05 UTC | Apr 20, 17:15 UTC | 1h 10m |
| 2026-04-20 | OST10 | - | Apr 20, 13:45 UTC | Apr 20, 14:40 UTC | 55m |
| 2026-04-20 | OST10 | - | Apr 20, 00:10 UTC | Apr 20, 00:55 UTC | 45m |
| 2026-04-19 | OST10 | - | Apr 19, 21:50 UTC | Apr 19, 22:10 UTC | 20m |
| 2026-04-19 | OST10 | - | Apr 19, 19:30 UTC | Apr 19, 20:00 UTC | 30m |
| 2026-04-19 | OST10 | - | Apr 19, 17:30 UTC | Apr 19, 18:05 UTC | 35m |
| 2026-04-19 | OST10 | - | Apr 19, 14:55 UTC | Apr 19, 15:10 UTC | 15m |
| 2026-04-19 | OST10 | - | Apr 19, 01:45 UTC | Apr 19, 03:55 UTC | 2h 10m |
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 N9202U page for operator, model, and routing details .