sensors Mode-S transponder
AE0A37
ICAO 24-bit transponder address
Currently assigned to 92-26423
- Hex
- AE0A37
- Octal
- 53405067
- Decimal
- 11,405,879
- Tail
- 92-26423
- Type
- H60
No current signal · last broadcast 5h ago
- Flights observed
- 69
- Distinct callsigns
- 12
- Country
- -
- Last broadcast
- 5h ago
Last known position
Callsign history 12 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| PIKES42 | - | 14 | 2026-07-17 |
| PIKES40 | - | 13 | 2026-07-14 |
| BELLS76 | - | 13 | 2026-07-01 |
| BELLS70 | - | 7 | 2026-06-11 |
| ARROW32 | - | 6 | 2026-07-10 |
| PIKES47 | - | 5 | 2026-05-21 |
| PIKES99 | - | 3 | 2026-05-14 |
| PIKES50 | - | 2 | 2026-07-13 |
| PIKES39 | - | 2 | 2026-05-11 |
| BELLS77 | - | 2 | 2026-05-15 |
| ARROW77 | - | 1 | 2026-05-13 |
| ARROW72 | - | 1 | 2026-06-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | PIKES42 | - | Jul 17, 18:05 UTC | Jul 17, 18:50 UTC | 45m |
| 2026-07-14 | PIKES40 | BFK → BFK | Jul 14, 20:00 UTC | Jul 14, 21:00 UTC | 1h 0m |
| 2026-07-13 | PIKES50 | - | Jul 13, 03:15 UTC | Jul 13, 04:25 UTC | 1h 10m |
| 2026-07-12 | PIKES50 | BFK → BFK | Jul 12, 22:50 UTC | Jul 13, 00:55 UTC | 2h 5m |
| 2026-07-12 | PIKES42 | - | Jul 12, 18:10 UTC | Jul 12, 18:35 UTC | 25m |
| 2026-07-12 | PIKES42 | - | Jul 12, 16:50 UTC | Jul 12, 17:40 UTC | 50m |
| 2026-07-11 | PIKES42 | - | Jul 11, 22:15 UTC | Jul 11, 22:35 UTC | 20m |
| 2026-07-11 | PIKES42 | - | Jul 11, 20:30 UTC | Jul 11, 21:05 UTC | 35m |
| 2026-07-11 | PIKES42 | - | Jul 11, 17:40 UTC | Jul 11, 18:20 UTC | 40m |
| 2026-07-11 | PIKES42 | - | Jul 11, 16:40 UTC | Jul 11, 17:15 UTC | 35m |
| 2026-07-11 | PIKES42 | - | Jul 11, 14:55 UTC | Jul 11, 15:15 UTC | 20m |
| 2026-07-10 | PIKES40 | BFK → BFK | Jul 10, 21:30 UTC | Jul 10, 21:50 UTC | 20m |
| 2026-07-10 | PIKES40 | BFK → BFK | Jul 10, 18:50 UTC | Jul 10, 20:25 UTC | 1h 35m |
| 2026-07-10 | ARROW32 | BFK → BFK | Jul 10, 01:55 UTC | Jul 10, 03:25 UTC | 1h 30m |
| 2026-07-02 | PIKES40 | - | Jul 2, 04:15 UTC | Jul 2, 04:50 UTC | 35m |
| 2026-07-02 | PIKES40 | - | Jul 2, 03:40 UTC | Jul 2, 04:05 UTC | 25m |
| 2026-07-02 | PIKES40 | BFK → BFK | Jul 2, 02:35 UTC | Jul 2, 02:45 UTC | 10m |
| 2026-07-02 | PIKES40 | BFK → BFK | Jul 2, 02:15 UTC | Jul 2, 02:30 UTC | 15m |
| 2026-07-02 | PIKES40 | BFK → BFK | Jul 2, 01:05 UTC | Jul 2, 02:10 UTC | 1h 5m |
| 2026-07-01 | BELLS76 | - | Jul 1, 21:00 UTC | Jul 1, 22:10 UTC | 1h 10m |
| 2026-07-01 | BELLS76 | - | Jul 1, 17:45 UTC | Jul 1, 18:05 UTC | 20m |
| 2026-07-01 | BELLS76 | - | Jul 1, 01:20 UTC | Jul 1, 03:00 UTC | 1h 40m |
| 2026-06-30 | PIKES40 | - | Jun 30, 03:15 UTC | Jun 30, 03:55 UTC | 40m |
| 2026-06-30 | PIKES40 | BFK → BFK | Jun 30, 00:00 UTC | Jun 30, 01:50 UTC | 1h 50m |
| 2026-06-27 | PIKES42 | - | Jun 27, 22:49 UTC | Jun 27, 23:39 UTC | 50m |
| 2026-06-27 | PIKES42 | - | Jun 27, 22:09 UTC | Jun 27, 22:20 UTC | 10m |
| 2026-06-27 | PIKES42 | - | Jun 27, 18:35 UTC | Jun 27, 19:34 UTC | 1h 0m |
| 2026-06-25 | ARROW32 | - | Jun 25, 02:49 UTC | Jun 25, 03:54 UTC | 1h 5m |
| 2026-06-25 | PIKES42 | - | Jun 25, 00:35 UTC | Jun 25, 01:24 UTC | 50m |
| 2026-06-24 | PIKES42 | BFK → BFK | Jun 24, 23:29 UTC | Jun 24, 23:45 UTC | 15m |
| 2026-06-24 | BELLS76 | BFK → BFK | Jun 24, 04:30 UTC | Jun 24, 05:49 UTC | 1h 20m |
| 2026-06-24 | BELLS76 | BFK → BFK | Jun 24, 02:49 UTC | Jun 24, 03:10 UTC | 20m |
| 2026-06-24 | BELLS76 | BFK → BFK | Jun 24, 02:09 UTC | Jun 24, 02:40 UTC | 30m |
| 2026-06-18 | ARROW32 | - | Jun 18, 01:55 UTC | Jun 18, 03:45 UTC | 1h 50m |
| 2026-06-17 | PIKES42 | - | Jun 17, 16:25 UTC | Jun 17, 17:50 UTC | 1h 25m |
| 2026-06-13 | BELLS76 | CNE → BFK | Jun 13, 21:45 UTC | Jun 13, 22:40 UTC | 55m |
| 2026-06-13 | BELLS76 | - | Jun 13, 20:05 UTC | Jun 13, 20:15 UTC | 10m |
| 2026-06-13 | BELLS76 | - | Jun 13, 18:25 UTC | Jun 13, 19:35 UTC | 1h 10m |
| 2026-06-12 | BELLS76 | BFK → BFK | Jun 12, 00:20 UTC | Jun 12, 01:35 UTC | 1h 15m |
| 2026-06-11 | BELLS70 | BFK → BFK | Jun 11, 04:35 UTC | Jun 11, 04:55 UTC | 20m |
| 2026-06-11 | BELLS70 | - | Jun 11, 03:50 UTC | Jun 11, 04:30 UTC | 40m |
| 2026-06-11 | BELLS70 | BFK → BFK | Jun 11, 03:35 UTC | Jun 11, 03:45 UTC | 10m |
| 2026-06-11 | BELLS70 | - | Jun 11, 01:30 UTC | Jun 11, 02:35 UTC | 1h 5m |
| 2026-06-05 | ARROW72 | BFK → BFK | Jun 5, 17:35 UTC | Jun 5, 17:55 UTC | 20m |
| 2026-05-29 | BELLS76 | - | May 29, 22:30 UTC | May 29, 22:40 UTC | 10m |
| 2026-05-29 | BELLS76 | - | May 29, 18:15 UTC | May 29, 19:15 UTC | 1h 0m |
| 2026-05-29 | BELLS76 | - | May 29, 14:15 UTC | May 29, 14:55 UTC | 40m |
| 2026-05-21 | PIKES47 | BFK → BFK | May 21, 03:00 UTC | May 21, 03:50 UTC | 50m |
| 2026-05-21 | PIKES47 | - | May 21, 01:35 UTC | May 21, 02:55 UTC | 1h 20m |
| 2026-05-21 | PIKES47 | - | May 21, 01:15 UTC | May 21, 01:25 UTC | 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 92-26423 page for operator, model, and routing details .
Mode-S AE0A37 frequently asked
What is Mode-S code AE0A37?
AE0A37 is an ICAO 24-bit transponder address. Assigned to 92-26423.
Is AE0A37 broadcasting right now?
No active broadcast right now. Last signal was 5h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AE0A37, octal 53405067, decimal 11,405,879.