sensors Mode-S transponder
0180AC
ICAO 24-bit transponder address · allocated to Libya
Currently assigned to 5A-BAA · AIRBUS A-320
- Hex
- 0180AC
- Octal
- 00300254
- Decimal
- 98,476
- Country
- LY
- Tail
- 5A-BAA
- Type
- A320
- Flights observed
- 50
- Distinct callsigns
- 20
- Country
- LY
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 0180AC 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| MNS503 | Ministic Air | 15 | 2026-05-29 |
| MNS502 | Ministic Air | 14 | 2026-05-29 |
| MNS505 | Ministic Air | 2 | 2026-05-24 |
| MNS504 | Ministic Air | 2 | 2026-05-17 |
| MNS400 | Ministic Air | 2 | 2026-05-28 |
| MNS4205 | - | 1 | 2026-05-05 |
| MNS4204 | - | 1 | 2026-04-26 |
| MNS407 | Ministic Air | 1 | 2026-05-21 |
| MNS401 | Ministic Air | 1 | 2026-05-11 |
| MNS123 | Ministic Air | 1 | 2026-05-05 |
| MNS122 | Ministic Air | 1 | 2026-05-05 |
| BRQ1273 | - | 1 | 2026-05-15 |
| BRQ1271 | - | 1 | 2026-05-14 |
| BRQ1261 | - | 1 | 2026-05-14 |
| BRQ1257 | - | 1 | 2026-05-13 |
| BRQ1249 | - | 1 | 2026-05-13 |
| BRQ1242 | - | 1 | 2026-05-12 |
| BRQ1236 | - | 1 | 2026-05-11 |
| BRQ1233 | - | 1 | 2026-05-10 |
| BRQ1220 | - | 1 | 2026-05-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | MNS503 | IST → MJI | May 29, 18:30 UTC | May 29, 21:20 UTC | 2h 50m |
| 2026-05-29 | MNS502 | MJI → IST | May 29, 14:15 UTC | May 29, 17:00 UTC | 2h 45m |
| 2026-05-28 | MNS503 | IST → MJI | May 28, 18:20 UTC | May 28, 21:05 UTC | 2h 45m |
| 2026-05-28 | MNS502 | MJI → IST | May 28, 13:50 UTC | May 28, 17:00 UTC | 3h 10m |
| 2026-05-28 | MNS400 | MJI → TUN | May 28, 09:25 UTC | May 28, 12:20 UTC | 2h 55m |
| 2026-05-24 | MNS505 | IST → MJI | May 24, 21:15 UTC | May 25, 04:05 UTC | 6h 50m |
| 2026-05-22 | MNS503 | IST → MJI | May 22, 18:30 UTC | May 22, 21:20 UTC | 2h 50m |
| 2026-05-22 | MNS502 | MJI → IST | May 22, 14:00 UTC | May 22, 16:45 UTC | 2h 45m |
| 2026-05-21 | MNS407 | TUN → MJI | May 21, 17:25 UTC | May 21, 20:15 UTC | 2h 50m |
| 2026-05-18 | MNS505 | IST → MJI | May 18, 01:25 UTC | May 18, 04:25 UTC | 3h 0m |
| 2026-05-17 | MNS504 | MJI → IST | May 17, 23:25 UTC | May 17, 23:35 UTC | 10m |
| 2026-05-17 | MNS504 | MJI → IST | May 17, 20:55 UTC | May 17, 22:50 UTC | 1h 55m |
| 2026-05-15 | MNS502 | MJI → IST | May 15, 14:30 UTC | May 15, 21:55 UTC | 7h 24m |
| 2026-05-15 | BRQ1273 | - | May 15, 02:05 UTC | May 15, 11:10 UTC | 9h 5m |
| 2026-05-14 | BRQ1271 | - | May 14, 14:50 UTC | May 15, 00:05 UTC | 9h 15m |
| 2026-05-14 | BRQ1261 | - | May 14, 02:20 UTC | May 14, 02:40 UTC | 20m |
| 2026-05-13 | BRQ1257 | - | May 13, 06:25 UTC | May 13, 15:40 UTC | 9h 15m |
| 2026-05-13 | BRQ1249 | - | May 13, 00:10 UTC | May 13, 00:40 UTC | 30m |
| 2026-05-12 | BRQ1242 | - | May 12, 04:30 UTC | May 13, 00:40 UTC | 20h 10m |
| 2026-05-11 | BRQ1236 | - | May 11, 16:10 UTC | May 11, 16:40 UTC | 30m |
| 2026-05-11 | MNS401 | TUN → MJI | May 11, 11:55 UTC | May 11, 12:35 UTC | 40m |
| 2026-05-11 | MNS400 | MJI → TUN | May 11, 09:40 UTC | May 11, 10:10 UTC | 30m |
| 2026-05-10 | BRQ1233 | - | May 10, 21:30 UTC | May 11, 07:10 UTC | 9h 40m |
| 2026-05-09 | BRQ1220 | - | May 9, 14:25 UTC | May 9, 22:55 UTC | 8h 30m |
| 2026-05-08 | MNS503 | IST → MJI | May 8, 14:05 UTC | May 8, 21:30 UTC | 7h 25m |
| 2026-05-07 | MNS503 | IST → MJI | May 7, 19:45 UTC | May 7, 22:54 UTC | 3h 9m |
| 2026-05-07 | MNS502 | MJI → IST | May 7, 17:00 UTC | May 7, 17:10 UTC | 10m |
| 2026-05-07 | MNS502 | MJI → IST | May 7, 15:40 UTC | May 7, 16:30 UTC | 50m |
| 2026-05-07 | MNS502 | MJI → IST | May 7, 14:30 UTC | May 7, 15:35 UTC | 1h 5m |
| 2026-05-05 | MNS123 | BEN → MJI | May 5, 19:15 UTC | May 5, 19:35 UTC | 20m |
| 2026-05-05 | MNS122 | MJI → BEN | May 5, 16:50 UTC | May 5, 17:05 UTC | 15m |
| 2026-05-05 | MNS4205 | - | May 5, 13:25 UTC | May 5, 13:40 UTC | 15m |
| 2026-04-26 | MNS4204 | - | Apr 26, 16:15 UTC | Apr 26, 16:40 UTC | 25m |
| 2026-04-24 | MNS503 | IST → MJI | Apr 24, 13:50 UTC | Apr 24, 21:20 UTC | 7h 30m |
| 2026-04-21 | MNS503 | IST → MJI | Apr 21, 22:55 UTC | Apr 22, 01:55 UTC | 3h 0m |
| 2026-04-21 | MNS502 | MJI → IST | Apr 21, 15:10 UTC | Apr 21, 17:40 UTC | 2h 30m |
| 2026-04-20 | MNS503 | IST → MJI | Apr 20, 14:00 UTC | Apr 20, 21:25 UTC | 7h 25m |
| 2026-04-16 | MNS503 | IST → MJI | Apr 16, 19:15 UTC | Apr 16, 20:15 UTC | 1h 0m |
| 2026-04-16 | MNS503 | IST → MJI | Apr 16, 18:35 UTC | Apr 16, 19:10 UTC | 35m |
| 2026-04-16 | MNS502 | MJI → IST | Apr 16, 15:25 UTC | Apr 16, 17:05 UTC | 1h 40m |
| 2026-04-16 | MNS502 | MJI → IST | Apr 16, 14:25 UTC | Apr 16, 14:45 UTC | 20m |
| 2026-04-15 | MNS503 | IST → MJI | Apr 15, 21:15 UTC | Apr 15, 21:35 UTC | 20m |
| 2026-04-15 | MNS503 | IST → MJI | Apr 15, 19:10 UTC | Apr 15, 20:25 UTC | 1h 15m |
| 2026-04-15 | MNS502 | MJI → IST | Apr 15, 14:25 UTC | Apr 15, 14:50 UTC | 24m |
| 2026-04-13 | MNS503 | - | Apr 13, 19:50 UTC | Apr 13, 21:25 UTC | 1h 35m |
| 2026-04-13 | MNS503 | - | Apr 13, 18:30 UTC | Apr 13, 20:05 UTC | 1h 35m |
| 2026-04-13 | MNS502 | - | Apr 13, 16:15 UTC | Apr 13, 16:50 UTC | 35m |
| 2026-04-13 | MNS502 | - | Apr 13, 15:50 UTC | Apr 13, 16:50 UTC | 1h 0m |
| 2026-04-13 | MNS502 | - | Apr 13, 14:20 UTC | Apr 13, 16:15 UTC | 1h 55m |
| 2026-04-12 | MNS503 | - | Apr 12, 18:50 UTC | Apr 12, 20:15 UTC | 1h 25m |
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-BAA page for operator, model, and routing details .