sensors Mode-S transponder

0180A6

ICAO 24-bit transponder address · allocated to Libya

Currently assigned to 5A-EMA · AIRBUS A-320

Hex
0180A6
Octal
00300246
Decimal
98,470
Country
LY
Tail
5A-EMA
Type
A320
No current signal · last broadcast 13d ago
Flights observed
179
Distinct callsigns
10
Country
LY
Last broadcast
13d ago

Last known position

Most recent position reported by Mode-S 0180A6.

Country allocation

The ICAO 24-bit address 0180A6 falls within the block assigned to Libya (LY) by ICAO Annex 10, Volume III. Every aircraft registered in Libya 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 10 distinct

Callsign Airline Flights Last seen
OYA593 - 45 2026-06-28
OYA503 - 37 2026-06-28
OYA502 Fly OYA 34 2026-06-28
OYA592 - 31 2026-06-28
OYA500 Fly OYA 13 2026-06-22
OYA501 Fly OYA 12 2026-06-22
OYA510 Fly OYA 4 2026-06-23
OYA511 - 1 2026-06-23
OYA5090 - 1 2026-06-30
OYA5061 - 1 2026-05-04

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-30 OYA5090 - Jun 30, 07:40 UTCJun 30, 09:20 UTC1h 40m
2026-06-28 OYA503 - Jun 28, 21:45 UTCJun 29, 00:29 UTC2h 45m
2026-06-28 OYA502 MJI → IST Jun 28, 17:19 UTCJun 28, 19:59 UTC2h 40m
2026-06-28 OYA593 - Jun 28, 11:29 UTCJun 28, 13:29 UTC2h 0m
2026-06-28 OYA592 - Jun 28, 07:40 UTCJun 28, 08:09 UTC30m
2026-06-27 OYA593 - Jun 27, 11:39 UTCJun 27, 13:44 UTC2h 5m
2026-06-27 OYA592 - Jun 27, 08:05 UTCJun 27, 09:34 UTC1h 30m
2026-06-25 OYA503 - Jun 25, 21:40 UTCJun 26, 00:50 UTC3h 10m
2026-06-25 OYA502 MJI → IST Jun 25, 17:20 UTCJun 25, 19:54 UTC2h 35m
2026-06-25 OYA592 - Jun 25, 07:59 UTCJun 25, 13:55 UTC5h 55m
2026-06-24 OYA503 - Jun 24, 22:10 UTCJun 25, 01:24 UTC3h 15m
2026-06-24 OYA502 MJI → IST Jun 24, 17:40 UTCJun 24, 20:09 UTC2h 30m
2026-06-24 OYA593 - Jun 24, 12:04 UTCJun 24, 14:20 UTC2h 15m
2026-06-24 OYA592 - Jun 24, 07:30 UTCJun 24, 09:09 UTC1h 40m
2026-06-23 OYA511 - Jun 23, 19:39 UTCJun 23, 19:59 UTC20m
2026-06-23 OYA510 MJI → SEB Jun 23, 16:20 UTCJun 23, 16:44 UTC25m
2026-06-23 OYA593 - Jun 23, 11:49 UTCJun 23, 14:04 UTC2h 15m
2026-06-23 OYA592 - Jun 23, 07:40 UTCJun 23, 09:14 UTC1h 35m
2026-06-22 OYA501 IST → MJI Jun 22, 16:34 UTCJun 22, 19:29 UTC2h 55m
2026-06-22 OYA500 MJI → IST Jun 22, 11:30 UTCJun 22, 14:19 UTC2h 50m
2026-06-21 OYA503 - Jun 21, 21:44 UTCJun 22, 00:50 UTC3h 5m
2026-06-21 OYA502 MJI → IST Jun 21, 17:35 UTCJun 21, 20:14 UTC2h 40m
2026-06-21 OYA593 - Jun 21, 12:55 UTCJun 21, 13:29 UTC35m
2026-06-21 OYA593 - Jun 21, 11:24 UTCJun 21, 11:34 UTC10m
2026-06-21 OYA592 - Jun 21, 07:09 UTCJun 21, 08:49 UTC1h 40m
2026-06-20 OYA510 MJI → SEB Jun 20, 16:05 UTCJun 20, 16:19 UTC15m
2026-06-20 OYA593 - Jun 20, 11:49 UTCJun 20, 13:49 UTC2h 0m
2026-06-20 OYA592 - Jun 20, 07:39 UTCJun 20, 09:14 UTC1h 35m
2026-06-18 OYA503 - Jun 18, 21:45 UTCJun 19, 00:55 UTC3h 9m
2026-06-18 OYA502 MJI → IST Jun 18, 17:15 UTCJun 18, 20:05 UTC2h 50m
2026-06-17 OYA503 - Jun 17, 22:30 UTCJun 18, 01:30 UTC3h 0m
2026-06-17 OYA502 MJI → IST Jun 17, 18:15 UTCJun 17, 21:20 UTC3h 5m
2026-06-17 OYA593 - Jun 17, 11:35 UTCJun 17, 13:55 UTC2h 20m
2026-06-17 OYA592 - Jun 17, 07:30 UTCJun 17, 09:10 UTC1h 40m
2026-06-16 OYA593 - Jun 16, 11:20 UTCJun 16, 13:19 UTC2h 0m
2026-06-16 OYA592 - Jun 16, 07:45 UTCJun 16, 08:20 UTC35m
2026-06-15 OYA501 IST → MJI Jun 15, 16:40 UTCJun 15, 19:39 UTC3h 0m
2026-06-15 OYA500 MJI → IST Jun 15, 12:00 UTCJun 15, 14:50 UTC2h 50m
2026-06-14 OYA503 - Jun 14, 22:55 UTCJun 15, 01:59 UTC3h 4m
2026-06-14 OYA502 MJI → IST Jun 14, 17:40 UTCJun 14, 20:40 UTC3h 0m
2026-06-14 OYA593 - Jun 14, 12:55 UTCJun 14, 13:45 UTC50m
2026-06-14 OYA592 - Jun 14, 07:50 UTCJun 14, 09:20 UTC1h 30m
2026-06-13 OYA593 CAI → MJI Jun 13, 11:30 UTCJun 13, 13:30 UTC2h 0m
2026-06-13 OYA592 - Jun 13, 08:00 UTCJun 13, 09:30 UTC1h 30m
2026-06-11 OYA503 IST → MJI Jun 11, 21:45 UTCJun 12, 00:30 UTC2h 45m
2026-06-11 OYA502 MJI → IST Jun 11, 17:15 UTCJun 11, 20:10 UTC2h 55m
2026-06-11 OYA593 CAI → MJI Jun 11, 11:45 UTCJun 11, 14:10 UTC2h 25m
2026-06-11 OYA592 MJI → CAI Jun 11, 07:50 UTCJun 11, 09:40 UTC1h 50m
2026-06-10 OYA503 IST → MJI Jun 10, 22:15 UTCJun 11, 01:10 UTC2h 55m
2026-06-10 OYA502 MJI → IST Jun 10, 18:00 UTCJun 10, 21:00 UTC3h 0m

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

Mode-S 0180A6 frequently asked

What is Mode-S code 0180A6?
0180A6 is an ICAO 24-bit transponder address. Allocated to Libya. Assigned to 5A-EMA.
Where is Mode-S 0180A6 registered?
Mode-S code 0180A6 is allocated to Libya (LY). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0180A6 broadcasting right now?
No active broadcast right now. Last signal was 13d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0180A6, octal 00300246, decimal 98,470.
What flights does 0180A6 operate?
Mode-S 0180A6 has broadcast 10 distinct callsigns, including OYA593, OYA503, OYA502, OYA592, OYA500.