sensors Mode-S transponder
0ACA5D
ICAO 24-bit transponder address · allocated to Costa Rica
Currently assigned to HK-5388 · AIRBUS A-320neo
- Hex
- 0ACA5D
- Octal
- 02545135
- Decimal
- 707,165
- Country
- CR
- Tail
- HK-5388
- Type
- A20N
- Flights observed
- 328
- Distinct callsigns
- 20
- Country
- CR
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address 0ACA5D 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 | Avianca - Aerovias Nacionales de Colombia, S.A. | 13 | 2026-06-08 |
| AVA204 | Avianca - Aerovias Nacionales de Colombia, S.A. | 10 | 2026-06-07 |
| AVA029 | Avianca - Aerovias Nacionales de Colombia, S.A. | 10 | 2026-06-03 |
| AVA261 | - | 8 | 2026-07-13 |
| AVA260 | - | 8 | 2026-07-13 |
| AVA247 | Avianca - Aerovias Nacionales de Colombia, S.A. | 8 | 2026-06-27 |
| AVA246 | - | 7 | 2026-06-27 |
| AVA218 | - | 7 | 2026-07-11 |
| AVA050 | Avianca - Aerovias Nacionales de Colombia, S.A. | 7 | 2026-06-05 |
| AVA154 | - | 6 | 2026-07-05 |
| AVA028 | Avianca - Aerovias Nacionales de Colombia, S.A. | 6 | 2026-06-03 |
| AVA239 | - | 5 | 2026-07-12 |
| AVA227 | Avianca - Aerovias Nacionales de Colombia, S.A. | 5 | 2026-06-09 |
| AVA217 | Avianca - Aerovias Nacionales de Colombia, S.A. | 5 | 2026-06-05 |
| AVA155 | - | 5 | 2026-06-24 |
| AVA149 | Avianca - Aerovias Nacionales de Colombia, S.A. | 5 | 2026-05-28 |
| AVA116 | - | 5 | 2026-07-11 |
| AVA109 | - | 5 | 2026-06-29 |
| AVA049 | Avianca - Aerovias Nacionales de Colombia, S.A. | 5 | 2026-06-05 |
| AVA241 | - | 4 | 2026-07-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | AVA8459 | - | Jul 14, 14:15 UTC | Jul 14, 14:25 UTC | 10m |
| 2026-07-13 | AVA241 | - | Jul 13, 21:55 UTC | Jul 13, 22:10 UTC | 15m |
| 2026-07-13 | AVA260 | - | Jul 13, 10:40 UTC | Jul 13, 16:40 UTC | 6h 0m |
| 2026-07-13 | AVA261 | - | Jul 13, 04:15 UTC | Jul 13, 08:40 UTC | 4h 25m |
| 2026-07-13 | AVA261 | - | Jul 13, 03:20 UTC | Jul 13, 03:30 UTC | 10m |
| 2026-07-12 | AVA189 | DFW → BOG | Jul 12, 20:55 UTC | Jul 13, 01:45 UTC | 4h 50m |
| 2026-07-12 | AVA188 | BOG → DFW | Jul 12, 13:05 UTC | Jul 12, 18:20 UTC | 5h 15m |
| 2026-07-12 | AVA239 | BOG → BOG | Jul 12, 03:01 UTC | Jul 12, 10:50 UTC | 7h 50m |
| 2026-07-11 | AVA116 | - | Jul 11, 23:25 UTC | Jul 12, 01:10 UTC | 1h 45m |
| 2026-07-11 | AVA116 | - | Jul 11, 20:00 UTC | Jul 11, 20:10 UTC | 10m |
| 2026-07-11 | AVA115 | - | Jul 11, 14:15 UTC | Jul 11, 14:25 UTC | 10m |
| 2026-07-11 | AVA115 | - | Jul 11, 13:00 UTC | Jul 11, 13:15 UTC | 15m |
| 2026-07-11 | AVA218 | - | Jul 11, 05:01 UTC | Jul 11, 11:20 UTC | 6h 20m |
| 2026-07-10 | AVA255 | YYZ → EZE | Jul 10, 13:15 UTC | Jul 11, 03:10 UTC | 13h 55m |
| 2026-07-10 | AVA254 | BOG → YYZ | Jul 10, 05:30 UTC | Jul 10, 11:05 UTC | 5h 35m |
| 2026-07-09 | AVA9816 | - | Jul 9, 22:25 UTC | Jul 9, 22:40 UTC | 15m |
| 2026-07-09 | AVA9205 | - | Jul 9, 20:15 UTC | Jul 9, 20:30 UTC | 15m |
| 2026-07-09 | AVA067 | - | Jul 9, 14:55 UTC | Jul 9, 18:05 UTC | 3h 10m |
| 2026-07-08 | AVA066 | - | Jul 8, 22:15 UTC | Jul 9, 01:35 UTC | 3h 20m |
| 2026-07-08 | AVA257 | - | Jul 8, 17:45 UTC | Jul 8, 19:10 UTC | 1h 25m |
| 2026-07-08 | AVA112 | - | Jul 8, 05:45 UTC | Jul 8, 16:15 UTC | 10h 30m |
| 2026-07-07 | AVA111 | - | Jul 7, 22:05 UTC | Jul 8, 04:05 UTC | 6h 0m |
| 2026-07-07 | AVA269 | - | Jul 7, 17:50 UTC | Jul 7, 19:15 UTC | 1h 25m |
| 2026-07-07 | AVA256 | - | Jul 7, 13:20 UTC | Jul 7, 16:20 UTC | 3h 0m |
| 2026-07-07 | AVA240 | - | Jul 7, 08:40 UTC | Jul 7, 09:10 UTC | 30m |
| 2026-07-06 | AVA241 | - | Jul 6, 21:55 UTC | Jul 6, 23:20 UTC | 1h 25m |
| 2026-07-06 | AVA059 | - | Jul 6, 16:20 UTC | Jul 6, 16:40 UTC | 20m |
| 2026-07-06 | AVA263 | - | Jul 6, 05:00 UTC | Jul 6, 07:30 UTC | 2h 30m |
| 2026-07-05 | AVA262 | - | Jul 5, 23:15 UTC | Jul 6, 02:15 UTC | 3h 0m |
| 2026-07-05 | AVA154 | - | Jul 5, 10:10 UTC | Jul 5, 15:15 UTC | 5h 5m |
| 2026-07-04 | AVA211 | JFK → AEP | Jul 4, 19:55 UTC | Jul 5, 08:20 UTC | 12h 25m |
| 2026-07-04 | AVA210 | - | Jul 4, 15:20 UTC | Jul 4, 17:50 UTC | 2h 30m |
| 2026-07-03 | AVA184 | GRU → BOG | Jul 3, 23:50 UTC | Jul 4, 04:25 UTC | 4h 35m |
| 2026-07-03 | AVA199 | - | Jul 3, 04:00 UTC | Jul 3, 19:10 UTC | 15h 10m |
| 2026-07-03 | AVA118 | - | Jul 3, 00:10 UTC | Jul 3, 00:55 UTC | 45m |
| 2026-07-02 | AVA129 | PUJ → BOG | Jul 2, 14:05 UTC | Jul 2, 18:10 UTC | 4h 5m |
| 2026-07-02 | AVA187 | - | Jul 2, 07:00 UTC | Jul 2, 08:40 UTC | 1h 40m |
| 2026-07-01 | AVA186 | GUA → MEX | Jul 1, 20:20 UTC | Jul 2, 04:35 UTC | 8h 15m |
| 2026-06-30 | AVA034 | CTG → MIA | Jun 30, 23:45 UTC | Jul 1, 19:00 UTC | 19h 15m |
| 2026-06-30 | AVA034 | CTG → MIA | Jun 30, 22:50 UTC | Jul 1, 19:00 UTC | 20h 10m |
| 2026-06-30 | AVA258 | - | Jun 30, 20:55 UTC | Jun 30, 21:05 UTC | 10m |
| 2026-06-30 | AVA258 | - | Jun 30, 19:50 UTC | Jun 30, 20:10 UTC | 20m |
| 2026-06-30 | AVA110 | - | Jun 30, 10:20 UTC | Jun 30, 15:30 UTC | 5h 10m |
| 2026-06-29 | AVA109 | - | Jun 29, 20:00 UTC | Jun 30, 08:30 UTC | 12h 31m |
| 2026-06-29 | AVA194 | BOG → TPA | Jun 29, 16:59 UTC | Jun 29, 17:49 UTC | 50m |
| 2026-06-29 | AVA201 | - | Jun 29, 03:29 UTC | Jun 29, 06:14 UTC | 2h 45m |
| 2026-06-28 | AVA200 | - | Jun 28, 22:20 UTC | Jun 29, 01:20 UTC | 3h 0m |
| 2026-06-28 | AVA154 | - | Jun 28, 10:15 UTC | Jun 28, 15:20 UTC | 5h 5m |
| 2026-06-27 | AVA247 | IAD → BOG | Jun 27, 20:04 UTC | Jun 28, 08:50 UTC | 12h 45m |
| 2026-06-27 | AVA246 | - | Jun 27, 16:10 UTC | Jun 27, 17:55 UTC | 1h 45m |
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-5388 page for operator, model, and routing details .