sensors Mode-S transponder
AE5A23
ICAO 24-bit transponder address
Currently assigned to 17-08232 · BOEING-VERTOL CH-47 Chinook
- Hex
- AE5A23
- Octal
- 53455043
- Decimal
- 11,426,339
- Tail
- 17-08232
- Type
- H47
- Flights observed
- 69
- Distinct callsigns
- 11
- Country
- -
- Last broadcast
- Jul 24, 08:35 UTC
Last known position
Callsign history 11 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | URSA10 | FBK → FBK | Jul 24, 08:10 UTC | Jul 24, 08:30 UTC | 20m |
| 2026-07-24 | URSA10 | FBK → FBK | Jul 24, 07:35 UTC | Jul 24, 07:55 UTC | 20m |
| 2026-07-24 | URSA10 | FBK → FBK | Jul 24, 07:20 UTC | Jul 24, 07:30 UTC | 10m |
| 2026-07-21 | URSA10 | - | Jul 21, 23:45 UTC | Jul 22, 00:00 UTC | 15m |
| 2026-07-21 | URSA10 | FBK → FBK | Jul 21, 21:50 UTC | Jul 21, 23:40 UTC | 1h 50m |
| 2026-07-21 | URSA05 | FBK → FBK | Jul 21, 19:40 UTC | Jul 21, 21:25 UTC | 1h 45m |
| 2026-07-21 | URSA05 | FBK → FBK | Jul 21, 19:20 UTC | Jul 21, 19:35 UTC | 15m |
| 2026-07-20 | URSA75 | - | Jul 20, 22:30 UTC | Jul 20, 23:10 UTC | 40m |
| 2026-07-20 | URSA75 | - | Jul 20, 22:10 UTC | Jul 20, 22:20 UTC | 10m |
| 2026-07-20 | URSA75 | - | Jul 20, 20:05 UTC | Jul 20, 21:55 UTC | 1h 50m |
| 2026-07-20 | URSA75 | - | Jul 20, 19:25 UTC | Jul 20, 19:40 UTC | 15m |
| 2026-07-20 | URSA75 | - | Jul 20, 19:10 UTC | Jul 20, 19:20 UTC | 10m |
| 2026-07-20 | URSA75 | - | Jul 20, 18:40 UTC | Jul 20, 18:55 UTC | 15m |
| 2026-07-15 | URSA75 | - | Jul 15, 20:10 UTC | Jul 15, 20:40 UTC | 30m |
| 2026-07-15 | URSA75 | ENN → ENN | Jul 15, 19:55 UTC | Jul 15, 20:05 UTC | 10m |
| 2026-07-15 | URSA75 | ENN → ENN | Jul 15, 19:30 UTC | Jul 15, 19:40 UTC | 10m |
| 2026-07-15 | URSA75 | ENN → ENN | Jul 15, 19:15 UTC | Jul 15, 19:25 UTC | 10m |
| 2026-07-15 | URSA75 | - | Jul 15, 18:25 UTC | Jul 15, 19:10 UTC | 45m |
| 2026-07-15 | URSA05 | MLY → FBK | Jul 15, 00:20 UTC | Jul 15, 01:15 UTC | 55m |
| 2026-07-14 | URSA05 | - | Jul 14, 19:30 UTC | Jul 14, 20:10 UTC | 40m |
| 2026-07-14 | URSA05 | - | Jul 14, 19:10 UTC | Jul 14, 19:20 UTC | 10m |
| 2026-07-08 | URSA20 | - | Jul 8, 23:45 UTC | Jul 9, 00:10 UTC | 25m |
| 2026-07-08 | URSA20 | - | Jul 8, 19:05 UTC | Jul 8, 20:25 UTC | 1h 20m |
| 2026-07-02 | URSA98 | - | Jul 2, 21:40 UTC | Jul 2, 22:00 UTC | 20m |
| 2026-07-02 | URSA98 | - | Jul 2, 18:25 UTC | Jul 2, 18:35 UTC | 10m |
| 2026-07-02 | URSA98 | - | Jul 2, 00:05 UTC | Jul 2, 00:35 UTC | 30m |
| 2026-07-01 | URSA98 | - | Jul 1, 18:55 UTC | Jul 1, 19:15 UTC | 20m |
| 2026-06-25 | URSA32 | - | Jun 25, 22:49 UTC | Jun 25, 22:59 UTC | 10m |
| 2026-06-16 | URSA12 | - | Jun 16, 19:15 UTC | Jun 16, 19:25 UTC | 10m |
| 2026-06-16 | URSA12 | - | Jun 16, 19:05 UTC | Jun 16, 19:10 UTC | 5m |
| 2026-06-05 | URSA22 | FBK → FBK | Jun 5, 17:25 UTC | Jun 5, 17:30 UTC | 5m |
| 2026-06-05 | URSA22 | FBK → FBK | Jun 5, 17:10 UTC | Jun 5, 17:20 UTC | 10m |
| 2026-06-05 | URSA22 | FBK → FBK | Jun 5, 16:10 UTC | Jun 5, 17:05 UTC | 55m |
| 2026-06-04 | URSA22 | FBK → FBK | Jun 4, 20:40 UTC | Jun 4, 21:20 UTC | 40m |
| 2026-06-03 | URSA22 | - | Jun 3, 21:10 UTC | Jun 3, 21:25 UTC | 15m |
| 2026-06-03 | URSA22 | FBK → FBK | Jun 3, 20:40 UTC | Jun 3, 20:50 UTC | 10m |
| 2026-06-03 | URSA22 | FBK → FBK | Jun 3, 20:20 UTC | Jun 3, 20:35 UTC | 15m |
| 2026-06-03 | URSA22 | FBK → FBK | Jun 3, 00:10 UTC | Jun 3, 00:20 UTC | 10m |
| 2026-06-02 | URSA22 | FBK → FBK | Jun 2, 23:35 UTC | Jun 3, 00:00 UTC | 25m |
| 2026-06-02 | URSA22 | FBK → FBK | Jun 2, 23:15 UTC | Jun 2, 23:20 UTC | 5m |
| 2026-04-27 | URSA32 | FBK → FBK | Apr 27, 16:50 UTC | Apr 27, 17:40 UTC | 50m |
| 2026-04-22 | URSA19 | FBK → FBK | Apr 22, 21:55 UTC | Apr 22, 22:05 UTC | 10m |
| 2026-04-22 | URSA19 | FBK → FBK | Apr 22, 21:30 UTC | Apr 22, 21:40 UTC | 10m |
| 2026-04-22 | URSA19 | FBK → FBK | Apr 22, 21:05 UTC | Apr 22, 21:15 UTC | 10m |
| 2026-04-22 | URSA19 | FBK → FBK | Apr 22, 20:40 UTC | Apr 22, 20:50 UTC | 10m |
| 2026-04-22 | URSA19 | FBK → FBK | Apr 22, 19:45 UTC | Apr 22, 20:35 UTC | 50m |
| 2026-04-22 | URSA19 | FBK → FBK | Apr 22, 19:25 UTC | Apr 22, 19:35 UTC | 10m |
| 2026-04-22 | URSA98 | - | Apr 22, 10:25 UTC | Apr 22, 10:40 UTC | 15m |
| 2026-04-22 | URSA98 | - | Apr 22, 08:45 UTC | Apr 22, 10:20 UTC | 1h 35m |
| 2026-04-22 | URSA98 | - | Apr 22, 08:01 UTC | Apr 22, 08: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 17-08232 page for operator, model, and routing details .