sensors Mode-S transponder
0AC9EF
ICAO 24-bit transponder address · allocated to Costa Rica
Currently assigned to HK-5366 · AIRBUS A-320neo
- Hex
- 0AC9EF
- Octal
- 02544757
- Decimal
- 707,055
- Country
- CR
- Tail
- HK-5366
- Type
- A20N
- Flights observed
- 302
- Distinct callsigns
- 20
- Country
- CR
- Last broadcast
- 43m ago
Last known position
Country allocation
The ICAO 24-bit address 0AC9EF falls within the block assigned to Costa Rica (CR) by ICAO Annex 10, Volume III. Every aircraft registered in Costa Rica 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AVA205 | - | 11 | 2026-07-04 |
| AVA204 | - | 11 | 2026-07-04 |
| AVA154 | - | 11 | 2026-07-12 |
| AVA155 | - | 10 | 2026-07-12 |
| AVA198 | Avianca - Aerovias Nacionales de Colombia, S.A. | 8 | 2026-04-25 |
| AVA197 | Avianca - Aerovias Nacionales de Colombia, S.A. | 8 | 2026-04-24 |
| AVA073 | - | 8 | 2026-06-16 |
| AVA261 | - | 7 | 2026-06-26 |
| AVA260 | - | 6 | 2026-06-26 |
| AVA239 | - | 6 | 2026-07-06 |
| AVA160 | - | 6 | 2026-07-03 |
| AVA116 | - | 6 | 2026-06-14 |
| AVA247 | - | 5 | 2026-07-11 |
| AVA246 | - | 5 | 2026-07-11 |
| AVA240 | - | 5 | 2026-07-13 |
| AVA201 | Avianca - Aerovias Nacionales de Colombia, S.A. | 5 | 2026-04-27 |
| AVA200 | Avianca - Aerovias Nacionales de Colombia, S.A. | 5 | 2026-04-26 |
| AVA105 | - | 5 | 2026-07-10 |
| AVA072 | Avianca - Aerovias Nacionales de Colombia, S.A. | 5 | 2026-06-16 |
| AVA021 | Avianca - Aerovias Nacionales de Colombia, S.A. | 5 | 2026-06-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | AVA110 | - | Jul 14, 10:40 UTC | Jul 14, 15:25 UTC | 4h 45m |
| 2026-07-14 | AVA109 | - | Jul 14, 03:00 UTC | Jul 14, 09:05 UTC | 6h 5m |
| 2026-07-13 | AVA069 | CUN → BOG | Jul 13, 22:00 UTC | Jul 14, 00:55 UTC | 2h 55m |
| 2026-07-13 | AVA068 | BOG → CUN | Jul 13, 17:25 UTC | Jul 13, 20:40 UTC | 3h 15m |
| 2026-07-13 | AVA240 | - | Jul 13, 11:40 UTC | Jul 13, 13:25 UTC | 1h 45m |
| 2026-07-12 | AVA241 | - | Jul 12, 21:40 UTC | Jul 12, 21:55 UTC | 15m |
| 2026-07-12 | AVA9361 | - | Jul 12, 19:35 UTC | Jul 12, 19:55 UTC | 20m |
| 2026-07-12 | AVA9330 | - | Jul 12, 17:55 UTC | Jul 12, 18:05 UTC | 10m |
| 2026-07-12 | AVA154 | AEP → BOG | Jul 12, 10:35 UTC | Jul 12, 16:15 UTC | 5h 40m |
| 2026-07-12 | AVA155 | BOG → AEP | Jul 12, 03:01 UTC | Jul 12, 09:00 UTC | 6h 0m |
| 2026-07-11 | AVA247 | IAD → BOG | Jul 11, 19:50 UTC | Jul 12, 00:55 UTC | 5h 5m |
| 2026-07-11 | AVA246 | BOG → IAD | Jul 11, 13:15 UTC | Jul 11, 18:10 UTC | 4h 55m |
| 2026-07-11 | AVA124 | - | Jul 11, 10:40 UTC | Jul 11, 11:05 UTC | 25m |
| 2026-07-10 | AVA105 | BOG → BOG | Jul 10, 13:25 UTC | Jul 11, 01:15 UTC | 11h 50m |
| 2026-07-10 | AVA224 | BOG → BOG | Jul 10, 03:45 UTC | Jul 10, 11:30 UTC | 7h 45m |
| 2026-07-09 | AVA104 | - | Jul 9, 13:40 UTC | Jul 10, 01:35 UTC | 11h 55m |
| 2026-07-08 | AVA184 | - | Jul 8, 21:55 UTC | Jul 9, 03:00 UTC | 5h 5m |
| 2026-07-08 | AVA199 | - | Jul 8, 16:05 UTC | Jul 8, 20:10 UTC | 4h 5m |
| 2026-07-07 | AVA9322 | - | Jul 7, 01:35 UTC | Jul 7, 01:45 UTC | 10m |
| 2026-07-06 | AVA079 | - | Jul 6, 22:40 UTC | Jul 6, 23:55 UTC | 1h 15m |
| 2026-07-06 | AVA078 | - | Jul 6, 19:40 UTC | Jul 6, 20:50 UTC | 1h 10m |
| 2026-07-06 | AVA943 | - | Jul 6, 17:55 UTC | Jul 6, 18:15 UTC | 20m |
| 2026-07-06 | AVA239 | - | Jul 6, 03:20 UTC | Jul 6, 10:05 UTC | 6h 45m |
| 2026-07-06 | AVA219 | - | Jul 6, 00:15 UTC | Jul 6, 00:30 UTC | 15m |
| 2026-07-05 | AVA219 | - | Jul 5, 21:00 UTC | Jul 5, 21:50 UTC | 50m |
| 2026-07-05 | AVA216 | - | Jul 5, 17:35 UTC | Jul 5, 18:35 UTC | 1h 0m |
| 2026-07-04 | AVA146 | - | Jul 4, 20:30 UTC | Jul 5, 00:55 UTC | 4h 25m |
| 2026-07-04 | AVA205 | - | Jul 4, 05:55 UTC | Jul 4, 18:55 UTC | 13h 0m |
| 2026-07-04 | AVA204 | - | Jul 4, 00:45 UTC | Jul 4, 03:45 UTC | 3h 0m |
| 2026-07-03 | AVA160 | - | Jul 3, 05:30 UTC | Jul 3, 10:05 UTC | 4h 35m |
| 2026-07-02 | AVA161 | BOG → GRU | Jul 2, 18:10 UTC | Jul 3, 03:45 UTC | 9h 35m |
| 2026-07-02 | AVA268 | - | Jul 2, 05:45 UTC | Jul 2, 16:40 UTC | 10h 55m |
| 2026-07-01 | AVA111 | CUN → EZE | Jul 1, 18:15 UTC | Jul 2, 04:05 UTC | 9h 50m |
| 2026-07-01 | AVA205 | YYZ → CUN | Jul 1, 05:10 UTC | Jul 1, 16:45 UTC | 11h 35m |
| 2026-07-01 | AVA204 | - | Jul 1, 00:20 UTC | Jul 1, 03:05 UTC | 2h 45m |
| 2026-06-30 | AVA227 | - | Jun 30, 13:55 UTC | Jun 30, 16:30 UTC | 2h 35m |
| 2026-06-30 | AVA222 | NAS → BOS | Jun 30, 07:45 UTC | Jun 30, 10:40 UTC | 2h 55m |
| 2026-06-29 | AVA267 | - | Jun 29, 20:30 UTC | Jun 29, 23:29 UTC | 3h 0m |
| 2026-06-29 | AVA266 | - | Jun 29, 15:30 UTC | Jun 29, 18:44 UTC | 3h 15m |
| 2026-06-29 | AVA248 | - | Jun 29, 04:30 UTC | Jun 29, 09:00 UTC | 4h 30m |
| 2026-06-28 | AVA249 | - | Jun 28, 20:59 UTC | Jun 29, 01:14 UTC | 4h 15m |
| 2026-06-27 | AVA222 | - | Jun 27, 08:05 UTC | Jun 27, 09:44 UTC | 1h 40m |
| 2026-06-26 | AVA260 | - | Jun 26, 10:39 UTC | Jun 26, 13:49 UTC | 3h 10m |
| 2026-06-26 | AVA261 | - | Jun 26, 04:30 UTC | Jun 26, 08:45 UTC | 4h 15m |
| 2026-06-25 | AVA105 | - | Jun 25, 14:39 UTC | Jun 26, 00:15 UTC | 9h 35m |
| 2026-06-24 | AVA154 | - | Jun 24, 10:19 UTC | Jun 24, 15:09 UTC | 4h 50m |
| 2026-06-24 | AVA155 | - | Jun 24, 03:35 UTC | Jun 24, 08:30 UTC | 4h 55m |
| 2026-06-23 | AVA240 | - | Jun 23, 08:25 UTC | Jun 23, 08:59 UTC | 35m |
| 2026-06-22 | AVA260 | - | Jun 22, 10:30 UTC | Jun 22, 15:29 UTC | 5h 0m |
| 2026-06-21 | AVA261 | - | Jun 21, 20:09 UTC | Jun 22, 08:40 UTC | 12h 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.
Prefer a tail-number view? See the HK-5366 page for operator, model, and routing details .