sensors Mode-S transponder
01809C
ICAO 24-bit transponder address · allocated to Libya
Currently assigned to 5A-DFN · CESSNA 680 Citation Latitude
- Hex
- 01809C
- Octal
- 00300234
- Decimal
- 98,460
- Country
- LY
- Tail
- 5A-DFN
- Type
- C68A
- Flights observed
- 86
- Distinct callsigns
- 1
- Country
- LY
- Last broadcast
- 16h ago
Last known position
Country allocation
The ICAO 24-bit address 01809C 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| 5ADFN | - | 86 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | 5ADFN | - | Jul 17, 11:04 UTC | Jul 17, 11:45 UTC | 40m |
| 2026-07-15 | 5ADFN | - | Jul 15, 19:25 UTC | Jul 15, 21:40 UTC | 2h 15m |
| 2026-07-15 | 5ADFN | - | Jul 15, 13:25 UTC | Jul 15, 15:30 UTC | 2h 5m |
| 2026-07-14 | 5ADFN | - | Jul 14, 15:40 UTC | Jul 14, 16:00 UTC | 20m |
| 2026-07-14 | 5ADFN | - | Jul 14, 14:15 UTC | Jul 14, 15:05 UTC | 50m |
| 2026-07-10 | 5ADFN | - | Jul 10, 17:30 UTC | Jul 10, 17:55 UTC | 25m |
| 2026-07-10 | 5ADFN | - | Jul 10, 15:55 UTC | Jul 10, 16:50 UTC | 55m |
| 2026-07-10 | 5ADFN | - | Jul 10, 11:50 UTC | Jul 10, 12:05 UTC | 15m |
| 2026-07-09 | 5ADFN | - | Jul 9, 17:55 UTC | Jul 9, 18:25 UTC | 30m |
| 2026-07-09 | 5ADFN | - | Jul 9, 14:00 UTC | Jul 9, 17:15 UTC | 3h 15m |
| 2026-07-09 | 5ADFN | - | Jul 9, 09:20 UTC | Jul 9, 12:30 UTC | 3h 10m |
| 2026-07-08 | 5ADFN | - | Jul 8, 17:15 UTC | Jul 8, 19:35 UTC | 2h 20m |
| 2026-07-08 | 5ADFN | MJI → MRA | Jul 8, 16:10 UTC | Jul 8, 16:35 UTC | 25m |
| 2026-07-06 | 5ADFN | - | Jul 6, 14:30 UTC | Jul 6, 16:00 UTC | 1h 30m |
| 2026-07-06 | 5ADFN | - | Jul 6, 11:50 UTC | Jul 6, 13:15 UTC | 1h 25m |
| 2026-07-05 | 5ADFN | - | Jul 5, 13:15 UTC | Jul 5, 15:25 UTC | 2h 10m |
| 2026-07-05 | 5ADFN | - | Jul 5, 09:45 UTC | Jul 5, 11:25 UTC | 1h 40m |
| 2026-07-03 | 5ADFN | - | Jul 3, 18:25 UTC | Jul 3, 18:50 UTC | 25m |
| 2026-07-03 | 5ADFN | - | Jul 3, 13:55 UTC | Jul 3, 17:05 UTC | 3h 10m |
| 2026-07-03 | 5ADFN | - | Jul 3, 10:55 UTC | Jul 3, 11:10 UTC | 15m |
| 2026-06-30 | 5ADFN | - | Jun 30, 11:40 UTC | Jun 30, 13:45 UTC | 2h 5m |
| 2026-06-30 | 5ADFN | - | Jun 30, 07:50 UTC | Jun 30, 09:40 UTC | 1h 50m |
| 2026-06-29 | 5ADFN | - | Jun 29, 22:05 UTC | Jun 30, 01:04 UTC | 3h 0m |
| 2026-06-29 | 5ADFN | - | Jun 29, 18:14 UTC | Jun 29, 20:59 UTC | 2h 45m |
| 2026-06-26 | 5ADFN | - | Jun 26, 10:39 UTC | Jun 26, 11:00 UTC | 20m |
| 2026-06-26 | 5ADFN | - | Jun 26, 05:35 UTC | Jun 26, 06:15 UTC | 40m |
| 2026-06-25 | 5ADFN | - | Jun 25, 10:09 UTC | Jun 25, 12:19 UTC | 2h 10m |
| 2026-06-25 | 5ADFN | - | Jun 25, 07:19 UTC | Jun 25, 07:49 UTC | 30m |
| 2026-06-19 | 5ADFN | - | Jun 19, 19:49 UTC | Jun 19, 21:34 UTC | 1h 45m |
| 2026-06-19 | 5ADFN | MJI → SKG | Jun 19, 14:49 UTC | Jun 19, 16:55 UTC | 2h 5m |
| 2026-06-17 | 5ADFN | MJI → MRA | Jun 17, 11:55 UTC | Jun 17, 17:40 UTC | 5h 45m |
| 2026-06-16 | 5ADFN | - | Jun 16, 21:15 UTC | Jun 16, 23:35 UTC | 2h 20m |
| 2026-06-15 | 5ADFN | - | Jun 15, 18:10 UTC | Jun 15, 20:45 UTC | 2h 35m |
| 2026-06-15 | 5ADFN | - | Jun 15, 14:34 UTC | Jun 15, 15:30 UTC | 55m |
| 2026-06-14 | 5ADFN | - | Jun 14, 15:10 UTC | Jun 14, 21:05 UTC | 5h 55m |
| 2026-06-13 | 5ADFN | - | Jun 13, 11:50 UTC | Jun 13, 13:05 UTC | 1h 15m |
| 2026-06-13 | 5ADFN | - | Jun 13, 09:10 UTC | Jun 13, 10:35 UTC | 1h 25m |
| 2026-06-11 | 5ADFN | - | Jun 11, 11:00 UTC | Jun 11, 11:10 UTC | 10m |
| 2026-06-10 | 5ADFN | - | Jun 10, 20:05 UTC | Jun 10, 22:10 UTC | 2h 5m |
| 2026-06-10 | 5ADFN | - | Jun 10, 16:15 UTC | Jun 10, 18:50 UTC | 2h 35m |
| 2026-06-10 | 5ADFN | - | Jun 10, 14:15 UTC | Jun 10, 15:00 UTC | 45m |
| 2026-06-09 | 5ADFN | - | Jun 9, 13:35 UTC | Jun 9, 14:25 UTC | 50m |
| 2026-06-09 | 5ADFN | - | Jun 9, 11:15 UTC | Jun 9, 12:05 UTC | 50m |
| 2026-06-08 | 5ADFN | - | Jun 8, 14:15 UTC | Jun 8, 16:25 UTC | 2h 10m |
| 2026-06-08 | 5ADFN | MJI → MRA | Jun 8, 12:45 UTC | Jun 8, 13:05 UTC | 20m |
| 2026-06-06 | 5ADFN | - | Jun 6, 20:10 UTC | Jun 6, 20:45 UTC | 35m |
| 2026-06-06 | 5ADFN | - | Jun 6, 13:54 UTC | Jun 6, 14:04 UTC | 10m |
| 2026-06-06 | 5ADFN | - | Jun 6, 07:40 UTC | Jun 6, 12:45 UTC | 5h 5m |
| 2026-06-03 | 5ADFN | - | Jun 3, 12:50 UTC | Jun 3, 21:35 UTC | 8h 45m |
| 2026-06-02 | 5ADFN | - | Jun 2, 08:40 UTC | Jun 2, 14:35 UTC | 5h 55m |
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-DFN page for operator, model, and routing details .