sensors Mode-S transponder
AFA14A
ICAO 24-bit transponder address
- Hex
- AFA14A
- Octal
- 53720512
- Decimal
- 11,510,090
- Flights observed
- 32
- Distinct callsigns
- 3
- Country
- -
- Last broadcast
- 10d ago
Last known position
Callsign history 3 distinct
Recent flights last 32
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-30 | HOBO52 | OKC → OKC | Jun 30, 14:25 UTC | Jun 30, 16:05 UTC | 1h 40m |
| 2026-06-08 | HOBO52 | - | Jun 8, 22:25 UTC | Jun 8, 22:40 UTC | 15m |
| 2026-06-08 | HOBO52 | - | Jun 8, 20:55 UTC | Jun 8, 21:10 UTC | 15m |
| 2026-06-05 | HOBO71 | - | Jun 5, 18:10 UTC | Jun 5, 18:20 UTC | 10m |
| 2026-06-05 | HOBO71 | - | Jun 5, 17:10 UTC | Jun 5, 17:30 UTC | 20m |
| 2026-06-05 | HOBO71 | - | Jun 5, 15:05 UTC | Jun 5, 15:20 UTC | 15m |
| 2026-06-05 | HOBO71 | - | Jun 5, 14:10 UTC | Jun 5, 14:20 UTC | 10m |
| 2026-06-05 | HOBO71 | - | Jun 5, 13:10 UTC | Jun 5, 13:40 UTC | 30m |
| 2026-06-04 | HOBO71 | - | Jun 4, 18:45 UTC | Jun 4, 20:35 UTC | 1h 50m |
| 2026-06-04 | HOBO71 | - | Jun 4, 17:10 UTC | Jun 4, 18:00 UTC | 50m |
| 2026-06-04 | HOBO71 | - | Jun 4, 14:55 UTC | Jun 4, 15:20 UTC | 25m |
| 2026-06-04 | HOBO71 | - | Jun 4, 13:05 UTC | Jun 4, 13:35 UTC | 30m |
| 2026-06-03 | HOBO71 | - | Jun 3, 18:35 UTC | Jun 3, 20:05 UTC | 1h 30m |
| 2026-06-03 | HOBO71 | - | Jun 3, 15:50 UTC | Jun 3, 17:25 UTC | 1h 35m |
| 2026-06-03 | HOBO71 | - | Jun 3, 12:50 UTC | Jun 3, 14:40 UTC | 1h 50m |
| 2026-06-02 | HOBO71 | - | Jun 2, 20:50 UTC | Jun 2, 21:10 UTC | 20m |
| 2026-06-02 | HOBO71 | - | Jun 2, 19:20 UTC | Jun 2, 19:35 UTC | 15m |
| 2026-06-02 | HOBO71 | - | Jun 2, 15:50 UTC | Jun 2, 17:00 UTC | 1h 10m |
| 2026-06-02 | HOBO71 | - | Jun 2, 12:40 UTC | Jun 2, 14:20 UTC | 1h 40m |
| 2026-05-30 | HOBO71 | - | May 30, 19:55 UTC | May 30, 20:15 UTC | 20m |
| 2026-05-30 | HOBO71 | - | May 30, 15:45 UTC | May 30, 17:40 UTC | 1h 55m |
| 2026-05-30 | HOBO71 | - | May 30, 12:55 UTC | May 30, 14:40 UTC | 1h 45m |
| 2026-05-29 | HOBO71 | - | May 29, 21:50 UTC | May 29, 22:05 UTC | 15m |
| 2026-05-29 | HOBO71 | - | May 29, 18:35 UTC | May 29, 19:00 UTC | 25m |
| 2026-05-29 | HOBO71 | - | May 29, 16:25 UTC | May 29, 16:50 UTC | 25m |
| 2026-05-29 | HOBO71 | - | May 29, 14:35 UTC | May 29, 15:05 UTC | 30m |
| 2026-05-28 | HOBO71 | - | May 28, 17:00 UTC | May 28, 18:50 UTC | 1h 50m |
| 2026-05-26 | HOBO61 | - | May 26, 17:04 UTC | May 26, 18:19 UTC | 1h 15m |
| 2026-05-26 | HOBO61 | - | May 26, 15:54 UTC | May 26, 16:15 UTC | 20m |
| 2026-05-12 | HOBO71 | - | May 12, 16:15 UTC | May 12, 18:15 UTC | 2h 0m |
| 2026-05-08 | HOBO71 | - | May 8, 19:40 UTC | May 8, 21:10 UTC | 1h 30m |
| 2026-05-08 | HOBO71 | - | May 8, 15:50 UTC | May 8, 17:20 UTC | 1h 30m |
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.