sensors Mode-S transponder
4D02A1
ICAO 24-bit transponder address · allocated to Luxembourg
Currently assigned to LX-ZAP · PILATUS PC-24
- Hex
- 4D02A1
- Octal
- 23201241
- Decimal
- 5,046,945
- Country
- LU
- Tail
- LX-ZAP
- Type
- PC24
- Flights observed
- 51
- Distinct callsigns
- 1
- Country
- LU
- Last broadcast
- 17d ago
Last known position
Country allocation
The ICAO 24-bit address 4D02A1 falls within the block assigned to Luxembourg (LU) by ICAO Annex 10, Volume III. Every aircraft registered in Luxembourg 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 |
|---|---|---|---|
| JFA99X | - | 51 | 2026-05-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-12 | JFA99X | - | May 12, 08:15 UTC | May 12, 09:35 UTC | 1h 20m |
| 2026-05-10 | JFA99X | - | May 10, 14:25 UTC | May 10, 15:19 UTC | 55m |
| 2026-05-08 | JFA99X | - | May 8, 15:20 UTC | May 8, 15:45 UTC | 25m |
| 2026-05-08 | JFA99X | - | May 8, 13:40 UTC | May 8, 14:40 UTC | 1h 0m |
| 2026-05-08 | JFA99X | - | May 8, 09:09 UTC | May 8, 09:39 UTC | 30m |
| 2026-05-08 | JFA99X | GVA → OXF | May 8, 06:30 UTC | May 8, 07:55 UTC | 1h 25m |
| 2026-05-07 | JFA99X | - | May 7, 15:50 UTC | May 7, 16:40 UTC | 50m |
| 2026-05-07 | JFA99X | - | May 7, 12:15 UTC | May 7, 13:45 UTC | 1h 30m |
| 2026-05-05 | JFA99X | - | May 5, 15:55 UTC | May 5, 17:30 UTC | 1h 35m |
| 2026-05-05 | JFA99X | - | May 5, 13:50 UTC | May 5, 15:10 UTC | 1h 20m |
| 2026-05-03 | JFA99X | - | May 3, 14:05 UTC | May 3, 15:25 UTC | 1h 20m |
| 2026-05-01 | JFA99X | - | May 1, 17:15 UTC | May 1, 18:30 UTC | 1h 15m |
| 2026-05-01 | JFA99X | - | May 1, 14:10 UTC | May 1, 16:00 UTC | 1h 50m |
| 2026-05-01 | JFA99X | - | May 1, 10:40 UTC | May 1, 12:55 UTC | 2h 15m |
| 2026-04-30 | JFA99X | - | Apr 30, 13:30 UTC | Apr 30, 14:55 UTC | 1h 25m |
| 2026-04-27 | JFA99X | - | Apr 27, 12:30 UTC | Apr 27, 12:55 UTC | 25m |
| 2026-04-27 | JFA99X | GRS → ZRH | Apr 27, 10:30 UTC | Apr 27, 11:40 UTC | 1h 10m |
| 2026-04-27 | JFA99X | - | Apr 27, 08:10 UTC | Apr 27, 09:05 UTC | 55m |
| 2026-04-26 | JFA99X | - | Apr 26, 14:15 UTC | Apr 26, 15:45 UTC | 1h 30m |
| 2026-04-25 | JFA99X | - | Apr 25, 14:45 UTC | Apr 25, 16:10 UTC | 1h 25m |
| 2026-04-23 | JFA99X | - | Apr 23, 13:35 UTC | Apr 23, 14:25 UTC | 50m |
| 2026-04-23 | JFA99X | - | Apr 23, 09:25 UTC | Apr 23, 11:15 UTC | 1h 50m |
| 2026-04-23 | JFA99X | - | Apr 23, 06:15 UTC | Apr 23, 07:05 UTC | 50m |
| 2026-04-22 | JFA99X | - | Apr 22, 13:15 UTC | Apr 22, 14:20 UTC | 1h 5m |
| 2026-04-22 | JFA99X | - | Apr 22, 09:45 UTC | Apr 22, 10:35 UTC | 50m |
| 2026-04-20 | JFA99X | - | Apr 20, 14:25 UTC | Apr 20, 15:10 UTC | 45m |
| 2026-04-20 | JFA99X | - | Apr 20, 11:30 UTC | Apr 20, 13:10 UTC | 1h 40m |
| 2026-04-20 | JFA99X | - | Apr 20, 07:35 UTC | Apr 20, 10:00 UTC | 2h 25m |
| 2026-04-19 | JFA99X | - | Apr 19, 15:00 UTC | Apr 19, 15:25 UTC | 25m |
| 2026-04-19 | JFA99X | LCY → LUG | Apr 19, 13:05 UTC | Apr 19, 14:30 UTC | 1h 25m |
| 2026-04-19 | JFA99X | - | Apr 19, 11:40 UTC | Apr 19, 11:55 UTC | 15m |
| 2026-04-18 | JFA99X | PEG → LTN | Apr 18, 13:25 UTC | Apr 18, 15:45 UTC | 2h 20m |
| 2026-04-18 | JFA99X | - | Apr 18, 11:20 UTC | Apr 18, 12:00 UTC | 40m |
| 2026-04-17 | JFA99X | - | Apr 17, 15:20 UTC | Apr 17, 15:50 UTC | 30m |
| 2026-04-17 | JFA99X | - | Apr 17, 15:00 UTC | Apr 17, 15:15 UTC | 15m |
| 2026-04-17 | JFA99X | - | Apr 17, 09:20 UTC | Apr 17, 10:00 UTC | 40m |
| 2026-04-17 | JFA99X | - | Apr 17, 09:05 UTC | Apr 17, 09:15 UTC | 10m |
| 2026-04-17 | JFA99X | - | Apr 17, 07:20 UTC | Apr 17, 07:35 UTC | 15m |
| 2026-04-17 | JFA99X | - | Apr 17, 06:55 UTC | Apr 17, 07:15 UTC | 20m |
| 2026-04-16 | JFA99X | - | Apr 16, 17:15 UTC | Apr 16, 17:30 UTC | 15m |
| 2026-04-16 | JFA99X | - | Apr 16, 15:25 UTC | Apr 16, 17:10 UTC | 1h 45m |
| 2026-04-16 | JFA99X | - | Apr 16, 09:10 UTC | Apr 16, 09:39 UTC | 30m |
| 2026-04-16 | JFA99X | - | Apr 16, 08:00 UTC | Apr 16, 09:05 UTC | 1h 5m |
| 2026-04-14 | JFA99X | - | Apr 14, 15:40 UTC | Apr 14, 16:45 UTC | 1h 5m |
| 2026-04-14 | JFA99X | - | Apr 14, 12:50 UTC | Apr 14, 14:15 UTC | 1h 25m |
| 2026-04-14 | JFA99X | - | Apr 14, 11:05 UTC | Apr 14, 11:50 UTC | 45m |
| 2026-04-13 | JFA99X | - | Apr 13, 11:55 UTC | Apr 13, 12:05 UTC | 10m |
| 2026-04-13 | JFA99X | BQH → GVA | Apr 13, 10:40 UTC | Apr 13, 12:05 UTC | 1h 25m |
| 2026-04-13 | JFA99X | - | Apr 13, 08:20 UTC | Apr 13, 08:30 UTC | 10m |
| 2026-04-13 | JFA99X | - | Apr 13, 07:55 UTC | Apr 13, 08:30 UTC | 35m |
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 LX-ZAP page for operator, model, and routing details .