sensors Mode-S transponder

0ACA66

ICAO 24-bit transponder address · allocated to Costa Rica

Currently assigned to HK-5393 · AIRBUS A-320

Hex
0ACA66
Octal
02545146
Decimal
707,174
Country
CR
Tail
HK-5393
Type
A320
Broadcasting now · callsign AVA9309 · 19,000 ft
Flights observed
104
Distinct callsigns
20
Country
CR
Last broadcast
1h ago

Current position

0ACA66 is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address 0ACA66 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

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-30 AVA9368 BOG → MDE May 30, 02:06 UTCMay 30, 02:20 UTC14m
2026-05-29 AVA9301 MDE → BOG May 29, 23:30 UTCMay 29, 23:40 UTC10m
2026-05-29 AVA9328 BOG → MDE May 29, 21:20 UTCMay 29, 21:35 UTC15m
2026-05-29 AVA9711 BGA → BOG May 29, 19:05 UTCMay 29, 19:20 UTC15m
2026-05-29 AVA9710 BOG → BGA May 29, 17:15 UTCMay 29, 17:30 UTC15m
2026-05-29 AVA8427 MDE → BOG May 29, 15:00 UTCMay 29, 15:15 UTC15m
2026-05-29 AVA9466 BOG → BGA May 29, 03:05 UTCMay 29, 03:20 UTC15m
2026-05-28 AVA8559 CTG → BOG May 28, 21:40 UTCMay 28, 22:05 UTC25m
2026-05-28 AVA8559 CTG → BOG May 28, 16:40 UTCMay 28, 20:05 UTC3h 25m
2026-05-28 AVA9458 BOG → CUC May 28, 03:25 UTCMay 28, 03:40 UTC15m
2026-05-28 AVA9371 BGA → BOG May 28, 01:50 UTCMay 28, 02:05 UTC15m
2026-05-28 AVA9472 BOG → BGA May 28, 00:00 UTCMay 28, 00:20 UTC20m
2026-05-27 AVA9351 MDE → BOG May 27, 22:25 UTCMay 27, 22:45 UTC20m
2026-05-27 AVA9340 BOG → MDE May 27, 20:30 UTCMay 27, 20:40 UTC10m
2026-05-27 AVA9243 MDE → BOG May 27, 16:55 UTCMay 27, 17:15 UTC20m
2026-05-26 AVA9448 BOG → CUC May 26, 18:24 UTCMay 26, 18:40 UTC15m
2026-05-26 AVA8522 CLO → BOG May 26, 16:35 UTCMay 26, 16:59 UTC25m
2026-05-26 AVA8523 BOG → CLO May 26, 14:30 UTCMay 26, 14:40 UTC10m
2026-05-26 AVA8459 MTR → BOG May 26, 12:45 UTCMay 26, 13:04 UTC20m
2026-05-26 AVA8506 BOG → MTR May 26, 10:20 UTCMay 26, 10:34 UTC15m
2026-05-26 AVA8581 VUP → BOG May 26, 03:30 UTCMay 26, 03:45 UTC15m
2026-05-26 AVA8580 BOG → VUP May 26, 00:49 UTCMay 26, 01:05 UTC15m
2026-05-25 AVA9351 MDE → BOG May 25, 22:44 UTCMay 25, 23:04 UTC20m
2026-05-25 AVA9340 BOG → MDE May 25, 20:40 UTCMay 25, 20:50 UTC10m
2026-05-25 AVA9411 VUP → BOG May 25, 18:30 UTCMay 25, 18:45 UTC15m
2026-05-25 AVA9216 CLO → BOG May 25, 15:55 UTCMay 25, 16:10 UTC15m
2026-05-25 AVA8416 CLO → BOG May 25, 13:55 UTCMay 25, 14:10 UTC15m
2026-05-25 AVA8493 BOG → CLO May 25, 12:05 UTCMay 25, 12:20 UTC15m
2026-05-25 AVA9513 BAQ → BOG May 25, 03:50 UTCMay 25, 04:00 UTC10m
2026-05-24 AVA8491 SMR → BOG May 24, 23:25 UTCMay 24, 23:35 UTC10m
2026-05-24 AVA9763 SMR → BOG May 24, 12:25 UTCMay 24, 12:40 UTC15m
2026-05-24 AVA8486 BOG → SMR May 24, 02:15 UTCMay 24, 02:30 UTC15m
2026-05-24 AVA9566 CLO → BOG May 24, 00:20 UTCMay 24, 00:35 UTC15m
2026-05-23 AVA9527 BOG → CLO May 23, 22:25 UTCMay 23, 22:35 UTC10m
2026-05-23 AVA8531 BAQ → BOG May 23, 20:25 UTCMay 23, 20:40 UTC15m
2026-05-23 AVA9524 BOG → BAQ May 23, 17:20 UTCMay 23, 17:35 UTC15m
2026-05-23 AVA9445 ADZ → BOG May 23, 15:45 UTCMay 23, 16:05 UTC20m
2026-05-23 AVA9445 ADZ → BOG May 23, 14:20 UTCMay 23, 14:30 UTC10m
2026-05-23 AVA9774 BOG → SMR May 23, 13:15 UTCMay 23, 13:20 UTC5m
2026-05-23 AVA9774 BOG → SMR May 23, 11:40 UTCMay 23, 12:00 UTC20m
2026-05-23 AVA9781 ADZ → BOG May 23, 04:00 UTCMay 23, 04:20 UTC20m
2026-05-23 AVA9781 ADZ → BOG May 23, 02:40 UTCMay 23, 02:50 UTC10m
2026-05-23 AVA9780 BOG → ADZ May 23, 01:30 UTCMay 23, 01:35 UTC5m
2026-05-23 AVA9780 BOG → ADZ May 23, 00:00 UTCMay 23, 00:15 UTC15m
2026-05-22 AVA8563 BGA → BOG May 22, 22:05 UTCMay 22, 22:20 UTC15m
2026-05-22 AVA9470 - May 22, 20:10 UTCMay 22, 20:25 UTC15m
2026-05-22 AVA9216 CLO → BOG May 22, 15:30 UTCMay 22, 15:45 UTC15m
2026-05-22 AVA8416 CLO → BOG May 22, 14:00 UTCMay 22, 14:15 UTC15m
2026-05-22 AVA8493 BOG → CLO May 22, 12:00 UTCMay 22, 12:15 UTC15m
2026-05-22 AVA8581 VUP → BOG May 22, 03:15 UTCMay 22, 03:30 UTC15m

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-5393 page for operator, model, and routing details .

Mode-S 0ACA66 frequently asked

What is Mode-S code 0ACA66?
0ACA66 is an ICAO 24-bit transponder address. Allocated to Costa Rica. Assigned to HK-5393.
Where is Mode-S 0ACA66 registered?
Mode-S code 0ACA66 is allocated to Costa Rica (CR). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0ACA66 broadcasting right now?
Yes. Mode-S 0ACA66 is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0ACA66, octal 02545146, decimal 707,174.
What flights does 0ACA66 operate?
Mode-S 0ACA66 has broadcast 20 distinct callsigns, including AVA9780, AVA9781, AVA9774, AVA9445, AVA9701.