sensors Mode-S transponder
AE0207
ICAO 24-bit transponder address
Currently assigned to 86-0081 · BEECH 1900
- Hex
- AE0207
- Octal
- 53401007
- Decimal
- 11,403,783
- Tail
- 86-0081
- Type
- B190
- Flights observed
- 60
- Distinct callsigns
- 15
- Country
- -
- Last broadcast
- 5d ago
Last known position
Callsign history 15 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| MOJO67 | - | 8 | 2026-06-26 |
| MOJO65 | - | 8 | 2026-05-01 |
| MOJO05 | - | 8 | 2026-06-24 |
| MOJO70 | - | 6 | 2026-05-10 |
| MOJO68 | - | 4 | 2026-07-02 |
| MOJO24 | - | 4 | 2026-05-04 |
| MOJO21 | - | 4 | 2026-06-02 |
| MOJO12 | - | 4 | 2026-07-09 |
| MOJO25 | - | 3 | 2026-05-12 |
| MOJO18 | - | 3 | 2026-07-09 |
| MOJO66 | - | 2 | 2026-04-22 |
| MOJO23 | - | 2 | 2026-05-07 |
| MOJO10 | - | 2 | 2026-05-06 |
| MOJO15 | - | 1 | 2026-05-20 |
| MOJO01 | - | 1 | 2026-06-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-09 | MOJO12 | OKO → OKO | Jul 9, 05:25 UTC | Jul 9, 07:30 UTC | 2h 5m |
| 2026-07-09 | MOJO18 | OKO → OKO | Jul 9, 02:30 UTC | Jul 9, 02:50 UTC | 20m |
| 2026-07-09 | MOJO18 | - | Jul 9, 02:15 UTC | Jul 9, 02:25 UTC | 10m |
| 2026-07-09 | MOJO18 | - | Jul 9, 01:40 UTC | Jul 9, 01:55 UTC | 15m |
| 2026-07-02 | MOJO68 | - | Jul 2, 06:25 UTC | Jul 2, 07:20 UTC | 55m |
| 2026-07-02 | MOJO68 | - | Jul 2, 05:00 UTC | Jul 2, 05:30 UTC | 30m |
| 2026-07-02 | MOJO68 | - | Jul 2, 03:10 UTC | Jul 2, 03:50 UTC | 40m |
| 2026-07-02 | MOJO68 | - | Jul 2, 00:30 UTC | Jul 2, 02:05 UTC | 1h 35m |
| 2026-06-30 | MOJO01 | OKO → OKO | Jun 30, 03:15 UTC | Jun 30, 05:15 UTC | 2h 0m |
| 2026-06-26 | MOJO67 | - | Jun 26, 00:30 UTC | Jun 26, 01:34 UTC | 1h 5m |
| 2026-06-25 | MOJO67 | - | Jun 25, 21:59 UTC | Jun 25, 22:45 UTC | 45m |
| 2026-06-24 | MOJO05 | - | Jun 24, 08:04 UTC | Jun 24, 10:04 UTC | 2h 0m |
| 2026-06-24 | MOJO05 | - | Jun 24, 04:20 UTC | Jun 24, 06:25 UTC | 2h 5m |
| 2026-06-23 | MOJO05 | - | Jun 23, 02:09 UTC | Jun 23, 03:15 UTC | 1h 5m |
| 2026-06-22 | MOJO05 | - | Jun 22, 22:24 UTC | Jun 22, 23:20 UTC | 55m |
| 2026-06-10 | MOJO12 | - | Jun 10, 01:20 UTC | Jun 10, 03:25 UTC | 2h 5m |
| 2026-06-04 | MOJO12 | OKO → OKO | Jun 4, 00:50 UTC | Jun 4, 02:40 UTC | 1h 50m |
| 2026-06-02 | MOJO21 | OKO → OKO | Jun 2, 02:45 UTC | Jun 2, 04:15 UTC | 1h 30m |
| 2026-05-20 | MOJO15 | OKO → OKO | May 20, 04:15 UTC | May 20, 06:00 UTC | 1h 46m |
| 2026-05-19 | MOJO21 | - | May 19, 04:10 UTC | May 19, 05:50 UTC | 1h 40m |
| 2026-05-19 | MOJO21 | - | May 19, 01:20 UTC | May 19, 03:05 UTC | 1h 45m |
| 2026-05-13 | MOJO05 | - | May 13, 04:05 UTC | May 13, 04:50 UTC | 45m |
| 2026-05-12 | MOJO05 | - | May 12, 23:01 UTC | May 12, 23:50 UTC | 50m |
| 2026-05-12 | MOJO25 | - | May 12, 05:50 UTC | May 12, 06:15 UTC | 25m |
| 2026-05-11 | MOJO05 | - | May 11, 04:50 UTC | May 11, 05:25 UTC | 35m |
| 2026-05-11 | MOJO05 | - | May 11, 00:25 UTC | May 11, 01:10 UTC | 45m |
| 2026-05-10 | MOJO70 | - | May 10, 08:54 UTC | May 10, 09:24 UTC | 30m |
| 2026-05-10 | MOJO70 | - | May 10, 05:10 UTC | May 10, 06:30 UTC | 1h 20m |
| 2026-05-10 | MOJO70 | - | May 10, 02:24 UTC | May 10, 03:25 UTC | 1h 0m |
| 2026-05-10 | MOJO70 | - | May 10, 00:05 UTC | May 10, 00:30 UTC | 25m |
| 2026-05-09 | MOJO70 | - | May 9, 06:30 UTC | May 9, 07:10 UTC | 40m |
| 2026-05-09 | MOJO70 | - | May 9, 01:50 UTC | May 9, 04:05 UTC | 2h 15m |
| 2026-05-07 | MOJO23 | - | May 7, 06:00 UTC | May 7, 06:35 UTC | 35m |
| 2026-05-06 | MOJO23 | - | May 6, 23:50 UTC | May 7, 02:40 UTC | 2h 50m |
| 2026-05-06 | MOJO10 | - | May 6, 10:45 UTC | May 6, 12:10 UTC | 1h 25m |
| 2026-05-06 | MOJO10 | - | May 6, 05:15 UTC | May 6, 07:05 UTC | 1h 50m |
| 2026-05-05 | MOJO25 | FKS → OKO | May 5, 04:25 UTC | May 5, 04:55 UTC | 30m |
| 2026-05-05 | MOJO25 | - | May 5, 00:10 UTC | May 5, 00:55 UTC | 45m |
| 2026-05-04 | MOJO24 | OKO → OKO | May 4, 08:25 UTC | May 4, 10:05 UTC | 1h 40m |
| 2026-05-01 | MOJO65 | - | May 1, 10:45 UTC | May 1, 11:25 UTC | 40m |
| 2026-05-01 | MOJO65 | - | May 1, 08:05 UTC | May 1, 08:30 UTC | 25m |
| 2026-05-01 | MOJO65 | - | May 1, 06:05 UTC | May 1, 06:40 UTC | 35m |
| 2026-05-01 | MOJO65 | - | May 1, 04:10 UTC | May 1, 04:55 UTC | 45m |
| 2026-05-01 | MOJO65 | - | May 1, 01:35 UTC | May 1, 02:30 UTC | 55m |
| 2026-04-30 | MOJO65 | - | Apr 30, 23:00 UTC | Apr 30, 23:40 UTC | 40m |
| 2026-04-28 | MOJO65 | - | Apr 28, 11:20 UTC | Apr 28, 11:45 UTC | 25m |
| 2026-04-28 | MOJO65 | - | Apr 28, 07:25 UTC | Apr 28, 08:55 UTC | 1h 30m |
| 2026-04-24 | MOJO67 | - | Apr 24, 07:35 UTC | Apr 24, 08:20 UTC | 45m |
| 2026-04-24 | MOJO67 | - | Apr 24, 05:50 UTC | Apr 24, 06:30 UTC | 40m |
| 2026-04-24 | MOJO67 | - | Apr 24, 03:25 UTC | Apr 24, 04:15 UTC | 50m |
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 86-0081 page for operator, model, and routing details .