Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

60111C

ICAO 24-bit transponder address · allocated to Kyrgyzstan

Currently assigned to EX-32014 · AIRBUS A-320

Hex
60111C
Octal
30010434
Decimal
6,295,836
Country
KG
Tail
EX-32014
Type
A320
No current signal · last broadcast 1h ago
Flights observed
71
Distinct callsigns
6
Country
KG
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S 60111C.

Country allocation

The ICAO 24-bit address 60111C falls within the block assigned to Kyrgyzstan (KG) by ICAO Annex 10, Volume III. Every aircraft registered in Kyrgyzstan 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 6 distinct

Callsign Airline Flights Last seen
AVJ960 Avia Traffic Company 22 2026-05-29
AVJ880 Avia Traffic Company 17 2026-05-30
AVJ879 Avia Traffic Company 16 2026-05-27
AVJ884 Avia Traffic Company 9 2026-05-27
AVJ959 Avia Traffic Company 6 2026-05-15
AVJ883 Avia Traffic Company 1 2026-05-06

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-30 AVJ880 LED → FRU May 30, 08:30 UTCMay 30, 08:45 UTC15m
2026-05-29 AVJ960 DME → FRU May 29, 20:35 UTCMay 30, 03:45 UTC7h 10m
2026-05-29 AVJ960 DME → FRU May 29, 09:00 UTCMay 30, 03:45 UTC18h 45m
2026-05-28 AVJ880 LED → FRU May 28, 11:15 UTCMay 29, 09:00 UTC21h 45m
2026-05-28 AVJ880 LED → FRU May 28, 10:10 UTCMay 29, 09:00 UTC22h 50m
2026-05-27 AVJ879 FRU → LED May 27, 20:30 UTCMay 28, 11:20 UTC14h 50m
2026-05-27 AVJ879 FRU → LED May 27, 08:40 UTCMay 28, 05:05 UTC20h 25m
2026-05-27 AVJ884 DME → FRU May 27, 07:40 UTCMay 27, 07:55 UTC15m
2026-05-26 AVJ880 LED → FRU May 26, 09:59 UTCMay 26, 21:20 UTC11h 20m
2026-05-26 AVJ880 LED → FRU May 26, 08:39 UTCMay 26, 08:59 UTC20m
2026-05-25 AVJ879 FRU → LED May 25, 20:30 UTCMay 26, 05:25 UTC8h 55m
2026-05-25 AVJ960 DME → FRU May 25, 19:35 UTCMay 25, 19:54 UTC20m
2026-05-24 AVJ960 DME → FRU May 24, 19:55 UTCMay 24, 20:15 UTC20m
2026-05-23 AVJ960 DME → FRU May 23, 20:40 UTCMay 24, 08:50 UTC12h 10m
2026-05-22 AVJ880 LED → FRU May 22, 21:00 UTCMay 23, 11:15 UTC14h 15m
2026-05-21 AVJ879 FRU → LED May 21, 03:25 UTCMay 21, 11:10 UTC7h 45m
2026-05-20 AVJ879 FRU → LED May 20, 08:45 UTCMay 21, 05:25 UTC20h 40m
2026-05-20 AVJ884 DME → FRU May 20, 07:45 UTCMay 20, 08:15 UTC30m
2026-05-18 AVJ880 LED → FRU May 18, 20:15 UTCMay 19, 12:40 UTC16h 25m
2026-05-17 AVJ960 DME → FRU May 17, 19:40 UTCMay 17, 20:05 UTC25m
2026-05-16 AVJ960 DME → FRU May 16, 20:25 UTCMay 17, 09:00 UTC12h 35m
2026-05-15 AVJ880 LED → FRU May 15, 21:05 UTCMay 16, 17:01 UTC19h 56m
2026-05-15 AVJ880 LED → FRU May 15, 16:25 UTCMay 16, 11:11 UTC18h 46m
2026-05-15 AVJ959 FRU → DME May 15, 09:05 UTCMay 16, 03:40 UTC18h 34m
2026-05-14 AVJ959 FRU → DME May 14, 20:45 UTCMay 15, 16:50 UTC20h 4m
2026-05-14 AVJ884 DME → FRU May 14, 11:05 UTCMay 15, 09:10 UTC22h 5m
2026-05-14 AVJ880 LED → FRU May 14, 10:55 UTCMay 15, 09:00 UTC22h 5m
2026-05-14 AVJ879 FRU → LED May 14, 03:30 UTCMay 14, 20:50 UTC17h 20m
2026-05-13 AVJ879 FRU → LED May 13, 17:05 UTCMay 14, 11:05 UTC18h 0m
2026-05-13 AVJ879 FRU → LED May 13, 16:50 UTCMay 14, 11:05 UTC18h 15m
2026-05-12 AVJ959 FRU → DME May 12, 20:40 UTCMay 13, 17:15 UTC20h 35m
2026-05-12 AVJ880 LED → FRU May 12, 10:05 UTCMay 12, 20:45 UTC10h 40m
2026-05-12 AVJ879 FRU → LED May 12, 06:50 UTCMay 12, 07:00 UTC10m
2026-05-11 AVJ879 FRU → LED May 11, 17:00 UTCMay 12, 05:25 UTC12h 25m
2026-05-10 AVJ959 FRU → DME May 10, 21:04 UTCMay 11, 21:00 UTC23h 56m
2026-05-10 AVJ959 FRU → DME May 10, 20:54 UTCMay 11, 17:25 UTC20h 31m
2026-05-10 AVJ884 DME → FRU May 10, 08:54 UTCMay 10, 21:10 UTC12h 15m
2026-05-09 AVJ880 LED → FRU May 9, 14:15 UTCMay 10, 09:15 UTC19h 0m
2026-05-09 AVJ880 LED → FRU May 9, 13:10 UTCMay 9, 13:30 UTC20m
2026-05-09 AVJ879 FRU → LED May 9, 03:00 UTCMay 9, 10:25 UTC7h 25m
2026-05-08 AVJ960 DME → FRU May 8, 09:09 UTCMay 9, 08:55 UTC23h 45m
2026-05-07 AVJ884 DME → FRU May 7, 20:55 UTCMay 8, 09:25 UTC12h 30m
2026-05-07 AVJ879 FRU → LED May 7, 03:35 UTCMay 7, 21:05 UTC17h 30m
2026-05-06 AVJ960 DME → FRU May 6, 20:25 UTCMay 7, 11:00 UTC14h 35m
2026-05-06 AVJ960 DME → FRU May 6, 08:35 UTCMay 7, 03:45 UTC19h 9m
2026-05-06 AVJ883 FRU → DME May 6, 06:00 UTCMay 6, 06:10 UTC10m
2026-05-04 AVJ960 DME → FRU May 4, 20:30 UTCMay 4, 20:40 UTC10m
2026-05-02 AVJ960 DME → FRU May 2, 20:35 UTCMay 3, 09:35 UTC12h 59m
2026-05-02 AVJ879 FRU → LED May 2, 03:30 UTCMay 2, 20:55 UTC17h 25m
2026-05-01 AVJ879 FRU → LED May 1, 08:45 UTCMay 2, 05:00 UTC20h 15m

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

Mode-S 60111C frequently asked

What is Mode-S code 60111C?
60111C is an ICAO 24-bit transponder address. Allocated to Kyrgyzstan. Assigned to EX-32014.
Where is Mode-S 60111C registered?
Mode-S code 60111C is allocated to Kyrgyzstan (KG). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 60111C broadcasting right now?
No active broadcast right now. Last signal was 1h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 60111C, octal 30010434, decimal 6,295,836.
What flights does 60111C operate?
Mode-S 60111C has broadcast 6 distinct callsigns, including AVJ960, AVJ880, AVJ879, AVJ884, AVJ959.