sensors Mode-S transponder

0ACC60

ICAO 24-bit transponder address · allocated to Costa Rica

Hex
0ACC60
Octal
02546140
Decimal
707,680
Country
CR
Broadcasting now · callsign AVR4801 · 17,500 ft
Flights observed
250
Distinct callsigns
20
Country
CR
Last broadcast
2h ago

Current position

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

Country allocation

The ICAO 24-bit address 0ACC60 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
EFY9131 - 9 2026-07-08
AVR4866 - 8 2026-07-13
AVR4867 - 7 2026-07-13
AVR4857 - 7 2026-07-13
AVR4803 - 7 2026-07-13
AVR4802 - 7 2026-07-13
AVR4874 - 6 2026-07-07
AVR4854 - 6 2026-07-06
AVR4800 - 6 2026-07-14
EFY9127 - 5 2026-07-11
AVR4880 - 5 2026-06-17
AVR4858 - 5 2026-06-07
AVR4853 - 5 2026-06-18
AVR4835 - 5 2026-06-17
AVR4834 - 5 2026-06-17
AVR4833 - 5 2026-05-15
AVR4829 - 5 2026-06-18
AVR4827 - 5 2026-07-06
AVR4824 - 5 2026-07-06
AVR4801 Avianca Express 5 2026-06-05

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 AVR4800 - Jul 14, 01:00 UTCJul 14, 01:20 UTC20m
2026-07-13 AVR4802 - Jul 13, 23:15 UTCJul 14, 00:00 UTC45m
2026-07-13 AVR4803 - Jul 13, 21:50 UTCJul 13, 22:20 UTC30m
2026-07-13 AVR4857 - Jul 13, 18:10 UTCJul 13, 18:20 UTC10m
2026-07-13 AVR4866 - Jul 13, 16:30 UTCJul 13, 17:20 UTC50m
2026-07-13 AVR4867 - Jul 13, 14:25 UTCJul 13, 15:00 UTC35m
2026-07-11 EFY9127 EOH → BOG Jul 11, 20:00 UTCJul 11, 20:45 UTC45m
2026-07-11 EFY8984 - Jul 11, 16:10 UTCJul 11, 16:20 UTC10m
2026-07-10 EFY8989 - Jul 10, 22:05 UTCJul 10, 22:15 UTC10m
2026-07-10 EFY8988 - Jul 10, 20:15 UTCJul 10, 20:25 UTC10m
2026-07-10 EFY8987 - Jul 10, 19:10 UTCJul 10, 19:25 UTC15m
2026-07-10 EFY8986 - Jul 10, 17:20 UTCJul 10, 17:30 UTC10m
2026-07-10 EFY9053 - Jul 10, 15:25 UTCJul 10, 15:35 UTC10m
2026-07-10 EFY9052 - Jul 10, 14:05 UTCJul 10, 14:15 UTC10m
2026-07-10 EFY9110 BOG → EOH Jul 10, 12:55 UTCJul 10, 13:30 UTC35m
2026-07-10 EFY9109 EOH → BOG Jul 10, 10:55 UTCJul 10, 11:40 UTC45m
2026-07-09 EFY9128 BOG → EOH Jul 9, 22:00 UTCJul 9, 22:40 UTC40m
2026-07-09 EFY9127 EOH → BOG Jul 9, 20:15 UTCJul 9, 21:00 UTC45m
2026-07-09 EFY9110 BOG → EOH Jul 9, 18:40 UTCJul 9, 19:20 UTC40m
2026-07-09 EFY9107 EOH → BOG Jul 9, 15:25 UTCJul 9, 16:15 UTC50m
2026-07-09 EFY9106 - Jul 9, 14:05 UTCJul 9, 14:45 UTC40m
2026-07-09 EFY9105 - Jul 9, 12:10 UTCJul 9, 13:05 UTC55m
2026-07-09 EFY9104 - Jul 9, 11:25 UTCJul 9, 11:35 UTC10m
2026-07-09 EFY9048 - Jul 9, 00:25 UTCJul 9, 00:40 UTC15m
2026-07-08 EFY9131 - Jul 8, 23:10 UTCJul 8, 23:20 UTC10m
2026-07-08 EFY9048 - Jul 8, 00:50 UTCJul 8, 01:10 UTC20m
2026-07-07 EFY9131 - Jul 7, 23:10 UTCJul 7, 23:25 UTC15m
2026-07-07 EFY9130 - Jul 7, 21:10 UTCJul 7, 21:25 UTC15m
2026-07-07 EFY9045 - Jul 7, 18:55 UTCJul 7, 19:20 UTC25m
2026-07-07 EFY9044 - Jul 7, 17:15 UTCJul 7, 17:30 UTC15m
2026-07-07 EFY9015 - Jul 7, 15:35 UTCJul 7, 16:10 UTC35m
2026-07-07 EFY9014 - Jul 7, 13:50 UTCJul 7, 14:00 UTC10m
2026-07-07 AVR4874 - Jul 7, 00:10 UTCJul 7, 00:35 UTC25m
2026-07-06 AVR4895 - Jul 6, 22:15 UTCJul 6, 22:30 UTC15m
2026-07-06 AVR4827 - Jul 6, 21:05 UTCJul 6, 21:25 UTC20m
2026-07-06 AVR4824 - Jul 6, 19:35 UTCJul 6, 19:45 UTC10m
2026-07-06 AVR4854 - Jul 6, 18:30 UTCJul 6, 18:40 UTC10m
2026-07-06 AVR5212 - Jul 6, 04:15 UTCJul 6, 04:25 UTC10m
2026-07-06 AVR5213 - Jul 6, 02:15 UTCJul 6, 02:30 UTC15m
2026-07-06 AVR4874 - Jul 6, 00:55 UTCJul 6, 01:15 UTC20m
2026-06-20 EFY9131 - Jun 20, 22:25 UTCJun 20, 22:35 UTC10m
2026-06-20 EFY9130 BOG → EOH Jun 20, 21:40 UTCJun 20, 21:49 UTC10m
2026-06-19 EFY9046 - Jun 19, 20:14 UTCJun 19, 20:34 UTC20m
2026-06-19 EFY9017 - Jun 19, 18:49 UTCJun 19, 19:09 UTC20m
2026-06-19 EFY9016 - Jun 19, 17:14 UTCJun 19, 17:29 UTC15m
2026-06-19 EFY7835 MZL → BOG Jun 19, 16:04 UTCJun 19, 16:19 UTC15m
2026-06-19 EFY7834 BOG → MZL Jun 19, 14:19 UTCJun 19, 14:39 UTC20m
2026-06-19 EFY9041 - Jun 19, 12:54 UTCJun 19, 13:04 UTC10m
2026-06-19 EFY9040 - Jun 19, 11:09 UTCJun 19, 11:30 UTC20m
2026-06-19 AVR5212 - Jun 19, 03:49 UTCJun 19, 04:14 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.

Mode-S 0ACC60 frequently asked

What is Mode-S code 0ACC60?
0ACC60 is an ICAO 24-bit transponder address. Allocated to Costa Rica.
Where is Mode-S 0ACC60 registered?
Mode-S code 0ACC60 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 0ACC60 broadcasting right now?
Yes. Mode-S 0ACC60 is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0ACC60, octal 02546140, decimal 707,680.
What flights does 0ACC60 operate?
Mode-S 0ACC60 has broadcast 20 distinct callsigns, including EFY9131, AVR4866, AVR4867, AVR4857, AVR4803.