sensors Mode-S transponder

0AC3F9

ICAO 24-bit transponder address · allocated to Costa Rica

Currently assigned to HK-5294 · ATR-72-600

Hex
0AC3F9
Octal
02541771
Decimal
705,529
Country
CR
Tail
HK-5294
Type
AT76
Broadcasting now · callsign AVR4854 · 16,675 ft
Flights observed
407
Distinct callsigns
20
Country
CR
Last broadcast
Jul 26, 21:30 UTC

Current position

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

Country allocation

The ICAO 24-bit address 0AC3F9 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
AVR4853 - 13 2026-07-24
AVR4824 - 13 2026-07-18
AVR4810 - 13 2026-07-18
AVR4874 - 12 2026-07-19
AVR4860 - 12 2026-07-17
AVR4855 - 12 2026-07-17
AVR4854 - 12 2026-07-10
AVR4829 Avianca Express 12 2026-07-17
AVR4859 - 11 2026-07-16
AVR4835 - 11 2026-07-16
AVR4828 - 11 2026-07-17
AVR4880 - 10 2026-07-16
AVR4852 - 10 2026-07-24
AVR4827 - 10 2026-07-18
AVR4809 - 10 2026-07-18
AVR4881 - 9 2026-07-16
AVR4858 - 9 2026-07-23
AVR4857 Avianca Express 9 2026-07-23
AVR4834 - 9 2026-07-16
AVR4800 Avianca Express 9 2026-07-25

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 EFY9130 BOG → EOH Jul 26, 20:50 UTCJul 26, 21:30 UTC40m
2026-07-26 EFY7817 MZL → BOG Jul 26, 18:15 UTCJul 26, 18:50 UTC35m
2026-07-26 EFY7816 BOG → MZL Jul 26, 17:00 UTCJul 26, 17:30 UTC30m
2026-07-25 EFY9047 NVA → BOG Jul 25, 23:00 UTCJul 25, 23:25 UTC25m
2026-07-25 EFY9046 BOG → NVA Jul 25, 21:10 UTCJul 25, 21:25 UTC15m
2026-07-25 AVR4801 BGA → BOG Jul 25, 03:30 UTCJul 25, 03:45 UTC15m
2026-07-25 AVR4800 BOG → BGA Jul 25, 01:20 UTCJul 25, 01:40 UTC20m
2026-07-24 EFY9031 PTX → BOG Jul 24, 22:50 UTCJul 24, 23:35 UTC45m
2026-07-24 EFY9130 BOG → EOH Jul 24, 21:35 UTCJul 24, 22:10 UTC35m
2026-07-24 EFY7835 MZL → BOG Jul 24, 15:30 UTCJul 24, 16:15 UTC45m
2026-07-24 EFY7834 BOG → MZL Jul 24, 14:20 UTCJul 24, 14:40 UTC20m
2026-07-24 EFY9041 NVA → BOG Jul 24, 12:45 UTCJul 24, 13:10 UTC25m
2026-07-24 EFY9040 BOG → NVA Jul 24, 11:20 UTCJul 24, 11:30 UTC10m
2026-07-24 AVR4852 - Jul 24, 02:45 UTCJul 24, 02:55 UTC10m
2026-07-24 AVR4853 - Jul 24, 01:55 UTCJul 24, 02:05 UTC10m
2026-07-23 AVR4802 - Jul 23, 23:05 UTCJul 23, 23:45 UTC40m
2026-07-23 AVR4803 - Jul 23, 21:40 UTCJul 23, 22:15 UTC35m
2026-07-23 AVR4858 - Jul 23, 20:10 UTCJul 23, 20:35 UTC25m
2026-07-23 AVR4857 BOG → AXM Jul 23, 18:10 UTCJul 23, 18:25 UTC15m
2026-07-23 AVR4866 - Jul 23, 17:05 UTCJul 23, 17:15 UTC10m
2026-07-23 AVR4867 BOG → AXM Jul 23, 14:45 UTCJul 23, 15:20 UTC35m
2026-07-23 AVR4801 BGA → BOG Jul 23, 03:40 UTCJul 23, 03:50 UTC10m
2026-07-22 AVR9264 - Jul 22, 23:55 UTCJul 23, 00:10 UTC15m
2026-07-22 AVR9265 - Jul 22, 22:50 UTCJul 22, 23:00 UTC10m
2026-07-22 AVR9255 - Jul 22, 21:10 UTCJul 22, 21:30 UTC20m
2026-07-22 AVR9254 - Jul 22, 20:10 UTCJul 22, 20:20 UTC10m
2026-07-22 AVR9277 MTR → MDE Jul 22, 15:10 UTCJul 22, 15:20 UTC10m
2026-07-21 EFY9088 EOH → BGA Jul 21, 22:30 UTCJul 21, 22:35 UTC5m
2026-07-21 EFY9089 BGA → EOH Jul 21, 21:35 UTCJul 21, 21:45 UTC10m
2026-07-21 AVR9264 - Jul 21, 02:00 UTCJul 21, 02:10 UTC10m
2026-07-21 AVR9265 - Jul 21, 00:35 UTCJul 21, 01:00 UTC25m
2026-07-20 AVR9255 - Jul 20, 20:30 UTCJul 20, 20:50 UTC20m
2026-07-20 AVR9254 - Jul 20, 19:10 UTCJul 20, 19:40 UTC30m
2026-07-20 AVR9277 MTR → MDE Jul 20, 14:30 UTCJul 20, 14:45 UTC15m
2026-07-20 AVR4800 - Jul 20, 01:00 UTCJul 20, 01:15 UTC15m
2026-07-19 AVR4802 - Jul 19, 23:10 UTCJul 19, 23:50 UTC40m
2026-07-19 AVR4803 - Jul 19, 21:30 UTCJul 19, 22:05 UTC35m
2026-07-19 AVR4858 - Jul 19, 20:05 UTCJul 19, 20:25 UTC20m
2026-07-19 AVR4857 BOG → AXM Jul 19, 18:10 UTCJul 19, 18:25 UTC15m
2026-07-19 AVR4866 - Jul 19, 16:55 UTCJul 19, 17:05 UTC10m
2026-07-19 AVR4867 - Jul 19, 14:25 UTCJul 19, 14:55 UTC30m
2026-07-19 AVR5212 - Jul 19, 03:35 UTCJul 19, 03:55 UTC20m
2026-07-19 AVR5213 - Jul 19, 01:45 UTCJul 19, 02:20 UTC35m
2026-07-19 AVR4874 - Jul 19, 00:15 UTCJul 19, 00:40 UTC25m
2026-07-18 AVR4873 - Jul 18, 22:30 UTCJul 18, 22:45 UTC15m
2026-07-18 AVR4827 - Jul 18, 20:55 UTCJul 18, 21:20 UTC25m
2026-07-18 AVR4824 - Jul 18, 19:05 UTCJul 18, 19:15 UTC10m
2026-07-18 EFY8941 - Jul 18, 17:05 UTCJul 18, 17:50 UTC45m
2026-07-18 EFY8940 - Jul 18, 15:00 UTCJul 18, 15:35 UTC35m
2026-07-18 AVR4809 - Jul 18, 13:25 UTCJul 18, 13:50 UTC25m

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

Mode-S 0AC3F9 frequently asked

What is Mode-S code 0AC3F9?
0AC3F9 is an ICAO 24-bit transponder address. Allocated to Costa Rica. Assigned to HK-5294.
Where is Mode-S 0AC3F9 registered?
Mode-S code 0AC3F9 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 0AC3F9 broadcasting right now?
Yes. Mode-S 0AC3F9 is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0AC3F9, octal 02541771, decimal 705,529.
What flights does 0AC3F9 operate?
Mode-S 0AC3F9 has broadcast 20 distinct callsigns, including AVR4853, AVR4824, AVR4810, AVR4874, AVR4860.